Final Databases Sample Clauses

Final Databases. For each spacecraft procured under this contract, the Contractor shall deliver in accordance with Table 2/1 the final version of the databases. All updates including final calibration curve coefficients, database corrections, and final memory maps shall be included. A report shall be provided in electronic format specifying which items have been modified from the previous version of database. Updates after this point shall be limited to emergency fixes and launch base calibrations only.
View Source

Related to Final Databases

  • Data The statistical, industry-related and market-related data included in the Registration Statement and the Prospectus are based on or derived from sources which the Company reasonably and in good faith believes are reliable and accurate, and such data agree with the sources from which they are derived. The Company has obtained the written consent to the use of such data from such sources to the extent necessary.

  • Processing Personal Data This ▇▇▇▇▇ shall be completed by the Controller, who may take account of the view of the Processors, however the final decision as to the content of this Annex shall be with the Buyer at its absolute discretion.

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

  • Personal Data Registry Operator shall (i) notify each ICANN-­‐accredited registrar that is a party to the registry-­‐registrar agreement for the TLD of the purposes for which data about any identified or identifiable natural person (“Personal Data”) submitted to Registry Operator by such registrar is collected and used under this Agreement or otherwise and the intended recipients (or categories of recipients) of such Personal Data, and (ii) require such registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. Registry Operator shall take reasonable steps to protect Personal Data collected from such registrar from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.

  • Personnel Data The School shall maintain accurate and complete personnel and payroll information and shall provide such information to the Commission, in the format and timeframe prescribed by the Commission, as required for the Legislature or any State agency including but not limited to the Department of Budget & Finance, Employees' Retirement System, and the Hawaii Employer-Union Health Benefits Trust Fund. The School shall ensure each employee receiving State benefits qualifies for such benefits.