DODD , National Committee for Employer Support of the Guard and Reserve DODD and DOD R, Executive Summary, March NUMBER May 12, USD(AT&L). SUBJECT: The Defense Acquisition System. References: (a) DoD Directive , “The Defense Acquisition. follows in achieving those objectives are described in DoD Directive and DoD. Instruction The Defense Acquisition Guidebook is designed to.
|Published (Last):||25 August 2004|
|PDF File Size:||20.77 Mb|
|ePub File Size:||1.99 Mb|
|Price:||Free* [*Free Regsitration Required]|
Its purpose will have to be reoriented to focios on program reviews at the key decision points and to advise the Secretary of the Army.
DODD 5000.1, DEPARTMENT OF DEFENSE DIRECTIVE, THE DEFENSE ACQUISITION SYSTEM (12 MAY 2003)
If no IP strategy has been developed, provide supporting rationale for this position. For potential systems applicatioiT, this normally indicated the program initiation and the beginning of the concept formulation phase of the acquisition cycle. As exploration and development of a new doddd tem concept proceeds, reliable trade-offs between cost, schedule and [per- formance is increased and estimates gain stability.
B If 5000.1 contracting officer makes a determination, under paragraphs b 1 A 1 and 2 of this section, for a competitive solicitation, 10 U. Volume 2, Part C, pages These members are supported by other Assistant Secretaries and members of the Army staff on an on-call basis.
After pro- gram approval, the designee will assume the role of Program Manager and will be given a charter for the establishment of his proctram office and program objectives. The “front-end” activity of the requirements generation process should be structurex! Whether or not tliis has ever been done by a PM is not as important as the fact tiiat he is 29 authorized to circumvent the established lines of authority if he con- siders it necessary.
DoD Directives thru
Program managers are held singularly responsible to report iimEdiately significant program exceptions including projected threshold breaches to the Service Secretary and SECDEF. Department of Defense, Depart me nt of Defe nse Direct ive The first number is the source listed in the bibliography.
Within the gestation process, operational iirpacts are derived frcm statements of capability goals vhich define a specific mission or operational capability needed dpdd the Army to counter a vulnerability in sane mission area The revised policy indicates further progress toward more de- centralized responsibility and authority at the service level for program execution and for program review at major milestones.
B The date approval for operational use has been or will be obtained. These policies were focused on a concept of a single program manager who was chartered with suificient authority to accortplish the program objective. The third fhiase included a review of the Army’s basic policies for eodd system acquisition in AR and AR”Operating Policies for Syste.
In a more practical sense, precedence and the estab- lished warkinq relationships within official lines will dictate how a PM interfaces witli the layers of authority between him and the Secretary of the Army.
This circular contained a new policy for the acquisition of major systems by all executive branch agencies. In May shortly after his currival, he decentralized the res- ponsibility for the acquisition and management of major systems to the individual serv’ices and established the Defense System Acquisition Review Council DSARCj.
Sane of these changes were being influenced by the same reports that had stimulated the DODD Throughout all the changes, the concept of a strong program manager with the proper responsibility and authority will have to be reinforced. If you are a client of PPI or subsidiary company CTI and wish to obtain a username and password, please use the email contact form.
Site developed by Webel IT Australia. This chcinge is not considered significant since inflation has been a major cause of escalating acquisition costs in recent years and is viewed as an administrative threshold in the procjram desicination process. The mission need should be based on an analysis of mission dkdd reconciled witli ov’erall cap- abilities, priorities and resources, and independent of any system product or solution.
Army Implementation As a result of the AT-IARC study recamendation concerning the issue of requirements instability, the Army revised its requireircnts pro- dkdd so that a “firm requirament” should not be established until both the materiel and conbat developers have a joint understanding of what is achievable and usable 1: The MENS is used to document the mission need and to provide essential support- ing and planning infomvition, such as projected threat, existing DOD cap- ability and deficiencies, and laiown constraints.
Additionally, the ASARC principals will have to be changed to include the Secretary or the Under Secretary as the chairman and the other Assistant Secretaries who have functional responsibilities in system acquisition management.
This program is to identify and to develop cjualified officers to support future requirements for project nanagers and other senior officials with- in the materiel development activities. Tlneso recemendations related to the organizational make-up, directives, instructions and other cjuidelines of the SECDEF pertaining to major weapons system acc]uisition within the OSD. After establishment of a baseline for an evaluation of the changes, the impact of the changes on the current Army’s policies and procedures was assessed and implementation options 500.1.
The formalized dofd structure is responsive to QMB Circular A acquisition objective to ensure that each major system fulfills a mission need 5: Although these criteria have changed, it is irportant to note that the re.
Discuss actions taken to ensure either elimination of or authorization to use class I ozone-depleting chemicals and substances see The Operational Capability CSDjectives OCO document provides guidance for technological advancement and justification for basic research, exploratory development and non- ddd advanced development It is of limited detail and reflects the following subjects: As required by U. These actions are culminated by the definition of the operational, tech- nical and logistical concepts in an LQA vihich is the document of record supporting the system advanced development program.
Any program exceptions or vixriances recpjiring SECCEF decisions, other them the four decision points, are to be resolveci with the OSD staff having primary functional responsibility. These basic and operating policies implement DOD Directives For addi- tional background on these roexxmendations and much of the policy set both in Circular A, see COGP report. SATC, the revised directive places the service acquisition decision-making pro- cess under civilian control.
For development acquisitions, describe the market research undertaken to identify commercial items, commercial items with modifications, or nondevelopmental items see FAR part 10 that could satisfy the acquisition objectives.