Electronic Reporting Solution Clause Samples

Electronic Reporting Solution. Post Deployment i. Work with S.D. DANR to develop a schedule for deployment in line with S.D. ▇▇▇▇’s permitting and program report deployment schedule (e.g., to have NeT available prior to the effective date of the general permit) and resource availability. ii. Assign appropriate resources to meet the agreed upon deployment schedule. If U.S. EPA will be unable to meet the scheduled deployment date, S.D. ▇▇▇▇ will be notified at least sixty days prior to the scheduled deployment date, or, if sixty days notice is not practicable an alternative schedule will be proposed as soon as practicable. U.S. EPA will work with S.D. DANR to finalize any alternative deployment schedules. iii. Work with S.D. DANR staff to develop a testing protocol, which will clearly identify any user acceptance criteria, the schedule for testing, how to test, and how to provide feedback to the U.S. EPA. At times, testing may occur concurrently with the tool development. iv. Inform S.D. DANR of any contingency plan in place to ensure regular and continuous operation of the electronic reporting solution. The contingency plan will address scenarios that could result in a disruption of operations. It can be expected that the plan will include notification, recovery, and reconstitution phases. v. Secure the integrity of the electronic reporting tool through the maintenance of a firewall. vi. Ensure access to any Copy of Record (COR). According to 40 CFR § 3.3, a COR is a true and correct copy of an electronic document received by an electronic document receiving system, which can be viewed in a human-readable format that clearly and accurately associates all the information provided in the electronic document with descriptions or labeling of the information. vii. Provide a notice on the U.S. EPA’s NPDES eReporting web page acknowledging this partnership between U.S. EPA and S.D. DANR to provide electronic reporting services.

Electronic Reporting Solution. Post Deployment i. Work with DNREC to develop a schedule for deployment in line with DNREC’s permitting schedule (e.g., to have NeT available prior to the effective date of the general permit) and resource availability. ii. Assign appropriate resources to meet the agreed upon deployment schedule. If U.S. EPA will be unable to meet the scheduled deployment date, DNREC will be notified at least sixty days prior to the scheduled deployment date, or, if sixty days notice is not practicable an alternative schedule will be proposed as soon as practicable. U.S. EPA will work with DNREC to finalize any alternative deployment schedules. iii. Work with DNREC staff to develop a testing protocol, which will clearly identify any user acceptance criteria, the schedule for testing, how to test, and how to provide feedback to the U.S. EPA. At times, testing may occur concurrently with the tool development. iv. Inform DNREC of any contingency plan in place to ensure regular and continuous operation of the electronic reporting solution. The contingency plan will address scenarios that could result in a disruption of operations. It can be expected that the plan will include notification, recovery and reconstitution phases. v. Secure the integrity of the electronic reporting tool through the maintenance of a firewall. vi. Ensure access to any Copy of Record (COR). According to 40 CFR § 3.3, a COR is a true and correct copy of an electronic document received by an electronic document receiving system, which can be viewed in a human-readable format that clearly and accurately associates all the information provided in the electronic document with descriptions or labeling of the information. vii. Provide a notice on the U.S. EPA’s NPDES eReporting web page acknowledging this partnership between U.S. EPA and DNREC to provide electronic reporting services.

Electronic Reporting Solution. Post Deployment i. Work with Mississippi Department of Environmental Quality to develop a schedule for deployment in line with Mississippi Department of Environmental Quality’s permitting and program report deployment schedule (e.g., to have NeT available prior to the effective date of the general permit) and resource availability. ii. Assign appropriate resources to meet the agreed upon deployment schedule. If U.S. EPA will be unable to meet the scheduled deployment date, Mississippi Department of Environmental Quality will be notified at least sixty days prior to the scheduled deployment date, or, if sixty days notice is not practicable an alternative schedule will be proposed as soon as practicable. U.S. EPA will work with Mississippi Department of Environmental Quality to finalize any alternative deployment schedules. iii. Work with Mississippi Department of Environmental Quality staff to develop a testing protocol, which will clearly identify any user acceptance criteria, the schedule for testing, how to test, and how to provide feedback to the U.S. EPA. At times, testing may occur concurrently with the tool development. iv. Inform Mississippi Department of Environmental Quality of any contingency plan in place to ensure regular and continuous operation of the electronic reporting solution. The contingency plan will address scenarios that could result in a disruption of operations. It can be expected that the plan will include notification, recovery, and reconstitution phases. v. Secure the integrity of the electronic reporting tool through the maintenance of a firewall. vi. Ensure access to any Copy of Record (COR). According to 40 CFR § 3.3, a COR is a true and correct copy of an electronic document received by an electronic document receiving system, which can be viewed in a human-readable format that clearly and accurately associates all the information provided in the electronic document with descriptions or labeling of the information. vii. Provide a notice on the U.S. EPA’s NPDES eReporting web page acknowledging this partnership between U.S. EPA and Mississippi Department of Environmental Quality to provide electronic reporting services. viii. Keep Mississippi Department of Environmental Quality apprised of the status of issues identified in accordance with paragraph Part IV.A.d.x above and/or completion of work to address severe issues or defects reported that prevent use of NeT. ix. Update the U.S. EPA’s national NPDES data system to collect...

