Service Order Entry Interface Sample Clauses

The Service Order Entry Interface clause defines the requirements and specifications for the system or platform through which service orders are submitted, tracked, and managed. Typically, this clause outlines the technical standards, accessibility, and data fields required for entering service orders, and may specify integration with existing business systems or third-party platforms. Its core practical function is to ensure a standardized, efficient, and reliable process for initiating and processing service orders, thereby reducing errors and streamlining workflow between parties.
Service Order Entry Interface. 12.9.1.1 The Service Order Entry Interface provides CLEC with unbundled access to SBC MISSOURI’s SMS hat is equivalent to SBC MISSOURI’s own service order entry process. Service Order Entry Interface allows CLEC to electronically transmit properly formatted records from CLEC’s service order process or other data source into the LIDB SMS. 12.9.1.2 CLEC’s access to the Service Order Entry Interface will be through a remote access facility (RAF). The RAF will provide SBC MISSOURI with a security gateway for CLEC access to the Service Order Entry Interface. The RAF will verify the validity of CLEC’s transmissions and limit CLEC’s access to SBC MISSOURI’s Service Order Entry Interface to the LIDB SMS. CLEC’s access to LIDB SMS through the RAF does not provide CLEC with access to any other SMS, interface, database, or operations support system through this Attachment. 12.9.1.3 SBC MISSOURI will provide CLEC with the file transfer protocol specifications CLEC will use to Administer CLEC’s data over the Service Order Entry Interface. CLEC acknowledges that transmission in such specified protocol is necessary for SBC MISSOURI to provide CLEC with Data Base Administration and Storage. 12.9.1.4 CLEC can choose the Service Order Entry Interface as its only interface to the LIDB SMS or CLEC can choose to use this interface in conjunction with the Interactive Interface that SBC MISSOURI provides under this Attachment. If CLEC chooses to use only the Service Order Entry Interface, CLEC will not have access to any data Administration capabilities available to the Interactive Interface (e.g., the ability to view Line Records in the LIDB SMS). 12.9.1.5 CLEC’s access to SBC MISSOURI’s LIDB SMS through the Service Order Entry Interface is only for its subscriber’s Line Records that are not administered through the LSR Process. 12.9.1.6 SBC MISSOURI will provide CLEC with SBC MISSOURI-specific documentation for properly formatting the records CLEC will transmit over the Service Order Entry Interface.
View SourceView Similar (4)
Service Order Entry Interface. 4.4.2.1 The Service Order Entry Interface allows Customer to provide bulk updates from its service order process or other data source (such as back office systems) to the LIDB SMS. Such bulk updates must be formatted as set forth in relevant AT&T-12STATE documentation which AT&T-12STATE will provide to Customer at no additional charge. Customer can combine the use of the Service Order Entry Interface with the Interactive Interface.
View SourceView Similar (2)
Service Order Entry Interface. 4.3.1.1 The Service Order Entry Interface provides switch-based CLECs with unbundled access to SBC-12STATE’s LIDB administrative systems that is equivalent to SBC-12STATE’s own service order entry process. Service Order Entry Interface allows CLEC to electronically transmit properly formatted records from CLEC’s service order process or other data source into the LIDB administrative system. SBC-SWBT also provides the Service Order Entry Interface to requesting CLECs that use SBC-SWBT’s UNE local switch ports. PACIFIC, SBC-AMERITECH, and SNET will also provide requesting CLECs that use those ILEC’s UNE local switch ports within one hundred eighty days (180) upon request unless otherwise offered earlier.
View Source
Service Order Entry Interface. The Service Order Entry Interface provides Pac-West with unbundled access to Pacific B▇▇▇'▇ OSMOP that is equivalent to Pacific B▇▇▇'▇ own service order entry process to OSMOP. Service Order Entry Interface allows Pac-West to electronically transmit properly formatted records from Pac-West's service order process into OSMOP.
View Source
Service Order Entry Interface. (A) The Service Order Entry Interface provides LSP with unbundled access to SWBT's LVAS that is equivalent to SWBT's own service order entry process to LVAS. Service Order Entry Interface allows LSP to electronically transmit properly formatted records from LSP's service order process into LVAS. (B) LSP's access to the Service Order Entry Interface will be through a remote access facility (RAF). The RAF will provide SWBT with a security gateway for LSP access to the Service Order Entry Interface. The RAF will verify the validity of LSP's transmissions and limit LSP's access to SWBT's Service Order Entry Interface to LVAS. LSP does not gain access to any other SMS, interface, database, or operations support system through this Appendix. (C) SWBT will provide LSP with the file transfer protocol specifications LSP will use to administer LSP's data over the Service Order Entry Interface. LSP acknowledges that transmission in such specified protocol is necessary for SWBT to provide LSP with Data Base Administration and Storage. (D) LSP can choose the Service Order Entry Interface as its only interface to LVAS and LIDB or the LSP can choose to use this interface in conjunction with any other interface that SWBT provides under this Appendix except the Manual Interface. (E) SWBT will provide LSP with SWBT-specific documentation for properly formatting the records LSP will transmit over the Service Order Entry Interface. (F) LSP understands that its record access through the Service Order Entry Interface will be limited to its own line/billing records.
View Source

Related to Service Order Entry Interface

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Interconnection Customer Any entity, including the Transmission Owner or any of the affiliates or subsidiaries, that proposes to interconnect its Small Generating Facility with the New York State Transmission System or the Distribution System.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor