Central Contractor Registration (CCR Sample Clauses

Central Contractor Registration (CCR. The Contractor shall register in the Central Contractor Registration (CCR) system, which is a central database of data in support of Agency missions, prior to being awarded a contract (FAR 52.204-7). The registration form is at xxx.xxx.xxx and requires the Contractor’s Data Universal Numbering System (DUNS) number.
AutoNDA by SimpleDocs
Central Contractor Registration (CCR. (1) Unless exempted by an addendum to this contract, the Contractor is responsible during performance and through final payment of any contract for the accuracy and completeness of the data within the CCR database, and for any liability resulting from the Government's reliance on inaccurate or incomplete data. To remain registered in the CCR database after the initial registration, the Contractor is required to review and update on an annual basis from the date of initial registration or subsequent updates its information in the CCR database to ensure it is current, accurate and complete. Updating information in the CCR does not alter the terms and conditions of this contract and is not a substitute for a properly executed contractual document.
Central Contractor Registration (CCR and Data Universal Numbering System (DUNS) Requirements.
Central Contractor Registration (CCR. A. As required under the Recovery Act, Subcontractor must have a Dun and Bradstreet Universal Numbering System (DUNS) number (xxx.xxx.xxx) (or update its existing DUNS record), and register with the Central Contractor Registration (CCR; xxx.xxx.xxx) no later than October 2, 2009. (ARRA § 1512, ARRA § 1609)
Central Contractor Registration (CCR. The CCR registration process may be done electronically at the World Wide Web (WWW) site: \*HYPERLINK "xxxx://xxx.xxx.xxx/"xxxx://xxx.xxx.xxx/ . (In order to be registered to use EDI, you must use the long form for registration. Certification information, including information on the EDI 838 TPP, must be furnished to the Contracting Officer within 60 calendar days after contract award to complete networking requirements within the Government.)

Related to Central Contractor Registration (CCR

  • Contractor and Subcontractor Registration Requirements Prior to the award of the Contract or Task Order, Contractor and Contractor’s subcontractors and suppliers must register with the City’s web-based vendor registration and bid management system. The City may not award the Contract until registration of all subcontractors and suppliers is complete. In the event this requirement is not met within the time frame specified by the City, the City reserves the right to rescind the Contract award and to make the award to the next responsive and responsible proposer of bidder.

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

  • Vendor Registration In order to complete any transaction between a Customer and the Contractor, the Contractor must be registered in MyFloridaMarketPlace.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

  • Texas Education Code Chapter 22 Contractor Certification for Contractor Employees Introduction Texas Education Code Chapter 22 requires entities that contract with school districts to provide service s to obtain criminal history record information regarding covered employees. Contractors must certify to the district t hat they have complied. Covered employees with disqualifying criminal histories are prohibited from serving at a sch ool district. Definitions: Covered employees: Employees of a contractor or subcontractor who have or will have continuing dutie s related to the service to be performed at the District and have or will have direct contact with students. The District will be the final arbiter of what constitutes direct contact with students. Disqualifying criminal history: Any conviction or other criminal history information designated by the District, or one of the following offenses, if at the time of the o ffense, the victim was under 18 or enrolled in a public school: (a) a felony offense under Title 5, Texas Penal Code; (b) an offense for which a defendant is required to register as a sex offender under Chapter 62, Texas Code of Criminal Procedure; or (c) an equivalent offense under federal law or the laws of another state. I certify that: NONE (Section A) of the employees of Contractor and any subcontractors are covered employees, as defined abo ve. If this box is checked, I further certify that Contractor has taken precautions or imposed conditions to ensure tha t the employees of Contractor and any subcontractor will not become covered employees. Contractor will maintain t hese precautions or conditions throughout the time the contracted services are provided. OR SOME (Section B) or all of the employees of Contractor and any subcontractor are covered employees. If this box is checked, I further certify that: (1) Contractor has obtained all required criminal history record information regarding its covered employees. None of the covered employees has a disqualifying criminal history. (2) If Contractor receives information that a covered employee subsequently has a reported criminal history, Contra ctor will immediately remove the covered employee from contract duties and notify the District in writing within 3 busi ness days. (3) Upon request, Contractor will provide the District with the name and any other requested information of covered employees so that the District may obtain criminal history record information on the covered employees. (4) If the District objects to the assignment of a covered employee on the basis of the covered employee's criminal h istory record information, Contractor agrees to discontinue using that covered employee to provide services at the District. Noncompliance or misrepresentation regarding this certification may be grounds for contract termination. None Texas Business and Commerce Code § 272 Requirements as of 9-1-2017 SB 807 prohibits construction contracts to have provisions requiring the contract to be subject to the laws of anothe r state, to be required to litigate the contract in another state, or to require arbitration in another state. A contract wit h such provisions is voidable. Under this new statute, a “construction contract” includes contracts, subcontracts, or agreements with (among others) architects, engineers, contractors, construction managers, equipment lessors, or materials suppliers. “Construction contracts” are for the design, construction, alteration, renovation, remodeling, or repair of any building or improvement to real property, or for furnishing materials or equipment for the project. The t erm also includes moving, demolition, or excavation. BY RESPONDING TO THIS SOLICITATION, AND WHEN APPLI CABLE, THE PROPOSER AGREES TO COMPLY WITH THE TEXAS BUSINESS AND COMMERCE CODE § 272 WH EN EXECUTING CONTRACTS WITH TIPS MEMBERS THAT ARE TEXAS GOVERNMENT ENTITIES. 7 5 Texas Government Code 2270 Verification Form Texas Government Code 2270 Verification Form Texas 2017 House Xxxx 89 has been signed into law by the governor and as of September 1, 2017 will be codified as Texas Government Code § 2270 and 808 et seq. The relevant section addressed by this form reads as follows: Texas Government Code Sec. 2270.002. PROVISION REQUIRED IN CONTRACT. A governmental entity may not ent er into a contract with a company for goods or services unless the contract contains a written verification from the c ompany that it: (1) does not boycott Israel; and (2) will not boycott Israel during the term of the contract.engaged by ESC Region 8/The Interlocal Purchasing System (TIPS) 0000 Xxxxxxx 000 Xxxxx Xxxxxxxxx,XX,00000 verify by this writing that the above-named company affirms that it (1) does not boycott Israel; and (2) will not boycot t Israel during the term of this contract, or any contract with the above-named Texas governmental entity in the futur e. I further affirm that if our company’s position on this issue is reversed and this affirmation is no longer valid, that t he above-named Texas governmental entity will be notified in writing within one (1) business day and we understand that our company’s failure to affirm and comply with the requirements of Texas Government Code 2270 et seq. shall be grounds for immediate contract termination without penalty to the above-named Texas governmental entity. AND our company is not listed on and we do not do business with companies that are on the the Texas Comptroller of Pu blic Accounts list of Designated Foreign Terrorists Organizations per Texas Gov't Code 2270.0153 found at xxxxx://x xxxxxxxxxx.xxxxx.xxx/xxxxxxxxxx/xxxx/xxxxxxx-xxxxxxxxx.xxx I swear and affirm that the above is true and correct. YES

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

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

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

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

  • Reservations for Registry Operations 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

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