MODIFICATION
63 -- DNDO RFI - RPM Vendor Data Collection Event - Amendment 1 - Revised Documents
- Notice Date
- 1/22/2016
- Notice Type
- Modification/Amendment
- NAICS
- 334511
— Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing
- Contracting Office
- Office of the Chief Procurement Officer, Washington, District of Columbia, 20528, United States
- ZIP Code
- 20528
- Solicitation Number
- HSHQDC-16-RFIVDCEvent
- Point of Contact
- Matthew Robertson, Phone: 2022547163
- E-Mail Address
-
matthew.robertson@hq.dhs.gov
(matthew.robertson@hq.dhs.gov)
- Small Business Set-Aside
- N/A
- Description
- Updated Attachment 1 Updated Attachment 6 1.INTRODUCTION The Department of Homeland Security (DHS), Domestic Nuclear Detection Office (DNDO) is hosting a Vendor Data Collection Event (VDCE) to be conducted at Radiological/Nuclear Countermeasures Test and Evaluation Complex (RNCTEC) at the Nevada National Security Site (NNSS), Mercury, NV. The VDCE is not an event that DNDO will use to evaluate Radiological Portal Monitor (RPM) system performance, but rather provides vendors with an opportunity to evaluate DNDO supplied radiological sources to support system improvements. 1.1Background DNDO Radiation Portal Monitor systems are used to scan containerized cargo, commercial conveyances, and privately owned vehicles for illicit nuclear and other radioactive materials. Information regarding the RPM Program is included in the RPM Industry Engagement briefing slides posted to FedBizOpps on December 17, 2015. 2.Vendor Data Collection Event The VDCE is projected to take place between April 2016 through June 2016 at RNCTEC at the NNSS, Mercury, NV. During the VDCE, vendor-provided RPMs will be exposed to a variety of DNDO supplied radiological sources, including special nuclear material, Naturally Occurring Radioactive Material (NORM), and Industrial. Each system will be subjected to radiation sources placed on stationary positioners within the lane and radiation sources in various configurations of shielding and masking (NORM) placed in an Intermodal Cargo Container (IMCC) and driven through the RPM. Vendors will supervise the setup and operation of their RPMs. DNDO expects that RPMs from multiple vendors will be operated concurrently. The data collection may assist vendors in refining algorithms, developing replay tools, and other system performance improvements. Vendors will be required to supply DNDO with copies of all data collected and data structure documentation during the event. DNDO anticipates the event assisting in refining data collection procedures, verifying data transfer and storage implications, etc. associated with proposed RPM solutions. 2.1 VDCE Notional Schedule 1. VDCE registration announcement (Jan 12, 2016) 2. VDCE participation requests received (Feb 3, 2016) 3. VDCE participants notified (Feb 9, 2016) 4. Execute bailment agreement (Feb 15, 2016) 5. Participant RPM Systems Received at NNSS (NLT March 30, 2016) 6. Conduct VDCE and release data (April - June 2016) 7. Systems shipped from NNSS to vendors (NLT July 2016) 2.2 Participation Requirements • Vendor is responsible for the shipment of an RPM system and spare parts before, during, and after the VDCE. At NNSS, covered storage for vendor systems and any accompanying spare parts when not in use will be provided. System, spare parts, and other ancillary equipment will be returned within 30 days after the VDCE ends. • Submit a list of ancillary equipment (e.g. occupancy sensors, tools, cameras, etc.) that vendors wish to bring on site. Note, use of cameras for photos and videos, other than occupancy, will not be allowed. • Supply fully enclosed radiation portal monitor that can be bolted to mounting base and can withstand typical outdoor conditions. DNDO will provide the mounting/bolt pattern that the vendor will be required to have their system mounted to (Attachment 7, filename WS4433.pdf). Vendors are also required to provide: (See Attachment 6: Draft Bailment Agreement) -the wiring between the RPM and the control computer, -your own computer, -the control/monitoring computer, -drawings for the RPM identifying detector locations and overall dimensions, -RPM data format description -spare parts, and -copies of all the data collected, data structure documentation and a copy of software that can be used to view the data collected from their system to DNDO. • Vendors will not be allowed to make any adjustments to any government-owned equipment or infrastructure, including tightening bolts, connecting cables to from the main power and /or communications terminal, and other use of hand tools. • Vendors will be allowed to make physical adjustments to any systems they own with NNSS supervision. • The use of cellular networks while on the test site will be limited. • Provide the number of required personnel participants and their function; limited to 2. All personnel proposed by a vendor will need to submit registration and visitor request forms. At most 2 personnel per system accepted can be on the NNSS site simultaneously. More than 2 personnel requests can be provided if vendors would like to switch one or both of the site personnel out over the course of the VDCE. 2.3 Invitation/Selection for participation DNDO will accept a limited number of commercial technologies for the VDCE. Depending on available space, non-commercial technologies may be allowed. Based on anticipated demand for VDCE participation, not all requests can be accommodated. DNDO reserves the right to limit VDCE participation and will prioritize acceptance based on the following criteria: Technology Diversity (e.g., PVT, NaI, HpGe) of Systems Single device for each vendor Maturity level of proposed system: Technology Readiness Level (TRL) (higher TRL level preferred, see below for definitions) Replay tool being supplied (Note: Replay tools are optional) Receipt date of VDCE completed participant request   Technology Readiness Level and Descriptions 1. Basic principles observed and reported.Lowest level of technology readiness. Scientific research begins to be translated into applied research and development. Examples might include paper studies of a technology's basic properties. 2. Technology concept and/or application formulated.Invention begins. Once basic principles are observed, practical applications can be invented. Applications are speculative and there may be no proof or detailed analysis to support the assumptions. Examples are limited to analytic studies. 3. Analytical and experimental critical function and/or characteristic proof of concept.Active research and development is initiated. This includes analytical studies and laboratory studies to physically validate analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or representative. 4. Component and/or breadboard validation in laboratory environment.Basic technological components are integrated to establish that they will work together. This is relatively "low fidelity" compared to the eventual system. Examples include integration of "ad hoc" hardware in the laboratory. 5. Component and/or breadboard validation in relevant environment.Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so it can be tested in a simulated environment. Examples include "high fidelity" laboratory integration of components. 6. System/subsystem model or prototype demonstration in a relevant environment.Representative model or prototype system, which is well beyond that of TRL 5, is tested in a relevant environment. Represents a major step up in a technology's demonstrated readiness. Examples include testing a prototype in a high-fidelity laboratory environment or in simulated operational environment. 7. System prototype demonstration in an operational environment.Prototype near, or at, planned operational system. Represents a major step up from TRL 6, requiring demonstration of an actual system prototype in an operational environment such as an aircraft, vehicle, or space. Examples include testing the prototype in a test bed aircraft. 8. Actual system completed and qualified through test and demonstration.Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples include developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications. 9. Actual system proven through successful mission operations.Actual application of the technology in its final form and under mission conditions, such as those encountered in operational test and evaluation. Examples include using the system under operational mission conditions. 3.SUBMISSION DIRECTIONS In order to facilitate vendor responses, the following attachments accompany this RFI: •Registration Form (Attachment 1) •Visitor Request Forms (Attachments 2 through 4) •Questionnaire (Attachment 5), and •Draft Bailment Agreement (Attachment 6) •Drawing of the mounting/bolt pattern (Attachment 7) Please return your fully completed registration form (Attachment 1), visitor request forms (Attachments 2 through 4), questionnaire (Attachment 5), and bailment agreement (Attachment 6) via email to Contract Specialist, Matthew Robertson at Matthew.Robertson@hq.dhs.gov, Contracting Officer, Tisha Blue at Tisha.Blue@hq.dhs.gov and to DNDORPMIndustryDay@hq.dhs.gov. Responses are due no later than Wednesday, February 3, 2016 at 12 pm Noon EST. An acknowledgement reply will be provided generally within 24 hours of receipt. Any questions regarding this RFI must be submitted by Wednesday, January 27, 2016 at 12 pm Noon EST via email to the Contract Specialist, Matthew Robertson at Matthew.Robertson@hq.dhs.gov, Contracting Officer, Tisha Blue at Tisha.Blue@hq.dhs.gov and to DNDORPMIndustryDay@hq.dhs.gov. All visitors to the NNSS site will need to read, understand and comply with procedures noted in the 2 documents below: 1)NNSS/Prohibited Articles, Electronic Devices Use 2)Real ID Implementation Guidance All proposed VDCE participants should provide a registration form(Attachment 1). US citizens need to read, comply and complete (Attachment 2). Visitor Request forms must be filled out by each person requesting access to the NNSS site. Even though the instructions on this form specify to return the completed form to NSTec badging, please do not do so. Instead, please return the completed form to Contract Specialist, Matthew Robertson at Matthew.Robertson@hq.dhs.gov, Contracting Officer, Tisha Blue at Tisha.Blue@hq.dhs.gov and to DNDORPMIndustryDay@hq.dhs.gov. Foreign Nationals, need to read, comply and complete (Attachment 3 through 4). Visitor Request forms must be filled by each foreign national requesting access to the NNSS site. Even though the instructions on these forms specify to return the completed form to Personnel Security, please do not do so. Instead, please return the completed forms to Contract Specialist, Matthew Robertson at Matthew.Robertson@hq.dhs.gov, Contracting Officer, Tisha Blue at Tisha.Blue@hq.dhs.gov and to DNDORPMIndustryDay@hq.dhs.gov. Attachment 4, IAP-66, page 1 only; the personal information on the foreign nationals. Please fill in your full name (if you do not have a middle name, indicate that as N/A), date of birth, place of birth, and current citizenship. Also, provide your employer information, including job title, current passport, and visa information (if applicable). Questionnaire (Attachment 5). This questionnaire should be completed and returned to assist in event planning. Bailment Agreement (Attachment 6). This Draft Bailment Agreement is for consideration and is included in this RFI for informational purposes only. Selected participants will be provided with the final Bailment Agreement for completion. The drawing of the mounting/bolt pattern (Attachment 7) that the vendor will be required to have their system mounted to during the event.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DHS/OCPO/DHS-OCPO/HSHQDC-16-RFIVDCEvent/listing.html)
- Record
- SN03998738-W 20160124/160122233855-514d723f097b097e4bb3242a2f77e512 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |