Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.
Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI 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 ECI 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 ECI’s Customers.
9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI 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 ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.
FRAMEWORK AGREEMENT MANAGEMENT The Parties shall manage this Framework Agreement in accordance with Schedule 14 (Framework Management).
Framework Agreement 4.1.2.1 The Parties shall enter into a Framework Agreement within 28 days after the Contractor receives the Letter of Acceptance, unless the Particular Conditions establish otherwise. The Framework Agreement shall be based upon FORM No. 3 – FRAMEWORK AGREEMENT annexed to the Particular Conditions. The costs of stamp duties and similar charges (if any) imposed by law in connection with entry into the Framework Agreement shall be borne by the Procuring Entity.
4.1.2.2 The Framework Agreement establishes the terms and conditions that will govern the contract awarded during the term of the Framework Agreement. The Framework Agreement establishes for the procurement works by package as and when required, over the specified period of time. The Framework Agreement does not commit a Procuring Entity to procure, nor a Firm to supply. The Framework Agreement allows the Procuring Entity to call the Contractor to commence the works on a particular package in a specified location within the duration of the agreement.
4.1.2.3 This Framework Agreement does not guarantee the contractor of being called for a contract to start and no commitment is made with regard to possible number of packages to carry out.
4.1.2.4 This Framework Agreement does exclude the Procuring Entity from the right to procure the same Works from other firms.
4.1.2.5 This Framework Agreement does not stop the Procuring Entity from removing the contractor from the same Agreement.
4.1.2.6 FAs shall be established for a maximum period of three (3) years. The Procuring Entity may with the Consent of the Contractor extend this Agreement if the agreement period is less than three (3) years, if the initial engagement has been satisfactory.
4.1.2.7 Call-off Contracts; for work on a package to start, the Procuring Entity shall issue a notice of acceptance of a particular package requesting the contractor to furnish a Performance Security and to start the works thereafter, and providing the contractor with details of location where the works, are to be carried out. The call-off statement shall specify the objectives, tasks, deliverables, timeframes and price or price mechanism. The price for individual call-off contracts shall be based on the prices detailed in the Framework Agreement.
Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.
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.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning):
1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises.
2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated.
3. If capacity exists, provide "side-door" porting through the switch.
4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch).
2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases.
2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.