MIL-STD-881C WhitepaperBack to the full Whitepaper

Appendix L: Common Elements

APPENDIX L: COMMON ELEMENTS WORK BREAKDOWN STRUCTURE AND DEFINITIONS L.1 SCOPE This appendix provides the WBS elements common to all types of systems. Applicable Government and non-Government documents are listed. Definitions for the common WBS elements are provided in this appendix. Unique uses of common elements are also included to better define the related systems.

Elements defined in this Appendix are elements common to all acquisition programs developed by the Department of Defense. The efforts associated with common elements should be placed at the level where they support a specific element. Common elements can be found at all levels of a WBS.

Using Appendix G Surface Vehicle System as an example, common elements found at Level 2 of the WBS capture efforts associated with the system as a “whole” (i.e., training for the entire surface vehicle system). Level 3 common elements will support Level 2 elements such as the primary vehicle or secondary vehicle. Level 4 common elements, when shown, support the subsystems captured at Level 3 (for example, Training for the Navigation and Remote Piloting System).

Many of the commodity classes apply common elements in a way that is unique to those commodities. This Appendix captures those unique applications for Space Systems (reference L.4), Launch Vehicle Systems (reference L.5) and Automated Information Systems (reference L.6).

L.2 APPLICABLE DOCUMENTS

None L.3 DEFINITIONS OF COMMON ELEMENTS

L.3.1 Integration, Assembly, Test and Checkout. In those instances in which an integration, assembly, test, and checkout element is used (Appendices A through K), this element includes all effort of technical and functional activities associated with the design, development, and production of mating surfaces, structures, equipment, parts, materials, and software required to assemble the Level 3 equipment (hardware/software) elements into a Level 2 mission equipment (hardware/ software) as a whole and not directly part of any other individual Level 3 element. (Reference Section L.4.1 for space systems application)

Includes, for example:
a. The development of engineering layouts, determination of overall design characteristics, and determination of requirements of design review
b. The set up, conduct, and review of testing assembled components or subsystems prior to installation
c. The detailed production design, producibility engineering planning (PEP), and manufacturing process capability, including the process design development and demonstration effort to achieve compatibility with engineering requirements and the ability to produce economically and consistent quality
d. Inspection activities related to receiving, factory and vendor liaison
e. Design maintenance effort
f. Quality planning and control
g. Tooling (initial production facilities, factory support equipment) including planning, design, and fabrication
h. Administrative engineering
i. The joining or mating and final assembly of Level 3 equipment elements to form a complete prime mission equipment when the effort is performed at the manufacturing facility
j. Integration of software (including loading and verification of firmware)
k. Conduct of production acceptance testing

Excludes, for example:
a. All systems engineering/program management and system test and evaluation that are associated with the overall system

NOTE: When an integration, assembly, test, and checkout element is utilized at lower levels of the contract work breakdown structure, it will be summarized into the next higher level equipment (hardware/software) WBS element and should never be summarized directly into a higher-level integration, assembly, test, and checkout element.

L.3.2. System Engineering. The technical and management efforts of directing and controlling a totally integrated engineering effort of a system or program.

Includes, for example:
a. Effort to define the system and the integrated planning and control of the technical program efforts of design engineering, specialty engineering, production engineering, and integrated test planning
b. Effort associated with developing the Systems Engineering Management Plan (SEMP)
c. Effort to transform an operational need or statement of deficiency into a description of system requirements and a preferred system configuration
d. Technical planning and control effort for planning, monitoring, measuring, evaluating, directing, and re-planning the management of the technical program
e. All programs, where applicable; value engineering, configuration management, Human Systems Integration (Human factors engineering; Personnel; Habitability; Manpower; Training; Environment, Safety and Occupational Health; Survivability), vulnerability, maintainability, reliability, standardization, system analysis, logistic support analysis, etc.
f. Technical baseline management and event based technical reviews with independent subject matter expertise participation
g. Cross product IPT integration
h. Survivability/vulnerability analysis
i. System of Systems (SoS) and System Level Architecting, modeling and simulation, verification and validation and external interface definition and management
j. For sea systems; the expanded Ship Work Breakdown Structure (ESWBS), configuration management (812 and 813), human factors (892), standardization (893), value engineering (894), and reliability and maintainability (895) elements

Excludes, for example:
a. Actual design engineering and the production engineering directly related to the WBS element with which it is associated

Examples of Systems Engineering efforts are:
a. System requirement and architecture definition, overall system design and margin management, design integrity analysis, system optimization, system/cost effectiveness analysis, and intra-system and inter- system compatibility assurance, etc.; the integration and balancing of reliability, maintainability, producibility, safety engineering, human health, environmental protection, manpower, personnel, training, and survivability; security requirements, quality assurance program, value engineering, preparation of equipment and component performance specifications, design of test and demonstration plans; determination of software development or software test facility/ environment requirements. Assessments of system effectiveness, life cycle costs, schedule, risk and evolutionary growth for each tradeoff following each iteration of the systems engineering process, and develop the associated required systems engineering products.
b. Requirements Management- ensures requirements traceability and version control for all program requirements starting with the Capabilities Development Document (CDD) and Capabilities Production Document (CPD) to the system specification and lower level Configuration Item (CI) specifications.
c. Interface Management – ensures interface compatibility of external and internal interfaces and coordination of changes between associate contractors and Integrated Product Teams (IPTs).
d. Preparation of the Systems Engineering Management Plan (SEMP), specification tree, program risk analysis, system planning, decision control process, technical performance measurement, technical reviews, subcontractor and vendor reviews, work authorization, and technical documentation control.
e. Reliability engineering—the engineering process and series of tasks required to examine the probability of a device or system performing its mission adequately for the period of time intended under the operating conditions expected to be encountered.
f. Maintainability engineering—the engineering process and series of tasks required to measure the ability of an item or system to be retained in or restored to a specified condition of readiness, skill levels, etc., using prescribed procedures and resources at specific levels of maintenance and repair.
g. Human Systems Integration—the engineering process and the series of tasks required to define, as a comprehensive technical and engineering effort involving the integration of the human operator and maintainer requirements while attempting to minimize lifecycle cost and maximize total system performance.
h. Supportability analyses—an integral part of the systems engineering process beginning at program initiation and continuing throughout program development. Supportability analyses form the basis for related design requirements included in the system specification and for subsequent decisions concerning how to most cost effectively support the system and its infrastructure over its entire life cycle.
i. Configuration Management – supports the identification and management of the technical baselines (functional baseline, allocated baseline, initial product baseline, final product baseline).
j. Data Management – identifies the essential technical data necessary for the definition and sustainment of the system reflected in the respective technical baselines.

