Terminated License Digitization Project
Description
- The ability to upload PDF documents to a RAD gray bar’s attachment list that can be limited from view by NJDEP employees outside of BER.
Problem Statement
The project to digitally archive the Bureau of Environmental Radiation’s terminated license files has been approved. Digitization of BER’s terminated files will create an invaluable network in which to quickly access necessary information digitally and remotely. The completion of this project will save significant time and effort in the future, while establishing a secure, accessible, and comprehensive archive of BER’s files to the benefit of all employees.
Because the license PI#’s already exist in NJEMS, the most comprehensive storage option is to add scanned files directly under the most recent RAD activity gray bar’s attachment list for ease of access. However, because radioactive materials documents are considered sensitive information and we are under regulatory obligation to limit access (per N.J.A.C. 7:1D-3.2(b)) from non-BER employees, our goal is to upload these PDF files to the NJEMS attachment list and protect view and access similar to the permissions granted to other RAD documents (such as RAD licenses and RAD word documents).
Because the license PI#’s already exist in NJEMS, the most comprehensive storage option is to add scanned files directly under the most recent RAD activity gray bar’s attachment list for ease of access. However, because radioactive materials documents are considered sensitive information and we are under regulatory obligation to limit access (per N.J.A.C. 7:1D-3.2(b)) from non-BER employees, our goal is to upload these PDF files to the NJEMS attachment list and protect view and access similar to the permissions granted to other RAD documents (such as RAD licenses and RAD word documents).
Project Justification
This has the potential to benefit not only this project but will allow for uploading of pertinent PDF documents to NJEMS under active licenses, which are currently only available on the shared drive or in a physical license file. Storing license files under the gray bar of an already existing PI# in NJEMS is the most comprehensive storage option, particularly for BER employees requiring access to whole, complete license files while working remotely. This consolidates pertinent documents to one location for time-saving ease of access. This will potentially avoid instances of licenses being taken out of the office for remote work, which can risk loss or damage of documents.
Estimated Transactions
None
Created
8 May 2025, 12:41
Target Rollout Date
1 July 2025
Target Rollout Date Reason
July 1, 2025 – This date is ideal, but flexible. The project is already underway but cannot move forward without a means of file storage.
Updated
5 March 2026, 10:11
Attachments
Linked work items
relates to
IPTD-489
Modification of DPHS NJEMS Attachment List
IPTD-37
Release Prevention eSubmission of Event Data
Completed
Active
Activity
Show:
Create issue
Active
Add watchers
Details
Sponsoring Leadership Area
Air, Energy and Materials Sustainability
Sponsoring Leadership Area's Priority
AP-4
Program Area Lead(s)
KJ Karausky, Jenn Daino, Joe Power
DOIT technical lead(s)
Mike McCormack
All Involved Leadership Areas
Div. of Information Technology
Created: 8 May 2025, 16:41
Updated:
5 March 2026, 15:11
Regarding the NJEMS enhancement to “hide” BER Attachment List based on security role:
Mike K. asked DMU to deploy RSP rollout scripts to Prod, awaiting completion. Service will be hidden in RSP prod while DPCC completes instruction language for the service.
NJEMS piece completed, awaiting DMU to deploy to production.
Once NJEMS piece is deployed to prod, and DPCC completes instruction language for RSP, the service can be unhidden in RSP and all will be live
CGI Work Plan 196 Modification 3 Signed 10/31/2025 for this project
Working with CGI to spec out the technical requirements for this effort (as also related to IPTD-489), to determine the extent of development that would be needed and next steps for implementation
This is same broad functionality requested as part of