Controlling data entries Sample Clauses

Controlling data entries. In the case of remote maintenance, each remote session is logged.
AutoNDA by SimpleDocs

Related to Controlling data entries

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • DATA USED FOR CALCULATIONS The calculations for payments under this Agreement shall be initially based upon the valuations that are placed upon all taxable property in the District, including the Applicant’s Qualified Property, by the Appraisal District in its annual certified tax roll submitted to the District for each Tax Year pursuant to TEXAS TAX CODE § 26.01 on or about July 25 of each year of this Agreement. Immediately upon receipt of the valuation information by the District, the District shall submit the valuation information to the Third Party selected and appointed under Section 4.3. The certified tax roll data shall form the basis of the calculation of any and all amounts due under this Agreement. All other data utilized by the Third Party to make the calculations contemplated by this Agreement shall be based upon the best available current estimates. The data utilized by the Third Party shall be adjusted from time to time by the Third Party to reflect actual amounts, subsequent adjustments by the Appraisal District to the District’s certified tax roll or any other changes in student counts, tax collections, or other data.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • FREQUENTLY ASKED QUESTIONS We may provide Frequently Asked Questions (“FAQs”) for reference on xxx.xxxxxxxxxxxxxxxxx.xxx. The FAQs are not a part of any Program agreement, and the Program enrollment application, ACH authorization, and these Terms will control in the event any conflicting information is contained in the FAQs.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

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

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

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Contractor’s Books and Records Contractor shall maintain any and all ledgers, books of account, invoices, vouchers, canceled checks, and other records or documents evidencing or relating to charges for services or expenditures and disbursements charged to the County for a minimum of five (5) years, or for any longer period required by law, from the date of final payment to the Contractor under this Contract. Any records or documents required to be maintained shall be made available for inspection, audit and/or copying at any time during regular business hours, upon oral or written request of the County.

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