Attachment 4.b - RMWT LEO GEPs Task Order 01 DD Form 1423, Contract Data Requirements List (CDRLs).pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

PREVIOUS EDITION MAY BE USED.

DD FORM 1423, FEB 2024

Page of (Updated 20260326) Instructions

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoDM 5010.12 for detailed instructions.)

DD FORM 1423, FEB 2024

Page of (Updated 20260326)

CONTRACT DATA REQUIREMENTS LIST

C. CATEGORY:

14. DISTRIBUTION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES Draft Final Reg Repro

16. REMARKS

14. DISTRIBUTION

15.TOTAL

Image of arrow pointing towards totals

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package; TM - Technical Manual; Other - other category of data, such as "Provisioning," "Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support (e.g., Mission Design Series (MDS) designator).

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Name of preparer of CDRL.

Item H. Date CDRL was prepared and signature of preparer of CDRL.

Item I. Name of CDRL approval authority.

Item J. Date CDRL was approved and signature of CDRL approval authority.

Item 1. See DFARS Subpart 204.71 for proper numbering. To add or delete additional data items, point and click the plus or minus sign to the right of Block J.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Identify only one Data Acquisition Document No. If a single work task generates more than one deliverable data product, prepare a separate data item for each deliverable data product.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work/Performance Work Statement paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data and computer software, specify the contractor's requirement to mark the appropriate distribution statement on the technical data or computer software (ref. DoDI 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15. Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14; Desired medium for delivery of the data item.

Identify for which data item additional remarks are provided. When tailoring the Data Acquisition Document invoked in Item 4, identify which portions of that Document are being tailored.

Identify any referenced attachments to the form. Attachments can be added using the button at the bottom of page 1.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government’s rights to use the data shall be governed by the pertinent provisions of the contract.

9.0.0.2.20120627.2.874785 DD Form 1423, "Contract Data Requirements List" Remove Continuation of Remarks Remove Continuation of Remarks Remove Continuation of Remarks Remove Continuation of Remarks Add Continuation of Remarks Remove Continuation of Remarks Remove Continuation of Remarks

The P&SEMP represents a tailored and consolidated document combining key information from what would ordinarily be captured in a Program Management Plan (PMP) and a Systems Engineering Management Plan (SEMP).

Format:

The P&SEMP shall shall be in contractor format and shall be unclassified.

Content:

The P&SEMP shall address, at a minimum, the following areas:

• Resources Management approach, including:

• Organizational structure

- Staffing, retention, and training plan

- Subcontractor/associate contractor management

- Organizational Conflict of Interest management and risk mitigation approach

• Contract Start Up plan, detailing the priority of activities and tasks that will be performed within the first 90 days of the contract to ensure Program and Stakeholder dependencies are in progress or achieved.

• Data Rights Plan to address all components/elements of the system (technical data, software, or hardware), including COTS products their functionality, and their proposed use in the system supporting the RMF

• Proposed metrics to be collected and reported during contract execution

• Process for monitoring, controlling, and reporting costs and fees

• Quality Assurance process

• Process for selecting, procuring, installing and maintaining government-approved system hardware and software, and a description of Supply Chain Management

• Process for receiving, inspecting, maintaining, storing, delivering and maintaining materials (including secondary movement of materials to/from stakeholders, maintainers, supply chain managers and supplier)

• Risk, Issue and Opportunity Management approach to ensuring schedule and technical requirements are met,and alignment with PWSA/Enterprise processes

• Schedule Management approach, including approach to maintaining IMS

• Communication/collaboration approach with Government, other PWSA contractors, and stakeholders including planned collaboration forums and their cadence

• Overview of Systems Engineering, Integration and Test (SEI&T) approach and processes to be used in alignment with PWSA to include, but not be limited to:

1) Include description of all SE tools and processes used within the Program, to include the interface and bi-directional traceability of these tools and processes.

2) Describe the contractor’s planned engineering approach to meeting the program’s contract, objectives, and overall technical and management approach.

3) Describe the contractor’s detailed operational plan for executing systems engineering, including integration of the specialty engineering disciplines.

4) Contain an annotated mapping between contractor and government/Enterprise SE processes. Identify any technical or technical management processes not mapped, including rationale for why they are not needed.

5) Show alignment of SE processes of the contractor and subcontractors providing engineering effort.

6) IVV&T and Test and Evaluation Mangement approach

