ACDBE Program Compliance Sample Clauses

ACDBE Program Compliance. Company shall comply with all requirements of Part 23, in reference to its ACDBE participation obligations. Company shall enter into contract(s) with the certified ACDBEs identified in Schedule A, ACDBE Participation form, submitted with Company’s Proposal, and if applicable, Schedule B, Information for Determining Joint Venture Eligibility, attached hereto, said ACDBE participation being a total of %, which the Aviation Authority relied upon in awarding this Agreement, subject only to the Aviation Authority’s right to approve all contractors, or vendors, and which becomes a part of this Agreement. Company shall not breach any of its obligations with the ACDBEs. In the event Company desires to terminate or replace an ACDBE, Company shall promptly notify the Aviation Authority of the impending termination, in writing, and the reason for such. In accordance with Part 23, the Aviation Authority must approve the proposed termination, and if approved, provide written notification to Company of such termination approval. Company shall replace the terminated ACDBE with another ACDBE. If Company is unable to secure another ACDBE for performance of that part of the contract for which such ACDBE was utilized, Company shall provide the Aviation Authority with documentation in a form satisfactory to demonstrate good faith efforts of its attempts to secure a replacement of the terminated ACDBE with another ACDBE.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs

Related to ACDBE Program Compliance

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • Labor Compliance Program The City has its own Labor Compliance Program authorized in August 2011 by the DIR. The City will withhold contract payments when payroll records are delinquent or deemed inadequate by the City or other governmental entity, or it has been established after an investigation by the City or other governmental entity that underpayment(s) have occurred. For questions or assistance, please contact the City of San Diego’s Equal Opportunity Contracting Department at 000-000-0000.

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

  • Subcontractor compliance The Recipient is responsible for Subrecipient compliance with the requirements of this clause and may be held liable for unpaid wages due Subrecipient workers.

  • Year 2000 Compliance Each Party warrants that it has implemented a program the goal of which is to ensure that all software, hardware and related materials (collectively called “Systems”) delivered, connected with BellSouth or supplied in the furtherance of the terms and conditions specified in this Agreement: (i) will record, store, process and display calendar dates falling on or after January 1, 2000, in the same manner, and with the same functionality as such software records, stores, processes and calendar dates falling on or before December 31, 1999; and (ii) shall include without limitation date data century recognition, calculations that accommodate same century and multicentury formulas and date values, and date data interface values that reflect the century.

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

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