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.
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.
Proposal Format a. Offerors shall submit an original of their proposals and the number of copies listed in paragraph “c” below.
Order Forms For Products, Customer and Snow (or Customer and Partner, as applicable) will execute Snow order forms (each an “Order Form”) which will describe the (a) Product Type, (b) length of Customer’s right to use, or license to, the Product (“Product Term”), (c) quantity, endpoints, Product descriptions, license metrics, authorized users, and other usage parameters as applicable (“Usage Parameters”), (d) pricing and fees (“Fees”) and (e) other relevant details.
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:
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.
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.
Advertising Materials 1. Open Ecosystem Partner may add its own material to the information supplied by either indirectly by Distributor or directly by SAP, solely for the purposes of Open Ecosystem Partner's own marketing activities. Any material which is added must be clearly marked as Open Ecosystem Partner's material.
Additional Software Should any additional Software licenses be purchased during the Term:
