HSHQDC-14-R-00032_Attachment_1_Statement_of_Requirements.doc

HSHQDC-14-R-00032

REQUEST FOR PROPOSAL – ATTACHMENT 1

Basic Handheld Radioisotope Identification Device (RIID) System Requirements In support of the Domestic Nuclear Detection Office (DNDO) RFP #HSHQDC-14-R-00032, below are the government’s requirements for the Basic Handheld RIID.

Background: The requirements table (see below) is divided into two (2) groups: effectiveness and suitability. The word “requirements”, as it relates to Attachment 1 of this Solicitation, means “desired capabilities.” A subset of these requirements is considered High Priority. High priority requirements are equivalent to key performance parameters (KPPs) and, as such, are those requirements deemed essential or critical for an effective system. Failure to meet a High Priority requirement will weigh heavily as a significant weakness, in assessing the overall value and performance of the system. Similarly, failure to meet a non-High Priority requirement will be considered a weakness in assessing the overall value and performance of the system. DNDO is providing this information so that Offerors may have a better understanding of the totality of characteristics that DNDO values in a system. A tradeoff analysis will determine whether the overall value of the total system outweighs the compromise of any requirements not met. DNDO is interested in selecting from among a wide range of offerings, trading combinations of performance against price.

It is the intent of DNDO to incorporate the Basic Handheld RIID System Requirements (Attachment 1 of this solicitation) into the IDIQ contract as part of the Work Statement before the award. The winning Offeror’s Statement of Requirements (Volume I, Tab C) will be updated after Government Test if Government Test results differ from the Offeror’s original claims.

The requirements are derived from a series of sources. These include:

· “Technical Capability Standard for Handheld Instruments Used for the Detection and Identification of Radionuclides,” (TCS) Document #500-DNDO-117250v0.00, Date Revised: October 2011. The handheld instruments TCS was published in accordance with the SAFE Port Act [H.R. 4954-16, Subtitle C-Port Operations, Section 121(f) Standards] and provides performance requirements for radionuclide detection and identification of selected industrial and special nuclear materials (SNM), both bare and shielded, and detection and identification of SNM under conditions of masking by industrial, medical, or NORM sources. (http://www.dhs.gov/xlibrary/assets/dndo/dndo-technical-capability-standard-for-handheld-final.pdf)

· ANSI N42.34-2006, “American National Standard Performance Criteria for Hand-Held Instruments for the Detection and Identification of Radionuclides”.

· ANSI N42.42-2012, “American National Standard Data Format for Radiation Detectors Used for Homeland Security”.

· MIL-STD-810G, MIL-STD-464C, MIL-STF-1472G.

· Certain design and operational characteristics sought by DNDO on the basis of user needs, experience and preferences.

Each Basic Handheld RIID system requirement in Attachment 1 is specified as being for the “general purpose” variant, “maritime” variant, or “all” (i.e., a requirement for both the “general purpose” and “maritime” variants). An Offeror’s proposed system may meet the requirements of one or both variants. The maritime variant will be required to operate under more severe operational conditions than the general purpose variant and, consequently, has specific Suitability (Group 2) “maritime”-only requirements.

Instructions: Vendors should review each requirement and enter an “x” in the appropriate column indicating whether their proposed system “Meets” or “Does Not Meet” the stated requirements and provide in Volume 1, Tab C (Statement of Requirements) of their proposal. For any entries of “Meets ,” the vendor shall provide an explanation in the appropriate column of the table below and/or reference to the appropriate supporting documentation (e.g., technical, functional, or test document) provided in Volume 1, Tab D (Test Reports and Other Substantiating Evidence) of their proposal. For any entry where “Does Not Meet” is selected, the Offeror shall still provide a brief explanation as to why the proposed device does not meet the requirement or to what extent that it does meet the requirement.

The test report(s) shall include the test date, test location, system configuration version under test, test plans and test data/results. The test facility’s qualifications in performing the test (i.e., certification, accreditation, etc.) should also be listed.