L.3.3 Program Management. The business and administrative planning, organizing, directing, coordinating, controlling, and approval actions designated to accomplish overall program objectives, which are not associated with specific hardware elements and are not included in systems engineering.

Includes, for example:
a. Cost, schedule, performance measurement management, warranty administration, contract management, data management, vendor liaison, subcontract management, etc.
b. Support element management, defined as the logistics tasks management effort and technical control, and the business management of the support elements. The logistics management function encompasses the support evaluation and supportability assurance required to produce an affordable and supportable defense materiel system.
c. Planning and management of all the functions of logistics. Examples are: 1. maintenance support planning and support facilities planning; other support requirements determination; support equipment requirements determination; supply support; packaging, handling, storage, and transportation; provisioning requirements determination and planning; training system requirements determination; computer resource determination; organizational, intermediate, and depot maintenance determination management; and data management
d. For sea systems; the Expanded Ship Work Breakdown Structure (ESWBS), project management (897); data management (896); and supply support (8643) elements.

L.3.4 System Test and Evaluation. The use of pilot, prototype, production, or specifically fabricated hardware/ software to obtain or validate engineering data on the performance of the system during the developmental phase (normally funded from RDT&E) of the program. It also includes all effort associated with the development of any specialized tools or data in support of the system level test program.

Includes, for example:
a. Detailed planning, conduct, support, data reduction and reports (excluding the contract data requirements list data) from such testing, and test articles that are functionally configured to represent and test subsystems/components of the defense materiel end item being developed or produced
b. Design and production of models, specimens, fixtures and instrumentation

NOTE: Test articles that are functionally configured to represent and test the complete defense materiel end item being developed or produced, are excluded from this WBS element.

Excludes, for example:
a. All formal and informal testing up through the subsystem level, which can be associated with the hardware/software element acceptance testing

NOTE: These excluded efforts are to be included with the appropriate hardware or software elements.

L.3.4.1 Developmental Test and Evaluation. This effort is planned, conducted and monitored by the developing agency of the DoD component. It includes test and evaluation conducted to:
a. Demonstrate that the engineering design and development process is complete
b. Demonstrate that the design risks have been minimized
c. Demonstrate that the system will meet specifications
d. Estimate the system’s military utility when introduced
e. Determine whether the engineering design is supportable (practical, maintainable, safe, etc.) For operational use
f. Provide test data with which to examine and evaluate trade-offs against specification requirements, life cycle cost, and schedule
g. Perform the logistics testing efforts to evaluate the achievement of supportability goals, the adequacy of the support package for the system, (e.g., deliverable maintenance tools, test equipment, technical publications, maintenance instructions, and personnel skills and training requirements, etc.)
Includes, for example:
a. All contractor/system developer in-house effort
b. All programs, where applicable; models, tests and associated simulations (e.g., such as wind tunnel, static, drop, and fatigue); integration ground tests; test bed aircraft and associated support; qualification test and evaluation, development flight test, test instrumentation, environmental tests, ballistics, radiological, range and accuracy demonstrations, test facility operations, test equipment (including its support equipment), chase and calibrated pacer aircraft and support thereto, and logistics testing
c. For aircraft; avionics integration test composed of the following: 1. Test bench/laboratory, including design, acquisition, and installation of basic computers and test equipments that will provide an ability to simulate in the laboratory the operational environment of the avionics system/subsystem 2. Air vehicle equipment, consisting of the avionics and/or other air vehicle subsystem modules that are required by the bench/lab or flying test bed in order to provide a compatible airframe avionics system/subsystem for evaluation purposes 3. Flying test bed, including requirements analysis, design of modifications, lease or purchase of test bed aircraft, modification of aircraft, installation of avionics equipment and instrumentation, and checkout of an existing aircraft used essentially as a flying avionics laboratory 4. Avionics test program, consisting of the effort required to develop test plans/procedures, conduct tests, and analyze hardware and software test results to verify the avionics equipments’ operational capability and compatibility as an integrated air vehicle subsystem 5. Software, referring to the effort required to design, code, de-bug, and document software programs necessary to direct the avionics integration test
d. For engines: engine military qualification tests and engine preliminary flight rating tests
e. For sea systems: model basin, hydrostatic, fatigue, shock, special sea tests and trials, etc., including the Expanded Ship Work Breakdown Structure (ESWBS), trials agenda preparation, data collection and analysis (842); dock and sea trials (868); and hull vibration survey (868 9825) elements
f. For missiles: test articles such as Inert Measurement Vehicles, Launch Separation Vehicles, Separation and Control Test Vehicles, Boost Test Vehicles
g. For ordnance: test articles such as Ballistic Test rounds, Inert Measurement rounds, Dummy rounds, Launch Separation rounds, etc.

L.3.4.2 Operational Test and Evaluation. The test and evaluation conducted by agencies other than the developing command to assess the prospective system’s military utility, operational effectiveness, operational suitability, logistics supportability (including compatibility, inter-operability, reliability, maintainability, logistic requirements, etc.), cost of ownership, and need for any modifications.

Includes, for example:
a. Initial operational test and evaluation conducted during the development of a system
b. Such tests as system demonstration, flight tests, sea trials, mobility demonstrations, on-orbit tests, spin demonstration, stability tests, qualification operational test and evaluation, etc., and support thereto, required to prove the operational capability of the deliverable system
c. Contractor support (e.g., technical assistance, maintenance, labor, material, etc.) Consumed during this phase of testing
d. Logistics testing efforts to evaluate the achievement of supportability goals and the adequacy of the support for the system (e.g., deliverable maintenance tools, test equipment, technical publications, maintenance instructions, personnel skills and training requirements, and software support facility/environment elements)

L.3.4.3 Mock-ups/System Integration Labs (SILs). The design engineering and production of system or subsystem mock-ups that have special contractual or engineering significance or that are not required solely for the conduct of one of the above elements of testing. SILs are often used in lieu of (or in addition to) mock-ups. SILs are risk reduction facilities where software and hardware can be developed, integrated, tested and evaluated for both stand alone functionality and/or interoperability prior to being fielded.

Includes, for example:
a. Hardware/Lab Equipment
b. SIL Software (written to simulate the operating environment or written to operate the SIL)

L.3.4.4 Test and Evaluation Support. The support elements necessary to operate and maintain, during test and evaluation, systems and subsystems, which are not consumed during the testing phase and are not allocated to a specific phase of testing.

Includes, for example:
a. Repairable spares, repair of reparables, repair parts, consumables, warehousing and distribution of spares and repair parts, test and support equipment, test bed vehicles, drones, surveillance aircraft, tracking vessels, contractor technical support