7) Trade studies for system requirements definition, architecture definition, design definition, integration, and verification/validation decisions.

8) Software development approach

9) Data Management approach

16. REMARKS: Block 4: The IMS provides a comprehensive overview of Tasks required to complete a project. It includes the start and end dates for each Task, as well as dependencies, durations, and resource requirements. It is an integrated, logically driven, networked-based schedule that is vertically and horizontally traceable. The IMS should reflect all activities detailing the work necessary to accomplish the program's objectives, including activities both the Govt,or other inter-dependent stakeholders, and Contractor are to perform. The IMS should trace directly to the WBS.

The IMS shall include all elements associated with the development, production, or modification, and delivery of the total product and project high-level plan. The IMS shall include durations for each discrete work package and planning package (or lower-level Task or activity), along with predecessor and successor relationships, and any constraints that control the start or finish of each work package and planning package (or lower level Task or activity). The IMS shall include Giver/Receiver information (CDRL C003)

Other Schedule Artifacts include extracts from the IMS or schedule-related data required to communicate planning, technical or status information.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/ PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

Blocks 10, 12, and 13: Initial IMS submission shall be submitted/presented as a draft at the Program/Project Kickoff meeting (AWD+ 2 calendar weeks); Final IMS shall be submitted at AWD + 45 calendar days. The IMS shall be updated and statused at a minimum monthly, in alignment with program status meetings. Additional deliveries with revisions as requested.

16. REMARKS: General: This CDRL applies to all Program/Project meetings and technical program/project reviews and the artifacts associated with these meetings and reviews to include, but not be limited to:

--Program/Project Kickoff meeting and associated artifacts --Cost and Software Data Reporting Readiness Review and follow on meetings, and associated artifacts --Program /project Requirement reviews/meetings/technical exchanges (TEMs) and associated artifacts --Program/project Design reviews/meetings/TEMs and associated artifacts

Block 4:

For all Meetings/reviews within this CDRL, the Contractor shall coordinate and gain approval from the government COR regarding agenda, location/format, and required artifacts for review/presentation. This coordination shall be conducted at the earliest practicable time, and no later than ten (10) business days prior to the meeting/review

The Contractor shall conduct a Program/project Kickoff Meeting within 30 calendar days of Authorization to Proceed (AWD).

The Contractor shall conduct a Cost and Software Data Reporting Readiness Review (CSDR-RR). The purpose of the CSDR-RR is to ensure that a contractor or reporting entity is fully prepared to accurately and consistently report actual costs and software data in accordance with the government-approved CSDR Plan. The CSDR-RR key activities include a review of the CSDR plan and reporting requirements, clarification of data reporting requirements, and identification of any potential revisions needed for data reporting to align with contractor procedures.

The Contractor shall conduct monthly Program/project reviews to provide the Government insight into Contract activities, risks, cost alignments/misalignments and plan to schedule. These reviews/meetings shall cover topics including but not limited to the Contractor IMS, risks, contract status, the status of technical performance measures, key system design trades, requirements verification status, and schedule performance. The Contractor shall provide monthly updates in these reviews to all burn-down plans, risks, issues and opportunities starting two calendar months after AWD and immediately upon occurrence of any new critical risk or issue.

The Contractor shall conduct bi-monthly (every 2 months) incremental GEP architecture design reviews with the Government. Guidance related to these design reviews shall be discussed at Contract/TO1 kickoff though the Contractor should anticipate the level of discussion and artifact development for the first design review to be at a Preliminary Design Review (PDR) level, and anticipate this activity to culminate with a Critical Design Review (CDR) level NLT AWD plus 160 calendar days. These meetings may be attended by T3 PWSA stakeholders.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/ PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

16. REMARKS: General/Block 4: The Contract Work Breakdown Structure (CWBS) is the Government approved product oriented family tree, used as a framework for technical planning, control and reporting. The RMWT LEO GEPs CWBS shall be product oriented, comply with DI-MGMT-81334D and subsequently MILSTD-881F, and represent an extension/expansion of the CWBS that will be used for the Cost and Software Data Report (CSDR) Plan (Contract Attachment xx). The CWBS extension/expansion shall be to the lowest level necessary to fully capture the scope of the Project. The CWBS shall include all product elements for which the Contractor is responsible, including product elements developed by or with subcontractor team members.

