Performance Work Statement (PWS)

Research and Development for Cost Estimating Modeling

Data Analytics and Research (CEMDAR) Development Effort for

Air Force Cost Analysis Agency (AFCAA)

January 2026 i

Table of Contents

INTRODUCTION AND PURPOSE ----------------------------------------------------------------------- 1

TASKS AND TASK REQUIREMENTS ------------------------------------------------------------------ 2 Task 1 (Enabling task) – Obtaining Permissions to Access Data Sources ------------------------ 3 Task 2 (Enabling task) – Develop a Plan of Action and Milestones (POA&M) ----------------- 3 Task 3 (Core task) – Development and Continuous Improvement of Data Pipelines for

Enterprise Cost and Technical Analysis -------------------------------------------------------- 4 Task 4 (Core task) – Data-Driven Analysis/Studies, Model Development and Application

Deployment ----------------------------------------------------------------------------------------- 8 Task 5 (Core task) – Contracts Database (Option CLIN) ------------------------------------------- 11 Task 6 (Core task) – DAF CSDR Support (O&M funded, Option CLIN) ----------------------- 11 Task 7 – Surge Support (RDT&E, Option CLIN) --------------------------------------------------- 12 Task 8 – DAF Surge Support (O&M, Option CLIN) ----------------------------------------------- 13

KNOWLEDGE, SKILLS, AND ABILITIES (KSA) --------------------------------------------------- 13 General Requirements------------------------------------------------------------------------------------ 13 Program Manager ----------------------------------------------------------------------------------------- 13 Chief Cost Data Scientist -------------------------------------------------------------------------------- 13 Expert Cost Estimator/Analyst ------------------------------------------------------------------------- 14 Senior Cost Estimator/Analyst -------------------------------------------------------------------------- 15 Journeyman Cost Estimator ----------------------------------------------------------------------------- 16 Junior Cost Estimator ------------------------------------------------------------------------------------ 17 Expert Data Scientist ------------------------------------------------------------------------------------- 17 Senior Data Scientist ------------------------------------------------------------------------------------- 18 Journeyman Data Scientist ------------------------------------------------------------------------------ 19 Junior Data Scientist ------------------------------------------------------------------------------------- 19 CSDR Subject Matter Expert --------------------------------------------------------------------------- 19 On-Demand Subject Matter Expert (SME) ----------------------------------------------------------- 20 Key Positions ---------------------------------------------------------------------------------------------- 20

SERVICE SUMMARY ------------------------------------------------------------------------------------- 20

DELIVERABLES -------------------------------------------------------------------------------------------- 22 Status Reports --------------------------------------------------------------------------------------------- 24 Associate Contractor Interface -------------------------------------------------------------------------- 25 Data Rights ------------------------------------------------------------------------------------------------ 25

EQUIPMENT, MATERIAL, INFORMATION, OR SERVICES ------------------------------------ 26 Equipment, Material, Information, or Services ------------------------------------------------------- 26 Contractor Acquired Property--------------------------------------------------------------------------- 26 ii

GENERAL INFORMATION ------------------------------------------------------------------------------ 26 Duty Hours ------------------------------------------------------------------------------------------------ 26 Place of Performance ------------------------------------------------------------------------------------- 26 Kickoff Meeting/Orientation Meeting ----------------------------------------------------------------- 26 Quality Control. ------------------------------------------------------------------------------------------- 27 Contractor Manpower Reporting Application (CMRA) -------------------------------------------- 28 Travel and Other Direct Costs -------------------------------------------------------------------------- 28 Employee Accountability and Turnover -------------------------------------------------------------- 29 Miscellaneous Paragraphs. ------------------------------------------------------------------------------ 30 Acronyms -------------------------------------------------------------------------------------------------- 32 Applicable Publications ---------------------------------------------------------------------------------- 35 Metadata/Key Word Example -------------------------------------------------------------------------- 38 Data Fidelity Scorecard Example ---------------------------------------------------------------------- 40

INTRODUCTION AND PURPOSE 1

The Department of the Air Force (DAF) has identified numerous gaps in the databases, methods, 2 and tools it regularly uses for cost estimating and analysis and has committed to improving the 3 efficiency and effectiveness of its cost estimating capabilities. This requirement invests in 4 strengthening, accelerating and elevating cost data and analytic capabilities using the latest 5 technologies to enable faster, more efficient, higher quality, and higher volumes of analytic 6 decision support from the DAF cost community. It shifts the focus from desktop-based tools to 7 cloud-based platforms; from stand-alone commodity-based datasets to integrated and relational 8 databases containing programmatic, cost, technical, and schedule information; from static 9 spreadsheets/reports to dynamic analysis and models connected to data pipelines; and from low-10 volume cost data modeling to highly scalable data collection, curation, analysis and models. 11

The objectives include (1) improving the quality and amount of data collected and available to 12 cost estimators, (2) building centralized/ enterprise relational and integrated cost, schedule, and 13 technical databases using data science best practices, (3) building the capability to optimize cost 14 estimators’ use of the larger amounts of data collected for cost estimating, and (4) providing 15 centrally available and authoritative datasets and to develop cost estimating relationships, 16 schedule estimating relationships, technical estimating relationships, benchmark tables, 17 dashboards/visualizations, cost models, and other tools that Air Force and Space Force cost 18 analysts can use to develop detailed, robust, and accurate cost estimates. The goal is to not only 19 improve the timeliness and quality of program life-cycle cost estimates for budgeting, 20 programming, and acquisition decisions but to enhance the capability to perform quick turn high-21 level force design and alternative capability analysis as well as lower level program element 22 trade-off analysis. 23

