Format of Deliverables Sample Clauses

Format of Deliverables. 29.1. Where reports are specified in the Contract, the Service Provider shall make such reports at the time and in such form as may be specified, or as otherwise agreed between the Parties. 29.2. The Final Report (one unbound paper copy and electronic files on disk) must be submitted to the Representative of the Authority within the time stated in Schedule One (the Project). Unless otherwise agreed the software used for the text elements of the report must be Word for Windows {tabular material should be supplied in Excel}. To be acceptable, the report must: ▇▇.▇.▇. ▇▇▇▇ the requirements of Schedule One (the Project); 29.2.2. adhere to the usual professional and scientific standards and 29.2.3. fully address the stated aims and objectives of the Project. 29.3. All reports produced under the Contract for the Authority will conform to the requirements set out in the Home Office RDS Guide to Authors 6th edition. In particular, each report will follow the same broad format of 1:3:25, unless otherwise specified, as described in this Condition 29: 29.3.1. (1pp) A concise bullet-point headline statement designed for immediate ministerial and policy overview;

Format of Deliverables. For this section, “Deliverables” shall mean all electronic documents CONTRACTOR provides to the County under this Agreement. CONTRACTOR shall ensure all Deliverables comply with the requirements of the Web Content Accessibility Guidelines (“WCAG”) 2.1, pursuant to the Americans with Disabilities Act (“ADA”). CONTRACTOR bears the burden to deliver Deliverables, such as Adobe Acrobat Portable Document Format (“PDF”) and Microsoft Office files, complying with WCAG 2.1. CONTRACTOR shall defend and indemnify the County against any breach of this Section. This Section shall survive the termination of this Agreement. Find more on Accessibility at this State website: ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇▇▇.▇▇.▇▇▇/accessibility/.

Format of Deliverables. ASA shall provide the BUNDLED PRODUCT in a binary executable format (PRC). ASA shall provide a Release Note document that will highlight the features and limitations of the PORTED PRODUCT.

Format of Deliverables. Unless otherwise expressly provided under this Agreement, all Drawings and Record As-Built Drawings prepared by Contractor or its Subcontractors or Sub-subcontractors under this Agreement shall be prepared using computer aided design (“CAD”). All CAD drawing files shall be in fully operable and editable native format in the latest commercially available version of Contractor’s preferred software. In addition, all Record As-Built Drawings and Specifications shall be provided to Owner in fully operable and editable native format in the latest commercially available version of AutoCAD®. Contractor shall provide all other deliverables in fully operable and editable native format in such software as specified by Owner, unless, with respect to such other deliverables, the only output available is in PDF.

Format of Deliverables. All deliverables will be prepared using standard MS-Office (2000 or XP) products. Formats will vary according to the type of deliverable, they include:

Format of Deliverables. Each of the foregoing deliverables shall be submitted via disk and shall be appropriately labeled to include identification of the software program (and version thereof) utilized. 2.2.4.13.1. All Drawings shall be organized within the layering system in accordance with the A/E Guidelines. 2.2.4.13.2. Layer format and names shall be in accordance with the A/E Guidelines. 2.2.4.13.3. All electronic data shall include an organized indexing system and/or a table of contents sufficiently detailed as to each discrete subject matter so as to allow for easy identification and location of each file or page of information.

Format of Deliverables. PDF file of the document, any appendices, concept plans, and typical sections. • Electronic files in their original formats with supporting graphics and GIS or other data files (Excel, InDesign, etc.).

Format of Deliverables. The work for this phase will be in the form of word processing documents as necessary to communicate the UI Overlay Zone and corresponding SPA Plan amendments for recommendation by Planning Commission and approval by City Council. ▪ Instruments of Service / Electronic Media: Electronic documents are the deliverable instruments of service. In accepting and utilizing any documents or other data on any form of electronic media generated and provided by the Consultant, the City and Applicant covenants and agrees that all such drawings and data are instruments of service of the Consultant. The electronic files submitted by the Consultant to the City and Applicant are submitted for an acceptance period of five working days. Any defects the City and ▇▇▇▇▇▇▇▇▇ discovers during this period will be reported to the Consultant and will be corrected by the Consultant.

Format of Deliverables. For the purpose of assisting construction, the BIMs developed by the consultant will be used, evolved, and transferred in the following sequence: 1. BIM Tender Model (BTM): to the owner for their records in the form of native BIM format (i.e. .rvt). 2. To the RFP candidates at 100% CD Development for the purpose of reviewing the working drawings and specifications for the preparation of a formal written bid. Note: The BTM may be amended during the bid process via addenda. 3. The BIM Record Model (BRM) shall be transferred to the owner by the consultant in native BIM format (i.e. .rvt). 4. The owner shall retain the right to use the BIM model, the BTM, the BIM Issue for Construction Model (BIFCM), and the BRM as necessary through life maintenance, repair, and modification of the building without recourse to the consultant and / or Constructor. 5. The last Revit file sent to the owner to be purged and compacted and a procedural document explaining how the model works, how to navigate it, etc., must be provided at the same time. All unnecessary or unused elements (view templates, view filters, tables, families, views, unnecessary work planes, etc.) should be removed from the document. 6. A Federated file is also requested in both native file format (.rvt), and Navisworks (.nwd).