Compliance of Your Sample Clauses
Related to Compliance of Your
Compliance Officer The Contractor shall employ a Compliance Officer who is accountable to the Contractor’s executive leadership and dedicated full-time to the Contractor’s Indiana Medicaid product lines. This individual will be the primary liaison with the State (or its designees) to facilitate communications between OMPP, the State’s contractors and the Contractor’s executive leadership and staff. This individual shall maintain a current knowledge of federal and state legislation, legislative initiatives and regulations that may impact the Hoosier Healthwise program. It is the responsibility of the Compliance Officer to coordinate reporting to the State as defined in Section 9 and to review the timeliness, accuracy and completeness of reports and data submissions to the State. The Compliance Officer, in close coordination with other key staff, has primary responsibility for ensuring all Contractor functions are in compliance with the terms of the Contract. The Compliance Officer shall meet with the OMPP Surveillance and Utilization Review Unit (SUR) on a quarterly basis.
Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered.
Compliance Training ADMINISTRATOR shall make General Compliance Training and Provider Compliance Training, where appropriate, available to Covered Individuals.
Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee:
Compliance Reports The Subadvisor at its expense will provide the Advisor with such compliance reports relating to its duties under this Agreement as may be agreed upon by such parties from time to time.
Compliance Audit LEA shall have the right but shall be under no obligation to conduct audit(s), from time to time, of Provider’s records concerning its compliance obligations as set forth in this Article V. Provider shall make such records and other documents available to LEA upon request.
COMPLIANCE OF PROVIDER 8) To ensure that HUB requirements of this contract are complied with, the Department will monitor the Provider’s efforts to involve HUBs during the performance of this contract. This will be accomplished by a review of the monthly State of Texas HUB Subcontracting Plan Prime Contractor Progress Assessment Report (Exhibit H-6) submitted to the Business Opportunity Programs Office by the Provider indicating his/her progress in achieving the HUB contract goal, and by compliance reviews conducted by the Department. The State of Texas HUB Subcontracting Plan Prime Contractor Progress Assessment Report (Exhibit H-6) must be submitted at a minimum monthly to the Business Opportunity Programs Office, in addition to with each invoice to the appropriate agency contact. The Provider shall receive credit toward the HUB goal based on actual payments to the HUB subproviders with the following exceptions and only if the arrangement is consistent with standard industry practice.
Compliance Verification (a) The subrecipient shall periodically interview a sufficient number of employees entitled to DB prevailing wages (covered employees) to verify that contractors or subcontractors are paying the appropriate wage rates. As provided in 29 CFR 5.6(a)(6), all interviews must be conducted in confidence. The subrecipient must use Standard Form 1445 (SF 1445) or equivalent documentation to memorialize the interviews. Copies of the SF 1445 are available from EPA on request.
Compliance Report The Subservicer agrees that it shall permit, not more than once per year, the Servicer, the Issuer, the Indenture Trustee or the Indenture Administrator, as the Indenture Trustee’s designee, to conduct or have conducted a procedural audit regarding the Subservicer’s compliance with the requirements of the Higher Education Act or the terms of this Agreement. Such audits shall be at the expense of the Servicer.
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.