The CWBS shall consist of two parts: the CWBS Index (listing the individual work elements by their CWBS, SOW paragraph reference(s) , CLIN(s), and CDRL(s)); and the CWBS dictionary describing in detail the effort and tasks associated with every CWBS element shown in the CWBS index.

The CWBS shall be submitted in the format specified within DI-MGMT-81334D, as well as a stand-alone Microsoft Excel file (extension “.xlsx”).

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

Blocks 10, 12, and 13: The first delivery of the and CWBS and CWBS Dictionary shall be provided as draft at the Program/project Kickoff meeting. Subsequent CWBS and CWBS Dictionary shall be delivered at AWD + 45 calendar days. Subsequent updates shall be delivered in alignment with CSDR Plan and CDRL requirements (B001, B002, B003), or as requested by the Government. Additional deliveries with revisions as requested.

16. REMARKS: Block 4: The Program Protection Implementation Plan (PPIP) content shall comply with the content specified in DID DI-MGMT-82144A, and shall be written in Contractor format.

GEPs Security Documents include security plans, designs and other documentation detailing the physical and operations security approach, agreements with/services provided by local/country hosts, access controls, process and technical measures, and other information per GEP site

Block 8: PPIP approval will be for content and format. All submissions shall be in Microsoft office product format. The Government shall provide comments to the Contractor within 14 calendar days of award for inclusion into the final program protection plan.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

Blocks 10, 12 and 13: The draft of the PPIP shall be submitted 30 days after receipt of the Government provided Program Protection Plan. The Government requires 30 days for review and commenting. The final PPIP submission shall be submitted 30 days after receipt and adjudication of Government comments. Other GEP Security Documents shall be delivered in draft as soon as practicable following GEP site location determination. Subsequent version maturity of these documents shall align with pre-construction/development activity milestones, dependent on GEP location, at a cadence negotiated with/approved by the Government. All GEP security documents delivered to the Government shall require a minimum of 5 working days for the government to review and submit comments back to the Contractor for resolution. The Contractor shall request written confirmation from the Government (CO/COR) that a Security document has been approved by the Government if no comment/response is received within 14 calendar days of submission by the Contractor.

16. REMARKS: Purpose: The purpose of the Data Accession List (DAL) is to provide a medium for identifying contractor internal data which has been generated by the contractor in compliance with the work effort described in the Statement of Work (SOW). The DAL is an index of the generated data that is made available upon request, using deferred ordering procedures. This data item is not a substitute for standard data requirements that are contractually applied. The DID (cited in Block 4) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

All documentation and data produced or prepared by the Contractor or any of their subcontractors under this contract shall be the property of the Government and have, at a minimum, Government purpose rights, unless otherwise negotiated.

Contents: the DAL Shall include requirements and development baseline documents (e.g. "A-Specs" and associated spec-tree flow-down documentation) as well as selected internally generated technical data and computer software used by the Contractor to develop test, and management the program.

The DAL shall include the items controlled by the prime Contractor and those controlled by its subcontractors. If the prime Contractor and subcontractors created separate DALs, the prime Contractor shall ensure the Government has access to all DALs created on the contract. This may require a subcontractor to submit their DAL directly to the Government or to grant the Government access to DAL content in a separate environment. The DAL requirements shall be flowed down to all subcontractors as mutually agreed to by the Government and prime Contractor.

The DAL shall list all data required for contract completion including data incidental to or developed with or for other contract deliverables either as a segregable item or as part of the contracted level of effort provided for under the contract. At a minimum the DAL must include the following entries for each item listed: identification number, title, brief description, security classification, applicable Government rights upon delivery (when called for if not initially cited as a deliverable at contract award), and the in-house release dates. Computer software (to include COTS and open source) shall include, at a minimum, file name, file date, file size, and version number (if applicable).

The Contractor shall inform the Government how it manages the DAL and the method by which the documents, data, and software are organized and/or categorized. The DAL shall identify the Government rights associated with the data and computer software with the following codes:

• “UR” unlimited rights

• “LR” limited rights (technical data only)

• “RR” restricted rights (software only)

• “GPR” Government purpose rights

