Att 5 - NIRIS Requirements.docx

CUI

NIRIS REQUIREMENTS

The following ER data/NIRIS requirements are current and applicable to task orders awarded in FY26. Failure to meet the requirements outlined below could affect the Contractor’s performance evaluation following the completion of the task order.

All data (including, but not limited to analytical data, well construction data, borehole data, environmental measurement data, geospatial data, and documents) that are produced under this contract task order shall be loaded to the Naval Installation Restoration Information Solution (NIRIS) in the manner outlined below. NIRIS is the Navy’s authoritative data source for its Environmental Restoration Program. NIRIS is an information management solution, the purpose of which is to ultimately ensure the continuity and support of the Environmental Restoration Program. The policies mandating the use of NIRIS for both ERN and BRAC can be found at https://exwc.navfac.navy.mil/Portals/88/Documents/EXWC/Restoration/er_pdfs/gpr/navfac-ev-inst4715.1-niris-20080411.pdf?ver=JXPpr2saCokn54TVtsYPUg%3d%3d&timestamp=1651190360253 and https://exwc.navfac.navy.mil/Portals/88/Documents/EXWC/Restoration/er_pdfs/gpr/bpmo-ev-pol-niris-20080519.pdf?ver=fWb1hZwUaze9zUUPhewBPw%3d%3d&timestamp=1651190327547

In order to meet the requirements of this task order, a project manager representing the Contractor is required to obtain NIRIS access. Instructions for gaining access can be found at https://administrative-records.navfac.navy.mil/Public_Documents/Knowledge_Base/SOP_Documentation/NIRIS Access Quick Reference Guide.pdf.

Required costs for obtaining NIRIS access (i.e. purchase of a PKI certificate and/or card reader) will be included in the estimated cost for this task order.

NOTE: NIRIS contains Controlled Unclassified Information (CUI) and should be handled accordingly. Any export of data from NIRIS should only be used for official purposes and should not be disseminated to 3rd parties without the written consent of the RPM.

NIRIS training is available throughout the year. On-demand training materials (slides, videos, etc) and the current NIRIS training schedule are available in the NIRIS help section. The Contractor may request additional training by submitting a Support Request in NIRIS.

Tracking Task Order Deliverables in NIRIS The RPM will assign the project manager representing the Contractor to manage this task order in NIRIS RPM Tools (NIRIS access is required for the project manager before this can be done). Within 30 days of the receipt of the awarded contract, the Contractor shall establish the list and planned schedule of expected deliverables (and all associated dependencies) in NIRIS RPM Tools, based on the deliverables and schedule outlined in this SOW. This includes anticipated start and end dates for any required task order field work and ALL other relevant deliverable dependencies, where applicable, including the SAP WS18_Location NEDD Table (to be submitted with a draft SAP). Dependencies can be manually added or removed based on the specific deliverable requirements of this task order.

The Contractor is responsible for tracking the schedule in NIRIS, and to ensure that expected dates of document deliverables are kept current.

This task order will not be considered complete until the project in RPM Tools shows it as complete. To reach this status in RPM Tools, all deliverables and their associated dependencies are required to be marked complete or removed if they are not needed.

Analytical Data Deliverables Analytical data are entered into NIRIS via NAVFAC Electronic Data Deliverables (NEDDs). The NEDD Specifications are a collection of tables that provide the requirements, valid values, and definitions for ER data submittals. The NEDD Standard Operating Procedures (SOP) NIRIS access required), provides guidance and support for the submittal of NEDD tables in NIRIS, along with detailed instructions for compiling and submitting data to NAVFAC, which can be downloaded at https://niris.navfac.navy.mil/Document_Management/Knowledge_Base/SOP_Documentation/03-000-01%20NEDD%20SOP.pdf

PLEASE NOTE: If this task order includes munitions response and/or vapor intrusion related work/sampling, the collection of specific types of additional data may be required in order to successfully submit MR and VI specific NEDDs. It is important to carefully plan sample collection events to ensure that appropriate data is collected to achieve a successful submittal of data to NIRIS.

Prior to conducting field work, the Contractor shall discuss with the RPM, and NIRIS Regional Data Manager (RDM) if necessary, which NEDD tables will be submitted. It is extremely important that the Contractor collects all data required in the NEDDs. The Contractor shall submit ALL applicable tabular data collected for this task order into NIRIS via the NEDDs, provided a location for that data exists in a NEDD table, including data that NIRIS business rules consider “optional”.

Following the collection and validation of data, the Contractor shall submit all tabular data collected under this task order in the specified NEDD format. All data associated with this task order shall be submitted to NIRIS as soon as the data has been validated, and no later than 3 months following the collection of the sample. If that timeframe cannot be reached, the Contractor shall notify the RPM with an explanation.

Geospatial Data Deliverables NIRIS maintains ER spatial data and displays the data in the GRX Viewer. Environmental Restoration geospatial data produced as a result of this Task Order shall be submitted to NIRIS in accordance with guidance set forth in the GIS Submissions Guide. This guide (and associated templates) can be found on the Help page in NIRIS or at https://www.navfac.navy.mil/Divisions/Environmental/Products-and-Services/Environmental-Restoration/Data-Submittal-Guidance

