Development Code Compliance Sample Clauses

Related to Development Code Compliance

  • Code Compliance Each of the Company Properties complies with all applicable codes, laws and regulations (including, without limitation, building and zoning codes, laws and regulations and laws relating to access to the Company Properties), except for such failures to comply that would not, in the aggregate, have a Material Adverse Effect; and neither the Company nor any of its subsidiaries has knowledge of any pending or threatened condemnation proceeding, zoning change or other proceeding or action that would reasonably be expected to have a Material Adverse Effect.

  • LABOR CODE COMPLIANCE The Grantee agrees to be bound by all the provisions of the Labor Code regarding prevailing wages and shall monitor all contracts subject to reimbursement from this Agreement to assure that the prevailing wage provisions of the Labor Code are being met. Current Department of Industrial Relations (DIR) requirements may be found at: xxxx://xxx.xxx.xx.xxx/ xxx.xxx. For more information, please refer to DIR’s Public Works Manual at: xxxxx://xxx.xxx.xx.xxx/ dlse/PWManualCombined.pdf. The Grantee affirms that it is aware of the provisions of section 3700 of the Labor Code, which requires every employer to be insured against liability for workers’ compensation or to undertake self-insurance, and the Grantee affirms that it will comply with such provisions before commencing the performance of the work under this Agreement and will make its contractors and subcontractors aware of this provision.

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

  • License Compliance HP may audit Customer compliance with the software license terms. Upon reasonable notice, HP may conduct an audit during normal business hours (with the auditor’s costs being at HP’s expense). If an audit reveals underpayments then Customer will pay to HP such underpayments. If underpayments discovered exceed five (5) percent of the contract price, Customer will reimburse HP for the auditor costs.

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

  • Diagnostic Assessment 6.3.1 Boards shall provide a list of pre-approved assessment tools consistent with their Board improvement plan for student achievement and which is compliant with Ministry of Education PPM (PPM 155: Diagnostic Assessment in Support of Student Learning, date of issue January 7, 2013).

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

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

  • Safety and Compliance The Company commits to make all management and employees aware of all the changes to the Occupational Health and Safety Act and Regulations. This should be done via training courses and or union seminars. The conducting of the training and or seminars shall be at times convenient to the company.

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

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