Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.
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.
NON-COMPLYING PRODUCT WATER & SEDIMENT CONTENT – PRICE DEDUCTION When the delivered fuel oil’s water and sediment content is found to be greater than three hundredths (0.03%) of a percent for Xxxxxxxx, Xx. 0 and No. 2, a deduction from the contracted price shall be taken at the rate of one (1%) percent for every two hundredths (0.02%) of a percent above the specified limit. (i.e., 0.02% above limit equals a 1% deduction, 0.04% above limit equals a 2% deduction, 0.06% above equals a 3% deduction) No. 4 fuel oil shall have an excess water and sediment content adjustment at the rate of one-tenth percent (0.1%) of invoice for every one-tenth (0.1%) in excess of five-tenths (0.5%) up to and including one percent (1.0%) and at the rate of two-tenths percent (0.2%) of invoice for every one-tenth percent (0.1%) in excess of one percent (1.0%).
Regulatory Compliance a. Monitor compliance with the 1940 Act requirements, including:
Export Compliance The Services, Content, other technology We make available, and derivatives thereof may be subject to export laws and regulations of the United States and other jurisdictions. Each party represents that it is not named on any U.S. government denied-party list. You shall not permit Users to access or use any Service or Content in a U.S.-embargoed country (currently Cuba, Iran, North Korea, Sudan or Syria) or in violation of any U.S. export law or regulation.
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.
Contract Compliance The participating state agency and/or political subdivision that utilize this State Term Schedule will be responsible for the administration of the Contract and will monitor the Contractor's performance and compliance with the terms, conditions and specifications of the Contract. If an agency observes any infraction(s), such shall be documented and conveyed to the Contractor for immediate correction. If the Contractor fails to rectify the infraction(s), the agency will notify the State through the Department of Administrative Services, Office of Procurement Services, by executing a Complaint to Vendor (CTV) to help resolve the infraction(s). The State will apply the terms and conditions of the Termination provision of this Contract to resolve the infractions(s).
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:
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.
