Rejection of Combined Network Alternative Train Slot Sample Clauses

Rejection of Combined Network Alternative Train Slot. If the Train Operator reasonably rejects under paragraph 5.3(b) the Combined Network Alternative Train Slot nominated by Network Rail, it may in its notice of rejection propose a different Combined Network Alternative Train Slot, which Network Rail shall treat as a Combined Network Train Operator Variation Request.
AutoNDA by SimpleDocs
Rejection of Combined Network Alternative Train Slot. If the Train Operator reasonably rejects under paragraph 4.2(b) the Combined Network Alternative Train Slot nominated by Network Rail, it may in its notice of rejection propose a different Combined Network Alternative Train Slot, which Network Rail shall treat as a Combined Network Train Operator Variation Request. If a Combined Network Alternative Train Slot is accepted under paragraph 4.2(a) or is accepted as a Combined Network Train Operator Variation under paragraph 4.3, then: Network Rail shall permit the Train Operator to make the relevant movement in accordance with that Combined Network Alternative Train Slot; the Service Characteristics of the Planned Combined Network Service shall be those of the original Combined Network Train Slot; and the performance of the movement shall be measured accordingly.

Related to Rejection of Combined Network Alternative Train Slot

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx 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 Xxxx. 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 Xxxx (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 Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • ODUF Pack Rejection 6.4.1 Image Access will notify BellSouth within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Image Access will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Image Access by BellSouth.

  • Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Qualified Medical Child Support Order A child who would otherwise meet the eligibility requirements and is required to be covered by a Qualified Medical Child Support Order (QMCSO) is considered an eligible dependent.

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • Unbundled Digital Loops 2.3.1 BellSouth will offer Unbundled Digital Loops (UDL). UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service. 2.3.2 BellSouth shall make available the following UDLs, subject to restrictions set forth herein:

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.

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