Inactive

1. Description Request for Information (RFI) Only. This RFI is issued solely for information and planning purposes-it does not constitute as a Request for Proposal (RFP) or a promise to issue an RFP i... 1. Description Request for Information (RFI) Only. This RFI is issued solely for information and planning purposes-it does not constitute as 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 Government is not at this time seeking proposals and will not accept unsolicited proposals. The RFI responders 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 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. Section 2 of this request provides context to the information requested in Section 3. 2. Background This background provides an overview of the Air Force Positioning, Navigation and Timing (AF PNT) need and how this need is driving the various facets of the lifecycle to create resilient AF PNT through the R-EGI program. 2. 1 R-EGI Program Background 2.1.1 The Need The 2018 National Defense Strategy charged the Department of Defense (DoD) to Reform the Department for Greater Performance and Reliability. This strategy included the need to accelerate planned upgrades; build robustness and resiliency into existing capabilities; and to integrate new processes/capabilities into current/future Positioning Navigation and Timing (PNT) solutions. Applying this direction, the 2019 U.S. Air Force (USAF) PNT Strategic Plan established a priority to “Provide robust and resilient PNT materiel solutions to the warfighter”. A key tenet to the capability delivery is to shorten acquisition timelines to facilitate the fielding of adaptable, cost-effective materiel solutions. R-EGI is the near-term materiel solution, planning to head into production with a competitive contract award(s) projected in FY2024. For manned and unmanned airborne platforms, the majority of PNT capability is implemented by coupling GPS with an Inertial Navigation System (INS). Before GPS, INS equipment had been coupled/aided using various PNT aiding sources using a federated architecture. This federated architecture had allowed some level of resilience and robustness of PNT sources. However, as GPS receiver technology was miniaturized, it has been embedded into the INS forming a non-federated, tightly coupled Embedded GPS/INS (EGI). Size Weight and Power efficiencies have been gained by embedding GPS in the INS, but much of the resilience found in the older federated systems has been lost. This loss of resilience, coupled with adversaries understanding of the US’s high dependence on GPS, has led to concerns of the impacts as GPS vulnerabilities are exploited. To overcome these concerns, R-EGI aims to modernize and enhance PNT robustness and resiliency by architecting and designing our EGI’s as a System-of-Systems aligned with AF Enterprise PNT capability development efforts creating a Resilient-EGI (R-EGI). This need is formalized in the DoD PNT Strategy (08/2019): “While GPS will remain the cornerstone PNT capability for the DoD, complementary PNT capabilities must be applied as well using a modular open-system approach to ensure timeliness and affordability in implementation and resiliency in effects.” R-EGI provides the efficiencies and performance of a tightly-coupled EGI, and R-EGI’s System-of-Systems architecture allows for the efficient integration of complementary and alternative PNT capabilities as was achievable in pre-GPS federated PNT systems. R-EGI also enables the integration of current Robust spaced-based PNT capabilities such as advanced digital anti-jam antennas and M-Code receivers with Regional Military Protect (RMP); and also enables integration of future space-based PNT capabilities being developed in the Navigation Technology Satellite-3 (NTS-3) program. 2.1.2 R-EGI Development Approach The first R-EGI systems are being develop for and integrated into post-block F-16s. To expedite development, integration and fielding of R-EGI, a different acquisition and lifecycle strategy and approach has been adopted to meet the identified urgent needs. Creating the development environment, having ownership of the LRU design (key interfaces, key technical data, software architecture), and working with platforms to maximize the effectiveness of integration are fundamental tenets to enable R-EGI to be resilient. To optimize agility and responsiveness in an ever-changing threat environment, the AF must own and manage the design of R-EGI and will continuously develop and field enhanced PNT capabilities as an enterprise to address new threats or platform needs. Executing under a Middle Tier of Acquisition (MTA) authority for Rapid Prototyping, R-EGI has been developing under the guidance of a Design Agent (DA) – Integrated Solutions for Systems (IS4S) – since 2019. The prototyping authority has covered two phases of development: Proof of Concept demonstrating the ability of a R-EGI to function under an OSA/GRA and Prototype Development which is still underway. The outcome of Prototype Development will be Production-Representative Prototypes to support verification of the design and its representation in a Level (3) Technical Data Package (TDP). The verified Level (3) Technical Data Package generated from this development effort provides the basis for competitive production of the R-EGI LRU. It is anticipated that one or multiple awards will be made for the manufacturing of the R-EGI LRU with product support aspects that are outlined in section 2.4.2. (Image can be seen in attached pdf version) 2.2 R-EGI Program Office The R-EGI Program Office is managing the R-EGI Technical Baseline (where Technical Baseline is defined in https://acqnotes.com/acqnote/careerfields/technical-baseline and includes the requirements model, sysML model, key interface IP, etc.) following initial development. The R-EGI Program Office is also managing the production of R-EGI based on the R-EGI design and partnering with platforms program offices for aircraft integration. The Technical Baseline will be managed by the AF organically and through Technical Baseline maintenance contracts. Storage and configuration management of the Technical Baseline is in the AF Enterprise Product Lifecycle Management (PLM) system. Development and integration of software capability will be driven from the PLM hosted Technical Baseline and managed by AF Software Maintenance Organizations. Development of software capabilities based on the Technical Baseline will be either performed organically in the R-EGI virtual Systems Integration Laboratory (vSIL) and/or through contracted efforts. These PLM and vSIL environments are/will be cloud-hosted. The development environment for both additional platform integration and technology insertion will be handled separate from the manufacturing effort- likely through separate contracts. The manufacturing of the R-EGI LRU will be executed on a contract type to be determined. R-EGI manufacturers are anticipated to build the LRU based on the Level (3) Technical Data Package. It is anticipated that R-EGI manufacturers will operate within the Digital Environment of R-EGI to include inputs to the vSIL (e.g. change requests) and Product Lifecycle Management (PLM) systems for life-cycle logistics. Product support elements are outlined below. 2.3 Platforms Supported The post-block F-16 is the lead platform for the R-EGI effort, with the design of the LRU influenced by the platform requirements. The production of the R-EGI LRU is to support the F-16 fielding of R-EGI on the post-block fleet. However, R-EGI is not a platform unique solution. The PNT Program Office anticipates additional platforms turning towards R-EGI upgrades to provide PNT resiliency and M-Code GPS solutions as outlined in the strategies listed above. The coordination between additional platforms and the PNT Program Office is currently underway, but it is anticipated that these platforms will drive additional production runs supporting their respective fleet implementation strategies. 2.4 Key Production / Product Support Elements 2.4.1 Key Characteristics of R-EGI LRU Functions and Architecture R-EGI provides PNT state data to platforms to support safety critical functions (e.g., outer-loop loop flight control; positioning and/or guidance for Communication Navigation Surveillance / Air Traffic Management (CNS/ATM) operations; platform attitude information; associated indicators and warnings; and more.) R-EGI must be designed and manufactured with system safety and design assurance to support these safety critical functions as appropriate for platform airworthiness. R-EGI also provides PNT state data to support mission critical weapons and mission systems. To support both safety and mission critical systems and be resilient- R-EGI is designed with a partitioned architecture to host these capabilities as appropriate. In addition, to enable development of AF enterprise-wide PNT capabilities, the R-EGI LRU architecture also includes partitioning between core PNT functions and interfaces and platform-specific functions and interfaces. 2.4.2 Product Support Strategy Through the 12 Integrated Product Support Elements (IPSEs), the product support strategy for R-EGI is to enable an agile adaptation and integration to a rapidly evolving hostile environment. It is a priority to minimize all sustainment costs and the overall logistics footprint without sacrificing warfighter readiness and capabilities. With the delivery of a Level (2) and Level (3) TDP, The R-EGI Program Office (PO) will maintain Operational Safety Suitability and Effectiveness (OSS&E) authority to support the mitigation of obsolescence and to maintain configuration control of the LRU. The delivery of the Level (2) and Level (3) TDPs will enable the Air Force to activate organic maintenance for the R-EGI LRU as well as manufacture and produce the LRU at the best cost to the DoD. The Maintenance Concept for R-EGI is in work and is expected to include three levels of maintenance: Operational, Intermediate, and Depot maintenance. R-EGI will be procured/integrated on multiple DOD platforms in later Spirals. It is anticipated that the depot workload will be a 70/30 split between Organic and Contractor Logistics Support (CLS). For any possible proprietary conditions then a Public-Private Partnership (PPP) will be considered for Organic Depot Maintenance. During the current prototyping effort, a Level of Repair Analysis (LORA) will be completed by the DA to help inform an Economic Analysis. An Initial Source of Repair Assignment (SORA) and Core Logistics Analysis (CLA) has been completed; dictating that Robins AFB will be the Organic depot for all hardware (HW), software (SW) and SW Crypto. The Depot Source of Repair (DSOR) is currently in the Depot Maintenance Interservice (DMI) phase. The Air Force is projected to be the Primary Inventory Control Activity (PICA) for all supply chain management (SCM) via the 407th SCMS at Robins. Also, The R-EGI LRU expects to be unclassified when keyed. For Production, a 2-year Interim Contractor Support (ICS) will be needed for Initial Fielding while the product support package is being deployed. ICS shall include on-site support, warranty support, depot maintenance of parts needing repair and will include all spare parts, repair parts, tools, test sets and any other support or test equipment need for O/I/D levels of maintenance. ICS will also include initial Provisioning/Cataloging and Tech Order development/management. 3. Requested Information This section details information of specific interest to the AF to help inform various aspects of planning R-EGI manufacturing and other lifecycle considerations. Given the breadth of the questions, it may not be appropriate for respondents to provide information to all questions outlined below. In addition, other relevant considerations not captured in the questions below are welcome as described in Section 3.4. 3.1 Level (2) Technical Data Package (TDP) for Manufacturing The following questions are oriented towards feedback on the Level (2) Technical Data Package, with the goal to help the Program Office refine the TDP and ensure a sufficient Level (3) TDP is provided for the Production RFP. Interested parties must request the Level (2) TDP from the Contracting Officer (Mr. Todd Rissmiller). The Level (2) TDP will be furnished upon verification of ability to receive/store ITAR data. Provide an assessment of the vendor’s ability and capability to manufacture a R-EGI LRU in accordance with Government provided Level (3) TDP. Given the current Level 2 draft TDP technical data (available upon request), requirements, and system model, are there: any specific issues you would anticipate for manufacturing? changes to the architecture & design that would: improve manufacturability or enhance the ability to produce the R-EGI LRU? improve ability to integrate key technologies from other sources? As applicable, discuss experience manufacturing a product from a third party or government provided TDP. What initiatives have you implemented in the past to successfully minimize production timelines? Please provide results of these actions. Provide insight into the vendor’s and production line startup. (i.e. time to stand up production line and time for tool change on average) Are there considerations that could be provided that might decrease these timelines including considerations on the acquisition approach. What type of mitigation strategies could be implemented to reduce long lead item impacts to production, especially given the recent supply chain issues? Provide an understanding of like products that the company may be currently producing or have produced in the past; Include description of any challenges encountered, as well as mitigation efforts implemented and results. Include a short description on any capital equipment relevant to manufacturing of R-EGI support, e.g. environmental test, configuration management tools, etc. physical elements software tools Describe your ability and experience in Model Based Systems Engineering tools in support of manufacturing based change requests into the Government-owned technical baseline. 3.2 Interest in Manufacturing Support The following questions pertain to the vendor's interest in providing the manufacture and product support of the R-EGI LRU. Discuss your company’s core technical focus areas, as well as your approach to obtaining technical capabilities needed to address manufacturing and sustainment. Describe current industrial/engineering/software certifications or those expected in the next year. Describe your current security classification (facilities and personnel) and resources available to perform manufacturing support of acceptance testing (i.e. crypto load support) acceptance testing may require some level of testing that requires people and facilities that are able to support at a classified level/crypto support Provide a short description of your facilities both current and planned. The Government is interested in any lessons learned regarding reducing delivery/task order award cycle time and resources. Describe any other relevant topics, concerns, and information that will help the Government in developing an acquisition strategy to meet the objectives of R-EGI described in section 2. 3.3 Logistics and Sustainment Elements The following questions pertain to the logistics and sustainment elements of R-EGI. Provide an understanding of the vendor’s, manufacturing methodology (i.e. Push, Pull, Work In Progress (WIP) philosophy); how does the government’s approach of providing the Level (3) TDP affect your manufacturing methodology Likelihood to entering a Public-Private Partnership (PPP) with Government If relevant, provide information on previous participation in a PPP including any positives/negatives/challenges you would anticipate or have experienced Provide insight into the following question: As a manufacturing company, is it typical for your company to also provide Interim Contract Support (ICS) until initial Fielding? (i.e. provisioning/cataloging, Tech Writers for TOs, Maintenance Support (Repair Turnaround Time), MILSPEC Authority) As a potential manufacturer of R-EGI, are you willing/could you or are you able to also provide ICS? If yes, please summarize your experience What are the teaming arrangements you anticipate in executing the combined production/ICS scope? Describe your company’s property accountability program and/or systems. Does your company have an APSR (Approved Property System of Record)? 3.4 Additional Information Additional relevant information industry would like to provide with respect to the AF development and lifecycle plans to build a resilient PNT capability through the R-EGI program are welcome. 4. Responses NOTE: If applicable, RFI responders should indicate any proprietary restrictions associated with their solutions. Responses to the RFI must be provided by interested parties through briefings or reports within 30 days of this RFI’s release. The Government will review all submissions. Depending on the quality and comprehensive nature of the responses, parties may be invited to present their strategies and capabilities during an Industry Day event. If the event occurs, it will take place in the Summer of 2022 at a location to be determined (note: employing VTC/sVTC capabilities are possible options). Such a scenario, each RFI responder must be cleared or could obtain clearance at the SECRET level, as a minimum. The classification of the briefings (physical, electronic, and verbal) must not extend beyond SECRET. Each RFI responder will be provided separate two-hour time periods to discuss their proposed solution(s) with a panel of DoD key stakeholders representing research laboratories, aircraft and weapon system program offices, and engineering directorates. THERE IS NO SOLICITATION AT THIS TIME. Contractors/Institutions responding to this market research are hereby notified that participation in this survey is voluntary and may not ensure participation in future solicitations or contract awards. The Government will not reimburse participants for any expenses associated with their participation in this survey. Not responding to this RFI does not preclude participation in any future solicitation, if any is issued. 5. Summary Parties interested in responding to the RFI or soliciting further information regarding the R-EGI Level (2) TDP, please contact Mr. Todd Rissmiller.