Para 18.104.22.168.4. Information
All programs shall be managed and engineered using best
processes and practices to reduce security risks; ensure programs
are synchronized; be designed to be mutually compatible with other electric
or electronic equipment and the operational electromagnetic environment;
identify Critical Program Information that requires protection to prevent
unauthorized disclosure or inadvertent transfer of leading edge
technologies and sensitive data or systems; require hardening, redundancy, or
other physical protection against attack; be certified for spectrum
supportability; and comply with the provisions of the Clinger-Cohen Act (CCA)
Para 22.214.171.124. The Defense
Acquisition Management Framework - General
...Acquisitions shall be structured in such a way that undue
risk (such as through the use of firm fixed price options
that cover more than five years) is not imposed on contractors, and so that
excessive contractor investment (beyond normal investments for plant,
equipment, etc.) is not required.
Para 126.96.36.199. The Defense
Acquisition Management Framework - General
Milestone decision authorities shall promote flexible,
tailored approaches to oversight and review based on mutual trust and a
program's dollar value, risk, and complexity.
Para 188.8.131.52. Technological
...The S&T Program is uniquely positioned to reduce the
risks of promising technologies before they are assumed in
the acquisition process.
Para 184.108.40.206.2.4. Technology
For those technologies with the most promise for application to weapon
systems or AISs, be responsible for maturing technology to a readiness level
that puts the receiving MDA at low risk for systems
integration and acceptable to the cognizant MDA, or until the MDA is no longer
considering that technology.
Para 220.127.116.11.3.1. Concept
Concept Exploration typically consists of competitive, parallel, short-term
concept studies. The focus of these efforts is to define and evaluate the
feasibility of alternative concepts and to provide a basis for assessing the
relative merits (i.e., advantages and disadvantages, degree of
risk, etc.) of these concepts.
Para 18.104.22.168.6. Component
The project shall exit Component Advanced Development when a system
architecture has been developed and the component technology has been
demonstrated in the relevant environment or the MDA decides to end this
effort. This effort is intended to reduce risk on components
and subsystems that have only been demonstrated in a laboratory environment
and to determine the appropriate set of subsystems to be integrated into a
Para 22.214.171.124.1.1. Begin
Development and Develop and Demonstrate Systems -
The purpose of the System Development and Demonstration phase is to develop
a system, reduce program risk, ensure operational
supportability, design for producibility, ensure affordability, ensure
protection of Critical Program Information, and demonstrate system
integration, interoperability, and utility.
Para 126.96.36.199.3.1.2. Milestone
For shipbuilding programs, the lead ship engineering development model
shall be authorized at Milestone B. Critical systems for the lead and follow
ships shall be demonstrated given the level of technology maturity and the
associated risk prior to ship installation.
Para 188.8.131.52.3.4.1 Entry into
System Development and Demonstration
Milestone B approval can lead to System Integration or System
Demonstration. Regardless of the approach recommended, PMs and other
acquisition managers shall continually assess program risks.
Risks must be well understood, and risk
management approaches developed, before decision authorities can authorize a
program to proceed into the next phase of the acquisition process.
Risk management is an organized method of identifying and
measuring risk and developing, selecting, and managing
options for handling these risks. The types of
risk include, but are not limited to, schedule, cost,
technical feasibility, threat, risk of technical
obsolescence, security, software management, dependencies between a new
program and other programs, and risk of creating a monopoly
for future procurements.
Para 184.108.40.206.4.2. System
This effort is intended to integrate the sub-systems and reduce
Para 220.127.116.11.2.1. Entrance
Technology maturity (with an independent technology readiness assessment),
system and relevant mission area (operational) architectures, mature software
capability, demonstrated system integration or demonstrated commercial
products in a relevant environment, and no significant manufacturing