Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.
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.
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 Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,
Interconnection Point The Service Provider is responsible for connecting to the LFC Network at the Interconnection Point. The LFC may only change an Interconnection Point if a change is necessary to protect the security or integrity of that Interconnection Point in order to maintain the continuity of supply of the Wholesale Services. In the event of any such change:
Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None
Indirect Network Connection 64.8.1 For purposes of this Agreement, Indirect Traffic means traffic which is originated by one Party and terminated to the other Party in which a third party ILEC’s Tandem switch both provides the intermediary Transit Service and serves CenturyLink’s NXXs. Indirect Network Connection for Indirect Traffic is intended only for de minimis traffic associated with CLEC “start- up” market entry into a CenturyLink local exchange. Therefore Indirect Network Connection will be allowed only on routes between CenturyLink End Offices and a CLEC switch in instances where, and only so long as, none of the POI thresholds set forth in Section 64.4.2 have been reached.
Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.
By Interconnection Customer Interconnection Customer may unilaterally terminate the Interconnection Service Agreement pursuant to Applicable Laws and Regulations upon providing Transmission Provider and the Interconnected Transmission Owner sixty (60) days prior written notice thereof, provided that Interconnection Customer is not then in Default under the Interconnection Service Agreement.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
