DCS Interface Requirements Sample Clauses

DCS Interface Requirements. 8.7.1 Where technically available in BellSouth’s DCS System and supported by BellSouth’s network management software, BellSouth shall provide physical interfaces on DS0, DS1, and VT1.5 channel cross-connect devices at the DS1 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, and ITU standards., 8.7.2 Where technically available in BellSouth’s DCS System and supported by BellSouth’s network management software, BellSouth shall provide physical interfaces on DS3 channel cross-connect devices at the DS3 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI and ITU standards. 8.7.3 Where technically available in BellSouth’s DCS System and supported by BellSouth’s network management software, BellSouth shall provide physical interfaces on STS-1 cross-connect devices at the OC-3 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI and , ITU standards. 8.7.4 Where technically available in BellSouth’s DCS System and supported by BellSouth’s network management software, Interfaces on all other cross- connect devices shall be in compliance with applicable Bellcore, ANSI and , ITU , standards.
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
DCS Interface Requirements. 7.7.1 U S WEST shall provide physical interfaces on DS-0, DS-1, and VT1.5 channel cross-connect devicxx xx xxx DS-1 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and AT&T standards. 7.7.2 U S WEST shall provide physical interfaces on DS-3 channel cross-connect devices at the DS-3 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and AT&T standards. 7.7.3 U S WEST shall provide physical interfaces on STS-1 cross- connect devices at the OC-3 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and AT&T standards. 7.7.4 Interfaces on all other cross-connect devices shall be in compliance with applicable Bellcore, ANSI, ITU, and AT&T standards.
Sample 1
DCS Interface Requirements. 10.7.1 BellSouth shall provide physical interfaces on DS0, DS1, and VT1.5 channel cross-connect devices at the DS1 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and MCIm standards. 10.7.2 BellSouth shall provide physical interfaces on DS3 channel cross-connect devices at the DS3 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and MCIm standards. 10.7.3 BellSouth shall provide physical interfaces on STS-1 cross-connect devices at the OC-3 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and MCIm standards. 10.7.4 Interfaces on all other cross-connect devices shall be in compliance with applicable Bellcore, ANSI, ITU, and MCIm standards. Attachment III - 37 MCIm-BellSouth Mississippi Interconnection Agreement
Sample 1
DCS Interface Requirements. 7.7.1 U S WEST shall provide physical interfaces on XX-0, XX-0, and VT1.5 channel cross-connect devices at the DS-1 rate or higher. In all such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and Pac-West standards. 7.7.2 U S WEST shall provide physical interfaces on DS-3 channel cross-connect devices at the DS-3 rate or higher. In ail such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and Pac-West standards. 7.7.3 U S WEST shall provide physical interfaces on STS-1 cross-connect devices at the OC-3 rate or higher. In ail such cases, these interfaces shall be in compliance with applicable Bellcore, ANSI, ITU, and Pac-West standards. 7.7.4 Interfaces on all other cross-connect devices shall be in compliance with applicable Bellcore, ANSI, ITU, and Pac-West standards.
Sample 1

Related to DCS Interface Requirements

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • Service Requirements Grantee shall:

  • Time Requirements The Independent Contractor will not be required to follow or establish a regular or daily work schedule, but shall devote during the term of this Agreement the time, energy and skill as necessary to perform the services of this engagement and shall, periodically or at any time upon the request of the Company, submit information as to the amount of time worked and scope of work performed.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Invoice Requirements Contractor hereby waives the right to enforce any term which contradicts or modifies any term of the solicitation or any Contract that may result, including subsequent amendments to the Contract, or would result in an unencumbered expense if enforced against the state. Contract quote and invoice must contain, at a minimum:

  • Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the Xxx Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!