Attachment 7 DIDs Consolidated.pdf

Source: http://www.assistdocs.com -- Downloaded: 2012-10-03T15:14Z Check the source to verify that this is the current version before use.

Source: http://www.assistdocs.com -- Downloaded: 2013-08-20T16:27Z

DATA ITEM DESCRIPTION

Title: Status Report

Number: DI-MGMT-80368A Approval Date: 30 OCT 2006 AMSC Number: 7619 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship:

The Status Report documents the status of contractor effort towards achieving contract objectives. It identifies accomplishments to date and difficulties encountered, and compare the status achieved to planned goals and the resources expended. It is used by the Government to monitor and evaluate contractor performance.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

It is not intended that all requirements herein should be applied to every program.

Portions of the DID are subject to tailoring by deletion depending on the specific status reporting requirements of the project.

This DID is related to DI-FNCL-80331, Funds and Man-Hour Expenditure Report which can be used in conjunction with this report if paragraph 3.2.3 below is deleted.

This DID supersede DI-MGMT-80368.

Requirements:

1. Reference documents. None.

2. Format. The Status Report shall be in contractor format.

2.1 Identification. The data indicated below shall be contained on a title page or on the first page of the report.

a. Title/identification of the system/component/program/project.

Source: http://www.assistdocs.com -- Downloaded: 2013-04-26T16:12Z

DI-MGMT-80368A

b. Type of report (e.g., monthly, interim, final).

c. Period covered by the report.

d. Contract number.

e. Preparing activity or contractor’s title.

f. Security classification, when required.

g. Distribution Statement.

2.2 Page size. The report shall be on 8 ½ by 11 inch (metric A4) paper.

3. Content. The report shall contain the following:

3.1 Summary. The summary shall include a brief statement of the overall project status , covering the accomplished technical activities and development, objectives of efforts, summary results of efforts, identification of major problems/deficiencies with impact, and recommended solutions.

3.2 Body of report. The Status Report shall contain the following items, where applicable:

3.2.1 Milestone/task status. The status of each milestone/task as defined by the statement of work or contract, as applicable:

a. A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include an overall status of each milestone, task, or unit of work. Include update schedule sheets, milestone charts, or task synopsis sheets identifying phase of task and percentage of completion of each task, technical instruction, or order.

b. A comparison of achieved end-product performance capabilities projected against contract baseline values, requirements, or allocations.

c. Effort expended on each task to date, and a brief description of technical developments and accomplishments.

d. Key dates in any testing program and description of tests performed and significant test results. If applicable, a description of the amount and type of down time on the equipment or system under test.

e. A list of all designs completed and a brief description of each item. For designs in process, provide estimated dates for design and drawing completion.

f. A narrative of outstanding problems existing as of the previous status report, and their resolution status. 2

DI-MGMT-80368A

g. New problem areas encountered or anticipated, their effect on the overall work effort/project and steps being taken to remedy problem situations.

h. Significant results of conferences, trips, or directives for the Contracting officer’s representatives.

i. Any other information which may cause significant changes in the program schedule.

3.2.2 Future plans. Summary of future plans, recommendations and proposals both for the next reporting period and for any long term plans.

3.2.3 Itemized man-hours and costs. Itemized man-hour and cost expenditure incurred for the reporting period by category and task, total contractual expenditures, and funds remaining as of the reporting date.

3.2.4 Contract deliveries status. The status of each deliverable end item, including data deliverables, as required by the contract. Provide item and contract identification, shipping/transmittal data, acceptance status, security classification, and schedule due date information.

3.2.5 Report preparer. Name of person(s) preparing report and telephone number(s).

3.3 Appendices. Appendices where applicable, for tables, references, charts, or other descriptive material. Each appendix shall be identified and referenced in the appropriate area of the report.

4. END OF DI-MGMT-80368A

Title: Contract Work Breakdown Structure

Number: DI-MGMT-81334D Approval Date: 20110518

AMSC Number: D9199 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: CAPE

Applicable Forms: Not Applicable

Use/relationship: This documents the Contract Work Breakdown Structure (CWBS) and its extension by the contractor using terminology and definitions, as applicable, in MIL-

HDBK-881.

This DID summarizes the format for the CWBS and provides preparation instructions to support the data and frequency requirements specified in the contract. This DID applies to all contracts that require a Work Breakdown Structure (WBS). It is related to the four

Contractor Cost Data Reporting (CCDR) formats: DD Form 1921, “Cost Data Summary

Report” (DI-FNCL-81565); DD Form 1921-1, “Functional Cost-Hour Report”

(DI-FNCL-81566); and DD Form 1921-2, “Progress Curve Report” (DI-FNCL-81567);

This DID is also related to the “Contract Performance Report” (DI-MGMT-81466) and

DD Form 1586, “Contract Funds Status Report” (DI-MGMT-81468).

For those contracts with Cost and Software Data Reporting (CSDR) requirements, the

CWBS must agree with the contract CSDR Plan approved by the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA).

