Six Acquisition Pathways for Massive-Scale, Advanced Techniques

In software program acquisition as in software program structure, one measurement doesn’t match all. Advanced mixed-criticality methods require a versatile government-acquisition system for approval, oversight, and funding. Our earlier weblog submit described how technical reference frameworks (TRFs) present versatile computing and infrastructure environments by way of modular parts that align a sample of temporal must scale with the processing wants for reusable area architectures. TRFs handle the total vary of army capabilities, juxtaposing the boundaries of criticality and scale. On this submit we present easy methods to map TRFs to the completely different pathways that compose the DoD’s Adaptive Acquisition Framework (AAF).

Advanced architectures of architectures comprising features of blended criticality require a mixing of various TRFs. As proven in Determine 1, a single, unified acquisition technique that may additionally apply a unified technical structure for such a system of methods (referred to henceforth extra compactly as “methods”) would set up synthetic processes and bounds for growing, securing, working, and enhancing these methods.

Simply as TRFs are tuned and optimized for the completely different scales by which these methods function, the methods and practices for buying these methods have to be equally tuned and optimized. In response to this want, the DoD launched the Adaptive Acquisition Framework (AAF) to instantiate flexibility and agility as foundational components for product growth and lifecycle administration throughout all acquisition packages. The AAF might be pursued successfully by enveloping the DoD Digital Engineering Technique, thereby placing the suitable instruments into the suitable locations for the product being pursued. This strategy additional helps the acquisition group handle distinctive functionality wants and threat profiles whereas encouraging customization.

To restrict complexity and reduce threat, program govt officers and program managers historically apply an acquisition technique that self-limits the out there choices. These acquisition practices ignore the cadence, necessities, and threat profile that uniquely characterize the kinds of parts or subsystems being created, and as an alternative apply a typical schedule-driven cadence and main-event-like obligatory programmatic critiques in packages that want a distinct strategy. Techniques for coping with technical complexity and future supply wants of innovation might be launched over time, however at an acceptable tempo for the goal know-how, program necessities, schedule, and price range.

The TRFs utilized in mixed-criticality methods ought to subsequently be structured to deal with layering-on these downstream options and deploying them in risk-prudent strategies which can be attentive to the warfighter wants whereas addressing acceptable security/safety issues. Fortuitously, the AAF permits packages to compose the strategy in ways in which finest match the know-how and use case of the completely different components of the acquisition in essentially the most environment friendly method. It affords appreciable flexibility to resolution authorities and packages concerning acquisition technique, governance devices, and general execution of this system.

Particularly, DoDI 5000.02, Part 3.1 expenses resolution authorities with

• tailoring of program methods and oversight
• timing and scope of resolution critiques
• phasing of functionality content material over time
• pathway choice and adaptation (see Determine 4 beneath)

Via this acquisition reform, DoD empowers the professionals doing the work with engineering the constructs, governance, and processes that allow profitable achievement of program targets. Recognizing that necessities and threat profiles are distinctive to every program and subsequently require completely different acquisition methods for one main functionality acquisition (MCA), the DoD created six pathways, proven in Determine 2 beneath, aimed toward streamlining and decreasing the chance related to the acquisition of IT methods, merchandise, and companies.

The flexibleness and steerage supplied by DoD 5000.02 provides choices to discover a number of pathways to match the acquisition technique to program wants. It allows acquirers to supply tailor-made assist for this system’s distinctive traits and threat profile.

Of the six pathways, each the Software program Acquisition and Protection Enterprise Techniques pathways current alternatives to discover the appliance of TRFs. Software program methods, together with both weapon or enterprise methods, want to make use of TRFs acceptable to the technical area being addressed. These selections make it potential for this system to attain its targets by leveraging environments that may be utilized to their wants, as an alternative of making their very own atmosphere(s) every time.

Of specific curiosity, the Software program Acquisition pathway, enlarged in Determine 3 beneath, allows a program workplace to outline an acquisition technique that leverages present software-delivery frameworks and introduces flexibility into planning and execution. This pathway encourages software-development practices, similar to Agile, DevOps, DevSecOps, and Lean, and provides a program the agility to discover cutting-edge growth strategies and applied sciences. Via the iterative nature of the pathway, disclosure on the traits of the design will get to stakeholders early and sometimes. Stakeholders and distributors talk all through design and growth with the federal government, offering enter and gaining clarification as acceptable.

Briefly, the Software program Acquisition pathway

• allows steady integration and supply of software program functionality on timelines acceptable to the battle­fighter and finish person, or mission requirement
• is the popular path for acquisition and growth of software-intensive methods
• establishes business-decision artifacts to handle threat and allow profitable software program acquisition and growth

The Software program Acquisition pathway is suitable for military-unique capabilities, similar to real-time command-and-control performance, the place the design is targeted on custom-built or extremely custom-made software program. The usage of TRFs 1 and a pair of could also be nicely fitted to these methods.

Nonetheless, the Software program Acquisition pathway is probably going not acceptable for purchasing enterprise methods which can be made up largely of industrial off-the-shelf (COTS) merchandise with some minor alterations or code-only enhancements (extra on this later).

The Pressing Functionality Acquisition pathway, enlarged in Determine 4 beneath, is reserved for capabilities required to save lots of lives or confirm mission accomplishment. This pathway employs a Lean acquisition course of that fields capabilities fulfilling pressing present or rising operational wants or fast reactions in lower than two years.