Excludes, for example:
a. Operational and maintenance personnel, special fixtures, special instrumentation, etc., that are utilized and/or consumed in a single element of testing and that should be included under that element of testing

L.3.4.5 Test Facilities. The special test facilities required for performance of the various developmental tests necessary to prove the design and reliability of the system or subsystem.

Includes, for example:
a. Test tank test fixtures, propulsion test fixtures, white rooms, test chambers

Excludes, for example:
a. Brick and mortar-type facilities identified as industrial facilities

L.3.5 Training. Deliverable training services, devices, accessories, aids, equipment, and parts used to facilitate instruction through which personnel will learn to operate and maintain the system with maximum efficiency.

Includes, for example:
a. All effort associated with the design, development, and production of deliverable training equipment and its associated software as well as the execution of training services

Excludes, for example:
a. Overall planning, management, and task analysis function inherent in the WBS element systems engineering/program management

L.3.5.1 Equipment. Distinctive deliverable end items of training equipment, assigned by either a contractor or military service, required to meet specific training objectives.

Includes, for example:
a. Operational trainers, maintenance trainers, and other items such as cutaways, mock-ups, and models (e.g. Operational Instructional Equipment, Maintainer Instructional Equipment)

L.3.5.2 Services. Deliverable training services, accessories, and aids necessary to accomplish the objectives of training.

Includes, for example:
a. Training course materials; contractor-conducted training (in-plant and service training); and the materials and curriculum required to design, execute, and produce a contractor developed training program. (e.g. Operator Instructional Software, Maintainer Instructional Software)
b. Materiel, courses, and associated documentation (primarily the computer software, courses and training aids)
Excludes, for example:
a. Deliverable training data associated with the WBS element support data

L.3.5.3 Facilities. The special construction necessary to accomplish training objectives.

Includes, for example:
a. Modification or rehabilitation of existing training facilities and infrastructure used to accomplish training objectives

Excludes, for example:
a. Installed equipment used to acquaint the trainee with the system or establish trainee proficiency
b. The brick and mortar-type facilities identified as industrial facilities

L.3.6 Data. The deliverable data required to be listed on a contract data requirements list, DD Form 1423.

Includes, for example:
a. Only such effort that can be reduced or avoided if the data item is eliminated
b. Government-peculiar data; acquiring, assembling, reproducing, packaging and shipping the data
c. Transforming data into Government format, reproducing and shipping data identical to that used by the contractor but in a different format

L.3.6.1 Technical Publications. Technical data, providing instructions for installation, operation, maintenance, training, and support, formatted into a technical manual. Data may be presented in any form regardless of the form or method of recording. Technical orders that meet the criteria of this definition may also be classified as technical manuals.

Includes, for example:
a. Operation and maintenance instructions, parts lists or parts breakdown, and related technical information or procedures exclusive of administrative procedures
b. Data item descriptions (DIDs)
c. For sea systems: Expanded Ship Work Breakdown Structure (ESWBS), technical manuals and other data (856) element

L.3.6.2 Engineering Data. Recorded scientific or technical information (regardless of the form or method of recording) including computer software documentation. Engineering data defines and documents an engineering design or product configuration (sufficient to allow duplication of the original items) and is used to support production, engineering and logistics activities.

Includes, for example:
a. All final plans, procedures, reports, and documentation pertaining to systems, subsystems, computer and computer resource programs, component engineering, operational testing, human factors, reliability, availability, and maintainability, and other engineering analysis
b. Technical data package (re-procurement package), which includes all engineering drawings, associated lists, process descriptions, and other documents defining physical geometry, material composition, and performance procedures
c. For sea systems; Expanded Ship Work Breakdown Structure (ESWBS), design support, ship’s selected records (8302); design support, services, reproduction (8303); and engineering drawings and specifications (855) elements

Excludes, for example:
a. Computer software or financial, administrative, cost or pricing, or management data or other information incidental to contract administration

L.3.6.3 Management Data. The data items necessary for configuration management, cost, schedule, contractual data management, program management, etc., required by the Government.

Includes, for example:
a. Contractor cost reports, cost performance reports, contract funds status reports, schedules, milestones, networks, integrated support plans
b. For sea systems; Expanded Ship Work Breakdown Structure (ESWBS), contract data requirements (988) element

L.3.6.4 Support Data. The data items designed to document support planning in accordance with functional categories

Includes, for example:
a. Supply; general maintenance plans and reports; training data; transportation, handling, storage, and packaging information; facilities data; data to support the provisioning process and all other support data; and software supportability planning and software support transition planning documents

L.3.6.5 Data Repository. The facility, including storage requirements, designated to act as custodian to maintain a master engineering specification and establish a drawing repository service for Government approved documents that are the property of the U.S. Government. As custodian for the Government, the repository, authorized by approved change orders, maintains these master documents at the latest approved revision level. This facility is a distinct entity that may hold electronic or hard copy data.

Includes, for example:
a. All drafting and clerical effort necessary to maintain documents

Excludes, for example:
a. All similar effort for facility’s specification and drawing control system, in support of its engineering and production activities.

NOTE: When documentation is called for on a given item of data retained in the Repository, the charges (if charged as direct) will be to the appropriate data element.

L.3.7 Peculiar Support Equipment. The design, development, and production of those deliverable items and associated software required to support and maintain the system or portions of the system while the system is not directly engaged in the performance of its mission, and which are not common support equipment.

Includes, for example:
a. Vehicles, equipment, tools, etc., used to fuel, service, transport, hoist, repair, overhaul, assemble, disassemble, test, inspect, or otherwise maintain mission equipment
b. Any production of duplicate or modified factory test or tooling equipment delivered to the Government for use in maintaining the system. (Factory test and tooling equipment initially used by the contractor in the production process but subsequently delivered to the Government will be included as cost of the item produced.)
c. Any additional equipment or software required to maintain or modify the software portions of the system

Excludes, for example:
a. Overall planning, management and task analysis functions inherent in the Work Breakdown Structure element, systems Engineering/Program Management
b. Common support equipment, presently in the DoD inventory or commercially available, bought by the using command, not by the acquiring command

L.3.7.1 Test and Measurement Equipment. The peculiar or unique testing and measurement equipment that allows an operator or maintenance function to evaluate operational conditions of a system or equipment by performing specific diagnostics, screening or quality assurance effort at an organizational, intermediate, or depot level of equipment support.

Includes, for example:
a. Test measurement and diagnostic equipment, precision measuring equipment, automatic test equipment, manual test equipment, automatic test systems, test program sets, appropriate interconnect devices, automated load modules, tapes, and related software, firmware and support hardware (power supply equipment, etc.) Used at all levels of maintenance
b. Packages that enable line or shop replaceable units, printed circuit boards, or similar items to be diagnosed using automatic test equipment

