Hardcopy Format Clause Samples

The Hardcopy Format clause specifies the requirements for providing documents or materials in a physical, printed form rather than electronically. Typically, this clause outlines the standards for print quality, the number of copies to be delivered, and the timeframe for delivery of hardcopy documents. Its core function is to ensure that parties receive tangible, physical records when necessary, which can be important for legal compliance, archival purposes, or when electronic formats are not suitable.
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.
View SourceView Similar (6)
Hardcopy Format. 15 Developer shall prepare all Plans on sheets 22 inches in height and 34 inches in length with
View SourceView Similar (3)
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.
View SourceView Similar (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.
View Source
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.
View Source

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.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the County Information Security Office.

  • File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.

  • 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: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and