DI-MGMT-XXXXX (Technical Data DID) April 13, 2017

Transcription

1 DRAFT DATA ITEM DESCRIPTION DRAFT Title: Technical Data Report (DRAFT) Number: DI-MGMT-XXXXX Approval Date: DRAFT AMSC Number: XXXX Limitation: DTIC Applicable: No GIDEP Applicable: No Preparing Activity: CAPE Project Number: FNCL Introduction: The Technical Data Report is the Department of Defense (DoD) system for collecting technical parameter data as part of the Cost, Software, and Technical Data Reporting (CSTDR) requirement. The resulting data repository serves as the primary source for contract cost, software, and technical data for many DoD resource analysis efforts; including cost database development, applied cost estimating, cost research, program reviews, Analysis of Alternatives (AoA), and life cycle cost estimates. The Technical Data Report provides context to cost data to derive cost estimating relationships. The Technical Data Report may be used in response to government solicitations according to Defense Federal Acquisition Regulations Supplement (DFARS) sections , , , , and Office of the Secretary of Defense Cost Assessment and Program Evaluation (OSD CAPE) and Acquisition, Technology, and Logistics Performance Assessments and Root Cause Analyses (AT&L PARCA) have jointly defined the CSTDR/EVM Co-Plan template and process, for use on contracts that meet both the CSTDR and Earned Value Management (EVM) reporting thresholds. The Co-Plan will leverage the consistent Cost and Hour Report (FlexFile) and Integrated Program Management Report (IPMR) reporting structures against the MIL-STD-881C appendices. All reporting under this DID shall be in accordance with the Cost & Software Data Reporting (CSDR)/Earned Value Management (EVM) Co-Plan (Form 2794); hereafter referenced as the Co-Plan Use/Relationship: For background and detailed requirements related to Cost, Software, and Technical Data Reporting (CSTDR), refer to DoD M-1 (or latest version), Cost and Software Data Reporting (CSDR) Manual The Technical Data Report Data Item Description (DID) is structured around the four data groups below, that contain the content and relationships required for the electronic submission: Technical Data Format Data Group Report Metadata Government Furnished Information (Co-Plan) Technical Data Parameters Technical Data WBS Mapping ID A B C D A. Data Group A Report Metadata: Provides metadata on the contract that allows the submitted data to be associated with other Data Groups and program data. Page 1

2 B. Data Group B Government Furnished Information (Co-Plan): Documents WBS reporting elements and any additional data tags as reported by the CSTDR/EVM Co-Plan. C. Data Group C Technical Data Parameters: Used to collect information related to each required item type, the technical parameter value, unit of measure, estimate/actual, margin, and comments. D. Data Group D Technical Data WBS Mapping: Used to map the technical parameter values to the WBS element and end-order codes, as required by the Co-Plan The Technical Data DID is structured around a format that contains the content and relationships required for the electronic submissions. This Data Item Description (DID) summarizes the Technical Data Report and provides instructions to complement the data requirements specified in the contract for CSTDR reporting. The primary purpose of the data is as follows: Technical Data Report data will be used by DoD Component staff, including program managers, systems engineers, cost estimators, logisticians and financial management personnel to: (1) review and evaluate the program technical baseline; (2) describe the technical parameters required to develop a program life cycle cost estimate; and (3) collect technical and programmatic information in support of system trade off analysis and cost analysis activities. It is important that the data be as accurate as possible so that they may be used for their intended purposes This DID summarizes the forms and provides instructions to support the data and frequency requirements specified in the contract for CSTDR technical reporting. The Technical Data Report is related to other program acquisition requirements, including the FlexFile (DI- FNCL-TBD), Quantity Data Report (DI-MGMT-TBD) and SRDR Development/Maintenance (DI-MGMT-82035) Reporting is required throughout the complete life cycle to include the Operating and Support (O&S) phase of the program. Contract reporting is required throughout the life of the contract. Software sustainment activities are captured using the separate SRDR, Software Maintenance and Data Dictionary DID (DI-MGMT-82035) Requirements: 3.1. Reference Documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, will be as cited in ASSIST at the time of the solicitation; or, for non-assist documents, as stated herein References DoD Instruction , Operation of the Defense Acquisition System, (current version). This instruction contains mandatory CSTDR requirements DoDI , Cost Analysis Guidance and Procedures, (current version) DoD M-1, Cost and Software Data Reporting (CSDR) Manual, (current version) Operating and Support Cost-Estimating Guide MIL-STD-881C, Work Breakdown Structure for Defense Materiel Items, (current version). Page 2

3 DD Form 2794, Cost, Software, Technical Data Reporting Plan, (current version), available at Commonly referred to as the CSTDR Plan, a completed DD Form 2794 must be approved by the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA) Technical Data Exchange Instructions (DEI), currently being documented Technical Data File Format Specifications (FFS), currently being documented Format. Provide Data Groups A through D using the electronic preparation instructions below. Data must be reported for each Work Breakdown Structure (WBS) Element for which an X is marked in Block 13c. iii from the approved contract or subcontract CSDR/EVM Co-Plan. Omit the other WBS Elements The Data Groups A through D of the Technical Data Report, must be submitted electronically in accordance with a CAPE-approved Technical Data DEI/FFS. The specific definition of the Technical Data DEI/FFS are provided under separate covers, (Reference and above). Electronic submittals shall be delivered to the OSD CAPE Defense Cost Resource Center s (DCARC s) secure web-site using the Cost Assessment Data Enterprise (CADE) CSDR Submit-Review (CSDR-SR) system Uploading data to the DCARC requires use of either a DoD Common Access Card (CAC) or a DoD-approved External Certification Authority (ECA) certificate. See for portal registration instructions Implementation. Contractors are responsible for implementing requirements on all subcontracts that meet the reporting thresholds (see DoD Instruction , Table 7.) 4.0. Preparation Instructions: 4.1. General Instructions. All reporting under this Technical Data DID will be in accordance with the CSTDR/EVM Contract or Sub-contract Co-Plan (Form 2794) process Mark the security classification of each report as Unclassified in the space provided on the upper left and lower right of the Form. However, if the report is classified, contact the DCARC for special processing instructions. Please note: Proprietary is not an official DoD security classification, and documents should not be marked as such. If the use of a proprietary disclosure statement is required, it should be inserted in the document s footer The 1921-T reporting frequency is referenced in Block 25 (Submission Events) of the approved contract or subcontract Co-Plan. When a corresponding FlexFile, Quantity, or Software Report is required, the Technical Data Report should align by the as of date, as referenced in the approved plan Contractors must report all technical data associated with the contract, including Advance Procurement, Long Lead Materials, Multiyear Procurement, Inter-Division or Inter-Company Work Orders (IWOs), Foreign Military Sales (FMS), Warranty, etc. Technical data should not be omitted based on contract Contract Line Item Number (CLIN) structure or definition. If IWO costs exceed $50M, separate reporting will be required for technical data Specific Instructions: 5.1. Data Group A - Metadata: Page 3

4 The following data elements must be reported: Program Name: Enter the name given to the program as identified on Page 1 (Summary), Item 1a (Program Name) from the approved contract or subcontract Co- Plan Phase/Milestone: Enter one of the following for the appropriate Phase/Milestone which is being reported: 1. Pre-A (Material Solution Analysis Phase), 2. A (Technology Maturation and Risk Reduction Phase), 3. B (Engineering and Manufacturing Development Phase), 4. C-LRIP (Low-Rate Initial Production), 5. C-FRP (Full-Rate Production), or 6. O&S (Operations and Support Phase) Prime Mission Product: Enter the most current official military designation for the end item as specified by the appropriate classification standard (e.g., DoD L, Military Designation of Military Aerospace Vehicles, would specify F-35 for the Joint Strike Fighter). For contract (or subcontract) Co-Plans, the end item being reported may have a different designation than the total program (e.g., the preparer would enter AN/APG-81 Radar for the F-35 Radar contract Co-Plan). If the end item does not have a military designation, enter the type of product being developed or procured, for example, radar Reporting Organization Type: Enter one of the following for the appropriate organization type: 1. Prime/Associate Contractor, 2. Direct-Reporting Subcontractor, or 3. Government Performing Organization: Enter the following information for the organization actually performing the work: Organization Name: Enter the name of the organization Division Name: Enter the name of the division of the organization performing the work, if applicable Cage Code: Enter the five-character ID number assigned to the organization performing the work, if applicable. If there are multiple Cage Codes, report all separated by commas Address: Enter the location of the organization, or the division of the organization, if applicable. Include the following information: Street Address City State Zip Code Page 4

