INITIAL NETWORK IMPLEMENTATION SCHEDULE FOR PENNSYLVANIA Sample Clauses

INITIAL NETWORK IMPLEMENTATION SCHEDULE FOR PENNSYLVANIA. In accordance with the provisions of Section 3 of the Agreement, the Parties shall make their best efforts to meet the following initial Milestones no later than the listed Dates. LATA in Pennsylvania Milestone Date LATA 228 LATA Start Date Done SS7 Certification, Collocation, Operator Services/DA Facilities, and NXX(s) Applied For Done Parties Agree on Trunking Arrangements for Traffic Exchange Done Valid Access Service Request(s) (“ASRs”) for Traffic Exchange Trunk Groups and Routing Information Received by BA Done Valid Orders for 911 Facilities Received by BA Done All Trunks (Traffic Exchange, Operator Services/DA, 911) Tested and Turned Up; SS7 Certification Achieved1 9/15/96 Collocation Arrangements Complete for Trunk Interconnection and Access to Network Elements2 11/1/96 Arrangements for Alternate-Billed Calls Agreed Upon 10/1/96 Call-through Testing Completed; “Interconnection Activation Date” 11/15/96 Failure of a Party or the Parties to meet an earlier Milestone Date shall not relieve either Party of the responsibility to make its best efforts to meet subsequent Milestone Date(s) in the LATA, unless, and only to the extent that, the subsequent Milestone Date(s) depend on the timely completion of such earlier Milestone Date. For purposes of Section 3, (i) business Telephone Exchange Service shall be considered “fully operational” in a LATA in Pennsylvania when ETC has an effective Tariff for business Telephone Exchange Service in Pennsylvania and has a significant number of Telephone Exchange Service Customer lines in service for business Telephone Exchange Service Customers in that LATA in Pennsylvania that are not affiliates or employees of either BA or ETC, and (ii) residential Telephone Exchange Service shall be considered “fully operational” in a LATA in Pennsylvania when ETC has an effective Tariff for residential Telephone Exchange Service in Pennsylvania and has a significant number of Telephone Exchange Service Customer 1 SS7 certification scheduling depends on actual schedule availability at time of request.
AutoNDA by SimpleDocs

Related to INITIAL NETWORK IMPLEMENTATION SCHEDULE FOR PENNSYLVANIA

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.

  • Project Implementation 2. The Borrower shall:

  • Implementation Services The Company and the Client have developed a plan for implementing the services to be provided hereunder, including with respect to the transition of responsibility for such services from the Client and its current administrator to the Company, which plan attached hereto as Schedule I (the “Implementation Plan”). The Company shall perform the services required to complete the Implementation Plan, as set forth therein (the “Implementation Services”). The Company and the Client shall comply with any applicable requirements agreed in the Implementation Plan.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

Time is Money Join Law Insider Premium to draft better contracts faster.