THE UNIVERSITY OF THE ARMY 1775
Headquarters
Department of the Army
Washington, DC
28 November 2023

*Army Regulation 70–1

Effective 28 November 2023

Research, Development, and Acquisition

Army Operation of the Adaptive Acquisition Framework

By Order of the Secretary of the Army:

RANDY A. GEORGE

General, United States Army

Chief of Staff

MARK F. AVERILL

Administrative Assistant to the

Secretary of the Army

History. This publication is a mandated revision. The portions affected by this revision are listed in the summary of change.

Authorities. The authorities for this regulation are 10 USCUSCUnited States Code 4271, DoDD 5000.01, DoDD 5105.84, DoDI 5000.02, DoDI 5000.73, DoDI 5000.74, DoDI 5000.75, DoDI 5000.80, DoDI 5000.81, DoDI 5000.82, DoDI 5000.83, DoDI 5000.85, DoDI 5000.87, DoDI 5000.88, DoDI 5000.89, DoDI 5000.90, DoDI 5000.91, DoDI 5000.95, and DoDI 5010.44.

Applicability. This regulation applies to the Regular Army, the Army National Guard/Army National Guard of the United States, and the U.S. Army Reserve, unless otherwise stated.

Proponent and exception authority. The proponent of this regulation is the Assistant Secretary of the Army (Acquisition, Logistics and Technology). The proponent has the authority to approve exceptions or waivers to this regulation that are consistent with controlling law and regulations. The proponent may delegate this approval authority, in writing, to a division chief within the proponent agency or its direct reporting unit or field operating agency in the grade of colonel or the civilian equivalent. Activities may request a waiver to this regulation by providing justification that includes a full analysis of the expected benefits and must include formal review by the activity's senior legal officer. All waiver requests will be endorsed by the commander or senior leader of the requesting activity and forwarded through their higher headquarters to the policy proponent. Refer to AR 25–30 for specific requirements.

Army internal control process. This regulation contains internal control provisions in accordance with AR 11–2 and identifies key internal controls that must be evaluated (see appendixes C and D).

Suggested improvements. Users are invited to send comments and suggested improvements on DA FormDA FormDepartment of the Army form 2028 (Recommended Changes to Publications and Blank Forms) directly to the Assistant Secretary of the Army (Acquisition, Logistics and Technology) (SAAL–ZF), 103 Army Pentagon, 2D516, Washington, DC 20310–0103 or usarmy.pentagon.hqda-asa-alt.mesg.asa-alt-publication-updates@army.mil.

Committee management approval. AR 15–39 requires the proponent to justify establishing/continuing committee(s), coordinate draft publications, and coordinate changes in committee status with the Office of the Administrative Assistant to the Secretary of the Army, Special Programs Directorate at email usarmy.pentagon.hqda-hsa.mbx.committee-management@army.mil. Further, if it is determined that an established "group" identified within this regulation later takes on the characteristics of a committee as found in AR 15–39, then the proponent will follow AR 15–39 requirements for establishing and continuing the group as a committee.

Distribution. This regulation is available in electronic media only and is intended for the Regular Army, the Army National Guard/Army National Guard of the United States, and the U.S. Army Reserve.

*This regulation supersedes AR 70–1, dated 10 August 2018.

AR 70–1 • 28 November 2023

UNCLASSIFIED

Pathway Programs

Decision Reviews

Decision Reviews

Acquisition position A civilian or military position in DoD that is coded an acquisition position and includes acquisition func- tions as defined in 10 USCUSCUnited States Code Chapter 87, as the predominant (greater than 50 percent) duty in a specific functional area. (see DoDI 5000.66).

Acquisition program A directed, funded effort that provides a new, improved, or continuing materiel, weapon, information sys- tem, or service capability in response to an approved need.

Architecture The structure of components, their relationships, and the principles and guidelines governing their design and evolution over time. For example, a technical architecture identifies the services, interfaces, stand- ards, and their relationships. It provides the technical guidelines for implementation of systems upon which engineering specifications are based, common building blocks are built, and product lines are de- veloped.

Armaments cooperation Cooperative research, development, test, and evaluation of defense technologies, systems, or equip- ment, such as the Coalition Warfare Initiative; joint production follow-on support of defense articles or equipment; and test and procurement of foreign equipment, technology, or logistics support (see AR 70 – 41 for additional information).

