DIR Customer Compliance Sample Clauses

DIR Customer Compliance. DIR Customer shall comply with all policies, procedures, and processes in the relevant SMM(s) and as provided by DIR.
AutoNDA by SimpleDocs

Related to DIR Customer Compliance

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

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

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

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

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

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

  • Contractor Compliance Contractor represents and warrants to pay, at its sole expense, for all applicable permits, licenses, tariffs, tolls and fees to give all notices and comply with all laws, ordinances, rules and regulations of any governmental entity in conjunction with the performance of obligations under the Contract. Prior to award and during the Contract term and any renewals thereof, Contractor must establish to the satisfaction of the Commissioner that it meets or exceeds all requirements of the Bid/Contract and any applicable laws, including but not limited to, permits, insurance coverage, licensing, proof of coverage for worker’s compensation, and shall provide such proof as required by the Commissioner. Failure to do so may constitute grounds for the Commissioner to cancel or suspend this Contract, in whole or in part, or to take any other action deemed necessary by the Commissioner.

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

  • DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).

  • Monthly MWBE Contractor Compliance Report A. In accordance with 5 NYCRR § 142.10, Contractor is required to report Monthly MWBE Contractor Compliance to OGS during the term of the Contract for the preceding month’s activity, documenting progress made towards achievement of the Contract MWBE goals. OGS requests that all Contractors use the New York State Contract System (“NYSCS”) to report subcontractor and supplier payments made by Contractor to MWBEs performing work under the Contract. The NYSCS may be accessed at xxxxx://xx.xxxxxxxxxxxxxx.xxx/. This is a New York State-based system that all State agencies and authorities will be implementing to ensure uniform contract compliance reporting throughout New York State.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!