TMIP-J Attachment 7 DD2794 CSDR Standard Plan.xls
DoD Form XLS spreadsheet 120 KB Posted
- Solicitation number
- HT003822R0001
- Issued by
-
Defense Health Agency
About this file
This document package includes a cost and software data reporting (CSDR) plan and related federal contract opportunity solicitation. The CSDR plan outlines reporting requirements for the Theater Medical Information Program Joint sustainment contract, including work breakdown structure elements, submission events, and technical data parameters. Key products and services under the single-award ID/IQ contract include program management, systems engineering, help desk support, data cleansing, IT infrastructure maintenance, hardware and software refresh, cybersecurity management, user training, system improvements, and facilities. Annual and final reporting will be conducted over the multiple-year ordering period using FlexFile and DD Form 1921 formats. Defense Health Agency Contracting Activity will issue the solicitation for the Theater Medical Information Program Joint sustainment and retirement. Responses are due by the dates specified in the solicitation and reporting plan.
View the file
Other versions and copies of DD Form 2794
Show all 20
Who attaches DD Form 2794
Other files
Show all 20
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD Form 2794, Pg 1 (METADATA)
| COST AND SOFTWARE DATA REPORTING PLAN | OMB No. 0704-0188 |
| 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 | ||
| Joint Operational Medicine Information Systems (JOMIS) | ||
| 1b. PHASE/MILESTONE (check all that apply) | ||
| Pre-A | ||
| A | ||
| B | ||
| C-LRIP | ||
| C-FRP | ||
| X | O&S | |
| 1c. PRIME MISSION PRODUCT | ||
| TMIP - J | ||
| 1d. ACQUISITION CATEGORY (ACAT) | ||
| Pre-ACAT | ||
| ACAT I (MDAP) | ||
| ACAT IA (MAIS) | ||
| ACAT II | ||
| ACAT III | ||
| X | Other | |
| 2. COMMODITY TYPE | ||
| Information System/Defense Business System | ||
| 3. PLAN ITERATION TYPE | ||
| X | INITIAL | |
| REVISION | ||
| 4. CURRENT SUBMISSION DATE (YYYYMMDD) | ||
| TBD | ||
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) | ||
| TBD | ||
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | ||
| Christopher Metz | ||
| 6b. ADDRESS (Include ZIP Code) | ||
| 1700 North Moore Street Suite 2300 Arlington, VA 22209 | ||
| 6c. TELEPHONE NUMBER (Include Area Code) | ||
| (571) 225-4266 | ||
| 6d. E-MAIL ADDRESS | ||
| Christopher.R.Metz2.civ@mail.mil | ||
| 7. PLAN TYPE | ||
| GOVERNMENT | ||
| X | CONTRACT (PRIME) | |
| CONTRACT (SUB) | ||
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | ||
| Joint Operational Medicine Information Systems (JOMIS) | ||
| 9a. CONTRACTOR NAME/ADDRESS | ||
| i. REPORTING ORGANIZATION NAME | ||
| TBD | ||
| ii. DIVISION NAME | ||
| TBD | ||
| iii. LOCATION | ||
| TBD | ||
| iv. CONTRACTOR BUSINESS DATA REPORT (CBDR 1921-3) REQUIREMENT: | ||
| X | CBDR REQUIRED FOR THIS ORGANIZATION | |
| 9b. CONTRACT NUMBER (List all that apply, separated by commas) | ||
| TBD | ||
| 9c. APPROPRIATION (check all that apply) | ||
| RDT&E | ||
| PROCUREMENT | ||
| X | O&M | |
| FMS | ||
| WCF | ||
| OTHER | ||
| 10a. APPROVED PLAN NUMBER | ||
| TBD | ||
| 10b. APPROVED PLAN REVISION NUMBER | ||
| TBD | ||
| 10c. APPROVED PLAN REQUIREMENTS | ||
| X | AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) | |
| X | AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only) | |
| X | TECHNICAL DATA REQUIRED | |
| 10d. COST REPORT TYPE | ||
| X | FLEXFILE | |
| LEGACY DD 1921 SERIES | ||
| DRAFT DD FORM 2794 (PAGE 1), METADATA, JANUARY 2019 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 2 (REPORTING)
| COST AND SOFTWARE DATA REPORTING PLAN | COST, SOFTWARE, & TECHNICAL DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN | |||||
| 11. WORK BREAKDOWN STRUCTURE (WBS) | 12. COST | 13. TECHNICAL DATA | ||||
| a. WBS | ||||||
| CODE | b. WBS | |||||
| LEVEL | c. WBS ELEMENT NAME | a. ACTUALS TO | ||||
| DATE (ATD) | b. LEGACY | |||||
| 1921-1 | c. LEGACY | |||||
| 1921-2 | d. LEGACY | |||||
| 1921-5 | e. EAC/FAC | |||||
| (See item 10d) | a. QUANTITY | b. SRDR | ||||
| FORMATS | c. |
MAINT. &
REPAIR
PARTS
| i. QUANTITY | ||
| DATA | ii. GFE |
QUANTITY
| 2.0 | 1 | Information Systems (IS)/Defense Business Systems (DBS) (Sustainment) | |||
| 2.1 | 2 | Program Management | X | X | |
| 2.2 | 2 | Systems/Sustainment Engineering | X | X | X |
| 2.3 | 2 | Change Management | X | X | |
| 2.4 | 2 | Help Desk | X | X | |
| 2.5 | 2 | Data Cleansing/Data Maintenance | X | X | X |
| 2.6 | 2 | System/Database Administration | X | X | |
| 2.7 | 2 | IT Infrastructure/Network Maintenance Support | X | ||
| 2.7.1 | 3 | IT Infrastructure Hardware/Equipment Maintenance | X | X | |
| 2.7.2 | 3 | IT Infrastructure Software License Support Services | X | X | |
| 2.7.3 | 3 | IT Infrastructure Management | X | X | X |
| 2.7.4 | 3 | Other IT Infrastructure Support 1...n (Specify) | X | X | X |
| 2.8 | 2 | Operational Hardware Refresh/Upgrade | |||
| 2.8.1 | 3 | End-User Equipment | X | X | |
| 2.8.2 | 3 | Cybersecurity Equipment | X | X | |
| 2.8.3 | 3 | IT Infrastructure and Enterprise Services Equipment | X | X | |
| 2.8.4 | 3 | Other (Specify) | X | X | |
| 2.9 | 2 | Operational Software License Refresh/Update | |||
| 2.9.1 | 3 | End-User Software License | X | X | |
| 2.9.2 | 3 | Cybersecurity Software Licenses/Services | X | X | |
| 2.9.3 | 3 | IT Infrastructure and Enterprise Software Licenses/Services | X | X | |
| 2.9.4 | 3 | Other (Specify) | X | X | |
| 2.10 | 2 | Cybersecurity Maintenance Management | X | ||
| 2.10.1 | 3 | Cybersecurity Compliance Operations and Tracking | X | X | X |
| 2.10.2 | 3 | Follow-on Cybersecurity Test and Evaluation | X | X | X |
| 2.10.3 | 3 | Cybersecurity and IT Certification and Accreditation | X | X | X |
| 2.11 | 2 | Follow-on User Training | X | X | X |
| 2.12 | 2 | System Independent Verification and Validation | X | X | X |
| 2.13 | 2 | Continuing System Improvements | X | ||
| 2.13.1 | 3 | Operational Hardware Modification | |||
| 2.13.1.1 | 4 | Mod Kit Hardware Development | X | X | |
| 2.13.1.2 | 4 | Mod Kit Hardware Procurement | X | X | |
| 2.13.1.3 | 4 | Mod Kit Hardware Installation | X | X | |
| 2.13.2 | 3 | Software Release Modification/Enhancement 1...n (Specify) | X | ||
| 2.13.2.1 | 4 | Modifications/Enhancements | X | X | X |
| 2.13.2.2 | 4 | Routine Fixes and Deficiency Correction | X | X | X |
| 2.13.2.3 | 4 | Installation/Test | X | X | X |
| 2.13.2.4 | 4 | IAVAs | X | X | X |
| 2.14 | 2 | AW/Safety/Networthiness Certification | X | X | |
| 2.15 | 2 | Facilities | X | X | |
| Subtotal Cost | X | X | |||
| Reporting Contractor G&A | X | X | |||
| Reporting Contractor Undistributed Budget | X | X | |||
| Reporting Contractor Management Reserve | X | X | |||
| Reporting Contractor FCCM | X | X | |||
| Total Cost | X | X | |||
| Reporting Contractor Profit/Loss or Fee | X | X | |||
| Total Price | X | X | |||
| DRAFT DD FORM 2794 (PAGE 2), REPORTING, JANUARY 2019 |
DD Form 2794, Pg 3 (EVENTS)
| COST AND SOFTWARE DATA REPORTING PLAN | |||||||
| 14. CSDR SUBMISSION EVENTS | |||||||
| a. | |||||||
| EVENT ID | b. | ||||||
| DATA REPORT(S) | c. | ||||||
| SUBMISSION EVENT NAME | d. | ||||||
| REPORT CYCLE | e. AS OF DATE | f. DUE DATE | |||||
| (YYYYMMDD) | (YYYYMMDD) | ||||||
| 1 | Cost and Hour Report (FlexFile) | Cost and Hour Report (FlexFile) - Contract Award (plus 12 months) | Initial | 20221101 | 20230101 | ||
| 2 | SRDR Maintenance | SRDR Maintenance - Contract Award (plus 12 months) | Initial | 20221101 | 20230101 | ||
| 3 | Technical Data Report | Technical Data Report - Contract Award (plus 12 months) | Initial | 20221101 | 20230101 | ||
| 4 | CWBS Dictionary | CWBS Dictionary - Contract Award (plus 12 months) | Initial | 20221101 | 20230101 | ||
| 5 | Cost and Hour Report (FlexFile) | Cost and Hour Report (FlexFile) - Annual Report - OY1 | Interim | 20231101 | 20240101 | ||
| 6 | SRDR Maintenance | SRDR Maintenance - Annual Report - OY1 | Interim | 20231101 | 20240101 | ||
| 7 | Technical Data Report | Technical Data Report - Annual Report - OY1 | Interim | 20231101 | 20240101 | ||
| 8 | CWBS Dictionary | CWBS Dictionary - Annual Report - OY1 | Interim | 20231101 | 20240101 | ||
| 9 | Cost and Hour Report (FlexFile) | Cost and Hour Report (FlexFile) - Annual Report - OY2 | Interim | 20241101 | 20250101 | ||
| 10 | SRDR Maintenance | SRDR Maintenance - Annual Report - OY2 | Interim | 20241101 | 20250101 | ||
| 11 | Technical Data Report | Technical Data Report - Annual Report - OY2 | Interim | 20241101 | 20250101 | ||
| 12 | CWBS Dictionary | CWBS Dictionary - Annual Report - OY2 | Interim | 20241101 | 20250101 | ||
| 13 | Cost and Hour Report (FlexFile) | Cost and Hour Report (FlexFile) - Annual Report - OY3 | Interim | 20251101 | 20260101 | ||
| 14 | SRDR Maintenance | SRDR Maintenance - Annual Report - OY3 | Interim | 20251101 | 20260101 | ||
| 15 | Technical Data Report | Technical Data Report - Annual Report - OY3 | Interim | 20251101 | 20260101 | ||
| 16 | CWBS Dictionary | CWBS Dictionary - Annual Report - OY3 | Interim | 20251101 | 20260101 | ||
| 17 | Cost and Hour Report (FlexFile) | Just in Time Cost and Hour Report (FlexFile) | Interim | 20261101 | 20270101 | ||
| 18 | SRDR Maintenance | Just in Time SRDR Maintenance | Interim | 20261101 | 20270101 | ||
| 19 | Technical Data Report | Just in Time Technical Data Report | Interim | 20261101 | 20270101 | ||
| 20 | CWBS Dictionary | Just in Time CWBS Dictionary | Interim | 20261101 | 20270101 | ||
| 21 | Cost and Hour Report (FlexFile) | Cost and Hour Report (FlexFile) - Contract Completion | Final | 20261101 | 20270101 | ||
| 22 | SRDR Maintenance | SRDR Maintenance - Contract Completion | Final | 20261101 | 20270101 | ||
| 23 | Technical Data Report | Technical Data Report - Contract Completion | Final | 20261101 | 20270101 | ||
| 24 | CWBS Dictionary | CWBS Dictionary - Contract Completion | Final | 20261101 | 20270101 | ||
| DRAFT DD FORM 2794 (PAGE 3), SUBMISSION EVENTS, JANUARY 2019 | PREVIOUS EDITION IS OBSOLETE |
DD Form 2794, Pg 4 (REMARKS)
| COST AND SOFTWARE DATA REPORTING PLAN |
| 15. REMARKS |
| The contractor must report costs on all CLINs associated with the (Insert contract name) contract including Over and Above, Advance Procurement, Long Lead Materials, Multiyear Procurement, Inter-Division or Inter-Company Work Orders (IWOs), Foreign Military Sales (FMS), Warranty, etc. Costs should not be omitted based on contract CLIN structure or definition. |
| INITIAL REPORT |
| Other than the Resource Distribution Table, submission events associated with this CSDR Plan are classified as either "Initial", "Interim", or "Final" submissions as identified in block 14.d of this CSDR plan. |
| i. Submission events marked "Initial" shall report the Contractor's total anticipated contract cost and resulting price using the maximum allowable contractor quantities, hours, or options (as applicable). For sealed bid contracts (i.e., contracts awarded under FAR Part 14) the reported FAC/EAC shall equal the value of the Contractor's sealed bid (using the maximum allowable contractor quantities, hours, or options (as applicable)). For negotiated contracts (i.e., contracts award under FAR Part 15) the reported FAC/EAC shall be equal in overall value to the Contractor's best and final offer (and consistent in distribution with any supporting cost and pricing data (e.g., basis of estimates, engineering build-ups) (using the maximum allowable contractor quantities, hours, or options (as applicable)). For all other contracts, the reported FAC/EAC shall be equal in overall value to the Contractor's final proposal and consistent in distribution with any supporting data provided to substantiate the contract's value, reasonableness, and/or realism (e.g., basis of estimates, engineering build-ups) (using the maximum allowable contractor quantities, hours, or options (as applicable)). No ATD costs are anticipated to reported on an "Initial" submission except for any certified precontract costs incurred prior to or on the date of contract award. |
| ii. Interim" report submissions are any report that is not either an "Initial" or "Final" report. Reported ATD, EAC/FAC, and quantities on "Interim" submissions shall be prepared reflecting only the value of work, quantities, hours, or options (as applicable) awarded on the report's "As Of Date" (do not include costs for anticipated but not awarded scopes of work, quantities, hours, or options). |
| iii. Reported ATD, EAC/FAC, and quantities on "Final" submissions shall be prepared reflecting the value of work, quantities, hours, and options (as applicable) anticipated to be awarded on a contract and meet the conditions listed in block 15.c.i.4. |
| 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.
| 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 Costs required for all levels: |
| Recurring costs. Repetitive elements of development, investment or sustainment costs that may vary with the quantity being produced or maintained, irrespective of system life cycle phase and appropriation. Recurring cost categories include procurement, and production and maintenance activities; acceptance testing; maintenance and support equipment, training, and data; test articles built to an operational configuration; and certain elements of systems engineering and program management. |
| Examples of Prime Mission Product activities include repetitive costs incurred when building prototype, test systems, or production units to an operational configuration. Examples of Prime Mission Product Hardware activities include Fabrication and assembly of partial/full prototype, test, or production units whether for customer or contractor use; Raw material, purchased parts, equipment associated with the fabrication and assembly of partial/full prototype or test units whether for customer or contractor use; Touch labor, integration and assembly, installation and check out; Engineering support for production unit fabrication, assembly and check out. |
| Examples of Prime Mission Product Software activities include Procurement of stand-alone or bundled COTS software licenses used in an operational system and installation and checkout of developed software into production units. Examples of Systems Engineering activities include Sustaining engineering, logistics support, planning, organizing, monitoring and reporting activities, document maintenance. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of production unit fabrication, assembly and check out; meetings & efforts in support of supplier, manufacturing & production activities. |
| Nonrecurring costs. Non-repetitive elements of development, investment or sustainment costs that generally do not vary with the quantity being produced or maintained, irrespective of system life cycle phase and the appropriation. Nonrecurring cost categories include product design and development (PD&D) activities, including those for modifications; system test and evaluation (ST&E) including ST&E for modifications; tooling; pre-production or pre-maintenance activities; design and development of support equipment, training, and data; and certain elements of systems engineering and program management. |
| Examples of Prime Mission Product PD&D activities are: Requirements definition, engineering design, analysis & development; Redesign, rework & retest due to design flaws & first time corrective actions; test articles built for testing purposes only (i.e., units that are not production-representative) such as wind tunnel models, and bench and coupon test articles; structural development, static, fatigue, software, and ballistics testing; stress analysis; flight, ground, or sea testing of system properties; redesign as a result of testing; and retesting efforts; All configuration, quality, and data management efforts supporting release activity for first article configuration, delivery & certification; System safety plan, manuals, tech services, & maintenance manual development in support of first article delivery. |
| Examples of hardware design and development activities include material, purchased parts and labor associated with engineering models, operational models, bench, lab articles or partially built units (i.e. units that are not production representative), tooling, and ground support equipment for qualification, structural, static, fatigue or stress testing, and refurbishment of test units; and engineering support including manufacturing engineering, quality engineering, and tool engineering for development unit fabrication, assembly & tests. |
| Examples of software design and development activities include design and development of all software; delivered operational software and software developed to correct deficiencies and add capabilities; Initial integration of COTS and GOTS products into operational configuration; Support for HW-SW integration and test, system level testing; initial integration of COTS and GOTS products into operational configuration; and commercial software licenses for development facilities. System Engineering, Program Management, and Data activities occur throughout the system life cycle and are supportive in nature; as such, these costs take on the characteristics of the underlying activities being performed. |
| Examples of Systems Engineering activities include installation plans or quality inspection plans; requirements definition, allocation and flow-down; creation of specification and Interface Control Documents (ICDs); design and implementation of system security; top level design trade-offs; analyses, studies, and simulations for system performance and effectiveness, reliability, availability, maintainability or survivability; internal & external design review, IPT coordination & integration meetings; Certification & Control documentation; and supplier selection & coordination. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of development, design & testing efforts. |
| Examples of System Test and Evaluation activities include development of test plans/procedures; subsystem and system level test and integration for developmental articles; test equipment in support of development including for static & fatigue testing, test stands, wind tunnel models, stress analysis, ballistics testing, flight, ground or sea testing of system, redesign from testing, retesting; System/Software Integration Laboratory (SIL) development; and analysis to support verification, validation & certification. Examples of Training activity include initial courseware development and simulator development. Examples of Initial Spares and Repair Parts activity include spare parts and material in support of the nonrecurring subsystem/system level articles. |
| Examples of Support Equipment activity include initial equipment design and test efforts, and test program sets development. Examples of Tooling activity include special test equipment, special tooling, procurement of initial & rate tooling, tool replacement (with the exact same tool) & tool modification (to accommodate product configuration changes). Examples of Operational/Site Activation activity include site planning efforts. |
| IRAD EFFORT |
| The contractor should list the major relevant IRAD projects leveraged for this development effort, provide a brief description of the cost of the projects, and provide/attach any more detailed actual cost information at the level available. |
| WBS INDEX AND DICTIONARY |
| The WBS Dictionary is a living document and must match the technical content, cost content, and work content of each end item (see Block 17) for all WBS elements for each Cost and Hour (FlexFile) submission. The dictionary shall contain a disclosure statement detailing any differences between the CSDR reporting methodology and the reporting entity's Cost Accounting Standards. The dictionary shall include a section detailing how parts are procured under this contract and any limitations of the parts procurement cost data or allocation of cost data for the WBS element. |
The reporting entity must maintain and update the WBS Dictionary throughout the life of the contract, IAW DI-FNCL-82162, if changes to the WBS occur, the reporting entity shall annotate and track changes by adding the “As of Date” of the submitted FlexFile report and indicate the changes to the WBS Index and Dictionary Definitions.
For WBS elements identified in block 11 of the CSDR plan that is not within the contract's scope of work, the reporting entity shall report in the dictionary that “This CSDR WBS element is not associated with this contract’s scope of work”, and zero costs will be associated for ATD and FAC for these WBS elements.
| 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. |
| 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 |
| 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 DEVELOPMENT- RELEASES AND COMPUTER SOFTWARE CONFIGURATION ITEMS (CSCIs) |
| For Software Release and CSCI WBS Element Names identified in Item 11c. as Subcomponent Release 1..n or Subcomponent 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. See the SRDR Implementation Guide for more detail https://cade.osd.mil/policy/srdr |
| 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. |
| CSDR READINESS REVIEW (CSDR-RR) also known as Post Award Conference (PAC) |
| The Reporting Entity shall attend and participate in a CSDR Readiness Review meeting (also known as the Post award CSDR conference) which will be held with the Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoDM 5000.04 (CSDR Manual). During this meeting, the CWIPT and contractor will review the Reporting Entity's process for data collection and reporting to ensure it satisfies the guidelines outlined in the DoDM 5000.04, CSDR Manual, the approved CSDR plan reporting requirement, and the Resource Distribution Table. The Reporting Entity shall demonstrate how costs will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations; describe how recurring vs. nonrecurring costs will be segregated; demonstrate how the data from its accounting system will be mapped into the reporting categories in the approved CSDR plan. The Reporting Entity shall present the methodologies used for mapping internal cost accounts to the agreed upon WBS, specifically illustrating how individual WBS elements and standard functional categories in the FlexFile (functional data elements in the 1921 series) codes will be populated. The review shall include any reporting issue corrections and identify proposed changes to the approved CSDR Plan as necessary. |
| RESOURCE DISTRIBUTION TABLE (RDT) |
| The Reporting Entity is instructed to provide a Resource Distribution Table upon contract award, which identifies the value and work assigned to the Reporting Entity and its subcontractors. The Reporting Entity shall provide an updated RDT when additional quantities/scope are added to the contract to ensure that no major sub-contract(s) breach the direct CSDR reporting threshold specified in DODI 5000.73 and DoDM 5000.04-M-1. |
| PERIOD OF PERFORMANCE (POP) |
| If contract Period of Performance is extended, the contractor shall submit an additional cost report for each additional year of extension. The final report will be moved to the revised end of the Period of Performance. |
| 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.
DRAFT DD FORM 2794 (PAGE 4), REMARKS, JANUARY 2019 PREVIOUS EDITION IS OBSOLETE
DD Form 2794, Pg 5 (SCOPE DEF)
| COST AND SOFTWARE DATA REPORTING PLAN | |||||
| INTRA-CONTRACT SCOPE REPORTING DEFINITION | |||||
| 16. ORDERS/LOTS | |||||
| a. ID | b. NAME | c. PHASE/MILESTONE | |||
| TO1 | TMDS | O&S | |||
| TO2 | MSAT | O&S | |||
| TO3 | Clinical Components | O&S | |||
| TO4 | Program Management | O&S | |||
| TO5 | Integration and Sustainment | O&S | |||
| 17. END ITEMS | |||||
| a. ID | b. NAME | ||||
| SBY1 | Sustainment BY1 | ||||
| SOY1 | Sustainment OY1 | ||||
| SOY2 | Sustainment OY2 | ||||
| SOY3 | Sustainment OY3 | ||||
| SOY4 | Sustainment OY4 | ||||
| 18. OPTIONAL REQUIREMENTS | |||||
| a. ORDER/LOT ID | b. END ITEM ID | c. UNIT REPORTING | |||
| (X if applicable) | d. SEQUENCING |
(X if applicable)
DRAFT DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, JANUARY 2019
DD Form 2794, Pg 7 (SRDR MX)
| COST AND SOFTWARE DATA REPORTING PLAN - SRDR MAINTENANCE | |||||||
| 23. RELEASES | |||||||
| a. ID | b. NAME | c. DATE | |||||
| 1 | Annual Releases BY1 | 20221101 | |||||
| 2 | Annual Releases OY1 | 20231101 | |||||
| 3 | Annual Releases OY2 | 20241101 | |||||
| 4 | Annual Releases OY3 | 20251101 | |||||
| 5 | Annual Releases OY4 | 20261101 | |||||
| 24. PRODUCT SIZE REPORTING ELEMENTS | |||||||
| a. CODE | b. NAME | c. RELEASE ID | |||||
| 2.2 | Systems/Sustainment Engineering | 1 | |||||
| 2.5 | Data Cleansing/Data Maintenance | 1 | |||||
| 2.7 | IT Infrastructure/Network Maintenance Support | 1 | |||||
| 2.7.3 | IT Infrastructure Management | 1 | |||||
| 2.7.4 | Other IT Infrastructure Support 1...n (Specify) | 1 | |||||
| 2.10 | Cybersecurity Maintenance Management | 1 | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | 1 | |||||
| 2.10.2 | Follow-on Cybersecurity Test and Evaluation | 1 | |||||
| 2.10.3 | Cybersecurity and IT Certification and Accreditation | 1 | |||||
| 2.11 | Follow-on User Training | 1 | |||||
| 2.12 | System Independent Verification and Validation | 1 | |||||
| 2.13 | Continuing System Improvements | 1 | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | 1 | |||||
| 2.13.2.1 | Modifications/Enhancements | 1 | |||||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | 1 | |||||
| 2.13.2.3 | Installation/Test | 1 | |||||
| 2.13.2.4 | AW/Safety/Networthiness Certification | 1 | |||||
| 2.2 | Systems/Sustainment Engineering | 2 | |||||
| 2.5 | Data Cleansing/Data Maintenance | 2 | |||||
| 2.7 | IT Infrastructure/Network Maintenance Support | 2 | |||||
| 2.7.3 | IT Infrastructure Management | 2 | |||||
| 2.7.4 | Other IT Infrastructure Support 1...n (Specify) | 2 | |||||
| 2.10 | Cybersecurity Maintenance Management | 2 | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | 2 | |||||
| 2.10.2 | Follow-on Cybersecurity Test and Evaluation | 2 | |||||
| 2.10.3 | Cybersecurity and IT Certification and Accreditation | 2 | |||||
| 2.11 | Follow-on User Training | 2 | |||||
| 2.12 | System Independent Verification and Validation | 2 | |||||
| 2.13 | Continuing System Improvements | 2 | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | 2 | |||||
| 2.13.2.1 | Modifications/Enhancements | 2 | |||||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | 2 | |||||
| 2.13.2.3 | Installation/Test | 2 | |||||
| 2.13.2.4 | AW/Safety/Networthiness Certification | 2 | |||||
| 2.2 | Systems/Sustainment Engineering | 3 | |||||
| 2.5 | Data Cleansing/Data Maintenance | 3 | |||||
| 2.7 | IT Infrastructure/Network Maintenance Support | 3 | |||||
| 2.7.3 | IT Infrastructure Management | 3 | |||||
| 2.7.4 | Other IT Infrastructure Support 1...n (Specify) | 3 | |||||
| 2.10 | Cybersecurity Maintenance Management | 3 | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | 3 | |||||
| 2.10.2 | Follow-on Cybersecurity Test and Evaluation | 3 | |||||
| 2.10.3 | Cybersecurity and IT Certification and Accreditation | 3 | |||||
| 2.11 | Follow-on User Training | 3 | |||||
| 2.12 | System Independent Verification and Validation | 3 | |||||
| 2.13 | Continuing System Improvements | 3 | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | 3 | |||||
| 2.13.2.1 | Modifications/Enhancements | 3 | |||||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | 3 | |||||
| 2.13.2.3 | Installation/Test | 3 | |||||
| 2.13.2.4 | AW/Safety/Networthiness Certification | 3 | |||||
| 2.2 | Systems/Sustainment Engineering | 4 | |||||
| 2.5 | Data Cleansing/Data Maintenance | 4 | |||||
| 2.7 | IT Infrastructure/Network Maintenance Support | 4 | |||||
| 2.7.3 | IT Infrastructure Management | 4 | |||||
| 2.7.4 | Other IT Infrastructure Support 1...n (Specify) | 4 | |||||
| 2.10 | Cybersecurity Maintenance Management | 4 | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | 4 | |||||
| 2.10.2 | Follow-on Cybersecurity Test and Evaluation | 4 | |||||
| 2.10.3 | Cybersecurity and IT Certification and Accreditation | 4 | |||||
| 2.11 | Follow-on User Training | 4 | |||||
| 2.12 | System Independent Verification and Validation | 4 | |||||
| 2.13 | Continuing System Improvements | 4 | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | 4 | |||||
| 2.13.2.1 | Modifications/Enhancements | 4 | |||||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | 4 | |||||
| 2.13.2.3 | Installation/Test | 4 | |||||
| 2.13.2.4 | AW/Safety/Networthiness Certification | 4 | |||||
| 2.2 | Systems/Sustainment Engineering | 5 | |||||
| 2.5 | Data Cleansing/Data Maintenance | 5 | |||||
| 2.7 | IT Infrastructure/Network Maintenance Support | 5 | |||||
| 2.7.3 | IT Infrastructure Management | 5 | |||||
| 2.7.4 | Other IT Infrastructure Support 1...n (Specify) | 5 | |||||
| 2.10 | Cybersecurity Maintenance Management | 5 | |||||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | 5 | |||||
| 2.10.2 | Follow-on Cybersecurity Test and Evaluation | 5 | |||||
| 2.10.3 | Cybersecurity and IT Certification and Accreditation | 5 | |||||
| 2.11 | Follow-on User Training | 5 | |||||
| 2.12 | System Independent Verification and Validation | 5 | |||||
| 2.13 | Continuing System Improvements | 5 | |||||
| 2.13.2 | Software Release Modification/Enhancement 1...n (Specify) | 5 | |||||
| 2.13.2.1 | Modifications/Enhancements | 5 | |||||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | 5 | |||||
| 2.13.2.3 | Installation/Test | 5 | |||||
| 2.13.2.4 | AW/Safety/Networthiness Certification | 5 | |||||
| 25. PRODUCT SIZE SUBMISSIONS | c. RELEASE ID: | 1 | 2 | 3 | 4 | 5 | |
| a. NUMBER | b. NAME | Included? | Included? | Included? | Included? | Included? | |
| 2 | SRDR Maintenance - Contract Award (plus 12 months) | X | |||||
| 6 | SRDR Maintenance - Annual Report - OY1 | X | X | ||||
| 10 | SRDR Maintenance - Annual Report - OY2 | X | X | X | |||
| 14 | SRDR Maintenance - Annual Report - OY3 | X | X | X | X | ||
| 18 | Just in Time SRDR Maintenance | X | X | X | X | X | |
| 21 | Cost and Hour Report (FlexFile) - Contract Completion | X | X | X | X | X | |
| DRAFT DD FORM 2794 (PAGE 7), SRDR MAINTENANCE, JANUARY 2019 |
DD Form 2794, Pg 8 (TECH RQTS)
| COST AND SOFTWARE DATA REPORTING PLAN - TECHNICAL PARAMETER REQUIREMENTS | ||||||||
| TECHNICAL PARAMETER REQUIREMENTS | ||||||||
| 26. WBS | ||||||||
| ELEMENT CODE | 27. WBS ELEMENT NAME | 28. ITEM TYPE | 29. TECHNICAL PARAMETER | |||||
| a. PARAMETER NAME | b. UNIT OF MEASURE | c. UNIT OF MEASURE QUALIFIER | d. REPEATABLE | e. REMARKS | ||||
| 2.4 | Help Desk | Help Desk | Tickets | Quantity | Tickets | |||
| 2.5 | Data Cleansing/Data Maintenance | Data Cleansing/Data Maintenance | Defects/bugs | Quantity | Defects/bugs | |||
| 2.5 | Data Cleansing/Data Maintenance | Data Cleansing/Data Maintenance | Test cases | Quantity | Test cases | |||
| 2.5 | Data Cleansing/Data Maintenance | Data Cleansing/Data Maintenance | New test cases automated | Quantity | Test cases | |||
| 2.5 | Data Cleansing/Data Maintenance | Data Cleansing/Data Maintenance | Refactors | Quantity | Refactors | |||
| 2.7.1 | IT Infrastructure Hardware/Equipment Maintenance | IT Infrastructure/Network Maintenance Support | Equipment | Quantity | Equipment | |||
| 2.7.2 | IT Infrastructure Software License Support Services | IT Infrastructure/Network Maintenance Support | Licenses | Quantity | Licenses | |||
| 2.8.1 | End-User Equipment | Operational Hardware Refresh/Upgrade | Equipment | Quantity | Equipment | |||
| 2.8.2 | Cybersecurity Equipment | Operational Hardware Refresh/Upgrade | Equipment | Quantity | Equipment | |||
| 2.8.3 | IT Infrastructure and Enterprise Services Equipment | Operational Hardware Refresh/Upgrade | Equipment | Quantity | Equipment | |||
| 2.8.4 | Other (Specify) | Operational Hardware Refresh/Upgrade | Licenses | Quantity | Licenses | |||
| 2.9.1 | End-User Software License | Operational Software License Refresh/Update | Licenses | Quantity | Licenses | |||
| 2.9.2 | Cybersecurity Software Licenses/Services | Operational Software License Refresh/Update | Licenses | Quantity | Licenses | |||
| 2.9.3 | IT Infrastructure and Enterprise Software Licenses/Services | Operational Software License Refresh/Update | Licenses | Quantity | Licenses | |||
| 2.10.1 | Cybersecurity Compliance Operations and Tracking | Cybersecurity Maintenance Management | ATOs | Quantity | ATOs | |||
| 2.10.2 | Follow-on Cybersecurity Test and Evaluation | Cybersecurity Maintenance Management | ATOs | Quantity | ATOs | |||
| 2.10.3 | Cybersecurity and IT Certification and Accreditation | Cybersecurity Maintenance Management | ATOs | Quantity | ATOs | |||
| 2.11 | Follow-on User Training | Follow-on User Training | End users | Quantity | People | |||
| 2.11 | Follow-on User Training | Follow-on User Training | Super users | Quantity | People | |||
| 2.11 | Follow-on User Training | Follow-on User Training | End users provisioned | Quantity | People | |||
| 2.11 | Follow-on User Training | Follow-on User Training | Trainers trained | Quantity | People | |||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | Continuing System Improvements | Defects/bugs | Quantity | Defects/bugs | |||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | Continuing System Improvements | Test cases | Quantity | Test cases | |||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | Continuing System Improvements | New test cases automated | Quantity | Test cases | |||
| 2.13.2.2 | Routine Fixes and Deficiency Correction | Continuing System Improvements | Refactors | Quantity | Refactors | |||
| 2.13.2.3 | Installation/Test | Continuing System Improvements | Defects/bugs | Quantity | Defects/bugs | |||
| 2.13.2.3 | Installation/Test | Continuing System Improvements | Test cases | Quantity | Test cases | |||
| 2.13.2.3 | Installation/Test | Continuing System Improvements | New test cases automated | Quantity | Test cases | |||
| 2.13.2.3 | Installation/Test | Continuing System Improvements | Refactors | Quantity | Refactors | |||
| 2.15 | Facilities | Facilities | Facilities | Quantity | Facilities |
File details come from the government source that posted it. Updated .