Army acquisition workforce The personnel component of the acquisition system. The acquisition workforce includes permanent civil- ian and military members who occupy acquisition positions or are in acquisition development programs.

Army command The highest level of command, designated by the SECARMYSECARMYSecretary of the Army, primarily responsible for generating Army forces and planning and executing 10 USCUSCUnited States Code functions.

Army service component command An operational command, responsible for recommendations to the Joint force commander on the alloca- tion and employment of Army forces within a CCMD (see JP 1 – 02).

Army Systems Acquisition Review Council Top-level DA review body for acquisition programs where the AAE or DAE is the MDA/DA. It is chaired by the AAE and convened at formal milestone or other program reviews to provide information and develop recommendations for decisions by the AAE.

Basis of issue The authority that prescribes the number of items to be issued to an individual, a unit, or a military activity. Basis of issue is stated in authorization documents.

Capability developer Responsible for analyzing, determining, prioritizing warfighting requirements for DOTMLPF – P require- ments, personnel, facilities, and policy implications within the context of the force development process. Also responsible for representing the end user during the full development and life cycle process (coun- terpart to generic use of MATDEV).

Capability development document A document that specifies capability requirements in terms of developmental Key Performance Parame- ters, Key System Attributes, Additional Performance Attributes, and other related information necessary to support development of one or more increments of a materiel capability solution.

Capability production document A document that addresses the production elements specific to a single increment of an acquisition pro- gram.

Chief information officer assessment An established matrix of criteria used to evaluate program compliance with statutory and regulatory acqui- sition requirements.

Chief management officer The principal advisor to the SECARMYSECARMYSecretary of the Army on the effective and efficient organization of business operations and transformation initiatives.

Clothing and individual equipment Used as a collective term that includes personal clothing, optional clothing, organizational clothing, and individual equipment items that are an integral part of the design of the individual Soldier as a weapons platform.