Numerous kinds of merchandise might be fielded as an pressing functionality. It’s subsequently arduous to say the usage of a selected TRF for one of these acquisition, although TRFs 1 and a pair of could also be appropriate. One benefit of utilizing these frameworks in fast functionality acquisition is that the trouble to ascertain and handle the event and deployment atmosphere might be leveraged throughout many packages, releasing sources to concentrate on the uniquely wanted army functionality. It will seemingly additionally assist scale the productionization of an pressing functionality if its utility is confirmed particularly beneficial within the warfighting enviornment.

The Center Tier of Acquisition (MTA) pathway, enlarged in Determine 5 beneath, is used to quickly develop fieldable prototypes inside an acquisition program to show new capabilities or quickly discipline manufacturing portions of methods with confirmed applied sciences that require minimal growth. The MTA pathway is meant to fill a niche within the protection acquisition system for these capabilities with a stage of maturity that allows fast prototyping inside an acquisition program or fielded inside 5 years of the MTA program begin. The MTA pathway can be utilized to speed up functionality maturation earlier than transitioning to a different acquisition pathway or to minimally develop a functionality earlier than quickly fielding.

The rapid-prototyping path supplies for the usage of modern applied sciences and new capabilities to quickly develop fieldable prototypes to show new capabilities and meet rising army wants. The targets of an acquisition program underneath this path contain fielding a prototype that was efficiently demonstrated in an operational atmosphere and to supply a residual operational functionality inside 5 years of this system begin date. Digital-prototyping fashions are acceptable in the event that they yield a fieldable residual operational functionality. MTA packages is probably not deliberate to exceed 5 years to completion and, in execution, is not going to exceed 5 years after MTA program begin with out a protection acquisition govt (DAE) waiver.

The rapid-fielding path supplies for the usage of present merchandise and confirmed applied sciences to discipline manufacturing portions of latest or upgraded methods with minimal growth required. The target of an acquisition program underneath this path is to start manufacturing inside six months and full fielding inside 5 years of the MTA program begin date. The manufacturing begin date of the MTA program is not going to exceed six months after the MTA program begin date with out a DAE waiver.

Related advantages to the usage of TRFs 1 and a pair of within the growth of pressing capabilities apply to the acquisition of middle-tier capabilities. This acquisition is especially beneficial provided that middle-tier merchandise are sometimes productized in a number of portions, fielded for longer durations, and topic to evolving calls for for functionality that might be delivered with software program upgrades. TRFs 1 and a pair of are significantly appropriate for this atmosphere.

Determine 6 exhibits the pathway and the cyclical Enterprise Functionality Acquisition Cycle. The authority to proceed (ATP) gates compartmentalize the phases, and the method reduces a lot of the paperwork required in DoDI 5000.02. Particulars concerning the execution of the pathway might be discovered at https://aaf.dau.edu/aaf/dbs/. The pathway is dependent upon steady course of enchancment and might be leveraged as a streamlined path for buying parts which can be commercially out there.

This pathway, enlarged in Determine 7 beneath, is meant to establish the required companies, analysis the potential contractors, contract for the companies, and handle efficiency. The pathway actions are damaged into three phases: plan, develop, and execute. This pathway is described within the DoD Handbook for the Coaching and Growth of the Companies Acquisition Workforce.

A Main Functionality Acquisition (MCA) pathway acquires and modernizes military-unique packages that present enduring functionality. It’s arduous to conceive of any MCA that may not be software-reliant. Ought to that be the case, a blended strategy to the authorities of the varied acquisition pathways would match one of the best framework to the enterprise wants of this system similar to proven in Determine 8. Matching trade incentives and enterprise fashions might be tuned to the kind of exercise, sources, and cadence of motion. General execution threat could be lowered by combining these insurance policies in a coordinated vogue.

As beforehand described, there’s a correlation between acquisition pathways and TRFs. Determine 9 presents a mapping of how these might be utilized. Main capabilities would, in lots of instances, be tied to a selected army platform (sea-going, land-based, flight automobile, spacecraft, and so on.). These autos would require real-time management methods for which TFR 1 is finest suited. As well as, the platform-level integration of methods and subsystems might be derived from cross-platform product strains. The appliance of these merchandise into new main capabilities would offer the propelling must transition into TRFs to scale back execution and integration threat for the general enterprise. These military-unique capabilities developed underneath the Center Tier or Software program Acquisition pathways might be constructed on TRFs 1, 2, and three.

Establishing growth and deployment environments for functionality, in addition to the modeling and services used to assist growth testing, operational testing, and lifecycle assist companies might be acquired underneath a mixture of the Acquisition of Companies and Protection Enterprise Techniques pathways. These features would seemingly be finest fitted to the usage of TRF 3.

On this submit, we’ve proven that DoD acquisition packages now not should go it alone and settle for the burden of unbounded technical threat on the subject of constructing their mission methods, or the assist companies that they might rely on. What we prescribe right here is nicely throughout the realm of technical achievement right now. The most important problem is to wrangle the construction of the acquisition atmosphere, the funding fashions, and the cultural incentives.

Because the idea of TRFs beneficial properties traction and extra methods are compelled to observe swimsuit, the strategies of integration, growth testing, and operational testing must evolve as nicely. As well as, the strategies of managing interoperability must evolve to deal with repeatedly evolving functionality within the discipline, delivered on completely different time horizons, and to handle shifting interoperability/evolving performance over a lifecycle of a long time.