DRAFT CSDR Plan F100 RDN DD Form 2794.xls
DoD Form XLS spreadsheet 84 KB Posted
- Attached to
- Regional Depot Network (RDN) Re-manufacture of F100-PW-220/-220E/-229/-229EEP Series Engine Modules
- Solicitation number
- SPRTA1-23-R-0196
- Issued by
-
Defense Logistics Agency Aviation
About this file
This document is a draft Cost and Software Data Reporting (CSDR) Plan for the remanufacture of F100 engine modules for foreign military sales customers.
The plan covers a potential 10-year firm fixed price requirements contract between the Defense Logistics Agency Aviation and a contractor to remanufacture F100-PW-220/-220E/-229/-229EEP engine modules, including the inlet fan, core, fan drive turbine, high pressure turbine, and gearbox. Key details include the work breakdown structure to be used for reporting, definitions of recurring and nonrecurring costs, requirements for interim and final reporting, and schedules and formats for cost and hour reports, quantity data reports, and maintenance and repair parts reports. The plan also provides instructions for mapping costs to the work breakdown structure and segregating recurring and nonrecurring costs. Submission events are identified for contract award, biennial interim reports, and contract completion.
View the file
Other versions and copies of DD Form 2794
Show all 20
Who attaches DD Form 2794
Other files
Show all 14
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 | |
| DLA - Defense Logistics Agency | |
| 1b. PHASE/MILESTONE (check all that apply) | |
| Pre-A | |
| A | |
| B | |
| C-LRIP | |
| C-FRP | |
| X | O&S |
| 1c. PRIME MISSION PRODUCT | |
| Remanufactured Engines Modules (F100 -220/-229) for Foreign Parnter Nations (FMS) | |
| 1d. ACQUISITION CATEGORY (ACAT) | |
| Pre-ACAT | |
| ACAT I (MDAP) | |
| ACAT IA (MAIS) | |
| ACAT II | |
| ACAT III | |
| X | Other |
| 2. COMMODITY TYPE | |
| Engine Subsystems | |
| 3. PLAN ITERATION TYPE | |
| X | INITIAL |
| REVISION | |
| 4. CURRENT SUBMISSION DATE (YYYYMMDD) | |
| 20231128 | |
| 5. LAST APPROVED PLAN DATE (YYYYMMDD) | |
| 6a. GOVERNMENT PLAN POINT OF CONTACT (POC) NAME (Last, First, M.) | |
| Germony, Daniel | |
| 6b. ADDRESS (Include ZIP Code) | |
| 1800 Defense Pentagon |
BE828
Washington, DC 20301-1800
| 6c. TELEPHONE NUMBER (Include Area Code) | ||
| (703) 901-8678 | ||
| 6d. E-MAIL ADDRESS | ||
| Daniel.R.Germony.civ@mail.mil | ||
| 7. PLAN TYPE | ||
| GOVERNMENT | ||
| X | CONTRACT (PRIME) | |
| CONTRACT (SUB) | ||
| 8. PLAN GOVERNMENT PREPARING ORGANIZATION | ||
| OSD CAPE | ||
| 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 - (D-20-A-C38) | ||
| 9c. APPROPRIATION (check all that apply) | ||
| RDT&E | ||
| X | PROCUREMENT | |
| O&M | ||
| X | FMS | |
| WCF | ||
| OTHER | ||
| 10a. APPROVED PLAN NUMBER | ||
| D-20-A-C38 | ||
| 10b. APPROVED PLAN REVISION NUMBER | ||
| 0 | ||
| 10c. APPROVED PLAN REQUIREMENTS | ||
| X | AT COMPLETION COSTS FOR STANDARD FUNCTIONAL CATEGORIES (FlexFile or Legacy) | |
| X | AT COMPLETION COSTS FOR RECURRING/NONRECURRING (FlexFile only) | |
| 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
| 1.0 | 1 | F100 FMS Regional Depot Network | ||||
| 1.1 | 2 | Unit-Level Manpower | X | X | ||
| 1.2 | 2 | Unit Operations | X | X | ||
| 1.3 | 2 | Maintenance | X | |||
| 1.3.1 | 3 | Consumables and Repair Parts | X | X | X | X |
| 1.3.2 | 3 | Depot Level Reparables (DLRs) / Repair of Reparables (RORs) | X | X | X | X |
| 1.3.3 | 3 | Intermediate Maintenance | X | X | X | X |
| 1.3.4 | 3 | Depot Maintenance | X | |||
| 1.3.4.1 | 4 | Scheduled Overhaul | X | X | X | X |
| 1.3.4.2 | 4 | Unscheduled Overhaul | X | X | X | X |
| 1.3.5 | 3 | Other Maintenance | X | X | X | X |
| 1.3.6 | 3 | Packing, Handling, Shipping and Transportation (PHS&T) | X | |||
| 1.3.6.1 | 4 | Containers | X | X | X | X |
| 1.3.6.2 | 4 | Transportation | X | X | X | X |
| 1.4 | 2 | Sustaining Support | ||||
| 1.4.1 | 3 | System-Specific Training | X | X | ||
| 1.4.2 | 3 | Support Equipment Replacement and Repair | ||||
| 1.4.2.1 | 4 | Support Equipment Replacement | X | X | X | |
| 1.4.2.2 | 4 | Support Equipment Repair | X | X | X | |
| 1.4.3 | 3 | Sustaining/Systems Engineering | X | X | ||
| 1.4.4 | 3 | Program Management | X | X | ||
| 1.4.5 | 3 | Data and Technical Publications | X | X | ||
| 1.4.6 | 3 | Simulator Operations and Repair | X | X | ||
| 1.4.7 | 3 | Other Sustaining Support (Specify in Remarks) | X | |||
| 1.5 | 2 | Continuing System Improvements | X | |||
| 1.5.1 | 3 | Hardware Modifications | X | X | X | |
| 1.5.2 | 3 | Software Support | 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), Quantity Data Report | Contract Award | Initial | 20250531 | 20250731 | ||
| 2 | Cost and Hour Report (FlexFile), Quantity Data Report | Biennial Submission 1 | Interim | 20270531 | 20270731 | ||
| 3 | Maintenance and Repair Parts Data Report | Biennial Submission 1 | Interim | 20270531 | 20270731 | ||
| 4 | Cost and Hour Report (FlexFile), Quantity Data Report | Biennial Submission 2 | Interim | 20290531 | 20290731 | ||
| 5 | Maintenance and Repair Parts Data Report | Biennial Submission 2 | Interim | 20290531 | 20290731 | ||
| 6 | Cost and Hour Report (FlexFile), Quantity Data Report | Biennial Submission 3 | Interim | 20310531 | 20310731 | ||
| 7 | Maintenance and Repair Parts Data Report | Biennial Submission 3 | Interim | 20310531 | 20310731 | ||
| 8 | Cost and Hour Report (FlexFile), Quantity Data Report | Biennial Submission 4 | Interim | 20330531 | 20330731 | ||
| 9 | Maintenance and Repair Parts Data Report | Biennial Submission 4 | Interim | 20330531 | 20330731 | ||
| 10 | Cost and Hour Report (FlexFile), Quantity Data Report | Contract Complete | Final | 20350531 | 20350731 | ||
| 11 | Maintenance and Repair Parts Data Report | Contract Complete | Final | 20350531 | 20350731 | ||
| 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 |
| a. CSDR Planning Approach & Preparation Instructions |
| 1. In addition to the direction provided in the associated CSDR Data Item Descriptions (DIDs) and the CSDR Manual (DoDM 5000.04), the following instructions, requirements, and considerations found on this page/worksheet shall be utilized when collecting data and preparing CSDR submissions. |
2. This CSDR Contract plan is intended to capture costs associated with the contract number(s) listed in block 9.b. The contractor shall capture and report any and all costs incurred in order to perform the scopes of work on the Contract irrespective of contract type (e.g., firm-fixed price, cost-plus fixed fee) or funding source (i.e., via contract, via contractor internal research & development funds). The reporting entity is not expected or required to significantly modify its accounting system or technical approach to execution solely to comply with this CSDR Plan’s reporting requirements. The reporting entity is not required to track costs from specific employees, purchase orders, agreements, or subcontracts if it utilizes a standard cost accounting system and may utilize internal standard costs when prepared CSDR deliverables if those standard costs represent the most accurate “actual” cost data available to the reporting entity.
3. Costs reported against this CSDR plan shall be cumulative in nature (i.e., each submission shall report any and all costs incurred on and prior to the submission’s “AS OF DATE” (block 14.e)).
4. 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.
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).
ii. 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.
5. Regarding the WBS Structure (block 11): This CSDR Plan utilizes the Office of the Secretary of Defense Cost Assessment and Program Evaluation Operating and Support Cost-Estimating Guide's Cost Estimating Structure (available here: https://www.cape.osd.mil/files/OS_Guide_Sept_2020.pdf) as the baseline for its WBS which has been extended to provide additional insight into system(s) or subsystem(s) which the Government believes to be high-risk or high-technical-interest in accordance with DoD Manual 5000.04. The contractor shall utilize the definitions found in the Operating and Support Cost-Estimating Guide when mapping its costs into this CSDR plan’s WBS.
i. The contractor may extend any WBS element to allow the contractor to provide additional insight into its technical solution. Any and all extensions or tailoring of the WBS shall be in accordance with the Office of the Secretary of Defense Cost Assessment and Program Evaluation Operating and Support Cost-Estimating Guide's Cost Estimating Structure, the WBS guidelines included in MIL-STD-881E, and DoD Manual 5000.04.
ii. If changes to the contract scope, hours, or options (as applicable) necessitate the need to revise or add additional WBS elements to remain in compliance with the Operating and Support Cost-Estimating Guide's Cost Estimating Structure, MIL-STD-881E, or DoD Manual 5000.04, any associated contract cost/price changes related to the updated CSDR Plan or submission of revised CSDR deliverables, shall be included within the contract modification that awards the changed scope of work, hours, or options (as applicable).
| b. Resource Distribution Table |
| 1. Submissions of the Resource Distribution Table (RDT) are required under the following conditions: |
i. An RDT shall be delivered seven calendar days before the “Post-Award Cost and Software Data Reporting Conference”. Prepare this submission of the RDT at FAC/EAC value and utilizing the instructions at Block15.a.4.i.This copy of the RDT will be used during the “Post-Award Cost and Software Data Reporting Conference” in order to finalize which subcontractors will be required to provide CSDR reporting via electronic submission of deliverables directly to the Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.
ii. An RDT shall be delivered within thirty calendar days of the contractor identifying that a subcontractor who, at the time of initial subcontractor award, was not anticipated to qualify for direct subcontractor CSDR reporting via electronic submission of deliverables directly to the DCARC but is subsequently anticipated to meet the CSDR direct reporting subcontractor threshold value due to changes to scopes of work, end-item design, subcontractor/supplier, or subcontract price changes since initial contract award (unless the newly identified subcontractor has already been issued a subcontractor reporting waiver associated with this contract).
| c. Submission Dates |
| 1. All CSDR deliverable “AS OF DATES” and “DUE DATES” listed in blocks 14.e and 14.f are identified for planning purposes only. Submission dates are subject to change and are determined in accordance with the event drivers as identified below: |
i. Interim Submission(s): Submission events marked as an "Interim" submission in block 14.d shall have an "AS OF DATE" based on the submission event name in block 14.c. For example, if the submission event name was "Contract Award Plus 24 Months" then the submission's "AS OF DATE" is the contract award date plus 24 calendar months. If the submission event name was "Complete Delivery of First Article Test Assets" then the submission's "AS OF DATE" would be the date the final First Article Test Asset was delivered.
ii. Final Submission(s): Submission events marked as "Final" submission in block 14.d shall have an "AS OF DATE" when the following conditions have been met:
1. Condition 1: All end items anticipated to be procured on the contract have been delivered and accepted by the government (e.g., as evidenced by a completed DD Form 250) or higher tier contractor in the case of a subcontractor.
2. Condition 2: 95% or more of all ATD total costs have been incurred relative to all costs the reporting entity expects to incur for each and every Order/Lot (defined in Data Group B, Item 4 of the approved FlexFile DID).
| d. Cost and Hour Report (FlexFile) & Quantity Data Report |
| 1. FAC vs. EAC: Block 12.e of this CSDR plan indicate that a "Forecast at Completion" (FAC) is required to be reported in CSDR deliverables. The FAC required 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. |
2. Nonrecurring/Recurring Segregation: The contractor shall utilize the specific definitions and requirements in the CSDR Manual (DoDM 5000.04) and the definitions in the DID for the Cost and Hour Report (FlexFile) report (DI-FNCL-82162) to segregate Recurring and Nonrecurring costs discretely and not as an aggregate.
3. Order Lot Scope: Block 16 of this CSDR Plan is meant to capture the discrete Delivery Orders/Task Orders (as applicable) exercised on the contract. If a Delivery Order/Task Order (as applicable) is exercised on the contract but is not listed in block 16, the contractor shall submit the dollars and hours in the Cost and Hour Report (FlexFile) and the quantity information in the Quantity Report tagged using the name of the Delivery Order/Task Order (as applicable) utilized on the contract. The CSDR Plan will be updated to include the appropriate Delivery Order/Task Order (as applicable) name in block 16, after report submission, if required.
i. If a Delivery Order/Task Order (as applicable) is exercised on the contract but is not listed in block 16, the contractor shall submit the dollars and hours in the Cost and Hour Report (FlexFile) and the quantity information in the Quantity Report tagged using the name of the Delivery Order/Task Order (as applicable) utilized on the contract. The CSDR Plan will be updated to include the appropriate Delivery Order/Task Order (as applicable) name in block 16, after report submission, if required.
4. End Item Scope: Block 17 of this CSDR Plan is meant to capture the discrete hardware end items that are DD-250'ed, ordered, procured, or exercised (as applicable) on the contract to the greatest degree possible given the reporting entity’s accounting system capabilities and technical approach to contract execution. If an End Item is DD-250'ed, ordered, procured, or exercised (as applicable) on the contract but is not listed in block 17, the contractor shall submit the dollars and hours in the Cost and Hour Report (FlexFile) and the quantity information in the Quantity Report tagged using the name of the End Item utilized on the contract. The CSDR Plan will be updated to include the appropriate End Item name in block 17, after report submission, if required. If the reporting entity’s accounting system and technical approach to contract execution does not allow for the segregation and reporting of data at the level indicated in block 17, it shall seek Government approval on an alternate set of end item IDs or revisions to the WBS that provide insight into actual contractual costs at a time no later than the completion of the CSDR Readiness Review. The reporting entity may utilize internal standard costs when reporting hardware or material costs when its accounting system cannot associate specific purchase orders or subcontractor agreements to the contract number(s) listed in block 9.b.
| e. Period Of Performance & Additional Scope Of Work |
| 1. If the Contract period of performance is extended by more than six months, or if the scope of work is modified to include work not otherwise covered by the CSDR Plan, the government may modify the CSDR Plan to require additional submission events and add additional WBS elements in order to ensure the accurate and complete collection of cost data associated with the modified contract. Depending on the scope and complexity of the contract modification, the contractor may be required to host or attend an additional Post-Award Cost and Software Data Reporting Conference to review the CSDR Plan changes and the contractor’s plan to collect and report costs associated with the additional scope of work. |
| f. FAC vs EAC |
| 1. 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. |
| g. 1921-3 CONTRACTOR BUSINESS DATA REPORT |
| 1. 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. |
2. Reports are submitted annually at the end of the contractor's fiscal year.
3. 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.
4. 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.
| h. Cost Accounting Standards (CAS) Disclosure Statement Differences |
| 1. The contractor shall follow the accounting procedures specified in its latest approved CAS Disclosure Statement and with any clauses or requirements included in the contract. As part of the Post-Award Cost and Software Data Reporting Conference, the contractor shall identify any aspect(s) of its latest approved CAS Disclosure Statement which preclude or inhibit compliance with this CSDR Plan and DoD 5000.04 (CSDR Manual). The contractor shall identify any deviations from its CAS disclosure statement it intends to utilize to prepare CSDR submissions. |
| i. Nonrecurring/Recurring Segregation |
| 1. The contractor shall utilize the specific definitions and requirements in the CSDR Manual (DoDM 5000.04) and the definitions in the DID for the Cost and Hour Report (FlexFile) report (DI-FNCL-82162) to segregate Recurring and Nonrecurring costs discretely and not as an aggregate. |
| j. Common |
| i. End Item ID Common: The "Common" end item tag shall be used to report costs and hours which are not incurred or directly attributable to an individual end item. For example, overarching program management costs and hours that are required, independent of the type or quantity of end items on contract would be tagged against the “Common” end item. Common hardware (i.e., identical/homogeneous part numbers) procured and integrated into multiple end items shall utilize the end item tag for the prime product they were integrated onto and shall not be tagged with the “Common” end item. |
| k. CSDR Readiness Review |
| 1. The contractor shall host a CSDR Readiness Review (CSDR-RR) at the contractor’s facility where CSDRs are prepared with the Government’s Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD Manual 5000.04 (CSDR Manual). The purpose of the CSDR-RR is to review the contract’s CSDR requirements and assess how the Contractor’s accounting system satisfies the CSDR requirements found in DoD 5000.04 (CSDR Manual) and this CSDR Plan. In a briefing presented by the Contractor in its own format, the Contractor shall: |
i. Demonstrate how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables.
ii. Describe how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting.
iii. Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by this CSDR Plan and associated CDRLs.
iv. Present the methodologies used for mapping internal cost accounts to the WBS, specifically showing how individual WBS elements and functional element codes will be populated.
v. Propose any changes to this CSDR Plan in order to tailor the plan to the contractor's accounting system to include any contractor recommended changes or additions to the WBS elements or end item IDs. These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.
vi. The contractor and CWIPT will also review the initial submission of the "Resource Distribution Table (RDT)", in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to the Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.
vii. The CSDR-RR shall be held within 60 days of contract award or the start of work meeting on a date mutually agreed to by the CWIPT and the contractor. This meeting has an anticipated duration of one business day.
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 | |||
| 1..n | Delivery Order 1…n | O&S | |||
| 17. END ITEMS | |||||
| a. ID | b. NAME | ||||
| 1..N | NIINs..n | ||||
| 18. UNIT/SUBLOT REPORTING AND UNIT SEQUENCING REQUIREMENTS | |||||
| a. ORDER/LOT ID | b. END ITEM ID | c. UNIT/SUBLOT REPORTING | |||
| (X if applicable) | d. UNIT SEQUENCING |
(X if applicable)
DRAFT DD FORM 2794 (PAGE 5), INTRA-CONTRACT SCOPE, JANUARY 2019
File details come from the government source that posted it. Updated .