The purpose and intent of the CWBS and CWBS dictionary is to document the contractor’s deliverable products and planned approach to performing the contract scope of work. It also contains the technical description of the military end item being developed/procured by the contract. The technical definitions and descriptions of each product-oriented (i.e., hardware) WBS element should be derived from the contractor’s systems engineering Integrated Product Team (IPT) or related technical department. The cost content of each WBS element definition should be produced by the contractor’s finance department.

MIL-HDBK-881 serves as the basis for developing the CWBS. Routine reporting shall be at CWBS level 3 for all contractors. Extensions of the CWBS can be tailored to the specific program but will be consistent with MIL-HDBK-881. More detailed reporting of the CWBS shall be required only for those lower-level elements that address high-risk, high-value, or high-technical-interest areas of a program. Identifying these additional elements for inclusion in the CWBS is a critical early assignment for the Cost Working-

Group Integrated Product Team (CWIPT) for inclusion in the CWBS.

The reporting contractor must prepare and submit, using the CSDR Submit-Review

System, the first contract CWBS Index and Dictionary at the same time the first Interim

Report is due or, when the Initial Report, if required, is due. However, contractors also have the option to submit the Index and Dictionary earlier to facilitate report planning.

The reporting contractor must also maintain and update the Dictionary throughout the life of the contract. If changes to the CWBS occur, the contractor must submit an updated

CWBS Index and Dictionary with the next affected CSD Reports. The contractor is not

DI-MGMT-81334D

required to submit the updated CWBS Index and Dictionary more frequently than its

CSDR submissions.

This DID supersedes DI-MGMT-81334C.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in ASSIST at the time of the solicitation; or, for non-ASSIST documents, as stated herein.

2. References.

a. MIL-HDBK-881, “Work Breakdown Structures for Defense Materiel Items,” available at http://dcarc.pae.osd.mil.

b. DoD 5000.4-M, “Cost Analysis Guidance and Procedures,” [current version], available at http://www.dtic.mil/whs/directives/.

c. DoD 5000.04-M-1, “Cost and Software Data Reporting (CSDR) Manual,”

[current version], available at http://www.dtic.mil/whs/directives/.

d. DD Form 2794, “Cost and Software Data Reporting Plan,” [current version], available at http://www.dtic.mil/whs/directives/. Commonly referred to as the

CSDR Plan, a completed DD Form 2794 must be approved by the OSD DDCA.

3. Formats. The CWBS shall be reflected in an electronic report that consists of two parts. The first part, the CWBS Index, lists the individual elements by their CWBS

Codes and Levels. The second part, the CWBS Dictionary, describes the effort and tasks associated with every CWBS element shown in the CWBS Index. Examples of the

CWBS Index and CWBS Dictionary are shown in Figures 1 and 2, respectively. These are examples only, and are not intended to be a set format. If a contractor wishes to use an existing WBS internal to its organization, the contractor must first map their internal elements and definitions to the OSD DDCA-approved CSDR plan, and then develop a

CWBS that conforms to the guidance in this DID.

The CWBS Dictionary must be submitted as a stand-alone Word-compatible file to the

Defense Cost and Resource Center (DCARC) secure Web site using the CSDR Submit-

Review System. Uploading requires the use of a DoD Common Access Card (CAC) or a

DoD-approved External Certificate Authority (ECA) certificate. See the DCARC Web site for certificate instructions.

Preparation Instructions:

1. Contract Work Breakdown Structure Index:

a. CWBS Code. Enter the code, if applicable. The CWBS codes used in the CWBS

Index and Dictionary must be identical to those in the OSD DDCA-approved contract CSDR Plan. The preferred convention is to use a numeric structure starting with 1.0 for the level 1 CWBS element (as displayed in Figure 1. CWBS

Index Example). Every element on the OSD DDCA-approved CSDR Plan must be included in the Index, regardless of applicability on the contract. The contractor must not include any elements that are not on the OSD DDCA-approved CSDR plan.

b. CWBS Element Level c.

. Enter the level of the CWBS element. Level 1 is the total contract. Levels 2, 3, and so on, are successively lower levels of the contract.

CWBS Element Name

2. Contract Work Breakdown Structure Dictionary:

. Enter the title of the CWBS element using the specific name or nomenclature. The CWBS element names used in the CWBS Index and

Dictionary must be identical to those in the OSD DDCA-approved contract CSDR

Plan.

a. CWBS Code b.

. Enter the same codes used in the Index.

CWBS Element Name c.

. Enter the same element names used in the Index.

CWBS Definition

The CWBS dictionary must also include a description of the cost and work content for each element. Cost content definitions must include explanations of recurring versus nonrecurring efforts, functional cost element inclusion or exclusion, and purchased versus made in-house decisions. The description of the cost content must also include characterizations by functional category (i.e., engineering, tooling, quality control, and manufacturing) as appropriate. The cost content portion of the definition for each element should be tied to the contractor’s control account, work package, and work scope definitions. The work content definition must include a short description of the process used to design, produce or sustain the end item or service. The description must address the types of activities (e.g., design, production, analysis, or management) included within the WBS element. These descriptions must include information on whether the reporting contractor or a supplier/subcontractor is performing the work being described.

. Enter a complete description of the technical, cost, and work content of each CWBS element. For the technical content, the dictionary must include a general system level description (i.e., highest level WBS element) of the military end item that captures top-level attributes of the system. If the system has a known official military designation (e.g., AN/ S L Q -32A (V)2), this designation should be included in the top-level description. The contractor must provide general descriptions of the physical characteristics of each individual element below the system level. It is important that the contractor specify all hardware and software equipment that are associated with each WBS element.

Each WBS element definition must provide the end user with the means to determine what the item is, what it does within the system, and how the item is physically defined.

CWBS dictionaries must reflect only the work being done on the contract for which the document is being submitted. If work is not expected to occur for a given WBS element, the CWBS dictionary definition must indicate that this element is not applicable. If work at some elements is being performed by a supplier/subcontractor, the dictionary must state this. Similarly, if the CWBS is for a subcontract/supplier, the work defined for each element must be specific to the subcontractor/supplier’s scope of effort, and must not include the prime contractor’s work. Definitions of a generic nature are acceptable for some parent level elements provided that more detailed definitions are given for the lower level elements. If there are GFE items being integrated into the end item, it is not expected that a detailed description of those items be provided, however, all GFE items being integrated into the system as part of the contract must be labeled as such in the CWBS dictionary under the appropriate elements.

Figure 1. CWBS Index Example (based on MIL-HDBK-881 Missile Systems)

Program: Vector Surface to Air Interceptor RFP NO: XXXXX Contract Plan No: A-10-X-C1

Contract No: DAAE07-XX-E-0001

DATE: 6/14/2010

CWBS CODE

1 2 3 4 5

1.0 X Vector Surface to Air Interceptor Missile System

1.1 X Air Vehicle

1.1.1 X Propulsion (Stages I...n,]

1.1.2 X Payload

1.1.3 X Airframe

1.1.4 X Reentry System

1.1.5 X Post Boost System

1.1.6 X Guidance and Control

1.1.6.1 X Guidance Section

1.1.6.1.1 X RF Active Seeker

1.1.6.1.2 X IF Receiver

1.1.6.1.3 X Digital Signal Processor

1.1.6.1.4 X Integration, Assembly, Test and Checkout

1.1.6.2 X Control Section

1.1.6.2.1 X Tail Fin Control Section

1.1.6.2.2 X Canards

1.1.6.2.3 X Integration, Assembly, Test and Checkout

1.1.7 X Ordnance Initiation Set

1.1.8 X Airborne Test Equipment

1.1.9 X Airborne Training Equipment

1.1.10 X Auxiliary Equipment

1.1.11 X Integration, Assembly, Test and Checkout

1.2 X Command and Launch

1.2.1 X Surveillance, Identification and Tracking Sensors

1.2.2 X Launch and Guidance Control

1.2.3 X Communications

1.2.4 X Command and Launch Applications Software

1.2.5 X Command and Launch System Software

1.2.6 X Launcher Equipment

1.2.7 X Auxiliary Equipment

1.2.8 X Booster Adapter

1.3 X System Engineering/Program Management

1.4 X System Test and Evaluation

1.4.1 X Development Test and Evaluation

1.4.2 X Operational Test and Evaluation

1.4.3 X Mock-ups / System Integration Labs (SILs)

1.4.4 X Test and Evaluation Support

1.4.5 X Test Facilities

1.5 X Training

1.5.1 X Equipment

1.5.2 X Services

1.5.3 X Facilities

1.6 X Data

1.6.1 X Technical Publications

1.6.2 X Engineering Data

1.6.3 X Management Data

1.6.4 X Support Data

1.6.5 X Data Depository

1.7 X Peculiar Support Equipment

1.7.1 X Test and Measurement Equipment

1.7.2 X Support and Handling Equipment

1.8 X Common Support Equipment

1.8.1 X Test and Measurement Equipment

1.8.2 X Support and Handling Equipment

1.9 X Operational/Site Activation

1.9.1 X System Assembly, Installation and Checkout on Site

1.9.2 X Contractor Technical Support

1.9.3 X Site Construction

1.9.4 X Site/Ship/Vehicle Conversion

1.10 X Industrial Facilities

1.10.1 X Construction/Conversion/Expansion

1.10.2 X Equipment Acquisition or Modernization

1.10.3 X Maintenance (Industrial Facilities)

1.11 X Initial Spares and Repair Parts

CWBS ELEMENT NAMECWBS ELEMENT

LEVEL

Contract Work Breakdown

Structure Index

Figure 2. CWBS Dictionary Example

Program: Vector Surface to Air Interceptor RFP NO: XXXXX Contract Plan No: A-10-X-C1

Contract No: DAAE07-XX-E-0001

DATE: 6/14/2010

CWBS CODE

1.0 Vector Surface to Air Interceptor Missile System

1.1 Air Vehicle

1.1.1 Propulsion (Stages I...n,]

1.1.2 Payload

1.1.3 Airframe

1.1.4 Reentry System

1.1.5 Post Boost System

1.1.6 Guidance and Control

1.1.6.1 Guidance Section

1.1.6.1.1 RF Active Seeker

1.1.6.1.2 IF Receiver

1.1.6.1.3 Digital Signal Processor

1.1.6.1.4 Integration, Assembly, Test and Checkout

1.1.6.2 Control Section