L.3.7.2 Support and Handling Equipment. The deliverable tools and handling equipment used for support of the mission system.

Includes, for example:
a. Ground support equipment, vehicular support equipment, powered support equipment, non-powered support equipment, munitions material handling equipment, materiel handling equipment, and software support equipment (hardware and software)

L.3.8 Common Support Equipment. The items required to support and maintain the system or portions of the system while not directly engaged in the performance of its mission, and which are presently in the DoD inventory for support of other systems.

Includes, for example:
a. Acquisition of additional quantities of this equipment needed to support the item
b. All efforts required to assure the availability of this equipment to support the item

L.3.8.1 Test and Measurement Equipment. The common testing and measurement equipment that allows an operator or maintenance function to evaluate operational conditions of a system or equipment by performing specific diagnostics, screening or quality assurance effort at an organizational, intermediate, or depot level of equipment support.

Includes, for example:
a. Test measurement and diagnostic equipment, precision measuring equipment, automatic test equipment, manual test equipment, automatic test systems, test program sets, appropriate interconnect devices, automated load modules, tapes, and related software, firmware and support hardware (power supply equipment, etc.) Used at all levels of maintenance
b. Packages that enable line or shop replaceable units, printed circuit boards, or similar items to be diagnosed using automatic test equipment

L.3.8.2 Support and Handling Equipment. The deliverable tools and handling equipment used for support of the mission system.

Includes, for example:
a. Ground support equipment, vehicular support equipment, powered support equipment, non-powered support equipment, munitions material handling equipment, materiel handling equipment, and software support equipment (hardware/software)

L.3.9 Operational/Site Activation. The real estate, construction, conversion, utilities, and equipment to provide all facilities required to house, service, and launch prime mission equipment at the organizational and intermediate level.

Includes, for example:
a. Conversion of site, ship, or vehicle
b. System assembly, checkout, and installation (of mission and support equipment) into site facility or ship to achieve operational status
c. Contractor support in relation to operational/site activation

L.3.9.1 System Assembly, Installation, and Checkout on Site. The materials and services involved in the assembly of mission equipment at the site.

Includes, for example:
a. Installation of mission and support equipment in the operations or support facilities and complete system checkout or shakedown to ensure operational status. Where appropriate, specify by site, ship or vehicle.
b. The efforts and activities associated with shipping the system from contractor facility to customer site. That site could be a DT&E site, an installation and checkout site or any similar site that is outside the direct control of the contractor.

L.3.9.2 Contractor Technical Support. The materials and services provided by the contractor related to activation.

Includes, for example:
a. Repair of reparables, standby services, final turnover

L.3.9.3 Site Construction. Real estate, site planning and preparation, construction, and other special- purpose facilities necessary to achieve system operational status.

Includes, for example:
a. Construction of utilities, roads, and interconnecting cabling

L.3.9.4 Site/Ship/Vehicle Conversion. The materials and services required to convert existing sites, ships, or vehicles to accommodate the mission equipment and selected support equipment directly related to the specific system.

Includes, for example:
a. Operations, support, and other special purpose facilities conversion necessary to achieve system operational status, e.g., launch. Where appropriate, specify by site, ship or vehicle

L.3.9.5 Sustainment/Interim Contractor Support. The complex of equipment (hardware/software), data, and services required to operate, maintain, support and modernize prime mission product of existing operational systems done before the Material Support Date (MSD).

Includes, for example:
a. Prime Mission Product (PMP) maintenance and modernization. The cost for this element includes maintenance and modernization (including the development and production) of existing, operational systems. It excludes the development and production of the original prime mission product.
b. Support functions required to maintain and modernize the system, such as sustaining engineering, program management, logistics support, and supply chain management
c. Test and evaluation for system and subsystem modifications
d. Replacement of common and peculiar support equipment
e. Replacement of repairable items
f. Operational, maintenance and other personnel required at the operational unit level
g. Unit operations costs, including operating material and support services at the operating unit
h. Installation and personnel support functions in support of the unit level manpower

L.3.10 Industrial Facilities. The construction, conversion, or expansion of industrial facilities for production, inventory, and contractor depot maintenance required when that service is for the specific system.

Includes, for example:
a. Equipment acquisition or modernization, where applicable
b. Maintenance of these facilities or equipment
c. Industrial facilities for hazardous waste management to satisfy environmental standards

Excludes, for example:
a. Capital equipment

L.3.10.1 Construction/Conversion/Expansion. The real estate and preparation of system peculiar industrial facilities for production, inventory, depot maintenance, and other related activities.

L.3.10.2 Equipment Acquisition or Modernization. The production equipment acquisition, modernization, or transferal of equipment for the particular system. This pertains to Government owned and leased equipment under facilities contract.

L.3.10.3 Maintenance (Industrial Facilities). The maintenance, preservation, and repair of industrial facilities and equipment.

L.3.11 Initial Spares and Repair Parts. The deliverable spare components, assemblies and subassemblies used for initial replacement purposes in the materiel system equipment end item.

Includes, for example:
a. Repairable spares (repairables) and repair parts required as initial stockage to support and maintain newly fielded systems or subsystems during the initial phase of service, including pipeline and war reserve quantities, at all levels of maintenance and support

Excludes, for example:
a. Developmental Test spares and spares provided specifically for use during installation, assembly, and checkout on site. Lower level WBS breakouts should be by subsystem.

L.4 DEFINITIONS OF COMMON ELEMENTS APPLICABLE TO SPACE SYSTEMS

When the Space Appendix is used the common elements have been specifically grouped into four subcategories. These subcategories shall be used when creating program/contract WBS. Lower level elements to the four categories may be created but must sum to the correct category. The four common elements to be used are systems engineering, integration and test, program management, and support equipment (SEIT/PM and Support Equipment).

L.4.1 Space Systems. The Space community must report, at a minimum, the common elements of systems engineering, integration and test and program management (SEIT/PM) and Support Equipment. The following paragraphs represent WBS elements common to all Space System WBS elements.

L.4.1.1 SEIT/PM and Support Equipment. This section provides the WBS elements common to all Space System WBS elements. Consistent with the manner in which space systems are designed, built, and tested, there are multiple levels of Systems Engineering, Integration and Test, and Program Management (SEIT/PM) and Support Equipment throughout the WBS. It is expected that, whenever possible, SEIT/PM and Support Equipment costs be reported with the item(s) they are supporting. For example, subsystem management of the Attitude Control Subsystem should be booked under the ACS WBS element. If a contractor (or other developer) manages the project by a different means and does not collect SEIT/PM and Support Equipment data at this level, then the costs shall be reported at the next higher-level WBS element. For example, an electronics product manager with areas of responsibility spanning both ACS and the TT&C subsystems cost may have their effort defined and collected within the Spacecraft Bus SEIT/PM elements. SEIT/PM and Support Equipment shall be broken out into their individual elements (defined below) for WBS levels one through four (subsystem). At level five (product level), Systems engineering and management (SEPM) responsibilities are often indistinct and may be combined into a single SEPM element.

