System for Award Management XXX Registration and Unique Entity Identifier Uei Sample Clauses

System for Award Management XXX Registration and Unique Entity Identifier Uei a. Requirement for System for Award Management (XXX): Unless the Sponsor is exempted from this requirement under 2 CFR § 25.110, the Sponsor must maintain the currency of its information in the XXX until the Sponsor submits the final financial report required under this Grant, or receives the final payment, whichever is later. This requires that the Sponsor review and update the information at least annually after the initial registration and more frequently if required by changes in information or another award term. Additional information about registration procedures may be found at the XXX website (currently at xxxx://xxx.xxx.gov).
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
System for Award Management XXX Registration and Unique Entity Identifier Uei 
Sample 1Sample 2Sample 3

Related to System for Award Management XXX Registration and Unique Entity Identifier Uei

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • 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).

Time is Money Join Law Insider Premium to draft better contracts faster.