SOURCES SOUGHT
10 -- RFI-SS AMDWS
- Notice Date
- 11/12/2015
- Notice Type
- Sources Sought
- NAICS
- 541330
— Engineering Services
- Contracting Office
- Department of the Army, Army Contracting Command, ACC - RSA - Missile, BLDG 5303 SPARKMAN CIR, Redstone Arsenal, Alabama, 35898-5090, United States
- ZIP Code
- 35898-5090
- Solicitation Number
- AMDWS-RFI-SS
- Archive Date
- 12/12/2015
- Point of Contact
- David F. Cobb, Phone: 256-876-5209, Felicia Dortch, Phone: 256-876-4964
- E-Mail Address
-
DAVID.F.COBB.CIV@MAIL.MIL, felicia.r.dortch.civ@mail.mil
(DAVID.F.COBB.CIV@MAIL.MIL, felicia.r.dortch.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- Description of Action THIS IS A REQUEST FOR INFORMATION ONLY. THERE IS NO SOLICITATION PACKAGE AVAILABLE. This Request for Information (RFI) is issued solely for information and planning purposes; it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. The Government will not pay for any information received in response to this request for information nor will the Government compensate the respondent for any cost incurred in developing the information for the Government. Any request for copies of solicitations will not be addressed since this is a request for information, not a request for proposal. Not responding to this RFI does not preclude participation in any future RFP. Any comments provided may or may not be included in a formal solicitation. The Government will not release any information marked with a proprietary legend received in response to this RFI to any firms, agencies or individuals outside the Government without written permission in accordance with the legend. Respondents may provide information on any currently available product or service that meets the Army's requirements. Format of Submissions/Point of Contact To be considered, responses to this RFI shall be submitted no later than 23 November, 2015 to: David F. Cobb and Felicia Dortch Building 5250 Martin Road Redstone Arsenal, AL 35898 Submissions or questions may also be sent electronically to: RFI responses are due 15 days after the release of this RFI. Responses can be emailed to Felicia Dortch at felicia.r.dortch.civ@mail.mil and David F. Cobb at david.cobb2.civ@mail.mil. A return email will be the indicator that your paper has been received. Responses will consist of an unclassified white paper on 8.5 x 11 inch paper, double spaced with fonts no smaller than 10 point, one inch margins, in a Microsoft Word or Adobe file format. Each page of the submission shall contain the document identifier in the document header. Respondents should ensure to label any information contained in the white paper considered to be proprietary. Data Requested The United States Army is conducting market research to identify currently available technological solutions and approaches in support of the Air and Missile Defense Workstation (AMDWS). AMDWS is the Force Operations (FO) component of the Air and Missile Defense Planning and Control System (AMDPCS) and the Air Defense Airspace Management (ADAM) Cell providing both planning and Situational Awareness of Air Defense assets. This notice is published in accordance with FAR Parts 10.002 and 15.201 and is a Request for Information (RFI) only in support of market research. All information received will be used for planning purposes only. This notice does not constitute Invitation for Bids, Request for Proposals, or Request for Quotes. The Government will not award a contract based on this notice and will not reimburse respondents for any cost associated with responses to it. PROBLEM STATEMENT: AMDWS is the Air Defense component for AMDPCS, ADAM Cell, and Army Mission Command (MC). AMDWS is also the gateway between the Air and Missile Defense (AMD) Force and the Maneuver Commander. Interoperability with MC, Joint and Multinational systems will be maintained and extended to enable collaborative planning and situational awareness through tactical graphics and staff element overlays. The U.S. Army will update AMDWS with regulatory changes required to maintain interoperability with the Air Operations Center (AOC) and the Command, Control, Battle Management and Communications (C2BMC). The AMDWS system will retrieve, fuse, and distribute this time-sensitive information to support operator inputs necessary for decision cycle dominance at all AMD Echelons. The AMDWS user interface will enable display of the near real time situation to allow the primary FO mission of monitoring the situation, assessing the situation, conducting planning, and directing and controlling forces to be performed easily. The fusion of the current Battlespace picture on AMDWS is an enabler as the primary Common Operating Picture (COP) within the ADAM Cell, AMDPCS, and Forward Operating Bases (FOBs). The AMDWS operates at SECRET classification level and requires compliance with the DOD Information Assurance Certification and Accreditation Program (DIACAP). The U.S. Army seeks to maintain the current AMDWS capability set as well as provide enhancements to meet emerging requirements. Any candidate solution must meet the following AMDWS capability set: 1) Disseminate integrated Air Picture sourced from Forward Area Air Defense (FAAD), Air Defense System Integrator (ADSI), Self-Reporters, and Blue Force Tracker (BFT) - A. This interface must be accomplished with no changes to the above systems. 2) Interface with various systems for Situational Awareness (SA) information exchange to include Mission Command (MC) Data Dissemination Service (DDS), Command Post of the Future (CPOF), Command Post Web. This interface must be accomplished with no changes to the above systems. 3) Facilitate airspace coordination among the Air Operations Center (AOC), Surface-to-Air Missile Operations Center (SAMOC), Tactical Airspace Integration System (TAIS), and Advanced Field Artillery Tactical Data System (AFATDS) using the Air Operations Community of Interest (AO COI) schema, United States Military Text Format (USMTF), and Allied Data Publication 3 (ADatP-3). This interface must be accomplished with no changes to the system/schema. 4) Conduct Defense Design planning with Command, Control, Battle Management & Communications (C2BMC), Patriot, and Terminal High Altitude Area Defense (THAAD). This interface must be accomplished with no changes to the weapon system. 5) Interface and exchange tactical data messages with Counter Rocket Artillery Mortar (C-RAM) Command and Control (C2) system to include receipt and dissemination of Rocket, Artillery, and Mortar (RAM) events to Mission Command systems. This interface must be accomplished with no changes to C-RAM C2 or Mission Command systems. 6) Support MIL-STD-3011 Joint Range Extension Applications Protocol (JREAP) B and C. 7) Provide automatic, optimized emplacement of Air Defense assets based on: • Sensor and Weapon Models • Launch and Defended Area Analysis • Terrain, Urban Features, and Weather Impacts • Communication Node Coverage 8) Optimize C-RAM weapon emplacement utilizing high fidelity models for accurate prediction of RAM intercepts. 9) Interface with Army Field Artillery (FA) automated systems using native Variable Message Format (VMF) messages in support of the automatic and computer assisted counter battery missions for Rocket, Artillery, and Mortar (RAM) event threats. This interface must be accomplished with no changes to the FA systems. 10) Disseminate RAM Point of Origin / Point of Impact (POO / POI) to Mission Command systems to include warnings to localized edge nodes. This interface must be accomplished with no changes to Mission Command systems. 11) Support Link 11B communication. 12) Provide alerts based on track and volume conflict detection. 13) Provide route planning and maneuverability analysis for planned assets. 14) Provide unique information based on the operator's profile and tactical environment. 15) Maintain backwards compatibility with the currently fielded Army Common Operating Environment (COE)/software blocking baselines. This must be accomplished with no changes to the fielded systems. 16) Must be completely interoperable with currently fielded AMDWS baselines to include near real-time exchange of air and space tracks, RAM tracks, defense designs, mission plans, track management, and battle management data. This must be accomplished with no changes to the fielded systems. 17) Must create and maintain task organization and configuration of nodes on the network. 18) Provide 3D map visualization of Air Defense planning assets and related Situational Awareness information to include: units, sensors, weapons, communication nodes, control measures, air breather tracks, ground tracks, tactical ballistic missiles, and RAM events. 19) Support tactical graphics in accordance with MIL-STD-2525 (B and C) and MIL-STD-1477C. 20) Provide support for network operations with North Atlantic Treaty Alliance (NATO) C2 systems. 21) Provide Fire Mission management functions to include initiation of a Call for Fire (CFF) and the ability to refine targets via Cursor on Target (CoT), Check-Fire, and End Mission. 22) Process geospatial map products to include: Digital Terrain Elevation Data (DTED), Compressed ARC Digitized Raster Graphics (CADRG), Controlled Image Base (CIB), Vector Product Format (VPF), Urban Feature Data (UFD), and National Imagery Transmission Format (NITF). 23) Support Cursor-on-Target (CoT) interface to friendly UAS Ground Control Station (GCS). This interface must be accomplished with no changes to the GCS. 24) Provide ability to play back historical air picture information. 25) Support Air track reception requirements as defined in the MIL-STD-6016. 26) Support Air track reception requirements as defined in the IBSS and IBSI specifications. 27) Support the merge of multiple air track data feeds. 28) Provide air track information associated with the Air Tasking Order (ATO). 29) Support forensic data logging and after-action reports. 30) Provide an interface to exchange SA with Force Protection systems including Joint Tactical Ground Station (JTAGS) and Tactical Automated Security System (TASS). This interface must be accomplished with no changes to the external systems. 31) Disseminate air strike warnings and Call for Fire (CFF) in response to aerial threats. 32) Must be a Technology Readiness Level 9 (TRL 9) system that has been government tested and accepted. 33) Capable of providing continuous onsite support at various government test facilities for the purpose of product certification testing. 34) Support software installation in both standalone and client-server configurations. 35) Support deployment of Air Defense services in a virtual server environment. 36) Support integration into the objective Integrated Air and Missile Defense Battle Command System (IBCS) architecture for exchange of critical SA and Defense Design information. This must be accomplished with no changes to the IBCS architecture. 37) Must provide a Government-validated training/logistics package. 38) Must provide client software supportive of a Common Warfighting Machine Interface (CWMI) capable of providing a common look and feel and shared components. 39) Must have the capability to obtain a current Authority to Operate (ATO) and provide evidence of maintaining a current Information Assurance (IA) program. The candidate must be able to support all technical, operational, safety, interoperability, security testing, and be able to provide the requisite training support. 40) Simultaneously support a both FO and SA mission roles to include near real-time Air Defense and Planning Operations. 41) Possess expertise and experience in working with international countries. Must possess product-specific expertise and domain experience to accomplish Foreign Military Sales (FMS) tasks within stringent time constraints. 42) Must run on existing hardware (ADAM servers and General Dynamics Topaz, Hewlett Packard Z-Book, and/or Miltope laptops). 43) Support forensic data logging and after-action reports. Instructions for Market Survey Response The AMDWS market research will be conducted via white paper submissions: The Government will not reimburse respondents for any costs associated with responses to this notice. Respondents may submit question to the Contracting Officer and Contract Specialist by email to david.cobb2.civ@mail.mil and felicia.r.dortch.civ@mail.mil by 23 November 2015. All white papers must be received by the Government Contracting Officer and Contract Specialist electronically through email at david.cobb2.civ@mail.mil and felicia.r.dortch.civ@mail.mil (same as above) NLT 1600hrs CST on 23 November 2015. Responses will consist of an unclassified white paper on 8.5 x 11 inch paper, double spaced with fonts no smaller than 10 point, one inch margins, in a Microsoft Word or Adobe file format. Each page of the submission shall contain the document identifier in the document header. Respondents should ensure to label any information contained in the white paper considered to be proprietary. At a minimum, the white paper shall provide a description of the technical approach and a statement on how the technical capabilities meet these key attributes: 1.) AMDWS capabilities as defined above 2.) Operational effectiveness 3.) Integration: Ability of the software to integrate with key Army Mission Command Systems 4.) Software only; supportable on existing fielded/planned server/client architecture 5.) Sustainable with theater assets (training, software maintenance) 6.) Affordability: The estimated system costs for budgeting purposes. System costs must be both reasonable and achievable. The baseline for requested solutions is "just good enough." Responses should clearly identify and summarize all previous testing of either individual components of their proposed system of systems, or of the integrated system of systems, by either US Government agencies or other test agencies. Responses should discuss types, extent, depth and breadth of analysis and data to substantiate performance and containment claims. Responses should also describe the firm's capability and experience in providing tactical systems in this mission area. The white paper will contain NO more than 25 total pages including tables, charts, and figures. The white paper will include a technical POC, phone number and email.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/905d4800300edce808dfbbc1f0b11726)
- Place of Performance
- Address: Redstone Arsenal, Alabama, 35898, United States
- Zip Code: 35898
- Zip Code: 35898
- Record
- SN03944422-W 20151114/151112234315-905d4800300edce808dfbbc1f0b11726 (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 |