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.
Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.
Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.
Accounting Format Applications for Payment shall be broken down by CSI Category and, in certain situations, by CSI Description and capital asset category, as set forth in the form for Application for Payment. The purpose is to provide appropriate backup documents for the Contractor’s Final Certification of Costs in conformance with GASB 34 accounting standards. See Section 7 – Forms, “Application for Payment” and Final Certification of Costs.
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
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.
Flexible Work Schedules (a) Academic Professional staff members throughout the University may have, as indicated below, flexible work schedules. For example, Academic Professionals often travel on University business and/or work evenings and weekends. A flexible work schedule is defined as having established working hours different from the standard 8:00 a.m. to 5:00 p.m. Monday through Friday schedule, to be followed by an employee for an agreed upon period of time.
Proposal Format a. Offerors shall submit an original of their proposals and the number of copies listed in paragraph “c” below.
Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.
Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.
