Attachment 2 - SOW - NODS and NAVREMS System - FY22.docx

1. Introduction

The DT-702/PD dosimetry system is supported through efforts from multiple activities including the Naval Dosimetry Center (NDC), the Naval Surface Warfare Center Carderock Division (NSWCCD), and the Radiation, Detection, Indication and Computation (RADIAC) In-Service Engineering Agent (ISEA). There are approximately 200,000 dosimeters for the Naval Nuclear Propulsion Program (NNPP) and 50,000 dosimeters for the Navy’s Bureau of Medicine and Surgery (BUMED) supported by NDC. The vendor of the DT-702/PD dosimetry system has not successfully addressed three items of concern:

· Element correction coefficient (ECC) variability

· Inability to produce new dosimeters that meet acceptance criteria

· 8800 Reader processing variability and inconsistencies

Due to these factors, the expected lifetime of the DT-702/PD is the end of 2030. The Navy Occupational Dosimetry System (NODS) will provide the Navy the capability of a dosimetry system that will be able to consolidate legacy records and provide improved dosimetry capabilities. The NODS will enhance the Navy’s capability to detect, transmit, record and report dose received by Navy radiation workers at accident and occupational levels as defined by the American National Standards Institute (ANSI) N 13.11 (2009).

The Naval Radiation Exposure Management System (NAVREMS) comprehensive software package is planned as a replacement for several existing systems: the Automated Radiological Controls Management Information System (ARCMIS), the Navy Radiation Exposure Registry (NARER), and Maritime Medical Module (MMM). The existing systems are decades old, use technology that is out of date (e.g., Oracle forms), are largely redundant in functionality, and result in multiple instances of the same information recorded in different locations without checking for contradictory entries. Currently operated as separate instances at multiple facilities, record keeping can be consolidated, simplified, and streamlined to eliminate redundant storage of information and significantly reduce reporting requirements by creating a master database of radiation records. Reduced operational costs will result from fewer operating instances of record keeping software, reduced reporting, and overseeing radiation health requirements as Navy-wide rather than facility-specific.

2. Quantities

The acquisition plan calls for the procurement of approximately 155,000 dosimeters, 2,750 readers/base stations, logistics hardware and infrastructure needed to maintain the NODS for its lifecycle, and a comprehensive software package which has the capability of managing critical aspects of Navy Radiation Health Program business and the associated records, both current and legacy. Naval Sea Systems Command (NAVSEA) 04ND will implement a pre-planned product improvement plan and refresh technology as NODS advances occur.

A Rough Order of Magnitude (ROM) is requested based on the quantities stated above and the requirements described in Sections 2.1 through 3.6.5. The ROM shall be divided into the following categories:

a. ROM for the NODS Hardware:

· NODS Dosimeters Low Rate Initial Production (LRIP) – 15,000

· NODS Base Station LRIP – 50

· NODS Dosimeters (Production) – 140,000

· NODS Base Station (Production) – 2,700

· NODS Spare Parts – Replacement Clips with Lanyard – 14,000

· NODS Spare Parts – Replacement Holders – 14,000

· NODS Spare Parts – Replacement Batteries – 14,000

· NODS Verification and Calibration System (if applicable) – 7

b. ROM for the Software:

· NODS Commercial of the Shelf (COTS) software and database in accordance with (IAW) Section 3 of this document – 1

· NODS software improvements and test support IAW with 3.1 – 3.6 of this document – Cost Reimbursable Pricing

c. ROM for any support services necessary to install and maintain the NODS.

· NODS Data Products – See table 3 for list of NODS data deliverables

· NODS Operation, Maintenance and Calibration Training – 3 locations (Norfolk Naval Shipyard, Puget Naval Shipyard and Navy Dosimetry Center)

· NODS Base Station Site Analysis Service – 3 locations (Norfolk Naval Shipyard, Puget Naval Shipyard and Navy Dosimetry Center)

· NODS Base Station Site Installation Service – 3 locations (Norfolk Naval Shipyard, Puget Naval Shipyard and Navy Dosimetry Center)

NODS Hardware Requirements Some of the requirements for the NODS will be categorized as threshold or objectives. The threshold value for an attribute is the minimum acceptable value considered achievable within the available cost, schedule and technology at low-to-moderate risk. Performance below the threshold value is not operationally effective or suitable. The objective value for an attribute is the desired operational goal achievable, but at higher risk in cost, schedule and technology. All threshold and objective values are specifically identified within the body of this document.

The symbols [T] and [O] correspond to “(threshold)” and “(objective)” respectively for, and immediately follow each stated requirement, as applicable. Additional information is sometimes stated in directive terms and should be considered as amplifying information to the stated requirement. Where an objective is not listed, the threshold equals the objective.

2.1 NODS General Requirements

2.1.1 The NODS shall maintain the same dose measurement capabilities as the existing DT-702/PD device while reducing data collection time and potentially lowering operational costs through reduced labor needs.

2.1.2 The NODS shall be a single dosimeter design with the capability of detecting personnel dose due to photon, beta and neutron radiation. The NODS shall consist of a single dosimeter design to support all radiation monitoring requirements regardless of whether the radiation environment to be monitored is known or unknown.