1.1.6.2.1 Tail Fin Control Section

1.1.6.2.2 Canards

1.1.6.2.3 Integration, Assembly, Test and Checkout

This WBS element includes the cost of the Mk51 control surface tail f in control set.

This WBS element includes the cost of procurement, fabrication, assembly and test of the canard devices utilized to provide directional control to the missile in f light.

This WBS element includes the cost of all direct and indirect labor costs associated w ith integrating, assembling, testing and perform checkout procedures on the Control Section subassemblies in order to build up the complete Vector missile control section.

This element includes the cost of the Vector Missile Guidance Section. Cost for this element represent touch labor costs for the inspection, quality assurance, testing, recurring engineering design, and f inal assembly of all subassemblies into the completed Guidance set. Costs for purchased parts of children WBS elements are rolled up into and reported for this WBS element. There are no direct reporting CSDR requirements from any supplier or vendor for any component w ithin this WBS element.

This WBS element includes the cost of the Radio Frequency (RF) missile seeker that provides an all w eather capability. The RF active seeker is designed and manufactured at the prime contractors integration facility in

Dallas, TX. The cost for this element includes the material cost for the subassemblies and direct and indirect labor associated w ith the IAT&C fo the subassemblies into the RF Active Seeker end-item.

This WBS element includes the cost of all the electronic circuitry and RF w aveguide.

This WBS element includes the cost of the tw o Texas Instruments TMS320C6414T/15T/16T DSPs that provide the signal processing capabilities for discrimination of the target from clutter and jammer returns in the received signal.

This WBS element includes the cost of all direct and indirect labor costs associated w ith integrating, assembling, testing and perform checkout procedures on the Guidance Section subassemblies in order to build up the complete Vector missile Guidance section.

This WBS element includes the cost of the Vector missile control section. The tail f in controls are equipment designed and manufactured in-house by the prime. Cost for the tail f in controls include engineering, tooling, quality control and manufacturing direct and indirect costs. The canard is a purchased item and its cost reflects the primes costs for direct and indirect labor for IAT&C of the canards into the control section of the missile.

This WBS element includes the cost of the Vector missile's rocket motor and labor required to integrate and assemble the propulsion system into the AUR. The single Thiokol TX-486-1 solid-fueled rocket motor is a subcontracted item but the cost falls under the threshold for "direct reporting" by the supplier. This WBS element captures the cost of the purchased solid rocket motor and IAT&C costs necessary to install, test and checkout the rocket motor inside the airframe. There is one TX-486-1 rocket motor per AUR.

This WBS element includes the cost of the Mk125 w arhead and labor required to integrate and assemble the w arhead into the AUR. The Vector payload consists of the Mk 125 Warhead and its support assemblies.

This element is a subcontracted item by the prime contractor. The dollar amount for this item is exceeds the dollar threshold for CSDR reporting and consequently the prime contractor has f low ed dow n CSDR reporting requirements to the supplier and provided the subcontractor w ith their CA-approved CSDR Subcontract plan.

Prime contractor recurring and non-recurring costs w ill capture the price paid for the Mk125 w arhead in addition to the prime's direct and indirect costs for integration, assembly, test and checkout of the Mk125 w arhead into the payload section of the missle. There is one Mk125 w arhead per AUR.

This element refers to labor and material costs associated w ith the components that comprise the airframe.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost for the 1.1.6.1 Guidance Section and 1.1.6.2 Control Section. This parent element includes the cost of labor and material for the prime contractor and any subassembly manfactured and procured by outside vendors.

Contract Work Breakdown

Structure Index

CWBS ELEMENT NAME CWBS DEFINITION

This WBS element includes the cost of the Vector missile All Up Round (AUR) in addition to the cost of the common WBS elements. The Vector missile is an Army Surface-to-Air interceptor missile providing 360 degree coverage for the air defense mission of forw ard deployed forces. It is a Single-stage, short-range, low -to high-altitude theater missile defense system that utilizes advanced guidance and control technologies including an advanced active RF seeker to extend the range of engagement beyond current and projected threats. This WBS element reports the total development or production cost, w hichever is applicable to the instant contract, of the All Up Round (AUR) through the cost for the common WBS elements. WBS elements

1.1 Air Vehicle and 1.2 Command and Launch are the tw o child WBS elements that capture the cost of the product, w hile WBS elements 1.3 through 1.1.1 capture the cost of the "common elements".

This element refers to the means for delivering the destructive effect to the target, including the capability to generate or receive intelligence to navigate and penetrate to the target area and to detonate the w arhead. This element includes the design, development, and production of complete units (prototype and operationally configured units, w hich satisfy the requirement of their applicable specif ications) regardless of their use. This

WBS element has eleven children WBS elements. The government CWIPT has required, through the use of a

CA-approved Plan for the Vector Missile, that WBS element 1.1.6 Guidance and Control w ill contain tw o child

WBS elements, each one containing a low er levels of WBS indenture in order to capture the cost of the specif ic cost driving elements w ithin the G&C element.

Figure 2. CWBS Dictionary Example (Continued)

Program: Vector Surface to Air Interceptor RFP NO: XXXXX Contract Plan No: A-10-X-C1