Commercial item Any item, other than real property, that is of a type customarily used for nongovernmental purposes and that has been sold, leased, or licensed to the general public; or has been offered for sale, lease, or li- cense to the general public; or any item evolved through advances in technology or performance and that is not yet available in the commercial marketplace, but will be available in the commercial marketplace in time to satisfy the delivery requirements under a Government solicitation. This definition also includes ser- vices in support of a commercial item, of a type offered and sold competitively in substantial quantities in the commercial marketplace based on established catalog or market prices for specific tasks performed under standard commercial terms and conditions. This does not include services that are sold based on hourly rates without an established catalog or market price for a specified service performed (see the DAU Contracting Cone website available at https://aaf.dau.edu/aaf/contracting-cone/ and FARFARFederal Acquisition Regulation Subpart 2.1).

Computer software Computer programs that comprise a series of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations; and recorded information comprising source code listings, design details, algorithms, pro- cesses, flow charts, formulas, and related material that would enable the computer program to be pro- duced, created, or compiled. Computer software does not include computer databases or computer soft- ware documentation.

Corrosion The deterioration of a material or its properties due to a reaction of that material with its chemical environ- ment.

Critical program information U.S. capability elements that contribute to the warfighters’ technical advantage, which if compromised, undermines U.S. military preeminence. U.S. capability elements may include, but are not limited to, soft- ware algorithms and specific hardware residing on the system, its training equipment, or maintenance support equipment (see DoDI 5000.83 and DoDI 5200.39).

Critical technologies Those technologies that may pose major technological risk during development, particularly during the EMD phase of acquisition.

Data Recorded information, regardless of form or the media on which it may be recorded. The term includes technical data and computer software. It does not include information incidental to contract administration, such as financial, administrative, cost or pricing, or management information (see FARFARFederal Acquisition Regulation Clause 52.227 – 14).

Decision authority The person vested with the authority to make acquisition program decisions. This may be the DAE, the component acquisition executive (for the Army, this is the AAE), or an individual with appropriate delega- tion of authority, (that is, the PEOPEOProgram executive office(r), a DRPM, or a PM of an ACAT IV acquisition program).

Defense Acquisition System The management process by which the DoD provides effective, affordable, and timely systems to the us- ers.

Defense business systems Information systems that are operated by, for, or on behalf of the Department of Defense, including any of the following: a financial system, a financial data feeder system, a contracting system, a logistics system, a planning and budgeting system, an installations management system, a human resources management system, a training and readiness system. The terms does not include a national security system; or an information system used exclusively by and within the defense commissary system or the exchange sys- tem or other instrumentality of the Department of Defense conducted for the morale, welfare, and recrea- tion of members of the armed forces using nonappropriated funds.

Detailed manufacturing or process data Technical data that describe the steps, sequences, and conditions of manufacturing, processing, or as- sembly the manufacturer used to produce an item or component or to perform a process (see DFARS Clause 252.227 – 7013).

Digital engineering An integrated digital approach that uses authoritative sources of systems’ data and models as a contin- uum across disciplines to support life cycle activities from concept through disposal.

Direct reporting unit An Army organization comprised of one or more units with institutional or operational support functions, designated by the SECARMYSECARMYSecretary of the Army, normally to provide broad general support to the Army in a single, unique discipline not otherwise available elsewhere in the Army. DRUs report directly to a HQDA principal and/or ACOMACOMArmy service component command and operate under authorities established by the SECARMYSECARMYSecretary of the Army.

Direct support A mission requiring a force to support another specific force and authorizing it to answer directly to the supported force’s request for assistance.

Director, Acquisition Career Management The official appointed by the AAE to assist in the performance of duties as they relate to the training, edu- cation, and career development of the acquisition workforce.

Domain For Army enterprise architecture purposes, a group of systems or SoS of a similar nature or focused on satisfying similar objectives. These four domains are primarily used within the DoD Information Technol- ogy Standards Registry: command, control, communications, computers, and intelligence; weapon sys- tems; modeling and simulation; and sustainment. For HSI purposes, a group of seven areas that integrate human considerations into the system acquisition process. The domains are manpower, personnel capa- bilities, training, human factors engineering, system safety, health hazards, and Soldier survivability.

Economic useful life Estimate of the point in time when the Army should plan on replacing or modernizing a weapon or sys- tem, based on the expected impact to readiness (technical or operational obsolescence) and resources (business case analysis and cost benefit analysis).

Family of systems A set or arrangement of independent systems that can be arranged or interconnected in various ways to provide different capabilities. The mix of systems can be tailored to provide desired capabilities, depend- ent on the situation. An example of a family of systems is a brigade combat team that includes combat and combat support systems. Although these systems can independently provide militarily useful capabili- ties, in collaboration they can more fully satisfy a more complex and challenging capability to detect, lo- calize, track, and engage the enemy.

Force sustainment The management and care of materiel equipment after a capability transitions to sustainment (see para 6–2 a ) and before the Army divests the capability. It includes the maintenance, targeted modernization, and recapitalization of enduring platform capabilities the Army must retain to enable a multi-domain oper- ations-capable force.

Form, fit, and function data Technical data that describes the required overall physical, functional, and performance characteristics (along with the qualification requirements, if applicable) of an item, component, or process to the extent necessary to permit identification of physically and functionally interchangeable items (see DFARS Clause 252.227 – 7013).

Government purpose rights For noncommercial technical data, the rights to (i) use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and (ii) release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose that data for United States government pur- poses. See DFARS 252.227 – 7013(a)(13). For noncommercial computer software and noncommercial computer software documentation, the rights to (i) use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation within the Government without re- striction; and (ii) release or disclose computer software or computer software documentation outside the Government and authorize persons to whom release or disclosure has been made to use, modify, repro- duce, release, perform, display, or disclose the software or documentation for United States government purposes. See DFARS 252.227 – 7014(a)(12).

Grant A legal instrument which, consistent with 31 USCUSCUnited States Code 6304, is used to enter into a relationship— pose of support or stimulation authorized by a law of the United States, rather than to acquire property or services for the DoD’s direct benefit or use. the activity contemplated by the grant (see 32 CFRCFRCode of Federal Regulations 37.1295).

Health hazard assessment The application of biomedical knowledge and principles to document and quantitatively determine the health hazards of Army systems. This assessment identifies, evaluates, and recommends controls to re- duce risks to the health and effectiveness of personnel who test, use, or service Army systems. This as- sessment includes: the evaluation of hazard severity, hazard probability, risk assessment, consequences, and operational constraints; the identification of required precautions and protective devices; training re- quirements.

Heraldic items All items worn on the uniform to indicate unit, skill, branch, award, or identification and for which a design has been established by The Institute of Heraldry (TIOH) on an official drawing

Human systems integration A comprehensive management and technical strategy, initiated early in the acquisition process, to ensure that human performance, the burden the design imposes on manpower, personnel, and training, and safety and occupational health aspects are considered throughout the system design and development processes.

Information technology Any equipment or interconnected system or subsystem of equipment that is used in the automatic acqui- sition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information by the executive agency.

Infrastructure Fundamental facilities, systems, and related services necessary for the Army to function. For purposes associated with the CCA of 1996, shared computers, ancillary equipment, software, firmware, and similar procedures, services, people, business processes, facilities (to include building infrastructure elements), and related resources used in the acquisition, storage, manipulation, protection, management, move- ment, control, display, switching, interchange, transmission, or reception of data or information in any for- mat, including audio, video, imagery, or data, whether IT or NSS.

Initial capabilities document Documents the need for a materiel approach to a specific capability gap derived from an initial analysis of materiel approaches executed by the operational user and, as required, an independent analysis of mate- riel alternatives. It defines the capability gap in terms of the functional area, the relevant range of military operations, desired effects, and time. The ICD summarizes the results of the DOTMLPF – P analysis and describes why non-materiel changes alone have been judged inadequate in fully providing the capability.

Initial operational capability The criteria and schedule for when a program must attain IOC is defined as the program’s CDD, capabili- ties production document (when retained as a valid legacy document) or CDD update. It is the first attain- ment of the capability (as declared by the IOC organization) by a modified table of organization and equipment unit and supporting elements to operate and maintain a production item or system effectively provided that— erational environment. ment, repair parts, documentation, and training devices. cision review and implies that the unit is combat ready.

In–process review Review body for ACAT II, III, and IV programs (or their equivalent AAF pathway-determined categories) when the AAE delegates MDA/DA. Convened at each formal milestone (or AAF pathway equivalent re- view) and at other critical points to evaluate status and make recommendations to the MDA/DA. An IPR is also commonly called a program review.

Installation A fixed or relatively fixed location together with its real estate, buildings, structures, utilities, and improve- ment thereon. It is usually identified with an existing or potential organization and missions or functions (see DAU’s Glossary of Defense Acquisition Acronyms and Terms).

Integrated product support A unified and iterative approach to the management and technical activities needed to influence opera- tional and materiel requirements and design specifications, define the support requirements best related to materiel design and to each other, develop and acquire the required support, provide required opera- tional phase support at lowest cost, seek readiness and life cycle cost improvements in the materiel and support systems during the operational life cycle, and repeatedly examine support requirements through- out the service life of the materiel.

Integrated product team A working-level team of representatives from all appropriate functional disciplines working together to build successful and balanced programs, identify and resolve issues, and provide recommendations to facilitate sound and timely decisions.

Intellectual property A product of the human mind which is protected by law. It includes inventions, trademarks, patents, indus- trial designs, copyrights, and technical information including software, data designs, technical know-how, manufacturing information and know-how, techniques, Technical Data Packages (TDPs), manufacturing data packages, and trade secrets.

Interoperability The ability of Army systems, units, or forces to provide data, information, materiel, and services to and accept the same from other systems, units, or forces and to use data, information, materiel, and services so exchanged to enable them to operate effectively together.

Interoperability certification Confirmation that the candidate system has undergone appropriate testing and that the applicable stand- ards and requirements for compatibility, interoperability, and integration have been met.

Item unique identification A system of marking items with UIIs that have machine-readable data elements to distinguish an item from all other like and unlike items.

Key performance parameters An attribute or characteristic of a system that is considered critical or essential to the development of an effective military capability and those attributes that make a significant contribution to the characteristics of the future Joint Force as defined in the Capstone Concept for Joint Operations. The KPPs are validated by the JROC for JROC Interest documents, and by the DoD component for Joint Integration, Joint Information, or Independent documents. Capability development KPPs, CDD update KPPs and ca- pabilities production document KPPs (when capabilities production documents are retained as a valid leg- acy document) are included verbatim in the APB.

Key system attribute Performance attribute of a system considered important to achieving a balanced solution/approach to a system, but not critical enough to be designated as a Key Performance Parameter.

Life cycle management A management process, applied throughout the life (systems development, production, delivery, sustain- ment, and disposal) of a system (products, processes, or services) that bases all programmatic decisions on the anticipated mission-related and economic benefits (cost, schedule, performance, risk, and support- ability) derived over the life of a system.

Limited Production Instrumentation and Testing Program Effort that provides capability in response to a requirement from the testing community. May include test instrumentation, targets, and threat with limited production quantities. A process that takes a holistic look at the investment in S&T and the life cycle management of equipment and systems to ensure the costs of programs are considered over a 30-year period.

Materiel developer The RDA command, agency, or office assigned responsibility for the system under development or being acquired. The term may be used generically to refer to the RDA community in the materiel acquisition pro- cess (counterpart to the generic use of CAPDEV).

Milestone decision authority Designated individual with overall responsibility for a program. The MDA will have the authority to ap- prove entry of an acquisition program into the next phase of the acquisition process and shall be account- able for cost, schedule, and performance reporting to higher authority, including Congressional reporting. This may be the DAE, the Component Acquisition Executive (for the Army, this is the AAE), the PEOPEOProgram executive office(r), or the PM of an ACAT IV program who has been delegated MDA/DA.

Mission critical computer resources Elements of computer hardware, software, or services with a function, operation, or use that involves in- telligence activities or crypto logical activities related to national security, command and control of military forces; or equipment that is an integral part of a weapon or weapon system.

Modular open system approach With respect to an MDAP, the modular open system approach is an integrated business and technical strategy that–a. employs a modular design that uses modular system interfaces between major systems, major system components and modular systems; b. Is subjected to verification to ensure modular system interfaces–(1) comply with, if available and suitable, widely supported and consensus-based standards; or (2) are delivered pursuant to the requirements established in subsection (a)(2)(B) of section 804 of the William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021; c. 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— (1) significant cost savings or avoidance; (2) schedule reduction; (3) opportunities for technical upgrades; (4) increased interoperability, including sys- tem of systems interoperability and mission integration; or (5) other benefits during the sustainment phase of a major weapon system; and d. Complies with the technical data rights set forth in 10 USCUSCUnited States Code 3771 – 3775 (see 10 USCUSCUnited States Code 4401).

Modular system interface A shared boundary between major systems, major system components, or modular systems, defined by various physical, logical, and functional characteristics, such as electrical, mechanical, fluidic, optical, ra- dio frequency, data, networking, or software elements. (see 10 USCUSCUnited States Code 4401).

Non-developmental item Any previously developed item of supply used exclusively for Government purposes by a Federal agency, a state or local government, or a foreign government with which the U.S. has a mutual defense cooperation agreement; any item described above that requires only minor modifications or modifications of the type customarily available in the commercial marketplace to meet the requirements of the procuring department or agency (see FARFARFederal Acquisition Regulation 2.101).

Optional purchase uniform items Uniform items authorized for wear by the individual but that are not a part of the initial or supplemental clothing issue. Optional purchase uniform items are not centrally procured but may be obtained through the Army and Air Force Exchange Service or authorized commercial sources.

Organizational clothing, and individual equipment The uniforms, clothing, and equipment listed in the CTA, which are issued to an individual on a loan basis and remain the property of the organization. Commanders issue organizational clothing and equipment in accordance with the allowances and directives published in the appropriate CTA. When issued, organiza- tional clothing is worn when prescribed by the commander in accordance with Army regulations, technical manuals, and the CTA. Examples of organizational uniforms are the maternity work uniform, hospital duty, and food service uniforms, modular load carriage equipment, and cold-weather clothing.

Program protection The integrating process for managing risks to DoD warfighting capability from foreign intelligence collec- tion; hardware, software, and cyber vulnerability or supply chain exploitation; and battlefield loss through- out the system life cycle.

Program Protection Plan A living plan to guide efforts to manage the risks to critical program information and mission critical func- tions and components as well as program and system information. This milestone acquisition document captures both systems security engineering and security activities and the results of the analyses as the program and system become more defined (see DoDI 5000.83, DoDI 5200.39, and AR 70 – 77).

Program, project, or product manager An HQDA manager for a system or program. A PM may be subordinate to the AAE, PEOPEOProgram executive office(r), or DRPM. Re- fers to the management level of intensity the Army assigns to a particular weapon system or information system.

Programmatic environment, safety and occupational health evaluation Documents data generated by ESOH analyses conducted in support of program execution—regardless of size, type, or number of ESOH risks that are anticipated or known for the system.

Security assistance A group of programs authorized by the Foreign Assistance Act of 1961, as amended; the Arms Export Control Act of 1976, as amended; or other related statutes by which the United States provides defense articles, military training, and other defense-related services by grant, lease, loan, credit, or cash sales in furtherance of national policies and objectives, and those that are funded and authorized through the De- partment of State to be administered by Department of Defense/Defense Security Cooperation Agency, which are considered part of security cooperation. (see AR 12 – 1).

Serialized item management Programs and techniques that use life cycle item management data to track the performance of uniquely identified items throughout their life cycle. The overarching goal of these programs and techniques is to enable managers achieve optimum weapon system materiel availability at the best total ownership cost through the use of effective and efficient life-cycle management practices..

Software Also commonly referred to as computer software, defined as (i) computer programs that comprise a se- ries of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations; and (ii) recorded information comprising source code listings, design details, algorithms, processes, flow charts, formulas, and related material that would enable the computer program to be produced, created, or compiled. It does not in- clude computer databases or computer software documentation.

Software support activity An organization assigned the responsibility for post-production software support.

Synchronization The coordination, harmonization, and integration effort that starts early in the EMD phase of a program and continues throughout its life cycle. The objective is the appropriate consideration of the interoperabil- ity and interdependency of the constituent legacy, current, and future systems so that capabilities which are greater than the sum of individual systems are provided to the Warfighter.

System of systems A set or arrangement that results when independent and useful systems are integrated into a large sys- tem that delivers unique capabilities. The SoS may deliver capabilities by combining multiple collaborative and independent-yet-interacting systems. The mix of systems may include existing, partially developed, and yet-to-be designed independent systems.

Technical data Recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer databases and computer software documentation). The term does not include com- puter software or financial, administrative, cost or pricing, or management data or other information inci- dental to contract administration.