2.1.3 The dosimeter to be worn on the body, or posted in areas or the environment, shall weigh no more than 120 grams [T], 60 grams [O].

2.1.4 The physical size of the dosimeter, to include all attachment features, shall be no more than 6.5 cm x 6.5 cm x 2.5 cm thick.

2.1.5 The dosimeter case protecting dosimeter internal components shall have multiple and independent methods of attaching the dosimeter case to clothing. At least three independent methods of attachment shall be able to be used simultaneously when wearing a dosimeter. One of the attachment methods shall be belt loop(s) capable of accepting a belt 4.5 cm wide. A second attachment method shall be a clip able to withstand a 1 pound pull without removal from clothing; the clip may be inserted through the belt loop, or be integral to the case. A third attachment method, independent of one of the first two attachment methods, shall utilize a small lanyard with a clip. If the dosimeter requires it be worn facing the source of radiation, the attachment methods shall aid in maintaining the correct position. The attachment methods shall prevent the dosimeter from swinging away from the body, for example, when bending over.

2.1.6 For a battery-powered dosimeter, the manufacturer shall specify the application of all the batteries used on the device. In addition, all batteries in the device shall be replaceable.

If batteries are used for communications protocol, the required battery life under normal operating conditions shall be; No less than 1 year [T]; No less than 3 years [O].

If an internal battery is used on the dosimeter to maintain a small constant voltage across the detector elements, or as a backup circuit battery supply, the battery life of the internal battery under normal operating conditions shall be; No less than 5 years [T]; No less than 7 years [O].

2.1.7 The dosimeter shall be capable of operating within a relative humidity of 40-90% [T]; or 10-95% [O].

2.1.8 Sunlight resistance is measured in Watts per unit area (W/m2) and it extends beyond visible light into the infrared and ultraviolet wavelength regions. This requirement can be simulated in laboratory environments using specialized lamps and bulbs for imitating varying intensities of sunlight; 1000 W/m2 [T]; or 1120 W/m2 [O].

2.1.9 The dosimeter shall be sealed in a manner where it shall prevent tampering.

2.1.10 The NODS will be utilized in a variety of environments and locations. Due to this, the NODS performance shall not be affected when operated in the following temperature range: -20°C to 50°C [T] -35°C to 65°C [O].

2.1.11 The NODS, if utilizing a set of batteries, shall be capable of collecting and retaining dose for at least a period of 24 hours straight. Although the dosimeter may not be capable of transmitting this dose until the battery is replaced, the performance of the dosimeter shall not be affected.

2.1.12 The manufacturer of the NODS, shall state the manufacturers and types of primary and secondary batteries used with the device. If the NODS power is supplied by a battery, after the first appearance of the indication that the operational life is going to end (low battery), this indication shall be permanent until the battery is replaced. In a field between 1 mrem/hr – 10 mrem/hr, for 100 continuous hours, the relative response of the dosimeter shall be between -0.09 to 0.11 [T] = [O]

2.1.13 The NODS components shall be designed to eliminate, or minimize to the greatest extent possible, any hazardous materials. The NODS users shall have the ability to maintain and dispose of the NODS in full compliance with existing applicable local, state, and federal statutes, regulation and standards.Access to potentially hazardous substances within or on the device shall be maintained to a minimum. [T] = [O]

2.1.14 As described in International Electrotechnical Commission (IEC) 61526, Section 6.11, indication shall be given of operational conditions in which the accumulation of dose equivalent is not accurate (within the specifications of the standard), for example, low battery supply, detector failure, electronic failure, or when used in high dose equivalent rate fields. The NODS shall have the ability to run diagnostic tests on itself and provide real-time or immediate feedback to the user as to its performance status. Items of interest for diagnostic testing shall include, but are not limited to, battery status and remaining lifetime, data integrity, communication mechanism status, last software update, update requirements, last data reading, past due for maintenance, onboard calendar and time, circuit integrity, current dose, dose rate, and user info. [T]= [O]

2.1.15 Dosimeters may require calibration to ensure accuracy and precision of the data recorded. The calibration process may vary, but some detection methods may require calibration more often than others. The calibration frequency only refers to how often the device requires calibration, independent of the calibration method itself. Triennial [T]; No recurrence Necessary [O]

2.1.16 The NODS shall not be damaged, nor experience any degradation in performance, following a salt fog exposure with the following criteria: Salt solution of 5 ± 1%, 96 hour total duration, temperature of 35˚C ± 2˚C, and a fallout rate of 3 ml/hr for each 80cm3 of horizontal collecting area [T=O].

2.1.17 For safety in the proximity of ordnance, the NODS shall be Hazards of Electromagnetic Radiation to Ordnance (HERO) compliant. The NODS shall not generate an Electromagnetic Energy (EME) to levels, which induce actuation of the Electrically Initiated Device (EID) and inadvertent activation of an electrically powered firing circuit of HERO SAFE ORDNANCE [T] and HERO UNSAFE ORDNANCE [O].

