Conformance to Sprint PCS Technical Program Requirements Clause Samples

Conformance to Sprint PCS Technical Program Requirements. (a) Manager must meet or exceed the Sprint PCS Technical Program Requirements established by Sprint PCS from time to time for the Sprint PCS Network. Manager will be deemed to meet the Sprint PCS Technical Program Requirements if: (i) Manager operates the Service Area Network at a level equal to or better than the lower of the Operational Level of Sprint PCS or the operational level contemplated by the Sprint PCS Technical Program Requirements; or (ii) Sprint PCS is responsible under the Services Agreement to ensure the Service Area Network complies with the Sprint PCS Technical Program Requirements. (b) Manager must demonstrate to Sprint PCS that Manager has complied with the Sprint PCS Technical Program Requirements prior to connecting the Service Area Network to the rest of the Sprint PCS Network. Once the Service Area Network is connected to the Sprint PCS Network, Manager must continue to comply with the Sprint PCS Technical Program Requirements. Sprint PCS agrees that the Sprint PCS Technical Program Requirements adopted for Manager will be the same Sprint PCS Technical Program Requirements applied by Sprint PCS to the Sprint PCS Network.
View SourceView Similar (16)
Conformance to Sprint PCS Technical Program Requirements. The first sentence of Section 7.1(b) is replaced by the following sentence: "Manager must demonstrate to Sprint PCS' reasonable satisfaction that Manager has complied with the Sprint PCS Technical Program Requirements prior to connecting the Service Area Network to the rest of the Sprint PCS Network."
View SourceView Similar (3)

Related to Conformance to Sprint PCS Technical Program Requirements

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Clinical Data and Regulatory Compliance The preclinical tests and clinical trials, and other studies (collectively, “studies”) that are described in, or the results of which are referred to in, the Registration Statement or the Prospectus were and, if still pending, are being conducted in all material respects in accordance with the protocols, procedures and controls designed and approved for such studies and with standard medical and scientific research procedures; each description of the results of such studies is accurate and complete in all material respects and fairly presents the data derived from such studies, and the Company and its subsidiaries have no knowledge of any other studies the results of which are inconsistent with, or otherwise call into question, the results described or referred to in the Registration Statement or the Prospectus; the Company and its subsidiaries have made all such filings and obtained all such approvals as may be required by the Food and Drug Administration of the U.S. Department of Health and Human Services or any committee thereof or from any other U.S. or foreign government or drug or medical device regulatory agency, or health care facility Institutional Review Board (collectively, the “Regulatory Agencies”); neither the Company nor any of its subsidiaries has received any notice of, or correspondence from, any Regulatory Agency requiring the termination, suspension or modification of any clinical trials that are described or referred to in the Registration Statement or the Prospectus; and the Company and its subsidiaries have each operated and currently are in compliance in all material respects with all applicable rules, regulations and policies of the Regulatory Agencies.

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.