Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:
Contract Capacity The electric power producing capability of the Generating Facility which is committed to Edison.
Capacity Interconnection Rights Pursuant to and subject to the applicable terms of the Tariff, the Interconnection Customer shall have Capacity Interconnection Rights at the Point(s) of Interconnection specified in this Interconnection Service Agreement in the amount of 33.6
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers.
9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA.
9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Generating Facility The Interconnection Customer’s device for the production of electricity identified in the Interconnection Request, but shall not include the Interconnection Customer’s Interconnection Facilities.
Initiating Interconnection 4.1 If ENT determines to offer Telephone Exchange Services and to interconnect with Verizon in any LATA in which Verizon also offers Telephone Exchange Services and in which the Parties are not already interconnected pursuant to this Agreement, ENT shall provide written notice to Verizon of the need to establish Interconnection in such LATA pursuant to this Agreement.
4.2 The notice provided in Section 4.1 of this Attachment shall include (a) the initial Routing Point(s); (b) the applicable technically feasible Point(s) of Interconnection on Verizon’s network to be established in the relevant LATA in accordance with this Agreement; (c) ENT’s intended Interconnection activation date; (d) a forecast of ENT’s trunking requirements conforming to Section 14.2 of this Attachment; and (e) such other information as Verizon shall reasonably request in order to facilitate Interconnection.
4.3 The interconnection activation date in the new LATA shall be mutually agreed to by the Parties after receipt by Verizon of all necessary information as indicated above. Within ten (10) Business Days of Verizon’s receipt of ENT’s notice provided for in Section 4.1of this Attachment, Verizon and ENT shall confirm the technically feasible Point of Interconnection on Verizon’s network in the new LATA and the mutually agreed upon Interconnection activation date for the new LATA.
Interconnection Facilities 4.1.1 The Interconnection Customer shall pay for the cost of the Interconnection Facilities itemized in Attachment 2 of this Agreement. The NYISO, in consultation with the Connecting Transmission Owner, shall provide a best estimate cost, including overheads, for the purchase and construction of its Interconnection Facilities and provide a detailed itemization of such costs. Costs associated with Interconnection Facilities may be shared with other entities that may benefit from such facilities by agreement of the Interconnection Customer, such other entities, the NYISO, and the Connecting Transmission Owner.
4.1.2 The Interconnection Customer shall be responsible for its share of all reasonable expenses, including overheads, associated with (1) owning, operating, maintaining, repairing, and replacing its own Interconnection Facilities, and
Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.
Interconnection Customer’s Interconnection Facilities The Interconnection Customer shall design, procure, construct, install, own and/or control the Interconnection Customer’s Interconnection Facilities described in Appendix A at its sole expense.
Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks.
2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI.
2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks.
2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.
2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5).
2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275.
2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three
