Attachment 0005 DD2794 Sustainment CSDR Standard Plan 23-R-0075 PRID 2022H018.xlsx

DD Form 2794, Pg 1 (METADATA)

PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.

Aircraft Systems

5. LAST APPROVED PLAN DATE (YYYYMMDD)

5300 Martin Road Redstone Arsenal, AL 35898

10b. APPROVED PLAN REVISION NUMBER

DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE

mailto:erika.d.southward.civ@army.mil DD Form 2794, Pg 2 (REPORTING)

MAINT. &

REPAIR

PARTS

QUANTITY

Subtotal Cost X X

Reporting Contractor Profit/Loss or Fee X X

DD Form 2794, Pg 3 (EVENTS)

DD Form 2794, Pg 4 (REMARKS)

FAC vs EAC

The checkmarks for EAC/FAC in column 12e at the WBS level shall be reported as "Forecast at Completion" (FAC). The Forecast At Completion (FAC) required here is not subject to the standards established in ANSI/EIA-748 guideline #27 (Estimate at Complete); therefore, the FAC does not need to be, but may be, derived from Industry Earned Value Management (EVM) processes.

NON-RECURRING/RECURRING DEFINITIONS

Recurring and Non-Recurring will be segregated according to the definitions in the DID.

COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT DIFFERENCES

Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable.

1921-3 CONTRACTOR BUSINESS DATA REPORT

a. The Contractor Business Data Report is prepared by and for the business entity (e.g., business unit, segment, or site) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government.

b. Reports are submitted annually at the end of the contractor's fiscal year.

c. Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA. If the document applies to more than three future years, attach additional future year sheets as required. In the absence of these documents, estimates should be provided for three future years.

d. The existing 1921-3 requires strictly formatted data and necessitates mappings to a government standard, the new DRAFT 1921-3 may be submitted in the contractor’s own format and according to the contractor’s own rate structure, so long as it meets the data requirements in the DRAFT 1921-3 Data Item Description DI-FNCL-81765.

END ITEMS/ORDER LOTS SCOPE IDIQ

Block 16 Orders/Lots is meant to capture the discrete Delivery Orders/Task Orders exercised on the contract. If a Delivery Order/Task Order is exercised on the contract and the CSDR plan has not been updated, it is the Reporting Entity's responsibility to still submit the dollars and hours in the FlexFile tagged to the appropriate Delivery Orders/Task Orders. The CSDR plan will be revised accordingly to include all exercised Delivery Orders/Task Orders.

PERFORMANCE BASED LOGISTICS (PBL)

Contractor shall provide the performance metrics on contract (availability, reliability, flying hours, steaming hours, turnaround time, and parts order time) etc. as well as reporting the actual metrics achieved.

COST AND HOUR REPORT UNIT/SUBLOT REPORTING

The Reporting Entity is required to provide unit or sublot (specify) reporting for any given Order/Lot and End Item as outlined in block 18 of the DD Form 2794. If Unit Reporting is selected in item 18c (Unit Reporting), it is expected that all touch labor costs and hours that are associated with the discrete units or sublots be tagged as Touch Manufacturing or Touch Maintenance as defined in Data Group E, Item 7.

QUANTITY REPORTING

a. If the quantity for a given element differs from the quantity reported for the full system, provide a comment in the WBS Element Remarks section.

b. The Reporting Entity shall provide meaningful quantity information lower than the summary level in the remarks for WBS elements Peculiar Support Equipment, Common Support Equipment, and Initial Spares and Repair Parts, if applicable.

SRDR MAINTENANCE

Software Releases are meant to capture the technical information and effort associated with each software release. If a release is identified/definted on the contract and the CSDR plan has not been updated, it is the Reporting Entity's responsibility to submit the technical data, the dollars, and the hours in the SRDR by the appropriate Release(s). The CSDR plan will be revised accordingly to include any identified Releases.

CSCIs

For Software Release and CSCI WBS Element Names identified in Item 11d. as Subcomponent Release 1..n or Subcomponent Release 1..n CSCI 1..n, the Reporting Entity must specify the specific releases and associated CSCIs at the post award meeting in order to revise the CSDR Plan to reflect the Reporting Entity’s actual releases and associated CSCIs.

FINAL COST REPORT

Final Cost Report to be submitted when final end item has been delivered and accepted by the government (e.g., as evidenced by a completed DD 250) and 95% or more of total costs for each Order/Lot (see Block 16) and each End Item (see Block 17) has been incurred.

SUSTAINMENT

a. Reporting Entity shall provide the following Quantity information in the Remarks section of the Cost and Hour Report: number of systems supported by this contract, and number of repairs performed. The Reporting Entity must state the nominal capacity planned for each Delivery Order (e.g., the # of repairs, # of overhauls, # of flight hours, etc.) identified in the plan. This requirement is intended to capture what services are being bought with each effort.

b. For Element 1.6 Installation and Personnel Support, the quantity listed should reflect the number of sites/bases/installations.

COVID-19 Remarks:

The Reporting Entity shall provide a description of the type and timing of all impacts to program schedule, incurred actual costs, forecasted at complete costs, in process quantities, and delivered quantities, which are directly attributable to the COVID-19 pandemic.

Per the DIDs, note any relevant information that could be used in the interpretation of the data. Provide general or, if available, quantifiable contract impacts within the Summary Remarks. Provide impacts to specific WBS Elements or Functional Elements within the Remarks by DD FORM 2794 WBS Element. Provide impacts to the business unit within the Remarks of each 1921-3 submission. Organize impacts under a heading in the remarks that refers to “COVID-19 impacts”, or similar language, that segments this information from the rest of the remarks.

If applicable, the Reporting Entity shall provide an explanation of any new charge codes, work packages, control accounts, pricing categories, or other methods explicitly utilized to capture impacts of COVID-19.

If there are no impacts to report, then report there are no impacts in the Summary Remarks of each FlexFile and the Remarks of each 1921-3 submission.

Additional Data Fields #1-#12 (FlexFile): If applicable, the Reporting Entity shall utilize a “Tag” or the “Additional Data Field” referenced in Section B of the FlexFile DID (DI-FNCL-82162) to identify COVID-19 related data.

SOFTWARE RESOURCE DATA REPORT (SRDR)

The Reporting Entity shall provide a description of the type and timing of all impacts to program schedule and software effort (whether software development or maintenance), which are directly attributable to the COVID-19 pandemic.

Provide general effort impacts within the Effort Comments (Item 3.4.3 of the SRDR Development DID or Item 3.4.1.5 of the SRDR Maintenance DID). Provide release level impacts within the Release-Level Comments or Comments of the SRDR Development or Maintenance form respectively (Item 3.3.1.13 of the SRDR Development DID or Item 3.3.1.14 of the SRDR Maintenance DID). Organize impacts under a heading in the remarks that refers to “COVID-19 impacts”, or similar language, that segments this information from the rest of the remarks.

DRAFT DD FORM 2794 (PAGE 4), REMARKS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE

DD Form 2794, Pg 5 (SCOPE DEF)

(X if applicable)

DD Form 2794, Pg 7 (SRDR MX)