Engine Government Reference Architecture (eGRA) RFI

Engine Government Reference Architecture (eGRA) Request for Information Introduction THIS IS A REQUEST FOR INFORMATION ONLY to understand industry approaches to propulsion system architecting and how best to evolve the government’s existing toolset to complement those approaches in current and future development. 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 RFI does not commit the U.S. Government to contract for any supply or service. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI. Use of Reference Architectures has long been an established best practice in Systems Engineering. In its revised Guidebook on Implementing Modular Open Systems Architectures in Weapon Systems[1], Air Force Materiel Command (AFMC) recommends a broad range of systems engineering principles, including Reference Architectures, as key to developing and acquiring our increasingly complex systems-of-systems and families of systems. The Propulsion Acquisition Division of the Air Force Lifecycle Management Center (AFLCMC/LPA) is implementing Government Reference Architectures (GRAs) as a component of its broader strategy to drive Digital Materiel Management (DMM) across the propulsion enterprise. The Engine Government Reference Architecture (eGRA) is a key product of that strategy currently in active development. The objectives of the eGRA are: To provide a standardized, consistent means to convey government requirements and receive vendor responses and data To provide a tool for management of the propulsion system at appropriate levels of detail for effective sustainment across the lifecycle To complement concurrent work on the Interface Government Reference Architecture (iGRA) The eGRA project team is currently seeking to provide industry access to its first eGRA Minimum Viable Product (MVP), “Release 2,” and to obtain feedback from prospective users. This early feedback is crucial to ensure the eGRA can be developed into a tool that adds definitive value to both government and industry users throughout the full range of propulsion acquisition efforts. The scope of this RFI therefore includes: Access to eGRA Release 2, as well as the Digital Engineering Style Guide (DESG). Options to provide feedback including, but not limited to Responding to the prepared questions in section 2 Participation in the eGRA workshop at the Turbine Engine Technology Symposium (TETS) 2026 One-on-one engagement during TETS 2026, or as otherwise coordinated Requested Information Respondents should contact the technical POCs, Maj Andrew Cottle (andrew.cottle.1@us.af.mil) and Mr. Jed Cox (john.cox.17@us.af.mil), and the contracting officer, Capt Dustin Herridge (dustin.herridge@us.af.mil) and include your CAGE code for access to eGRA Release 2 (.mdzip file), introductory materials (.pptx), and the DESG (.pdf). The eGRA model was developed using Cameo Enterprise Architecture 2024x [UAF 1.2] Refresh3 The eGRA and DESG are Controlled Unclassified Information (CUI). To receive this information, respondents will require the following: Active contracts with the USAF Appropriate systems for storing and processing CUI information Note: Future releases of the eGRA are planned for broader dissemination. If respondents do not meet the conditions of 2.1.2, they may still express interest and obtain access in future releases. Respondents should address one or more of the following questions for feedback: Describe how you would incorporate the eGRA into your modeling practices. What aspects of the eGRA are complementary to your current practices and which are in conflict? How would you leverage a model-based approach such as the eGRA to link requirements to system architecture elements? What attributes of the eGRA would best enhance your processes for validating design satisfaction of yo...