L.4.1.1.1 Systems Engineering. This WBS element contains all the resources associated with all engineering from functional specialists who provide technical planning, technical management, analysis, and support efforts for development and production activities. The Systems Engineering entity is responsible for the analysis, derivation, allocation, and traceability, of requirements and interfaces.

Includes, for example:
a. Systems definition
b. Systems analysis (e.g., thermal, power, mass properties, environments, dynamics, modeling and simulation)
c. Requirements analysis and allocation
d. Interface definition and control
e. Performance assessment and verification/validation
f. Technical direction (SE leadership, planning, and coordination)
g. System safety
h. Quality assurance, product assurance
i. mission assurance and critical skill protection and retention
j. Logistics Support Analysis (LSA including reliability, availability, maintainability, produceability)
k. Engineering services
l. Configuration control
m. System documentation
n. Algorithm development
o. Recommended Operating Procedures (PROCs), Satellite Databases
p. Risk management
q. Human engineering
r. Security engineering
s. Electro-Magnetic Compatibility (EMC) / Electro-Magnetic Interference (EMI)
t. Radiation and survivability
u. Contamination and control
v. Autonomy and fault management
w. Other specialty engineering
x. Engineering and design (excluding box level) including Electrical Design Integration (EDI), Mechanical Design Integration (MDI), Thermal Design Integration (TDI), and Facility Design
y. Parts, material and processes (PM&P)
z. Trade studies aa. System studies

Excludes, for example:
a. Systems engineering efforts that can be associated specifically with the equipment (Hardware/Software) for a unit or CSCI (Level 5 element)
b. Launch systems integration that is contained in its own Level 3 element

L.4.1.1.2 Assembly, Integration and Test. This element includes the effort of technical and functional activities required to assemble and test at one level into a next higher level (e.g., from product level to subsystem level) as a whole and not directly part of any other individual element.

Includes, for example:
a. Development of test plans and procedures
b. Test preparations
c. Test support and management
d. HW/SW integration
e. SW CSCI integration
f. HW integration and assembly (e.g., electrical and mechanical integration, including kitting)
g. Test, checkout, inspection and acceptance
h. System test and evaluation to include: Developmental Test and Evaluation, Operational Test and Evaluation
i. I&T management, leadership, planning and scheduling
j. Analysis and documentation of test results
k. Transportation and movement (excludes transportation of the Space Vehicle to the launch pad covered under the Launch Operations WBS element)
l. Integration hardware
m. Delivered initial spares and repair parts
n. I&T Facilities

Excludes, for example:
a. Integration and test efforts that can be associated specifically with the equipment (Hardware/Software) for a unit or CSCI (Level 5 element)

L.4.1.1.3 Program Management. Program Management (PM) includes the resources necessary to manage, direct, and control all effort contributing to the development, production of custom and commercial off-the-shelf (COTS) procurements and integration. Additionally, it includes training related items used to facilitate instruction through which personnel will learn to operate and maintain the system and elements of the system. Data related items are also captured here, such as the deliverable data required to be listed on a Contract Data Requirements List (CDRL).

Includes, for example:
a. Project management
b. Business management (includes business operations., scheduling, accounting and finance)
c. Project control and planning
d. Configuration management
e. Contract / subcontract management
f. Security management
g. Delivered data, including, for example: 1. Technical publications and technical manuals 2. Cost and Schedule Reporting (CPR, CFSR, IMS, WBS, etc.) 3. Training plans, manuals, guides
h. Data management including data repository and associated drafting and clerical effort to maintain master, Government approved, and Government owned documents
i. Administration
j. Product effectiveness
k. Training services to include: course development, material preparation, and conducting initial training

Excludes, for example:
a. Program management efforts that can be associated specifically with the equipment (Hardware/Software) for a unit or CSCI (Level 5 element)

L.4.1.1.4 Systems Engineering and Program Management (SEPM). This element can be used at Level 5 (and below) of the WBS when Systems Engineering and Program Management are inseparable. This WBS element is a combination of the Systems Engineering and the Program Management responsibility, task, and deliverable content defined above.

L.4.1.1.5 Support Equipment. This element pertains to the design, development, and production of those items and associated software required to build, assemble, integrate, move, support and maintain the system or portions of the system. This also pertains to the testing and measurement equipment that allows an operator or maintenance function to evaluate operational conditions of a system or equipment by performing specific diagnostics, screening, or quality assurance efforts.

Includes, for example:
a. Peculiar Support Equipment (PSE)
b. Common Support Equipment (CSE)
c. Tooling, (e.g., taps, dies, etc.)
d. Mock-ups/System Integration Labs (SILs), Simulators, Stimulators, and training equipment (excludes EMs of Space Vehicle HW that is included within the Space Vehicle HW WBS elements)
e. Vehicles, equipment, tools, and the like used to fuel, service, transport, hoist, repair, overhaul, assemble, disassemble, test, inspect, or otherwise maintain mission equipment
f. Any production of duplicate or modified factory test or tooling equipment delivered to the government for use in maintaining the system
g. Support and handling equipment including ground, vehicular, powered, non-powered, and materiel handling
h. Electrical Aerospace Ground Equipment and Mechanical (AGE)
i. Precision measuring equipment
j. Automatic test equipment
k. Manual test equipment
l. Test program sets
m. Automated load modules
n. Support equipment software

Excludes, for example:
a. Support equipment efforts that can be associated specifically with the equipment (Hardware/Software) for a unit or CSCI (Level 5 element).

L.5 DEFINITIONS OF COMMON ELEMENTS APPLICABLE TO LAUNCH VEHICLE SYSTEMS.

The Launch Vehicle community has unique application of systems engineering, integration and test and program management (SEIT/PM). The following paragraphs represent the SEIT/PM WBS elements common to Launch Vehicle System elements. For the remaining Common Elements, reference paragraph L.3 Definitions of Common Elements.

L.5.1 SEIT/PM. This section provides the WBS elements common to all Launch Vehicle System WBS elements. Consistent with the manner in which launch vehicle systems are designed, built, and tested, there are multiple levels of Systems Engineering, Integration and Test, and Program Management (SEIT/PM) throughout the WBS. It is expected that, whenever possible, SEIT/PM costs be reported with the item(s) they are supporting. For example, subsystem management of the Reaction Control Subsystem should be booked under the Reaction Control System WBS element.