2.1.18 The NODS should be capable of detecting motion while being used/worn.

2.1.19 The dosimeter shall have the capability of disabling the data transmission as needed. The dose collection shall continue without any performance detriment, even when the data transmission is disabled.

2.1.20 The NODS shall be capable of completing the mission within an Electromagnetic Operational Environment (EMOE) at ≤ 15 meters [T=O]. The NODS shall meet the applicable Electromagnetic Interference requirements stated on MIL-STD-461-G for the following radiated susceptibility:

· RS101, Magnetic Field - This requirement is applicable from 30 Hz to 100 kHz for equipment and subsystem enclosures, including electrical cable interfaces. The requirement is not applicable for electromagnetic coupling via antennas. The NODS shall not exhibit any malfunction, degradation of performance, or deviation from specified indications, beyond the tolerances indicated in the individual equipment or subsystem specification, when subjected to the magnetic fields shown on Figures RS101-1 and RS101-2 of MIL-STD-461G. [T=O]

· RS103, Electric Field - This requirement is applicable for equipment and subsystem enclosures and all interconnecting cables. The requirement is applicable for NODS as follows: 2 MHz to 18 GHz. The NODS shall not exhibit any malfunction, degradation of performance, or deviation from specified indications, beyond the tolerances indicated in the individual equipment or subsystem specification, when subjected to the radiated electric fields listed in Table XI of MIL-STD-461G. Up to 30 MHz, the requirement shall be met for vertically polarized fields. Above 30 MHz, the requirement shall be met for both horizontally and vertically polarized fields. Circularly polarized fields are not acceptable. [T=O]

2.1.21 The table below contains the summary of the NODS general requirements.

Table 1: Summary of NODS General Requirements

Objective [O]

60 grams [O]

[T] = [O]

Belt loops attachment Clip capable of withstanding 1lb Clip with a lanyard [T] = [O]

No less than 1 year [T] No less than 3 years [O]

Internal battery:

No less than 5 years [T] No less than 7 years [O]

10% - 95% [O]

1120 W/m2 [O]

-25°C to 65°C [O]

No recurrence necessary [O]

Salt solution of 5 ± 1%, 96 hour total duration, temperature of 35˚C ± 2˚C, and a fallout rate of 3 ml/hr for each 80cm3 of horizontal collecting area [T=O]

· RS101

· RS103

Capable of completing mission in intended Electromagnetic Operational Environment (EMOE) at ≤ 15 m.

[T=O]

2.2 NODS Sustainment Requirements

2.2.1 Material Availability of the dosimeter (Amd) portion of the system shall be 0.75.

Material Availability is the measure of the total inventory of a system that is operationally capable (ready for tasking) at a given time, based on material condition. It can be expressed mathematically as the number of operational end items divided by the total population. Amd will be calculated for all Navy occupational radiation dosimeters, beginning with placement into operational service, through the planned end of service life, which is 20 years. It addresses the total population of end items planned for operational use to include those temporarily in a non-operational status once placed into service, due to calibration, unscheduled maintenance, scheduled maintenance, technology insertion opportunities, and delay times encountered in logistics and maintenance support structures.

2.2.2 Material Availability of the dosimeter reader or dosimeter communication system (Amr) shall be 1.0.

Amr will be calculated for all equipment associated with communicating (passive-active) a dosimeter’s raw data to a computer storage device for further processing. Amr of 1.0 may require redundant equipment in locations to ensure processing/communication is always available, and able to accommodate planned throughput.

Amr will be calculated for all Navy occupational radiation dosimeter processors/communication devices, beginning with placement into operational service, through the planned end of service life, which is 20 years. Amr addresses the total population of end items planned for operational use to include those temporarily in a non-operational status once placed into service, due to calibration, unscheduled maintenance, scheduled maintenance, technology insertion opportunities, and delay times encountered in logistics and maintenance support structures. Redundant equipment may be used to ensure Amr of 1.0 can be achieved.

2.2.3 Material Availability of computers and specialized software (Amc) used for dose evaluation must be 1.0.

Amc shall be calculated for all computer equipment and associated specialized software required for a dosimeter to communicate dose data and evaluate communicated dose and turn it into reportable dose (passive-active). Amc shall include all computers and specialized software required to support dose evaluation. Amc of 1.0 may require redundant equipment in locations to ensure the ability to transmit and evaluate dose of record is always available.

Amc will be calculated for all computers and their associate dose evaluation software applications, beginning with placement into operational service, through the planned end of service life, which is 20 years. Upgrades and replacement computers will be included in the calculations. Amc addresses the total population of end items planned for operational use to include those temporarily in a non-operational status once placed into service due to unscheduled maintenance, scheduled maintenance, technology insertion opportunities, and delay times encountered in logistics and maintenance support structures. Redundant equipment may be used to ensure Amc of 1.0 can be achieved.

2.2.4 Material Availability of computers and specialized software used for radiation health record keeping, control of dosimeters (inventory, issue, etc.), reporting of dose of record, etc. (Ams) must be 1.0.