5 Approved Plan Number: Enter the Approved Plan Number of the current approved contract or subcontract Co-Plan that authorized the collection of data for this report Customer (Direct-Reporting Subcontractor Use Only): Enter the name of the prime contractor for whom the work on the subcontract is being performed. Otherwise enter NA (for not applicable ) Contract Price: Enter the total contract price applicable to the data reported: If the data are in response to a solicitation in accordance with DFARS sections , , and , enter the total estimated price. If the data being reported is for a lot, delivery order, or task, enter the price for the work being reported, not the total contract price Contract Number: Enter the assigned prime contract number the prime contractor has with the Government customer. This requirement is identical for both reporting contractors and reporting subcontractors Solicitation Number: 1. If the data are in response to a solicitation in accordance with DFARS sections , , and , enter the solicitation number. 2. Otherwise enter NA (for not applicable ) Period of Performance: Enter the dates for the data being reported (contract, lot, delivery order, or task). Enter the appropriate numeric data for the year, month, and day. For example, July 31, 2004, would be shown as Start Date: The actual start date End Date: The actual end date Report Type: Enter one of the following: 1. Initial, 2. Interim, or 3. Final Submission Event: Enter the following information for the report submission: Number: Enter the submission number for the report provided Name: Enter the submission event for the report provided. This must match Item 30c of the current approved contract or subcontract Co-Plan Type: Enter one of the following: 1. Initial, 2. Change Report As Of: Enter the appropriate numeric data for the year, month, and last day of the reporting period. For example, July 31, 2004, would be shown as : For event driven submissions, the Report As Of date should be consistent with the event in Item 30c of the approved contract or subcontract Co-Plan. If an event date changes due to a programmatic schedule slip, adjustment to the Page 5

6 As of Date reported in Item 30d of the Co-Plan must be requested through the CSDR Submit-Review system for DCARC approval by the Government Program Office prior to the date reflected in the Co-Plan. A date change request does not require an official Co-Plan revision Point of Contact: Information for the person to contact for answers to any questions about entries on the submission: Name (Last Name, First Name, and Middle Initial) Department Telephone Number (including Area Code) Address Date Prepared: Enter the appropriate numeric data for the year, month, and day of the date the report was prepared in the appropriate numeric format. For example, July 31, 2004, would be shown as Order Name: The Order Name as identified in the Co-Plan which results from the contract negotiations of new scope Data Group B Government Furnished Information (Co-Plan): Work Breakdown Structure (WBS) Element Code: The WBS element code reflective of the Co-Plan WBS element code for each reporting WBS element. The WBS Element Code shall be the same as Block 11b of the Co-Plan WBS Element Level: The WBS level consistent with the WBS Element Code for each reporting WBS Element. The WBS Element Level shall be the same as Block 11c of the Co-Plan WBS Element Name: The WBS element name reflective of the Co-Plan WBS element name for each reporting WBS element. The WBS Element Name shall be the same as Block 12 of the Co-Plan. There will be no space indentations before the WBS Element Name representing indenture of the WBS Element Level Order Name: The Order Name as identified in the Co-Plan which results from contract negotiations of new scope. When appropriate, the Order Name will have sequence or fiscal year buy information associated with it. The Order Name shall be the same as Block 17b of the Co-Plan. The tag that identifies technical data with each Order Name will be the same as the End-Order Code, defined in of Data Group B below. The End-Order Code will discretely map to one Order Name. Examples include Technology Development (TD), Engineering and Manufacturing Design (EMD), Low Rate Initial Production (LRIP) #3, Full Rate Production (FRP) #5, and Operations and Support (O&S) FY17. Examples of Order Names on the same contract Co-Plan include Lot 1, Lot 2, Lot 3, etc., or, Construction Preparation, Detailed Design & Construction, etc. Page 6