L.5.1.1 Systems Engineering. This WBS element contains all the resources associated with all engineering from functional specialists who provide technical planning, technical management, analysis, and support efforts for development and production activities. The Systems Engineering entity is responsible for the analysis, derivation, allocation, and traceability, of requirements and interfaces.

Includes, for example:
a. Systems definition
b. Systems analysis (e.g., thermal, power, mass properties, environments, dynamics, modeling and simulation)
c. Requirements analysis and allocation
d. Interface definition and control
e. Performance assessment and verification/validation
f. Technical direction (SE leadership, planning, and coordination)
g. System safety
h. Quality assurance, product assurance
i. Mission assurance and critical skill protection and retention
j. Logistics Support Analysis (LSA including reliability, availability, maintainability, produceability)
k. Engineering services
l. Configuration control
m. System documentation
n. Algorithm development
o. Recommended Operating Procedures (ROPs), Procedures (PROCs), Satellite Databases
p. Risk management
q. Human engineering
r. Security engineering
s. Electro-Magnetic Compatibility (EMC) / Electro-Magnetic Interference (EMI)
t. Radiation and survivability
u. Contamination and control
v. Autonomy and fault management
w. Other Specialty Engineering
x. engineering and design (excluding box level) including Electrical Design Integration (EDI), Mechanical Design Integration (MDI), Thermal Design Integration (TDI), and Facility Design
y. Parts, material and processes (PM&P)
z. Trade studies aa. System studies

Excludes, for example:
a. Systems engineering efforts that can be associated specifically with the equipment (Hardware/Software)

L.5.1.2 Assembly, Integration and Test. This element includes the effort of technical and functional activities required to assemble and test at one level into a next higher level (e.g., from product level to subsystem level) as a whole and not directly part of any other individual element.

