02. Attachment A - Signature Managed Group 3 Technologies - RFI Response Template.xlsx
XLSX spreadsheet 44 KB Posted
- Solicitation number
- FA8629
About this file
This document is a Request for Information (RFI) from the Department of the Air Force Materiel Command Lifecycle Management Center (AFLCMC) for a Signature Managed (SM) Group 3 small Uncrewed Aircraft System (sUAS) capable of providing Command and Control/Data Relay (C2/DR) and Electronic Warfare (EW) capabilities within 24-36 months.
The RFI seeks responses for: 1) SM Group 3 sUAS currently integrated with a C2/DR or EW payload, 2) SM Group 3 sUAS ready to integrate a C2/DR or EW payload, and 3) C2/DR and EW payloads that are low Size, Weight, and Power and Cost (SWAP-C) and can be integrated onto the Group 3 SM sUAS. The RFI provides details on submission requirements, including the use of Attachment A (RFI Response Template) and optional Attachment B (Technology Synopsis). Responses are due by 1700 EST on January 17, 2025. The government may use the information gathered to inform acquisition strategies for initial and future capabilities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 01. SM RFI - SM C2 Node Extension.pdf | ||
| 06. RFI Questions Answers.xlsx | XLSX spreadsheet | |
| 03. Attachment B - Technology Synopsis.pdf | ||
| 05. Acronyms.docx | DOCX document | |
| 01. SM RFI - SM C2 Node - Signed.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Cover Sheet Offensive Small Uncrewed Aircraft Systems (sUAS) System Program Office (SPO) Group 3 sUAS, Air-Launchable Signature Managed Request for Information (RFI)
| Signature Managed (SM) Group 3 Technology RFI Response Template |
| Company: |
| Name of Primary Company Point of Contact (POC) |
| POC Email: |
| POC Phone Number: |
| Date of Submission: |
| INSTRUCTIONS |
| The Company information tab must be completed to ensure U.S. Government (USG) has necessary information on your company. |
| If your submission is for a: |
| PLATFORM ONLY: Complete the PLATFORM tab and disregard the PAYLOAD tab. |
| PAYLOAD ONLY: Complete the PAYLOAD tab and disregard the Platform tab. |
| PLATFORM WITH CURRENTLY INTEGRATED COMMAND AND CONTROL / DATA RELAY (C2/DR) OR ELECTRONIC WARFARE (EW )PAYLOAD: Complete both tabs, ensuring to capture the payload information on the PAYLOAD tab. |
Companies may submit more than one platform but are asked to use a separate file for each submission.
If you do not enter the required data for a particular attribute category, we will assume you do not have a solution that meets the specified attributes.
| RFI responses must be submitted to USAFOffensiveSmallUAS@groups.af.mil via encrypted email no later than 1700 EST on 01/17/2025 |
| If you do not have access to DoD SAFE or an encrypted email, please contact the Contracting Officer identified in the original posting for additional submission instructions. |
| As a reminder, this request is for the purpose of preliminary planning, not a Request for Proposal (RFP) or solicitation. |
| All costs associated with the RFI submissions will be solely at the expense of the respondent. Please reference the original posting for additional ground rules: |
Company Information
| GENERAL COMPANY INFORMATION | |||
| Provide answers to the below questions to the best of your ability | |||
| Question / Prompt | Response | ||
| DUNS Code | |||
| CAGE code | |||
| Socioeconomic Designation (if relevant) | |||
| Number of Employees | |||
| Current Corporate Headquarters Location | |||
| Are you able to meet to discuss classified information? | |||
| Do you have a dedicated, classified facility to conduct meetings? If so, to what classification level? | |||
| What regions/locations within the United States would you, or representatives from your company, be willing to travel to for discussions with USG representatives? | |||
| HISTORICAL REVENUE | |||
| Enter yearly revenue in whole dollars (e.g., $100,000 not $100K) from 2020 - 2024 and provide estimate of % of revenue from commercial vs DoD customers. Please ensure Columns D and E sum to 100% | |||
| Year | Revenue ($) | % commercial | % DoD |
| 2020 | |||
| 2021 | |||
| 2022 | |||
| 2023 | |||
| 2024 | |||
| GENERAL QUESTIONS | |||
| Question | Response | ||
| The Air Force plans to field an initial Signature Managed C2/DR and Signature Managed EW capability in 24-36 months. Please provide any commentary on the feasibility of that timeline and your ability to meet the Air Force's goal. | |||
| Please describe any potential Organizational Conflict of Interest (OCI) concerns relative to this requirement and strategy. | |||
| How have you mitigated Organizational Conflicts of Interest in the past? | |||
| Does the contractor use Model Based Systems Engineering (MBSE), specifically maintaining program-specific systems engineering models using System Modeling Language (SysML)? | |||
| If yes to the above question, would the contractor be willing to submit the model to the USG for review? | |||
| OPTIONAL QUESTIONS | |||
| The below questions are optional. Please feel free to answer any or all of the below questions | |||
| Question | Response | ||
| Regarding the high-level summary of the opportunity presented in this RFI, are there any requirements or topics where you anticipate additional clarity is necessary for an RFP? If so, what clarifications might be helpful? | |||
| What, if any, teaming arrangements or partnerships do you envision to be necessary to successfully deliver this requirement? | |||
| How might the USG maximize participation of non-traditional and small business vendors in a future procurement? | |||
| Based on your experience and the information contained in the RFI, what existing contract vehicles or strategic sources can support this requirement? |
PLATFORM
| Respondents are reminded that this RFI is intended for higher Technical Readiness Level (TRL) solutions and unless specified, questions are asking about the platform in it's current state, not the assumed final state once development is complete. The synposis (Attachment B) provides the opportunity to discuss planned development of the current platform. | |
| RESPONSE | |
| GENERAL INFORMATION | |
| Platform Name | |
| Current Technical Readiness Level (TRL) of your solution | |
| Current Manufacturing Readiness Level (MRL) of your solution | |
| Current Production Quantity (units per month) | |
| Planned Monthly Production Capability starting FY26 (October 2025) | |
| Planned Monthly Production Capability starting FY27 (October 2026) | |
| COST | |
| PRODUCTION COST - AVERAGE PRODUCTION UNIT COST (USG) | |
| 1-10 | |
| 11-50 | |
| 51-300 | |
| 301+ | |
| What is your methodology for deriving this unit cost? (e.g., experience curve, commonality with related systems, etc.) | |
| DEVELOPMENT COST | |
| NRE Costs through LRIP | |
| What is your methodology for deriving this unit cost? (e.g., experience curve, commonality with related systems, etc.) | |
| SUSTAINMENT COST PER UNIT (USD) | |
| Annual cost per unit | |
| What is your methodology for deriving this sustainment cost? | |
| What is the expected rate of refresh or upgrade for the subsystem over the next 10 years? e.g., never, once, every 2 years? | |
| ALTERNATIVE COST CALCULATION | COST |
| If there is an alternative method you utilize to calculate the cost of integration, provide the whole dollar amount (e.g., $100,000 not $100K) required to complete the effort and any additional commentary necessary to explain that method | |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| [Insert cost category] | $0.00 |
| Additional comments: | |
| SYSTEM ATTRIBUTES | |
| Does this solution currently have signature management attributes, properties, and/or capabilities? | |
| What is the lowest security level at which you can provide information regarding the signature management of this solution? | |
| What is the current internal payload capacity (in lbs)? | |
| What is the current weight of the full system (including max. payload capacity)? | |
| What is the current max/sprint speed of the solution? | |
| What is the current average speed while achieving max range? | |
| What are the current environmental limits for operation? (e.g., temperature and environmental elements) | |
| What is the current operating altitude for this solution? (Min/Max) | |
| Is this solution currently deployable from altitudes outside of its operating altitude range? | |
| Assuming a payload capacity of 35 lbs and operating between the altitudes of 8,000 feet and 12,000 feet at previously stated average speed: | |
| What is the range of this solution? (one way with 3 hours of loiter) | |
| What is the range of this solution? (one way with 4 hours of loiter) | |
| What is the current propulsion source? Type(s) of fuel, if applicable | |
| Is this vehicle currently air-launchable via Munitions Adaptive Unit? | |
| What other Launch Mechanism(s) does the vehicle currently use? | |
| Any additional planned Launch Mechanisms? (ready by when?) | |
| What Line of Sight and Beyond Line of Sight capabilities does the current solution have? (i.e. SATCOM, FTS, Location, Payload Status, C2) | |
| Does the system currently have any ability to mitigate EMI and/or cyber attacks? | |
| What type PNT capabilities are currently utilized by the system? How do these capabilities mitigate vulnerabilities in a contested environment? | |
| What are the Operational dimensions of the solution? (height/width/length) | |
| If wings and/or other portions of the solution are currently foldable, stowable, collapsible etc., what are the dimensions in it's most compact form? | |
| Is it deployable from this compact form (i.e. solution is launched and then wings open/move into place)? | |
| Describe what power the system can currently provide | |
| PAYLOAD | |
| What, if any, payload package/LRUs/datalinks are currently integrated with this system to provide C2 node and data relay services for other sUAS? | |
| If not currently integrated with the system, what payload configuration would you recommend to provide C2 node and data relay services for other sUAS? | |
| What bands, bandwidths, and frequencies does the currently integrated C2 (or recommended C2) payload utilize? | |
| What encryption does the currently integrated C2 (or recommended C2) utilize? | |
| What are the data transfer/processing capabilities of the system's currently integrated or recommended payload? | |
| What is the maximum range at which the currently integrated or recommended onboard datalinks will be able to receive, process, and distribute relevant mission information? | |
| What are the parameters currently associated with this max. range? | |
| How many vehicles can the datalinks provide collaborative autonomy and multi-aircraft control? | |
| What is the maximum range the datalinks(?) can rebroadcast mission information? | |
| What, if any, payload package/LRUs are currently integrated with this system to provide EW capabilities? | |
| What payload command and control does the system currently have? | |
| Provide the Size, Weight, and Power (SWaP) of the currently integrated payload components. If recommending a payload package, provide the Size, Weight, and Power (SWaP) and Cost of the proposed C2/data relay solution. | |
| LOGISTICS | |
| Is the system currently able to maintain an operational charge if connected to an external power source with a voltage of 120V or 240V? | |
| Does the system currently accommodate modification and/or replacement of payloads at either a logistics depot or designated forward location? | |
| How long can this current solution be stored in an operationally ready state without upkeep? | |
| What is the "operationally ready state"? | |
| What is the required scheduled maintainenance of the current system? | |
| Does the current solution contain batteries that need to be charged? | |
| If applicable, how long do the batteries last when solution is not in use? | |
| What type of routine maintenance and periodic maintenance is required on the current solution, and how often would it need to be accomplished? | |
| Are there special storage requirements (e.g., temperature and environmental elements)? | |
| How will the solution be shipped to a unit (i.e. commercial or standard)? | |
| What is the size of the storage container the solution will be kept in when not in use? | |
| How often are software updates required and how long does it take to load the new software? | |
| What is the method to load software and firmware? (e.g., over the air, SD card, etc) | |
| Can parts be repaired and/or replaced as needed in the field vice sending the solution back for repair? | |
| Are there any special tools or maintenance equipment required to support your solution? | |
| How many Field Service Representatives would be required to sustain an inventory of your solutions at the base level? | |
| What capabilities/limitations would your Field Service Representatives have? | |
| Does the solution have any transportation restrictions? If so, please explain workarounds. | |
| What types of shop stock or servicing equipment would be required to maintain the solution? | |
| Do you maintain and provide a "Bill of Materials" for your solution? | |
| Does your solution cost include Operational and Maintenance Manuals? | |
| Can operational and maintenance manuals be tailored to support USAF operational requirements? | |
| What training program(s) are required and/or available for the solution? (e.g., Operational vs Maintenance? Durations? Train the trainer?) | |
| What is the target service life of your solution? | |
| MOSA/IP RIGHTS | |
| Will USG have the necessary IP rights to complete all maintenance actions? | |
| Will USG have the IP rights to manufacture or procure spares as needed (e.g., possibly from multiple vendors)? | |
| Will USG have the necessary IP rights required to make modifications to the solution over time? | |
| Will USG have the necessary IP rights to integrate the solution's software across multiple platforms and perform necessary software updates/upgrades? | |
| AUTONOMY | |
| Does the current solution have open architecture autonomy? If so, please provide a brief description. | |
| Is the current solution autonomy compatible with government owned autonomy? | |
| Is the system capable of achieving a compliance rate of 100% adherence to assigned area assignments and flight restrictions? | |
| CYBER SECURITY | |
| Is the system Net Ready KPP compliant? (see Attachment or iaw NR-KPP attachment) | |
| How does the system protect stored data? | |
| Does the system have anti-tamper protections to detect, report, contain, and mitigate any cyber anomalies or intrusions? If so, please provide a brief description | |
| COMMON CONTROL SOFTWARE (CCS) | |
| Does the system's CCS enable positive control handoff and accept retask commands through a Government reference architecture? |
PAYLOAD
DESCRIPTION
| Description | End state | |
| Payloads | Payload components are specific components which can be integrated into the platform to provide a C2, DR, or EW solution. Vendors are to design payload components with MOSA and low SWAP-C principles in mind and in accordance with architecture and integration strategies established by the SM Architect. Vendor responses will help shape and drive investment to ensure a complete breadth of components are available. | Provide high TRL payloads for C2, DR, and EW capabilities for integration on the SM platform. |
| Technology Area | Description | Examples |
| C2/DR | High TRL/MRL technologies that support real time mission management, tasking/re-tasking of deployed sUAS and data relay to and from the contested area. | Communications, Datalinks, Data Processing, Mission Processing, Command and Control software |
| Electronic Warfare | High TRL/MRL technologies that provide EW detection or disruptive capabilities for insertion on SM Weapons System. | Active and Passive DLIR, Decoy, Disrupt |
| Enabling Technologies | High TRL technologies for Platforms, Mission Systems, Payloads, and/or sub-components that aid or enhance the payload's or platform's ability to perform it's intended mission such as increasing the platform's ability to function in a contested environment or handle larger amounts of data from more sources | Alt-Nav, PNT, EO/IR, Edge Processing |
INSTRUCTIONS
| Row / column headers | Light grey cells indicate column headers; these are not to be changed. |
| Table headers | Dark blue cells indicate table headers; these are not to be changed. |
| Input cells | Light yellow cells indicate inputs for suppliers to input responses. |
| GENERAL SOLUTION INFORMATION |
| Provide the below information for solutions that meet at least one of the descriptions provided in C10 - C12. |
| Once a Solution Name has been typed into the first Row, it should auto-populate down the spreadsheet |
| Name | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| General solution description | ||||||||
| Projected Production quantity | 2025 | |||||||
| 2026 | ||||||||
| Describe perceived applicability of solution to SM C2/DR CONOPS | ||||||||
| Please describe any specific power requirements for your solution | ||||||||
| Please describe any known barriers/complications to integrating this solution | ||||||||
| Please describe any specific encryption requirements for your solution |
| USE CASES |
| For each solution, indicate whether the solution satisfies, enhances, or enables the use case described below. Not all technologies need apply to all use cases. If there are additional use cases that you would like to propose, you may do so in Cells C50 - C56 |
| Name | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| Communications | ||||||||
| Datalinks | ||||||||
| Data Processing | ||||||||
| Mission Processing | ||||||||
| PNT | ||||||||
| Alt-Nav | ||||||||
| Command and Control | ||||||||
| Use Cases | Decoy | |||||||
| Disrupt | ||||||||
| DLIR | ||||||||
| Passive DLIR | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE | ||||||||
| INSERT ADDITIONAL USE CASES HERE IF APPLICABLE |
| ATTRIBUTES/SPECIFICATIONS |
| For each solution listed above, provide a description of how the solution meets the use case listed in Cell D10, including detailed attributes or specifications |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| Description |
Briefly describe the solution, including detailed attributes or specifications that support how the solution satisfies, enables, and/or enhances the platform, C2/DR or EW requirement. A more robust description may be provided in the optional synopsis attachment.
| COST |
| Enter the whole dollar amount in the input cells (e.g., $100,000), NOT $100K or $0.1M for the expected run rate unit cost. |
| Current Average Production Unit Cost (USG) | Qty | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] |
| 1-10 | ||||||||
| 11-50 | ||||||||
| 51-300 | ||||||||
| 301+ | ||||||||
| What is your methodology for deriving this unit cost? (e.g., experience curve, commonality with related systems, etc.) |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | ||
| Development Cost | NRE Costs through LRIP | |||||||
| What is your methodology for deriving this unit cost? (e.g., experience curve, commonality with related systems, etc.) |
| Sustainment Cost per Unit (USD) | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| Annual cost per unit | ||||||||
| What is your methodology for deriving this sustainment cost? | ||||||||
| What is the expected rate of refresh or upgrade for the subsystem over the next 10 years? e.g., never, once, every 2 years? |
| ALTERNATIVE COST CALCULATION |
| If there is an alternative method you utilize to calculate the cost of integration, provide the whole dollar amount (e.g., $100,000 not $100K) required to complete the effort and any additional commentary necessary to explain that method |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | ||
| Alternative cost structure | [Insert cost category] | |||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| [Insert cost category] | ||||||||
| SUM | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
| Description and additional comments: |
| SWAP (Size, Weight, and Power) |
| Enter the SWAP details by solution; if SWAP is NOT applicable for the solution, write N/A in the input cell. If you leave the input cell blank, we will assume "N/A". |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | ||
| Total Weight (lbs.) | ||||||||
| Total Space | Length (in.) | |||||||
| Width (in.) | ||||||||
| Height (in.) | ||||||||
| Total power usage (W) |
| TECHNOLOGY READINESS LEVEL (TRL) |
| Enter the current Technology Readiness Level (TRL) and Manufacturing Readiness Level (MRL) of your solution. |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| Current TRL | |||||||
| Current MRL |
| MOSA & IP / DATA RIGHTS |
| Answer the following questions regarding MOSA/IP Rights. Provide any additional clarification on responses. |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | ||
| MOSA | Is the solution MOSA compatible/compliant? | |||||||
| IP Rights | Will USG have the necessary IP rights to complete all maintenance actions? | |||||||
| Will USG have the IP rights to manufacture or procure spares as needed (e.g., possibly from multiple vendors)? | ||||||||
| Will USG have the necessary IP rights required to make modifications to the solution over time? | ||||||||
| Will USG have the necessary IP rights to integrate the solution's software across multiple platforms and perform necessary software updates/upgrades? |
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| Additional Description and/or Comments: | |||||||
| [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | [INSERT SOLUTION NAME HERE] | |
| Please list all recently completed, relevant projects, the end client, total cost, and degree of similairity to this effort (Limit relevant projects to a max of 3 per solution) |
ACRONYMS
| AFLCMC | Air Force Life Cycle Management Center |
| Alt-Nav | Alternative Navigation |
| C2 | Command and Control |
| C2/DR | Command and Control / Data Relay |
| CAGE | Commercial and Government Entity |
| CCS | Common Control Software |
| CONOPS | Concept Of Operations |
| DAF | Department Of the Air Force |
| DLIR | Downward-Looking Infrared Radar |
| DR | Data Relay |
| DUNS | Data Universal Numbering System |
| EMI | Electromagnetic Interference |
| EO | Electro-Optical |
| EW | Electronic Warfare |
| FAR | Federal Acquisition Regulation |
| FTS | Flight Termination System |
| FY | Fiscal Year |
| IP | Intellectual Property |
| IR | Infra-Red |
| ISR | Intelligence, Surveillance, Reconnaissance |
| KPP | Key Performance Parameter |
| LRIP | Low-Rate Initial Production |
| LRU | Line Replaceable Unit |
| MBSE | Model Based Systems Engineering |
| MOSA | Modular Open System Approach |
| MRL | Manufacturing Readiness Level |
| NR | Net Ready |
| NRE | Non-Recurring Engineering |
| OCI | Organizational Conflict of Interest |
| O-sUAS | Offensive small Uncrewed Aircraft Systems |
| PNT | Position, Navigation, Timing |
| POC | Point of Contact |
| RFI | Request for Information |
| RFP | Request for Proposal |
| RFQ | Request for Quote |
| SATCOM | Satellite Communications |
| SETA | Systems Engineering and Technical Assistance |
| SM | Signature Managed |
| SOF | Special Operations Forces |
| SPO | System Program Office |
| SPO | System Program Office |
| sUAS | Small Uncrewed Aircraft Systems |
| SWaP | Size, Weight, and Power |
| SWaP-C | Size, Weight and Power - Cost |
| SysML | System Modeling Language |
| TRL | Technical Readiness Level |
| USAF | United States Air Force |
| USC | United States Code |
| USG | United States Government |
File details come from the government source that posted it. Updated .