Database Updates and Quality Process a Sample Clauses

Database Updates and Quality Process a. The Contractor must update and maintain all Databases in accordance with the timeframe(s) set forth in the Annual Business Plan following receipt of all files from Department data contractors, unless the Parties agree to a different schedule in writing by way of Change Requests. b. The Contractor must provide a reconciliation report allowing at least forty-eight (48) hours lead time before approval is required. c. The Solution’s annual variance related to financials from the Department’s Data Source systems must not exceed 1%. a. $2,500 per Calendar Day the Database is not updated. b. $100 per hour under the forty-eight (48) hour lead time. c. $1000 per one-hundredth percent over the 1% allowed variance. Liquidated damages will be assessed annually for subsection c.
Sample 1
AutoNDA by SimpleDocs

Related to Database Updates and Quality Process a

  • STANDARDS AND QUALITY The Supplier shall at all times during the Contract Period ensure that the Services are delivered in accordance with: the Digital Service Design Manual (and the Supplier shall comply with the processes and procedures set out therein); the Standards; the KPIs; the Methodology; the applicable SOW; and all other applicable provisions of this Contract.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • NMHS Governance, Safety and Quality Requirements 3.1 Participates in the maintenance of a safe work environment.

  • EMHS Governance, Safety and Quality Requirements 4.1 Participates in the maintenance of a safe work environment.

  • SMHS Governance, Safety and Quality Requirements 4.1 Participates in the maintenance of a safe work environment.

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

  • Technical Accuracy Owner shall not be responsible for discovering deficiencies in the technical accuracy of Engineer’s services. Engineer shall correct deficiencies in technical accuracy without additional compensation, unless such corrective action is directly attributable to deficiencies in Owner-furnished information.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

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