Design Submittals/Deliverables Sample Clauses

Design Submittals/Deliverables. It is the expectation of MDOT the Section Work will progress in a cooperative and collaborative manner such that all design will be shared and reviewed on a continual basis. Additionally, it is the desire of MDOT to have the Section Developer xxxxxx open communications and all Parties continually work together to meet the P3 Program goals and encourage and empower staff at all levels to continually seek opportunities to improve efficiency, while meeting the requirements of the Agreement. All Deliverables for Section Work are to be submitted for review by the IQF and made available to MDOT prior to official submission, unless otherwise specified. Any Deliverable required for submission to MDOT for review or subject to review and acceptance by MDOT shall be reviewed by the IQF to verify the Deliverable meets the requirements of the Section P3 Agreement prior to the official submission to MDOT for MDOT to begin their review. With the official submission, include written confirmation of the review by the IQF including. Documentation of the IQF’s review, review findings, and the resolution of the findings shall be included in the Section Developer’s Quality Management System recordkeeping. All Deliverables are to be accurate, complete and in a form and level of detail satisfying the Section P3 Agreement. In addition to the electronic files required by the Technical Provisions, provide any documents in an acceptable or native format when requested by MDOT.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Design Submittals/Deliverables

  • Contract Deliverables The Contractor shall provide information technology staff augmentation services, including comprehensive management of staff, as set forth in this Contract. The term “staff” refers to the temporary staff provided by the Contractor to render information technology services identified by Customers, but that staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks. Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. The Department’s intent is for Contractor’s information technology staff to provide services closely related to those described in the Job Family Descriptions document. Detailed scopes of work, specific requirements of the work to be performed, and any requirements of staff shall be provided by the Customer in a Request for Quote. The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified information technology staff to perform the services requested by the Customer. The Contractor shall provide Customers with staff who must have sufficient skill and experience to perform the services assigned to them. All of the information technology staff augmentation services to be furnished by the Contractor under the Contract shall meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. The Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of staff. The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s information technology staff. The Contractor shall maintain during the term of the Contract all licenses, permits, qualifications, insurance and approvals of whatever nature that are legally required to perform the information technology staff augmentation services.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • CONTRACTOR TO PACKAGE DELIVERABLES The Contractor will package deliverables in accordance with good commercial practice and shall include a packing list showing the description of each item, the quantity and unit price unless otherwise provided in the Specifications or Supplemental Terms and Conditions, each shipping container shall be clearly and permanently marked as follows: (a) The Contractor's name and address, (b) the City’s name, address and purchase order or purchase release number and the price agreement number if applicable, (c) Container number and total number of containers, e.g. box 1 of 4 boxes, and (d) the number of the container bearing the packing list. The Contractor shall bear cost of packaging. Deliverables shall be suitably packed to secure lowest transportation costs and to conform to all the requirements of common carriers and any applicable specification. The City's count or weight shall be final and conclusive on shipments not accompanied by packing lists.

  • Review of Submittals A/E and ODR review is only for conformance with the design concept and the information provided in the Contract Documents. Responses to submittals will be in writing. The approval of a separate item does not indicate approval of an assembly in which the item functions. The approval of a submittal does not relieve the Contractor of responsibility for any deviation from the requirements of the Contract unless the Contractor informs the A/E and ODR of such deviation in a clear, conspicuous, and written manner on the submittal transmittal and at the time of submission, and obtains the A/E’s and Owner’s written specific approval of the particular deviation.

  • Scope of Work and Deliverables 9.1 Background and Scope

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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