The Enterprise-Wide Agile Acquisition Contract (EWAAC) is a multiple-award IDIQ contract vehicle for authorized government users whose requirements support the Air Force Air Armament mission. It supports the acquisition of digital, open, and agile supplies and services related to weapons and enterprise analytics requirements. For qualified users, EWAAC provides a path to compete and award in-scope work through the government’s ordering process.
A downloadable PDF of this guide is available here
1. Confirm That You Are an Authorized EWAAC User
Use EWAAC only if your organization is an authorized customer or government user whose requirement supports the Air Force Air Armament mission. This is the first threshold question.
2. Confirm That Your Requirement Fits EWAAC Scope
Use EWAAC only when the requirement is clearly within contract scope. EWAAC supports work across the weapons lifecycle, including development, testing, integration, production, fielding, modernization, sustainment, and related analytics.
3. Define the Requirement Before Release
Develop a clear requirement before starting the order process. The requirement should identify the mission need, the product or service, key deliverables, schedule, deployment environment, integration needs, and support requirements.
4. Match the Requirement to the Correct EWAAC Work Element
Assign the requirement to the EWAAC work element that best fits the acquisition. Digital Trinity covers digital engineering, agile processes, and open architecture work. Armament/Weapons Development covers design, engineering, prototyping, production, deployment, integration, training, and logistics support. Enterprise Analytics covers data transformation, reporting, and analysis products. Innovation Hub is a limited path and should be used only when specifically appropriate and authorized.
5. Address Technical Requirements Early
Define software, hardware, interface, cybersecurity, and digital engineering requirements before release. If applicable, address model-based systems engineering, government reference architecture alignment, technical stack requirements, and required reviews early in the process.
6. Resolve Security, Data Rights, and Access Requirements Up Front
Security requirements are addressed at the delivery order or task order level. Many orders will require at least a Secret clearance, and some may require more. Data rights and software license rights are also determined at the order level and may affect award decisions. If performance requires access to Air Force computer systems or facilities, those access requirements should be identified early.
7. Identify Any Organizational Conflict of Interest Issues Early
If the requirement may involve advisory support, evaluation of another contractor’s products or work, access to proprietary information, or participation in writing specifications or statements of work, review organizational conflict of interest issues early. Potential conflicts should be disclosed and addressed before performance begins.
8. Issue the Fair Opportunity Proposal Request
Under EWAAC, most orders are placed through a Fair Opportunity Proposal Request, or FOPR, under FAR 16.505. The FOPR should include the statement of work or statement of objectives, required deliverables, evaluation criteria, proposal instructions, and due date. In most cases, the government provides all awardees a fair opportunity to compete unless a valid exception applies.
9. Evaluate Proposals and Award the Delivery Order
The government contracting office evaluates proposals based on the criteria in the FOPR. Evaluation may use lowest price technically acceptable, tradeoff, or another stated method. Award is made at the delivery order level, and the contractor may not begin work until a signed order or other written contracting officer approval is issued.
When to Contact Us
Contact Vigilant Aerospace Systems when your team has a defined requirement that appears to fit EWAAC and before the final FOPR or task order package is released. At that stage, we can discuss whether our capabilities align with the requirement and identify product, integration, security, or deployment considerations relevant to our scope of work.