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 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.
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.
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 Review During the Term, Developer agrees to permit the GLO, HUD, and/or a designated representative of the GLO or HUD to access the Property for the purpose of performing Compliance-Monitoring Procedures. In accordance with GLO Compliance-Monitoring Procedures, the GLO or HUD will periodically monitor and audit Developer’s compliance with the requirements of this Agreement, the CDBG-DR Regulations, the CDBG Multifamily Rental Housing Guidelines, and any and all other Governmental Requirements during the Term. In conducting any compliance reviews, the GLO or HUD will rely primarily on information obtained from Developer’s records and reports, on-site monitoring, and audit reports. The GLO or HUD may also consider other relevant information gained from other sources, including litigation and citizen complaints. Attachment G GLO Contract No. 19-097-041-B662 5.04 HAZARDOUS MATERIALS: INDEMNIFICATION
Compliance Reviews The Department may conduct a compliance review of the Contractor’s security procedures before and during the Contract term to protect Confidential Information.
MWBE COMPLIANCE 2.17.1 Contractor shall comply with the City’s Minority and Women Business Enterprise (“MWBE”) programs as set out in Chapter 15, Article V of the City of Houston Code of Ordinances. Contractor shall make good faith efforts to award subcontracts or supply agreements in at least % of the value of this Agreement to MWBEs. Contractor acknowledges that it has reviewed the requirements for good faith efforts on file with the City’s Office of Business Opportunities (“OBO”) and will comply with them.
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.
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:
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”).