7 End Item: Uniquely identify a Platform, Model, Version, Flight, Variant, Kits or equivalent grouping or variant of a reported unit or system. The End Items shall be the same as Block 18 of the Co-Plan. There will always be at least one End Item on a technical data submission, which may be the same as the Program Name reported in Block 1a of the Co-Plan. Instead of placing each variant into the WBS, the common WBS provided in Co-Plan Blocks 11 and 12 will be reported against with an additional tag that identifies End Item. The tag that identifies technical data with each End Item will be the same as the End-Order Code, defined in of Data Group B below. The End-Order Code will discretely map to one End Item. For example, a family of vehicles may have unique End Items for each variant bought, such as Cargo, Van, Tractor, Wrecker, Dump Truck, and Load Handling. Common material or software costs that span across End Items, if applicable, may also be given their own unique End Item End-Order Code: The End-Order Code is a unique string of five characters provided in Block 19b of the Co-Plan. The End-Order Code identifies the how technical data are segregated across Order Name(s) (Block 17b of the Co-Plan), and further, how technical data within an Order Name are segregated across End Items (Block 18 of the Co-Plan). Technical data will be reported to each and every End-Order Code, representing the unique combination of each and every Order Name along with each and every End Item, as determined in the Co-Plan. The End-Order Code is the tag that relates the technical parameter data to the model/variant with associated cost/hour and quantity information reported through the FlexFile (DI-FNCL-TBD) and Quantity Data (DI-MGMT-TBD), respectively. For example, if there are three Order Names (e.g., Lot 1, Lot 2, and Lot 3 ) and two End Items (e.g., Variant A and Variant B ), then technical data will be reported against six Sub-Order Codes (e.g., A1001, B1002, A1002, etc., representing Lot 1 Variant A, Lot 1 Variant B, Lot 2 Variant A, etc.). If the reporting entity begins charging to new scope before the Co-Plan is amended with updates to Order Name and/or End Item, or the reporting entity would like to logically separate a new Order Name or End Item that is not provided by the Co- Plan, the contractor may create a new End-Order Code so long as the relevant Order Name and End Item names are also identified with the intention of updating the Co-Plan Blocks 17, 18, and 19 to reflect the new tags Data Group C Technical Data Parameters Refer to Page 4 (Technical Parameter Requirements) of the approved contract or subcontract Co-Plan for the required WBS Element Codes and Names; Technical Parameter Item Type, Name, Unit of Measure, Unit of Measure Qualifier, Repeatable instructions; and any CWIPT required remarks. Definitions for each parameter are provided on the CADE website, The following data elements must be reported: Page 7