• “SLR” special license rights (use for all specifically negotiated licenses including licenses to data that cannot be easily categorized as technical data or business data and that are subject to agreement pursuant to FAR52.002(B)

The Contractor shall purpose a marking scheme for commercial documents. The marking scheme must be approved by the CO and the markings shall not include the term “propriety” when the document contains commercial data which the Government is entitled unlimited rights to such as operations, maintenance, installation and training(OMIT) and fit, form, function (F3) data.

Information that cannot easily be categorized as technical data or business data e.g. program schedules, EVM reports, and program management reports and is sufficiently detailed to reveal a Contractor’s confidential business practices shall be identified before, or as soon as practicable, after contract award. The parties will agree to the party’s rights and obligations in such data and how it is to be marked, handled,

16. REMARKS: Block 4: The Contractor shall provide an inventory listing of GP (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the Contractor’s possession (to include subcontractors) on the contract. The listing and content shall be in accordance with the DID DI-MGMT-80441D, listed in Block 4. DI-MGMT-80441D Section 3 Content, add: Asset Manufacturer, Year of Manufacture, Manufacturer Cage Code, Asset Useful Life (years), and Manufacturer Address.

The Contractor shall develop and maintain a Hardware Bill of Materials (HBOM) and a Software Bill of Materials (SBOM) for the GEPs capturing resources used for Test and Operations. These BOMs shall be developed in compliance with the content and format specified in DID DI-PSSS-81656B, listed in Block 4 . Hardware and Software BOMs provide a nested inventory of hardware and software “components” and enable identification of embedded dependencies which may represent supply chain and/or security risks.

The Contractor shall maintain an asset inventory that includes all hardware and software assets to include asset specifications, versions, End of Life timelines, locations, and primary vendor and organizational point of contact for the asset.

The contractor shall utilize the GFP module in Procurement Integrated Enterprise Environment (PIEE), in accordance with DFARS 252.245-7005, to report receipt of GFP, which includes Contractor Acquired Property (CAP), to ensure accountability for later disposition.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

Blocks10, 12 and 13: Initial reports/inventories are due at AWD + 3 calendar months. Subsequent deliveries are required monthly or as property changes possession. PIEE updates are to be made as specified in PIEE guidance. Additional deliveries with revisions as requested.

16. REMARKS: Block 4: The Contractor shall develop and deliver Agendas, Minutes, Actions, Risks and Mitigations, Follow-up Steps, etc., for all meetings and/or collaboration forums led by the contractor. For meetings, technical exchanges, reviews etc. attended by the Contractor, the Contractor shall deliver artifacts as required for the review/meeting/activity, document actions assigned to the Contractor, and deliver them for review/concurrence by the Government.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

Blocks 10, 12, 13: Stakeholder meeting and review related materials shall delivered sufficently in advance of the associated meeting/review to allow review by the Government prior to external presentation (nominally five (5) business days prior). Artifacts required to support an external stakeholder led event shall be delivered at the maturity level required for that activity, in alignment with the date of need. These dates shall be identified as Giver/receiver items and included in the Contractor IMS (A002). Actions items shall be delivered within two business days of the meeting. All other delivery timelines are as per agreed to between the Contractor and the Government. Additional deliveries with revisions as requested.

16. REMARKS: Blocks 10 - 13: Prepare the Cost and Hour Report (FlexFile) in accordance with DI-FNCL-82162 and the OSD CAPE Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-FNCL-82162, is available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/csdrreportingguidance/dids.html. The CSDR Plan is included as a contract attachment.

The following tailoring of the DID is acceptable:

1. Data Group B - Item 4 - Additional Data Fields #1-#12 Not required.

Contractors shall be required to submit the Cost and Hour Report (FlexFile) at frequencies specified in the CAPE-approved CSDR plan. The contract CSDR plan uses the event field as the driver for the submission of the reports, not the "as of date." If the event slips, the contractor must notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a request for change in the event-driven date for reporting through the CADE website for CAPE approval before relief is given for the date reflected in the CAPE-approved CSDR Plan.

The FlexFile shall be delivered in either a) MS Excel (.xlsx) or comma separated values (.csv) in accordance with the FlexFile & Quantity cPet-compatible templates and the DD FORM 2794, or b) JavaScript Object Notation (JSON) as described in the FlexFile File Format Specification (FFS) and Data Exchange Instructions (DEI) referenced in the FlexFile DID Requirements Section 2 and available on the CADE website at https://cade.osd.mil.

All files shall be submitted electronically using the CADE website. Data submitters must register through the CADE website and possess a DoD-approved ECA digital certificate or DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested roles. All CADE Portal accounts need to be renewed at least annually.