Thorough and current cost datasets and databases are the cornerstones to the Air Force and Space 24

Force continuously improving the accuracy and consistency of its acquisition program cost 25 estimates required by statute (e.g., Title 10, United States Code § 3222, 3225, 4251, 4252, 4253, 26

4271, and 4328) and regulation (e.g., DoD Instruction (DoDI) 5000.02, DoDI 5000.73, DoDI 27

5000.75, DoDI 5000.80, DoDI 5000.85, DoDI 5000.87, and Air Force Instruction (AFI) 65-508) 28 in support of DAF and Department of War (DoW) acquisition decisions. Moreover, these 29 integrated datasets and databases as well as the accompanying analysis should serve as the basis 30 to what the DAF cost community provides during the Strategy, Planning, Programming, 31

Budgeting, and Execution processes. These analytically based cost estimates must be robust 32 enough to identify available budget trade-space and what the near-term risks are as decision-33 makers balance competing priorities as they aim to deliver critical out-year capabilities to pace 34 the threat. 35

Building credible and defensible cost estimates to assess program affordability and support 36 budget development starts with complete and accurate datasets, sound estimating methods, 37 models, and enterprise tools. This effort addresses focuses on primarily DAF requirements, but 38 the solutions will be made available to benefit the government cost community, including the 39

Office of the Secretary of Defense (OSD) Cost Assessment and Program Evaluation (CAPE) and 40 other service cost agencies, and help it meet its growing demands. 41

TASKS AND TASK REQUIREMENTS 42

The contractor will develop enterprise datasets, methods and tools for use by cost estimators to 43 meet the AFCAA Cost Estimating Modeling Data Analytics and Research (CEMDAR) 44 objectives of an up-to-date, searchable, user-friendly, centrally available data and method 45 repository that enables a high volume and timely delivery of quality, effective cost estimates. 46

The contractor shall adhere to all scheduled timelines, milestones, delivery schedules, and 47 administrative requirements to include scheduled on-time delivery of reports, data products, 48 billing invoices, staffing of personnel, and action item completion. The contractor shall provide 49 the necessary labor, supplies, equipment, and supervision to fulfill this effort as described in the 50 following tasks and subtasks as outlined below. 51

The contractor will systematically and continuously document DAF and joint service cost 52 estimating data requirements, then collect and store the required data, and provide analyses, 53 methods, tools, applications, and models for use by cost estimators. Data will be collected in a 54 manner that ensures complete and accurate documentation and based on the government’s 55 approval, as well as shared within the AFCAA’s cloud-based platform(s) of choice (an 56 appropriately designated platform/system for these products). Currently, for example, this would 57 be within DAF Data Visible, Accessible, Understandable, Linked and Trusted (VAULT) data 58 platform as well as CAPE’s CADE system. 59

The contractor shall be responsible for ensuring the accuracy, timeliness, and completion of all 60 tasks under this effort, Replacement or substitute personnel for vacancies shall be filled with 61 qualified personnel within fourteen (14) business days of vacancy, in accordance with Table 1: 62

Performance ThresholdsTable 1: Performance Thresholds in Section IV, unless approved in writing 63 or otherwise directed by the Contracting Officer (CO). 64

Meetings will include a kickoff meeting within ten (10) business days after the start of the 65 contract award and each exercised option; meetings as needed between the contractor’s Program 66

Manager and AFCAA’s Program Manager to track performance, resolve issues, and ensure 67 compliance with the Performance Work Statement (PWS); status meetings as needed between 68 the contractor’s project leads and the AFCAA technical leads; and quarterly formal reviews to 69 include a final review about 30 calendar days before the end of the period of performance 70 between the contractor and the entire AFCAA government team to include the AFCAA 71

Technical Director, AFCAA Program Manager, and the AFCAA technical leads. All meetings 72 shall use Microsoft Teams as the default choice. Delivering the agenda and recapping the 73 meeting, as outlined in Table 2: Task Order Deliverables in Section VTable 2: Task Order 74

Deliverables, is the contractor’s responsibility for the kickoff meeting and formal reviews, 75 including the final review. 76

The contractor shall provide the COR with all passwords, data collected, processes used, and any 77 other information obtained throughout the contract’s period of performance. The COR will meet 78 with the contractor within 7 business days prior to the end of the contract to ensure all 79 information is received. Once confirmed, the contractor will send a letter to the COR confirming 80 that the data rights requirements (paragraph 0) were completed not later than five business days 81 prior to the end of the contract. 82

Task 1 (Enabling task) – Obtaining Permissions to Access Data Sources 83

Successful performance of this requirement depends on the contractor working proactively with 84 the government to obtain permissions to access government held data. Much of the data in the 85

Cost Assessment Data Enterprise (CADE) repository is from defense contractors and major 86 subcontractors. Each considers its data as business sensitive and subsequently has marked it, or 87 considered it, as proprietary. This requires protecting this information from public disclosure. 88

