Compliance Tracking Clause Samples

Compliance Tracking. Solution should include industry-specific regulations (e.g., NIST CSF, GDPR, HIPAA, PCI-DSS), with automated controls and real-time monitoring to detect non-compliance or control failures.
Compliance Tracking. In accordance with the IPDES Program Description, this agreement, and as required in 40 CFR §123.26, IDEQ must operate a compliance tracking system so that staff will be capable of determining that: 1. Self-monitoring reports required by permit and/or pretreatment management requirements are submitted in a timely manner; 2. Submitted reports are complete and accurate; and 3. Permit conditions and/or pretreatment management requirements (when applicable) are met IDEQ's compliance program will track the submittal of all reports on date-related permit conditions or other schedules in effect pursuant to the permit (e.g., required reports, Notices of Violation, Administrative Orders, Consent Agreements, and court orders). IDEQ must conduct a timely and substantive review of all date-related permit conditions and reports and consider possible enforcement actions for failure to submit required reports. EPA will be responsible to enter data into EPA's national ICIS-NPDES database for the facilities it retains authority over (e.g., facilities in Indian Country).
Compliance Tracking. ‌ As provided in Chapter 7 of the Plan (Section 7.9.2), the Conservancy will track all aspects of compliance with the Permits, the Yolo HCP/NCCP, and this Agreement. It will maintain related information and data of various types, all as set forth in Section 7.9.2 of Chapter 7, to track progress toward successful implementation of the conservation strategy. This information and data will be linked to supporting information that documents Plan compliance and, where feasible, will be stored and archived electronically. The database developed for Plan compliance tracking must be compatible with the HabiTrak system developed by CDFW. The Conservancy’s database will be developed to assemble, store, and analyze all monitoring data in the database, including but not limited to data from the monitoring and adaptive management program described in Chapter 6 of the Plan. The Conservancy will make the database available to CDFW and the other Parties. All recipients of sensitive species information will keep such information confidential to the extent permitted by the Freedom of Information Act, the California Public Records Act, or other applicable laws. The Conservancy may determine, in its sole discretion, whether to provide any information in the database to third parties, including but not limited to Third Party Participants.
Compliance Tracking. ‌ 1. In accordance with the APDES Program Description, this AGREEMENT, and as required in 40 CFR §123.26, the DEPARTMENT will operate a compliance tracking system so that staff will be capable of determining that: a) self-monitoring reports required by permit and/or pretreatment management requirements are submitted in a timely manner, b) submitted reports are complete and accurate, c) permit conditions and/or pretreatment management requirements (when applicable) are met, and d) the data are accurately entered into ICIS-NPDES. 2. The DEPARTMENT’s DROPS database will track the submittal of all reports on date-related permit conditions or other schedules in effect pursuant to the permit (e.g., required reports, Notices of Violation, Administrative Orders, Consent Agreements, and court orders). The DEPARTMENT will conduct a timely and substantive review of all date-related permit conditions and reports and will consider possible enforcement actions for failure to submit required reports. 3. EPA will be responsible to enter data into ICIS-NPDES for the facilities it retains authority over (Appendix A).
Compliance Tracking. For the caps on PM/PM10 emissions from non-milling and milling equipment, ▇▇▇▇▇▇▇▇ will show compliance based on a 13 tracking period rolling sum. For the first year after permit issuance, alternative limits or calculations will be established in the permit. If data is available for the 13 tracking periods prior to issuance, the facility will use this pre-permit data in the calculations. If no pre-permit data exists, alternative tracking period specific limits will be established for the first 13 tracking periods. ▇▇▇▇▇▇▇▇ will report deviations, which could endanger human health or the environment as soon as possible after discovery of the deviation in accordance with MN Rule § 7019.1000. ▇▇▇▇▇▇▇▇ shall report all other deviations within 7 days after discovery of the deviation. For purpose of this requirement, deviation shall be defined pursuant to MN Rule § 7007.0100, subpart 8, as any noncompliance with an applicable requirement or permit condition.
Compliance Tracking. This Agreement is subject to contract compliance tracking, and the Borrower is required to provide any noted and/or requested contract compliance- related data electronically using the B2GNOW/LCPtracker systems unless other methods are approved by the Lender.
Compliance Tracking. This Agreement is subject to contract compliance tracking, and the Grantee is required to provide any noted and/or requested contract compliance- related data electronically using the B2GNOW/LCPtracker systems unless other methods are approved by the Grantor.
Compliance Tracking. For the facility-wide cap, any subcaps and the remaining VOC synthetic minor limit on the diptanks, compliance will be determined every tracking period, based on a 13 period rolling sum. For the performance ratio, compliance will be determined every tracking period based on a 13 tracking period rolling average. For the first year after permit issuance because there may not be data for the 13 periods of the rolling limit, alternative limits or calculations will be established in the permit. If data is available for the 13 tracking periods prior to issuance, the facility will use this pre-permit data in the calculations. If no pre-permit data exists, alternative tracking period specific limits will be established for the first 13 tracking periods. Particulate Matter (PM/PM10) Andersen will verify that all milling equipment is exhausted to the baghouse filters. In addition, Andersen will perform weekly visual inspections of the baghouse filters to determine that the filters are properly operated and maintained. Andersen will use representative stack test data to ensure the BACT emission limitation is being met. Based on existing data, MPCA will determine the need for additional testing. Further monitoring of emissions from the Andersen West Site milling operations will be established in the permit. For the non-milling equipment, Andersen will monitor the outflow of paints from the paint vault and bulk tanks using flow meters or daily logs. Monitoring requirements will be developed for the paint booth control equipment that ensures that the equipment is being operated properly. In order to determine PM/PM10 emissions from vinyl, Andersen will track machine throughput using daily logs. For Fibrex, combustors and other miscellaneous sources, the parties and the CAC will identify the remaining PM/PM10 monitoring conditions in the Minnesota XL Permit. These conditions will be consistent with ▇▇▇▇▇▇▇▇’▇ routine business practices to the extent practicable.