Contract No: DAAE07-XX-E-0001

DATE: 6/14/2010

CWBS CODE

1.1.7 Ordnance Initiation Set

1.1.8 Airborne Test Equipment

1.1.9 Airborne Training Equipment

1.1.10 Auxiliary Equipment

1.1.11 Integration, Assembly, Test and Checkout

1.2 Command and Launch

1.2.1 Surveillance, Identification and Tracking Sensors

1.2.2 Launch and Guidance Control

1.2.3 Communications

1.2.4 Command and Launch Applications Software

1.2.5 Command and Launch System Software

1.2.6 Launcher Equipment

1.2.7 Auxiliary Equipment

1.2.8 Booster Adapter

1.3 System Engineering/Program Management

1.4 System Test and Evaluation

1.4.1 Development Test and Evaluation

1.4.2 Operational Test and Evaluation

1.4.3 Mock-ups / System Integration Labs (SILs)

1.4.4 Test and Evaluation Support

1.4.5 Test Facilities

1.5 Training

1.5.1 Equipment

1.5.2 Services

1.5.3 Facilities

Contract Work Breakdown

Structure Index

CWBS ELEMENT NAME CWBS DEFINITION

This WBS element includes the cost of training equipment, services and facilities for the Vector missile contract.

This WBS element includes the cost of Vector Missile operational trainers, maintenance trainers, and other items such as cutaw ays, mock-ups, and models used to support development and operational testing.