Since the contractor team while providing these services will be provided or have access to 89 nonpublic information, each person on the contractor and subcontractor team working this effort 90 shall sign a non-disclosure agreements (NDA) with AFCAA (Error! Reference source not 91 found.) and an NDA with OSD CAPE for CADE (Error! Reference source not found.). The 92 contractor and subcontractor team shall work proactively and sign, as required, NDAs with other 93 government organizations to support and fulfill data collection and task requirements. 94

The contractor will work with AFCAA to identify NDA requirements for all Original Equipment 95

Manufacturer (OEM) and major subcontractors. Should an OEM or major subcontractor require 96 an NDA with the contractor, then the contractor shall develop and complete this before AFCAA 97 provides access to this OEM’s or major subcontractor’s government-held data. These NDAs 98 must carry through the entire contract period of performance, including all option contracts. 99

Furthermore, the NDAs should flow equally across the contractor and its subcontractors. 100

As part of its proposal and throughout the duration of this contract, the contractor shall identify 101 and notify per paragraph Error! Reference source not found. the Contracting Officer of any 102

Organizational Conflict of Interest (OCI) it or any of its subcontractors has, or could have, with 103 any OEM or major subcontractor who has submitted reports held in CADE or the Earned Value 104

Management Central Repository (EVMCR). Moreover, the contractor shall notify the 105

Contracting Officer and the AFCAA Program Manager of any acquisition or merger involving 106 itself, or its subcontractors and explain whether that action will cause create a OCI. Similarly, the 107 contractor will identify any other emerging event or action that would create a OCI. 108

Task 2 (Enabling task) – Develop a Plan of Action and Milestones 109

(POA&M) 110

The contractor shall develop and submit, for government review and approval, a POA&M 111 describing the contractor’s approach to satisfy all tasks and elements for data ingestion and 112 curation, analysis, and other task requirements for the base period within 20 business days of 113 contract award and for each option year within 15 business days of the option year start. The 114

POA&M will be a living document that will be modified throughout the entire contract period of 115 performance, including all option periods. 116

a. As part of the kickoff meeting and at the start of the base period and each option 117 period, the contractor and AFCAA will meet to discuss POA&M development and 118 subtasks for inclusion. A draft POA&M shall be delivered for review and comment 119 not later than (NLT) 20 business days after contract performance begins (and within 120

15 business days after each option year begins). The contractor will work with the 121

AFCAA Technical Director, its Technical Leads, and its Program Manager to obtain 122 approval of a final POA&M. The POA&M will include, as a minimum: 123

b. A detailed description of the approach to completing each task (with element level 124 descriptions) and subtask. 125

c. Task and subtask activity and milestone schedule, including interim, draft, and final 126 milestones, products, and contract project deliverables and a description of risk 127 associated with completing the planned schedule. Interim milestones should include 128 any events or progress points that would require a go or no-go decision from the 129 government based on research to-date prior to moving ahead. The schedule will be 130 used for tracking purposes and should be included in eachStatus ReportsStatus 131

Reports. 132

d. The contractor’s plan should include sufficient lead time for the delivery of all project 133 deliverables to allow the government to review and provide feedback. The contractor 134 shall resolve all the government’s comments before any deliverable can be considered 135 final. This shall occur not later than ten business days prior to the end of the contract 136 base period and each contract option year end. 137

e. Each task and subtask will document approvals to collect classified data. This 138 includes tracking potential data aggregation or compilation as determined by program 139 classification guides. The contractor shall ensure the collected data is protected at the 140 appropriate level necessary to safeguard this information. The contractor shall work 141 closely with the AFCAA technical leads to gain approval to collect classified data. 142

f. A management plan explaining the contractor’s approach to staffing, schedule 143 management, business management, and reporting. This plan will track and align to 144 both task and subtask activity and schedule0. The plan will be specific in the Chief 145

Cost Data Scientist and Program Manager (PM) role and activities. 146

g. Plans to format and share CEMDAR deliverables as working documents and to 147 finalize all products for upload onto AFCAA’s cloud-based platform(s) of choice (for 148 example, currently the DAF VAULT data platform), the CADE system, or any other 149 designated repository. These deliverables will include, but are not limited to, all 150 datasets, databases, tools, models, reports, documents, manuals, Data Item 151

Descriptions, training materials, and dictionaries required to upload and share the 152

CEMDAR products. 153

The contractor shall be available to brief the POA&M to the government, along with any risk 154 areas associated with completing the planned schedule, to the AFCAA Technical Director, the 155

Program Manager, and the COR. The POA&M is a ‘living document’ and the contractor will 156 provide recommended changes/updates to the government at the quarterly meetings, or as 157 needed, and will be given direction and/or approvals by the government on the recommended 158 changes/updates to this document. 159

After the government sends its statement of intent to exercise its next option, AFCAA will 160 inform contractor of the specific requirements to be incorporated into the POA&M. The 161 contractor will respond to AFCAA’s requests and update the POA&M as needed. 162

Task 3 (Core task) – Development and Continuous Improvement of Data 163

Pipelines for Enterprise Cost and Technical Analysis 164

Task Objective 166

