Requirement for Data Universal Numbering System Sample Clauses

Requirement for Data Universal Numbering System. (DUNS) Numbers 1. Must notify potential subrecipients that no entity (see definition in paragraph C of this award term) may receive a subaward from you unless the entity has provided its DUNS number to you. 2. May not make a subaward to an entity unless the entity has provided its DUNS number to you.
Requirement for Data Universal Numbering System. (DUNS) Numbers If you are authorized to make subawards under this award, you: 1. Must notify potential subrecipients that no entity (see definition in paragraph c of this award term) may receive a subaward from you unless the entity has provided its DUNS number to you. 2. May not make a subaward to an entity unless the entity has provided its DUNS number to you.
Requirement for Data Universal Numbering System. (DUNS) Numbers
Requirement for Data Universal Numbering System. (DUNS) numbers. The contractor is required to have a DUNS number and provide it to DEQ.
Requirement for Data Universal Numbering System. (DUNS) numbers. If the sponsor is authorized to make subawards under this award, the sponsor: a. Must notify potential subrecipients that no entity may receive a subaward from the sponsor unless the entity has provided its DUNS number to the sponsor. b. May not make a subaward to an entity unless the entity has provided its DUNS number to the spnosor.
Requirement for Data Universal Numbering System. (DUNS) numbers. The awardee may not enter into a contract or agreement with an entity that does not have a DUNS number. The awardee may verify DUNS numbers using ▇▇▇.▇▇▇.gov or may contact the assigned GTR to verify the DUNS numbers. The awardee of this Agreement is required to notify potential consultants and contractors of the requirements for a DUNS number.

Related to Requirement for Data Universal Numbering System

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.