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.
Standards Compliance DNS. 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”).
Compliance Program The Company has established and administers a compliance program applicable to the Company, to assist the Company and the directors, officers and employees of the Company in complying with applicable regulatory guidelines (including, without limitation, those administered by the FDA, the EMA, and any other foreign, federal, state or local governmental or regulatory authority performing functions similar to those performed by the FDA or EMA); except where such noncompliance would not reasonably be expected to have a Material Adverse Effect.
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.
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-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.
CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11165.7, AB 1432, and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.
Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.
Labor Compliance Program The City has its own Labor Compliance Program authorized in August 2011 by the DIR. The City will withhold contract payments when payroll records are delinquent or deemed inadequate by the City or other governmental entity, or it has been established after an investigation by the City or other governmental entity that underpayment(s) have occurred. For questions or assistance, please contact the City of San Diego’s Equal Opportunity Contracting Department at 000-000-0000.
Year 2000 Compliance Each Party warrants that it has implemented a program the goal of which is to ensure that all software, hardware and related materials (collectively called “Systems”) delivered, connected with BellSouth or supplied in the furtherance of the terms and conditions specified in this Agreement: (i) will record, store, process and display calendar dates falling on or after January 1, 2000, in the same manner, and with the same functionality as such software records, stores, processes and calendar dates falling on or before December 31, 1999; and (ii) shall include without limitation date data century recognition, calculations that accommodate same century and multicentury formulas and date values, and date data interface values that reflect the century.
