Workflow for Compliance & Enforcement and Land Resource Protection Staff Field Work
Description
No description
Project Justification
This project aims to reduce inefficient use of time and resources spent compiling field information/data which is replicated several times across multiple platforms within NJEMS, reports, and official documents. (See attached DEP IT Project Sheet for full details)
Attachments
Name
Created at
Size
Actions
FILE
NOTES-WLM Field Workflow IT Project Sheet - questions-notes-20230118T225822.pdf
2023-01-18 21:58
809.3 KiB
Activity
Show:
Completed
Add watchers
Details
Sponsoring Leadership Area
Watershed and Land Management
Sponsoring Leadership Area's Priority
AP-2
Program Area Lead(s)
Magda Usarek-Witek, Michele Agnoli
DOIT technical lead(s)
None
All Involved Leadership Areas
Div. of Information TechnologyWatershed and Land Management
Created: 6 December 2022, 21:55
Updated:
27 May 2025, 16:14
Tablets were all enabled for service plans worth about $40k/year for about 65 tablets.
Program is considering the ongoing cost to run data plans on each tablet. Possibly to cut back from 60 machines.
Tablets are at DEP but not yet deployed. With Tyler Paterson currently seeking SIM cards. Last check was 2 weeks prior to today.
CIO approval needed to proceed with data plans for tablets. Knute, to check status.
A large group meeting was held 1/20/23 with program and DOIT reps.
Magda shared a number of detailed slides showing workflow and overall expected data points and migration.
It was confirmed that existing tools like Survey123 do allow for compilation of reports with text, data and photos from a collector, with plenty of caveats and detail to be worked out.
Michele Zola and Pete T. emphasized the need to migrate/keep resultant end products and possibly even the original photos directly in Highview in keeping with file management and OPRA access standards and strategies.
We confirmed that the compliance expectations end at the loading of some inspection attributes into open compliance screens for future manual completion. There is expected to be access that leverages imported entire field records or reports (word or PDF) and/or photos - all similar to handling of current NJEMS attachments.
Compliance determinations or checklists are not envisioned for this project. No enforcement records are envisioned.
We discussed challenges to creating new masterfile and centralfile records and to importing data back into incident records across multiple simultaneous activities. Keeping these straight may require adoption of some new manual procedures and/or strict up-front creation and tracking of activities, introducing some extra, unused or lightly used activity (and maybe masterfile) placeholders.
We acknowledged that the creation of new activities in NJEMS to support batch or automated data loading has not yet been accomplished in-house.
Angela and her GIS team will take the lead to implement from here and there is currently no expectation to engage or fund a vendor.