1_EWAAC_SOO_7.16.24_Rev 4.pdf

Controlled Unclassified Information (CUI) Attachment 1

FA8656-24-R-B002

STATEMENT OF OBJECTIVES

FOR

THE ENTERPRISE WIDE AGILE ACQUISITION CONTRACT (EWAAC)

Formerly Eglin Wide Agile Acquisition Contract

Original - 24 June 2021

Rev. 1 - 5 December 2022

Rev. 2 – 15 December 2022

Rev. 3 – 5 April 2023

Rev. 4 – 16 July 2024

1. Introduction The Armament Directorate (AFLCMC/EB) at Eglin AFB, FL is seeking the ability to: a) rapidly develop technologies of novel weapons capabilities, b) apply unique solutions and innovative ideas, and c) characterize new technologies and system concepts that provide evolutionary, revolutionary, and disruptive capabilities for the United States Air Force through weapons systems requirements development, studies and demonstrations. The primary objective is to provide rapid response applicable to all areas and lifecycle phases of weapons development to include weapons concepts, concept development, concept demonstrations, weapons system procurement, production, fielding, operations, and sustainment to quickly meet current and future weapons system requirements. Customers include AFLCMC/EB divisions, SOCOM Det-1, Air Force Research Lab (AFRL), and the Air Force Nuclear Warfare Center (AFNWC). Other service departments and federal agencies may be authorized to use the IDIQ if their requirement complements, supplements, or supports the Air Force Air Armament's mission.

2. Overall Scope

This specification establishes the requirements for the EWAAC Indefinite Delivery Indefinite Quantity (IDIQ) contract including but not limited to the following:

• Science and Technology (S&T)

• Research and Development (R&D)

• Test and Evaluation (T&E)

• Integration / Assembly

• Production and Fielding

• Operations and Sustainment

• Modernization

• Prototyping

• Experimentation

• Studies, Demonstrations, Testing of prototypes

• Hardware and Software modifications

• Weapon Design

• System Modeling

• Data mining/collection/analysis

3. Objectives

3.1. Deliver innovative capabilities to the warfighter with increased speed and agility.

3.2. Incorporate digital acquisition and sustainment practices to include Digital Engineering (DE), Agile Processes, and Open System Architecture (OSA).

4. Technical Areas of Interest

4.1. Planning activities to develop and transition concepts into weapon acquisition and fielding. This includes work at the technology level, system level, testing, modeling, and analysis.

4.2. Weapon studies applied to current and potential weapon systems in perceived mission scenarios.

4.3. Use of agile enabling processes such as DE and OSA in order to accelerate acquisition and provide capability to the warfighter faster.

4.3.1. DE and Model Based Systems Engineering (MBSE). These include but are not limited to Integrated Trade Space Analyses, Behavior Modeling, Machine Learning and Artificial Intelligence, and a system/concept Modeling and Simulation (M&S) foundation that includes performance modeling, operational analysis, digital twin/thread, and live virtual construct (LVC). Integration of a DE framework that combines models, data, and artifacts allows the US to rapidly respond to changing threats, field advanced capabilities, and engineer dominant systems at the speed of relevance.

4.3.2. OSA is a structure in which systems/concepts interfaces share common, widely accepted standards that can be independently verified, and is key to enabling incremental development, enhancing competition, driving innovation, and maximizing interoperability.

4.3.2. Agile processes include agile software development that allows continuous collaboration with the end user, agile validation/verification processes to include the use of modeling and simulation for risk reduction, and agile test methods such as the use of surrogate test beds.

4.4. Technologies and/or processes that enable the development, testing, and fielding of capabilities in the areas of, but not limited to: propulsion development, guidance, navigation and control, sensors (e.g.

seekers, inertial measurement units, datalinks, etc.), payloads, software/algorithms, new materials, flight termination systems, and telemetry/instrumentation systems; integration of these technologies into components, subsystems or systems.

4.5. Support in developing concepts, analyzing mission effectiveness (including affordability), and demonstrating prototypes for innovative Air Force Armament materiel solutions in the following areas:

Reach, Affordable Mass, Autonomous Collaboration, Sensing and Communication Nodes, and Non- Kinetic Effects.

