Watershed Planning and Regulatory Compliance Support i. Reports - technical editing; graphics; report preparation and reproduction; scientific peer review of papers, reports and planning documents;
Watershed Planning and Regulatory Compliance Support Sample Clauses
Related to Watershed Planning and Regulatory Compliance Support
Legal and Regulatory Compliance The Consultant shall perform all services and prepare documents in compliance with the applicable requirements of laws, codes, rules, regulations, ordinances, and standards.
Regulatory Compliance a. Monitor compliance with the 1940 Act requirements, including:
Statutory and Regulatory Compliance Contractor shall comply with all laws and regulations applicable to the Community Development Block Grant-Disaster Recovery funds appropriated by the Disaster Relief Appropriations Act, 2013 (Pub. L. 113-2), including but not limited to the applicable Office of Management and Budget Circulars, which may impact the administration of funds and/or set forth certain cost principles, including the allowability of certain expenses.
Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.
Financial Viability and Regulatory Compliance 4.6.1 The Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. The Contractor further warrants and represents that it owes no outstanding delinquent federal, state, or local taxes or business assessments.
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.
Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.
Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.
Incident Reporting and Client Risk Prevention An incident report shall be created and maintained at the AGENCY for the following: in the event the AGENCY’S staff or subcontractor becomes aware of an occurrence of any incident of injury to a client receiving program services through the COUNTY, requiring medical treatment by a licensed physician; any lawsuit entered into or against the AGENCY, all allegations of any kind of abuse, neglect, or exploitation of the AGENCY’S clients with the exception of those AGENCIES whose primary function is working with those that have been abused, neglected or exploited unless the allegation is against an AGENCY staff member; media coverage relating to the media expressing an interest in a case or issue concerning a client of the AGENCY or an employee on the AGENCY premises, a fire, hostage situation, bomb threat, epidemic or any circumstance which may impact the service provision. All occurrences shall be verbally communicated directly to COUNTY staff no later than 10:00 a.m. the following business day via telephone to the COUNTY. All incident reports shall be made available to the COUNTY upon request and maintained at the AGENCY. These reporting requirements shall in no way supersede the requirements for notification of allegations of abuse/neglect/exploitations to the State of Florida Abuse Hotline, as mandated in Chapter(s) 39 and 415, Florida Statutes.
