Deliverable Format Sample Clauses

Deliverable Format. Consultant shall submit deliverables in both electronic and hardcopy format. Deliverables shall be submitted in PDF and native (editable) format, including Word documents, Excel spreadsheets, PowerPoint files, AutoCAD files, etc. The hard copy deliverables shall be printed in professional quality presentation and submitted in 5 (five) copies. District may require original copies of signed documents and/or scanned (Adobe PDF) versions.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Deliverable Format. Alpha shall retain ownership of the Phase 3 Deliverable until such time as designated by Section 5(b), but will provide VDOT with two hard copies of the Deliverable, which shall not be reproduced by VDOT. VDOT shall then have ten (10) calendar days following receipt to review the Deliverable. VDOT shall record all notes and questions on one original hard copy of the Deliverable. A meeting between the Department and Alpha, at an Alpha in-house location, shall be scheduled on the last day of the Department’s review in order to brief the Department on the Phase 3 Deliverable, answer questions and reconcile inconsistencies with the scope and requirements of this Phase 3 Deliverable. Following the review meeting, the Department shall have eleven (11) additional calendar days to review and analyze information obtained at the review meeting. At the end of the 11 day additional review period (21 calendar days total), the Department shall return all documents constituting the Phase 3 Deliverable to Alpha. Within fourteen (14) calendar days of the return of the Deliverable, Alpha will resolve any and all outstanding issues or deficiencies identified by the Department relating to the Limited Feasibility Study and the Report.
Sample 1Sample 2
Deliverable Format. Pioneer shall retain ownership of the Phase 3 Deliverable until such time as designated by Section 5(b), but will provide VDOT with two hard copies of the Deliverable, which shall not be reproduced by VDOT. VDOT shall then have ten (10) calendar days following receipt to review the Deliverable. VDOT shall record all notes and questions on one original hard copy of the Deliverable. A meeting between the Department and Pioneer, at a Pioneer in-house location, shall be scheduled on the last day of the Department’s review in order to brief the Department on the Phase 3 Deliverable, answer questions, and reconcile inconsistencies with the scope and requirements of this Phase 3 Deliverable. Following the review meeting, the Department shall have eleven (11) additional calendar days to review and analyze information obtained at the review meeting. At the end of the 11 day additional review period (21 calendar days total), the Department shall return all documents constituting the Phase 3 Deliverable to Pioneer. Within fourteen (14) calendar days of the return of the Deliverable, Pioneer will resolve any and all outstanding issues and deficiencies identified by the Department relating to the Limited Feasibility Study or the Report.
Sample 1Sample 2
Deliverable Format. The Cooperator’s submittals and compliance with notification requirements must be in writing unless specified otherwise. In writing includes email communication. All documents, maps, and illustrations must be of high quality and easily reproducible on standard or color copiers. All documents will be two sided, single spaced, on 8 ½” by 11” paper in manuscript format, with standard outline spacing. Fold out pages should be avoided. If these are necessary, they will be no larger than 11” x 17” and have the same design as the 8 ½” by 11” graph pages, and they will be approved by the Government before document preparation. Pages intentionally left blank shall be labeled as such. All pages of the documents will be appropriately numbered with filename and date listed in the footer of hard copies, and inserted into a 3 ring binder with a labeled edge. All deliverable documents and maps, charts, etc. shall also be delivered in electronic format, Microsoft Office Word or jpeg formats. If ADOBE ACROBAT is used, files will be scanned per chapter, per figure and per appendix so that files are manageable. Files must be delivered in electronic formats that can be altered or updated by the Government. All chapters shall be saved as separate files on a CD for ease of reproduction. All databases containing raw data and all associated electronic data summary and analytical files shall be formatted in Excel, Word, Dbase IV, or any compatible Microsoft database software and submitted to the TPOC and SPOC (via CD-ROM). Microsoft ACCESS files shall include all queries, reports, tables etc. If required, all original still photographs will be captured at a minimum of 1 million pixels and 24-bit color.
Sample 1
Deliverable Format. The Stormwater Master Plan Update will be both hard copy (8.5” x 11” with other size inclusions as needed) and electronic and will include all deliverables defined in the Contract Task Orders. Deliverables will be submitted to the City at the completion of each Task Order. Each Task Order will be considered a chapter in the hard copy Stormwater Master Plan and each Deliverable will be entered as a section within the chapter. At the City’s discretion, the electronic deliverable will either be submitted to the City via internet or on flash drive(s). Acceptable formats for digital submittals shall be Microsoft Office Suite (Word, Excel, and Access), Autodesk, ESRI and Contractor’s recommended and City approved stormwater modeling software.
Sample 1
Deliverable Format. A. All deliverables shall be provided in a format compatible with the DCSS Project Office standard applications (currently, Microsoft Office 2013). In all cases, the Contractor shall verify application compatibility with the State Contract Manager prior to creation or delivery of any electronic documentation. Any deviations to these standards shall be approved by the DCSS Technology Services Division (TSD) and Information Security Office (ISO).
Sample 1

Related to Deliverable Format

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

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

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

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Other Deliverables For any Deliverable that is not a System Deliverable, the applicable Work Order will set forth the acceptance criteria and other testing required for District to evaluate and accept (or, where necessary, reject) such Deliverable; provided, however, that in no case will a Deliverable be accepted by District until District has provided Contractor with District’s written acceptance thereof.

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

  • Instructional Materials A. The Board recognizes that appropriate texts, library reference facilities, maps and globes, laboratory equipment, audio-visual equipment, art supplies, athletic equipment, current periodicals, standard tests and questionnaires, computers, and similar materials are the tools of the teaching profession.

  • Deliverable [Insert a description of the deliverable.]

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