4.5.1. Reach: Hold adversaries at risk in air, ground, and surface domains with increased standoff technologies that enhance scramjet/ramjet engines, compact boosters with higher specific impulse, small and efficient gas turbine engines, and hypersonic flight are primary emphasis areas; technologies that increase weapon standoff at neutral inventory cost are also highly desired.

4.5.2. Affordable Mass: Deliver large quantities of low cost weapons from traditional and non-traditional platforms. The goal is to impart a cost imposing strategy on the adversary by overwhelming the airspace with low cost, yet effective weapons.

4.5.3. Autonomous Collaboration: Weapons adapt to the battlespace and maximize outcomes in situations that would overwhelm human decision makers; sharing data and develop/execute coordinated actions to improve information across the entire group.

4.5.4. Sensing and Communication Nodes: Weapons will be used as a sensor and communication node to enable Multi-Domain Operations.

4.5.5. Non-Kinetic Effects: Add unique, disruptive battlespace capability (multi target defeat) with large, “reusable” magazine. Directed energy (high energy lasers, high power microwaves, etc.)

and electronic warfare are primary focus areas.

4.6. Support explorations of new technologies through accelerated design cycles that enhance weapon system modularity, robustness, affordability, platform capacity, standoff, survivability, accuracy, flexibility, and improved lethality against a wider array of target types, and allow for rapid integration on both legacy and next generation platforms. This includes initiatives for the rapid execution of innovative, emerging capabilities and technologies for munitions or munitions related products by developing, integrating, and proving through rapid prototyping, demonstration, and/or fielding within 24 months. Tools that advance the Air Force’s ability to determine the value of various technologies are also desired.

5. Work Elements

5.1. Digital Trinity: Digital Engineering and Management, Agile Processes, and Open Architecture.

Examples of required activities are:

5.1.1. Utilize DE and MBSE methodologies to include the development of a Digital Ecosystem that integrates the relevant technical data, models, analyses, and associated digital artifacts as part of the Authoritative Source of Truth (ASoT) to be utilized over the lifecycle of the program. If a Government Integrated Digital Environment (IDE) is available at the appropriate classification level, the offeror shall establish the offeror’s Digital Ecosystem within the Government IDE.

Otherwise, the offeror shall coordinate with the Government to provide continuous live access and updates to the DE Ecosystem. If the Government IDE is not available, Government access to the DE Ecosystem at contractor's facility is acceptable to meet this objective.

5.1.2. Develop a Digital Ecosystem or components thereof using models as an integral part of the technical baseline that includes requirements, analysis, design, implementation, verification/validation, manufacturing, and general product life-cycle management.

5.1.3. Develop a detailed DE/MBSE Plan which outlines the DE/MBSE strategy for the lifecycle of the program to include maturation of the digital thread and digital twin as well as use of a Government Reference Architecture (GRA).

5.1.4. Adhere to the GRA provided by the Government. The GRA is a general-purpose architecture design consisting of data models that capture the physical, logical, and functional description of a common open systems architecture. The GRA clearly identifies key government-owned interfaces based on the Government acquisition objectives and identifies trade space for design flexibility.

5.1.5. Develop a Contractor Implementation Model based on the GRA IAW the DE/MBSE Plan.

5.1.6. Use commercially available software tools as defined by the Government as part of the Technical Stack or “Tech Stack.”

5.1.7. Incorporate a cybersecurity architecture at the beginning of the development effort.

5.1.8. Conduct model based program System Engineering Technical Reviews (e.g., System

Requirements Review (SRR), Preliminary Design Review (PDR), etc.).

5.2. Armament/Weapons Development. Examples of required activities are:

5.2.1. Perform trade space and capabilities studies in fielding and supporting armament systems.

5.2.2. Perform design and engineering development in fielding and supporting armament systems.

5.2.3. Perform prototyping and experimentation activities in fielding and supporting armament systems.

5.2.4. Perform production and deployment activities such as manufacturing planning and fabrication of armament systems.

5.2.5. Perform operations and support functions such as system installation, integration (e.g., component / subsystem / system, manufacturing, aircraft, laboratory, or other levels of integration), training, and integrated logistics support of armament systems.

5.2. Enterprise Analytics. Examples of required activities are:

5.2.1. Provide Business Intelligence (BI) tools by leveraging DoD investment in high performance computing centers.

5.2.2. Provide data mining and transformation for BI tools.