Ams shall be calculated for all computer equipment and associated specialized software required for radiation health record keeping, control of dosimeters (inventory, issue, etc.), reporting of dose of record, etc. By design, a web-based common record system database at one operational center shall be assumed as the radiation health specialized software model. Ams of 1.0 may require redundant equipment, mirrored disks, etc. in a location(s) to ensure the specialized radiation health software package is always available.

Ams will be calculated for computer equipment and an associated specialized radiation health software application, beginning with placement into operational service, through the planned end of service life, which is 20 years. Upgrades and replacement computers will be included in the calculations. Ams addresses the total population of end items planned for operational use to include those temporarily in a non-operational status once placed into service due to unscheduled maintenance, scheduled maintenance, technology insertion opportunities, and delay times encountered in logistics and maintenance support structures. Redundant equipment may be used to ensure Ams of 1.0 can be achieved.

2.3 NODS Detection Energy Range, Detection Range, Accreditation and Accuracy Requirements

2.3.1 The NODS shall be able to detect, classify, measure, and report ionizing radiation (beta, gamma, x-ray (including pulsed x-ray systems), and neutron (including pulsed neutron generators)) as personnel dose equivalent (absorbed dose for accident level photon doses).

2.3.1.1 Detection Energy Range: The NODS shall have bounds of each radiation type as listed in Table 1. [T] [O]

2.3.1.2 Detection Range. The NODS shall be used to measure personnel as well as area and environmental radiation in terms of dose equivalent (absorbed dose for accident level photon range). Detection ranges are as listed in Table 1 by National Voluntary Laboratory Accreditation Program (NVLAP) accreditation category. [T] [O]

2.3.1.3 Lower Limit of Detection (LLD). The NODS shall be capable of measuring radiation of different types with LLD listed in Table 1. LLD is defined as the minimum detectable radiation dose for a one calendar-quarter (95 days) dosimeter issue period, and calculated in accordance with ANSI N13.11 (2009). [T] [O]

2.3.1.4 Accuracy. The NODS shall have accuracy for each required radiation category as defined in ANSI N13.11 (2009) by the performance quotient (L); where B is the Bias, S is the standard deviation and L is the tolerance level. The equation is the following; B2 + S2 <L2. [T] [O]

Table 2: NODS Radiological Requirements

(MeV)

Detection Range (Rem) (Rad for 1A) LLD[footnoteRef:1] [1: The lower limit of detection shall be determined using the procedures described in ANSI/HPS N13.11-2009 Appendix F (page 36).]

(Rem) Accuracy (L2)

1A (Photon)

0.02 – 7 [T]

0.01 – 15 [O] >5 to 500 [T] >5 to 5000 [O]

0.0576 [T]

0.0144 [O]

2A Shallow (Photon)

0.02 – 7 [T]

0.01 – 15 [O]

0.01 to 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.0288 [O]

2A Deep (Photon)

0.02 – 7 [T]

0.01 – 15 [O]

