THE ASSISTANT SECRETARY OF THE HAW (RESEARCH. DEVELOPMENT AND ACQUISITION) WASHINGTON. DC 20350-1000 2 xi 20l8 MEMORANDUM FOR DISTRIBUTION SUBJECT: Middle Tier Acquisition and Acquisition Agility Guidance Reference: (3) Fiscal Year 2016 National Defense Authorization Act (Public Law I 14?92) Fiscal Year 2017 National Defense Authorization Act (Public Law 1 14-328) USD Memo? "Middle Tier ol?Acquisition (Rapid Prototyping/ Rapid Fielding) Interim Authority and Guidance" ASN (RDELA) Memo. ?Designation ol'the Deputy Assistant Secretary of the Navy for Research, Development, Test and Evaluation to Lead Implementation of Accelerated Acquisition?, Nov 8, 2017 I hereby direct that the Middle Tier Acquisition and Acquisition Agility authorities provided under references through will be implemented within the Department of the Navy (DON) consistent with the attached Middle Tier Acquisition Interim Guidance and Acquisition Agility Interim Guidance. Reference authorizes the Secretary of Defense and Service Secretaries to establish Middle Tier Acquisition pathways for Rapid Prototyping and Rapid Fielding. Reference authorizes Acquisition Agility aimed at speeding the development and transition of advanced technology and high risk components through a separate and distinct path of?eomponent acquisition" characterized by rapid prototyping. The DON will follow an incremental approach to implementation. We will use these authorities to enable speed and agility. while maintaining appropriate accountability. oversight and transparency. We will continue to collaborate with the Of?ces of the Secretary of Defense (OSD) to better align policies and regulations and evolve the DON policy accordingly. The DON implementation plan will include a series ofpilot programs to exercise these authorities and inform policy development. These pilot programs will be executed utilizing the interim acquisition guidance attached. As we learn from these pilot programs, we will provide Future guidance to support full implementation of these authorities into the DON Acquisition System. Program Executive Of?cers with pilot program candidates will work with their product Deputy Assistant Secretaries of the Navy (DASN) to be evaluated for acceleration as a pilot program. SUBJECT: Implementation of Middle Tier and Acquisition Agility Guidance In addition to this guidance, I am directing the Systems Commands and Program Executive Of?ces to assess their organizations? contracting, technical, legal, and ?nancial processes to facilitate the acceleration of programs when appropriate. Effective implementation of these authorities will require learning and changing the way we do acquisition. Until more formal training is available, points of contact from each of the DASNs, per reference are available to support the acquisition workforce in implementation. The DASN for Research, Development, Test and Evaluation will continue to provide a ?War Room? to facilitate familiarization of the new authorities and implementation of this plan. For questions related to this implementation plan, please contact Mr. Peter Manternach, peter.manternach@navy.mil, (703) 413-0702 or Ms. Kristen Alvarez, kristen.alvaez@navy.mil, (703) 695-7949. a eurts Attachments: As stated cc: CNO CMC PMD ASN PCD ASN AGC ASN DASNs DC, OPNAV N9 ONR PEOs NAVSEASYSCOM DACM ASN Middle Tier Acquisition Interim Guidance 1. Description. Section 804 of the Fiscal Year (FY) 2016 National Defense Authorization Act (N DAA), as amended in FY 17 NDAA (codi?ed at 10 U.S.C. 2302 note), authorizes a Middle Tier acquisition pathway, separate from the traditional acquisition system, for rapid prototyping projects and rapid ?elding programs to acquire new or improved capabilities. Rapid prototyping projects and rapid ?elding programs are excluded from the Major Defense Acquisition Program (MDAP) de?nition in 10 U.S.C. 243 and, therefore, exempt from complying with the MDAP requirements set forth in 10 U.S.C. Chapter 144. Similarly, rapid prototyping projects and rapid ?elding programs are not subject to the Joint Capabilities Integration Development System (JCIDS) or Department of Defense Instruction 5000.02 policies and procedures. Program Managers (PMs) are encouraged to request additional waivers from statutory or regulatory requirements on a case-by-case basis, as appropriate, to accelerate a rapid prototyping project or rapid ?elding program. The Middle Tier Acquisition statute authorizes the use of special transfer authorities and authorizes the creation of rapid prototyping ?mds for both the and the DON to facilitate program initiation and acceleration within the budget year of execution. The DON will continue to work with Congress to appropriate funding to the DON Rapid Prototyping Fund in order to enable Middle Tier Acquisition. Until appropriated, the DON will maximize current budget authorities to accelerate program execution. This guidance establishes the policies and procedures for rapid prototyping projects and rapid ?elding programs. 2. Implementation 2.1. Rapid Prototyping Pathway. The rapid prototyping pathway shall provide for the use of innovative technologies to rapidly develop ?eldable prototypes to demonstrate new capabilities and meet emerging military needs. The objective of a rapid prototyping project under this pathway shall be to ?eld a prototype that can be demonstrated in an operational environment and provide for a residual operational capability within ?ve years of initiation. The PM should review the documentation in Table 2-1 and make recommendations to the Approval Authority to identify which documents best support project execution when utilizing the Rapid Prototyping pathway. When rapid prototyping projects have successfully demonstrated the war?ghting need in an Operationally relevant environment, they may enter the Middle Tier Acquisition under the Rapid Fielding pathway. Table 2-1. Rapid Prototyping Documentation Documentation . - Elements to Address Approval Authority Acquisition Decision ASN Memorandum Prototyping Plan - Prototype Acquisition Strategy ADA - Performance Goals - Knowledge Points - System Experimentation and Assessment Plan - Prototype Deployment Strategy Acquisition Plan When required by the Federal Acquisition ADA Regulation (FAR) Attachment 1 THE ASSISTANT SECRETARY OF THE NAVY (RESEARCH, DEVELOPMENT AND WASHINGTON, DC 20350-1000 2 at 2018 MEMORANDUM FOR DISTRIBUTION SUBJECT: Middle Tier Acquisition and Acquisition Agility Guidance Reference: Fiscal Year 2016 National Defense Authorization Act (Public Law 114?92) Fiscal Year 2017 National Defense Authorization Act (Public Law 114-328) USD Memo? ?Middle Tier of/thuisition (Rapid Prototypingi? Rapid Fielding) Interim Authority and Guidance" ASN (RDSLA) Memo, ?Designation of the Deputy Assistant Secretary of the Navy for Research, Development, Test and Evaluation to Lead Implementation of Accelerated Acquisition", Nov 8, 2017 I hereby direct that the Middle Tier Acquisition and Acquisition Agility authorities provided under references through will be implemented within the Department of the Navy (DON) consistent with the attached Middle Tier Acquisition Interim Guidance and Acquisition Agility Interim Guidance. Reference authorizes the Secretary of Defense and Service Secretaries to establish Middle Tier Acquisition pathways for Rapid Prototyping and Rapid Fielding. Reference authorizes Acquisition Agility aimed at speeding the development and transition of advanced technology and high risk components through a separate and distinct path of ?component acquisition" characterized by rapid prototyping. The DON will follow an incremental approach to implementation. We will use these authorities to enable speed and agility, while maintaining appropriate accountability, oversight and transparency. We will continue to collaborate with the Offices of the Secretary of Defense (OSD) to better align policies and regulations and evolve the DON policy accordingly. The DON implementation plan will include a series ofpilot programs to exercise these authorities and inform policy development. These pilot programs will be executed utilizing the interim acquisition guidance attached. As we learn from these pilot programs, we will provide future guidance to support full implementation of these authorities into the DON Acquisition System. Program Executive Of?cers with pilot program candidates will work with their product Deputy Assistant Secretaries of the Navy (DASN) to be evaluated for acceleration as a pilot program. SUBJECT: Implementation of Middle Tier and Acquisition Agility Guidance In addition to this guidance, I am directing the Systems Commands and Program Executive Of?ces to assess their organizations? contracting, technical, legal, and ?nancial processes to facilitate the acceleration of programs when appropriate. Effective implementation of these authorities will require learning and changing the way we do acquisition. Until more formal training is available, points of contact from each of the DASNs, per reference are available to support the acquisition workforce in implementation. The DASN for Research, Development, Test and Evaluation will continue to provide a ?War Room? to facilitate familiarization of the new authorities and implementation of this plan. For questions related to this implementation plan, please contact Mr. Peter Manternach, peter.manternach@navy.mil, (703) 413-0702 or Ms. Kristen Alvarez, kristen.alvaez@navy.mil, (703) 695-7949. a .- eurts Attachments: As stated cc: CNO CMC PMD ASN PCD ASN AGC ASN DASNs DC, OPNAV N9 ONR PEOs NAVSEASYSCOM DACM ASN Middle Tier Acquisition Interim Guidance 1. Description. Section 804 of the Fiscal Year (FY) 2016 National Defense Authorization Act (NDAA), as amended in FY 17 NDAA (codi?ed at 10 U.S.C. 2302 note), authorizes a Middle Tier acquisition pathway, separate from the traditional acquisition system, for rapid prototyping projects and rapid ?elding programs to acquire new or improved capabilities. Rapid prototyping projects and rapid ?elding programs are excluded from the Major Defense Acquisition Program (MDAP) de?nition in 10 U.S.C. 243 and, therefore, exempt from complying with the MDAP requirements set forth in 10 U.S.C. Chapter 144. Similarly, rapid prototyping projects and rapid ?elding programs are not subject to the Joint Capabilities Integration Development System (JCIDS) or Department of Defense (DOD) Instruction 5000.02 policies and procedures. Program Managers (PMs) are encouraged to request additional waivers from statutory or regulatory requirements on a case-by-case basis, as appropriate, to accelerate a rapid prototyping project or rapid ?elding program. The Middle Tier Acquisition statute authorizes the use of special transfer authorities and authorizes the creation of rapid prototyping ?mds for both the and the DON to facilitate program initiation and acceleration within the budget year of execution. The DON will continue to work with Congress to appropriate funding to the DON Rapid Prototyping Fund in order to enable Middle Tier Acquisition. Until appropriated, the DON will maximize current budget authorities to accelerate program execution. This guidance establishes the policies and procedures for rapid prototyping projects and rapid ?elding programs. 2. Implementation 2.1. Rapid Prototyping Pathway. The rapid prototyping pathway shall provide for the use of innovative technologies to rapidly develop ?eldable prototypes to demonstrate new capabilities and meet emerging military needs. The objective of a rapid prototyping project under this pathway shall be to ?eld a prototype that can be demonstrated in an operational environment and provide for a residual operational capability within ?ve years of initiation. The PM should review the documentation in Table 2-1 and make recommendations to the Approval Authority to identify which documents best support project execution when utilizing the Rapid Prototyping pathway. When rapid prototyping projects have success?illy demonstrated the war?ghting need in an operationally relevant environment, they may enter the Middle Tier Acquisition under the Rapid Fielding pathway. Table 2-1. Rapid Prototyping Documentation Documentation . - . - Elements to Address Approval Authority Acquisition Decision ASN Memorandum Prototyping Plan - Prototype Acquisition Strategy ADA - Performance Goals Knowledge Points - System Experimentation and Assessment Plan - Prototype Deployment Strategy Acquisition Plan When required by the Federal Acquisition ADA Regulation (FAR) Attachment 1 Capability - Top Level Requirements Document -or- Responsible DCNO Documentation JEONS, JUONS, Service ONS -or- -or- DC, (within 6 months of - CDD or CPD initiation) ADA?ACquisition Decision Authority . DCNO- -Deputy Chief of Naval Operations. . - DC, ?Deputy Commandant for Capability Development Integration 2.2.Rapid Fielding Pathway. The rapid ?elding pathway shall provide for the use of proven technologies to deploy production quantities of new or upgraded systems where minimal development is required. The objective of an acquisition program under this pathway shall be to begin production within six (6) months and complete ?elding within ?ve (5) years of initiation. The PM should review the documentation in Table 2-2 and 2-3 and make recommendations to the Approval Authority to identify which documents will best support program execution when utilizing the Rapid Fielding pathway. In order to optimize production and ?elding timelines, the PM may tailor timelines for developing program documents that are not required for program initialization. The documentation tailoring plan shall be included in Rapid Fielding plan. Rapid Fielding programs under oversight, as determined by the Director of Operational Test and Evaluation may have additional compliance requirements. Program Managers should engage the Operational Test Community as early as possible. Table 2-2. Rapid Fielding Documentation - Statutory Documentation Elements to Address . Approval Authority Acquisition Strategy - Address applicable elements: 0 Acquisition Approach 0 Bene?t Analysis and Determination 0 Business Strategy 0 Contracting Strategy (including Contract Type) Cooperative Opportunities General Equipment Valuation 0 Industrial Base Capability Considerations .- Not to exceed 20 pages in length ADA Acquisition Plan When required by the Federal Acquisition Regulation (FAR). May be combined with Acquisition Strategy ADA Core Log Determination Workload Estimate May be summarized in acquisition strategy ADA Frequency Allocation For all systems/equipment that use the electromagnetic spectrum while operating in the United States and its possessions. DON CIO Low-Rate Initial Production Quantity Production Quantities will be addressed in Acquisition Decision Memorandum ADA Post Implementation Review Ful?lled by disposition decision to sustain Rapid Fielding program or transition to Program of Record ADA Attachment 1 Cyber Security Strategy Statutory for only mission critical or ADA mission essential IT systems Clinger Cohen Act Statutory for all programs that acquire IT DON CIO Compliance systems PESHE and Not required for software programs with PM 12114 Compliance Schedule no hardware components ADA - Acquisition Decision Authority PM Program Manager DON C10 Department of the Navy Chief Informationlot?cer Table 2-3. Rapid Fielding Documentation - Regulatory Documentation Elements to Address Approval Authority Acquisition Decision - Acquisition Decision Memorandum - Program Cost Estimate - Rapid Fielding Quantities (ful?lls Low- Rate Initial Production Quantity statute) - Schedule IT Deployment Strategy Address applicable elements: DON CIO - IT NSS Interoperability Cert - Spectrum Supportability Risk *Authority to Assessment Operate granted per - Bandwidth Requirement Review DODI 8510.01 - Cyber Security Strategy (non? mission critical or mission essential IT systems) - Program Protection Plan - Waveform Assessment Application . Capability Documentation - Top Level Requirements Document -or- Responsible DCNO (within 6 months of initiation) - EONS, JUONS, Service ONS -or- -or- DC, - CDD or CPD Concept of Operations Responsible (CONOPS) -or-DC, Course of Action-Analysis Replaces and serves as ADA Defense Intel Threat Library DIA Operational Test Plan Service OTA Operational Test Report Service OTA Systems Engineering Strategy PM Sustainment Strategy PM Training Systems Strategy PM ADA Acquisition Decision Authority OTA ?-?Operational Test Authority PM .- Program Manager DCNO- -Deputy Chief of Naval Operations DC, -Deputy Commandant for Capability Development Integration DON ?Department of the Navy Chief Information Of?cer . - a Defense Intelligence Agency lIn coordination with Naval Warfare Command and War?ghting Development Centers 2.3. Transition to Acquisition Program. Where production exceeds the ?ve (5) year limit of Rapid Fielding, or the program would be more appropriately managed under a traditional Attachment 1 acquisition pathway, the Acquisition Decision Authority may transition the program to a traditional acquisition pathway at an appropriate Milestone. Under the 5000.02 and JCIDS, such programs shall be subject to, appropriately tailored where possible, the statutory and regulatory requirements for their respective Acquisition Category (ACAT) designation. 3. Initiation. The Middle Tier Acquisition pathways require rapid prototyping projects and rapid ?elding programs to be completed within ?ve (5) years of initiation. For rapid ?elding, production must be scheduled to begin within six (6) months of initiation. Each pathway requires a distinct merit based assessment to ensure the transparency, accountability and alignment within the Navy and Marine Corps acquisition, requirements, and resourcing communities. will initiate all Middle Tier Acquisition programs .by an Acquisition Decision Memorandum and may designate Acquisition Decision Authority at that time. A Program Manager will be designated and report directly to Acquisition Decision Authority. 3.1. Rapid Prototyping a. Merit Based Selections. In order to initiate Rapid Prototyping projects under the Middle Tier Acquisition, each project shall be selected under a Merit Based Selection framework. The Merit Based selection will review the war?ghting problem, the overall capability required, and a solution trade space within which to prototype. The DON will initiate Rapid Prototyping projects when the prototyping effort has: (1) Alignment with a high priority military capability need; (2) A de?ned and manageable capability, cost, schedule, feasibility of success, and technical risk; (3) Available and stable funding through the normal Flaming, Programming, Budgeting and Execution (PPBE) process, Above and Below Threshold Reprogramming, and/or through the use of the Rapid Acquisition Special Transfer Authorities; (4) Opportunity to reduce total ownership costs to include reduction in development, production, and sustainment costs as compared to development through the Defense Acquisition System b. Rapid Prototyping Initiation. The rapid prototyping pathway can be initiated in support of one or more of the following categories: (I) Emergent Strategic Needs. Those needs that are emergent strategical Fleet/Forces needs not documented by a capability requirement through the normal Capability Based Assessment Process, nor suf?cient funds programmed through the normal PPBE process to execute in the year the need was identi?ed. Emergent Strategic Needs initiation is consistent with the Secretary of the Navy Instruction (SECNAVIN ST) 5000.42, Department of the Navy Accelerated Acquisition for the Rapid Development, Demonstration and Fielding of Capability for initiating accelerated acquisition programs. Attachment 1 (2) Emergent Technologies. New wartighting capabilities that have been identified as an offsetting or disruptive warfighting needs through Future Naval Capability (FNC), Innovative Naval Prototype UNPS), Joint Capability Technology Demonstrations Advance Naval Technology Exercise (ANTX), Vt?artighter Experiments, or similar information technology development advancements. Documented Needs. Projects that currently have a validated requirement documented via the Joint Requirements Oversight Council (.IROC), Joint Rapid Acquisition Cell RAC). the Chiefof Naval Operations or Commandant of the Marine Corps Operational Needs process requiring acceleration to meet a wartighting need. Table 3.1 Initiation Decision Category Initiation Decision Merit Based Assessment Elements Alignment with high 1 Navy AA Bot) priority need i USMC AA I I De?ned capability. cost Emergent Strategic Needs schedule. feasibility, and See technical risks 5000.42] Available and stable funding II Total ownership cost savings N9 Emergent Technologies -or- 8: DAEN. CDELI (RD De?ned capability, cost Accelerating schedule, and capabilities -1 a technical . fr om CDDICPD N8, N4, . . {Available and Istable funding Documented JEONs Total cost savmgs Needs JUONS -or- Service UONS CD521 Resource 13130 I Available and stable funding Sponsor Total ownership cost savings 3.2. Rapid Fielding Pathways. a. Merit Based Selection. In order to initiate Rapid Fielding efforts under the Middle Tier Acquisition, each project shall be selected under a Merit Based Selection framework. The Merit Based selection will review the warlighting problem, the overall capability required, and a solution trade space within which to prototype. The DON will initiate Rapid Fielding efforts when the prototyping effort has: Continued alignment with a high priority military capability need; 2) A defined and manageable capability, cost, schedule- concept ofsupportability, and technical risk for a designated number of fielded systems; Attachment 1 (3) Available and stable funding through the normal PPBE process, internal Above and Below Threshold Reprogramming, or through the use of the Rapid Acquisition Special Transfer Authorities; (4) Opportunity to reduce total ownership costs to include reduction in development, production, and sustainment costs as compared to development through the Defense Acquisition System (5) A con?guration of the solution that was demonstrated in an operationally and relevant environment . 4. Funding. 4.1. Rapid Prototyping Funding. Rapid Prototyping projects and Rapid Fielding programs may be funded through one or more of the following paths: a. Program Appropriated Funding. Programs with suf?cient, and appropriate ?rnding sources already appropriated through PPBE process. Rapid Fielding programs should utilize the PPBE process when time permits. b. Department of the Navy (DON) Rapid Prototyping Fund. The DON is authorized to establish a ?exible ?mding account that will contain appropriated ?inds to be distributed as warfighting needs arise. Once established, programs can be funded by the DON Rapid Prototyping Fund only when designated by their service Accelerated Acquisition Board of Directors (AA The DON Rapid Prototyping Fund can fund both rapid prototyping and rapid ?elding pathways. c. Of?ce of the Secretary of Defense (OSD) Rapid Prototyping Fund. The statute authorized the Of?ce of the Secretary of Defense (OSD) to establish a ?exible funding account that will contain appropriated funds to be used to initiate projects within various Components and Services focused on Emergent Technologies category of Rapid Prototyping. DASN will coordinate with OSD for distribution and initiation of projects under this funding source. The OSD Rapid Prototyping Fund can only fund rapid prototyping pathway. d. Other Prototype Funding Sources. Other sources may be used to initiate Rapid Prototyping efforts to include special transfer authorities under Rapid Acquisition Authorities of the Secretary of Defense, Below Threshold Reprogramming within the DON, and Above Threshold Reprogramming process with Congress. 4.2. Reporting: If projects or programs utilize Special Transfer Authorities under the Rapid Acquisition Authority. The Secretary of Defense shall notify the Congressional Committees within ten (1 0) days of the transfer. 5. Capability Requirements. All Middle Tier Acquisition projects shall have documented capability requirements, not more than six months from when the project was initiated, from the requirement community. At a minimum, a Top Level Requirements Documentation will outline Attachment the minimum viable product that is acceptable to the operational force. For Rapid Fielding, the Top Level Requirements shall include the production quantity required to meet the war?ghting need within the ?rst ?ve (5) years of service. 6. Transition. Successful Rapid Prototyping projects not transitioning into Rapid Fielding, shall transition into existing acquisition program, a new acquisition program, or the residual capability can be sustained in the ?eld. 6.1. Fielding of Rapid Prototypes. If the Acquisition Decision Authority and the capability requirement community want to continue to operate the initial Rapid Prototypes in the ?eld, the Program Manager (PM) is not required to enter Rapid Fielding under this guidance. The PM will develop the appropriate sustainment package to support the items in the ?eld until they are dispositioned. 6.2. Transition to Traditional Acquisition. Programs determined by the Acquisition Decision Authority to transition to the traditional acquisition system shall follow the guidance under 5000.02 and JCIDS Attachment 1 Acquisition Agility Interim Guidance 1. Description. Section 805 and 806 of the FY 2017 NDAA, collectively referred to as Department of Defense Acquisition Agility, amended Title 10, United States Code, Chapter 144, Major Defense Acquisition Programs (MDAPs). These amendments fundamentally alter the way MDAPs will be executed. Speci?cally, section 2446a of Chapter 144B now states that MDAPs that receive Milestone A or Milestone approval a?er January 1, 2019 shall be designed and deve10ped, to the maximum extent practicable, with a modular open system approach (MOSA) to enable incremental development and enhance competition, innovation, and interoperability. Additionally, section 2447a of Chapter 1443 requires the Secretary of Defense to set forth in budget exhibits the amounts requested for advanced component development and prototype activities for the development, prototyping, and experimentation of weapon system components or other technologies, including those based on commercial items and technologies, separate from acquisition programs of record. When coupled with the MOSA requirements of section 2446a, this allows the Milestone Decision Authorities (MDA) for MDAPs to separate higher risk component and technology maturation efforts from the major system platform development effort. These authorities allow the MDAP platform to move faster through the traditional acquisition process as addressed in DoDl $000.02 by maturing advanced technologies in a parallel path. The component and technology advancement can now assume more risk to push the state-of-the-art, and incrementally integrate into the platform when ready. These component and technology prototypes will be developed separately from, but aligned with, the MDAP. These prototyping efforts will not assume the ACAT designation of the platform and will not be subject to the requirements of 5000.02 or the Joint Capability Integration Development System (J CIDS). These prototyping efforts will follow an accelerated and agile pathway outlined in this DON guidance while ensuring transparency, oversight, and accountability. 2. Key Tenets 2.1. Definitions. As de?ned in 10 U.S.C. Chapter 1443, Section 2446a. a. Major System Platform. The Major System Platform is the highest level structure of a major weapon system that is not physically mounted or installed into a higher level structure and on which a major system component can be physically mounted or installed. Major System Component (1) A high level or assembly, including hardware, software, or an integrated assembly of both, that can be mounted or installed on a major system platform through well-de?ned major system interfaces; and (2) Includes a or assembly that is likely to have additional capability requirements, is likely to change because of evolving technology or threat, is needed for interoperability, facilitates incremental deployment of capability, or is expected to be replaced by another major systems component. Attachment 2 c. Major System Interface (1) A shared boundary between a major system platform and a major system component, between major system components, or between major system platforms, de?ned by various physical, logical, and functional characteristics, such as electrical, mechanical, ?uidic, optical, radio frequency, data, networking, or software elements; and (2) Is characterized clearly in terms of form, function, and the content that ?ows across the interface in order to enable technological innovation, incremental improvements, integration, and interoperability. (1. Modular Open System Approach (MOSA). For an MDAP, a MOSA is an integrated business and technical strategy that? l) Employs a modular design that uses major system interfaces between a major system platform and a major system component, between major system components, or between major system platforms; (2) Is subjected to veri?cation to ensure major system interfaces comply with, if available and suitable, widely supported and consensus-based standards; (3) Uses a system architecture that allows severable major system components at the appropriate level to be incrementally added, removed, or replaced throughout the life cycle of a major system platform to afford opportunities for enhanced competition and innovation while yielding? (A) signi?cant cost savings or avoidance; (B) schedule reduction; (C) opportunities for technical upgrades; (D) increased interoperability, including system of systems interoperability and mission integration; or (E) other bene?ts during the sustainment phase of a major weapon system; and (4) Complies with the technical data rights requirements of 10 U.S.C. 2320. 2.2. Application of MOSA. MOSA is an integrated business and technical strategy key to incrementally evolve the MDAP platform when technology becomes available. The most recent changes to 10 U.S.C. and the 5000.02 Chapter 144 strengthen the use of MOSA on MDAPs to the maximum extent practicable. This includes provisions for Program Capability Documents (ICD, CDD, CPD) to characterize the likely evolution of the system, key changes to the Analysis of Alternatives, requirements in Request for Proposals, Milestone 2366b certi?cation, and the requirement to be include in Selected Acquisition Reports (SAR). Program Managers shall develop MOSAs that comply with the de?nitions in this guidance. Program Attachment 2 Managers also shall follow the Naval Open Architecture Contract Guidebook for Program Managers, Version 20, dated 30 June 2010, This guidance will take precedence over the guidebook in the event of event of any conflict between them. 2.3. Application of Data Rights. In order to facilitate the maximum trade space for future technology development, it is critical that the platforms consider the appropriate Data Rights. Current Data Rights Strategy requirements shall address future Acquisition Agility increments and comply with 10 U.S.C. 2320. 3. Implementation 3.1. Component Prototyping. Regulatory documentation required for initiation of a Component/Technology Prototype is located in Table 3-1. All required documentation and content is tailorable by the Approval Authority. a. Replacement Components. De?ned as components already established under the platform functional, allocated, and production baseline that are being replaced to increase the affordability of the MDAP or provide an incremental increase in capabilities. These capabilities should already be captured in the capability document of the platform. b. Additional Component. De?ned as components not already established under the platform functional, allocated, and product baseline that provide an additional functionality to the system and not be captured in current capability documentation. Table Acquisition Agility Prototyping Documentation Documentation - Elements to Address - Approval Authority Prototype Decision Milestone Decision Memorandum Authority Prototyping Plan - Prototyping Approach Acquisition Decision - Performance Goals Authority - Knowledge Points - Demonstration Experimentation Plan - Prototype Deployment Strategy - Acquisition Plan Transition - Technical data required at transition Milestone Decision Agreement - Performance veri?cation requirements Authority - Interface information required for certi?cations Capability - Top Level Component Requirement Portfolio Prototyping Documentation Document Board Chairman Attachment 2 3.2. Transition to MDAP platform. Regulatory documentation required at transition is located in Table 3-2. Table 3-2 Acquisition Agility Prototype Transition Documentation Documentation Elements to Address Approval Authority Transition Plan - Transition Approach - Milestone Decision - Operational Test Approach Authority - Unique supportability requirements - Acquisition Plan Veri?cation Report - Prototype . Milestone Decision Demonstration/Experimentation results Authority - Prototype performance veri?cation results - Completed certi?cations - Interface compliance 4. Component/Technology Prototype Initiation. Component [Technology Prototypes under the Acquisition Agility pathway must be less than $10 Million, per prototyping effort, and take no longer than two (2) years. The Secretary of the Navy can approve up to $50 Million, per prototyping effort and must provide noti?cation to Congress. These pathway requirements only pertain to the component/technology prototyping effort. Program Managers may utilize Middle Tier Acquisition pathway for prototypes exceeding these limitations. 4.1. Portfolio Prototyping Board. When established, the portfolio oversight board(s) will make recommendation to for projects to initiate under Acquisition Agility pathway. Until the Portfolio Prototyping Boards are established, DASN will be responsible for the executing the responsibilities of the Portfolio Prototyping Board. The Portfolio Prototyping Board will be reSponsible for the following: a. Issue strategic plan every three (3) years that prioritizes capability and weapon systems. b. Make recommendations on annual funding levels for component prototyping efforts. c. Submit semiannual noti?cations to Congress. 4.2. Merit Based Selection. a. Component/Technology Prototype. In order to initiate Component or Technology Prototyping efforts under the Acquisition Agility pathway, each project shall be selected under a Merit Based Selection framework. The Merit Based selection will de?ne the war?ghting problem, the capability required, and a solution type to meet and the needs. The DON will only initiate Component/Technology Prototyping efforts when prototyping effort has: Attachment 2 A high priority war?ghter need. (2) Available and stable funding. (3) A component and technology that is operationally and technically relevant within two (2) years. (4) The ability to be successfully demonstrated in a relevant enviromnent within two (2) years. (5) A cost-effective?solution that will address the war?ghter needs. 5. Transition to Platform. The Program Manager will implement the Component/Technology Prototype into the platform utilizing their existing configuration management procedures. Prior to transition, the Program Manager will seek approval through the MDAP Con?guration Steering Board. The Program Manager will work with the Oversight organization to ensure Operational Testing, and Supportability requirements are updated as required. Under the authorities of the Acquisition Agility, ASN or delegated Acquisition Decision Authority, may authorize award of a follow-on production contract or other transaction without the use of competitive procedures if there were competitive procedures used in the original project selection. Selection to integrate a successful prototype into the platform, at a minimum, will evaluate: The component or technology remains a high priority war?ghter need or will reduce the cost of the weapons system platform. (2) Available and stable funding. (3) The prototype was demonstrated in a relevant environment. 6. Funding. 6.1. Prototyping and Experimentation Funding. Until ?exible funding constructs are established, all Acquisition Agility projects will utilize program appropriated funding with the standard reprogramming authorities as required. 6.2. Platform Transition Funding a. Special Transfer Authorities. When available, the SECNAV may authorize transfer of procurement funds up to $50 Million, over a two (2) year period to fund low-rate initial production of the Component/Technology Prototype. b. Platform Permanent Alterations. Until ?exible funding constructs are established, all Acquisition Agility projects will utilize program appropriated funding with the normal reprogramming authorities by the platform. Attachment 2 c. Full Rate Production and Sustainment. Full-rate production will be funded through the normal Planning, Programming, Budgeting, and Execution (PPBE) Process by the platform. 7. Budget Displays. Research, Development, Test and Evaluation requested amounts for the acquisition program of record shall be separately displayed from the development, prototyping, and experiment of the weapon system components or technologies. Future budget display guidance will be distributed by DASN 8. Cost Accounting. Until guidance is published by OSD, the MDAP will account for all cost changes as a result of Component/Technology Prototype transitioning to the platform. All component prototyping conducted outside of the MDAP will not be accounted for as a part of the MDAP Acquisition Program Baseline and reporting. 9. Capability Documents. In coordination with the appropriate OPNAV or requirements and resource sponsor, the Portfolio Prototyping Board Chairman shall approve a Component Requirement Document outlining component/technology performance goals, interoperability requirements, and transition timing requirements. 10. Reporting. 10.1. Component Prototyping Selection and Status. The Portfolio Prototyping Board shall submit a semi-annual noti?cation through DASN for consolidation and submission to the congressional committees containing the following: a. Projects initiated in the preceding six months, including an explanation of the project and its required funding. b. The results achieved from Component/Technology Prototype and technology projects completed and tested during the preceding six (6) months. 10.2. Component Prototyping Selection of greater than $10 Million. The Secretary of the Navy (SECNAV) is required to notify Congress if the Component/Technology Prototype exceeds $10 Million. The Portfolio Prototyping Board shall submit to the SECNAV the following information within ten (10) days of initiation past this threshold: a. The project and description b. Expected ?rnding for the project c. A statement of the anticipated outcome of the project. 10.3. Component Transition to Platform. The Program Managers shall submit a noti?cation to their associated DASN within ten (10) days of selection of a component or technology project follow-on production contract. It will include a brief description of the rapid Attachment 2 ?elding project. The DASN will submit through ASN a noti?cation to Congress of the transition within thirty (30) days. Attachment 2 INFORMATION PAPER March 27, 2018 SUBJECT: Middle Tier and Acquisition Agility Pilot Programs. 1. Purpose. The purpose of these pilot programs is to demonstrate alternate pathways to deliver timely and suf?cient capabilities, gain Congressional Authorizer?s trust that the Department of the Navy (DON) is agile enough to accelerated programs when required, and start the process of energizing our industrial base to accelerate deliver of needed technology. Conversely, these pilot programs will con?rm the DON has adequate oversight, accountability of programs, sound strategies to support communication, synergy within the department, and transparency to Congressional Committees. 2. Middle Tier Acquisition Pilot Programs 2.1. Phase 1. Phase I will focus on rapid prototyping program initiation, establishment of capability requirements, and funding enablers and constraints of the Rapid Prototyping element of Middle Tier Acquisition. The DON will pilot 2-5 Rapid Prototyping effort in the following Rapid Prototyping Pathways. a. Emergent Strategic Needs b. Emergent Technology. c. Documented Needs 2.2. Phase 11. Phase II will focus on Rapid Fielding program initiation, initiation of a Rapid Prototyping project from the Navy?s Rapid Prototyping Fund 3. Acquisition Agility 3.1. Portfolio Prototyping Board. The Assistant Secretary of the Navy for Research, Development and Acquisition in coordination with Deputy Chief of Naval Operations for Warfare Systems (N9) and Deputy Commandant of the Maine Corps for Capabilities Development and Integration (DC, will select 1- 2 currently chartered oversight boards composed of both the requirements, acquisition, and technical community to pilot the procedures within this guidance to address the following items: a. Selection process and initiation of projects b. Funding constructs 3.2. Component Prototypes. in coordination with N9 and DC, will select 2-5 pilot projects to develop component prototypes for future integration under the procedures within this guidance and will address the following items: - a. Regulatory documentation required to communicate within the DON and OSD partners b. Validation requirements of the component prototype prior to transition to the platform. 3.3. MDAP Platform. in coordination with N9 and DC, will select 1-3 MDAPs to pilot the transition of a component prototype into the platform and address the following items: a. Data requirements from the component prototyping performer required for adequate transition into the platform. b. Operational testing strategies to adhere to the current oversight authorities. c. Inform on the technical and business barriers of implementing Modular Systems Open Architecture. 4. Lessons Learned. The 804/806 Implementation Working Group will follow the pilot programs and consolidate the lessons learned and metric for future guidance distribution. Prepared by: Pete Mantemach,Action Of?cer 703-614-0663, peter.manternach@navy.mil Approved by: Mr. William Bray, 571-256-4981, william.p.bray@navy.mil DEPARTMENT OF THE NAVY OFFICE OF THE: ASSISTANT SECRETARY (RESEARCH. DEVELOPMENT AND NAVY PENTAGON emsrurtoron DC 20350-1000 s-P; qs-b Law MEMORANDUM 130R DEPUTY ASSISTANT SECRETARY OF THE NAVY 170R TEST AND SUBJECT: Designation ol'the Deputy Assistant Secretary of the Navy for Research. Development. 'feSt anti l'isl'aluation to Lead Implementation ofAccelerated Acquisition Reference: Fiscal Year 2016 National Defense Authorization Act (NDAA) (Public Law 114?92}. 804 codified in 10 U.S.C. 2302 note Fiscal Year 201? NDAA (Pub. Law 114-328}. 805 codi?ed in 10 use. 24413;: a 2446:; 2017 NDAA. 306(1?ub. 114-328 codi?ed in 10 U.S.C {$244711 ((1)201? NDAA. 806 (Pub. Law 114-328 codified in 10 U.S.C 2447b 2017 NDAA. 806 (Pub. Law 114-328 codified in 10 U.S.C ?2447c 806 (Pub. Law 114-328 codi?ed 10 U.S.C 244m 2017' NDAA. 897(1?1111. Law 114-323 codi?ed in 10 U.S.C 2302 note I am directing the Deputy Assistant Secretary oftlte Navy for Research. Development. Test. and liivaluatitm to lead a team from each oftlte DASNs to analyze and develop an action plan for implementing the congressional Acquisition Agility attd Mid-'l'ier Acquisition laws itt references and The outcome will enable department wide deployment of the new accelerated acquisition authorities. All DASNs will nominate an acquisition subject matter expert representative to support in this effort to address the following topics: 1. Mid-tier Acquisition (reference a. Implementation ofSI'iCDI-il? Procedures in accordance with guidance for a "middle tier" ofacquisition programs intended to be completed in a period of two to ?ve years; b. Initiation ofa project under ntiddlc tier proton-?ping or ?elding pathways through special transfer authorities from the D01) Rapid Prototyping l-?und: c. Notification to defense committees: Establishment and administration of Department of New Speci?c Rapid Prototyping Fund (reference 3. Acquisition Agility (references a. Incremental development through Modular Open Systems Architecture (reference SUBJECT: Designation of the Deputy Assistant Secretary of the Navy for Research, Development, Test and Evaluation to Lead Implementation of Accelerated Acquisition Weapon system components or technology prototype project budget displays (reference Oversight board for managing prototype projects for weapon system components and other technologies and (reference Selection of prototype projects through a merit-based selection process (reference Special funds transfer authority for low-rate initial production (reference Selection of production following prototype project without the use of competitive procedures (reference (0) The effort is considered complete when an action plan and implementation schedule is developed and briefed to me. It is expected that I will participate in interim reviews for further guidance and re?nement as outlined below: cc: CNO CMC 30 Days from Memorandum Signature: Form the DASN representative working group to provide recommendations on the tepics outlined in this memorandum. Provide an interim review of the scope and understanding of the law. I will provide direction on the extent and timing of the implementation of guidance. 45 Days from Memorandum Signature: Review of draft guidance and implementation schedule. 60 Days from Memorandum Signature: Issue draft guidance for review with the Chief of Naval Operations, the Commandant of the Marine Corps, Systems Commands, and Program Executive Offices. 90 Days from Memorandum Signature: Implementation of communication and training plan. Allison F. Stiller Acting PMD ASN ASN AGC DASN (SHIPS, AIR, UXS, IPO, AP) DC, N9