8 Mapping ID: By hardware item, a unique identifier by Item Type for each individual group of parameters. Created by the reporting contractor, the Mapping ID is any unique alpha-numeric code that is used to differentiate between individual parts. This is used to match the technical parameters to the End Item ID and corresponding WBS element code in the Technical Data WBS Mapping ID table, Data Group D (Mapping ID) of the Technical Data Report. If there is only one identified End-Order Code, the reporting contractor may use the WBS element code as the Mapping ID Item Type: The Item Type for each required WBS element, referencing Page 4, Item 23 (Item Type) from the approved contract or subcontract Co-Plan. The Item Type is required for management of the Technical Parameter database and will always be defined for the reporting contractor as part of the Co-Plan Technical Parameter Name: The Technical Parameter Name as presented in Page 4, Item 24a (Parameter Name) from the approved contract or subcontract Co-Plan Group Key: The Group Key indicator is used to keep like-rows together. This is necessary when a WBS element has repeated subsets of the same parameters. Reference Page 4, Item 24d (Repeatable) from the approved contract or subcontract Co-Plan for specific instructions required for the repeating of parameters associated with the WBS Element and Item Type. For example, if an electronic box has multiple cards that perform different functions, the technical parameters will need to be repeated for each unique card. The Group Key is used to ensure these parameters are grouped together in the CADE database. Any unique alpha-numeric content will meet the IT-need to keep records grouped, but even-so, reasonable meaningful keys are recommended. These keys exist solely in the context of a single submission Value: A single value, excluding margin, for the associated Technical Parameter and hardware item identified by the Mapping ID. The value can be considered Estimated or Actual. The Type (numeric, text, multiple choice from list, etc.) of entry and the Unit of Measure (watts, percent, kilos, etc.) are defined by the parameter being requested. Parameters and their associated definition, allowable value, Unit of Measure, etc. will be specified in the approved Co-Plan language or by other means. (Note: Each parameter definition has instructions for the Item Type entry and the additional data type information elements specified below) Unit of Measure: The Unit of Measure as presented in Page 4, Item 24b (Unit of Measure) from the approved contract or subcontract Co-Plan. Requirements and guidance for the Unit of Measure entry are specific to each Parameter (or grouping of Parameters) and are provided with each Parameter definition Unit of Measure Qualifier: The Unit of Measure Qualifier name as presented in Page 4, Item 24c (Unit of Measure Qualifier) from the approved contract or subcontract Co-Plan. Requirements and guidance for the Unit of Measure Qualifier entry are specific to each Parameter (or grouping of Parameters) and are provided with each Parameter definition. For example, if the area of a Solar Array is required, the Unit of Measure might be square feet. The Unit of Measure Qualifier might be Per Panel if multiple array panels are specified or could be Total if the square footage Page 8

9 is specified for the entire set of panel or entire array(s) Estimate/Actual: For each parameter value, enter Estimate or Actual, for the most representative valuation of the pedigree or derivation of the technical parameter values reported: Estimate the threshold, spec value for any given parameter. Enter Estimate if the parameter value applies to the following definitions: o o o Specified - It is likely that the reported value will deviate somewhat from the current prediction. A specified value might represent a mostlikely estimate derived or taken from a specification expressed as a single value (Objective), or from an expressed pair (Objective and Threshold). It can also be an approximation based on historical experience, Subject Matter Expert (SME) experience, rough sketches, or conceptual analysis. Predicted - There is a realistic likelihood that the reported value specified will remain unchanged from the current prediction. Expected value from a design (e.g. pre-release or released drawings) expressed as a single value (e.g. Most Likely, or a Point Estimate with no statement of likelihood). Spec- There is a good likelihood that the reported value will not deviate or only slightly vary from the current valuation. Expected value may come from (or be extrapolated from) an actual measurement of a developmental or production representative unit or from an un-verified specification or catalog. Actual the measured, known value for any given parameter. Enter Actual if the parameter value applies to the following definition: o Known - The reported value will not deviate as it is a final measurement or valuation. Demonstrated (e.g. measured) value from completed production or operating unit, assembly, or other product being used or delivered and reported Margin: The estimated or measured margin for the associated Technical Parameter specified by the Mapping ID. The margin value should be reported for any hardware item with a reported technical parameter which is an Estimated value, and considered for Actual technical parameters which exhibit significant margin in their measured values Comments: Enter any information that would explain any peculiarities or ambiguities in any of the data reported in Data Group C. Reference Page 4, Item 24e (Comments) from the approved contract or subcontract Co-Plan, and enter any required information dictated by the CWIPT. Enter explanations of changes from previous submissions (e.g. error corrections or substantive changes in underlying equipment or products.) Include any basis for, or calculations, used to derive any of the element responses Data Group D - Technical Data WBS Mapping ID: The following data elements must be reported: WBS Element Code: The WBS Element Code for each WBS element being reported. The code must be identical as presented in Block 11b (WBS Element Page 9

10 Code) from the approved contract or subcontract Co-Plan End-Order Code (1-n): The Mapping ID from Data Group C (Technical Data Parameters), enter the Mapping ID for Item Types which uniquely identify the corresponding End-Order Code (Model, Version, Flight, Variant, or equivalent grouping or variant of a reported unit or system). Allowable entries for this element and their scope will be specified in from the approved contract or subcontract Co-Plan. Each item must be reported in a single column, expanded to the right (End-Order Code 1 n). End-Order Code is further defined in END OF DI-MGMT-XXXXX Page 10