Test Samples The Contractor is responsible for providing Samples of sufficient size for test purposes and for coordinating such tests with the Work Progress Schedule to avoid delay.
Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.
Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.
Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.
Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.
EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.
ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.
Review and Selection Process The Project Narratives of SAMHSA applications are peer-reviewed according to the evaluation criteria listed above. Decisions to fund a grant are based on the strengths and weaknesses of the application as identified by peer reviewers. The results of the peer review are advisory in nature. The program office and approving official make the final determination for funding based on the following: • Individual awards over $250,000 are approved by the Center for Mental Health Services National Advisory Council; • Availability of funds; • Equitable distribution of awards in terms of geography (including urban, rural, and remote settings) and balance among populations of focus and program size; • Submission of any required documentation that must be submitted prior to making an award; and • SAMHSA is required to review and consider any information about your organization that is in the Federal Award Performance and Integrity Information System (FAPIIS). In accordance with 45 CFR 75.212, SAMHSA reserves the right not to make an award to an entity if that entity does not meet the minimum qualification standards as described in section 75.205(a)(2). If SAMHSA chooses not to award a fundable application in accordance with 45 CFR 75.205(a)(2), SAMHSA must report that determination to the designated integrity and performance system accessible through the System for Award Management (XXX) [currently, FAPIIS]. You may review and comment on any information about your organization that a federal awarding agency previously entered. XXXXXX will consider your comments, in addition to other information in FAPIIS in making a judgment about your organization’s integrity, business ethics, and record of performance under federal awards when completing the review of risk posed as described in 45 CFR 75.205 HHS Awarding Agency Review of Risk by Applicants.
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.
