SPECIAL NOTICE
A -- Request for Information for Participation in Project Director, Counter Rocket, Artillery Mortar (C-RAM) conducted testing of Counter-Unmanned Aerial System (C-UAS) capability at Yuma Proving Ground (YPG)
- Notice Date
- 9/12/2016
- Notice Type
- Special Notice
- NAICS
- 541330
— Engineering Services
- Contracting Office
- Department of the Army, Army Contracting Command, ACC - NJ (W15QKN), BUILDING 10 PHIPPS RD, PICATINNY ARSENAL, New Jersey, 07806-5000, United States
- ZIP Code
- 07806-5000
- Solicitation Number
- W15QKN-16-Z-07K6
- Archive Date
- 10/7/2016
- Point of Contact
- Steven S. Ghazi, Phone: 9737248141
- E-Mail Address
-
steven.s.ghazi.civ@mail.mil
(steven.s.ghazi.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- Project Director (PD), C-RAM 1.0 Background. This special notice is being posted to the Federal Business Opportunities (FBO) website located at http://www.fbo.gov and the DoD Ordnance Technology Consortium (DOTC) portal located at http://www.nac-dotc.org. PD C-RAM has been tasked to develop a C-UAS capability in support of a validated JUON (0558). The requirements for this mission will include system testing of candidate technologies at YPG. Pursuant to this testing and selection of candidates systems to invite to this demonstration, PD C-RAM is requesting information on systems capabilities, attributes, and maturity. Submitted systems should be able to detect, track, classify or defeat a Group 1 or 2 UAS. It is not necessary for a submitted system to perform functions of the entire kill chain. 1.1 This Request for Information (RFI) is issued for planning purposes only. The notice does not constitute a request for proposal and does not commit the Government to solicit or award a contract. Submission of a response to PD C-RAM does not guarantee inclusion in any demonstration or test events nor does it guarantee the system will be procured as a part of the deployed system architecture. 1.2 It is anticipated that the PD-CRAM will utilize the DoD Ordnance Technology Consortium (DOTC) Other Transaction Action (OTA) to potentially fund one or more projects for use in a multi-phase technology development and demonstration program in FY17. Interested parties within the U.S. technology base who are not members of the National Armaments Consortium (NAC), must join the consortium to respond to any future C-UAS solicitation that may be issued under the DOTC program. Interested parties should visit the NAC website, www.nac-dotc.org/How_to_Join.html for additional information. 1.3 It is anticipated that candidate systems that meet the minimum qualification will be asked to participate at a fully instrumented test at YPG in January 2017. Systems should be capable of performing in a System of Systems (SoS) architecture. At a minimum, systems shall operate without causing interference to other C-RAM Sense, Warn and Intercept as well as other Base Defense architecture elements. 1.4 Selected candidate systems shall provide an active interface to C-RAM SoS architecture for the purpose of providing system status, target detection/alert/track including target kinematic state, and general target classification as unknown, manned or unmanned. If the system does not have an active interface, candidates shall detail an engineering plan to create an interface. 1.5 All costs in responding to this RFI, participation in any testing, or any other portions of this effort will be the responsibility of the responding party unless explicitly stated by the Contracting Officer/Agreements Officer in writing. 1.6 Classified Information will be accepted. Please contact Government Point of Contact (POC) to discuss delivery options. 1.7 The government will protect all properly marked proprietary information from unauthorized disclosure. No proprietary information will be used to create requirements. 2.0 Interested parties should submit the following information: 2.1 Business name, address, webpage, CAGE code, Company POC and contact information. 2.2 System/subsystem description (to include any unique technology, components, subsystem elements, and/or architecture). Additionally, an Operational View 1 (OV-1) may be submitted. 2.3 Program, Product or System Security Classification Guide or Guidance used to develop necessary security measures related to documentation, storage and operation and maintenance of the system and system data, in lieu of a classification guide, classification guidelines used to protect critical system parameters or critical information related to the program/product/system/technology must be provided. 2.4 Information Exchange Requirements (IERs)/Interface Control Documents (ICDs), and/or information exchange capabilities already incorporated and/or readily available. 2.5 Any information on the level of autonomous operations in the system. 2.6 Description and documentation of past experiments, demonstrations and/or tests, to include performance results and reduced system level test data products. 2.7 Any type classifications or current materiel releases. 2.8 Existing contracts with government agencies, along with past performance information. 2.9 Measured performance against representative targets. Estimate of the capability limit (e.g., maximum effective range, weather impacts, and complex electromagnetic environment). Representative targets consist of Group 1 and 2 UAS in both fixed and rotary wing configurations. 2.10 Estimated time and cost to achieve Technology Readiness Level (TRL)-6 and TRL-8. 2.11 Estimated cost of a deployable system based on number of units procured, from single unit to bulk purchase. 2.11.1 Provide the Basis of Estimate background information. 2.12 Availability of full system sets. 2.12.1 Production timeline to deliver and quantity of systems based on the timeline. 2.13 Existing documentation 2.13.1 Operator manual. 2.13.2 Repair manual (operator through depot) 2.13.2.1 Assuming two level Army maintenance, only the 1st level is required for soldier documentation. 2.13.3 Installation manual. 2.13.4 Training documentation for both Forward Support Representatives and Operators. 2.14 If selected, the interested parties will be required to provide the Government sample system log file or recorded data from which an independent Government team can conduct system performance analysis and assessment. 2.15 Cybersecurity 2.15.1 Describe the methodology for ensuring Cybersecurity is incorporated into the system development life cycle that can meet the US Government's Federal Information Security Management Act (FISMA) and Risk Management Framework (RMF) of confidentiality, integrity, and availability requirements. 2.15.2 What is the proposed strategy for identifying cybersecurity risks, secure configuration, security patched software, and remediation/mitigation procedures by qualified cybersecurity personnel. Please provide POC for the candidate system cybersecurity program. 2.15.3 Describe the Operating System (OS) and software utilized on both the UAS and supporting setup/maintenance computers. What software validation measures have been completed to ensure vendor backdoors and vulnerabilities have been addressed in the source code? 2.15.4 Depict the system network boundary and network interfaces along with the Ports, Protocols, and Services (PPS) that this system utilizes for data transference. 2.15.5 Are data in transit and data at rest products implemented to provide additional layers of defense for CONUS and OCONUS operations? 2.15.6 Please provide any associated cybersecurity documentation as it applies to your system. 2.15.7 Provide a detailed plan to meet DoD Cybersecurity requirements to mitigate or remediate risks as they are identified on the system. 3.0 All interested responding parties should submit relevant information to Mr. Kirk Smith at kirk.m.smith.civ@mail.mil or MAJ Rustin Jessup at rustin.s.jessup.mil@mail.mil. 4.0 All systems will be subject to identical test protocols at YPG. 4.1 The test will be conducted in a classified environment at the Secret//REL US level. 4.2 Responding parties shall submit all data from their system to the Government on a daily basis. 4.3 The Government will provide truth data from approved sources on a daily basis. 4.4 The Government will protect responding parties' systems information with all reasonable safeguards. 4.5 All responding parties will sign a Non-Disclosure Agreement prior to attending the test and accessing any data from the range. 4.6 Any non-compliance with the above rules will result in immediate removal from the range and from the testing process and any extra costs will be borne by the responding party. 5.0 The Government reserves the right to consider systems in total or at the component level. 6.0 All inclusions to any testing at YPG must conform to safety regulations in effect at the time of testing. Any systems with novel methods of attack should consult with PD C-RAM to determine test requirement lead times and ability to fully test capability.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/4ba89432de8a5ab86a44dc017bc2d80b)
- Record
- SN04268164-W 20160914/160913000043-4ba89432de8a5ab86a44dc017bc2d80b (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 |