IPTD-103
WRM Data Management for Project Data
Description
The Division of Water Supply and Geoscience and Division of Water Quality collect data from regulated entities for compliance determination. Additionally, there are other cases in which the programs need to request data that is not for specific compliance or a regulatory requirement. These include data collected ahead of an onsite inspection, monitoring requested related to emerging contaminants, special project data and data submissions required as a result of an emergency incident. There are currently data management systems that are utilized to manage compliance data and the programs are working with DOIT to evaluate the areas in which these data are not managed electronically (eMORs project, NJLCR project etc). However, there is not currently a process/data system to address these types of project data that is not specifically rule or compliance driven.
Without an established data management system staff are often receiving data from the various regulated entities that is not formatted in a way to easily assess/analyze. Depending on the project this could result in hundreds of spreadsheets that staff are manually summarizing. Additionally, without the data management system there is not a centralized location that these data could be archived for future use. The current practice is to receive data on forms or excel spreadsheets via email submissions.
Project Justification
1) Outward facing data entry portal for the regulated community/laboratories to submit data
2) An internal database to house the data
3) The ability to query the data either through existing tools such as Business Objects/Web Intelligence or its own query functionality for both internal analysis
4) Ability to capture geospatial information such as monitoring site locations
5) Potentially the ability to make the reports and data publicly available as appropriate
Potential Project Types: Emergency Incident data, Pre inspection data, Emerging Contaminant Data, Watershed study data etc.
Data Types Examples- this list may not be all inclusive
• Facility Data: Facility ID, Facility Name
• Project Data: Project Name, Project Description,
• Site Data Types: Location (Lat/Long), Site Name, Site Description, Site Type,
• Result Date Types: Parameter, Result Value, Result Units, Date of analysis, Method
Project Examples:
Drinking Water System Inspection: DWSG requested the water system provide turbidity data from various locations within the treatment process and at point of entry to the DS
Change in Source Analysis: DWSG requested the water system collect water quality parameter (Alkalinity, pH, Chloride, Sulfate, etc) data at 5 locations within the distribution system and submit to the department for review prior to and during change in source.
Emerging Contaminants: DWSG requested drinking water system collect 1,4 Dioxane data at the intake and in the source water. DWQ has requested PFAS data from a group of permittees.
The team that I typically work with at Rutgers has been moved to a new section within the University that provides them with significantly more resources. Therefore, they now have someone available to work on this project immediately. Next steps are for me to go through the original design doc and highlight what has changed from a few years ago till now. One item that I want to add is the ability to push the data from Rutgers to DEP so that people can access the information via DEP supported tools (TABLEAU, GIS, etc.) if needed. I will be communicating with Kurt Jaegers regarding this.
This project was originally supposed to kick off in October of 2023. Rutgers has been swamped with projects. AC Gardner has stated that this is a priority project to her, so I have come to an agreement with Rutgers University to begin this project in place of the Pesticide Surveys project which was set to begin 7/1/24. The pesticides project will be pushed back by 6 months so that this specific project can get started.
Turns out me and the Rutgers guys made a mistake in the budget breakdown for the project cost. One row of developer's time was missing out of the budget spreadsheet. I’ve adjusted the cost of this project from $94,179 to $125,474.
Spending Plan package has been submitted for signatures. Once I receive signed documents, I can begin the Contract Agreement process.
RU reviewed proposal/design document. Came back with …
Cost: $94,179
Start Date: 10/2023
Duration: 18 Months
Mike K waiting to hear back form Rutgers on pricing/schedule.
Sent a nearly finalized version of the proposal/design document to the WRM Divisions. Asking them if they are okay if I send it on to Rutgers for review. If WRM Divisions want to review the document again, I gave them a deadline of 11/10 to do so. I expect that we will be able to send this out to RU very soon.
Mike K. confirmed Rutgers can take this on.
At Pete’s request, I confirmed that Rutgers is interested in doing this project. Next step will be for me to work with the program to write up a detailed design document laying out a vision for the system. Then will work through the typical contract process that I’ve used over the years to get the work done.
First inquiry is with Enfo Tech. This requires Jim and Rich H. engaging Enfo Tech. Jim to gather requirements form this write-up and program as needed.
Options look like a workplan with either of:
EnfoTech reenacting WQDE
Rutgers (like Beaches work)
Do we need to engage with each before deciding between? Yes, need to involve the program in review of what is possible. Preferences to look and feel.
Audience is those handling data for Trish (PFAS data/non-compliance, other info coming in from email)