Engine Government Reference Architecture (eGRA) RFI

Engine Government Reference Architecture (eGRA)

Request for Information

1. Introduction
   
   
   
   
   1. 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.
   
   
   2. 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.
   
   
   3. 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:
      
      
      
      1. To provide a standardized, consistent means to convey government requirements and receive vendor responses and data
      
      
      2. To provide a tool for management of the propulsion system at appropriate levels of detail for effective sustainment across the lifecycle
      
      
      3. To complement concurrent work on the Interface Government Reference Architecture (iGRA)
      
      
      
      
   
   
   4. 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.
   
   
   5. The scope of this RFI therefore includes:
      
      
      
      1. Access to eGRA Release 2, as well as the Digital Engineering Style Guide (DESG).
      
      
      2. Options to provide feedback including, but not limited to
         
         
         
         1. Responding to the prepared questions in section 2
         
         
         2. Participation in the eGRA workshop at the Turbine Engine Technology Symposium (TETS) 2026
         
         
         3. One-on-one engagement during TETS 2026, or as otherwise coordinated
         
         
         
         
      
      
      
      
   
   
   
   


2. Requested Information
   
   
   
   1. 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).
      
      
      
      1. The eGRA model was developed using Cameo Enterprise Architecture 2024x [UAF 1.2] Refresh3
      
      
      2. The eGRA and DESG are Controlled Unclassified Information (CUI). To receive this information, respondents will require the following:
         
         
         
         1. Active contracts with the USAF
         
         
         2. Appropriate systems for storing and processing CUI information
         
         
         
         
      
      
      3. 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.
      
      
      
      
   
   
   2. Respondents should address one or more of the following questions for feedback:
      
      
      
      1. 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?
      
      
      2. 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 your requirements?
      
      
      3. Describe potential approaches and challenges associated with incorporating your standard work into a model that the government will have access to throughout the program lifecycle.
      
      
      4. Describe how you envision the eGRA structure, content, and format informing and streamlining future Requests for Proposal.
      
      
      5. Describe any other issues or recommendations for continued development of the eGRA to ensure it can be a useful tool in the propulsion system acquisition and sustainment process.
      
      
      
      
   
   
   
   


3. Responses
   
   
   
   1. Interested parties are requested to respond to this RFI with one or both of the following:
      
      
      
      1. A white paper, not to exceed 10 pages using 12-point Times New Roman font. Any supporting technical data and digital artifacts provided will not count against this page limit.
      
      
      2. A 30-minute in-person oral presentation at the upcoming Turbine Engine Technology Symposium (TETS). Sessions are tentatively being scheduled for Thursday 3 September.
      
      
      
      
   
   
   2. Initial responses or coordination shall be accomplished no later than 24 August 2026, 1700 Eastern Time. Unclassified responses shall be submitted via secure email or secure website to the technical POC and the contracting officer.
   
   
   3. Responses should be marked, if applicable, with appropriate controlled unclassified information (CUI) caveats, to include any ITAR restrictions.
   
   
   4. Responses should NOT include marketing information, commercial documentation, or product literature.
   
   
   5. Proprietary information, if any, MUST BE CLEARLY MARKED. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Please be advised that all submissions become Government property and will not be returned. All information received in response to this RFI that is properly marked as “proprietary” will be handled accordingly.
   
   
   6. Respondents are advised that employees under contract with the Government will be used to process submissions and provide technical support to the eGRA project team. All members of the team will be reminded of their obligation to protect such information to the maximum extent permitted or required by the Economic Espionage Act, 18 U.S.C. 1831 et seq., and other applicable statutes or regulations. In addition, Government members will be reminded of their obligations to afford protection under the Trade Secrets Act, 18 U.S.C. 1905. All contractor members are required to protect the information by the terms of their contracts. These support contracts include non-disclosure agreements (NDA) prohibiting contractor employees from disclosing any information submitted by other contractors or using such information for any purpose other than that for which it was furnished.
   
   
   
   


4. Questions and Industry Discussion
   
   
   
   1. Questions regarding this announcement shall be submitted in writing via email to the technical POCs and the contracting officer.
   
   
   2. Broad discussion on the eGRA, iGRA, and the Propulsion Directorate’s Digital Materiel Management Strategy will occur at TETS 2026. An eGRA workshop is scheduled for Thursday, 3 September; opportunities for one-on-one discussions will also be available and shall be coordinated with the technical POCs and the contracting officer.