Subcontractor Reporting: Prime contractors shall ensure CSDR requirements contained in their prime contracts are flowed down to all subcontractors with an anticipated eventual contract value greater than $20M unless given relief by the Government. This flow down includes requiring subcontractors to electronically report directly to CAPE using the CSDR Submit-Review System.

The prime contractor shall be required to work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to the CAPE for DDCA approval.

The Office of the Secretary of Defense (OSD) Cost Assessment & Program Evaluation (CAPE) may use a CADE management support contractor to review the data submitted under this CDRL to ensure contractual requirements are met and to facilitate distribution of the data to authorized Government users (hereinafter referred to as "the support contractor"). This data may include information that is considered a trade secret, proprietary, business sensitive, or otherwise protected pursuant to law or regulation (hereinafter referred to as “protected information”). Execution of this contract by the contractor is considered consent to CAPE's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its CADE management support contractor for the limited purpose of executing its CADE management support contract responsibilities.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

16. REMARKS: Blocks 10 - 13: Prepare the Technical Data Report (TDR) in accordance with DI-MGMT-82165 (or the most recently approved version) and the OSD Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-MGMT-82165, is available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/csdrreportingguidance/dids.html. The CSDR Plan is included as a contract attachment.

Contractors shall be required to submit Technical Data Reports at frequencies specified in the OSD DDCA-approved CSDR plan and in the contract. The "As of Dates" and "Due Dates" are notional and subject to change. The CSDR plan uses the submission event names as the driving mechanism for the submittal of the cost reports, not the "as of date." In the event of a programmatic schedule slip, the Reporting Entity shall notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a date change request with supporting documentation in the CADE system for the event-driven submission for CAPE approval. CAPE will not issue an updated OSD DDCA-approved contract CSDR plan for revisions based solely on date changes.

Any alternative CDRL identified through the CWIPT process that meets the requirements for technical parameter reporting should be submitted using the CADE CSDR Submit-Review System along with the TDR for each required submission event. Alternative CDRLs can be uploaded as "Other" file types.

All Technical Data Reports shall be submitted electronically using the CADE CSDR Submit-Review System. Only unclassified technical data may be uploaded to the CADE Portal. All Technical Data must be reviewed by the contractor prior to submission to submission for CADE to ensure that aggregation of the technical data does not warrant a higher classification level.

The required file format for each Technical Data Report is specified in its Data Item Description (DID), unless the DDCA-approved CSDR plan specifies another format. Data submitters must register through the CADE website (https://cade.osd.mil) and possess a DoD-approved ECA digital certificate or a DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested role. All CADE Portal accounts need to be renewed at least annually.

Subcontractor Reporting: The prime contractor is responsible for the collection and reporting of all Technical data required in the CSDR Plan, including work performed by subcontractors or suppliers. If the prime contractor cannot report all required data, then it's the prime contractor's responsibility to inform the Government to determine if the subcontractor or supplier should electronically report directly to CAPE using the CSDR Submit-Review System.

The prime contractor shall be required to work with the CWIPT and all appropriate subcontractors to prepare separate subcontract CSDR plans for submission to the DCARC for approval.

Technical data will be available to support contractors who work for the Office of the Secretary of Defense (OSD) or the services. Access to the data is only granted while the contractor is supporting a legitimate Department of Defense (DoD) contract, the contractor has a need-to-know, and a Non-Disclosure Agreement (NDA) has been signed with the Government organization that the contractor supports.

The Office of the Secretary of Defense (OSD) Cost Assessment & Program Evaluation (CAPE) may use a CADE management support contractor to review the data submitted under this CDRL to ensure contractual requirements are met and to facilitate distribution of the data to authorized Government users (hereinafter referred to as "the support contractor"). This data may include information that is considered a trade secret, proprietary, business sensitive, or otherwise protected pursuant to law or regulation (hereinafter referred to

16. REMARKS: Blocks 10 - 13: Prepare the Quantity Data Report in accordance with DI-MGMT-82164 and the OSD CAPE Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID, DI-MGMT-82164, is available from the Cost Assessment Data Enterprise (CADE) website at https://cade.osd.mil/csdrreportingguidance/dids.html. The CSDR Plan is included as a contract attachment.

The following tailoring of the DID is acceptable:

N/A

Contractors shall be required to submit the Quantity Data Report at frequencies specified in the CAPE-approved CSDR plan. The contract CSDR plan uses the event field as the driver for the submission of the reports, not the "as of date." If the event slips, the contractor must notify the Government Program Office that a date change is needed. It is the responsibility of the Government Program Office to submit a request for change in the event-driven date for reporting through the CADE website for CAPE approval before relief is given for the date reflected in the CAPE-approved CSDR Plan.

The Quantity Date Report shall be delivered in either a) MS Excel (.xlsx) or comma separated values (.csv) in accordance with the Quantity cPet-compatible template and the DD FORM 2794 or b) JavaScript Object Notation (JSON) as described in the Quantity Data Report Format Specification (FFS) and Data Exchange Instructions (DEI) referenced in the Quantity Data Report DID Requirements Section 2 and available on the CADE website at https://cade.osd.mil.

