Requirement for Data Universal Numbering System (DUNS) Numbers Sample Clauses

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.
AutoNDA by SimpleDocs
Requirement for Data Universal Numbering System (DUNS) Numbers. If the Underlying Agreement is intended to be used for subawards, the Recipient agrees to notify each potential Subrecipient and entity that:
Requirement for Data Universal Numbering System (DUNS) Numbers. If the Recipient is authorized to make subawards under this Award, the Recipient: i. Must notify potential subrecipients that no entity (see definition in paragraph C of this award term) may receive a subaward from the Recipient unless the entity has provided its DUNS number to the Recipient. ii. May not make a subaward to an entity unless the entity has provided its DUNS number to the Recipient.
Requirement for Data Universal Numbering System (DUNS) Numbers. The Recipient agrees that if it is authorized to make subawards under this award, the Recipient: 1 Must notify potential subrecipients that no entity (see definition in Paragraph 8.c(3)(c)3 of this Master Agreement) may receive a subaward under the Grant Agreement or Cooperative Agreement for the Project unless the entity has provided its DUNS number to the Recipient of that Grant Agreement or Cooperative Agreement for the Project. 2 Make no subaward to an entity unless the entity has provided its DUNS number to the Recipient of that Grant Agreement or Cooperative Agreement for the Project.
Requirement for Data Universal Numbering System (DUNS) Numbers. If it is authorized to make subawards under the underlying Agreement, the Recipient agrees: Section 8.b(2)(c)3 of this Master Agreement) may receive a subaward through the underlying Agreement unless the entity has provided its DUNS number to the Recipient.
Requirement for Data Universal Numbering System (DUNS) Numbers. The Indian Tribe agrees that if it is authorized to make subawards under this award, the Indian Tribe: 1 Must notify potential subrecipients that no entity (see definition in Paragraph 8.c(3)(c)3 of this Tribal Transit Program Master Agreement) may receive a subaward under the Grant Agreement for the Tribal Transit Project unless the entity has provided its DUNS number to the Indian Tribe that is the recipient of that Grant Agreement for the Tribal Transit Project. 2 Make no subaward to an entity unless the entity has provided its DUNS number to the Indian Tribe of that Grant Agreement for the Tribal Transit Project.
Requirement for Data Universal Numbering System (DUNS) Numbers. If the Subrecipient is authorized to make subawards under this Agreement, the Subrecipient: 1. Must notify potential subrecipients that no entity (see definition in paragraph C of this Agreement term) may receive a subaward from the Subrecipient unless the entity has provided its DUNS number to the Subrecipient. 2. May not make a subaward to an entity unless the entity has provided its DUNS number to the Subrecipient.
AutoNDA by SimpleDocs
Requirement for Data Universal Numbering System (DUNS) Numbers. The Indian Tribe agrees that if it is authorized to make subawards under this award, the Indian Tribe: 1 Must notify potential subrecipients that no entity (see definition in Paragraph 8.c(3)(c)3 of this Tribal Transit Program Master Agreement) may receive a subaward under the Grant Agreement for the Tribal Transit Project unless the entity has provided its DUNS number to the Indian Tribe that is the recipient of that Grant Agreement for the Tribal Transit Project.

Related to Requirement for Data Universal Numbering System (DUNS) Numbers

  • 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-­‐xxxxxx-­‐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).

  • Local Number Portability The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. PNP is currently being worked in industry forums. The results of these forums will dictate the industry direction of PNP. BellSouth will provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

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

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • SINGLE-USE PRODUCTS The Board of County Commissioners has established a single-use products and plastic bags policy intended to reduce the use of products which have become globally recognized as having lasting negative impacts on the environment. Neither single-use products nor plastic bags may be sold or disbursed on County property by staff or contracted vendors, except as set forth in Orange County Administrative Regulation 9.01.03. Failure to comply with the Regulation may result in termination of the contract or other contractual remedies, and may affect future contracting with the County. The use of reusable, recyclable, biodegradable, or compostable materials is encouraged.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

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