The contractor shall design, develop, and implement a series of robust, automated data pipelines 167 to integrate disparate data sources into a unified data environment, enabling enhanced cost, 168 schedule, and technical analysis. These pipelines will conform to the organization's defined data 169 operating model and support recurring and ad-hoc analytical needs. The pipelines will be 170 developed in the AFCAA’s platform of choice, optimally utilizing available DAF 171 technologies/toolsets. The ultimate goal is to leverage these data pipelines so that they provide 172 reliable, accurate, and readily accessible data to improve cost estimating methods and other 173 analyses, aligning with the Cost Analysis Data Operating Model (CADOM) 174

Scope of Work 175

The contractor shall perform the following subtasks, as required by AFCAA in the approved 176

POA&M: 177

Cost Analysis Data Operating Model (CADOM) Data Architecture 178

Design/Support 179

• Collaborate with government stakeholders to assist in data architecture design/support 180 as required, to include: 181 o Assistance in conducting assessment of platforms, toolsets and assistance in 182 defining the optimal solution/tech stack meeting all AFCAA’s requirements 183 and considering all constraints. This also includes ensuring innovative 184 methods are utilized throughout the development of the CADOM 185 o Assistance in architecting solutions that meet unique government 186 requirements, such as data and applications that span various classification 187 environments, and spanning users that have different levels of access to data 188 o Assistance in maintaining the Standard Operating Procedures (SOPs) for the 189

CADOM 190

o Assistance in developing and incorporating optimal process user/Subject 191

Matter Expertise (SME) feedback and workflows 192

Data Source Identification and Assessment: 193

• Collaborate with government stakeholders to identify and document relevant data 194 sources across the organization to feed the data pipelines described below. Note that 195 data and data pipelines are expected to include (but are not limited to): Cost and 196

Schedule Data Reporting (CSDR), Earned Value Management (EVM), Selected 197

Acquisition Report (SAR/MSAR), Contracts, Budget, Air Force Total Ownership 198

Cost (AFTOC), etc. 199

• Conduct a comprehensive assessment of each data source, focusing on: 200 o Data Quality: Evaluate data accuracy, completeness, consistency, and fidelity 201 using defined metrics (e.g., leveraging a Data Fidelity Scorecard like the 202 example in reference g of this document). 203 o Data Normalization Requirements: Determine the necessary normalization 204 processes, including inflation/price escalation adjustments, Work Breakdown 205

Structure (WBS) alignment, and Cost Element Structure (CES) 206 standardization. Justify the chosen normalization methods. 207 o Data Availability and Access: Investigate data security classifications, 208 aggregation limitations, proprietary restrictions, access requirements, and 209 control information. Adhere to all applicable security policies and regulations. 210 o Data Source Characteristics: Document any other relevant database 211 characteristics (e.g., data formats, API availability, data update frequency) that 212 may affect data collection, management, and use. 213

Data Pipeline Design and Development: 215

• Design data pipelines that adhere to modern data architecture principles and leverage 216 appropriate technologies (e.g., Apache Spark, Python, R, SQL, Databricks, cloud-217 based data warehousing solutions). 218

• Develop modular, scalable, and maintainable data pipelines for data extraction, 219 transformation, and loading (ETL) processes. 220

• Implement automated data quality checks and validation rules wherever possible and 221 optimal within the pipelines to ensure data accuracy and consistency. 222

• Develop error handling and logging mechanisms to facilitate pipeline monitoring and 223 troubleshooting. 224

• Development/maintenance of a “metadata” data pipeline/layer in order to connect the 225 distinct and disparate datasets with an overarching framework of metadata 226 architecture/fields. This metadata layer shall connect into all the data pipelines to the 227 greatest extent possible such that the user can query fields from the metadata layer 228 and return data at various levels of detail for each of the related data pipelines. 229

Data Ingestion and Transformation: 231

• Ingest data from identified sources into a raw data storage area (e.g., a data lake). 232

• Perform data cleansing, normalization, and transformation operations to conform to 233 the organization's data model. 234

• Create curated data tables and views optimized for analytical queries and reporting. 235

• Implement data lineage tracking to maintain traceability from raw data to transformed 236 data. 237

Data Repository Development and Maintenance: 238

• Organize data tables and views into user-friendly, searchable data repositories (such 239 as a data catalog), leveraging existing available technologies wherever available, and 240 customizing solutions where available technologies are not present in the cloud-based 241 platform of choice. 242

• Ensure the data repositories are optimized for performance and scalability. 243

• Implement data security measures to protect sensitive data. 244

• Develop and maintain data dictionaries and metadata documentation to facilitate data 245 understanding and usage. 246

• Document and maintain data fidelity information (e.g. the data fidelity scorecard 247 example in reference g) to facilitate user data understanding and usage 248

Documentation and Training: 249

• Develop comprehensive and user-friendly documentation for each data pipeline, 250 including data source descriptions, ETL processes, data transformations, data quality 251 checks, and data lineage information. Integrate, wherever possible the documentation 252 for data pipelines within the CADOM architecture in an efficient way (i.e. GitHub, 253 markdown, tooltips, Wiki, etc). 254

• Conduct training sessions for users to demonstrate the use of the data repositories and 255 analytical tools. 256

