Network Architecture Requirements Sample Clauses

Network Architecture Requirements. 4.1 XO will establish a physical point of interconnection (POI) in each mandatory local calling area in which it has assigned telephone numbers (NPA/NXXs) in the Local Exchange Routing Guide (LERG). Each Party shall be financially responsible for one hundred percent (100%) of the facilities, trunks, and equipment on its side of the POI. (a) In California and Illinois, the Parties agree that this section is satisfied if XO (at its sole option) establishes a POI either: (i) at each access or local tandem in which tandem serving area XO has established a working telephone number local to a rate center in that tandem serving area, and each end office where XO maintains a physical collocation arrangement (but only for those trunk groups associated with that end office); or (ii) within 15.75 miles of the Vertical and Horizontal coordinate of each rate center where XO has established a working telephone number local to that rate center. (b) In Connecticut, Indiana, Michigan, Nevada, Ohio, and Wisconsin, the Parties agree that this section is satisfied if, XO (at its sole option), establishes a POI either: (i) at each access or local tandem in which tandem serving area XO has established a working telephone number local to a rate center in that tandem serving area, and each end office where XO maintains a physical collocation arrangement (but only for those trunk groups associated with that end office); or (ii) within each mandatory local calling area where XO has established a working telephone number local to a rate center in that calling area. (c) The Parties agree that the waivers contained in Section 2.2 with respect to changes in law do not apply to state commission-required changes in the geographic scope or definition of local calling areas. Where the local calling scope has changed, either party may exercise the right to renegotiate the number and location of POIs required under this Further Amendment. This provision shall not be interpreted to affect how the Parties agree to exchange, and compensate one another for, Virtual Foreign Exchange traffic (as defined herein) pursuant to Sections 4, 5, and 6 during the term of this Further Amendment. (d) XO may, at its sole option, establish a POI by obtaining dedicated Special Access services or facilities from SBC ILECs (without the need for XO equipment, facilities, or collocation at the SBC ILECs’ offices), or services or facilities from a third party, by establishing collocation, by establishing a fiber mee...
AutoNDA by SimpleDocs

Related to Network Architecture Requirements

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

  • 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.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Network Upgrades The Transmission Owner shall design, procure, construct, install, and own the Network Upgrades described in Attachment 6 of this Agreement. If the Transmission Owner and the Interconnection Customer agree, the Interconnection Customer may construct Network Upgrades that are located on land owned by the Interconnection Customer. Unless the Transmission Owner elects to pay for Network Upgrades, the actual cost of the Network Upgrades, including overheads, shall be borne initially by the Interconnection Customer.

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