Consideration: Is differentiation needed if the is the result of ‘first touch’ enforcement or compliance assistance? where a process that might require a record is started in a co-regulator’s False start system but is later determined unwarranted (ex. there is nothing to regulate or no impact to report). information is generated by a municipality/others (ex. a resident may Pre-regulator request a permit to build a deck, and in the process discovers that a wetlands permit is required as well). Facility (ex. port) that reports to which do not coordinate. The pain multiple agencies points for such facilities are expected to be different from pain points at facilities that report to a single agency. Consideration: In a future phase, potentially interview stakeholders and document their problem statements to glean insight. Pain points are expected to vary for facilities that report to a single agency vs. multiple agencies. In general, it is difficult to drive users to the same portal and then to disperse these consumers to different agencies. Similarly, from the state/EPA perspective, the following use cases were identified: A record exists somewhere within the agency or within the A record exists somewhere. enterprise but external to the agency and E-Enterprise partner notification of modified data may be beneficial. Determine how to account for the varying levels of information based on need. information that leads to a request for different kinds of information. Public notice Users typically want to search by either an address/geographic polygon location or by a (ex. Facility). ‘thing’
Consideration: Is differentiation needed if the ‘first touch’ is the result of enforcement or compliance assistance? False start where a process that might require a record is started in a co-regulator’s system but is later determined unwarranted (ex. there is nothing to regulate or no impact to report). Pre-regulator information is generated by a municipality/others (ex. a resident may request a permit to build a deck, and in the process discovers that a wetlands permit is required as well). Facility (ex. port) that reports to multiple agencies which do not coordinate. The pain points for such facilities are expected to be different from pain points at facilities that report to a single agency. Consideration: In a future phase, potentially interview stakeholders and document their problem statements to glean insight. Pain points are expected to vary for facilities that report to a single agency vs. multiple agencies. In general, it is difficult to drive users to the same portal and then to disperse these consumers to different agencies. Similarly, from the state/EPA perspective, the following use cases were identified: A record exists somewhere. A record exists somewhere within the agency or within the enterprise but external to the agency and E-Enterprise partner notification of modified data may be beneficial. Determine how to account for the varying levels of information based on need. Public notice information that leads to a request for different kinds of information. Users typically want to search by either an address/geographic polygon location or by a ‘thing’ (ex. Facility).
Facility_Data_Integration_Discovery_and_Analysis_Phase_1_Final_Report.docx