• Provide detailed documentation for future enhancements and maintainers of the 257 developed pipelines. 258

Continuous Improvement (Once data pipelines have been developed and deployed): 259

• Monitor data pipeline performance and stay abreast of new technologies and best 260 practices in data engineering identify areas for optimization, suggesting potential 261 improvements to AFCAA, where applicable. 262

• Implement regular maintenance and updates to ensure data accuracy and availability. 263

• Respond to user feedback on any issues with the pipeline or products within CADOM 264 and address these issues as well as data quality issues promptly. 265

AFCAA will evolve and adapt its Cost Analysis Data Operating Model (CADOM) over time to 267 adapt to changes/evolutions in available platforms, technologies and toolsets. The current 268

CADOM architecture is pictured in Figure 1 for reference. 269

Figure 1- Current Cost Analysis Data Operating Model (CADOM) Architecture, for reference purposes 273

Data Fidelity ScorecardData Fidelity ScorecardThe contractor shall support AFCAA in 274 collaborations with other cost organizations to identify data sources for collection efforts. These 275 include but are not limited to: the Air Force Life Cycle Management Center, the Space Systems 276

Command, the Air Force Nuclear Weapons Center, the Air Force Sustainment Centers, the Air 277

Force Rapid Sustainment Office, the Naval Cost Agency, the Naval Systems Commands, the 278

Deputy Assistant Secretary of the Army for Cost & Economics, the OSD CAPE, the Department 279 of Homeland Security, the National Aeronautics and Space Administration, the National 280

Reconnaissance Office, the Navy Strategic Systems Program Office, and the Missile Defense 281

Agency. 282

Task 4 (Core task) – Data-Driven Analysis/Studies, Model Development 283 and Application Deployment 284

Metadata/Key Word Example0Metadata/Key Word ExampleData Fidelity 286

Scorecard0Task Objective: 287

The contractor shall perform in-depth cost, schedule, and technical analyses and/or studies, 288 develop dynamic predictive models, custom applications, and insightful visualizations; and 289 deliver actionable recommendations to improve cost estimating methodologies and decision-290 making across the organization, as required by the approved POA&M. The goal of this task is to 291 provide data-driven insights, analysis, and tools tailored to AFCAA's needs. This task will 292 include projects that are intended to be fully deployed within the CADOM, projects that are 293 intended to be fully deployed outside the scope of the CADOM, and those that are a hybrid of 294 these two. This task shall ensure optimal delivery and integration of analysis/studies within the 295

CADOM ecosystem or as standalone deliverables, as determined by AFCAA. The contractor 296 shall leverage, to the greatest extent possible, the existing and future data pipelines developed 297 and delivered in Task 3 for Task 4 projects. The contractor shall assist the government in 298 identification of opportunities to migrate traditional studies/analysis to the CADOM and/or other 299 modern platforms/toolsets wherever synergies and/or efficiencies could be achieved. 300

Scope of Work: 301

The contractor shall develop use cases, dynamic analysis/predictive models, custom applications, 302 and conduct cost and technical studies as required per approved subtasks in the POA&M. The 303 subtasks in the POA&M, depending on the type of task, will include some combination of data 304 analysis, model development, application/tool development, and conducting targeted cost and/or 305 technical studies. Subtasks as defined in the POA&M could fall into one or more of these 306 categories as listed below. Each category is further defined below, along with potential 307 expectations and/or examples of what will be required (each subtask will be clearly defined 308 within POA&M): 309

Data Analysis, Model Development, Cost and/or Technical Studies: 310

• Conduct thorough data analysis and/or develop models using available data pipelines 311 and/or other data sources. 312

• Identify trends, patterns, and relationships within the data relevant to the identified 313 use cases, including but not limited to cost estimating benchmarks, methods, Cost 314

Estimating Relationships (CER), Schedule Estimating Relationships (SER), 315

Technical Estimating Relationships (TER), and other analysis/estimating approaches, 316 as required. 317

• Develop end-to-end cost model architectures and/or models, that could be used as a 318 template/ starting point, early acquisition trades, etc. 319

• Employ appropriate statistical and machine learning techniques to build predictive 320 models that improve forecasting accuracy and risk assessment. 321

• Ensure all models are rigorously tested and validated using appropriate statistical 322 methods. 323

• Conduct targeted studies to meet mission-unique requirements for specific 324 commodities and/or program. 325

• Create interactive dashboards and visualizations that provide insights into key 326 performance indicators and trends. 327

Application and Tool Development: 329

• Design and develop custom applications and tools to support cost, schedule and 330 technical estimating/ analysis. This could include, for example, development of cost 331 and schedule toolsets/applications that could then be leveraged by analysts on specific 332 program’s estimates. 333

• Develop user-friendly interfaces that enable stakeholders to easily access and utilize 334 the developed tools and applications. 335

CADOM Deployment (as required by approved POA&M): 336

• For projects intended for integration/deployment within the CADOM cloud-based 337 platform(s), the contractor shall work with AFCAA to ensure compliance with 338

CADOM architecture, data standards, and security requirements. 339

• Deploy developed models, applications, and tools to the CADOM environment 340 following established SOPs. 341

• Provide any troubleshooting and/or continuous improvement for deployed 342 applications within the CADOM as required 343

