Airspace Mission Planning Division JMPS VO RFI.docx

28 AUGUST 2025

DAF PEO/C3MK 25-226

JOINT MISSION PLANNING SYSTEM (JMPS) SOLUTION TEAM

REQUEST FOR INFORMATION (RFI)

AIRSPACE MISSION PLANNING DIVISION

HANSCOM AFB, MA 01731

THIS NOTICE IS NOT A REQUEST FOR PROPOSAL.

THIS IS A RFI NOTICE ONLY.

This RFI is for informational and planning purposes only, and it does not constitute a Request for Proposal (RFP)/Fair Opportunity Proposal Request (FOPR) or a promise to issue an RFP/FOPR in the future. It is not to be construed as a commitment by the Government for any actual procurement of materials, machinery, or services. Respondents are advised that the Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI are solely at the responding parties' expense. White papers shall be UNCLASSIFIED and shall not contain any proprietary information or trade secrets. Any white papers containing restrictive markings will not be read by the Government. Any response submitted by respondents to this RFI constitutes consent for that submission to be reviewed by Government personnel, Federally Funded Research and Development Center employees, and Advisory & Assistance Services contractor employees supporting AFLCMC/C3BM employed by Leidos, Odyssey, and Astrion, unless the respondent clearly objects in writing to the release of this information to Federally Funded Research and Development Center employees, and Advisory and Assistance Services contractor employees supporting AFLCMC/C3BM.

Background

JMPS is a Windows-based common solution package for shared and platform-unique mission planning applications. It is the current Mission Planning Solution used by the HH-60W. JMPS currently uses the National Geospatial-Intelligence Agency’s (NGA) Vertical Obstruction (VO) data to provide information about vertical obstructions to mission planners. NGA is required to provide the following VO data:

a. > 50 ft in the immediate vicinity (1.5 nm radius) around airfields

b. > 150 ft in the 14 X 14 nm area around airfields

c. > 150 ft within Military Training Routes (MTR)

NGA provides some VOs under 150 ft outside the areas listed above, but there is no guarantee that all VOs under 150 ft outside these areas are contained in NGA’s VO data. Mission planners and/or HH-60W pilots need VO data with increased coverage to plan routes outside MTRs, outside of airfields, and/or within those areas while at low elevations.

Responses

Responses shall be in the form of a white paper that addresses two specific sections:

1. Administrative

2. Requested Information.

This white paper shall not exceed eight single-sided pages (not including Section 1), using 12-point font, and shall be UNCLASSIFED.

The anticipated North American Industry Classification System (NAICS) is 541511 – Custom Computer Programming Services. RFI respondents are encouraged to suggest different NACIS codes as they see applicable/relevant.

Interested potential sources should provide their responses to the Contracting Officer, Capt Chace Morris (Chace.morris.2@us.af.mil) and Contract Specialist Ms. April Febbi (april.febbi@us.af.mil).

This RFI will be cross posted to multiple Government Points of Entry (GPE). Vendors are not permitted to provide more than one response.

All questions about the RFI are due to the Contracting Officer and Contract Specialist on or before 12:00 PM Eastern Standard Time, Monday 08 September 2025. Answers will be posted to GPE not later than COB, Wednesday, 10 September 2025. RFI responses are due on or before 5:00 PM Eastern Standard Time, Wednesday, 17 September 2025.

1.0 ADMINISTRATIVE

Section 1 of the white paper shall provide administrative information (not included in the page count), and shall include the following as a minimum:

1. Name, mailing address, cage code, Unique Entity ID, phone number, fax number, and e-mail of designated point of contact.

2. Please list your business type (large business; small business; small, disadvantaged business; 8(a)-certified small, disadvantaged business; Historically Under-utilized Business Zone small business; woman-owned small business; very small business; veteran-owned small business; service-disabled veteran-owned small business).

3. Applicable contract vehicles your company has contracts with (GSA Multiple Award Schedule (MAS), Blanket Purchase Agreements (BPAs), Indefinite Delivery/Indefinite Quantity (ID/IQ) contracts, etc.) and include contract numbers.

4. Interest as a Prime or Subcontractor.

2.0 REQUESTED INFORMATION

Special Requirements:

1) The anticipated contract action requires all personnel assigned to be United States citizens and possess a minimum of a SECRET Security Clearance. Does your company meet this requirement? If not, please explain if and how you are working towards meeting this requirement.

2) The anticipated contractor shall comply with all appropriate provisions of the security regulations to include Department of Defense (DoD) National Industrial Security Program Operating Manual (DOD 5220.22-M) and cybersecurity certification as defined in DoD 8140.01, DoD 8570.01-M and AFMAN 17-1303. Can your company comply with the security regulations? Please explain.

VO Questions:

1) Does your company provide vertical obstruction data for obstacles below 150 feet? If yes, for what geographic regions can your company provide this data?

2) What is the source of the data your company provides?

3) What quality assurance processes does your company use when collecting and processing this data?

4) Does your company provide vertical obstruction data in Table Formatted Aeronautical Data-Obstacle (TFADS-O) format? If no, how could this feature be added to the data your company provides in the future? If your data is available in other formats, please describe.

5) Does the vertical obstruction data your company provides include cables (TFADS-L)? If yes, can you describe how cables are included?

6) How do users access the data your company provides? Is the data transferable from your service to a standalone computer?

7) Is a connection required to access your company’s data? If yes, will your software work in a standalone environment?

8) Can your software provide a confidence level of accuracy?

9) Are licenses required to access the vertical obstruction and line data your company provides? If yes, can you describe the licensing model your company uses?

10) Does your company have experience supplying vertical obstruction data to DoD customers? If yes, please describe.

11) Does the data your company provides contain any mechanisms to differentiate it from similar data in the same format but from a different source? If yes, please explain. If no, how could this feature be added to the data your company provides in the future?

12) If there was a use case for your data in an environment above unclassified, how would your company ensure that your data could be delivered and used in that environment?

13) How does your company protect the vertical obstruction data it produces?

14) How does your company vet the employees that have access to the vertical obstruction data your company produces?

15) Does your company use any open-source software in collecting and processing vertical obstruction data? If yes, how are cyber vulnerabilities in these tools tracked?

16) Is that data your company provides compatible with Open Mission Systems (OMS)? If yes, please explain. If no, how could the data your company provides work with OMS in the future?

//End of Questions//

5 | P a g e