5.2.3. Generate concise and reporting and analysis products such as contract analyses, enterprise risk analyses, business cases analyses, and cost-benefit analyses.

5.3. Innovation Hub: The innovation hub will serve as a location and/or physical place for collaborative efforts between experts, innovators, and creators throughout the DoD enterprise to convene and conduct “industry-changing” research, development, test and evaluation, production, and sustainment for the greater defense of the United States. The contractor will accomplish all acquisition/procurement, program management, and systems engineering actions to operate the Innovation Hub. The actions include, but are not limited to logistics, cyber, environmental, industrial, energy, security and safety requirements (i.e., some projects may require in-house testing, demonstration, and validation support while others will require management of sub-tier suppliers whereby planning and requirements matching to ensure sub-contractor contract deliverables are the critical activities required). Solutions under this work element are exclusively authorized by AFLCMC/EB, PEO Weapons, for Operational Imperative and related efforts/requirements and should be product and/or process focused, using a mixture of people and technologies to provide foundational armament/weapons capabilities in support of DoD mission-sets. Examples of required activities are:

5.3.1. Developmental [Ops] Environment – The contractor will provide:

5.3.1.1. A developmental ops environment that is ICD 705 compliant and accredited located in the greater Okaloosa County area locality, within 10 miles of Eglin Air Force Base, FL

5.3.1.2. Sufficient capacity for developmental operations, demonstration labs, collaboration space, and technology integration to conduct the full range of day-to-day programmatic and operational capabilities for Armament missions.

5.3.2. Integrated Hardware, Software, and Network Services - The contractor will ensure:

5.3.2.1. Environment includes dedicated network bandwidth, Wi-Fi, power, and security suitable to meet AF requirements for a DevSecOps environment to support Armament mission needs.

5.3.2.2. IT support by personnel with the expertise, certifications, skills, and ability in maintaining and solving environment, network, and service issues.

5.3.2.3. IT support tasks (anticipated during standard business hours) include monitoring and maintaining the IT environment; installing and configuring computer systems;

diagnosing hardware and software operating system faults; and solving technical and applications problems, either over the phone or in person.

5.3.3. Software License Management – The contractor will provide:

5.3.3.1. Personnel authorized by the USAF to install, maintain, and manage licenses for software and business tools that support the Armament mission to include tasks such as conducting software security assessments, software and business tool product research, recommendations, and procurement.

5.3.3.2. Monitoring license expirations and renewals; system administration; and addressing integration issues.

5.3.3.3. Providing situational awareness into which Product Teams are using what tools, when the subscriptions expire, and providing recommendations to continuously improve our tools.

5.3.4. Integrated and Configurable Tech Labs Supporting DoD Mission-Sets – The contractor will develop and provide:

5.3.4.1. Lab/workspace, equipment, and infrastructure that will foster the creation of new technology demonstrations in a central location/marketplace.

5.3.4.2. Labs may offer hands-on learning opportunities and demonstrations of technology, support to startups of interest to the Armament Directorate, projects, risk reduction efforts, and corporate innovation programs designed to prototype new solutions for the

USAF.

5.3.4.3. Labs may foster new partnerships and collaborations of partner institutions to push the bounds of technological advancements and create breakthroughs from which new ventures will emerge to enable a lighthouse effect within the Armament portfolio and its enterprise.

6. Other Considerations

6.1. Security. Offerors need not possess a security clearance for an award on the basic contract. However, the majority of delivery orders / task orders on this contract will require a minimum of a SECRET level clearance, and some will be at a higher level. Security requirements shall be addressed at the program level pending specific requirements.

6.2. Data Rights. The Government’s intent is to own data rights for the majority of delivery orders / task orders on this contract.

7. Definitions

Agile Processes – Project management processes, mainly used for software development, where demands and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customers.

Agile Software – Software development methodologies centered round the idea of iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams and their customers.

Authoritative Source of Truth (ASoT) – The central reference point for models and data across the lifecycle.

The ASoT provides traceability as a system evolves, capturing historical knowledge and connecting authoritative versions of the models and associated data. Types of models include management, design, manufacturing, product support, verification and validation, and specialty engineering.

Behavior Modeling – A model that shows the interactions between objects to produce some particular system behavior that is specified as a use-case. Sequence diagrams (or collaboration diagrams) are used to model interaction between objects.

