Universal Identifier and Central Contractor Registration Sample Clauses

Universal Identifier and Central Contractor Registration. The Recipient agrees to comply with award terms in U.S. OMB guidance, “Universal Identifier and Central Contractor Registration,” 2 C.F.R. part 25, appendix A, which FTA has included in this Master Agreement at the direction of U.S. OMB:
Sample 1Sample 2Sample 3See All (17)
AutoNDA by SimpleDocs
Universal Identifier and Central Contractor Registration. You must comply with 2 CFR Part 25, including Appendix A. Note that the Central Contractor Registration is now available through the System for Award Management at xxx.xxx.gov.
Sample 1Sample 2Sample 3See All (4)
Universal Identifier and Central Contractor Registration. Subpart A—General Sec.
Sample 1Sample 2Sample 3See All (4)
Universal Identifier and Central Contractor Registration. In compliance with U.S. OMB guidance, “Universal Identifier and Central Contractor Registration,” 2 C.F.R. Part 25, [75 Fed. Reg. 55675, September 14, 2010], FTA is including the following award term in this Tribal Transit Program Master Agreement excerpted from “Appendix A” of that guidance:
Sample 1Sample 2Sample 3
Universal Identifier and Central Contractor Registration. 2 CFR Part 25 Effective October 1, 2010, all grant applicants must obtain a universal identifier for Federal financial assistance. Active grant recipients and their direct sub-recipients of a sub-grant award also must obtain a UEI number. To request a UEI, visit xxx.xxx.gov. The grant recipient must also register its UEI number in XXX.xxx. If you were registered in the CCR, your company’s information should be in XXX and you will need to set up a XXX account. To register in XXX you will need your entity’s UEI and your entity’s Tax ID Number (TIN) and taxpayer name (as it appears on your last tax return). Registration should take 3-5 days. If you do not receive confirmation that your XXX registration is complete, please contact XXX.xxx at xxxxx://xxx.xxx.xxx/app/answers/list. FNS may not make an award to an applicant until the applicant has complied with the requirements described in 2 CFR Part 25 to provide a valid DUNS number and maintain an active XXX registration with current information. Reporting Sub-award and Executive Compensation Information 2 CFR Part 170 The Federal Funding Accountability and Transparency Act (FFATA) of 2006 (Public Law 109–282), as amended by Section 6202 of Public Law 110–252, requires primary grantees of Federal grants and cooperative agreements to report information on sub-grantee obligations and executive compensation. FFATA promotes open government by enhancing the Federal Government’s accountability for its stewardship of public resources. This is accomplished by making Government information, particularly information on Federal spending, accessible to the general public. Primary grantees, including State agencies, are required to report actions taken on or after October 1, 2010, that obligates $25,000 or more in Federal grant funds to first-tier sub-grantees. This information must be reported in the Government-wide FFATA Sub-Award Reporting System (FSRS). In order to access FSRS, a current XXX registration is required. A primary grantee and first-tier sub-grantees must also report total compensation for each of its five most-highly compensated executives. Every primary and first-tier grantee must obtain a DUNS number prior to being eligible to receive a grant or sub-grant award. Additional information will be provided to grant recipients upon award. Xxxxxx Xxxxxx National Defense Authorization Act of Fiscal Year 2009, Public Law 110-417 Section 872 of this Act requires the development and maintenance of a Federal Governme...
Sample 1Sample 2
Universal Identifier and Central Contractor Registration. As a recipient of federal funds, Grantee will be required to maintain an active registration in the federal Central Contractor Registry (CCR) through the System for Award Management (XXX) as required by 2 CFR Part 25. Information on registration is available at xxx.xxx.gov.
Sample 1
Universal Identifier and Central Contractor Registration. I. Central Contractor Registration and Universal Identifier Requirements
Sample 1
AutoNDA by SimpleDocs
Universal Identifier and Central Contractor Registration. The Indian Tribe agrees to comply with the following award terms in “Appendix A” of U.S. OMB guidance, “Universal Identifier and Central Contractor Registration,” 2 C.F.R. Part 25, which FTA has included in this Tribal Transit Program Master Agreement at the direction of U.S. OMB:
Sample 1

Related to Universal Identifier and Central Contractor Registration

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.

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

  • Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD

  • Contract Database Metadata Elements Title: Manchester-Shortsville Central School District and Manchester-Shortsville Employees Unit, CSEA, Local 1000 AFSCME, AFL-CIO, Ontario County Local 835 (2007) Employer Name: Manchester-Shortsville Central School District Union: Manchester-Shortsville Employees Unit, CSEA, AFSCME, AFL-CIO Local: 1000, Ontario County Local 835 Effective Date: 07/01/07 Expiration Date: 06/30/11 PERB ID Number: 8608 Unit Size: Number of Pages: 33 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ Gen/8608 Agreement by and between the RED JACKET CENTRAL SCHOOL DISTRICT SUPERINTENDENT and the CIVIL SERVICE EMPLOYEES ASSOCIATION, INC. Manchester-Shortsville Employees Unit Ontario County Local 835 Local 1000 AFSCME, AFL-CIO 🙞🙜 7/1/2007 – 6/30/2011 Received 12/11/08 Table of Contents Article Page II Union Rights 3 III Job Duties 4 IV Probationary Period …………………………………………………… 5 V Work Day/Work Week 5 VI Payroll Time Sheets 6 VII Seniority 6 IX Long Term Leave Of Absence Without Pay 6 X Sick Bank 7 XI Promotions 8 XII NYS Employees Retirement Program 9 XIII Physical Examinations 9 XV Evaluations 9 XVI Wages & Merit Increases 9 XVII Eligibility For Chaperoning 13 XVIII Labor-Management Meeting 13 XIX Temporary Adjustments In A Job Assignment ……………………….. 13 XX Leave 14 XXI Payroll Deposit, Payroll Deductions ………………………………….. 15 XXII Replacement Of Damaged Items 16 XXIII Accidents & Worker’s Compensation 16 XXIV Snow Days 16 XXVI Twelve Month Employees Work Schedule & Benefits 21 XXVII Ten Month Employees Work Schedule & Benefits 22 XXVIII Eleven Month Employees Work Schedule & Benefits 22 XXX Bus Drivers 23 XXXI Grievance Procedures 24 XXXII Uniforms 27 XXXIII Discipline & Discharge 27 XXXIV Management Rights, Duration, Signatures 27

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

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