Hardcopy Format Sample Clauses

Hardcopy Format. 2 Developer shall prepare all Plans on sheets 22 inches in height and 34 inches in length with 3 1-1/4-inch margins on the left and right sides, and 3/4-inch margins on the top and bottom, 4 unless otherwise noted in the Contract Documents. A blank space, 4 inches wide by 3 inches 5 high, must be left inside the margin in the lower right hand corner. All Plans must be made in 6 such a manner that clear and legible copies can be made from them. Developer shall prepare 7 half-size copies on standard 11 inch x 17 inch sheets. The number of hardcopies indicated in 8 the “Nonexclusive Submittals List” tables in the TPs for Plans indicates half-size copies.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Hardcopy Format. 15 Developer shall prepare all Plans on sheets 22 inches in height and 34 inches in length with
Sample 1Sample 2
Hardcopy Format. 9 Developer shall prepare all Plans on sheets 22 inches in height and 34 inches in length with 10 1-1/4-inch margins on the left and right sides, and 3/4-inch margins on the top and bottom, 11 unless otherwise noted in the Contract Documents. A blank space, 4 inches wide by 3 inches 12 high, must be left inside the margin in the lower right hand corner. All Plans must be made in 13 such a manner that clear and legible copies can be made from them. Developer shall prepare 14 half-size copies on standard 11 inch x 17 inch sheets. The number of hardcopies indicated in 15 the “Nonexclusive Submittals List” tables in the TPs for Plans indicates half-size copies. 16 Developer shall prepare exhibits on 8.5 inch x 11 inch, 11 inch x 17 inch, or 22 inch x 34 inch 17 sized sheets. 18 All documents, reports, and calculations must be prepared on 8.5 inch x 11 inch sheets, unless 19 otherwise noted in the Contract Documents.
Sample 1Sample 2
Hardcopy Format. In addition to the electronic submittal, one hardcopy package of specific data deliverables shall be delivered to the NASA Contracting Officer for the Government contract file. This requirement is indicated in Item 15.4, Format of each DRD. The hardcopy package shall consist of the contractor’s Transmittal Memo and one copy of the data deliverable.
Sample 1
Hardcopy Format. 7 Developer shall prepare all Plans on sheets 22 inches in height and 34 inches in length with 1- 8 1/4-inch margins on the left and right sides, and 3/4-inch margins on the top and bottom, unless 9 otherwise noted in the Contract Documents. A blank space, 4 inches wide by 3 inches high, 10 must be left inside the margin in the lower right hand corner. All Plans must be made in such a 11 manner that clear and legible copies can be made from them. Developer shall prepare half-size 12 copies on standard 11” x 17” sheets. The number of hardcopies for indicated in the 13 “Nonexclusive Submittals List” tables in the TPs for Plans indicates half-size copies. Developer 14 shall prepare exhibits on 8.5” x 11”, 11” x 17”, or 22” x 34” sized sheets. 15 All documents, reports, and calculations must be prepared on 8.5” x 11” sheets, unless 16 otherwise noted in the Contract Documents.
Sample 1

Related to Hardcopy Format

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

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

  • Templates The Applicant shall use Templates provided by Alberta Innovates to comply with its Required Reporting Metrics, Reports obligations, and with the Survey requirements. Because the Reports may contain technical or proprietary information about the Project or the Applicant, the Templates will specify when a section will be considered non-confidential. The content of sections that are marked as non-confidential can be disclosed in the public domain. All other sections will be considered confidential, and thus can only be disclosed to the Government of Alberta and to Funding Partners, if any, in confidence, but to no other party.

  • Transfer Format Transfers may include, but are not limited to, conversion of all Data into or from an industry standard format or providing application programmable interface. ENCRYPTION Data must be encrypted at all times unless specifically outlined otherwise in the Authorized User Agreement. At a minimum, encryption must be carried out at the most current NYS Encryption Standard (NYS-S14-007), (or successor policy with key access restricted to the Authorized User only, unless with the express written permission of the Authorized User. All Data in transit must be handled in accordance with ITS Policy NYS-S14-007 (or successor) or the National Institute of Standards and Technology (NIST) Federal Institute Processing Standard (FIPS)-140-2 or Transport Layer Security (TLS) 1, or TLS2 (or successor). The Authorized User Agreement shall specify the respective responsibilities of the Authorized User and the Contractor for the encryption of Data.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

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