Includes, for example:
a. Development of test plans and procedures
b. Test preparations
c. Test support and management
d. HW/SW Integration
e. SW CSCI Integration
f. HW Integration and Assembly (e.g., Electrical and Mechanical Integration, including kitting)
g. Test, checkout, inspection and acceptance
h. System test and evaluation to include: Developmental Test and Evaluation, Operational Test and Evaluation)
i. I&T management, leadership, planning and scheduling
j. Analysis and documentation of test results
k. Transportation and movement (excludes transportation of the space vehicle to the launch pad (covered under the Launch Operations WBS element)
l. Integration hardware
m. Delivered initial spares and repair parts
n. I&T Facilities

Excludes, for example:
a. Integration and test efforts that can be associated specifically with the equipment (Hardware/Software)

L.5.1.3 Program Management. Program Management (PM) includes the resources necessary to manage, direct, and control all effort contributing to the development, production of custom and commercial off-the-shelf (COTS) procurements and integration. Additionally, it includes training related items used to facilitate instruction through which personnel will learn to operate and maintain the system and elements of the system. Data related items are also captured here, such as the deliverable data required to be listed on a Contract Data Requirements List (CDRL).

Includes, for example:
a. Project management
b. Business management (includes business operations., scheduling, accounting and finance)
c. Project control and planning
d. Configuration management
e. Contract / subcontract management
f. Security management
g. Delivered data, including, for example: 1. Technical publications and technical manuals 2. Cost and Schedule Reporting (CPR, CFSR, IMS, WBS, etc.) 3. Training plans, manuals, guides
h. Data management including data repository and associated drafting and clerical effort to maintain master, Government approved, and Government owned documents
i. Administration
j. Product effectiveness
k. Training services to include: course development, material preparation, and conducting initial training

Excludes, for example:
a. Program management efforts that can be associated specifically with the equipment (Hardware/Software)

L.5.2 Operational Site Activation. The Common element Operational Site Activation (L.3.9) should be captured under the Launch Vehicle Element Launch Site (1…n) referenced in Appendix J, paragraph J.4.5.

L.6 DEFINITIONS OF COMMON ELEMENTS APPLICABLE TO AUTOMATED INFORMATION SYSTEMS.

L.6.1 Systems Engineering or Systems Analysis (Blueprinting). The technical and management efforts of directing and controlling a totally integrated engineering effort of a system or program.

Includes, for example:
a. System definition, overall system design, design integrity analysis, system optimization, system/cost effectiveness analysis, and intra-system and inter-system compatibility assurance, etc.; the integration and balancing of reliability, maintainability, producibility, safety, human health, environmental protection, and survivability; security requirements, configuration management and configuration control; quality assurance program, value engineering, preparation of equipment and component performance specifications, design of test and demonstration plans; determination of software development or software test facility/environment requirements.
b. Preparation of the Systems Engineering Plan (SEP), specification tree, program risk analysis, system planning, decision control process, technical performance measurement, technical reviews, subcontractor and vendor reviews, work authorization, and technical documentation control.
c. Reliability engineering—the engineering process and series of tasks required to examine the probability of a device or system performing its mission adequately for the period of time intended under the operating conditions expected to be encountered.
d. Maintainability engineering—the engineering process and series of tasks required to measure the ability of an item or system to be retained in or restored to a specified condition of readiness, skill levels, etc., using prescribed procedures and resources at specific levels of maintenance and repair.
e. Human systems integration—the engineering process and the series of tasks required to define, as a comprehensive technical and engineering effort, the integration of doctrine, manpower, and personnel integration, materiel development, operational effectiveness, human characteristics, skill capabilities, training, manning implication, and other related elements into a comprehensive effort.
f. Supportability analyses—an integral part of the systems engineering process beginning at program initiation and continuing throughout program development. Supportability analyses form the basis for related design requirements included in the system specification and for subsequent decisions concerning how to most cost effectively support the system and its infrastructure over its entire life cycle.
g. System of Systems (SoS) and System Level Architecting, modeling and simulation, verification and validation and external interface definition and management.
h. Weapon Systems Integration (WSI) – an overarching set of tools and processes which enables the integration of sound engineering practices at the system level; the impetus being the sustainment of safety, suitability and effectiveness for the life of the system. Includes the ability to return systems to specification level performance after repair/overhaul activities. WSI is and integral process through which operational safety, suitability, and effectiveness (OSS&E) are implemented.

L.6.2 Program Management. The business and administrative planning, organizing, directing, coordinating, controlling, and approval actions designated to accomplish overall program objectives, which are not associated with specific hardware elements and are not included in systems engineering.

Includes , for example:
a. Cost, schedule, performance measurement management, warranty administration, contract management, data management, vendor liaison, subcontract management, etc.
b. Support element management, defined as the logistics tasks management effort and technical control, and the business management of the support elements. The logistics management function encompasses the support evaluation and supportability assurance required to produce an affordable and supportable defense materiel system
c. Planning and management of all the functions of logistics. Examples are, Maintenance support planning and support facilities planning; other support requirements determination; support equipment; supply support; packaging, handling, storage, and transportation; provisioning requirements determination and planning; training system requirements determination; computer resource determination; organizational, intermediate, and depot maintenance determination management; and data management

L.6.3 Change Management. Change management refers to the broad process for managing organizational change. Change management encompasses planning, oversight or governance, project management, testing and implementation.

L.6.4 System Test and Evaluation. The use of pilot, production, or specifically configured systems to obtain or validate engineering data on the performance of the system during the developmental phase (normally funded from RDT&E) of the program. It also includes all effort associated with the development of any specialized tools or data in support of the system level test program.

Includes, for example:
a. Developmental test and evaluation
b. Operational test and evaluation
c. Mock-ups/System Integration Labs (SIL)
d. Test support
e. Test facilities

L.6.4.1 Developmental Test and Evaluation. This effort is planned, conducted and monitored by the developing agency of the DoD component. It includes test and evaluation conducted to:
a. Demonstrate that the engineering design and development process is complete.
b. Demonstrate that the design risks have been minimized
c. Demonstrate that the system will meet specifications
d. Estimate the system’s military utility when introduced
e. Determine whether the engineering design is supportable (practical, maintainable, safe, etc.) For operational use
f. Provide test data with which to examine and evaluate trade-offs against specification requirements, life cycle cost, and schedule
g. Perform the logistics testing efforts to evaluate the achievement of supportability goals, the adequacy of the support package for the system, (e.g., deliverable maintenance tools, test equipment, technical publications, maintenance instructions, and personnel skills and training requirements, etc.)

Includes, for example:
a. All system developer in-house effort
b. All programs, where applicable; models, tests and associated simulations; integration ground tests; qualification test and evaluation, test instrumentation, environmental tests, test facility operations, test equipment (including its support equipment), and logistics testing
c. Qualification test
d. Accreditation
e. Independent verification and validation
f. Test software

L.6.4.2 Operational Test and Evaluation. The test and evaluation conducted by agencies other than the developing command to assess the prospective system’s military utility, operational effectiveness, operational suitability, logistics supportability (including compatibility, inter-operability, reliability, maintainability, logistic requirements, etc.), cost of ownership, and need for any modifications.

Includes, for example:
a. Initial operational test and evaluation conducted during the development of a system
b. Such tests as system demonstration, qualification operational test and evaluation, etc., and support thereto, required to prove the operational capability of the deliverable system
c. Contractor support (e.g., technical assistance, maintenance, labor, material, etc.) Consumed during this phase of testing
d. Logistics testing efforts to evaluate the achievement of supportability goals and the adequacy of the support for the system (e.g., deliverable maintenance tools, test equipment, technical publications, maintenance instructions, personnel skills and training requirements, and software support facility/environment elements)

L.6.4.3 Mock-ups/System Integration Labs. The design engineering and production of system or subsystem “mock-ups”, which have special contractual or engineering significance, or which are not required solely for the conduct of one of the above elements of testing. SILs are often used in lieu of (or in addition to) mock-ups. SILs are risk reduction facilities where software and hardware can be developed, integrated, tested and evaluated for both stand alone functionality and/or interoperability prior to being fielded.

Includes, for example:
a. Hardware/lab equipment
b. SIL software (written to simulate the operating environment or written to operate the SIL)

L.6.4.4. Test Facilities. The special test facilities required for performance of the various developmental test necessary to prove the design and reliability of the system or subsystem.

Includes, but not limited to:
a. Test tank test fixtures, white rooms, test chambers

Excludes, for example:
a. Brick and mortar-type facilities identified as industrial facilities

L.6.5 Training. Deliverable training services, devices, accessories, aids, equipment, and parts used to facilitate instruction through which personnel will learn to operate and maintain the system with maximum efficiency.

Includes, for example:
a. All effort associated with the design, development, and production of deliverable training equipment and its associated software as well as the execution of training services
b. Operational trainers, maintenance trainers, and other items such as cutaways, mock-ups, and models
c. Training course material development; contractor-conducted training (in-plant and service training); and the materials and curriculum required to design, execute, and produce a contractor developed training program
d. Materiel, courses, and associated documentation (primarily the computer software, courses and training aids)
e. Modification or rehabilitation of existing facilities used to accomplish training objectives
f. Development
g. Training and professional development
h. Training software

Excludes, for example:
a. User training costs

L.6.6 Data. The deliverable data required to be listed on a contract data requirements list, DD Form 1423.

Includes, for example:
a. Technical publication
b. Engineering data
c. Management data
d. Support data
e. Data repository

L.6.6.1 Technical Publication. Technical data, providing instructions for installation, operation, maintenance, training, and support, formatted into a technical manual. Data may be presented in any form regardless of the form or method of recording. Technical orders that meet the criteria of this definition may also be classified as technical manuals.

Includes, for example:
a. Operation and maintenance instructions, parts lists or parts breakdown, and related technical information or procedures exclusive of administrative procedures
b. Data item descriptions set forth in categories selected from the Acquisition Management Systems and Data Requirements Control List (DoD 5010.12-L)

L.6.6.2 Engineering Data. Recorded scientific or technical information (regardless of the form or method of recording) including computer software documentation. Engineering data defines and documents an engineering design or product configuration (sufficient to allow duplication of the original items) and is used to support production, engineering and logistics activities.

Includes, for example:
a. All final plans, procedures, reports, and documentation pertaining to systems, subsystems, computer and computer resource programs, component engineering, operational testing, human factors, reliability, availability, and maintainability, and other engineering analysis
b. Technical data package (re-procurement package) that includes all engineering drawings, associated lists, process descriptions, and other documents defining physical geometry, material composition, and performance procedures

Excludes, for example:
a. Computer software or financial, administrative, cost or pricing, or management data or other information incidental to contract administration

L.6.6.3 Management Data. The data items necessary for configuration management, cost, schedule, contractual data management, program management, etc. (required by the Government).

Includes, for example:
a. Contractor cost reports, cost performance reports, contract funds status reports, schedules, milestones, networks, integrated support plans

L.6.6.4 Support Data. The data items designed to document support planning in accordance with functional categories.

Includes, for example:
a. Supply; general maintenance plans and reports; training data; transportation, handling, storage, and packaging information; facilities data; data to support the provisioning process and all other support data; and software supportability planning and software support transition planning documents

L.6.6.5 Data Repository. The facility designated to act as custodian to maintain a master engineering specification and establish a drawing depository service for Government approved documents that are the property of the U.S. Government. As custodian for the Government, the repository, authorized by approved change orders, maintains these master documents at the latest approved revision level. This facility is a distinct entity.

Includes, for example:
a. All drafting and clerical effort necessary to maintain documents

Excludes, for example:
a. All similar effort for facility’s specification and drawing control system, in support of its engineering and production activities

L.6.7 Peculiar Support Equipment. The design, development, and production of those deliverable items and associated software required to support and maintain the system or portions of the system while the system is not directly engaged in the performance of its mission, and which are not common support equipment.

Includes, for example:
a. Any production of duplicate or modified factory test or tooling equipment delivered to the Government for use in maintaining the system. (Factory test and tooling equipment initially used by the contractor in the production process but subsequently delivered to the Government will be included as cost of the item produced.)
b. Any additional equipment or software required to maintain or modify the software portions of the system

Excludes, for example:
a. Overall planning, management and task analysis functions inherent in the work breakdown structure element, systems Engineering/Program Management
b. Common support equipment, presently in the DoD inventory or commercially available, bought by the using command, not by the acquiring command

L.6.8 Common Support Equipment. The items required to support and maintain the system or portions of the system while not directly engaged in the performance of its mission, and which are presently in the DoD inventory for support of other systems.

Includes, for example:
a. Acquisition of additional quantities of this equipment needed to support the item
b. All efforts required to assure the availability of this equipment to support the item

L.6.9 Operational Site Activation (Production/Deployment). The costs associated with deploying the AIS solution at the). user site(s). This should cover only those efforts that are incurred at the implementation site. Any up-front effort involved with designing/engineering the solution for a particular site should be included in under Client-side Site Development. Any effort related to re-design of the solution once implementation has begun should be captured here.