Business Intelligence (BI) – Strategies and technologies used by enterprises for data analysis of business information. BI technologies provide historical, current, and predictive views of business operations.

Digital Ecosystem - A digital ecosystem is a group of interconnected information technology resources that can function as a unit. Digital ecosystems are made up of suppliers, customers, trading partners, applications, third-party data service providers and all respective technologies. Interoperability is the key to the ecosystem's success.

Digital Engineering (DE) – An integrated digital approach that uses authoritative sources of system data and models as a continuum across disciplines to support lifecycle activities from concept through disposal.

Digital Trinity – The complete approach to Digital Acquisition of incorporating Digital Engineering and Manufacturing, Agile Software, and Open System Architecture into weapon systems by enabling design, assembly, testing, and sustainment in the virtual/digital realm before real-world production begins.

Digital Twin - One-to-one system models, conjoined with their individual real-world systems in data feedback loops, which may or may not be governed by a full digital thread.

Digital Thread - An extensible analytic framework to connect models, and all associated data, software, and functional support, governing more than one system lifecycle phase with one-to-one real-word traceability.

Government Reference Architecture (GRA) – A model-based, authoritative source of information to guide and constrain mission architectures and solutions. It integrates data, information, boundary conditions, and rules that describe the mission capability needed by the warfighter in sufficient detail to allow for transition of technology-based solutions.

Integrated Digital Environment (IDE) -- A compilation of data, models, and tools for collaboration, analysis, and visualization across all functional domains. IDE includes the methodology and specification for data, models, and tools arrangement with processes and procedures to exploit informational results. This might look differently dependent on your program’s digital implementation, but one example is in the below graphic showing a government IDE with multi-levels of security exchanging models and data from a contractor's IDE also at multi-levels of security. One note of importance is that the IDE includes the integration of programmatic (program manager, financial manager, logistics manager, etc.) information with the engineering models and data so that the environment is truly integrated.

Integrated Trade Space Analyses – Analyses that address criteria relevant to decision making that can be traded off against one another to achieve specific outcomes to reflect specific alternative solutions. Typical criteria include performance/benefits, schedule, risk, and cost.

Open System Architecture (OSA) – A system design approach which aims to produce systems that are inherently interoperable and connectable without recourse to retrofit and redesign.

Machine Learning and Artificial Intelligence – Machine learning enables a computer system to make predictions using historical data without being explicitly programmed. It is a subset of Artificial Intelligence, a technology with which systems can be created to simulate human intelligence (do not require pre-programming).

Model Based Systems Engineering (MBSE) – The formalized application of modeling to support system requirements, design, analysis, verification, and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases.

Modeling and Simulation (M&S) – The use of a physical or logical representation of a given system to generate data and make predictions and support decision making.

Technical Stack or “Tech Stack” – The collection of data, models, software, and associated infrastructure needed to create and optimize the digital representation of a system over its lifecycle.

9. References

Item Document Date or latest 1 DODI 5000.87: Operation of the Software Acquisition Pathway 2 Oct 2020

2 ISO/IEC/IEEE/FDIS15289, Systems and software engineering - Content of life-cycle information items (documentation) Jul 2019

3 ISO/IEC/IEEE 15288:2015 Systems and Software Engineering - System Life Cycle Processes May 2015

4 ISO 10303-242 (STEP AP 242) Managed Model-Based 3D Engineering Apr 2020

5 Mil-Std-881E “Work Breakdown Structures for Defense Materiel Items” 6 Oct 2020

6 “There is No Spoon: The New Digital Acquisition Reality” Dr.

Will Roper 18 Sep 2020

‘Disruptive Agility for a Disruptive World’ Keynote Address by Dr. Will Roper, Air Force Association’s 2020 Virtual Air, Space and Cyber conference

15 Sep 2020

8 Weapon Open System Architecture (WOSA) Interface Control Document (ICD) VOLUME 2 – Logical Interface Provided at DO/TO level

9 WOSA ICD Volume 3 - Test Provided at DO/TO level

10 AFRL WeaponONE Program (Weapon Digital Enterprise - Digital Twin – RogueONE)

Public website forthcoming

11 EB Government Reference Architecture (GRA) Provided at DO/TO level