0.01 to 10 [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.0225 [O]

3A Shallow (Beta mixture)

0.07 – 0.935 [T] [O] = [T]

0.01 – 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.0225 [O]

3B Shallow (High energy beta)

0.935 [T] [O] = [T]

0.01 – 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.0225 [O]

4AA Shallow (Photon/beta mixture) 2A photon (0.02 – 7) with 3A beta mixtures (0.07 – 0.935) [T] [O] = [T]

0.01 – 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.0225 [O]

4AA Deep (Photon/beta mixture 2A photon (0.02 – 7) with 3A beta mixtures (0.07 – 0.935) [T] [O] = [T]

0.01 – 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.045 [O]

4AB Shallow (Photon mixture with high energy beta) 2A photon (0.02 – 7) with 3B high energy beta (0.935) [T] [O] = [T]

0.01 – 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.0225 [O]

4AB Deep (Photon mixture with high energy beta) 2A photon (0.02 – 7) with 3B high energy beta (0.935) [T] [O] = [T]

0.01 – 50 [T] [O] = [T]

0.01 [T]

0.003 [O]

0.09 [T]

0.045 [O]

5CB Deep (Moderated Cf-252 with Cs-137)

0.02 – 7 photon [T]

0.01 – 15 photon[O] 2.5E-8 to 14 neutron [T] 2.5E-8 to 20 neutron [O]

0.01 to 10 [T] 0.20– 10 neutron [T]

0.003 – 10 [O]

0.005 – 10 neutron [O]

0.010 photon

0.020 neutron [T]

0.003 photon

0.005 neutron [O]

0.09 T]

0.0225

2.4 NODS Operational Cost Requirements

2.4.1 The NODS shall have operating and support costs no more than 90% of the current system operating and support costs, over a 20 year operating period. [T]

2.4.2 The NODS shall have operating and support costs no more than 50% of the current system operating and support costs, over a 20 year operating period. [O]

Operation and support costs include:

Operation and support costs exclude the integrated software package as this is considered the same regardless of choice of dosimeter system.

2.5 NODS Reliability Requirements

2.5.1 The reliability of the NODS dosimeter devices shall be >99.95% [T] [O=T]

A reliability of >99.95% translates to < 5 errors per 10,000 dosimeters communicated.

This applies specifically to the dosimeter device. Reliability is defined as the ability of an issued dosimeter to communicate (for passive-active dosimeters) with a transceiver, and to transfer all dosimetric and identifying information from the measurement device to the supporting computer system for subsequent analysis.

NODS shall be capable of operating under normal operating environmental conditions and hazards, such as, but not limited to shock, corrosion, vibration, smoke, petroleum oil and petroleum lubricants.

2.6 NODS Data Products

2.6.1 The NODS Original Equipment Manufacturer (OEM) shall develop submit multiple data deliverables following the guidance provided Contracts Data Requirements List (CDRL).

The following data products shall be developed and submitted by the Contractor. Government guidance and final approval periods are described in each of the CDRLs below:

Table 3: NODS CDRLs List

3. NAVREMS Software Requirements

3.1 SCOPE

Naval Surface Warfare Center Carderock Division (NSWCCD), through Naval Sea Systems Command (NAVSEA) 04ND, has a requirement to procure the development, production and implementation of NAVREMS software, which will be the software application of the Naval Occupational Dosimetry System (NODS) hardware.

3.2 Reference Documents for NAVREMS Requirements

The following documents are applicable to this requirement and are hereby incorporated by reference:

· Automated Radiological Controls Management Information System (ARCMIS) Technical Design Document (TDD)

· ARCMIS Schema

· ARCMIS Table Description

· ARCMIS User’s Manual

· D6 SQL Database Schema

· Navy Radiation Exposure Registry (NARER) Schema

· Defense Innovation Board Do’s and Don’ts for Software

· Application Security and Development (ASD) Security Technical Implementation Guide (STIG) - Ver 4, Rel 10 Overview: U_ASD_V4R10_Overview (PDF file)

· U_ASD_STIG_V4R10_Manual-xccdf (XML document)

· Database Security Requirements Guide (SRG) - Ver 2, Rel 10 Overview: U_Database_V2R10_Overview (PDF file)

· Federal Risk and Authorization Management Program (FedRAMP): FedRAMP Cloud Services 2018 (PDF file) (FedRAMP website: https://fedramp.gov/)

3.3 NAVREMS General Requirements

3.3.1 NAVREMS shall use a Structured Query Language (SQL), or SQL-compatible, database for communication with legacy systems: ARCMIS, D6 and NARER.

3.3.2 NAVREMS shall have the capability to load legacy records, from ARCMIS, D6 and NARER legacy databases, and capture and quarantine replicate records, for the ultimate goal of record consolidation in one centralized database.

3.3.3 NAVREMS shall be operated using a cloud-based server: either the AWS Government Cloud (US) or the Azure Government Cloud. In addition, a NAVREMS proof of concept shall be produced and tested prior to transferring the NAVREMS production version into the Government Cloud.

3.4 NAVREMS User Interface Requirements

3.4.1 NAVREMS shall include the following modules and respective sub-modules following each module description:

· Demographics

· Exposure History – Personnel

· Exposure History – Area and Environmental

· Personnel Qualifications

· Dosimetry Inventory

· Dosimetry Issue: Personnel, Area, and Environmental

· Current Dosimeter

· Batch Loading

· Internal Dosimetry

· Reporting – Programmed and Ad-hoc

· Graduated Access

(References to this requirements section will include the modules and sub-modules, for example 3.2.M1.SM1.i is a reference to this section 3.2, module 1, sub-module 1, requirement i.)

Module 1 – Demographics

The demographics module shall track information related to personnel, area, and environmental locations monitored for radiation exposure.

The Demographics module shall have the following functionality:

1) Add Personnel

i. The primary key for personnel shall be a unique identifier, for example, a unique employee number or a system-generated unique ID.

ii. NAVREMS unique identifiers shall be linked to any existing legacy unique identifiers.

iii. Where feasible, personnel data entry shall have the capability to be completed through the use of pulldown menus. (Examples of pulldown menu selections are available in the ARCMIS schema.)

iv. NAVREMS administrator level shall have the ability to modify pulldown menu selections.

v. Individual personnel shall be identifiable by the following fields:

1) Visitor (from outside Navy) (Y/N)

2) Assigned site (home site)

3) Employer (which may be the home site or selectable from a pull down menu of employers)

4) Gender

5) Birth date

6) Service begin date

7) First, middle, last name, and suffix

8) Badge barcode number

9) Badge number

10) Work status (employed, terminated, inactive, etc.)

11) Organization

12) Permanent shop

13) Current shop (if on loan)

14) Trade skill

15) Occupation

16) Training level (worker or supervisor)

17) Crew

18) Group

19) UIC (a Navy-issued Unit Identification Code, six alpha-numeric characters)

20) Job level (military rank, GS level, etc.)

21) NNPP Program (Y/N)

22) Local control levels (in units of mrem):

a) Total Effective Dose Equivalent (TEDE)

b) Shallow dose

c) Extremity dose

d) Dose to lens of the eye

23) Date of last exposure audit

24) Audit Performer (text block to enter name)

25) General remarks (text box)

2) Display Personnel

