CONTRACT REGISTER Sample Clauses

CONTRACT REGISTER. 10.1 The Head of the Joint Procurement Service shall maintain a Register of all such Contracts awarded following Process 4 and 5 (and those under process 3 that have been communicated to the JPS), specifying the name of the Contractor, the goods works services to be supplied, the length of the Contract, its expiry date, value and named contract manager.
AutoNDA by SimpleDocs
CONTRACT REGISTER. Parties hereby acknowledge and agree that Institution shall be obliged to publish this Amendment 2 in accordance with Act No. 340/2015 Coll., On Contract Register.
CONTRACT REGISTER. 11.1 The ACO (Surrey) and Director of Finance (Sussex) shall maintain a Register of all such Contracts awarded following Process 4 and 5 specifying the name of the Contractor, the goods works services to be supplied, the length of the Contract, its expiry date and the value
CONTRACT REGISTER. All approved contracts are registered in the Contract Management System/Tool to enable easy retrieval and identification of all contractual arrangements. Contracts that are partially executed, signed by one party, may be registered into the Contract Management System prior to forwarding to other parties for signature. The Contract Management unit/function should ensure that all signatures are obtained and contracts are updated in the system. Contract registers should be used to monitor contract end dates in order to notify the end user to commence with the procurement strategy on time, at least 6 or 12 months prior to the expiry of the contract. Effective contract register should have the following characteristics: • Contract number, name of contractor, description, award date, type of contract, amount, contract period, business unit, project manager, contact details, expenditure, commitment; • This will simplify the reconciliation or cross-check between the register and the Municipality's financial management information system; • Expenditure against the contract and value of commitment. Contract register report will be established detailing status of contracts and the reports to be provided by the 6th of every month to the Head of SCM and CFO on the following: • Valid contracts in place; • Contracts due to expire in six or twelve months; • Contracts extended; • All expired contracts; • Contract variation; • Cancelled contracts; • Contracts captured on the system; (where applicable) • Value of commitments; • Value of accruals. The Accounting Officer of a Municipality or Municipal Entity must regularly report to the council of the Municipality or the Board of Directors of the entity, as may be appropriate, on the management of the contract or agreement and the performance of the contractor.
CONTRACT REGISTER. 11.1 The H e a d o f P r o c u r e m e n t shall maintain a Register of all such Contracts awarded following Process 4 and 5 specifying the name of the Contractor, the goods works services to be supplied, the length of the Contract, its expiry date, value and named contract manager.
CONTRACT REGISTER. All approved contracts are registered in the Contract Management System to enable easy retrieval and identification of all contractual arrangements. Contracts that are partially executed, signed by one party, may be registered into the Contract Management System prior to forwarding to other parties for signature. The Contract Management unit function should ensure that all signatures are obtained, and contracts are updated in the system. Contract registers should be used to monitor contract end dates in order to notify the end user to commence with the procurement strategy timeously, at least 6 months prior to the expiry of the contract. An effective contract register should have the following characteristics: • Contract number, name of contractor, description, award date, type of contract, amount, contract period, department, project manager, contact details, expenditure, commitment. • This will simplify the reconciliation or cross-check between the register and the municipality's financial management information system. • Expenditure against the contract and value of commitment. Contract register report will be established detailing status of contracts and the reports to be provided by the 5th working day of every month to the Head of SCM on the following: • Valid contracts in place. • Contracts due to expire in six to twelve months. • Contracts extended. • All expired contracts. • Contract variations. • Cancelled contracts. • Contracts captured on the system; (where applicable) • Value of commitments. • Value of accruals.
CONTRACT REGISTER. Xxxxxx Biomet agrees with publication of this Agreement in Contract Register according to Act No. 340/2015 Coll. on Agreements Register as amended in its entirety, including all its amendments.
AutoNDA by SimpleDocs
CONTRACT REGISTER. This contract is to be published in the contract register as required by the Contract Register Act No. 340/2015 Coll. The parties confirm that this publication is not deemed to violate the Confidential Information clause above and that no part of the contract has been excluded from the public record. The parties agree that the contract will be published by Xxxxxxx University, Faculty of Mathematics and Physics. The contract shall come into effect only if published in the contract register. This Agreement is the entire agreement between the parties related to this subject matter and no alteration or variation of the terms of this Agreement shall be valid unless made in writing and signed by the parties hereto. This Agreement supersedes any prior agreements or understandings between the parties hereto. The Effective date of this Agreement shall be: September 28, 2017 EVENT MANAGEMENT ORACLE CZECH S.R.O. Signature Signature Name Name
CONTRACT REGISTER. This Agreement comes into valid existence as of the day of its conclusion. The day of its conclusion is the date specified next to the Parties' signatures. If there are several dates given next to the Parties' signatures, then the latest date is the day of conclusion. This Agreement takes effect as of the day on which it has been published in the Czech register of contracts as envisioned by Act No. 340/2015 Coll., on the contract register. The Parties agree that information (such as personal data, business secrets), unless properly highlighted beforehand (in yellow) as per the Parties' prior understanding on redactions, may be published in the contract register in accordance with Act No. 340/2015 Coll., on the contract register. All such information as the Parties agreed to remove from the duty of publication in the contract register kept by the Czech Ministry of Interior shall be rendered illegible before the publication of the Agreement in the contract register as such. The Parties have agreed that it is the Collaborator's responsibility to see to it that the Agreement is published in the contract register in accordance with Act No. 340/2015 Coll. Performance of the subject matter of this Agreement prior to the effective date of this Agreement will be deemed to be performance under this Agreement when rights and obligations arising therefrom are governed by this Agreement Accepted and agreed to as of the Effective Date by the authorized representative of each party: In České Budějovice on ……………………………….. In České Budějovice on ……………………………….. i2L Research Limited Biologické centrum AV ČR, v. v. i. (Biology Centre CAS) Institute of Parasitology Name: RNDr. Xxxxx Xxxxxx, Ph.D. Name: prof. RNDr. Xxxxxx Xxxxx, CSc. SOW NO. 1; Effective Date: [MM/DD/YYYY] The purpose of this SOW is to describe the Services that BC will provide to i2L under the terms and conditions of the Services Agreement entered into between the parties on [MM/DD/YYYY](the “Agreement”). Additional terms and conditions may be set forth in this SOW. To the extent the terms and conditions of this SOW are inconsistent with those of the Agreement, the terms of this SOW will control with respect to the Services described herein. Capitalized terms used herein shall have the same meaning as those used in the Agreement. This SOW is an attachment to, and is incorporated by this reference into the Agreement as if fully set forth therein and made a part thereof. This SOW, together with the Agreement, rep...
CONTRACT REGISTER. The Parties have expressly agreed that this Agreement shall take effect only after publication of the Agreement pursuant to Act No. 340/2015 Coll., on Contract Register, as amended, unless a later date is specified (suspensive condition of effect by law). Publication shall be arranged by the Client. The Parties agree to this publication; for the purposes of publication, they do not consider anything in the Agreement or in the metadata relating to the Agreement to be excluded from publication. Should the Agreement be performed before its effective date, such performance shall be considered as an advance for the purposes of the Agreement. Company: Autonomous Manufacturing Ltd Client: CZECH TECHNICAL UNIVERSITY IN PRAGUE, Czech Institute of Informatics, Robotics and Cybernetics Signed Date Signed Date Print name Title Print name Title Billing Details: SCHEDULE I Name: CZECH TECHNICAL UNIVERSITY IN PRAGUE, Czech Institute of Informatics, Robotics and Cybernetics Address: Jugoslávských partyzánů 0000/0 Xxxxxx 0, 000 00, Xxxxxxx Email Address: Phone: VAT Number: CZ68407700 Co Registration Nr: 68407700 Each invoice must contain the designation of the project under which this agreement is paid, namely: “RICAIP – Research and Innovation Centre on Advanced Industrial Production Reg. No.: CZ.02.1.01/0.0/0.0/17_043/0010085” Part A: Pricing Tier - Modules Instant Quotation Module - Total of 9.600€ for 2 years (Payable in advance) Production Module - Total of 9.600€ for 2 years (Payable in advance) NetFabb/Magics Integration - For free Fee-Paket S with 800€ credit for produced files as described in Part B - Total 800€ for 2 years (Payable in advance) Inclusive of: Standard CAD files (IGES, OBJ, STP, STL) Locations: 1 Support licence (8 online hours) All updates for the purchased modules Contract start date: 31.01.2022 First Invoice Date - 31.01.2022 Excluded: Internal Quotation & Ticketing System, Logistic Module, E-catalogue, Integrations, Machine Integration, Full portfolio of CAD files Part B: Client Fees and Costs The fees (Fees) payable are determined by the Pricing Tier selected and comprise a mix of periodic fees: annual (“Annual Fees”), and usage fees for uploading of files or for staging instances (“Usage Fees”) as well as per transaction Fees calculated by reference to Commercial Orders (“Variable Fees”). We assume the number of items produced per part will not exceed an average of 2. Your flat variable fee per item = €0.047 per item Your annual estimated numb...
Time is Money Join Law Insider Premium to draft better contracts faster.