Metering Database Sample Clauses

The Metering Database clause establishes the requirements and procedures for maintaining a centralized record of metering data related to a project or service. Typically, this clause outlines who is responsible for collecting, updating, and granting access to the database, as well as the types of data to be included, such as energy usage or consumption figures. By clearly defining these responsibilities and data management protocols, the clause ensures accurate tracking and transparency of metering information, which is essential for billing, compliance, and performance monitoring.
Metering Database. (a) This clause 4.7 applies only if, and to the extent that, ADEWAP is required by Applicable Law to comply with the Metering Code. (b) In addition to maintaining and updating the Connection Point Details in accordance with clause 4.6, ADEWAP will maintain and update the Metering Database if, and to the extent, required by, and in accordance with, the Metering Code. (c) ADEWAP will provide User with access to the information in the Metering Database from time to time if, and to the extent, required by the Metering Code or otherwise by any Applicable Law.
View SourceView Similar (5)

Related to Metering Database

  • Metering Data At Developer’s expense, the metered data shall be telemetered to one or more locations designated by Connecting Transmission Owner, Developer and NYISO. Such telemetered data shall be used, under normal operating conditions, as the official measurement of the amount of energy delivered from the Large Generating Facility to the Point of Interconnection.

  • Metering The Interconnection Customer shall be responsible for the Connecting Transmission Owner’s reasonable and necessary cost for the purchase, installation, operation, maintenance, testing, repair, and replacement of metering and data acquisition equipment specified in Attachments 2 and 3 of this Agreement. The Interconnection Customer’s metering (and data acquisition, as required) equipment shall conform to applicable industry rules and Operating Requirements.

  • 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.

  • Calibration The comparison of a measurement system or device of unverified accuracy with a measurement system of known and greater accuracy to detect deviation of the unverified measurement system from required performance specifications (of the unverified measurement system or device) and to quantify all measured values to applicable units of the international system of units.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.