Final Product/Report/ Documentation: 345

• To the greatest extent possible, the projects, use cases, applications, dashboards, etc 346 developed within CADOM should be deployed within the cloud-based platform(s) of 347 the government’s choice. They should also leverage integrated documentation native 348 within the platform(s). This could be, for example, code documentation in GitHub, 349 markdown, wikis and/or other existing and custom tool tips/interactive documentation 350 wherever optimal and appropriate. 351

• Certain projects will involve scope both inside and outside of the CADOM. In this 352 case, a hybrid approach could include both deploying models and applications to the 353

CADOM platform, and development of a traditional report/documentation could still 354 be required as well. 355

• For projects outside the scope of the CADOM, or hybrid projects that documentation 356 within CADOM is not feasible, the contractor shall develop comprehensive reports 357 that document the analysis, methodology, findings, and recommendations. 358

• Reports will include the following sections: Purpose, Background, Scope and 359

Limitations, Ground Rules and Assumptions, Methodology (data, normalization 360 process, normalized data, and analytic methods), Risk/Uncertainty, 361

Results/Conclusions/Recommendations. 362

• Data sources used to populate the data collection will be clearly identified and 363 provided as reference material, to include the source data extracted and used when 364 required. 365

• All normalization and analysis must be fully documented in detail so that the analysis 366 can be recreated and normalized data is fully traceable back to the raw data. 367

• All instructions/training materials must be fully documented for 368 repositories/databases/tools developed. Source data and normalized data will be 369 provided in the final deliverable report or delivered dataset/database/tools. 370

Training and Knowledge Transfer: 371

• Develop and deliver training materials and workshops to educate users on the use of the 372 developed tools, applications, and models. 373

• Provide deployment training to users and collect feedback to refine the original training 374 materials 375

• Provide ongoing support to users and address any questions or issues that arise. 376

• Document all development activities and share knowledge with government stakeholders 377 to ensure long-term sustainability. 378

Task 5 (Core task) – Contracts Database (Option CLIN) 380

The contractor shall update an existing AFCAA Contracts Database with additional contract 381 information for programs that already exist in the database as well as add new programs to the 382 database. The contractor shall ensure the fields of the Contracts Database, as it exists in CADOM 383 cloud-based architecture (currently, VAULT), are relatable to metadata from datasets, such as 384

CSDR/FlexFile, SRDR, SAR, and others as identified by AFCAA, ingested per paragraph 385

Error! Reference source not found.. 386

AFCAA will identify new priorities for the Contracts Database at the start of each option period. 387

In addition, the contractor shall perform the following tasks: 388

a. Review lessons learned and business rules for contract growth buckets and redesign 389 features/mapping as necessary for database. 390

b. Incorporate new features per user input and incorporate data fixes for new features 391 not backward compatible yet. Leverage business intelligence (BI) tools for data 392 ingestion, normalization, and visualizations, as appropriate. 393

c. Update user guides for each version of the KDB tools to include new features or other 394 incorporated changes. 395

d. Add new data to the database. Make corrections as needed to data records in the 396 database. 397

e. Provide database updates on a quarterly basis. Ensure delivered versions of the KDB 398 database and associated tools/documents are available to all DoW CADE users, via 399 platform designated by government 400

f. Update training material and provide one combination virtual and in-person (National 401

Capital Region) course to KDB users. Sub-tasks include: 402

i. Updating existing training material to reflect current KDB structure, content, 403 data tagging, etc. 404

ii. Applying the data to cost estimating use cases to include products associated 405 with Task 4 or projects assigned when directed under this task (e.g., 406 engineering change order analysis from data). Error! Reference source not 407 found. 408

iii. Providing a demonstration of the KDB tools and major database updates with 409 an emphasis on how a cost estimator can use these tools. 410

Task 6 (Core task) – DAF CSDR Support (O&M funded, Option CLIN) 411

The DoW requires accurate and reliable cost reporting to inform life cycle cost estimates and 412 programming and acquisition decisions. The data collected from DoW cost reporting forms the 413 basis of these estimates, as mandated by statute and DoW and DAF policies. 414

The contractor shall provide support to the Air Force Cost Analysis Agency (AFCAA) and the 415

DAF Cost Centers to administer the Cost and Software Data Reporting (CSDR) process for 416

ACAT I level DAF programs and all programs delegated to AFCAA for CSDR plan approval, in 417 accordance with DoDI 5000.73, Cost Analysis Guidance & Procedures. This support would 418 include: 419

a. CSDR Planning, Verification and Validation, and Compliance: The contractor shall assist 420

AFCAA, Center Cost Staffs, and the Program Management Office (PMO) in all aspects 421 of planning, validation, and compliance as requested by AFCAA, for example: 422

i. Ensuring timely identification of upcoming solicitations and request for proposal 423

(RFP) releases as well ask tracking current submissions against due dates, etc 424

ii. Ensuring that approved CSDR plans represent the broader cost community data 425 needs for future cost estimating. 426

iii. Ensuring that valid data is submitted as required by the final approved CSD by 427 comparing submissions to plans and prior submissions 428

b. CRSB Support: The contractor shall work with AFCAA, Center Cost Staffs, and the 429

Program Management Office (PMO) to identify issues for the Cost Reporting Standards 430