i. Personnel queries shall be completed using a selectable single personnel field or a combination of personnel fields, for example all males, currently employed, with accumulated lifetime dose greater than 5 rem.

ii. Information displayed shall be savable to a file and printable.

iii. Displayed information pertaining to queried personnel shall include options to display the following additional information in a pop-up window:

1) Available reports

2) Lifetime dose, current-year dose and prior-year dose

3) Pregnancy status

4) Add a pregnancy

5) Issued dosimeters

6) Current radiological qualifications to include the ability to edit qualifications

7) Miscellaneous events

8) History of changes made to demographic information

9) Edit personnel, including option for deletion

3) Add Pre-employment Dose

i. Add Pre-employment Dose shall track dose from outside the Navy to a specific person, designate this dose as “non-Program”, and provide begin and end monitoring dates for each employer that performed monitoring.

ii. Radiation dose-type entries shall include the following (in units of mrem):

1) Gamma

2) Neutron

3) Shallow

4) Extremity

5) Extremity upper

6) Extremity lower

7) Eye

8) Committed Effective Dose (CED)

9) Committed Dose Equivalent (CDE)

10) Associated organ (e.g., lung)

iii. Employers shall be selectable from a pulldown menu.

4) Display Pre-Employment Dose Pre-employment dose shall be able to be queried based on a unique identifier, name, employer, date range, or dose type and a value (=, <=, >=).

5) Add Employer

i. NAVREMS shall maintain a list of employers.

ii. Employers shall be split into Navy employers (Navy sites, including all nuclear powered fleet assets by name and hull number) and non-Navy employers.

iii. New Navy assets shall be able to be added as they are built, for example new submarines and carriers entering service.

iv. Employers shall be identified by the following fields:

1) Full corporate name with acronym

2) Address

3) Radiation exposure contact name

4) Email address

5) Phone number

v. Information related to employers shall be editable.

vi. Employers shall be linked to a list of report flags (designated as Y/N) (to designate reports on which personnel are to be included).

vii. Report flags shall comprise a list of employer acronyms, for example BUMED, NAVSEA, DOE, NRC, and Johns Hopkins.

viii. The list of report flags shall be editable.

6) Display Employer Employers shall be able to be queried by acronym or name and all information related to the employer shall be displayed.

7) Dosimetry Issue Not Authorized (DINA)

i. NAVREMS shall maintain a common listing of reasons why personnel may not be issued dosimetry.

ii. The list shall be editable by personnel authorized to make additions or changes.

8) Add DINA

i. NAVREMS shall have functionality to place a single individual or a group of individuals by unique identifier on the DINA list for a specific reason.

ii. The reason shall be selectable from a pulldown menu with available DINA options.

iii. The individual placing a person on the DINA shall be captured, along with who authorized the DINA.

iv. A freeform remark field shall be available.

v. Placing an individual on the DINA list for any reason shall override the allowed issuance of dosimetry, or if dosimetry is already issued to an individual, shall notify the person adding the DINA entry that the issued dosimeter must be immediately turned in to the dosimetry office.

vi. Additionally, an email shall be generated from a default mailbox notifying the individual and individual’s supervisor of the need to return dosimetry.

vii. Add DINA shall automatically designate the date the DINA was entered as the start date.

9) Display DINA

i. NAVREMS shall have the functionality to display DINA by unique identifier, name, by DINA type, and by DINA that have no end date, that is, open DINA.

ii. Within the Display DINA functionality shall be the ability to add an end date to an individual’s DINA assignment, which on saving the entry, shall remove the DINA designation and permit an individual to again obtain dosimetry.

10) Add Event

i. NAVREMS shall have the functionality to add an event associated with a person, area or environmental location.

ii. The site at which the event occurred shall be selectable from a pulldown menu.

iii. Event reasons shall be maintained in a table, editable by a System Administrator, and available for selection in a pulldown menu.

iv. Date and time of the event, and date and time of investigation shall be able to be entered.

v. Flags for whether the event caused skin contamination and/or internal contamination shall be selectable.

vi. Events flagged for contamination shall be reported on the Article 238 report as well as BUMED reports.

vii. If the event caused the need for a dose estimate, the reason for the dose estimate shall be selectable from a pulldown menu, as well as the basis for the estimate.

viii. Various dose types shall be available for entry of dose values, and the estimated dose(s) shall be able to be designated as Program or non-Program.

11) Display Event

NAVREMS shall have the capability to display events based on the Add Event fields. (For example, queries to display an event shall be by individual or location, by type of event, event date, estimated dose ranges, or by combinations of the same.)

12) Add Area

i. NAVREMS shall have the functionality to add an area associated with either area or environmental monitoring, and designate the area as either area or environmental.

ii. Add Area shall also have the following functions:

1) Track the site for which the area is established

2) Assign a unique area id

3) Track building and room, if required

4) Track GPS coordinates, if required

5) Provide a dosimeter location descriptor

6) Record an occupancy factor

7) Record a background region

8) Assign a neutron area, if applicable

9) Have a general remarks field

13) Display Area

i. NAVREMS shall have the functionality to display area and environmental monitoring locations.

