RFI for GMTI Tracker_final_ 21_Jan_ 2020_updated.docx

DOCX document 42 KB Posted

Attached to
REQUEST FOR INFORMATION Federal contract opportunity
Solicitation number
FA8217-20-R-GMTI
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Hill Air Force Base

View the file

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

GMTI Solutions for CRC - Request for Information

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This 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. Further, the Air Force is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued.

Interested parties are requested to respond to this RFI with a white paper.

White papers in unprotected PDF format are due no later than 14 February 2020. Responses shall be limited to 10+5 pages (maximum of 10 pages of text/mixed content and up to 5 additional pages allowed for photos of or screenshots from similar or proposed solutions) for Section 2 and submitted via e-mail only to matthew.loffredo@us.af.mil and wendy.farley@us.af.mil. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. If any respondee does not currently have a Proprietary Data Protection Agreement (PDPA) that would permit the AFLCMC support contractors listed below to review and evaluate white papers submitted in response to this RFI, the respondee is requested to sign PDPAs with these AFLCMC support contractors for this purpose. A sample PDPA will be posted at https://e-commerce.spawar.navy.mil. (Click on Headquarters, then Market Surveys; then . . ..) The following is a list of Points of Contacts who will review the responses for completeness and disseminate the responses to the program office for review.

Matthew Loffredo 801-777-8666 matthew.loffredo@us.af.mil Wendy Farley 801-586-3464 wendy.farley@us.af.mil

Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum:

Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact.

Recommended contracting strategy.

Either 1) copies of executed non-disclosure agreements (NDAs) with the contractors supporting AFLCMC and AFLCMC supported PEOs and DRPMs in technical evaluations or 2) a statement that the respondee will not allow the Government to release its proprietary data to the Government support contractors. In the absence of either of the foregoing, the Government will assume that the respondee does NOT agree to the release of its submission to Government support contractors.

Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 541512, Computer Systems Design Services. If the respondee has a suggested NAICS code that they believe would be more suitable for this requirement, that NAICS code should be included in the white paper. “Small business concern” means a concern, including its affiliates that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121. A small business concern for the purposes of this procurement is generally defined as a business, including its affiliates, averaging no more than $27.5M million dollars in annual receipts. Annual receipts of a concern that has been in business for 3 or more complete fiscal years means the annual average gross revenue of the concern taken for the last 3 fiscal years. Annual receipts of a concern that has been in business for less than 3 complete fiscal years means its total receipts for the period it has been in business, divided by the number of weeks including fractions of a week that it has been in business, and multiplied by 52. Respondees are cautioned, however, that this is a general description only. Additional standards and conditions apply. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. The FAR is available at http://farsite.hill.af.mil

The facility security clearance of the offeror.

The number of pages in Section 1 of the white paper shall not be included in the 10+5-page limitation, i.e., the 10+5-page limitation applies only to Section 2 of the white paper.

Statement of Need:

The Air Force Life Cycle Management Center’s (AFLCMC) Aerospace Dominance Enabler Division (HBZ), through the Control and Reporting Center (CRC) Program Office, is seeking information on how industry could develop and implement Ground Moving Target Indicator (GMTI) solutions for the CRC. As the CRC modernizes and evolves to execute additional mission sets, the CRC needs the ability to ingest, manipulate, and disseminate GMTI data from various sensors and push Battle Management Command and Control (BMC2) information and taskings to various platforms and Command and Control (C2) nodes as necessary. AFLCMC/HBZ is requesting a Rough Order of Magnitude for Cost and Schedule for the development and source code, with unlimited data rights, of a prototype system in the FY2020/2021 timeframe, with an option for follow-on production of up to 20 additional systems. Provide a general description of any hardware and/or software requirements, production and sustainment actions to include two years of telephone support. The GMTI solutions considered must be compatible with the CRC AN/TYQ-23A Operations Module (OM) and the Multi Source Correlator Tracker (MSCT) software. Solutions shall be Open Mission System and Universal Command and Control Interface (OMS/UCI) compliant.

System Requirements

System Performance The CRC requires software upgrades to include a GMTI Tracker embedded capability to perform new core mission functions and to support future mission sets. These upgrades will allow increased functionality to support digitally sharing legacy/advanced sensor data, targeting data among tactical C2 and air/ground shooters, and GMTI data feeds. All OM systems will require these upgrades and modifications.

CRC and MTI Modes The system shall receive, store, process, display, correlate, fuse and forward surface data [GMTI, Synthetic Aperture Radar (SAR), Maritime Moving Target Indicator (MMTI), Inverse Synthetic Aperture Radar (ISAR), High Range Resolution (HRR) and Electronic Protection (EP)] from multiple sources IAW STANAG 4607:

- Receive, store, manually correlate and display GMTI, SAR

- Process GMTI

- Forward GMTI

- Receive, process, store, automatically correlate, fuse, and forward ISAR, HRR, and MMTI in addition to above stated threshold requirements

Manual Tracking Ability to initiate internal tracks on a data trail, with the option of the system picking up the data trail and beginning to automate tracking.

Support Future CRC and Global Hawk Block 40 (GH BLK40) capabilities The system shall automatically manage Multi-Platform Radar Insertion Program (MP-RTIP) modes based on operator selected parameters.