Board (CRSB) and working with the AFCAA CSDR Process Manager on CRSB 431 recommendations. 432

c. CSDR Process Management: The contractor shall support the AFCAA CSDR Process 433

Manager in management of the entire end to end process of CSDR planning, verification 434 and validation, and compliance for DAF program CSDRs. Note that all actual report 435 approvals will only be accepted by government personnel, but the contractor will 436 function in a support role by performing verification and validation analysis. This will 437 require interaction and collaboration with the support contractor and government staffs of 438 the Office of the Secretary of Defense (OSD) Defense Cost and Resource Center 439

(DCARC) office for DAF ACAT I level programs, and the DAF Cost and Resource 440

Center (DAFCARC) team for DAF ACAT II-III level programs. 441

d. Cost Working Integrated Product Team (CWIPT) Support: The contractor shall support 442 the CWIPT for DAF ACAT I level and ACAT II-III level programs, assisting in the 443 development of a final recommended CSDR plan for approval. 444

Task 7 – Surge Support (RDT&E, Option CLIN) 446

During the performance period of this PWS, the Government may require services that expand 447 beyond the ongoing support anticipated. This optional surge support CLIN provides a pre-448 negotiated mechanism for the Government to acquire additional expertise from cost estimators, 449 data scientists, and technical subject matter experts. The specific tasks and roles covered by this 450 surge support are defined within this PWS. 451

The Government may exercise this option CLIN at its discretion. The decision to invoke this task 452 will be based on the required level of support, project duration, and the availability of project 453 funding. Exercising this option allows the Government to quickly augment the team with pre-454 approved roles and labor rates to meet emergent mission requirements without the delay of a new 455 procurement action. 456

Task 8 – DAF Surge Support (O&M, Option CLIN) 457

During performance identified in this PWS, it is possible that the effort could potentially expand 458 past the anticipated, on-going DAF efforts for Support. This task refers to efforts that the 459 government may exercise at its discretion to obtain cost estimators, data scientists, and technical 460 subject matter experts for surge support to perform specific task descriptions and add these to 461 this contract via this option CLIN for any additional requirements. The government will define 462 specific task descriptions and add these to this contract via this option CLIN. The decision to 463 invoke the task shall be based on the level of support that is required, project length, and the 464 amount of available project funding. 465

Knowledge, Skills, and Abilities (KSA) 466

The contractor is responsible for ensuring its personnel (to include subcontractors) fully comply 467 with the minimum experience and knowledge described in the following paragraphs… labor 468 category… staff appropriate mix of skillsets 469

General Requirements 470

The contractor shall assign personnel to perform tasks outlined in this PWS. The contractor shall 471 notify the PCO of any proposed changes to key personnel. Substitutions of key personnel require 472

PCO approval. Also, the contractor can request from the AFCAA Program Manager and COR 473 waiver considerations for years of experience should a candidate possess unique or hard to find 474 skills. Administrative and clerical support under this contract is not considered a direct task or 475 labor category. 476

Program Manager 477

The Program Manager manages the coordination and completion of tasks and subtasks/projects 478 on time, within budget, and within scope. The Program Manager assigns responsibilities, leads 479 and directs the work of others, works with project leads to set deadlines, and monitors project 480 timelines. He or she prepares reports regarding the status of each project. A wide degree of 481 creativity and latitude is expected from the Program Manager. 482

The Program Manager requires a Bachelor of Science or Bachelor of Arts degree from an 483 accredited college or university and experience in the program management field or in a related 484 area and familiarity with management concepts, practices, and procedures. This person must 485 have a minimum of five (5) years managing projects of comparable scope to the CEM effort and 486 experience in managing similar cost estimating projects. 487

Chief Cost Data Scientist 488

The contractor shall provide an individual to serve as the Chief Cost Data Scientist. The Chief 489

Cost Data Scientist is required to manage and oversee all CEMDAR contractor activities from a 490 technical standpoint, including subcontractors, to satisfy the requirements identified in this PWS. 491

The Chief Cost Data Scientist is expected to seek innovative and transformative methods to meet 492 the objectives of this requirement. His or her responsibilities include ensuring technical content 493 quality, commonality, and configuration compliance across all tasks. 494

The Chief Cost Data Scientist requires a Bachelor of Science or Bachelor of Arts degree from an 495 accredited college or university and personnel in this category must have a minimum of three (3) 496 years performing projects of comparable scope to the CEM effort, a minimum of eight (8) years 497 as a data scientist, as well as five (5) years in cost estimating/analysis. The Chief Cost Data 498

Scientist shall demonstrate the following: 499

a. Leadership in Data Science – Experience in leading cross-functional teams of data 500 scientists, data engineers, and data/cost analysts. Proven ability to define and 501 articulate a data strategy aligned with organizational goals, identifying opportunities 502 for leveraging data to drive business growth and innovation. 503

b. Integration of Capabilities – Expertise in integrating advanced data science 504 capabilities with existing processes and technologies, ensuring alignment and 505 maximizing efficiency across departments. 506

c. Stakeholder Engagement – Exceptional communication skills to engage with 507 stakeholders, translating complex data insights into actionable strategies and 508 recommendations for business decisions. 509