All files shall be submitted electronically using the CADE website. Data submitters must register through the CADE website and possess a DoD-approved ECA digital certificate or DoD-issued CAC to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR submitter user role. After the registration information has been verified, CAPE shall authorize the user account and requested roles. All CADE Portal accounts need to be renewed at least annually.

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated..

16. REMARKS: Block 4 and General Information:

This CDRL is comprised of the following documents/data: System Requirements Document (SRD); Requirements Verification and Traceability Matrix (RVTM); and Giver/Receiver List. These documents/items are described below, including their Block 4 DID authority for format/content compliance.

The System Requirement Document (SRD) specifies the requirements for a system/subsystem(s), Computer Software/Firmware Configuration Item (CSCI), Computer Software Components (CSCs) and the methods to be used to ensure that each requirement has been met. Requirements pertaining to the external interfaces may be presented in the SRD or in one or more Interface Requirements Specifications /Documents. The SRD shall comply with the content prescribed in DID DI-IPSC-822

The Requirements Traceability Verification Matrix (RVTM) provides bidirectional traceability from high-level system performance requirements, to the lowest-level requirements. The RVTM shows the traceability and allocation of the requirements contained in the specification tree (i.e. performance specification, detailed specification, subsystem specification, software requirements specification, interface specification and design documentation). The RVTM is also used to describe how and at what test event(s) each requirement is verified. The RVTM shall comply with DID DI-MGMT-82133.

The Giver/Receiver List shall track the dependencies and hand-offs between different PWSA performers/contractors and government entities. It shall include all RMWT LEO GEPs giver items and timelines identified by T3 SVV and other PWSA T3 stakeholders. The format shall be organized as a table or spreadsheet and shall includes key details for tracking, communication, and issue resolution. At a minimum, the Giver/Receiver list shall include: Name and description of deliverable; Giver (owner); Receiver; Required by/Need date; anticipated delivery/Giver date; Status; Notes/Comments (include risks, issues, impacts if not delivered when needed, dependencies, etc.). Giver/receiver information shall be included in the Contractor IMS (CDRL A002).

Block 9: Distribution authorized to DoD and U.S. DoD Contractors only (Controlled Technical Information, 31 July 2023). Other requests for this document shall be referred to SDA/ PWSA Ground Program Director. Documents shall be controlled by their classification. All materials provided in CDRLs are considered Government Purpose Rights unless expressly negotiated.

Blocks 10, 12 and 13: First submission of the SRD and RVTM shall be as a Draft and shall be delivered in alignment with the first RMWT LEO GEPs Requirement/design review meeting. Updated versions of these documents shall be at the second quarterly RMWT LEO GEPs requirement/design review and Final Version of these documents shall be delivered at the third quarterly RMWT LEO GEPs requirement/design review, unless otherwise negotiated with the Government. With all deliveries, the Government has 14 calendar days in which to submit comments against the documents. If no comments are submitted to the Contractor within the 14 calendar days, the documents are to be considered approved. If comments are submitted, the Contractor shall resolve all comments within 14 calendar days of receipt. unless an extended period is approved by the Government.

First submission of the Giver/Receiver List shall be aligned with the RMWT LEO GEPs kickoff meeting, (NLT AWD plus 2 calendar weeks). An updated version, to include a more complete listing of stakeholder needs, shall be delivered at AWD plus 30 calendar days. The Giver/Receiver List shall be updated monthly, and included in program/project status reviews or other regular discussions with the COR, government team and stakeholder collaboration forums.