Commercial Solutions Opening (CSO) Department of the Air Force (DAF) Cost and Software Data Reporting (CSDR) Support and Curation.

DAF CSDR Support and Data Curation —PWS Page 1 of 13 Performance Work Statement (PWS) DAF Cost and Software Data Reporting (CSDR) Support and Data Curation for Air Force Cost Analysis Agency (AFCAA) Period of Performance: One (1) Year — Start Date TBD Funding: Operations and Maintenance (O&M) 1. INTRODUCTION AND PURPOSE The Department of War (DoW) requires accurate and reliable cost reporting to inform life cycle cost estimates and programming and acquisition decisions. The data collected from DoW cost reporting forms the basis of these estimates, as mandated by statute and DoW and Department of the Air Force (DAF) policies. This Performance Work Statement (PWS) defines a focused, one-year level of support to the Air Force Cost Analysis Agency (AFCAA) covering two related areas of work: (1) Cost and Software Data Reporting (CSDR) planning, verification and validation (V&V), and compliance support; and (2) CSDR submission data curation, metadata tagging, and quality preparation activities in support of the downstream CSDR data ingestion environment maintained by the Government. Both tasks are performed in support of the CSDR process under DoD Instruction (DoDI) 5000.73, Cost Analysis Guidance & Procedures, and Air Force Instruction (AFI) 65-508. -- 1 of 13 -- DAF CSDR Support and Data Curation —PWS Page 2 of 13 Use of automated validation, data analytics, and Artificial Intelligence (AI) tooling to improve the efficiency and quality of the work described herein is highly encouraged, subject to the limitations described in Section 7. 2. TASKS AND TASK REQUIREMENTS The contractor shall provide the necessary labor, supervision, and management to fulfill the tasks described below. The contractor shall adhere to all scheduled timelines, milestones, delivery schedules, and administrative requirements, including scheduled on-time delivery of reports, data products, status reports, billing invoices, staffing of personnel, and action item completion. Meetings shall include a kickoff meeting within ten (10) business days after contract start; recurring working meetings between the contractor's task leads and the AFCAA technical lead(s); and quarterly formal reviews with the AFCAA Program Manager and technical leads, to include a final review approximately thirty (30) calendar days before the end of the period of performance. Task 1 (Enabling Task) — Obtaining Permissions to Access Data Sources Successful performance of this requirement depends on the contractor working proactively with the Government to obtain permissions to access Government-held data. Much of the data in the Cost Assessment Data Enterprise (CADE) repository is from defense contractors and major subcontractors. Each considers its data as business sensitive and subsequently has marked it, or considered it, as proprietary. This requires protecting this information from public disclosure. Since the contractor team while providing these services will be provided or have access to nonpublic information, each person on the contractor and subcontractor team working this effort shall sign a non-disclosure agreement (NDA) with AFCAA and an NDA with OSW Cost Assessment Program Evaluation (CAPE) for access to CADE. The contractor and subcontractor team shall work proactively and sign, as required, NDAs with other Government organizations to support and fulfill data collection and task requirements. The contractor will work proactively with AFCAA to identify NDA requirements for all Original Equipment Manufacturer (OEM) and major subcontractor data the contractor will access in support of CSDR planning, verification and validation, and curation activities under this PWS. Should an OEM or major subcontractor require an NDA with the contractor, then the contractor shall develop and complete this before AFCAA facilitates access to that OEM's or major subcontractor's Government-held data. These NDAs must carry through the entire contract period of performance, including any option periods. Furthermore, the NDAs shall flow equally across the contractor and its subcontractors. These NDAs shall be coordinated directly between the contractor and the OEMs within thirty (30) days of identified need. If the contractor shows a diligent effort to complete the NDA process with consistent follow up with OEMs and is still unsuccessful, the Government will reassess and replan accordingly. Subcontractors may or may not be required to sign separate NDAs, dependent on the negotiated OEM agreements. As part of its proposal and throughout the duration of this contract, the contractor shall identify and notify the Contracting Officer (CO) of any Organizational Conflict of Interest (OCI) it or any of its subcontractors has, or could have, with any OEM or major subcontractor who has submitted -- 2 of 13 -- DAF CSDR Support and Data Curation —PWS Page 3 of 13 reports held in CADE. Moreover, the contractor shall notify the CO and the AFCAA Program Manager of any acquisition or merger involving itself or its subcontractors and explain whether that action will create an OCI. Similarly, the contractor will identify any other emerging event or action that would create an OCI. Task 2 (Enabling Task) — Plan of Action and Milestones (POA&M) The contractor shall develop and submit, for Government review and approval, a POA&M describing the contractor's approach to satisfy all tasks and elements under this PWS within thirty (30) calendar days of contract award. The POA&M shall be a living document and shall be updated quarterly, or as directed by the AFCAA technical lead. The POA&M shall include, at minimum: • A detailed description of the approach to completing each task and subtask, including interim and final milestones. • Task activity and milestone schedule, including any go/no-go decision points requiring Government concurrence. • Sufficient lead time for the delivery of all task products to allow Government review and feedback; the contractor shall resolve all Govern…