Interconnection to Line Information Data Sample Clauses

Interconnection to Line Information Data. Base (LIDB)
AutoNDA by SimpleDocs

Related to Interconnection to Line Information Data

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment.

  • Data Processing System, Program and Information (a) The Investment Company shall not, solely by virtue of this Agreement, obtain any rights, title and interest in and to the computer systems and programs, including all related documentation, employed by FTIS in connection with rendering services hereunder; provided however, that the records prepared, maintained and preserved by FTIS pursuant to this Agreement shall be the property of the Investment Company.

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8, in accordance with, but only to the extent required by, Applicable Law, Verizon grants to CBB a non-exclusive license to use Verizon OSS Information.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Service Information Service Visit Date Mode of service Face-to face, telephone, etc. Responsibility for payment Used to exclude federal govt., WCB, etc. Main and secondary diagnoses ICD10-CA codes Main and other interventions and attributes CCI procedure codes and attributes Type of Anesthetic Identifies the type used for interventions (general, spinal, local, etc.) Provider types NACRS code assigned to provider type (MD, Dentist, RN, etc.) Doctor name and identifier Physician specific information Admit via Ambulance Used if a Client is brought to the service delivery site by ambulance Institution from and institution to Used when a Client is transferred from or to another acute care facility Visit disposition Discharged, admitted, left without being seen, etc. Schedule “D” Appendix 2 Additional Elements Required for Data Management (XXX) Client Identifying Information Province Client‟s Home Province AB, BC, SK, MB, NL, PE, NS, NB, QC, ON, NT, YT, NU, US, OC (Other Country), NR (Unsp. Non-resident) Service Information Facility Code AHS provided code that indicates service being provided. Facility Fee Dollar value of service being provided Alberta Health Physician Fee Billing Code Alberta Health Physician Service Fee code that further defines facility code Regional standard format and submission method remains as is via excel file and email. NOTE: Submission method may be adjusted in accordance with security standards of AHS. Schedule “D” Appendix 3

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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