The standard also includes additional common elements unique to Space Systems, Launch Vehicle Systems, and Strategic Missile Systems. The common elements identified in MIL-STD-881E, Appendix K are: Integration, assembly, test, and checkout Systems engineering Program management System test and evaluation Data Peculiar support equipment Common support equipment Operational/Site activation Contractor Logistics Support Industrial facilities Initial spares and repair parts. Information Systems/Defense Business Systems.It includes WBS definitions for specific defense materiel commodity systems, and addresses WBS elements that are common to all systems.ĭefense Materiel Item categories from MIL-STD-881E are: The current version of this document can be found in "Work Breakdown Structures for Defense Material Items" (MIL-STD-881E). The document has been revised several times, most recently in 2018.
In 1968, the DoD issued "Work Breakdown Structures for Defense Materiel Items" (MIL-STD-881), a military standard requiring the use of work breakdown structures across the DoD. This guide was endorsed by the Secretary of Defense for adoption by all services. īy June 1962, DoD, NASA and the aerospace industry published a document for the PERT/COST system which described the WBS approach. While the term "work breakdown structure" was not used, this first implementation of PERT did organize the tasks into product-oriented categories. Navy in 1957 to support the development of its Polaris missile program. The concept of work breakdown structure developed with the Program Evaluation and Review Technique (PERT) by the United States Department of Defense (DoD).
The development of the WBS normally occurs at the start of a project and precedes detailed project and task planning. The WBS may be displayed horizontally in outline form, or vertically as a tree structure (like an organization chart). In addition to its function in cost accounting, the WBS also helps map requirements from one level of system specification to another, for example, a cross reference matrix mapping functional requirements to high level or low level design documents.
A well-designed WBS makes it easy to assign each project activity to one and only one terminal element of the WBS. Since the planned outcomes are the desired ends of the project, they form a relatively stable set of categories in which the costs of the planned actions needed to achieve them can be collected. The WBS is organized around the primary products of the project (or planned outcomes) instead of the work needed to produce the products (planned actions). This technique (sometimes called a system breakdown structure ) is used to define and organize the total scope of a project. For each element of the work breakdown structure, a description of the task to be performed is generated. Ī work breakdown structure permits summing of subordinate costs for tasks, materials, etc., into their successively higher level "parent" tasks, materials, etc. The work breakdown structure provides a common framework for the natural development of the overall planning and control of a contract and is the basis for dividing work into definable increments from which the statement of work can be developed and technical, schedule, cost, and labor hour reporting can be established. Example of work breakdown structure applied in a NASA reporting structure
0 kommentar(er)