Includes, for example (by site type):
a. Deployment hardware and software
b. Site activation labor
c. User training
d. Data migration

Note: This element will also include the real estate, construction, conversion, utilities, and equipment to provide all facilities required to house, service, and launch the AIS solution at the user sites.

L.6.9.1 Site Type 1. Captures the costs associated with the primary site type for the AIS implementation. Site types should be specifically defined.

L.6.9.1.1 Deployment Hardware and Software.

L.6.9.1.1.1 Deployment Hardware. Included in this element should be any Commercial-Off-the-Shelf (COTS) hardware purchased for the primary site type 1.

Includes, for example:
a. Processing equipment (servers, CPUs, etc.)
b. Network/communications
c. Storage
d. Security/crypto
e. UPS
f. Other/ancillary equipment

Excludes, for example:
a. Development /test hardware (captured with the prime mission product)

L.6.9.1.1.2 Deployment Software. Included in this element should be any Commercial-Off-the-Shelf (COTS) deployment software purchased for the primary site type 1. This would include the purchase of software licenses related to the AIS solution.

L.6.9.1.1.3 User Documentation (Place Holder).

L.6.9.1.2 Site Activation. This element includes the costs associated with shipping costs to the site, site survey, site preparation, equipment installation, equipment integration, test and checkout to allow implementation of the AIS solution. This should cover only those efforts that are incurred at the implementation site. Any effort related to re-design of the solution once implementation has begun should be captured here.

L.6.9.1.3 User Training. This element represents the effort involved with training the users of the implemented AIS solution at the user sites. The primary cost captured here will be the labor costs of instructors to train users on the new system and business processes required to operate within the new system(s). Any costs incurred as a result of revising the training courses and/or materials once implementation has begun should also be captured here.

Excludes, for example:
a. Any up-front costs associated with training the trainers, as well as course development and material costs that are not incurred as a result of circumstances encountered at the user sites

L.6.9.1.4 Data Migration. This element includes the effort for translating data from one format to another. This should cover only those efforts that are incurred at the implementation site. Also include any expense associated with the transition of data from the legacy systems to the AIS solution. Use lower levels to identify individual legacy systems.

Includes, for example:
a. Data translation
b. Data cleansing
c. Data loading

Excludes, for example:
a. External System Interface Development

Note: Data migration is necessary when an organization decides to use a new computing systems or database management system that is incompatible with the current system. Typically, data migration is performed by a set of customized programs or scripts that automatically transfer the data.

L.6.9.1.5 Management/Engineering Support. This element captures those support elements that are attributable only to specific user /implementation sites. This would include systems engineering/program management effort associated with a specific site, as well as any system test and evaluation specific to particular user sites.

L.6.9.1.6 Interim Logistics Support. Interim Logistics Support (ILS) costs represent those costs associated with transitioning the system from a contractor supported system to an organically supported system. This could include system maintenance, business process re-engineering, and change management efforts performed by the contractor in the interim before the Government is able to perform these tasks. Also includes operation and Maintenance up to FOC. This element captures the costs of supporting the AIS solution once Operational Site Activation (element L.6.9) is complete and the system has reach full operational capability (FOC). These could be costs incurred as a result of continuing contractor support or by the Government.

Includes, for example:
a. Systems engineering and program management
b. System operations / sustaining engineering
c. Help desk
d. System database administration
e. Deployment hardware/software refresh
f. Software maintenance
g. Follow on training
h. Accreditation
i. Independent verification and validation

L.6.10 Industrial Facilities. The construction, conversion, or expansion of industrial facilities for production, inventory, and contractor depot maintenance required when that service is for the specific system. This may be a Software Integration Laboratory (SIL).

Includes, for example:
a. Equipment acquisition or modernization, where applicable
b. Maintenance of these facilities or equipment
c. Industrial facilities for hazardous waste management to satisfy environmental standards

Excludes, for example:
a. Capital equipment

L.6.11 Initial Spares and Repair Parts. The deliverable spare components, assemblies and subassemblies used for initial replacement purposes in the materiel system equipment end item.

Includes, for example:
b. Repairable spares (repairables) and repair parts required as initial stockage to support and maintain newly fielded systems or subsystems during the initial phase of service, including pipeline and war reserve quantities, at all levels of maintenance and support

Excludes, for example:
b. Developmental test spares and spares provided specifically for use during installation, assembly, and checkout on sit, lower level WBS breakouts should be by subsystem

CONCLUDING MATERIAL

Custodians: Preparing Activity Army – MI OSD-WB Navy-SH Air Force – 10 (Project No. MISC-2010-002) Review Activities: Army-AR, AT, AV, CR Navy-AS, MC, OS Air Force-11, 16, 19, 70, 71, 84

NOTE: The activities listed above were interested in this document as of the date of this document. Since organizations and responsibilities can change, you should verify the currency of the information above using the ASSIST Online database at https://assist.daps.dla.mil