d. Innovation – Demonstrated history of driving research and development initiatives in 510 machine learning and Artificial Intelligence (AI), exploring cutting-edge technologies 511 and methodologies to keep the organization at the forefront of data science 512 advancements. 513

e. Cost Estimating Experience – Knowledge and experience in performing cost 514 estimating and analysis on major defense systems including typical work breakdown 515 structures, standard cost data (e.g., CSDRs, AFTOC O&S data), development of cost 516 estimating relationships and analogy estimating, and basic cost estimating experience 517

Expert Cost Estimator/Analyst 518

The contractor shall provide expert cost estimators or cost analysts that have comprehensive and 519 in-depth experience in cost analysis and mastery of Air Force and/or Space Force weapons 520 systems. The contractor shall provide expert cost estimators/analysts who can integrate 521 seamlessly with and mentor other weapons system cost estimators/analysts. These expert cost 522 estimators/analysts must have expertise in cost analysis principles including but not limited to: 523

a. Cost estimating – Recognized expertise in DAF weapon systems, including 524 innovative estimating methodologies that optimize data collection parameters. 525

Demonstrated mastery of DAF weapon systems as well as system-specific 526 programmatic and technical cost drivers associated with both acquisition and 527 operating and support (O&S) phases of an acquisition program’s life cycle. Proven 528 ability to develop new cost estimating methodologies. 529

b. Data collection – Mastery of collecting and normalizing cost, technical, and 530 programmatic data from government entities. Extensive knowledge of the Defense 531

Cost and Resource Center (DCARC) data collection process and deep experience in 532 the use of and analysis of the Cost and Software Data Reports (CSDR) and Integrated 533

Program Management Reports (IPMR)/Contract Performance Reports (CPR). Expert 534 knowledge of the Air Force Total Ownership Cost (AFTOC) system and ability to 535 improve the system. 536

c. Leading teams – Proven ability to lead and mentor cost research project teams to 537 successful conclusions. 538

d. Data analysis and cost tools – Mastery of data analysis and developing advanced 539 cost estimating methods and tools. Can serve as a SME to others. 540

e. Experience – Must have at least fifteen (15) years of cost analysis experience. 541

Senior Cost Estimator/Analyst 543

The contractor shall provide senior cost estimators or cost analysts that have significant 544 experience in cost analysis and expertise with Air Force and/or Space Force weapons systems. 545

The contractor shall provide senior cost estimators or analysts who can integrate with the other 546 weapons system cost estimators or analysts. These senior cost estimators/analysts must have 547 experience in cost analysis principles including but not limited to: 548

a. Cost estimating – Demonstrated expertise in DAF weapon systems, specifically 549 estimating methodologies that facilitate identification of data collection parameters. 550

Includes an in-depth understanding of DAF weapon systems as well as system-551 specific programmatic and technical cost drivers associated with both acquisition and 552 operating and support (O&S) phases of an acquisition program’s life cycle. 553

b. Data collection – Demonstrated expertise collecting and normalizing cost, technical, 554 and programmatic data from government entities. Knowledge of the Defense Cost 555 and Resource Center (DCARC) data collection process and demonstrated experience 556 in the use of and analysis of the Cost and Software Data Reports (CSDR) and 557

Integrated Program Management Reports (IPMR)/Contract Performance Reports 558

(CPR). Knowledge of the Air Force Total Ownership Cost (AFTOC) system 559

c. Leading teams – Demonstrated ability to lead cost research project teams to 560 successful conclusions. 561

d. Data analysis and cost tools – Demonstrated knowledge and demonstrated 562 expertise/ability to analyze data and develop cost estimating methods and tool. 563

e. Experience – Must have at least ten (10) years of cost analysis experience. 564

The contractor shall ensure they have identified individuals in each one of the following 565 categories for senior level cost and commodity specific Subject Matter Expertise (SME). The 566 individuals identified need to be either currently on staff and/or contractor must have the ability 567 to onboard SMEs within the timeframe they are needed to support requirements, per the 568 approved POA&M schedule. Senior Cost Analysts should have at minimum 10 years of 569 experience in cost analysis as well as years of experience as identified each of the commodity 570 areas. The requirement for individual commodity experience necessary is subject to vary each 571 year, per approved POA&M. 572

Senior Cost Estimator/Analyst – Aircraft SME 574

Must have at minimum 10 years of experience in cost analysis as well as at least seven 575

(7) years of progressive DoW, e.g., Navy, Army, MDA, and other DoW organizations. 576

Preferably Air Force/ Space Force ACAT I threshold level aircraft acquisition program 577 cost analysis experience. 578

Senior Cost Estimator/Analyst – Space and Launch Systems SME 579

Must have at minimum 10 years of experience in cost analysis as well as at least seven 580

(7) years of progressive DoW, e.g., Navy, Army, MDA, and other DoW organizations. 581

Preferably Air Force/ Space Force ACAT I threshold level acquisition program cost 582 analysis experience. 583

Senior Cost Estimator/Analyst – Tactical Missiles SME 585

Must have at minimum 10 years of experience in cost analysis as well as at least seven 586

(7) years of progressive DoW, e.g., Navy, Army, MDA, and other DoW organizations. 587

Preferably Air Force/ Space Force ACAT I…