flexfile 101 - cade flexfile 101.pdfone flexfile provides the analyst more granular data. than a...
TRANSCRIPT
COST ASSESSMENT DATA ENTERPRISE
FlexFile 101
2
AgendaFlexFile 101
Implementation
• FlexFile and Quantity Data Report will replace DD 1921 series as the default cost reporting requirement for newly approved CSDR plans starting May 15th (per DD,CA memo)
• Some tailoring of the DID requirements may be proposed by the CWIPT (e.g., time-phasing for periods longer than a month)
• If there is context-specific rationale, e.g., the reporting contractor and effort being performed make it unlikely the additional insight provided will be utilized, then the CWIPT may propose to use the DD 1921 series
FlexFile Overview
FlexFile Data Groups
New “Big Three”
Planning Process
End Item and Order/Lot in the Planning Process
Quantity Data Report
Submission and Validation
CADE Data & Analytics Redesign
3
Legacy 1921 Reports to FlexFilesFlexFile Overview
Flex
File
/Qua
ntity
Dat
a Re
port
Lega
cy D
IDs
From five DIDs to two
CWBS Index and Dictionary
1921: Cost Data Summary Report
1921-1: Functional Cost-Hour Report
1921-2: Progress Curve Report
1921-5: Sustainment Functional Cost-Hour Report
4
Legacy Reports and the FlexFileFlexFile Overview
Old “Big Three”
Work Breakdown Structure Nonrecurring and Recurring Standard Functional Categories
5
Legacy Reports and the FlexFileFlexFile Overview
Old “Big Three”
Work Breakdown Structure Nonrecurring and Recurring Standard Functional Categories
New “Big Three”
Monthly Time-phased Data “Account” Level Detail Contractor Functional Categories
The FlexFile combines both the old and the new in one report that supports both top-down and bottom-up estimates
FlexFile Data Fields will be explained on the next few slides
6
Approved FlexFile Data RequirementsFlexFile Data Groups
Data Group B
DD Form 2794 Data ElementsWBS ElementOrder/LotEnd Item
Data Group A
Report MetadataApproved Plan NumberSubmission EventPeriod of PerformanceReporting OrganizationAs of DateDate Preparedmore in the DID…
Data Group C
Definitions and RemarksWBS Element DefinitionsRemarks by WBS ElementSummary Remarks
Data Group E
Actuals To Date (ATD)AccountReporting PeriodCLINNonrecurring or RecurringFunctional Category / OverheadStandard Functional CategoryUnit/SublotWBS ElementOrder/Lot and End ItemATD (Dollars and Labor Hours)
Data Group D
Summary ElementsOrder/LotSubtotalGeneral and AdministrativeUndistributed BudgetManagement ReserveFacilities Capital Cost of MoneyContract FeeContract Price
Data Group F
Allocation MethodologyAllocation Method
Data Group G
Forecasts At Completion (FAC)FAC (Dollars)FAC (Labor Hours)
Legacy Element
The core of the FlexFile is providing dollars and hours at the account level in contractornative categories, time phased.
Insight into contractor’s native Functional Categories
Account level reporting at or below the WBS
Data time-phased monthly or to align with contractor’s financial calendar
Continuity with prior reports by requiring the legacy government tags
Greatest value to cost estimator, in many cases, will be the additional insight requested in Group E
End Item and Order/LotFlexFile Data Groups
Relationship with Submission Events
A single FlexFile submission will contain data for all of the identified End Items and Order/Lots as opposed to requiring as many submissions as there are End Item and Order/Lot combinations.
For example, if there are five lots on a contract, the Legacy CCDRs would have been given five submissionsfor each lot in the final year of the contract.
In the FlexFile, those five lots would be detailed in the Order/Lot table (depicted below) and the data for each will be provided in a single submission.
Order/Lot
Lot 1
Lot 2
Lot 3
Lot 4
Lot 5
What is End Item?End Items are uniquely identified platforms, models, versions, flights, variants, kits, services, or sustainment activities that are delivered.
They will be identified by the CWIPT during the planning process in block 17 of the plan.
Some examples are detailed below…
What is Order/Lot?Order/Lot field identifies different purchase orders on the same contract.
They will be identified by the CWIPT during the planning process in block 16 of the plan.
Some examples are detailed below…
End Item
Variant A
Variant B
End Item
Hull 100
Hull 101
End Item
Kit 1
Kit 2
End Item
F-120 A
F-120 B
Order/Lot
Lot 1
Lot 2
Order/Lot
LRIP 1
LRIP 2
Order/Lot
DO 001
DO 002
Order/Lot
Prelim Design
Detailed Design
The FlexFile will be reported in a way that tags each dollar and hour to a combination of one End Item tag and one Order/Lot tag
End Item
Aircraft
Order/Lot
Total Contract
More examples of this provided in the planning section
7
End Item and Order/LotFlexFile Data Groups
A B C D1 WBS ID WBS Name Variant A $ Variant B $2 1.1 Family of Vehicles 1,000.00$ 1,000.00$ 3 1.1.1 IAT&C 250.00$ 250.00$ 4 1.1.2 Hull/Frame/Body/Cab 250.00$ 250.00$ 5 1.1.3 System Survivability 500.00$ 500.00$
A B C D1 Order/Lot End Item WBS Dollars2 Total Contract Variant A 1.1.1 250.00$ 3 Total Contract Variant B 1.1.1 250.00$ 4 Total Contract Variant A 1.1.2 250.00$ 5 Total Contract Variant B 1.1.2 250.00$ 6 Total Contract Variant A 1.1.3 500.00$ 7 Total Contract Variant B 1.1.3 500.00$
Actual Cost-Hour Data Table (excerpt)
An example of what a pivot table could look like
What is submitted?
The FlexFile will be reported in way that tags every dollar and hour to a combination of one End Item and one Order/Lot. This means that End Item and Order/Lot are required data elements.
Take for example a contract where the End Item comprises of two variants and the Order/Lot is just the total contract.
The excerpt to the right shows what the FlexFile would look like with Order/Lot and End Item tags. The figure on the bottom right is an example of what a resulting pivot table could look like utilizing the End Item tag.
End Item
Variant A
Variant B
Order/Lot
Total Contract
8
One FlexFile provides the analyst more granular datathan a contract’s worth of 1921s
Default requirement for FlexFile is actual cost data time-phased discretely by month (e.g., a reporting period of 5 years would have 60 discrete monthly data points)
A 1921 only reports cumulative data for the given reporting period
To obtain the same number of data points, a contractor would have to submit 60 monthly 1921s
Disc
rete
Mon
thly
Hou
rs
Cumulative M
onthly Hours
9
Monthly Time-Phased DataNew “Big Three”
The 1921 provides no detail below the WBS or Standard Functional Category
Leads to ad hoc data calls for insight into control account, work package, or similar data
The FlexFile asks for data at an “Account” Level, which is meant to be at or below the lowest level of the WBS
“Account” can be control account, work package, charge code, or similar categories where actual costs are incurred and reflect the contractor’s native system
FlexFile provides the analysts insight into “Account” level detail and reduces need for ad hoc reporting 10
“Account” Level DataNew “Big Three”
Direct Engineering Labor
Engineering Labor OH
Other Manufacturing
Systems Engineering
Design Engineering
Software Engineering
Material Management
Production Engineering
Site 1 Engineering OH
Site 2 Engineering OH
Quality Assurance
Site 1 Manufacturing OH
Site 3 Manufacturing OH
High Value Material
Low Value Material
Material OH 1
Material OH 2
Manufacturing Ops. Labor OH
Direct Material
Material Overhead
Standard Functional Categories
Contractor Functional Categories
FlexFile Functional Categories intended to align with pricing categories for comparability with proposals, negotiations, and FPRA
1921-1s provide analysts a standard view of functional categories across programs, contracts, and business units
However, there may be inconsistencies, and there exists no clear mapping from the contractor’s internal categories to the standards
FlexFile provides insight into the contractor’s pricing categories and a clear mapping to the standard categories
11
Contractor Functional CategoriesNew “Big Three”
FlexFile provides more data and greater native detail, enhancing estimate credibility and defensibility
FlexFile will improve upon the data collected via the DD 1921 forms by including…
Monthly Time-Phased Data “Account” Level Detail Contractor Functional Categories
FlexFile will provide the analyst…
More data points in a single submission More detail, thereby reducing the need for
ad hoc reporting More applicable data when used in contract
proposals and negotiations
12
SummaryFlexFile 101
Planning Process FlowchartPlanning Process
The overarching CSDR planning process does not change when implementing a FlexFile, but some additional considerations exist...
Pre-Plan Plan Development Approval
RFP Release Contract Award
Contract Award and Validations
RFP Identified
Initial Plan Drafted
DCARC/CAPE Review
CWIPT Review
SCC Director Review
DCARC Director Review
DDCA Director Review
Dissemination to CWIPT
Dissemination to Contractors
Post Award Conference
Validation of Cost Reports
Service Component POCProgram OfficeOSD CAPE
DCARC
CWIPTContractors
Service Cost Center POCProgram Office Approves
13
14
Planning ConsiderationsPlanning Process
The following considerations should be included in addition to existing CSDR planning guidance
Define End Item and Order/Lot (see Figure 1)
FACs broken out by Nonrecurring/Recurring and the Standard Functional Category
Quantity Data Report requires that reporting elements are selected and that GFE are properly identified (see Figure 2)
Figure 2 - DD Form 2794, Pg 1 (REPORTING)
Figure 1 - DD Form 2794, Supp. (SCOPE DEF)
a. ID c. PHASE/MILESTONE1 C-LRIP2 C-LRIP
a. ID12
LRIP 2
COST AND SOFTWARE DATA REPORTING PLAN
INTRA-CONTRACT SCOPE REPORTING DEFINITION16. ORDERS/LOTS
17. END ITEMS
b. NAME
b. NAME
LRIP 1
Variant AVariant B
i. QUANTITY DATA
ii. GFE QUANTITY
XXXXXX
b. SRDR FORMATS
a. QUANTITYc.
MAINT. & REPAIR
1.0 1 Ground Vehicle System1.1 2 Family of Vehicles1.1.1 3 Vehicle Integration, Assembly, Test and Checkout X1.1.2 3 Hull/Frame/Body/Cab X1.1.3 3 System Survivability X1.1.4 3 Turret Assembly X
a. WBS CODE
b. WBS LEVEL
a. ACTUALS TO DATE (ATD)c. WBS ELEMENT NAME
a. NAME:
Pre-A B C-FRP X
A X C-LRIP O&S
PROGRAM XX
Myster Inc.X-12-Y-Z01
10. APPROVED PLAN NUMBER9b. CONTRACT NUMBER
X99XYZ-12-X-0001
6d. E-MAIL ADDRESS
ACME Corporation1 Central St.Hollywood, CA
6a. POINT OF CONTACT (POC) NAME AND ADDRESS (Include ZIP Code)
Scrappy Doo100 Main St.Spooky Island, HI
RDT&EPROCUREMENTO&M
9c. APPROPRIATION
6b. TELEPHONE NUMBER (Include Area Code)
7. PLAN TYPECONTRACT (PRIME)CONTRACT (SUB)
ii. DIVISION9a. CONTRACTOR NAME/ADDRESSi. PERFORMING ORGANIZATION
8. PREPARING ORGANIZATION
COST AND SOFTWARE DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN Form Approved OMB No. 0704-0188
b. PHASE/MILESTONE c. PRIME MISSION PRODUCT
The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
2. WBS SYSTEM TYPE1. MAJOR PROGRAM Mystery Machine
3. SUBMISSION TYPE 4. CURRENT SUBMISSION DATE (YYYYMMDD)
6c. FAX NUMBER (Include Area Code)
Surface Vehicle SystemMystery Machine5. LAST APPROVED PLAN DATE (YYYYMMDD)
20110601INITIAL CHANGE
2015 DD Form 2794, Pg 1
FlexFile DD Form 2794, Pg 1 (Metadata)
Metadata from the top of Pg 1 of the 2015 CSDR plan has its own page as part of the FlexFile CSDR plan
Use the section to specify if FAC will be broken out by Nonrecurring/Recurring and Standard Functional Categories
<Input Form Approved OMB Number>
1b. PHASE/MILESTONE (check all that apply)Pre-AAB
X C-LRIPC-FRPO&S
1d. ACQUISITION CATEGORY (ACAT)Pre-ACAT
X ACAT I (MDAP)ACAT IA (MAIS)ACAT IIACAT IIIOther (ACAT IV, Special Interest, etc.)
3. PLAN ITERATION TYPE X INITIAL
REVISION
Surface Vehicle System
20110601
4. CURRENT SUBMISSION DATE (YYYYMMDD)
COST AND SOFTWARE DATA REPORTING PLAN
Mystery Machine
2. COMMODITY TYPE
1c. PRIME MISSION PRODUCT
Mystery Machine
The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not
display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
1a. PROGRAM NAME
15
DD 2794 (CSDR Plan) ComparisonPlanning Process
i. QUANTITYDATA
ii. GFEQUANTITY
1.0 1 Ground Vehicle System X X1.1 2 Family of Vehicles X X1.1.1 3 Vehicle Integration, Assembly, Test and Checkout X X1.1.2 3 Hull/Frame/Body/Cab X X1.1.3 3 System Survivability X X1.1.4 3 Turret Assembly X X1.1.5 3 Suspension/Steering X X1.1.6 3 Vehicle Electronics X X1.1.7 3 Power Package/Drive Train X X1.1.8 3 Auxiliary Automotive X X1.1.9 3 Fire Control X1.1.10 3 Armament X X1.1.11 4 Automatic Ammunition Handling X1.1.12 3 Navigation and Remote Piloting X1.1.13 3 Special Equipment X1.1.14 3 Communications X X1.1.15 3 Vehicle Software Release 1...n X1.1.16 3 Other Vehicle Subsystems 1...n (Specify) X1.2 2 Secondary Vehicle X1.3 2 System Engineering X X1.4 2 Program Management X X1.5 2 System Test and Evaluation X X1.6 2 Training X X1.7 2 Data X1.8 2 Peculiar Support Equipment X1.9 2 Common Support Equipment X1.10 2 Operational/Site Activation X1.11 2 Industrial Facilities X1.12 2 Initial Spares and Repair Parts X X
Subtotal Cost N/A
d. LEGACY1921-5c. WBS ELEMENT NAME
12. COST
e. EAC/FAC(See item 10d)
b. WBSLEVEL
COST AND SOFTWARE DATA REPORTING PLAN
13. TECHNICAL DATA
a. QUANTITY c.MAINT. &REPAIRPARTS
b. SRDRFORMATS
11. WORK BREAKDOWN STRUCTURE (WBS)
a. WBSCODE
a. ACTUALS TODATE (ATD)
b. LEGACY1921-1
c. LEGACY1921-2
2015 DD Form 2794, Pg 1
FlexFile DD Form 2794, Pg 2 (Reporting)
If the CWIPT is requiring FlexFiles:
Indicate the LOWEST LEVEL of the WBS in column 12a (ACTUALS TO DATE (ATD)) where actual cost data is required
Indicate EVERY element for column 12e (AT COMPLETION COSTS) where forecasted data is required
Indicate which elements require quantity report data in box 13a
16
DD 2794 (CSDR Plan) ComparisonPlanning Process
X
e. DD 1921-5(SFCHR)
XXXXXXXXXXX
X1.1 X Family of VehiclesX1.1.1 X Variant AX1.1.1.1 X Variant A Vehicle Integration, Assembly, Test and CheckoutX1.1.1.2 X Hull/Frame/Body/CabX1.1.1.3 X System SurvivabilityX1.1.1.4 X Turret AssemblyX1.1.1.5 X Suspension/SteeringX1.1.1.6 X Vehicle ElectronicsX1.1.1.7 X Power Package/Drive TrainX1.1.1.8 X Auxiliary Automotive
1.0 Ground Vehicle System X
11. WBS ELEMENT CODE
c. DD 1921-1(FCHR)
13. REPORTS REQUIRED(X if applicable)
DD 1921-3 (CBDR): DD 1921-1 / 1921-5 EAC:
a. PROGRAM/CONTRACT/
SUBCONTRACT
b. CONTRACT/SUBCONTRACT
a. CWBSDICTIONARY
g. SRDRFORMATS
h. IPMRFORMAT 1b. DD 1921
(CDSR)
12.WBS REPORTING ELEMENTS
X
EVM Reporting:
CCDR
f. EACd. DD 1921-2(PCR)
2015 DD Form 2794, Pg 2
FlexFile DD Form 2794, Pg 3 (Events)
FlexFile and Quantity Data Reports will be submitted together
FlexFiles and Quantity Data Reports will typically be submitted annually or at a greater frequency
e. AS OF DATE f. DUE DATE(YYYYMMDD) (YYYYMMDD)
1 Cost Hour Report, Quantity Report Annual Report #1 Interim 20121231 201303022 Cost Hour Report, Quantity Report Annual Report #2 Interim 20131231 201403023 Cost Hour Report, Quantity Report Annual Report #3 Final 20141231 20150302
COST AND SOFTWARE DATA REPORTING PLAN
14. CSDR SUBMISSION EVENTS
d.REPORT CYCLE
a.EVENT ID
b.DATA REPORT(S)
c.SUBMISSION EVENT NAME
17
DD 2794 (CSDR Plan) ComparisonPlanning Process
e. AS OF DATE f. DUE DATE(YYYYMMDD) (YYYYMMDD)
1 CWBS Dictionary CWBS Dictionary Initial 20121231 201303022 1921, 1921-1 LRIP 1 Report #1 Interim 20121231 201303023 1921, 1921-2 LRIP 2 Report #1 Interim 20131231 201403024 1921, 1921-3 LRIP 1 Report #2 Interim 20131231 201403025 1921, 1921-4 LRIP 2 Report #2 Interim 20131231 201403026 1921, 1921-5 LRIP 1 Report #3 Final 20141231 201503027 1921, 1921-6 LRIP 2 Report #3 Final 20141231 20150302
14. CSDR SUBMISSION DATES
c.EVENT
a.SUBMISSION
b.FORM(S)
d.REPORT TYPE
If the CWIPT is requiring FlexFiles, the Scope Def page is required
Indicate the Order/Lots and End Items that the contractor will be tagging the reported dollars and hours to
Require Unit Reporting in box 18c if the CWIPT required unit cost reporting, similar to the 1921-2 requirement
Indicate that Unit Reporting is required in the FlexFile instead of a 1921-2
See the implementation guide for more information regarding these two fields
FlexFile DD Form 2794, Pg 5 Supp. (Scope Def)
a. ID c. PHASE/MILESTONE1 C-LRIP2 C-LRIP
a. ID12
a. ORDER/LOT ID b. END ITEM ID c. UNIT REPORTING (X if applicable)
d. SEQUENCING (X if applicable)
1 1 X
1 2 X
2 1 X
2 2 X
DRAFT DD FORM 2794 (SUPPLEMENT), INTRA-CONTRACT SCOPE, JANUARY 2019
LRIP 2
COST AND SOFTWARE DATA REPORTING PLAN
INTRA-CONTRACT SCOPE REPORTING DEFINITION
18. OPTIONAL REQUIREMENTS
16. ORDERS/LOTS
17. END ITEMS
b. NAME
b. NAME
LRIP 1
Variant AVariant B
18
DD 2794 (CSDR Plan) ComparisonPlanning Process
• Utilizing the End Item table results in the same information as breaking out the WBS by Variant
• Dollars and hours will be tagged to the discrete Variants using the End Item data field
• Since the WBS is NOT broken out by End Item, the CWIPT needs to ensure that the definitions provided in the FlexFile have unique End Itemdetail
ExampleEnd Item and Order/Lot in the Planning Process
19
• Utilizing the Order/Lot table in the FlexFile plan results in the same data as requiring a submission, for example, per LRIP (same applies to all Purchase Orders, including Delivery Orders)
• Dollars and hours will be tagged to the discrete LRIPs using the Order/Lot data field
• Since the WBS definitions are part of the FlexFile DID, there is no need to require it on the FlexFile plan
ExampleEnd Item and Order/Lot in the Planning Process
20
21
Approved Quantity Data Report RequirementsQuantity Data Report
Data Group B
Government Furnished EquipmentWBS Code/Level/NameOrder/LotEnd Item
Data Group A
Report MetadataApproved Plan NumberSubmission EventPeriod of PerformanceReporting OrganizationAs of DateDate Preparedmore in the DID…
Data Group C
Quantity at CompletionDelivered Quantity At CompletionInternal Quantity At CompletionCo-production or Concurrent Quantity At CompletionGovernment Furnished Equipment At CompletionRemarks
Data Group E
Sequencing (as required by Plan)First Unit NumberLast Unit NumberIs Internal
Data Group D
Assessed Quantity to DateQuantity Completed To DateQuantity In ProcessRemarks
Legacy Element
The Quantity Report ties the necessary quantity information to the FlexFile:
Units to date should reflect an actual count of physically completed units
Allow sequencing quantities to be optional through Planning process for each End-Item as not all End Items may require sequencing (e.g., Kits)
Sequencing was allowed for lower level WBS elements in legacy 1921-2, but FlexFile does not sequence WBS elements (only End Items)
To Date and In Process to be defined by contractor in the Remarks section
Since the Quantity Data Report is a separate requirement, it can be explicitly planned for as part of the CSDR Plan
• The CWIPT must request which WBS elements they expect to receive quantity information for
• Quantities at completion will then be reported for the combinations of applicable WBS elements, Order/Lot tags, and End Item tags
The FlexFile and Quantity Data Report must be submitted as part of the same submission event
If it is determined by the CWIPT that there is not value in asking for quantity data, then the Quantity Data Report does not need to be required
When deciding what quantity information to require, an analyst should consider…
1. the unique combinations of WBS element, Order/Lot tag, and End Item tag
2. What the quantity value would represent (i.e., would the value be standardized)
Note: The guidance above is only applicable for quantities at completion. Quantities in process and completed to date are only reported for the unique combinations of WBS element and Order/Lot tag
Planning ConsiderationsQuantity Data Report
22
Scenario:• Two delivery orders providing complete aircraft
systems to the government • The Order/Lot tags will be DO1 and DO2• The total system has two variants • The End Item tags will be VarA and VarB
Quantity Report: • Requirement should be checked off for the
applicable HW subsystems in addition to 1.0 to ensure sufficient quantities are reported
• If complete systems are not being delivered, then checking off 1.0 may be misleading since the number reported would comprise two or more different subsystems (i.e., not standardized)
A B C D
1
2Order or Lot ID End Item ID WBS Element ID
Delivered QuantityAt Completion
3 DO1 VarA 1.0 - Aircraft System 104 DO1 VarB 1.0 - Aircraft System 105 DO2 VarA 1.0 - Aircraft System 156 DO2 VarB 1.0 - Aircraft System 157 DO1 VarA 1.2.3 - Propulsion 208 DO1 VarB 1.2.3 - Propulsion 209 DO2 VarA 1.2.3 - Propulsion 30
10 DO2 VarB 1.2.3 - Propulsion 30
Quantities At Completion
Would want to know the relationship between the total system and certain subsystems (e.g., an aircraft comprises two propulsion systems)
ExampleQuantity Data Report
23
FlexFile Submission Options Submission and Validation
Contractor submits the FlexFile and Quantity Data Report in their own format, so long as it adheres to the DID and approved CSDR Plan
Contractor submits the FlexFile and Quantity Data Report utilizing an Excel template that mirrors the File Format Specifications (FFS)*
Contractor submits the FlexFile and Quantity Data Report in the data model according to the File Format Specifications (FFS)
Contractor has three options to submit the data in….
The following documents provide additional details regarding the submission mechanisms and processes
FlexFile and Quantity Data Report DIDs Implementation Guide Date Exchange Instructions (DEI) File Format Specifications (FFS) Excel-Compatible File Guidance New DD Form 2794 Format
All documents can be found at…https://cade.osd.mil/policy/flexfile
*Same options apply to the Quantity Data Report, except there is only a one part template, as opposed to three.
24
Contractor is ready to submit
Finalized*
SR Validation
*Unless another iteration is necessary
Ingested in Submit Review Data Gymnastics
Contractor submits report regardless of file type and receives receipt of submission
CWIPT can provide feedback at any point after the contractor submits
Submission will follow the normal workflow if submitted using the JSON Data Model or Three Part Template
If the file is submitted in Contractor Format, then additional time will be allotted to ensure that...o File is compliant with the DID and approved CSDR Plano File can be organized into the JSON Data Model
CWIPT will receive notification from DCARC once the contractor formatted file is organized in the JSON Data Model
DCARC Only
File type submitted Data Gymnastics
cPet or SR Conversion
SR Validation
CWIPT Review
JSON Data Model X X
Three Part Template X X X
Contractor Format X X X X
actions performed
WorkflowSubmission and Validation
cPet or SR Conversion
Contractor uploads file
25
What will be available for the analyst? Submission and Validation
FlexFile Pivot ExportFlatfile of the FlexFile actual dollars and hours according to Data Group E
FlexFile Template ExportExcel version of the data model structure outlined by the FFS
Formatted and Flat File 1921Equivalent of the 1921 DD Form and 1921 flatfile
JSON Data ModelAccording to the FFS
Contractor Submitted Files*Three Part Template, Contractor Format, or similar structure
Validation Error ReportDocument used to communicate CWIPT feedback to the contractor
DCARC DocumentationDescription of how DCARC interpreted Contractor Format submission
* if submitted as admin file with JSON Data Model 26
Data and Analytics RedesignCADE Data & Analytics Overview
• A new design for the Data and Analytics home page was published on 05 Dec 2018• It is intended to better support two primary modes of accessing data
• Browse Data Across Programs: Aggregate data from multiple Tasks/Contracts/Programs
• Think “analysis-ready flat files”
• Data by Program: Drill-down by Program, Contract, and Task• Think “standard reporting formats”
The Artist Formerly Known As Cross-Program Query has been appropriately
renamed
27
Multiple CSDRs – Flexible SearchCADE Data & Analytics Overview
• The Browse CSDR Submissions function provides a more flexible “DACIMS-like” search/browse
• Simultaneously locate and download multiple CSDRs• Works with any mix of Contractor Cost Data Reports
(CCDRs) and Software Resources Data Reports (SRDRs)
• Access to all contract-specific 1921-series forms• CDSR (1921), FCHR (1921-1), PCR (1921-2),
Sustainment FCHR (1921-5)• Includes FlexFiles!
• CCDRs are available as both “formatted” and flat file downloads
28
Choose Browse CSDR Submissions from the Data and Analytics home page…
…or from the Data menu
Browse CSDR Submissions DetailsCADE Data & Analytics Overview
Apply filters to narrow down search, including Report Type
29
Use Report Type to select CCDR or SRDR…
Running tally of Reports that match
filter criteria
Specify whether to include non-flat-file-exportable reports
…then use Report Type column header to
isolate specific types (e.g., FlexFile, SRDR
Initial)
30
All documents can be found athttps://cade.osd.mil/policy/flexfile/
FlexFile and Quantity Data Report DIDs Implementation Guide Date Exchange Instructions (DEI) File Format Specifications (FFS) New DD Form 2794 Format Draft CDRL Language
See https://cade.osd.mil/support for training material and information on upcoming training events
CDSG DirectorKelly [email protected](703) 614-5397
DCARC LeadBrian [email protected](571) 372-4259
Training & Outreach LeadTorri [email protected](571) 372-4270
FlexFile LeadMarc [email protected](703) 697-0362
Points of Contact
Important Documents and POCsFlexFile 101