All geospatial data shall be provided with metadata, using the appropriate coordinate system (e.g., WGS 1984), in an ESRI format (preferably in shapefile or geodatabase file format, although CAD files can be accepted) and submitted to the RDM for loading into the NIRIS geospatial database.

Before submitting spatial data, please review the Spatial Data SOP & Template. The primary focus for GIS deliverables is on Environmental Restoration Site and Land Use Control boundaries. These data should only be submitted if they represent:

· A new, legitimate site, or

· An update to an existing site boundary.

For GIS data outside these primary layers, please refer to the NIRIS Feature Classes section of the SOP for guidance. Any GIS data that does not fall within the SOP guidance should be provided on external media and submitted with the administrative record upload.

Any Environmental Restoration geospatial data produced as a result of this task order shall be submitted to the RDM no later than the submission of the final document containing that information.

If a requirement exists to submit non-Environmental Restoration Program spatial data, the Contractor shall submit that data in accordance with the Navy IGI&S Standards & Specifications for Vector GIS Deliverables, which may be appended to this SOW. Any questions related to the collection or submission of environmental restoration geospatial data should be directed to the RDM via a NIRIS Support Request.

The Contractor shall contact the appropriate RDM to obtain relevant geospatial data for use in official task order deliverables and environmental records. The Contractor shall contact the RDM, RPM, and/or a NIRIS Work Group member if there is a dispute as to whether the geospatial information located in NIRIS is correct, Contact information for the RDM can be found in the SOW.

Internal Document Reviews Pre-final versions of certain document deliverables associated with this task order require a formal review in the NIRIS Document Review Tool, in accordance with NAVFAC policy. Pre-final documents requiring review in the Document Review Tool include the following:

· Sampling and Analysis Plans and/or Field Change Requests (SAPs)

· Includes MR QAPP

· Remedial Alternatives Analysis (RAA)

· All IR documents that relate to remedy selection or evaluation, in accordance with QDR policy

The RPM may request a Subject Matter Expert (SME) review for other pre-final deliverables that do not fall into one of the categories identified above.

The Contractor shall address comments from all document reviews and load responses in the Document Review Tool as many times as necessary, in coordination with the RPM.

Document/Environmental Record Deliverables All Administrative Record, Post Decision, and Site File documents produced under this task order shall follow guidelines outlined in the Environmental Restoration Recordkeeping Manual, including any additional regional requirements where applicable. The Environmental Restoration recordkeeping Manual can be found in its entirety at https://www.navfac.navy.mil/Divisions/Environmental/Products-and-Services/Environmental-Restoration/Data-Submittal-Guidance/

All final document deliverables shall be prepared following the guidelines set forth in Appendix K of the Environmental Restoration Recordkeeping Manual and submitted to Records Management PRIOR to external distribution. Examples of final deliverables include the following:

· Reports

· Official correspondence

· Laboratory analytical data packages

· Meeting minutes

· PDF maps or drawings

· Photographs

· Fact sheets

· Public notices

· Unofficial correspondence such as emails and notes from phone conversations essential to the decision making processes

Documents shall be submitted to the appropriate Records Management representative outlined in Appendix O - NAVFAC SOP to Submit Documents to NIRIS of the Environmental Restoration Recordkeeping Manual.

Documents may only be distributed to other parties outside of the Navy after they have been approved by Records Management.

The Contractor shall work with the RPM (and installation security personnel, if appropriate) to exclude CUI in all document deliverables, when possible. Documents that must contain CUI shall follow the guidance outlined in Appendix G – Protecting Controlled Unclassified Information (CUI) and Required Markings of the ER Recordkeeping Manual. For Administrative Record and Post Decision File documents containing CUI, the Contractor shall submit two versions of the FINAL document to the applicable Records Manager or RDM. The first version shall be a “clean” document that contains CUI, and the second version shall be a redacted copy, with the CUI removed. The Contractor shall follow document redaction guidance outlined in the ER Recordkeeping Manual Appendix Z – Redaction Policy.

PLEASE NOTE: Redacted documents will not be accepted unless a clean version is concurrently submitted (or was previously submitted).

All deliverables should be submitted to NIRIS within 30 calendar days of completion. Final payment for “Final” deliverables will be dependent upon their successful loading to NIRIS.

Land Use Control Tracker The Contractor shall set up “controlled areas” for the Land Use Control(s) specified in this SOW in the NIRIS Land Use Control (LUC) Tracker module in accordance with the NIRIS specifications. The Contractor shall perform the following tasks:

· Enter all relevant LUC information required by NIRIS (e.g., LUC boundaries, monitoring reporting requirements, and responsible project team members’ contact information).

· Create a customized inspection checklist (if it does not already exist) that matches the inspection requirements outlined for the Land Use Control(s) in the LUC Remedial Design or other LUC requirements documentation.

The Contractor shall prepare a draft version of the relevant LUC information for the RPM’s review and approval prior to entering into the LUC Tracker.

The Contractor shall also enter any and all required data and documentation from LUC inspections identified in this SOW into NIRIS within three (3) months of completing the inspection. As part of the LUC inspection data entry process, the Contractor shall include a scanned copy of the field inspection form as well as any photographs taken of any issues or potential issues found during the inspection.

CUI