Any differences between the system version tested and the proposed system must be documented in Volume 1, Tab D to disclose the configuration changes made since the test was performed, and an explanation why previous test results should or should not apply to the proposed system. Failure to adequately justify why test results from a prior model should apply to the proposed product may result in the Government not considering those test results. Any omissions or deviations from referenced test plans/reports are required to be provided or explained by the vendor with justification for all noted changes.

If the test data is restricted to Government-only, Offerors should provide the test report title and document numbers as well as specific Government points of contact including contact information.

GROUP 1 – EFFECTIVENESS REQUIREMENTS

Notes:

For any “Meets” indicate (T) Threshold or (O) Objective, where applicable.

Variants:

General Purpose: A requirement for the general purpose use environment.

Maritime: A requirement for the maritime use environment

All: A requirement for both the general purpose and maritime use environments.

High Priority:

“x”: This is considered a High Priority requirement.

If no “x” is listed, this is not a High Priority requirement.

An exception is allowed for masking ratios greater than 5:1. If the instrument is unable to identify the presence of HEU, WGPu, or DU at the fluence rates for the masking sources defined in Table 8, Table 9 and Table 10 due to excessive count rates (at the energy region of interest for HEU, WGPu, and DU), then the instrument shall provide a message indicating that it cannot identify HEU, WGPu or DU.

x

• Products using FIPS 197 Advanced Encryption Standard (AES) algorithms with at least 256 bit encryption that have been validated under FIPS 140-2

• National Security Agency (NSA) Type 2 or Type 1 encryption (Note: The use of triple Data Encryption Standard [3DES] and FIPS 140-1 is no longer permitted.)

See DHS Sensitive Systems Policy Directive 4300A for applicable policies.

x

A. Peak energy centroid in kilo electron volts B. Channel number C. Full width half maximum (FWHM) of the located peaks in % D. Size-amplitude of the peak in standard deviation units E. Counts - total collected counts within the region of interest peak

GROUP 2 – SUITABILITY REQUIREMENTS

Notes:

For any “Meets” entry indicate (T) Threshold or (O) Objective, where applicable.

Variants:

General Purpose: A requirement for the general purpose use environment.

Maritime: A requirement for the maritime use environment

All: A requirement for both the general purpose and maritime use environments.

High Priority:

“x”: This is considered a High Priority requirement.

If no “x” is listed, this is not a High Priority requirement.

X (Maritime Only)

X (Maritime Only)

Objective = Threshold

Appendix 1 – Radionuclide Tables Table 1 – Radionuclides for Requirement BHH-OR-06a (High Priority Requirement)

Table 1 Note: Requirement BHH-OR-06a is a High Priority requirement. All radionuclides within the requirement are considered High Priority requirements.

Table 2 - Radionuclides for Requirement BHH-OR-06b

Table 2 Notes:

(a) When found at background levels, these radionuclides should be saved in background spectral files but do not need to be identified on the screen or separately identified in radioisotope ID spectral files.

(b) Any of the Identification Names listed are acceptable for screen display.

(c) “Beta Emitter” may be displayed in lieu of the name of the radionuclide.

Table 3 - Radionuclides for Requirement BHH-OR-06c

Table 3 Notes:

(a) When found at background levels, these radionuclides should be saved in background spectral files but do not need to be identified on the screen or separately identified in radioisotope ID spectral files.

(b) Any of the Identification Names listed are acceptable for screen display.

(c) “Beta Emitter” may be displayed in lieu of the name of the radionuclide.

Table 4 - Radionuclides for Requirement BHH-FR-06-06, BHH-OR-09, BHH-FR-09-01

Table 4 Notes:

(a) ‘SNM-Related’ is the desired Category name for screen display, but a similar designation is also acceptable.

(b) Either Category name listed is acceptable for screen display.

Table 5 – Radionuclides for Requirement BHH-FR-08-02

Appendix 2 – Notification Table Notification Table

Notification

Note: T – Threshold, O - Objective � Note: In the below table, for any “Meets” entry, indicate (T) Threshold or (O) Objective, where applicable.