ii. Query shall be available using one or more of the fields entered in the Add Area function.

14) Add Neutron Area

i. NAVREMS shall have the ability to maintain neutron areas.

ii. A unique identifier, energy correction factor, if needed, and description of the neutron area shall be tracked.

15) Personnel Reports

i. NAVREMS shall have functionality to provide programmed reports of personnel, area, and environmental locations savable to a file and printable.

ii. NAVREMS shall also have the capability for users to create ad hoc reports from queries, save and print them.

iii. Available programmed reports shall include the following:

1) Individual CDE Report: shall report internal dose associated with an individual.

2) Change Worker Lower Control Limit (LCL) Request:

a) Shall display an editable electronic form reporting demographic information, life-to-date and year-to-date exposure, and the current LCL.

b) Proposed LCL shall be enterable.

c) Electronic approval signatures shall be able to be entered.

3) Display Person Report: shall include basic identifying demographic information and the following selectable details:

a) Accumulated dose

b) Pregnancy summary

c) Pregnancy details

d) Visits

e) Dosimeters issued

f) Dosimeters assigned

g) Demographic history

4) Individual Dose History Report: shall be executable for one particular year or all years of data, and shall include the following summary selections:

a) TEDE

b) Gamma dose

c) Neutron dose

d) Shallow dose

e) Extremity dose

f) CED

g) Dose details

h) Internal monitoring

5) Lifetime Dose Report: shall be executable for a person, area, or environmental monitoring location.

6) Worker Qualifications: shall display list of worker qualifications

16) Demographic History NAVREMS shall maintain a history of changes to demographic information for personnel, area and environmental monitoring locations.

17) Pregnancy

i. NAVREMS shall maintain records for current and past pregnancies to include the following:

1) Declaration date

2) Estimated conception date

3) Pregnancy termination date

4) Dose at time of declaration

5) Dose for the duration of pregnancy

6) Monthly dose accumulated from declaration to termination

7) Total dose to the fetus

ii. Pregnancy shall allow only one active pregnancy per person at a time, but shall allow more than one pregnancy to occur in a nine-month period, if necessary.

18) Relatable Files NAVREMS shall have the functionality to scan (without character recognition), associate, and display PDF files specific to an individual, area or environmental monitoring location dose record.

Module 2 – Exposure History - Personnel

The exposure history module shall have functionality to store and retrieve personnel radiation exposure histories by unique identifier, save retrieved information to a file and print retrieved histories for personnel in the NAVREMS system.

The Exposure History module shall have the following functionality:

1. All radiation exposure history, including pre-employment dose from non-Navy sites, shall feed dose accumulators in order to have available an accurate lifetime dose.

1. Information shall be stored by individual dosimeter usage period, by date range, where information is available. Where date range is not available (for example, in older records), the granularity of the available record shall be used for entry in NAVREMS.

1. Exposure History shall be capable of storing information generated by the Navy from film records beginning in about 1945 through all dosimetry systems used to current day.

1. For each dosimeter usage period, all associated specific dose data (for example: deep photon, deep neutron, shallow dose, eye dose, extremity dose, extremity upper, and extremity lower) as applicable to the dosimeter usage shall be stored.

1. All data shall be stored in units of millirem (mrem).

1. For records reported in System International (SI) units, a dose converter shall be available for users to convert Sieverts (Sv) to Rem prior to dose loading.

1. For legacy records, the following information shall be stored based on the unique identifier, name and any other available identifying information:

1. Dosimeter read (processing) date and time

1. Operator of the reader

1. Reader serial number

1. Dosimeter serial number

1. Issue site

1. Anatomical location the dosimeter was worn

1. Dosimeter type

1. Neutron area, if applicable

1. Batch file name

1. Current dosimeter results (from the associated NAVREMS dosimeter hardware) shall be added to exposure history records only after approval of transmitted data by a National Voluntary Laboratory Accreditation Program (NVLAP) approved signatory.

1. Total Effective Dose Equivalent (TEDE, or TED in ICRP 60 terminology) accumulators and other dose accumulators shall be calculated and stored in fields. Where internal dose greater than zero mrem exists for an individual, the assigned Committed Effective Dose Equivalent (CEDE, or CED in ICRP 60 terminology) shall be included in dose accumulator values in order to calculate an accurate TEDE.

1. For retrieved dose details, information shall be savable to a file and printable.

1. Queries of exposure history shall be capable of using single or multiple fields stored in the NAVREMS system, for example, by a unique identifier, by accumulated lifetime dose where threshold values can be set, by date range, by neutron dose, dosimeter serial number, etc., or by combinations of fields able to be queried.

1. NAVREMS shall have the functionality for the Naval Dosimetry Center (NDC) to load external dose from dosimeter systems, other than NAVREMS dosimeter hardware, to Exposure History.

Module 3 – Exposure History – Area and Environmental Monitoring Locations

NAVREMS shall have the functionality to maintain radiation exposure history for each area and environmental monitoring location.

1. Each location monitored shall be designated as either an area or environmental monitoring location.

1. Reporting and queries shall be distinct for these two monitoring programs, although functionality may be identical.

