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.
Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.
Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.
OMB Standards Unless specified otherwise within this agreement, the Subrecipient shall procure all materials, property, or services in accordance with the requirements of 24 CFR 84.40−48.
Ethical Standards
7.8.1 Within ninety (90) days after the Effective Date, Developer shall adopt written policies establishing ethical standards of conduct for all Developer-Related Entities, including Developer’s supervisory and management personnel, in dealing with (a) IFA and the Department and (b) employment relations. Such policy shall be subject to review and comment by IFA prior to adoption. Such policy shall include standards of ethical conduct concerning the following:
7.8.1.1 Restrictions on gifts and contributions to, and lobbying of, IFA, the Department and any of their respective members, commissioners, directors, officers and employees, and elected State officials;
7.8.1.2 Protection of employees from unethical practices in selection, use, hiring, compensation or other terms and conditions of employment, or in firing, promotion and termination of employees;
7.8.1.3 Protection of employees from retaliatory actions (including discharge, demotion, suspension, threat, harassment, pay reduction or other discrimination in the terms and conditions of employment) in response to reporting of illegal (including the making of a false claim), unethical or unsafe actions or failures to act by any Developer-Related Entity;
7.8.1.4 Restrictions on directors, members, officers or supervisory or management personnel of any Developer-Related Entity engaging in any transaction or activity, including receiving or offering a financial incentive, benefit, loan or other financial interest, that is, or to a reasonable person appears to be, in conflict with or incompatible with the proper discharge of duties or independence of judgment or action in the performance of duties, or adverse to the interests of the Project or employees;
7.8.1.5 Restrictions on use of office or job position for a purpose that is, or would to a reasonable person appear to be, primarily for the private benefit of a director, member, officer or supervisory or management person, rather than primarily for the benefit of Developer or the Project, or primarily to achieve a private gain or an exemption from duty or responsibility for a director, member, officer or supervisory or management person; and
7.8.1.6 Restrictions on directors, members, officers or employees of any Developer-Related Entity performing any of the Work if the performance of such services would be prohibited under IFA’s conflict of interest rules and policies.
7.8.2 Developer shall cause its directors, members, officers and supervisory and management personnel, and require those of all other Developer-Related Entities, to adhere to and enforce the adopted policy on ethical standards of conduct. Developer shall establish reasonable systems and procedures to promote and monitor compliance with the policy.
7.8.3 Notwithstanding the foregoing in this Section 7.8, Developer has an affirmative obligation under this Agreement to disclose to IFA and to the Indiana State Ethics Commission when an interested party is or becomes an employee of IFA or the State. This obligation extends only to those facts that Developer knows or reasonably could know. For purposes of this Section 7.8.3, “interested party” means (a) the individual executing this Agreement, (b) an individual who has an interest of three percent (3%) or more of Developer, (c) any member of the immediate family of an individual specified in clause (a) or (b). For purposes of the preceding sentence, “immediate family” means the spouse and the unemancipated children of an individual.
CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.
Industry Standards Supplier will implement appropriate technical and organizational security measures that comply with Industry Standards in all applicable goods, services, equipment, software systems and platforms that Supplier uses to access, process and/or store Accenture Data. “Industry Standards” means security measures that are commercially reasonable in the information technology industry and that are designed to ensure the security, integrity, and confidentiality of Accenture Data, and to protect against Security Incidents.
Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
Additional Statutory and Regulatory Obligations Vendor acknowledges that it has the following additional obligations under Section 2-d with respect to any Protected Data received from the District, and that any failure to fulfill one or more of these statutory or regulatory obligations will be deemed a breach of the Master Agreement and the terms of this Data Sharing and Confidentiality Agreement:
(a) To limit internal access to Protected Data to only those employees or subcontractors that are determined to have legitimate educational interests within the meaning of Section 2-d and the Family Educational Rights and Privacy Act (FERPA); i.e., they need access in order to assist Vendor in fulfilling one or more of its obligations to the District under the Master Agreement.
(b) To not use Protected Data for any purposes other than those explicitly authorized in this Data Sharing and Confidentiality Agreement and the Master Agreement to which this Exhibit is attached.
(c) To not disclose any Protected Data to any other party, except for authorized representatives of Vendor using the information to carry out Vendor’s obligations to the District and in compliance with state and federal law, regulations and the terms of the Master Agreement, unless:
(i) the parent or eligible student has provided prior written consent; or
(ii) the disclosure is required by statute or court order and notice of the disclosure is provided to the District no later than the time of disclosure, unless such notice is expressly prohibited by the statute or court order.
(d) To maintain reasonable administrative, technical, and physical safeguards to protect the security, confidentiality, and integrity of Protected Data in its custody.
(e) To use encryption technology to protect Protected Data in its custody while in motion or at rest, using a technology or methodology specified by the Secretary of the U.S. Department of Health and Human Services in guidance issued under Section 13402(H)(2) of Public Law 111-5.
(f) To adopt technologies, safeguards and practices that align with the NIST Cybersecurity Framework.
(g) To comply with the District’s policy on data security and privacy, Section 2-d and Part 121.
(h) To not sell Protected Data nor use or disclose it for any marketing or commercial purpose or facilitate its use or disclosure by any other party for any marketing or commercial purpose or permit another party to do so.
(i) To notify the District, in accordance with the provisions of Section 5 of this Data Sharing and Confidentiality Agreement, of any breach of security resulting in an unauthorized release of Protected Data by Vendor or its assignees or subcontractors in violation of applicable state or federal law, the District’s Bill of Rights for Data Security and Privacy, the District’s policies on data security and privacy, or other binding obligations relating to data privacy and security contained in the Master Agreement and this Exhibit.
(j) To cooperate with the District and law enforcement to protect the integrity of investigations into the breach or unauthorized release of Protected Data.
(k) To pay for or promptly reimburse the District for the full cost of notification, in the event the District is required under Section 2-d to notify affected parents, students, teachers or principals of a breach or unauthorized release of Protected Data attributed to Vendor or its subcontractors or assignees.
Contract Work Hours and Safety Standards Act The following clauses apply to any Federal-aid construction contract in an amount in excess of $100,000 and subject to the overtime provisions of the Contract Work Hours and Safety Standards Act. These clauses shall be inserted in addition to the clauses required by 29 CFR 5.5(a) or 29 CFR 4.6. As used in this paragraph, the terms laborers and mechanics include watchmen and guards.
