Basis for Technical Tender Sample Clauses

Basis for Technical Tender. 5.1.2.1. Technical proposal: service implementation and quality management proposal 1.2.1 - Technical specifications. In particular the proposal for service implementation and quality management shall include: • Description of the proposed project management methodology and project management tools (max. 2100 words); • Description of the proposed tools and processes for managing the system lifecycle (max. 6000 words): o Management and storage of requirements, specifications and project documentation; o Management and storage of change requests (i.e. change management); o The software build process and management and storage of source code, configurations and any related software assets; o The software test process and management and storage of test plans, test cases and test scripts; o The software release process and management of software assets, including their transfer to ECHA; o Issue/defect tracking and management; o Knowledge base • Description of development and test environments at Contractor’s site (max. 600 words). • Proposal for the organisation and management of the application support and maintenance, including (max. 2000 words): o A proposal for the processes that are needed (relevant) for the application support and maintenance and a description of each process. o Clear description of what are the responsibilities between ECHA and the contractor (e.g. RACI-matrix) in the application support and maintenance. o The tools supporting and used in the context of each process. • Quality assurance plan, including security assurance20 (max. 1500 words). • Proposals exceeding or complementary to the specifications and offered at no additional cost for the Agency (e.g. extension of the warranty period, remote monitoring services and/or administering of ECHA Documentum environments (max. 1500 words). • Proposed templates to be used during the execution of the framework contract for the document deliverables, such as o Business requirements document o Solution specification document o System architecture document o Project management templates
Sample 1
AutoNDA by SimpleDocs
Basis for Technical Tender. 40 5.1.2.1. Technical proposal: service implementation and quality management proposal 40 5.1.2.2. Technical proposal: proposal for the project plan for the ECHA Electronic Records Management System implementation scenario 41 5.2. Contractual Documentation 43 5.3. Administrative documentation 44
Sample 1
Basis for Technical Tender. 5.1.2.1. Technical proposal: service implementation and quality management proposal 1.1 - Technical specifications. In particular the proposal for Service implementation and quality management shall include: • Description of the proposed project management methodology and project management tools (max. 2100 words); • Description of the proposed tools and processes for managing the system lifecycle (max. 6000 words): o Management and storage of requirements, specifications and project documentation; o Management and storage of change requests (i.e. change management); o The software build process and management and storage of source code, configurations and any related software assets; o The software test process and management and storage of test plans, test cases and test scripts; o The software release process and management of software assets, including their transfer to ECHA; o Issue/defect tracking and management; o Knowledge base • Description of development and test environments at Contractor’s site (max. 600 words). • Proposal for the organisation and management of the application support and maintenance, including the Contractor ticketing system (max. 1500 words). • Quality assurance plan, including security assurance (max. 1500 words). • Proposals exceeding or complementary to the specifications (e.g. extension of the warranty period, remote monitoring services and/or administering of ECHA Documentum environments (max. 1500 words). • Proposed templates to be used during the execution of the framework contract for the document deliverables, such as o Business requirements document o Solution specification document o System architecture document o Project management templates
Sample 1

Related to Basis for Technical Tender

  • Period of Validity of Tenders 17.1 Tenders shall remain valid for the Tender Validity period specified in the TDS. The Tender Validity period starts from the date fixed for the Tender submission deadline (as prescribed by the Procuring Entity in accordance with ITT 21.1). A Tender valid for a shorter period shall be rejected by the Procuring Entity as non-responsive. 17.2 In exceptional circumstances, prior to the expiration of the Tender validity period, the Procuring Entity may request Tenderers to extend the period of validity of their Tenders. The request and the responses shall be made in writing. If a Tender Security is requested in accordance with ITT 18, it shall also be extended for a corresponding period. A Tenderer may refuse the request without forfeiting its Tender Security. A Tenderer granting the request shall not be required or permitted to modify its Tender, except as provided in ITT 17.3. 17.3 If the award is delayed by a period exceeding the number of days to be specified in the TDS days beyond the expiry of the initial tender validity period, the Contract price shall be determined as follows: a) in the case of fixed price contracts, the Contract price shall be the tender price adjusted by the factor specified in the TDS; b) in the case of adjustable price contracts, no adjustment shall be made; or in any case, tender evaluation shall be based on the tender price without taking into consideration the applicable correction from those indicated above.

  • Legal Tender of United States All payments hereunder shall be made in coin or currency which at the time of payment is legal tender in the United States of America for public and private debts.

  • Legal Terms References to any English legal term shall, in respect of any jurisdiction other than England, be construed as references to the term or concept which most nearly corresponds to it in that jurisdiction.

  • Contractor Personnel – Reference Checks The Contractor warrants that all persons employed to provide service under this Contract have satisfactory past work records indicating their ability to adequately perform the work under this Contract. Contractor’s employees assigned to this project must meet character standards as demonstrated by background investigation and reference checks, coordinated by the agency/department issuing this Contract.

  • Language of Tender 9.1 The Tender, as well as all correspondence and documents relating to the Tender exchanged by the Tenderer and the Procuring Entity, shall be written in English Language. Supporting documents and printed literature that are part of the Tender may be in another language provided they are accompanied by an accurate translation of the relevant passages into the English Language, in which case, for purposes of interpretation of the Tender, such translation shall govern.

  • PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:

  • Scope of Tender 1.1 The Procuring Entity as defined in the TDS invites tenders for supply of goods and, if applicable, any Related Services incidental thereto, as specified in Section V, Supply Requirements. The name, identification, and number of lots (contracts) of this Tender Document are specified in the TDS. 1.2 Throughout this tendering document: a) the term “in writing” means communicated in written form (e.g. by mail, e-mail, fax, including if specified in the TDS, distributed or received through the electronic-procurement system used by the Procuring Entity) with proof of receipt; b) if the context so requires, “singular” means “plural” and vice versa;

  • U.S. Government Rights The Cloud Service is a “commercial item” as that term is defined at FAR 2.101. If Customer or User is a US Federal Government (“Government”) Executive Agency (as defined in FAR 2.101), Oracle provides the Cloud Service, including any related software, technology, technical data, and/or professional services in accordance with the following: (a) if acquired by or on behalf of any Executive Agency (other than an agency within the Department of Defense (“DoD”), the Government acquires, in accordance with FAR 12.211 (Technical Data) and FAR 12.212 (Computer Software), only those rights in technical data and software customarily provided to the public as defined in this Agreement; or (b) if acquired by or on behalf of any Executive Agency within the DoD, the Government acquires, in accordance with DFARS 227.7202-3 (Rights in commercial computer software or commercial computer software documentation), only those rights in technical data and software customarily provided in this Agreement. In addition, DFARS 252.227-7015 (Technical Data – Commercial Items) applies to technical data acquired by DoD agencies. Any Federal Legislative Agency or Federal Judicial Agency shall obtain only those rights in technical data and software customarily provided to the public as set forth in this Agreement. If any Federal Executive Agency, Federal Legislative Agency, or Federal Judicial Agency has a need for rights not conveyed under the terms described in this Section, it must negotiate with Oracle to determine if there are acceptable terms for transferring such rights, and a mutually acceptable written addendum specifically conveying such rights must be included in any applicable contract or agreement to be effective. This U.S. Government Rights Section is in lieu of, and supersedes, any other FAR, DFARS, or other clause, provision, or supplemental regulation that addresses Government rights in computer software or technical data under this Agreement.

  • U.S. Government End Users The Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire the Software with only those rights set forth herein.

  • CFR PART 200 AND FEDERAL CONTRACT PROVISIONS EXPLANATION TIPS and TIPS Members will sometimes seek to make purchases with federal funds. In accordance with 2 C.F.R. Part 200 of the Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards (sometimes referred to as “XXXXX”),Vendor's response to the following questions labeled "2 CFR Part 200 or Federal Provision" will indicate Vendor's willingness and ability to comply with certain requirements which may be applicable to TIPS purchases paid for with federal funds, if accepted by Vendor. Your responses to the following questions labeled "2 CFR Part 200 or Federal Provision" will dictate whether TIPS can list this awarded contract as viable to be considered for a federal fund purchase. Failure to certify all requirements labeled "2 CFR Part 200 or Federal Provision" will mean that your contract is listed as not viable for the receipt of federal funds. However, it will not prevent award. If you do enter into a TIPS Sale when you are accepting federal funds, the contract between you and the TIPS Member will likely require these same certifications.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!