1. Dose accumulators required to be maintained are deep photon, shallow dose and deep neutron.

1. Available area and environmental monitoring legacy information from prior dosimetry systems shall be loaded into NAVREMS.

1. Legacy information to be stored shall include the following fields, as applicable:

1. Monitoring location

1. Monitoring location active (Y/N)

1. GPS coordinates, if available

1. Read date and time

1. Operator of the reader

1. Reader serial number

1. Dosimeter serial number

1. Deep photon

1. Shallow dose

1. Neutron dose

1. Issuing site

1. Issue time

1. Start date

1. End date

1. Dosimeter type

1. Any associated batch file for the dosimeter

1. Area and environmental monitoring histories shall be able to be queried by single site and location, by site and all locations, or by various combinations of stored fields of data in the history records.

1. Current dosimeter records (from NAVREMS dosimeter hardware) for area and environmental monitoring locations shall add to the history records after data has been reviewed and approved by the issuing site.

1. Administrators shall have the ability to add data fields to support NAVREMS dosimeter hardware history records.

Module 4 – Personnel Qualifications

NAVREMS shall have the functionality to maintain qualifications required for issue of dosimetry to personnel.

1. Three main qualification types shall be maintained:

1. Radiological

1. Medical

1. Internal Dosimetry

1. Qualifications maintenance shall be by radiological qualification as the primary qualification, with medical and internal dosimetry qualifications secondary.

1. Each qualification shall have a designated acronym descriptor associated with a full qualification name. (The Navy will supply a list of qualification acronyms and descriptions for all three qualification types: radiological, medical and internal dosimetry.)

1. Qualification names and acronyms shall be maintained and editable in a supporting table.

1. NAVREMS shall be capable of interfacing with other software tools that grant and track qualifications in order to maintain current qualifications required for dosimetry issue.

1. Each qualification shall have an associated expiration period (for example, 6 months, 1 year, 2 years, 5 years, etc.). (The Navy will supply the expiration period associated with each qualification.)

1. NAVREMS shall consider any tiered qualification that has expired as invalid. (For example: If all radiological qualifications are current, the medical qualification is current, but one or more required internal monitoring qualifications has expired, then the qualification is not valid for dosimeter issue.)

1. When any personnel qualification expires, an email message from a default mailbox shall be sent to the home site radiation health office of the individual as well as the radiation health office of the site at which the individual is working, if different from the home site.

1. NAVREMS shall have functionality to automatically perform queries and reports of expired qualifications and coming-due qualifications.

1. Queried returns shall be savable to a file and printable.

1. Electronic reports of expired and coming-due qualifications shall be emailed to cognizant personnel.

1. NAVREMS shall have the functionality to store and query qualifications by individual, by qualification type, by site, or by combinations of stored qualification information.

1. Where qualifications have associated examination grades, the grade shall be able to be entered and stored in NAVREMS.

1. NAVREMS shall have the ability to declare a qualification for an individual.

1. For radiological training, NAVREMS shall have the ability for an authorized individual to certify a qualification.

1. NAVREMS shall have the ability to update qualifications for individuals when requirements have been met through loading of data into NAVREMS, either manually or electronically. (For example, if an individual has a required internal monitoring performed, on addition of the internal monitoring information to NAVREMS, the associated qualification shall be updated automatically.)

1. NAVREMS shall have the ability to issue reports associated with qualifications, to include:

0. Expired qualifications

0. Scheduling qualifications

0. Issued dosimeter qualification warning report

0. Partial qualifications report

0. Radiological training qualifications grade performance

1. Existing histories of qualifications shall be loaded from legacy Navy systems into NAVREMS, and then NAVREMS shall continue to update these qualification histories as updates occur.

Module 5 – Dosimetry Inventory

1. NAVREMS shall have the functionality to maintain dosimetry inventory of all legacy Navy dosimetry systems as well as the current dosimeter system.

1. All available legacy dosimetry system information shall be loaded into NAVREMS.

1. Fields of information shall be available in NAVREMS to support loading of legacy dosimeters as well as current dosimeters.

1. NAVREMS shall have the functionality to issue a batch of dosimeters to fleet assets assigned by UIC.

1. Batch issuance shall include the following data fields:

1. Assignment period

1. Number of days assigned

1. Delivery date

1. Scheduled exchange date

1. Required quantity

1. When a dosimeter is assigned to a fleet asset, the dosimeter use history shall be updated.

1. NAVREMS shall have the functionality to display dosimeter issues.

1. This function shall be selectable for personnel, area, or environmental dosimeter usage.

1. Query of dosimeter issue shall be capable of returning information related to a single issue or multiple issues.

1. Queries shall be selectable based on one or more fields of data based on the information sought.

1. NAVREMS shall support the designation and storage location of emergency dosimeters, including those designated as control dosimeters, if control dosimeters are required.

1. NAVREMS shall have the functionality to display dosimeter results (reads for legacy dosimeters). Dosimeter results shall be able to be queried by individual field or in combinations of fields based on the information sought.

1. Load Dosimeter Inventory

1. NAVREMS shall have the…