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:
Metering The Interconnection Customer shall be responsible for the Connecting Transmission Owner’s reasonable and necessary cost for the purchase, installation, operation, maintenance, testing, repair, and replacement of metering and data acquisition equipment specified in Attachments 2 and 3 of this Agreement. The Interconnection Customer’s metering (and data acquisition, as required) equipment shall conform to applicable industry rules and Operating Requirements.
Installation, Maintenance, Testing and Repair Unless otherwise agreed in writing by the Parties, to the extent required by Applicable Law, Interconnection provided by a Party shall be equal in quality to that provided by such Party to itself, any subsidiary, affiliates or third party. If either Party is unable to fulfill its obligations under this Section 14.2, it shall notify the other Party of its inability to do so and will negotiate alternative intervals in good faith. The Parties agree that to the extent required by Applicable Law, the standards to be used by a Party for isolating and clearing any disconnections and/or other outages or troubles shall be at parity with standards used by such Party with respect to itself, any subsidiary, affiliate or third party.
Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.
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.
Data and Information In furtherance of the authority contained in this Article 5, one or more of the Parties are authorized to obtain, compile, maintain, share, and exchange among themselves, or with one or more third parties, information related to any aspect of intermodal transport, equipment use, inland or marine terminals, operations, cargo throughput, transportation or traffic volumes, equipment use, and/or other information pertaining to matters authorized under this Article 5. Such information may include records, statistics, studies, compilations, projections, costs, data, and electronic or paper documents of any kind or nature whether prepared by a Party or the Parties or obtained from outside sources, relating to matters authorized by Article 5.
Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.
One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall:
2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or
2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier.
2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment.
2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.
Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection.
1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.
Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.