Electronic Reporting Solution i. Contribute to the development and implementation of a testing protocol for the reporting solution. ii. Complete required testing as requested by the OC, which might include coordinating testers, gathering results, reconciling results, and providing feedback. iii. Update the state’s NPDES permitting program and electronic data system to electronically collect the minimum set of NPDES data (Appendix A to 40 CFR part 127) to facilitate compliance with the NPDES eRule. iv. Report all NPDES data that supports electronic reporting (e.g., permitting, compliance monitoring, compliance determinations, and enforcement activities) to EPA's national NPDES data system three months prior to the electronic reporting start dates in Table 1 in 40 CFR 127.16(a) and maintain updates thereafter. Reporting will be timely, accurate, complete, and consistent (see 40 CFR 127.23).

Electronic Reporting Solution. Post Deployment 1. Contribute to the development and implementation ofa testing protocol for the reporting solution.

Electronic Reporting Solution i. Work with TCEQ to develop a schedule for deployment in line with TCEQ’s permitting schedule (e.g., to have NeT available prior to the effective date of the general permit) and resource availability. ii. Assign appropriate resources to meet the agreed upon deployment schedule. If U.S. EPA will be unable to meet the scheduled deployment date, TCEQ will be notified at least sixty days prior to the scheduled deployment date, or, if sixty days notice is not practicable an alternative schedule will be proposed as soon as practicable. U.S. EPA will work with TCEQ to finalize any alternative deployment schedules. iii. Work with TCEQ staff to develop a testing protocol, which will clearly identify any user acceptance criteria, the schedule for testing, how to test, and how to provide feedback to the U.S. EPA. At times, testing may occur concurrently with the tool development. iv. Inform TCEQ of any contingency plan in place to ensure regular and continuous operation of the electronic reporting solution. The contingency plan will address scenarios that could result in a disruption of operations. It can be expected that the plan will include notification, recovery and reconstitution phases. v. Secure the integrity of the electronic reporting tool through the maintenance of a firewall. vi. Ensure access to any Copy of Record (COR). According to 40 CFR § 3.3, a COR is a true and correct copy of an electronic document received by an electronic document receiving system, which can be viewed in a human-readable format that clearly and accurately associates all the information provided in the electronic document with descriptions or labeling of the information. vii. Provide a notice on the U.S. EPA’s NPDES eReporting web page acknowledging this partnership between U.S. EPA and TCEQ to provide electronic reporting services.

Electronic Reporting Solution. Post Deployment i. Work with the Maryland Department of the Environment to develop a schedule for deployment in line with the Maryland Department of the Environment’s permitting and program report deployment schedule (e.g., to have NeT available prior to the effective date of the general permit) and resource availability. ii. Assign appropriate resources to meet the agreed upon deployment schedule. If U.S. EPA will be unable to meet the scheduled deployment date, the Maryland Department of the Environment will be notified at least sixty days prior to the scheduled deployment date, or, if sixty days notice is not practicable an alternative schedule will be proposed as soon as practicable. U.S. EPA will work with the Maryland Department of the Environment to finalize any alternative deployment schedules. iii. Work with the Maryland Department of the Environment staff to develop a testing protocol, which will clearly identify any user acceptance criteria, the schedule for testing, how to test, and how to provide feedback to the U.S. EPA. At times, testing may occur concurrently with the tool development. iv. Inform the Maryland Department of the Environment of any contingency plan in place to ensure regular and continuous operation of the electronic reporting solution. The contingency plan will address scenarios that could result in a disruption of operations. It can be expected that the plan will include notification, recovery, and reconstitution phases. v. Secure the integrity of the electronic reporting tool through the maintenance of a firewall. vi. Ensure access to any Copy of Record (COR). According to 40 CFR § 3.3, a COR is a true and correct copy of an electronic document received by an electronic document receiving system, which can be viewed in a human-readable format that clearly and accurately associates all the information provided in the electronic document with descriptions or labeling of the information. vii. Provide a notice on the U.S. EPA’s NPDES eReporting web page acknowledging this partnership between U.S. EPA and the Maryland Department of the Environment to provide electronic reporting services. viii. Keep the Maryland Department of the Environment apprised of the status of issues identified in accordance with paragraph Part IV.A.d.x above and/or completion of work to address severe issues or defects reported that prevent use of NeT. ix. Update the U.S. EPA’s national NPDES data system to collect the minimum set of NPDES data (Appendix...

Electronic Reporting Solution i. Work with RIDEM to develop a schedule for deployment in line with RIDEM’s permitting schedule (i.e., to have NeT available prior to the effective date of the MSGP) and resource availability. ii. Assign appropriate resources to meet the agreed upon deployment schedule. If EPA will be unable to meet the scheduled deployment date, RIDEM will be notified at least sixty days prior to the scheduled deployment date, or, if sixty days notice is not practicable an alternative schedule will be proposed as soon as practicable. EPA will work with RIDEM to finalize any alternative deployment schedules. iii. Work with RIDEM staff to develop a testing protocol, which will clearly identify any user acceptance criteria, the schedule for testing, how to test, and how to provide feedback to the OC. At times, testing may occur concurrently with the tool development. iv. Inform the authorized NPDES program of any contingency plan in place to ensure regular and continuous operation of the electronic reporting solution. The contingency plan will address scenarios that could result in a disruption of operations. It can be expected that the plan will include notification, recovery and reconstitution phases. v. Secure the integrity of the electronic reporting tool through the maintenance of a firewall. vi. Ensure access to any Copy of Record (COR). According to 40 CFR § 3.3, a COR is a true and correct copy of an electronic document received by an electronic document receiving system, which can be viewed in a human-readable format that clearly and accurately associates all the information provided in the electronic document with descriptions or labeling of the information. vii. Provide a notice on the EPA’s NPDES eReporting web page acknowledging this partnership between OC and RIDEM to provide electronic reporting services for the RIDEM’s MSGP.