Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
COST ASSESSMENT DATA ENTERPRISE
Technical Data Reporting ImplementationMay 2019
Technical Data Overview Technical Data…Cost data has been delivered on DoD contracts for 60 years, SW data has been provided for 10 years. Technical Data has always been a requirement; however, not implemented effectively
Tech Data initiative: › Provides mechanism to systematically
capture Tech Data on contracts› Complements DoD CARD process› Creates a common Tech Data Vocabulary› Defines core set of needed parameters› Leverages other Tech Data on contract
Results:› Tech Data Plan reported via WBS› Common taxonomy for both CARD and
TDR - consistent with GOVT ENGR groups and Industry
Enduring Cost Analysis Need› Provides context to the cost data› Defines the Program’s Technical Baseline› Ingredient of acquisition strategies, e.g., schedules› Identification and quantification of cost drivers› Foundation for Independent Technical Assessments› Supports architecture trade studies› Highlights areas of potential risk
Unfortunately Tech Data is a Knowledge Gap› Technical Data has always been a requirement; however, not
implemented effectively› Data collections have been ad-hoc, inefficient, and random within DoD› Program documents contain lots of narrative and not enough real data› Result: We re-construct Technical analogies for nearly every estimate
2DoD now has Contractual Mechanism and Process to Collect Technical Data
USAF
Technical Data Collection
How Do We Get the Requirement on Contract?
4
Advocacy for Technical Data ReportingTechnical Data Reporting Implementation
Technical data is an enduring cost analysis need
Technical data will add value to the cost data collected for this contract
Estimating subsequent contracts on this program will use this technical data
Estimating future programs using this program as a reference will use this technical data
Obtaining technical data now as a contract deliverable avoids subsequent data calls to the contractor or program office
The Service Cost Center analyst is the voice of advocacy within the CWIPT for placing the Technical Data Report on contract
5
CWIPT Implementation ChecklistTechnical Data Reporting Implementation
Start with Core Parameters by Commodity & Phase
Refine Contract-Specific Parameters using Technical Data Vocabulary Database
Review other Contractual CDRL Requirements to Minimize Duplication
Finalize Technical Data Reporting, DD 2794 Supplement & Submission Events
Revise generic Technical Data CDRL (DD 1423) to Program specifics
Participate in pre / post award conferences to Ensure Tech Data requirements are well understood
CWIPT must always start with Core Parameter templates by Commodity and Phase
6
CWIPT Implementation ChecklistTechnical Data Reporting Implementation
Core Parameters by Commodity & Phase• From Commodity Data Templates, we developed “core” parameters
Absolutely Required to Perform Cost Analysis Typically not Produced by Govt TeamNormally Produced by IndustrySegregated by each CommodityChanges throughout the evolution of a Program
Commodity Standard TemplatesData Universe
Program Template
Acquisition Template
PMP Hardware Template
Non-Hardware Template
Cost Template
Other Templates
Metadata
MIL-STD881DWBS
(April ’18)
Core Parameters CWIPT Process
Access Technical Data Reporting Core Parameter Templates here:
https://cade.osd.mil/policy/techdata
Note: core parameters lists are currently out for comment to Industry
7
CSDR Standard PlansTechnical Data Reporting Implementation
Extending MIL STD 881D (2018)
Not AFCAA
Product ExtensionsRepeatablePredictableModularCollaboration FrameworkTailor-able by PhaseUpdate cycle as needed
AFCAA
MIL STD “…consistent and visible framework …”“…consistent application of the WBS for all programmatic needs (including performance, cost, schedule, risk, budget, and contractual).”“…tailoring may occur …”“An effective WBS … has a logical structure and is tailored to a particular defense materiel item. ”
Update cycle > 5 yearsMIL-STD-881D 2018MIL-STD-881C 2011 MIL-HDBK-881A 2005 MIL-HDBK-881 1998 MIL-STD-881B 1993MIL-STD-881A 1975MIL-STD-881 1968
H Unmanned Maritime
C Missile/Ordnance
B Electronic or Generic
A Aircraft
D Strategic MissileE SeaF SpaceG Ground Vehicle
I Launch Vehicle
J Information/Defense BusinessK Common ElementsL Sustainment
Missile-Ordnance
Electronic Warfare
Aircraft
Strategic MissileShipSpaceGround Vehicle UUVLaunch
C4I ElectronicsC4I Radar
Sustainment
EngineGeneric Subcontractor
OGC Flight Test
Training Systems
Avionics
Not 881
Modifications ImplementationGuidance only
UAV
IS/DBS Ground Segment for Space or UAVs
881D Appendices
Launch ServicesLaunch Service Support
Applicable to Edwards AFB only
Individual Standard Plan WBS Product Extensions:
• Serve as the starting point for weapon system and defense business system program CWIPTs CSDR Contract and Subcontract Planning
• WBS extensions provide the capability to capture high-cost, high-risk, advanced technology components as defined by the CWIPT and refined by industry feedback
• Serve as a starting point for building the Contract/Subcontract plans tied to company’s contract scope of work
• Facilitates effective and early communication of Government expectations for cost/technical/programmatic data collection with industry via CSDR CDRLs
• Starting point for technical data collection and basis of the Technical Data Vocab Core Parameters
8
CWIPT Implementation ChecklistTechnical Data Reporting Implementation
Core Parameters by Commodity & Phase
CWIPT will determine the data recipe for each Program, starting with the Core
PO Office
OSD CAPE
Service Cost
Service EV
DCARCL&MR
PARCA
SYSCOM
CWIPT• Core parameters should represent technical data required by cost analysts for current program and future program estimating Is the parameter typically captured by Industry practices? Is the parameter value available at required submission events?
Is this needed for this Phase?
Will this value be available at the submission
event?
Alignment to Program
WBS?
Reference to Common
Tech Vocabulary
WBS# ITEM TYPE SUBTYPE PARAMETER NAME UNIT OF MEASURE Dev Prod O&S
Final Authoritative Data Source For
ActualsMS A PD
R MS B CDR MS C DEFINITION VocabularyID
1.2.2.4.11 Battery Battery Capacity Ampere Hours X X Contractor X X X X Measure of the charge stored by the battery, and is determined
CADEVocab0131.2.2.4.11 Battery Output Voltage Volts X X Contractor X X X X The output voltage is the voltage released by a device. For
CADEVocab013
1.2.2.4.11 Battery Type of Battery List X X Contractor X X X X Type of technology used to power battery (e.g. Silver Zinc,
CADEVocab0131.2.2.4.11 Battery Number of Battery Cells Quantity X X Contractor X X X X Number of cells per battery CADEVocab0131.2.2.4.11 Battery Heritage New Design List X Contractor X X X X The extent of the item's design that is new on a 0-100% scale
CADEVocab046
1.2.2.4.11 Battery Heritage Predecessor System Year X Contractor X X X X When Percent New Design is less than 100%, cite the systems
CADEVocab0461.2.2.4.11 Battery Heritage Technology Readiness Level (TRL) Percent Government X X X X Technology Readiness Levels (TRL)are a set of nine graded
CADEVocab046
1.2.2.4.11 Battery Heritage Manufacturing Readiness Level Name/Number Government X X X X Manufacturing Readiness Levels are a set of nine graded
CADEVocab0461.2.2.4.11 Battery PhysicalElec Volume Cubic Inches X X Contractor X X X Physical volume of the item. CADEVocab0711.2.2.4.11 Battery PhysicalElec Weight Pounds X X Contractor X X X Physical weight of the item. CADEVocab0711.2.2.4.11 Battery PhysicalElec Weight - Structural Pounds X X Contractor X X X The item's mechanical/structural weight. CADEVocab0711.2.2.4.11 Battery PhysicalElec Weight - Electronics Pounds X X Contractor X X X The item's electronics weight. CADEVocab0711.2.2.4.11 Battery PhysicalOther Certification Full Time Equivalent Contractor X X X X Specify if terminal is military/air worthiness certified CADEVocab0721.2.2.4.11 Battery PhysicalOther Quantity Next Higher Assembly Quantity Contractor X X X Number of units of this item to be assembled into its parent CADEVocab0731.2.2.4.11 Battery PhysicalOther Nuclear Hardened List Contractor X X X The employment of any design or manufacturing technique
CADEVocab073
Core by Phase Anticipated Availability
Is this a typically Contractor
determined value?
9
CWIPT Implementation ChecklistTechnical Data Reporting Implementation
Refine Contract-Specific Parameters using Technical Data Vocabulary Database
TDR
CARD
Engineering Database(s)
Physical Characteristics:- Length, Width, Weight, …
Performance Characteristics:- Speed, Range, …
Physical Characteristics:- Length, Width, Weight, …
Performance Characteristics:- Speed, Range, …
Physical Characteristics:- Length, Width, Weight, …
Performance Characteristics:- Speed, Range, …
API(future)
PPM(future)
PPM”(future)
Functionality for CWIPT to assign tech parameters to WBS’s in Technical Data Report
Functionality to tailor CARD technical parameters by WBS
Functionality to consume data from another party’s database
CADEData Model
CADE Query& Analytics
(future)
Functionality to query the database and perform analytics
TechVocabulary
For additional information, see:Technical Data Vocabulary Database
Tech Data Vocabulary Database• Ensures consistent definition of terms across commodities
• MIL-STDs, Industrial STDs• IEEE, AIAA, other STDs
• Aligns with engineering community databases• Permits user to tailor technical parameters by WBS element• Assists in creation of Tech Data plans • Assists in creation of CARD submissions• Validate and Ingest Tech Data and CARD Submissions into the
CADE repository • Enables future CADE Data and Analytics functionality
Minimize Duplication of DeliveriesTechnical Data Reporting Implementation
Review other Contractual CDRL Requirements to Minimize Duplication
Applicable Data Items› DI-MGMT-81650 IMS› DI-GDRQ-81230 Mass props Status report› DI-GDRQ-81223 Schematic Block Diagram› DI-QCIC-80553A Acceptance test plan› DI-ADMN-81373 Presentation Material PDR Reports› DI-ADMN-81373 Presentation Material CDR Reports
Other Technical Data required› Specifications › System Description document› Technical Description document
Prod
uced
by
Indu
stry
Toda
y
If other CDRLs are identified, ensure that CDRL language reflects delivery to CADE, along withTechnical Data Report
10
Technical Data Reporting SupplementTechnical Data Reporting Implementation
Finalize Technical Data Reporting, DD 2794 Supplement & Submission Event Schedule• CWIPT process will derive contract data plan
Can the requirement be satisfied by GOVT CARD? Can the requirement be satisfied by other Program CDRL? Can the requirement be satisfied by other reputable data sources?
PARAMETER NAMECore Only
UNIT OF MEASURE Data Source Definition REMARKS Delivery
REMARKS1.2.2.4 Electrical Power (EPS) EPSSpace Power - Beginning of Life (BOL) Watts Contractor See Tech Vocab Power CDRL Delivery to CADE1.2.2.4.4 Solar Array Heritage New Design List Contractor See Tech Vocab1.2.2.4.4 Solar Array SolarArray Number of Solar Array Panels Quantity Contractor See Tech Vocab PDR / CDR CDRL Delivery to CADE1.2.2.4.4 Solar Array Heritage Predecessor System Year Contractor See Tech Vocab1.2.2.4.4 Solar Array SolarArray Solar Cell Material Text Contractor See Tech Vocab PDR / CDR CDRL Delivery to CADE1.2.2.4.4 Solar Array PhysicalElec Weight Pounds Contractor See Tech Vocab Mass Props CDRL Delivery to CADE1.2.2.4.5 Solar Array Positioner Heritage New Design List Contractor See Tech Vocab1.2.2.4.5 Solar Array Positioner Gimbal Number of Axes - Moveable Quantity Contractor See Tech Vocab PDR / CDR CDRL Delivery to CADE1.2.2.4.5 Solar Array Positioner Heritage Predecessor System Year Contractor See Tech Vocab1.2.2.4.5 Solar Array Positioner PhysicalElec Weight Pounds Contractor See Tech Vocab Mass Props CDRL Delivery to CADE1.2.2.4.9 Power Conditioning, Conversion a Heritage New Design List Contractor See Tech Vocab1.2.2.4.9 Power Conditioning, Conversion a Heritage Predecessor System Year Contractor See Tech Vocab1.2.2.4.9 Power Conditioning, Conversion a PhysicalElec Weight Pounds Contractor See Tech Vocab Mass Props CDRL Delivery to CADE1.2.2.4.11 Rechargeable Batteries Battery Battery Capacity Ampere Hours Contractor See Tech Vocab1.2.2.4.11 Rechargeable Batteries Heritage New Design List Contractor See Tech Vocab1.2.2.4.11 Rechargeable Batteries Battery Number of Battery Cells Quantity Contractor See Tech Vocab1.2.2.4.11 Rechargeable Batteries Battery Output Voltage Volts Contractor See Tech Vocab1.2.2.4.11 Rechargeable Batteries Heritage Predecessor System Year Contractor See Tech Vocab1.2.2.4.11 Rechargeable Batteries Battery Type of Battery List Contractor See Tech Vocab PDR / CDR CDRL Delivery to CADE1.2.2.4.11 Rechargeable Batteries PhysicalElec Weight Pounds Contractor See Tech Vocab Mass Props CDRL Delivery to CADE1.2.2.4.13 Harnesses and Cables Heritage New Design List Contractor See Tech Vocab1.2.2.4.13 Harnesses and Cables Heritage Predecessor System Year Contractor See Tech Vocab1.2.2.4.13 Harnesses and Cables PhysicalElec Weight Pounds Contractor See Tech Vocab Mass Props CDRL Delivery to CADE
COST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN
TECHNICAL PARAMETER REQUIREMENTS
23. WBS ELEMENT
CODE24. WBS ELEMENT NAME 25. ITEM TYPE
26. TECHNICAL PARAMETER
PO Office
OSD CAPE
Service Cost
Service EV
DCARCL&MR
PARCA
SYSCOM
CWIPT
11
12
Technical Data Submission EventsTechnical Data Reporting Implementation
Development
Production
Sustainment
TDR Submission Events and Frequency Varies by Life Cycle PhaseFor additional information, see:DD 2794 Overview
Event 1 CDR
Event 2 First
Delivery
Event 3 Contract
End
Lot 1
Lot 2
Lot 3
Event 1 Lot 1 Delivery(Contract End)
CLS Year 1 Europe
CLS Year 2 Europe
CLS Year 2 CONUS
Event 1 Year 1 Complete
Event 2Year 2 Complete
When Will the Cost Community Collect Technical Data?
Technical Data Reporting SupplementTechnical Data Reporting Implementation
Revise generic Technical Data CDRL (DD 1423) to Program specifics
13
• Technical Data Report example CDRL language can be downloaded at https://cade.osd.mil/policy/cdrl
• CDRL language should always refer to the CSDR Plan for technical data parameter requirements by WBS element
• In cases where other CDRLs meet the requirements for technical data parameter, but are not explicitly reported on the TDR, the CDRL language should specify the following:
• Any alternative CDRL identified through the CWIPT process that meets the requirements for technical parameter reporting should be submitted to CADE along with the TDR for each required submission event, as specified in Block 15 (CSDR Submission Events)
Technical Data Reporting SupplementTechnical Data Reporting Implementation
Participate in pre/post award conferences to Ensure Tech Data requirements are well understood
14
• Pre/Post Award discussions with industry can cover the following topics:• Review of “Scope Definition: Order/Lots/End Items” (DD 2794 Items 17, 18, 19)
• Ensure that industry understands the desired breakout of Delivery Orders, Lots, Builds, as well as all applicable Variant or End Item reporting
• Ties to the TDR requirement for “Mapping ID” to tie the reported technical parameter to applicable WBS, Lot, and End Item
• Review “Submission Events” (DD 2794, Item 15)• Ensure industry understands frequency of reporting• Discuss the evolution of parameter values from Estimates to Actuals over the lifecycle of the
contract/program• Review availability of desired parameters listed in the Technical Data Supplement (DD 2794, Items 27-30)
• Ensure industry can report parameter values according to WBS element• Allow contractor to identify other CDRLs that may meet reporting requirements • Ensure that other CDRLs that meet the TDR requirements are submitted along with the TDR in CADE• Review security or classification concerns
• If required, submit a revised Technical Data Supplement to the DCARC, along with revised plan for review and approval
15
Additional ConsiderationsTechnical Data Reporting Implementation
• SRDR Reporting:• If SRDR Development, Maintenance, or ERP reporting is required for the contract, ensure that
the Technical Data Reporting parameters do not duplicate SRDR DID reporting requirements• If SRDR Development, Maintenance, or ERP reporting is NOT required, the Technical Data
Reporting parameters allow for software parameters to be required
• Sustainment & Contractor Logistics Support (CLS) Reporting:• When Maintenance and Repair Reporting is planned, plan the Technical Data Report to capture
the fielded item being supported such as fleet size and OpTempo by location• Leverage the O&S phase Core parameter list to implement sustainment-specific parameters,
such as quantities
• Legacy & FlexFile Reporting:• The DD 2794 Technical Data Supplement can be added to contracts that require either 1921,
legacy reporting requirements, OR FlexFiles• Ensure the submission event tables reflect appropriate forms
For additional information, see:Intersection with Other Reporting
Technical Data Reporting ResourcesTechnical Data Reporting Implementation
16
1. Technical Data Reporting Implementation Intersection With Other Reporting
2. Technical Data Reporting Implementation Focus Group and CIPT Details 3. Technical Data Reporting Implementation Technical Data Vocabulary
Database4. Technical Data Reporting Implementation DD 2794 Overview5. Technical Data Reporting Implementation Treatment of Variants6. Technical Data Reporting Implementation Planning, Tailoring, and
Reporting Using Temporal Examples of Both CARD and TDR7. Technical Data Reporting Implementation Treatment of Margin and
Data Pedigree8. Technical Data Reporting Implementation Tech Data Usage Examples
USAF
Technical Data Reporting Frequently Asked Questions (FAQs)
Frequently Asked Questions & ResponsesTechnical Data Reporting Implementation
• Why Does Cost Community Need Technical Data?› Defines the Program’s Technical & Programmatic Baseline› Foundation for Independent Technical Assessments
› Supports architecture trade studies
› Highlights areas of potential risk› Backbone for Affordability Modeling
› Identification and quantification of cost drivers
› Permits assessment of Program A vs. Program B complexity• Critical to analogy estimating• Fine tunes parametric estimates
18
Frequently Asked Questions & ResponsesTechnical Data Reporting Implementation
• Doesn’t the CARD provide the requisite Tech Data?› CARDs are a product of the Program Office, whereas the TDR is a contract CDRL› The TDR typically pertains to only the immediate contract content whereas the CARD is forward
looking and pertains to the whole program life cycle
› The Technical Data Vocabulary Database organizes the parameters by data provider; either government or industry
› The CARD is a living document, updated on an annual basis, and serves as the authoritative source for all programmatic technical data:
› Parameters provided by the government are tagged as such in the “Source” column› Parameters provided by industry via the TDR and other CDRLs are added to the eCARD tables, and
documented as industry-provided in the “Source” column
19
Frequently Asked Questions & ResponsesTechnical Data Reporting Implementation
• Why Can’t I get Technical Data from Other Contract Data?› Cost Community does not own the requirement, hence it can get removed / tailored from contract› There is no consistent (standard) set of Tech Data required for every contract
› There is no central repository of Tech Data by contract
› There is not always consistent definition of terms used for Tech Data› Deliveries of other Tech Data via contract may not be timely to support estimating needs
• How can I ensure the Technical Data requirement can be satisfied by Industry?› The CWIPTs responsibility is to account of the availability of the contractor’s technical data› The Program Office should take advantage of the Post Award Conference to review the list of
technical parameters with industry to ensure availability of the data, the connection to the WBS, and to minimize the duplication of reported parameters across other CDRLs
• What about Industry Technical Data Rights, Security Concerns?› The TDR should be reviewed and approved by the security officer prior to submission into CADE to
ensure that there is no classified data, or aggregation of unclassified data that would cause the TDR to be classified 20
Frequently Asked Questions & ResponsesTechnical Data Reporting Implementation
• What Programs have we implemented the Tech Data requirement?• WSFO placed about 130 parameters on contract of which 50 were unique
Negotiated scope with PM / SPO team prior to RFP release Cemented the requirement with Industry during post award conference
• GBSD placed about 900 parameters on contract, 50 of them unique (e.g., weight, power, heritage)Data requirement worked together by SPO / AFCAAData requirement to be streamlined commensurate with GBSD tradespace solutions
• GPS IIIF program identified about 200 parameters (<50 unique) and through CWIPT process concluded requirement could be satisfied with revised CARD and other contract CDRLS Cost teams identified core parameters required Program team / AFCAA reviewed other program CDRLs to assess availability and accuracy of data Program Manager / AFCAA made agreement to include core parameters in the annual CARD and deliver
technical CDRLs where needed to define core parameters
• OPIR Contracts – CWIPT determining the right solution for rapid prototype efforts
21
USAF
BACKUP:Technical Data Reporting Resources
USAF
Technical Data Reporting ImplementationIntersection With Other Reporting
24
Intersection of Technical Data Reporting and SRDRTechnical Data Reporting Implementation
When SRDRs are planned for a contract, additional Technical Parameters on Software WBS elements are not needed.
However, when SRDRs are not planned but the contract has Software content, consider a Technical Data Report to obtain minimum essential software parameters.
Software (non-SRDR)Reused CodeCarryover CodeAuto-generated codeSoftware LanguageProduct Size - DeliveredProduct Size - EffectiveESLOC EquationNew Code Modified CodeDevelopment ProcessLanguageProduct SizeApplication Domain
Software SupportSoftware ChangesSoftware Support – FTEs
Software DetailAutocode SLOC Conversion FactorsSoftware Development Standard Software Effort Allocation FactorsSoftware Heritage Factors Software PlatformSoftware Productivity Rule-of-Thumb RatesSoftware Reliability Spec Level Software Security Requirements Software Target Security RqmtsSoftware Test Level
25
Intersection of Technical Data Reporting and Maintenance and Repair DataTechnical Data Reporting Implementation
Applicable to Sustainment contracts and Production contracts with Interim Contractor Logistics Support.
When Maintenance and Repair Reporting is planned, plan the Technical Data Report to capture the fielded item being supported such as fleet size and OPTEMPO.
26
Intersection of Technical Data Reporting and CARDTechnical Data Reporting Implementation
AcquisitionRoles
PMP Hardware Technical
Data
Program& Mile-stones
O&S Detail
Software DetailO&S
Total Cost Community Requirements
Time Phased
ManpowerCost
Time Phased
Equipment
Non-PMP Technical
Data
Technical Data Report
CARD captures a subset of total requirements – primarily a program office point of view.
M/R SRDR FlexFile
CDRLs capture a subset of total requirements- Primarily a contractor’s point of view
A Program Office may use the Tech Data Report to satisfy or augment their CARD requirements.
USAF
Technical Data Reporting ImplementationTechnical Data Vocabulary Database
28
Grouped Parameters Create Item Types and SubTypesTechnical Data Reporting Implementation
Item Types are Unique to a Type of WBS ElementSubtypes are Common to Many WBS Elements
C4I Electronics 1.1.1.2 Amplifier
VolumeWeight Weight - StructuralWeight - ElectronicsPower - Max Consumption Rate
Technology Readiness Level (TRL)Percent New DesignPredecessor System
Part NumberManufacturer
GainBandwidthEfficiencySlew RateFrequency – MaxFrequency – MinAmplifier EfficiencyAmplifier Type
Space 1.2.2.7 TT&C
VolumeWeight Weight - StructuralWeight - ElectronicsPower - Max Consumption Rate
Technology Readiness Level (TRL)Percent New DesignPredecessor System
Part NumberManufacturer
Number of Unique Designs - Application Specific Integrated Circuit (ASIC)Uplink ModesData Rate - Average DownlinkData Rate - Average UplinkData Rate - Maximum DownlinkData Rate - Maximum UplinkMemory - Data Storage Capacity
Missile 1.1.4.4.2 Transmitter
VolumeWeight Weight - StructuralWeight - ElectronicsPower - Max Consumption Rate
Technology Readiness Level (TRL)Percent New DesignPredecessor System
Part NumberManufacturer
Transmitter Power Output - PeakTransmitter Power Output - AverageBeam widthSensitivity - SeekerNoise Figure - ReceiverNumber of OscillatorsImpedance
PhysicalElec
Heritage
Identification
AmplifierTransRecRFTT&C
Common Subtypes are
applicable across many commodities
and WBS elements
Unique Item Types
Subtypes are applicable to
few commodities or few WBS
elements
29
Vocabulary File OverviewTechnical Data Reporting Implementation
Commodity WBS Sheets
The CADE Technical Vocabulary is comprised of two parts.
1. A glossary of parameter names, units, and definitions organized by Item Type
2. Commodity Work Breakdown Structures with associated Item Types
Vocabulary Sheet
Item Type Parameter Name Item TypesCSDR Standard Plan WBS
30
Creating Your Tech Data Plan (1 of 2)Technical Data Reporting Implementation
To tailor a specific contract Tech Data Plan.1. Insert your contract WBS onto a Commodity WBS sheet and designate Item Types by WBS element
1. Copy the WBS Commodity worksheet most similar to your Contract WBS and rename the worksheet.
2. Edit WBS Columns B and C to Match your Contract WBS.
3. Edit Item Types (Columns E-R, as needed) to match the content of each WBS element.
31
Creating Your Tech Data Plan (2 of 2)Technical Data Reporting Implementation
To tailor a specific contract Tech Data Plan (cont.)2. Edit parameters as needed for each Item Type.
2a. Navigate to the Vocabulary worksheet.2b. In column AF-AH for your phase, the rows with “Core” will be placed onto your TDR plan. Edit as desired.2c. Insert rows and add additional parameters if desired. 2d. In column AD verify all of your Core selections are also designated as Contractor.
- copy parameters from other item types if applicable- if inserting entirely new parameters then ensure name, units, and definition are
complete.
2e. Save file using a new filename.
32
Generating Your Tech Data PlanTechnical Data Reporting Implementation
1. Go to Main Menu Sheet.
2. Press Select a Commodity button on the Create CSDR Plan Tech Data Supplement box .
3. Select the commodity.
4. Select Phase.
5. Select Core (unless you want everything imaginable on your Tech Data Plan
33
Things to Note:Technical Data Reporting Implementation
1. When generating the Tech Data plan, the macro will hide all of the worksheets used to create the Tech Data plan. If you would like to create or edit a previously created Tech Data plan make sure to unhide all of the worksheets using the macro “UnHideAllWorkSheets”
2. When you create a new worksheet with for a new WBS structure, the name of the worksheet will populate in the drop down “1. Commodity”
3. Make sure that when updating the item type and WBS elements on the commodity worksheet you created, that the corresponding formulas are updated as well. Columns Z – AN pictured below.
4. Cells in columns AB – AN are used to verify the Item Type has been spelled correctly and is indeed on the Vocabulary sheet. When cell AB1 shows a zero you are good to go.
34
Future cPET FeaturesTechnical Data Reporting Implementation
Tech Data Supplement
The functionality of this utility is anticipated in a future version of cPET.
USAF
Technical Data Reporting ImplementationDD 2794 Overview
New DD 2794Technical Data Reporting Implementation
36
Legacy 1921 & SRDR
METADATA REPORTING SUMMARY SUBMISSION EVENTS REMARKS SRDR SUPPLEMENT
FlexFile & Technical & SRDR
METADATA REPORTING SUMMARY SUBMISSION EVENTS REMARKS SCOPE DEFINITION SRDR SUPPLEMENTS TECHNICAL DATA
SUPPLEMENT
METADATA REPORTING SUMMARY
SUBMISSION EVENTS REMARKS
+ SCOPE DEFINITION + SRDR SUPPLEMENTS+ TECHNCIAL DATA
SUPPLEMENT
RemarksTechnical Data Reporting Implementation
37
Remarks:
• Standard plan language will be leveraged
• Variant and submission instructions no longer applicable for FlexFileimplementation
• May contain post-award revisions to specify additional contractor reported fields in FlexFile submission
38
Prime Reporting of Subcontracted ItemsTechnical Data Reporting Implementation
Are primes responsible for reporting technical parameters for subcontractors/suppliers?
Direct Reporting Subcontractors(Contract Value > $50M)
Material Supplier/Non-Reporting Subcontractor
(Contract Value < $20M)
Prime flows reporting requirements down to
subcontractors
Subcontractor submits Technical Data directly to DCARC
Prime contractor collects technical data from supplier/subcontractor
Prime contractor submits Technical Data directly to DCARC
USAF
Technical Data Reporting ImplementationTreatment of Variants
40
Treatment of Multiple VariantsTechnical Data Reporting Implementation
› When reporting multiple variants, use Mapping ID to avoid repetition of common parameter values.
› Example two variants differing only in Mission LRU.
5.3.1 Mapping ID: By hardware item, a uniqueidentifier by Item Type for each individual groupof parameters. Unique identifiers are used onlywhen reporting common parameters acrossmultiple variants is desired. Otherwise the WBSElement Code may be repeated here and used asthe Mapping ID. Created by the reportingorganization, the Mapping ID is any unique alpha-numeric code that is used to differentiatebetween individual parts. This is used to matchthe technical parameters to the End Item ID andcorresponding WBS element code in the“Technical Data WBS Mapping ID” table, DataGroup D (Mapping ID) of the Technical DataReport. If there is only one identified End Itemand Order Name, the reporting organization mayuse the WBS element code as the Mapping ID.
Mapping ID WBS Element Code End Item Order Name RemarksA_1.0 1.0 B-R549-A Aircraft EMD Terrestrial VariantA_1.1 1.1 B-R549-A Aircraft EMD Terrestrial VariantA_1.1.1 1.1.1 B-R549-A Aircraft EMD Terrestrial VariantA_1.1.1.1 1.1.1.1 B-R549-A Aircraft EMD Terrestrial VariantA_1.1.1.2 1.1.1.2 B-R549-A Aircraft EMD Terrestrial VariantA_1.1.2 1.1.2 B-R549-A Aircraft EMD Terrestrial VariantA_1.1.3 1.1.3 B-R549-A Aircraft EMD Terrestrial VariantB_1.0 1.0 B-R549-B Aircraft EMD Maritime VariantB_1.1 1.1 B-R549-B Aircraft EMD Maritime VariantB_1.1.1 1.1.1 B-R549-B Aircraft EMD Maritime VariantB_1.1.1.1 1.1.1.1 B-R549-B Aircraft EMD Maritime VariantB_1.1.1.2 1.1.1.2 B-R549-B Aircraft EMD Maritime VariantB_1.1.2 1.1.2 B-R549-B Aircraft EMD Maritime VariantB_1.1.3 1.1.3 B-R549-B Aircraft EMD Maritime Variant
TECH: WBS Mapping ID
Mapping ID WBS Element Code End Item Order Name RemarksCommon_1.0 1.0 B-R549 Aircraft EMD Common to All VariantsUnique_A_1.1 1.1 B-R549-A Aircraft EMD Terrestrial VariantUnique_B_1.1 1.1 B-R549-B Aircraft EMD Maritime VariantCommon_1.1.1 1.1.1 B-R549 Aircraft EMD Common to All VariantsCommon_1.1.1.1 1.1.1.1 B-R549 Aircraft EMD Common to All VariantsUnique_A_1.1.1.2 1.1.1.2 B-R549-A Aircraft EMD Terrestrial VariantUnique_B_1.1.1.2 1.1.1.2 B-R549-B Aircraft EMD Maritime VariantCommon_1.1.2 1.1.2 B-R549 Aircraft EMD Common to All VariantsCommon_1.1.3 1.1.3 B-R549 Aircraft EMD Common to All Variants
TECH: WBS Mapping ID
Weak
Better
41
Use of Group Key ExampleTechnical Data Reporting Implementation
› 5.3.4 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.
› Example: LRU (a WBS element) comprised of three cards (not WBS elements). Used to keep each card’s parameters together.
42
Mapping ID & Lot ReportingTechnical Data Reporting Implementation
› 5.4.1 Mapping ID• By hardware item, a unique
identifier by Item Type for each individual group of parameters. Unique identifiers are used only when reporting common parameters across multiple variants is desired. Mapping ID for Item Types which uniquely identify the corresponding Order Name (Lot 1, Lot 2, Lot 3, etc.) and End Item (Model, Version, Flight, Variant, or equivalent grouping or variant of a reported unit or system).
Mapping ID WBS Element Code End Item Order Name RemarksA_Lot 1_ItemTypennn 1.1 A Lot 1B_Lot 1_ItemTypennn 1.1 B Lot 1Common_Lot 1_ItemTypennn 1.1 Common Lot 1A_Lot 2_ItemTypennn 1.1 A Lot 2B_Lot 2_ItemTypennn 1.1 B Lot 2Common_Lot 2_ItemTypennn 1.1 Common Lot 2Common_Lot 1_ItemTypennn 1.1.1 Common Lot 1A_Lot 1_ItemTypennn 1.1.2 A Lot 1B_Lot 2_ItemTypennn 1.1.2 B Lot 2A_Lot 1_ItemTypennn 1.1.2.1 A Lot 1B_Lot 2_ItemTypennn 1.1.2.2 B Lot 2Common_Lot 1_ItemTypennn 1.1.3 Common Lot 1Common_Lot 1_ItemTypennn 1.1.4 Common Lot 1Common_Lot 1_ItemTypennn 1.1.5 Common Lot 1A_Lot 1_ItemTypennn 1.1.7.1 A Lot 1C_Lot 2_ItemTypennn 1.1.7.1 C Lot 2A_Lot 1_ItemTypennn 1.1.7.2 A Lot 1B_Lot 1_ItemTypennn 1.1.7.2 B Lot 1Common_Lot 1_ItemTypennn 1.1.7.2 Common Lot 1
TECH: WBS Mapping ID
USAF
Technical Data Reporting ImplementationPlanning, Tailoring, and Reporting Using
Temporal Examples of Both CARD and TDR
44
An Example Aircraft Program WBS with Item TypesTechnical Data Reporting Implementation
Item Type Modularizes Data
1.0
1.1
1.1.1
1.1.1.1
1.1.1.2
1.1.2
1.1.3
Item TypeWBS Element NameWBS Code
XYZ System
BR549 Aircraft
Electronic Systems
LRU Navigation
LRU Mission
Airframe
Engine
AirVehicle
Avionics
Navigation
ElecBox
Airframe
EngineTurbine
Example will focus on this
WBS element
Core by Phase Anticipated Availability
ITEM TYPE SUBTYPE PARAMETER NAME UNIT OF
MEASURE Dev Prod O&SFinal Authoritative Data Source For
ActualsMS A PDR MS B CDR MS C DEFINITION VocabularyID
ElecBox Clock Speed Megahertz X X Contractor X X X The rate at which the processor can complete a processing CADEVocab0887ElecBox ASIC - Gate Count Quantity X X Contractor X X Enter Avg Application Specific Integrated Circuit (ASIC) gate CADEVocab0315ElecBox FPGA - Gate Count Quantity X X Contractor X X FPGA gate count NOT including memory CADEVocab0317ElecBox Transmitter Power Output - Peak Watts X X Contractor X X X X The Peak Transmitter Power Out. CADEVocab1393ElecBox Number of Receiver Channels Quantity X X Contractor X X X X This parameter is the Total Number of independent RF receivers CADEVocab0292ElecBox Type of Modulation List X X Contractor X X X X The type of Signal Modulation. CADEVocab0296ElecBox PhysicalElec Volume Cubic Feet X X X Contractor X X X X Physical volume of the item. CADEVocabPhSW000ElecBox PhysicalElec Weight Pounds X X X Contractor X X X X X Physical weight of the item. CADEVocabSWAP000ElecBox PhysicalElec Power - Maximum Consumption Rate Watts X X X Contractor X X X X Maximum rate of power consumption by the item. CADEVocabSWAP001ElecBox PhysicalElec Weight - Structural Pounds X Contractor X X The item's mechanical/structural weight. CADEVocabSWAP000ElecBox PhysicalElec Weight - Electronics Pounds X Contractor X X The item's electronics weight. CADEVocabSWAP001ElecBox Heritage New Design Percent X Contractor X X X X X The extent of the item's design that is new on a 0-100% scale as CADEVocabHrtg0001ElecBox Heritage Technology Readiness Level (TRL) List X Government X X X X X Technology Readiness Levels (TRL)are a set of nine graded CADEVocabHrtg0002ElecBox Identification NSN Name/Number X X Government X X The item's National Stock Number. A 13-digit number consisting CADEVocabIdnt0001ElecBox Operational Maintenance Level List X X Government X X X X The maintenance echelon(s) the contractor is supporting (e.g. CADEVocabOprn0001ElecBox Operational Mean Time Between Failure (MTBF) Hours X X Contractor X X The item's MTBF. Mean time between failures (MTBF) is the CADEVocabOprn0002ElecBox Operational Mean Time To Repair (MTTR) Hours X X Contractor X X The item's MTTR. Mean time to repair (MTTR) is the average CADEVocabOprn0003
1.0 XYZ Sytem 1.0 Aircraft1.1 BR549 Aircraft 1.1 Air Vehicle PhysicalStruc PhysicalOther Heritage Identification AirVehicle1.1.1 Electronic Systems 1.1.1 Avionics PhysicalElec PhysicalOther Heritage Identification Avionics ElecBox1.1.1.1 LRU Navigation 1.1.1.1 Navigation/Guidance PhysicalElec PhysicalOther Heritage Identification Navigation ElecBox1.1.1.2 LRU Mission 1.1.1.2 Mission Computer/Processing PhysicalElec PhysicalOther Heritage Identification Computer ElecBox1.1.2 Airframe 1.1.2 Airframe PhysicalStruc PhysicalOther Heritage Identification Airframe1.1.3 Engine 1.1.3 Engine/Propulsion PhysicalStruc PhysicalOther Heritage Identification EngineTurbine EngineTurboJetFan
45
Technical Vocabulary Comprised of Item TypesTechnical Data Reporting Implementation
Standard WBS Unique Items TypesProgram WBS Common Subtypes
Core by Phase Anticipated Availability
ITEM TYPE SUBTYPE PARAMETER NAME UNIT OF
MEASURE Dev Prod O&SFinal Authoritative Data Source For
ActualsMS A PDR MS B CDR MS C DEFINITION VocabularyID
ElecBox Clock Speed Megahertz X X Contractor X X X The rate at which the processor can complete a processing CADEVocab0887ElecBox ASIC - Gate Count Quantity X X Contractor X X Enter Avg Application Specific Integrated Circuit (ASIC) gate CADEVocab0315ElecBox FPGA - Gate Count Quantity X X Contractor X X FPGA gate count NOT including memory CADEVocab0317ElecBox Transmitter Power Output - Peak Watts X X Contractor X X X X The Peak Transmitter Power Out. CADEVocab1393ElecBox Number of Receiver Channels Quantity X X Contractor X X X X This parameter is the Total Number of independent RF receivers CADEVocab0292ElecBox Type of Modulation List X X Contractor X X X X The type of Signal Modulation. CADEVocab0296ElecBox PhysicalElec Volume Cubic Feet X X X Contractor X X X X Physical volume of the item. CADEVocabPhSW000ElecBox PhysicalElec Weight Pounds X X X Contractor X X X X X Physical weight of the item. CADEVocabSWAP000ElecBox PhysicalElec Power - Maximum Consumption Rate Watts X X X Contractor X X X X Maximum rate of power consumption by the item. CADEVocabSWAP001ElecBox PhysicalElec Weight - Structural Pounds X Contractor X X The item's mechanical/structural weight. CADEVocabSWAP000ElecBox PhysicalElec Weight - Electronics Pounds X Contractor X X The item's electronics weight. CADEVocabSWAP001ElecBox Heritage New Design Percent X Contractor X X X X X The extent of the item's design that is new on a 0-100% scale as CADEVocabHrtg0001ElecBox Heritage Technology Readiness Level (TRL) List X Government X X X X X Technology Readiness Levels (TRL)are a set of nine graded CADEVocabHrtg0002ElecBox Identification NSN Name/Number X X Government X X The item's National Stock Number. A 13-digit number consisting CADEVocabIdnt0001ElecBox Operational Maintenance Level List X X Government X X X X The maintenance echelon(s) the contractor is supporting (e.g. CADEVocabOprn0001ElecBox Operational Mean Time Between Failure (MTBF) Hours X X Contractor X X The item's MTBF. Mean time between failures (MTBF) is the CADEVocabOprn0002ElecBox Operational Mean Time To Repair (MTTR) Hours X X Contractor X X The item's MTTR. Mean time to repair (MTTR) is the average CADEVocabOprn0003 46
CWIPT’s Use of the Technical VocabularyTechnical Data Reporting Implementation
CWIPT Uses Tech Vocabulary to Tailor
each Co-Plan
Is this a typically
Contractor determined
value?
Is this needed for
this Phase?
Will this value be
available at the
submission event?
Is this value available from another source?
PO Office
OSD CAPE
Service Cost
Service EV
DCARCL&MR
PARCA
SYSCOM
CWIPT
47
Example CARDs and TDRs in EMDTechnical Data Reporting Implementation
In This Example, EMD’s Time Span Envelopes Three TDR Submissions by the Contractor and Multiple CARD Submissions by the PM
Annual CARDs
MS B CARD MS C CARD
Development Contract
CDRFirst
DeliveryContract
End
TDRSubmissions:
BR549 AircraftEnd Item WBS Elements Tech Data:
Estimates Actuals
TDR Submission
Event 1
TDR Submission
Event 2
TDR Submission
Event 3
WBS Number WBS Element Parameter Name Value Low High Margin Unit of
MeasureUnit
QualifierEstimate or Actual Objective Threshold Source
1.0 XYZ System1.1 BR549 Aircraft
Combat Radius 100 80 100 Nautical Miles Estimate 110 90 Lead Engineer (June 2014), draft CONOPSAbsolute Ceiling 25,000 25,000 30,000 Feet Estimate 27,000 22,000 Lead Engineer (June 2014), draft CONOPSWeight 99,500 Pounds Estimate 98,000 106,000 CCD Oct 2016
1.1.1.2 LRU MissionClock Speed 800 Megahertz Estimate Systems Engineering Plan (SEP)ASIC - Gate Count 300,000 300,000 350,000 Quantity Gates Estimate COTS Brochure, Lead Engineer (June 2014), Systems FPGA - Gate Count 275,000 275,000 325,000 Quantity Gates Estimate Lead Engineer (June 2014), Systems Engineering Plan (SEP)Type of Modulation AM List Estimate Lead Engineer (June 2014), draft CONOPSVolume 1 0.9 1.1 Cubic Feet Estimate Lead Engineer (June 2014), Systems Engineering Plan (SEP)Weight 20 18 21 Pounds Estimate CDD (May 2014)Power - Maximum Consumption 18 17 25 Watts Estimate Lead Engineer (June 2014), Systems Engineering Plan (SEP)New Design 100 Percent Estimate Lead Engineer (June 2014), Systems Engineering Plan (SEP)Technology Readiness Level (TRL) 4 List Actual TRL Assessment June 2014
48
Example MS B CARDTechnical Data Reporting Implementation
Government Ref Architecture
documents and Government SMEs cited.
Low and High values often in
early CARDs but TDR contains point
estimates.
Few actuals in early CARDs.
Assessing TRL is an inherently Government
function. Will not be on the
TDR.
Objective/ Threshold
stated at high levels of the
WBS.
a. PARAMETER NAME b. UNIT OF MEASURE
c. UNIT OF MEASURE QUALIFIER
d. REPEATABLE e. REMARKS
1.1 B-R549 Aircraft AirVehicle Combat Ceiling Feet1.1 B-R549 Aircraft AirVehicle Absolute Ceiling Feet1.1 B-R549 Aircraft AirVehicle Weight Pounds Mass Properties CDRL B0101.1.1.2 LRU Mission ElecBox Clock Speed Megahertz1.1.1.2 LRU Mission ElecBox ASIC - Gate Count Quantity Gates1.1.1.2 LRU Mission ElecBox FPGA - Gate Count Quantity Gates1.1.1.2 LRU Mission ElecBox Type of Modulation List Systems Engineering Plan1.1.1.2 LRU Mission ElecBox Volume Cubic Feet1.1.1.2 LRU Mission ElecBox Weight Pounds Mass Properties CDRL B0101.1.1.2 LRU Mission ElecBox Power - Maximum Consumption Rate Watts1.1.1.2 LRU Mission ElecBox New Design Percent
DD FORM 2794 (Page 4),TECHNCIAL PARAMETER REQUIREMENTS, JUNE 2017 PREVIOUS EDITION IS OBSOLETE
COST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN
TECHNICAL PARAMETER REQUIREMENTS
23. WBS ELEMENT
CODE
24. WBS ELEMENT NAME 25. ITEM TYPE
26. TECHNICAL PARAMETER
49
Example EMD Co-PlanTechnical Data Reporting Implementation
CWIPT prudently tailors the Co-
Plan.
PO Office
OSD CAPE
Service Cost
Service EV
DCARCL&MR
PARCA
SYSCOM
CWIPT
Mapping ID Item Type Technical Parameter Name Group Key Value Unit of MeasureUnit of Measure
Qualifier Estimate/Actual Margin Remarks1.1 Air Vehicle Combat Radius 98 Nautical Miles Estimate1.1 Air Vehicle Absolute Ceiling 25000 Feet Estimate Simulation Oct20201.1 Air Vehicle Weight 100000 Pounds Estimate 50001.1.1.2 ElecBox Clock Speed 800 Megahertz Estimate1.1.1.2 ElecBox ASIC - Gate Count 300000 Quantity Gates Estimate Average three candidate vendor proposals1.1.1.2 ElecBox FPGA - Gate Count 278000 Quantity Gates Estimate1.1.1.2 ElecBox Volume 1 Cubic Feet Estimate1.1.1.2 ElecBox Weight 20 Pounds Estimate 18.5 Low - 20.2 High1.1.1.2 ElecBox Power - Maximum Consumption Rate 18 Watts Estimate Power Budget Nov20191.1.1.2 ElecBox New Design 50 Percent Estimate Adapt from system zz
TECH: Parameters by Mapping ID
50
Example TDR Submission #1 CDRTechnical Data Reporting Implementation
Enter any information that would explain any peculiarities or ambiguities
in any of the data reported.
Many estimated values at this
event.
Reported values.
Mapping ID Item Type Technical Parameter Name Group Key Value Unit of MeasureUnit of Measure
Qualifier Estimate/Actual Margin Remarks1.1 Air Vehicle Combat Radius 98 Nautical Miles Estimate1.1 Air Vehicle Absolute Ceiling 25000 Feet Estimate1.1 Air Vehicle Weight 104883 Pounds Actual 1171.1.1.2 ElecBox Clock Speed 800 Megahertz Actual1.1.1.2 ElecBox ASIC - Gate Count 300324 Quantity Gates Actual1.1.1.2 ElecBox FPGA - Gate Count 245811 Quantity Gates Actual1.1.1.2 ElecBox Volume 1 Cubic Feet Actual1.1.1.2 ElecBox Weight 20 Pounds Actual1.1.1.2 ElecBox Power - Maximum Consumption Rate 18 Watts Actual Bench Test Results May 20211.1.1.2 ElecBox New Design 100 Percent Actual Abandoned reuse of prior design, TIM Jun 2021
TECH: Parameters by Mapping ID
51
Example TDR Submission #2 First DeliveryTechnical Data Reporting Implementation
Many actual values at this event.
Tighter measured values. More significant
digits.
Margin consumed since Submission #1
WBS Number WBS Element Parameter Name Value Low High Margin Unit of
MeasureUnit
QualifierEstimate or
Actual Objective Threshold Source
1.0 XYZ System1.1 BR549 Aircraft
Combat Radius 98 Nautical Miles Actual 110 90 DT&E Flight #12 Nov 2021Absolute Ceiling 25000 Feet Actual 27,000 22,000 DT&E Flight #14 Nov 2021Weight 105,000 Pounds Actual 98,000 106,000 Mass Properties First DeliveryL B010 May 2021
1.1.1.2 LRU MissionClock Speed 800 Megahertz Actual TDR First Delivery SubmissionASIC - Gate Count 300,000 Quantity Gates Actual TDR First Delivery SubmissionFPGA - Gate Count 278,000 Quantity Gates Actual TDR First Delivery SubmissionType of Modulation AM List Actual Lead Engineer (June 2014), draft CONOPSVolume 1 Cubic Feet Actual TDR First Delivery SubmissionWeight 20 Pounds Actual Mass Properties First DeliveryL B010 May 2021Power - Maximum Consumption 18 Watts Actual TDR First Delivery SubmissionNew Design 100 Percent Actual TDR First Delivery SubmissionTechnology Readiness Level (TRL) 7 List Actual TRL Assessment June 2021
52
Example MS C CARDTechnical Data Reporting Implementation
TDR cited as source in many
cases.
Low and High values sparse in
later CARDs.
More actuals in later CARDs.
53
Example DatabaseTechnical Data Reporting Implementation
Vandalay Industries
Filter
1.1 Air Vehicle
Air Vehicle
Weight
WBS Element
Item Type
Parameter
BR-549 Aircraft WXXXX-17-C-000X Vandalay
PoundsUnit of Measure
54
Example Parameter Over Time ChartTechnical Data Reporting Implementation
Vandalay Industries
BR-549 Aircraft WXXXX-17-C-000X Vandalay
Filter
1.1 Air Vehicle
Air Vehicle
Weight
WBS Element
Item Type
Parameter
PoundsUnit of Measure
USAF
Technical Data Reporting ImplementationTreatment of Margin and Data Pedigree
Mapping ID Item TypeTechnical
Parameter NameGroup Key Value Unit of Measure
Unit of Measure Qualifier
Estimate/Actual
Margin Remarks
1.0 VEHICLE Weight 2150 Pounds Estimate 200
TECH: Parameters by Mapping ID
56
MarginTechnical Data Reporting Implementation
› Margin 5.3.9• The estimated or measured
margin for the associated Technical Parameter specified by the Mapping ID. The margin value may be reported anytime the parameter is routinely expressed as a single planned value plus some amount of design margin or growth allowance. Margin is expressed in the same units as the parameter value – not as a percentage.
An item may have a planned value of 2150 lbs with a contingency of an additional 200 lbs of growth allowance. This would be expressed with a Value=2150; Margin=200; and Unit
of Measure="Pounds." Do not enter a percent.
Value 2150 Margin 200
57
Estimate vs. ActualTechnical Data Reporting Implementation
› 5.3.8 Estimate vs. Actual• For each parameter value,
“Estimate” or “Actual” shall be reported for the most representative valuation of the “pedigree” or derivation of the technical parameter values reported (DID reference 5.3.8)
Threshold Value
Spec Value
EstimateMeasured
Value
Known Value
Actual