Technology transfer The intentional sharing of knowledge, expertise, facilities, equipment, and other resources that benefit the DoD and/or non-DoD entities. (see DoDI 5535.08).

Total life cycle competition strategy Describes the technical and contracting methods for maximizing effective competition, with an objective of full and open competition, throughout the system’s life cycle. Addresses the entire system, to include end items, components, and spare parts in light of breakout, spares acquisition integrated with production, support services and other software, and acquisition of technical data and data rights.

Training aids, devices, simulators, and simulations A general term that defines training equipment that supports training in the live, virtual, and constructive environments. The TADSS are justified, developed, and acquired to support training of designated tasks. Examples include battle simulations, targetry, training-unique ammunition, flight or driving simulators, gunnery trainers, and maintenance trainers. The TADSS are categorized as system (supported by the MATDEV) or non-system (supported by the training program evaluation group). System devices are de- signed for use with a specific system, SoS, or item of equipment, including subassemblies and compo- nents. System TADSS may be designed or configured to support individual, crew, collective, and com- bined armed training strategies. System TADSS may be stand-alone, embedded, or appended. Non-sys- tem TADSS are designed to support general military training and non-system specific training require- ments. Both system and non-system TADSS are required for operational and unit readiness. Both types of TADSS are therefore considered integral parts of weapons, weapon systems, and SoS.

Transition to sustainment The deliberate, predictable, conditions-based and informed decision to transfer responsibility to execute sustainment of post FRP decision systems delivering sufficient capability to execute the mission and that no longer require significant enhancements, upgrades, or modernization.

Transportability The inherent capability of an item or system to be moved effectively and efficiently by required transporta- tion assets and modes.

Unique item identifier/unique item identification A globally unique and unambiguous identifier that distinguishes an item from all other like and unlike items. The UII is derived from a UII data set of one or more data elements. a set of data elements marked on items that is globally unique and unambiguous.

Unlimited rights Regarding rights in technical data other than commercial products and commercial surfaces, the rights to use, modify, reproduce, perform, display, release, or disclose technical data in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so. (see DFARS 252.227 – 7013(a)(16)). Regarding rights other than commercial computer software and other than com- mercial computer software documentation, the rights to use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation in whole or in part, in any manner and for any purpose whatsoever, and to have or authorize others to do so. (see DFARS 252.227 – 7014(a)(16)).

Urgent operational need Capability requirements identified as impacting an ongoing or anticipated contingency operation. If left un- fulfilled, UONs result in capability gaps potentially resulting in loss of life or critical mission failure. When validated by a single DoD component, these are known as DoD component UONs..