This WBS element includes the cost of training services, 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. Also included in the cost of this element are costs for training materials, training courses, and associated documentation (primarily the computer softw are, courses and training.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost of all System Test & Evaluation activities performed by the contractor necessary for the system to achieve its Key Performance Parameters (KPPs) required by the current

Acquisition Decision Memorandum. System Test & Evaluation costs are broken dow n into f ive unique child

WBS elements; each addressing a unique activity or function to be performed by the contractor during the

ST&E portion of the program. The Vector missile program is producing eleven prototype f light units to support the DT&E phase. There is one specially fabricated hardw are/ softw are test stand that w ill be used to instrument, test and validate the rocket motor engineering data.

This WBS element includes the cost of all Development Test and Evaluation activities performed by the prime contractor necessary for the Vector missile system to it's T&E acquisition milestone exit criteria. The prime contractor w ill conduct DT&E testing activities at the prime's integration facility in Dallas, TX to ensure that all engineering designs satisfy Preliminary Design Review (PDR) and Critical Design Review (CDR) requirements, prior to actual operational f light testing.

This WBS element includes the cost of all Operational Test and Evaluation activities performed by the prime contractor necessary for the Vector missile system to it's T&E acquisition milestone exit criteria. The prime contractor w ill conduct OT&E testing activities at the Army's White Sands Missile Range in conjunction w ith

Army Air Defense personnell. Included in this cost element are costs associated w ith test equipment, shelters, vans, testing communication equipment, contractor technical support, logistic testing efforts and develolpment of RAM requirements.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost of Vector Missile spares, repair of reparables, repair parts, w arehousing and distribution of spares and repair parts, test and support equipment, test bed vehicles and contractor technical support.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost of the effort associated w ith the systems engineering and program management activities for the Vector missile contract. The systems engineering and program management effort are combined and reported in total for the Vector missile contract. Specif ic system engineering activities included in this element for this contract are: CAIV analysis, Design-to-Unit-Production-Cost analysis, system cost effectiveness studies, reliability, availability and maintainability studies. Specif ic program management activities included in this element for this contract are: configuration management, ILS management, program management, supply support management, program control, and EVMS and CSDR reporting activities.

This WBS element includes the cost of the additional equipment generally excluded from other specif ic elements. This element includes the environmental control, safety and protective subsystems, and destruct system. It also includes equipment of a single purpose and function that is necessary for accomplishing the assigned mission.

This element includes the cost of Integration, Assembly, Test and Checkout (IAT&CO ) of the hardw are conducted at the contractor’s assembly facility. Subsystem components w ill be assembled and tested and then shipped to the prime contractor's facility for f inal assembly and testing.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This element includes the cost of the ordnance initiation set. The ordnance initiation set initiates all ordnance events throughout the missile and ground system (except reentry system components).

This WBS element includes the cost of the Vector missile AUR airborne test equipment.

This element includes the cost of an exercise w arhead that is interchangeable w ith the live w arhead and suitable for training f iring. This element also includes destruct systems, recovery systems, special instrumentation, and telemetry equipment associated w ith the training mission.

Figure 2. CWBS Dictionary Example (Continued)

END OF DI-MGMT-81334D

Program: Vector Surface to Air Interceptor RFP NO: XXXXX Contract Plan No: A-10-X-C1

Contract No: DAAE07-XX-E-0001

DATE: 6/14/2010

CWBS CODE

1.6 Data

1.6.1 Technical Publications

1.6.2 Engineering Data

1.6.3 Management Data

1.6.4 Support Data

1.6.5 Data Depository

1.7 Peculiar Support Equipment

1.7.1 Test and Measurement Equipment

1.7.2 Support and Handling Equipment

1.8 Common Support Equipment

1.8.1 Test and Measurement Equipment

1.8.2 Support and Handling Equipment

1.9 Operational/Site Activation

1.9.1 System Assembly, Installation and Checkout on Site

1.9.2 Contractor Technical Support

1.9.3 Site Construction

1.9.4 Site/Ship/Vehicle Conversion

1.10 Industrial Facilities

1.10.1 Construction/Conversion/Expansion

1.10.2 Equipment Acquisition or Modernization

1.10.3 Maintenance (Industrial Facilities)

1.11 Initial Spares and Repair Parts

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost of Vector missile system repairable spares (reparables) and repair parts required as initial stockage to support and maintain new ly f ielded systems or subsystems during the initial phase of service, including pipeline and w ar reserve quantities.

Contract Work Breakdown

Structure Index

CWBS ELEMENT NAME CWBS DEFINITION

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost of test and measurement equipment and support and handling equipment that are considered common under the Vector missile contract. Included in this element is the cost of test measurement and diagnostic equipment and signal processor automatic test equipment that are common inventory support equipment items.

This WBS element includes the cost of HHK-248A test and diagnostic equipment used by maintenance personel to perform routine propulsion system test and checkout procedures during schedule maintenance events.

This WBS element includes the cost of common support and handling equipment that is used to store, move and transport Vector AURs in their containers.

This WBS element is not applicable to the Vector Missile contract.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost of all engineering data in paper, Adobe PDF , and CD ROM formats to the government.

This WBS element includes the cost of all management data in paper, Adobe PDF , and CD ROM formats to the government. Included are the costs for EVMS and CSDR reports.

This WBS element includes the cost of all support data in paper, Adobe PDF , and CD ROM formats to the government. Included is the Vector missile program logistic support database containing all Army logistic reporting requirements and performance parameters.

This WBS element includes the cost of all engineering data in paper, Adobe PDF , and CD ROM formats to the government.

This WBS element includes the cost of test and measurement equipment and support and handling equipment that are peculiar to the Vector missile contract. Included in this element is the cost of missile equipment and tools used to service the missile during OT&E activities. Also included is the cost to modify factory test equipment for the RF missile seeker that is used by the prime contractor during testing and subsequently delivered to the government.

This WBS element includes test and measurement equipment, such as the ME-403 seeker test stand used to calibrate the Vector missile RF seeker unit during routine organizational unit maintenance activities.

This WBS element includes the cost of deliverable data to the government associated w ith the development of the Vector missile system. This element rolls up the cost of technical publications, engineering data, management data, support data and any data depository developed to store and disseminate information to the government.

This WBS element includes the cost of all technical publications in paper, Adobe PDF, and CD ROM formats to the government.

Title: OPERATIONS SECURITY (OPSEC) PLAN

Number: DI-MGMT-80934C Approval Date: 20101213 AMSC Number: 9178 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/I925 Applicable forms: N/A

Use/Relationship: The OPSEC Plan is used to identify and monitor a contractor’s OPSEC activities during the performance of a contract. It is intended to be a living document that will require periodic updates throughout the life of the contract. The OPSEC plan; (1) Describes the OPSEC environment to include identification of critical information, the OPSEC threat and vulnerabilities an adversary might exploit to acquire critical information, (2) Documents the OPSEC risk analysis, (3) Identifies proposed and actual OPSEC measures, (4) Defines and assigns specific OPSEC responsibilities and ties the OPSEC Plan to the contractor’s corporate OPSEC Program, and (5) Serves as a repository of the OPSEC history of the contract.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements delineated in the contract.

b. This DID is applicable only when the contracting activity determines that the sensitivity of the contracted effort warrants OPSEC protections.

c. The contractor’s implementation of the OPSEC Plan, approved by the contracting activity, is subject to joint audit and/or inspection by the Defense Security Service and the contracting activity.

d. This DID supersedes DI-MGMT 80934B.

Requirements:

1. Reference documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices and revisions, shall be as specified in the contract.

a. “Applying OPSEC to U.S. Government Acquisitions and Contracts”. This document is available from the Interagency OPSEC Support Staff (IOSS) at the following web address:

www.ioss.gov.

b. Department of Defense Manual (DODM) 5205.02M, DOD Operations Security (OPSEC) Program Manual, dated November 3, 2008.

Downloaded from http://www.everyspec.com http://www.ioss.gov/

DI-MGMT-80934C

c. Department of Defense Contract Security Classification Specification (DD 254). This document is included as a part of all Request for Proposals (RFP) and Contracts involving classified data.

d. Contract Data Requirements List (CDRL). This document is included as a part of all RFP and contracts containing data deliverable requirements.

e. National Industrial Security Program Operating Manual (NISPOM) 5220.22M, dated February 28. 2006.

2. Format: The OPSEC Plans shall be submitted in contractor determined format and, at a minimum, consist of the following sections listed in the Content Section below.

3. Content:

3.1 COVER PAGE

The cover page for an OPSEC Plan shall clearly present, at a minimum, the following information:

1. Title of the Acquisition Program

2. Title of the Document (i.e. “Operations Security Plan”)

3. Reference to the government contract number

4. Date of latest revision

5. Name, signature and title of the preparer of the OPSEC Plan

6. Name, signature and title of the approver of the OPSEC Plan.

7. Reference for whom the document was prepared (Contracting activity)

8. Reference by whom the document was prepared (Corporation)

9. All appropriate distribution or classification statements

3.2 TABLE OF CONTENTS PAGE

The Table of Contents for an OPSEC Plan shall outline each section contained in the OPSEC Plan.

3.3 PREFACE PAGE

The purpose of the Preface is to provide a brief, unclassified, overview of the program and the need for OPSEC measures. The specific objectives of the contracted effort shall be introduced with reference to all strategic participants and partnerships required to make the program a success. The anticipated development of any innovative concepts or technologies shall also be introduced in the Preface.

The Preface shall reference all links between the OPSEC Plan and any corporate OPSEC Program(s). The Preface may conclude by referencing requirement documents such as the contract number, Contract Security Classification Specification (DD254), Contract Data

Requirements List (DD1423) and any other pertinent guidance provided by the contracting activity. It shall also provide an OPSEC point of contact, with contact information, for additional guidance or assistance such as the OPSEC program manager or contractor program manager.

3.4 OPSEC PLAN INTRODUCTION

3.4.1 Purpose and Scope: The purpose of the OPSEC Plan shall be effectively communicated in this section and include a description of the scope of the OPSEC Plan (unique physical locations, subcontractors, suppliers, period of performance, etc.).

3.4.2 Authorities: The requirement to protect critical information shall be documented within this section. Documenting the requirement can be achieved by referencing the Corporate OPSEC Program (Policy) and Plan, DODM 5205.-2M, specific contract documents including the DD254 for contracts involving classified data, or other contracting activity specific guidance.

3.4.3 OPSEC Plan Major Activity Timeline: This section shall include a list of all major OPSEC Plan activities such as quarterly OPSEC Working Group Meetings, Annual Assessments, scheduled OPSEC awareness training, Sub-contractor OPSEC Assessments and Surveys, Threat and Vulnerability Reviews, etc. This section shall also include scheduled OPSEC Plan reviews.

3.4.4 Responsibilities: The OPSEC Plan shall identify whom is responsible for the major activities described in the Plan. For example (not intended as an inclusive list):

The OPSEC Manager shall be identified by name and include a list of duties that may include:

1. Coordinate all OPSEC policy responsibilities/ procedures within the program.

2. Revise the Program OPSEC Plan as necessary.

3. Convene and coordinate the annual Program OPSEC Assessment.

4. Disseminate updated threat information to program personnel.

5. Assist in the review of contract requirements for OPSEC considerations.

6. Conduct OPSEC briefing(s) upon customer approval of the plan.

7. Principal advisor to the Contractor Program Manager on all OPSEC matters.

8. Develop/Disseminate Program Critical Information List (CIL).

9. Promote OPSEC awareness within the program.

The Contractor Program Manager shall be identified by name and include a list of duties that may include:

1. Responsible for the overall implementation of the program/contract.

2. Ensure proper OPSEC procedures are implemented by program personnel.

3. Ensure all subcontractors and suppliers supporting the program develop and implement procedures in compliance with the Program OPSEC Plan.

4. Remain cognizant of emerging OPSEC threats and vulnerabilities that may adversely impact upon the success of the program.

5. Actively participate in periodic Program OPSEC assessments.

6. Remain cognizant of any changes in critical information and communicate them to the Program OPSEC Manager.

7. Promote OPSEC awareness within the program.

A short description of the expectations and responsibilities of all program personnel (including subcontractors and suppliers) shall be provided and may typically include:

1. Remain compliant with all applicable OPSEC Plans.

2. Maintain an awareness of all applicable CIL.

3. Attend all OPSEC program briefings.

4. Timely reporting of any OPSEC concerns to the Contractor Program Manager and/or the Program OPSEC Manager.

5. Generation of OPSEC Plans (sub-contractors or suppliers only).

3.4.5 Organizational OPSEC Communications and Interfaces: A description as to how the OPSEC Plan will be communicated to all personnel supporting the program (hardcopy, via a webpage, briefings, etc.).

3.4.5.1 Internal: In this section the OPSEC Plan shall identify all anticipated OPSEC interfaces internal to the corporation such as the senior corporate leadership, corporate OPSEC Working Group, OPSEC coordinators, program personnel, etc.

3.4.5.2 External: In this section the OPSEC Plan shall identify all anticipated external points of contact such as the contracting activity, Defense Contract Management Agency (DCMA), The Defense Security Service (DSS), Federal Bureau of Investigation (FBI) and local law enforcement and their primary role within the OPSEC program (i.e. DCMA audits acquisition management practices, DSS provides security oversight, FBI and law enforcement may provide threat data). Subcontractor and supplier OPSEC points of contact shall be similarly identified.

3.4.6 Marking, Handling and Distribution of Documents: This section shall provide a description of marking, handling, storage, access and transmission authorizations and procedures for any critical information provided to, or generated by, the contractor.

Reference to the program classification guide, Freedom of Information Act and any additional guidance provided by the contracting activity may be cited as applicable.

3.5 THREAT

3.5.1 General Threat: This section shall identify and demonstrate an understanding of the overall threat to program critical information throughout the anticipated duration of the contract/program. For example, an information systems program might note the following:

DSS analysis of 2008 threat data shows, “Information systems, especially C4ISR related systems remained the primary sought-after technology for East Asia and Pacific Region countries. Direct requests (often via the Internet) and other suspicious Internet activity continued to be the preferred method of collection. Information systems are primary targets for Near East adversaries of the United States. Near East commercial entity activity indicates a growing collusion between commercial entities and government associated entities such as universities, public agencies and research and development centers. Adversaries using HUMINT and OSINT collection methods represent a significant threat to program critical information. i

The section shall conclude with a brief description of all identified intelligence collection methods that may be expected to be used by an adversary to acquire critical information.

Note: A general description of intelligence collection methods may be found in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov.

3.5.2 Program Detailed Threat: This section shall be similar to section 3.5.1 above referencing any known direct threats to acquisition specific elements of critical information within the program/contract. As complete a description of each threat as possible shall be provided while maintaining the overall plan classification at the unclassified level. Since detailed threat information may derive from classified sources, reference to source documents as provided by the government contracting activity or other reputable source is permitted.

3.5.3 Threat Analysis: Each threat identified in sections 3.5.1 and 3.5.2 shall be analyzed to determine the level of threat to the corresponding critical information. The results of this analysis shall be presented in this section. A description of the specific threat analysis method used by the contractor to quantify each threat shall be included in this section.

Note: For additional guidance and a sample threat analysis methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.02.

3.5.4 Changes Within Threat Environment: The Threat section shall conclude with a statement that addresses how new threat data is to be received and incorporated into the OPSEC Plan to ensure OPSEC risk remains in compliance with all applicable guidance.

3.6 CRITICAL INFORMATION

3.6.1 General: Critical information shall be identified within this section of the plan and a comprehensive program Critical Information List (CIL) shall be included.

3.6.2 Critical Information List: Guidance on the creation of a CIL is contained within “Applying OPSEC to Government Acquisitions and Contracts,” available at www.ioss.gov, DODM 5205.02M, or may be provided by the contracting activity. Ideally the CIL shall remain unclassified to facilitate wide internal distribution, but may provide reference to classified information as applicable.

3.7 VULNERABILITY

3.7.1 General: The Vulnerability section of the OPSEC Plan shall describe the analysis of activities (indicators) that point to OPSEC vulnerabilities an adversary can exploit to acquire critical information. This section shall contain a list of all identified OPSEC vulnerabilities.

3.7.2 List of OPSEC Vulnerabilities: Each vulnerability shall be described in sufficient detail as to communicate to the contracting activity the extent of the vulnerability. The Vulnerability List shall remain unclassified, but may provide reference to classified information if applicable. Reference to classified reports and other information shall include an unclassified description of the documentation (report title, number, etc.) and the source responsible for publication of the information.

Note: A list of typical OPSEC vulnerabilities which may require OPSEC measures may be found within “Applying OPSEC to Government Acquisitions and Contracts”, available at www.ioss.gov or may be provided by the contracting activity. These sample vulnerabilities are not all inclusive and the submitted vulnerability list shall be tailored to the specific acquisition or contract.

3.7.3 Vulnerability Analysis: Once potential program vulnerabilities have been identified, the magnitude of each vulnerability shall be determined using a consistent methodology identified and documented in this section of the OPSEC Plan. The results of this analysis shall also be described in this section.

Note: For additional guidance and a sample vulnerability methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.0-2M.

3.8 RISK ASSESSMENT

3.8.1 General: The OPSEC risk of a program represents the probability of compromise of critical information and the impact to the program/contract taking into account the threat and vulnerabilities. The acceptable level of OPSEC risk (as determined by senior leadership, or the contracting activity) shall be described in this section in terms consistent with the selected OPSEC methodology.

3.8.2 Risk Assessment: The specific OPSEC risk shall be described in terms consistent with the OPSEC methodology selected for determining OPSEC threat and vulnerability.

The method, and the results of the assessment, shall be presented in this section. The conclusion of the risk assessment shall result in an ordinal ranking of OPSEC risk (highest to lowest).

Note: Additional guidance and a sample risk methodology are available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.0-2M.

3.9 OPSEC MEASURES

3.9.1 General: This section of the OPSEC Plan shall identify specific OPSEC

Downloaded from http://www.everyspec.com http://www.ioss.gov/

Measures proposed for mitigating OPSEC risk to acceptable levels including the cost to implement each measure. A sampling of common OPSEC measures is available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov . This list is not to be considered exhaustive and is provided as guidance for the development of the program/contract specific list of potential OPSEC measures.

3.9.2 Residual Risk: This section shall contain an analysis of residual OPSEC risk, in terms consistent with the OPSEC methodology selected, as a result of implementation of each OPSEC measure presented in section 3.9.1. This section shall identify which OPSEC measures will be implemented and the rationale for those that will not.

3.10 OPSEC Program Chronology: This section shall document significant program OSPEC events throughout the lifecycle of the program. Significant events may include changes to the CIL, changes in program leadership or results of program assessments and surveys (including…