· The system shall transfer the last hour of sensor data (e.g., GMTI, MMTI, HRR) to that node assigned operational control of the GH BLK40 A/V.

· The system shall transfer the last hour of sensor data (e.g., GMTI, MMTI, HRR) to the oncoming GH BLK40 A/V via Common Data Link (CDL) in preparation for handover.

Intelligence, Surveillance, and Reconnaissance The system shall be capable of simultaneous management of correlation and data fusion with information to support surface target classification and identification. Selection, filtering, and modification of track displays must include:

- Display, track generation, correlation of GMTI ground data.

- Display and track generation and correlation of MMTI maritime tracks.

- The system shall receive, display, process, store, and prepare for transmission, Link 16 messages to support surface mission operations.

-The system shall allow operators to define a set of Link 16 messages for display and automatically prepare for Link 16 transmission based on user-defined criteria.

- Ability to filter GMTI based off of radar cross section, radial velocity and resolution.

Surface Tracking The system shall track moving surface targets in real time by kinematically associating Surface Moving Target Indicator (SMTI) detections, both for GMTI and MMTI.

- The GMTI Tracker will be 100% compatible and integrated with the Raytheon/Solipsys’ MSCT.

- The GMTI Tracker shall be OMS/UCI compliant.

Automated Tracking Ability for the system to analyze the ingested STANAG 4607 and identify coherent data trails, incoherent data trails and stationary/rotating data trails.

Automated Track Updates Ability for the system to update the track information based off updates from the STANAG 4607 data.

GMTI Colors Currently the color of all MTI can be changed, but the functionality will need to be expanded to incorporate the addition of STANAG 4607 and the various new MTI types.

· Ability to change the color of MTI/GMTI based on the radar resolution, radial velocity and radar service request it is originating from.

Track Reports Ability to run an end-of-mission report that includes all the track history and notes.

History Replay Exploitation tools shall allow the operator to switch between or simultaneously display real-time and historical playback data.

- History playback shall include single-frame step through, and operator-adjustable forward and reverse play rates (sliding history), set time gates, speed up and slow down history playback.

- Data for history playback shall include SMTI (i.e. GMTI and MMTI), tracks (i.e. ground tracks and maritime tracks), and video.

Logging and Replay The system shall support logging of any external data inputs (e.g. GMTI and MMTI) and provide for logged data to be replayed into the system. The replay function shall allow the operator to select reusing the data's original internal/timestamp time as well as provide for time-shifting the data to the current playback time.

Correlation, Fusion, and Identification The system surface tracking and fusion capability shall be able to receive data about moving targets from multiple data sources including the following:

- Sensors providing STANAG 4607 data

- Link 11 messages

- Link 16 messages

- SADL Messages

- VMF messages (i.e., Blue Force tracking data) (e.g., Precise Participant Location and Identification (PPLI), Plots, Tracks, Electronic Warfare Support Measures)

Open Mission System The system shall be OMS compliant in accordance with OMSC-VDD-001 (available by request).

Cybersecurity The system shall comply with applicable Risk Management Framework security requirements to include providing protection for Data at Rest. The system shall provide National Security Agency (NSA) approved encryption for Data at Rest and all mass storage shall be designed for daily removal. Portions of the system not so encrypted shall provide a Statement of Volatility certifying the system retains no sensitive data.

Safety Practices Accepted industry safety practices shall be employed to ensure the safety of personnel and system equipment.

The Following Sections are Optional in this RFI

Training One class shall be provided at each system delivery site consisting of the following:

Maintenance Training.

Training shall:

(a) Include a combination of classroom and on-equipment training of sufficient length to enable those personnel involved with supporting system testing, setup, and operators to perform proficiently.

(b) The delivered training products shall be adequate for knowledgeable personnel to build/conduct follow-on training.

(c) All training materials used shall be delivered, including instructor guides/notes.

(d) Copies of all materials used in presentation or handout form shall be delivered as electronic media.

Operator Training.

System operator training shall:

(a) Be provided to enable Generic Battle Control Systems (BCS) and CRC operators, Air Force Specialty Code (AFSC) 13B3 and 1C5X1, to have a full understanding of the Control functions of the GMTI Tracker and a general understanding of the operation of the system.

(b) Include a combination of classroom and on-equipment training of sufficient length to enable those personnel involved with supporting system testing, setup, and operations to perform proficiently.

(c) Include delivered training products which are adequate for knowledgeable personnel to build/conduct follow-on training.

(d) Ensure all training materials used are delivered, including instructor guides/notes.

(e) Copies of all materials used in presentation or handout form shall be delivered in electronic media.

Support and Logistics Integrated logistics support shall (a) be provided to satisfy the intent of the Generic BCS and CRC GMTI Tracker Product Support Management Plan (PSMP). This effort shall (b) be systematically planned, implemented, and managed by introducing elements of logistics to obtain maximum support readiness, availability, reliability, and optimum cost effectiveness.

Industry Discussions

AFLCMC representatives may or may not choose to meet with potential offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks.

Questions

Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Officer, matthew.loffredo@us.af.mil, and Contract Specialist, wendy.farley@us.af.mil. Verbal questions will NOT be accepted. Questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received after will be answered.

File details come from the government source that posted it. Updated .