Service Ordering Sample Clauses
The Service Ordering clause defines the procedures and requirements for requesting and initiating services under the agreement. Typically, it outlines how a customer can place orders, the information that must be provided, and any approval or confirmation steps required before services commence. For example, it may specify that orders must be submitted in writing or through an online portal, and that each order is subject to acceptance by the service provider. This clause ensures a clear and consistent process for both parties, reducing misunderstandings and streamlining the commencement of services.
Service Ordering. BellSouth will make available the Electronic Data Interchange (EDI) interface and the TAG ordering interface for the purpose of exchanging order information, including order status and completion notification, for non- complex and certain complex resale requests and certain network elements. DTM may integrate the EDI interface or the TAG ordering interface with the TAG pre- ordering interface. In addition, BellSouth will provide integrated pre-ordering and ordering capability through the LENS interface for non-complex and certain complex resale service requests and certain network element requests.
Service Ordering. SPRINT initiates orders to establish, add, change or disconnect trunk-side interconnection services by sending an ASR to VERIZON. SPRINT should submit ASRs to VERIZON through on-line applications or electronic files. SPRINT will order services for INP and LNP by sending a LSR to VERIZON. SPRINT should submit LSRs to VERIZON through an electronic interface or via facsimile (fax). The ordering process is described in the GTE Guide. The ASR and/or LSR will be reviewed by VERIZON for validation and correction of errors. Errors will be referred back to SPRINT. SPRINT then will correct any errors that VERIZON has identified and resubmit the request to VERIZON electronically through a supplemental ASR/LSR. In instances where VERIZON initiates a service order to Sprint for interconnection facilities or trunks, until such time as VERIZON is capable of initiating such orders electronically, VERIZON will complete the necessary fields on the ASR and transmit the order to Sprint via FAX. The ASR will be reviewed by Sprint, and any errors will be referred back to VERIZON.
Service Ordering. BellSouth will make available the Electronic Data Interchange (EDI) interface and the TAG ordering interface for the purpose of exchanging order information, including order status and completion notification, for non- complex and certain complex resale requests and certain network elements. Tennessee Telephone Service may integrate the EDI interface or the TAG ordering interface with the TAG pre-ordering interface. In addition, BellSouth will provide integrated pre-ordering and ordering capability through the LENS interface for resale and certain complex resale service requests.
Service Ordering. The Company will submit a Service Order as specified in Schedule 2 of this Agreement to the Sub-Contractor in respect of each request for the supply of the Services. The Order must specify: the person making the order; a description of the Service (including, where relevant, an item number); the Price of the Service; the date for Delivery of the Performance of the Service, with regular reporting obligations; the reference and order number of this Agreement; and any other information relevant for the performance and completion of the Service deemed appropriate by the Company. The Sub-Contractor must perform the Order within the agreed timeframe.
Service Ordering. 17.2.1 Access Provider shall as soon as possible and latest 30 Working Days after receiving the Submitted Order (SO) send an Order Acknowledgement (OA) that Access Provider has received the Order.
17.2.2 An Order shall, to be deemed valid, include all of the information which is needed. Access Provider shall, in the case of each service that may be ordered pursuant to this Agreement, provide a form which will indicate clearly all such needed information.
17.2.3 Where clarification is required for an Order, Access Provider will initiate bilateral discussions and these will take place to correct the Order details before the Order is placed. Access Provider will contact the Access Seeker contact as detailed in the Order.
17.2.4 Access Provider shall at the latest within thirty (30) Working Days after receiving the Order inform Access Seeker about the Delivery Due Date (DDD) as part of the OA.
17.2.5 Access Seeker accepts the DDD by signing it and sending it to the Access Provider designated contact person and thereby the Acceptance of Order (AO) document is considered to be a binding agreement between the parties. If Access Seeker does not confirm the acceptance of the DDD within thirty (30s) Working Days, the DDD shall be deemed as declined and implementation of the order will not start.
17.2.6 The Parties may jointly agree in writing to handle changes and cancellations of orders as is suitable on a case by case basis involving both Parties best efforts to solve the mutual problems that changes and cancellations incur. If the Parties cannot find a mutual solution and if the Parties have not agreed differently, a change of an order shall be deemed to be an order cancellation followed by a new order.
17.2.7 Cancellation of orders prior to an agreed delivery date is subject to charges. Cancellation of Orders regarding which a delivery date has not been met shall not be subject to any cancellation fees or charges. If the Parties have not agreed otherwise or cancellation fees are specified in a Sub-Annex, the cancellation fee shall be 12.5% of the value of the order. The value of the order is calculated as the sum of the first six months payment(s).
17.2.8 The Parties shall adhere to the following KPIs with regards to Service Ordering: Number of orders completed within a specific time period: Over 75% (seventy-five per cent) that are completed within 5 (five) working days of receipt; and Percentage of orders rejected within a specific time period, subject to ...
Service Ordering. Customer shall offer to purchase Service(s) by executing completed Service Order(s). PCOM shall be deemed to have accepted such offer upon PCOM's execution thereof.
Service Ordering. Gulf Coast initiates orders to establish, add, change or disconnect trunk-side interconnection services by sending an ASR to GTE. Gulf Coast should submit ASRs to GTE through on-line applications or electronic files. Gulf Coast will order services for INP and LNP by sending a LSR to GTE. Gulf Coast should submit LSRs to GTE through an electronic interface or via facsimile (fax). The ordering process is described in the GTE Guide. The ASR and/or LSR will be reviewed by GTE for validation and correction of errors. Errors will be referred back to Gulf Coast. Gulf Coast then will correct any errors that GTE has identified and resubmit the request to GTE electronically through a supplemental ASR/LSR.
Service Ordering. The service ordering process for Alaska services defined in this SOW will be consistent with the service ordering process for Networx services offered in the lower 48 states.
Service Ordering. For enquires and ordering resources in Leonhard Med, please contact the service desk of ▇▇▇▇▇▇▇▇ ▇▇▇ (see section 8.8). For standard service configurations, the service provisioning usually takes two weeks from the date of a valid service request (i.e., complete service request information is provided by the customer). Please refer to sections 7.1 and 7.2 for details about the different service configurations.
Service Ordering. 1027 Section G.2 describes the MAA service ordering requirements and requirements to 1028 interface to the Government’s ordering and billing system. The service ordering process 1029 incorporates the following functions:
(a) Initiate service or features
(b) Disconnect service or features
(c) Add, change, or move service or features 1033 (d) Modify an existing service order 1034 The contractor shall provide the capability for GSA to provide its customer organizations 1035 two service ordering methods: