CEMDAR PWS ID 3.13.26.pdf

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)

March 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 -------------------------------------------------------- 5 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) ----------------------- 12 Task 7 – Surge Support (RDT&E, Option CLIN) --------------------------------------------------- 13 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 -------------------------------------------------------------------------------- 14 Expert Cost Estimator/Analyst ------------------------------------------------------------------------- 14 Senior Cost Estimator/Analyst -------------------------------------------------------------------------- 15 Journeyman Cost Estimator ----------------------------------------------------------------------------- 17 Junior Cost Estimator ------------------------------------------------------------------------------------ 17 Expert Data Scientist ------------------------------------------------------------------------------------- 18 Senior Data Scientist ------------------------------------------------------------------------------------- 18 Journeyman Data Scientist ------------------------------------------------------------------------------ 19 Junior Data Scientist ------------------------------------------------------------------------------------- 19 CSDR Subject Matter Expert --------------------------------------------------------------------------- 20 On-Demand Subject Matter Expert (SME) ----------------------------------------------------------- 20 Key Positions ---------------------------------------------------------------------------------------------- 21

SERVICE SUMMARY ------------------------------------------------------------------------------------- 21

DELIVERABLES -------------------------------------------------------------------------------------------- 23 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 ------------------------------------------------------------------------------------- 27 Kickoff Meeting/Orientation Meeting ----------------------------------------------------------------- 27 Quality Control. ------------------------------------------------------------------------------------------- 28 Contractor Manpower Reporting Application (CMRA) -------------------------------------------- 28 Travel and Other Direct Costs -------------------------------------------------------------------------- 28 Employee Accountability and Turnover -------------------------------------------------------------- 29 Miscellaneous Paragraphs. ------------------------------------------------------------------------------ 30 Acronyms -------------------------------------------------------------------------------------------------- 33 Applicable Publications ---------------------------------------------------------------------------------- 36 Notional Plan of Action and Milestones -------------------------------------------------------------- 39 Metadata/Key Word Example -------------------------------------------------------------------------- 40 Data Fidelity Scorecard Example ---------------------------------------------------------------------- 42

APPENDIX A: EXAMPLE LIST OF PROJECTS ----------------------------------------------------- 45

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, systems utilized are 57 withing the DAF Data Fabric and include DAF Data Visible, Accessible, Understandable, 58

Linked and Trusted (VAULT) data platform and Envision platform. 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 f91 ound.) 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 proactively with AFCAA to identify NDA requirements for all Original 95

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

As part of its proposal and throughout the duration of this contract, the contractor shall identify 102 and notify per paragraph Error! Reference source not found. the Contracting Officer of any O103 rganizational Conflict of Interest (OCI) it or any of its subcontractors has, or could have, with 104 any OEM or major subcontractor who has submitted reports held in CADE or the Earned Value 105

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

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

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

(POA&M) 111

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

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

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

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

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

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

c. Task and subtask activity and milestone schedule, including interim, draft, and final 127 milestones, products, and contract project deliverables and a description of risk 128 associated with completing the planned schedule. Interim milestones should include 129 any events or progress points that would require a go or no-go decision from the 130 government based on research to-date prior to moving ahead. The schedule will be 131 used for tracking purposes and should be included in each Status 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 are protected at 140 the appropriate level necessary to safeguard this information. The contractor shall 141 work closely with the AFCAA technical leads to gain approval to collect classified 142 data. 143

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

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

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

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

CEMDAR products. 154

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

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

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

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

Pipelines for Enterprise Cost and Technical Analysis 165

Task Objective 167

The contractor shall design, develop, and implement a series of robust, automated data pipelines 168 to integrate disparate data sources into a unified data environment, enabling enhanced cost, 169 schedule, and technical analysis. These pipelines will conform to the organization's defined data 170 operating model and support recurring and ad-hoc analytical needs. The pipelines will be 171 developed in the AFCAA’s platform of choice, optimally utilizing available DAF 172 technologies/toolsets. Currently, systems utilized are withing the DAF Data Fabric and include 173

DAF Data Visible, Accessible, Understandable, Linked and Trusted (VAULT) data platform and 174

Envision platform, but this is subject to change over time as the DAF Data Fabric evolves.The 175 ultimate goal is to leverage these data pipelines so that they provide reliable, accurate, and 176 readily accessible data to improve cost estimating methods and other analyses, aligning with the 177

Cost Analysis Data Operating Model (CADOM) 178

Scope of Work 179

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

POA&M: 181

Cost Analysis Data Operating Model (CADOM) Data Architecture 182

Design/Support 183

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

CADOM 194

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

Matter Expertise (SME) feedback and workflows 196

Data Source Identification and Assessment: 197

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

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

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

Cost (AFTOC), etc. AFCAA will work with pipeline owners to allow access as 203 needed to the contractor team. 204

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

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

Data Pipeline Design and Development: 220

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

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

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

• Develop error handling and logging mechanisms to facilitate pipeline monitoring and 228 troubleshooting. 229

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

Data Ingestion and Transformation: 236

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

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

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

• Implement data lineage tracking to maintain traceability from raw data to transformed 241 data. 242

Data Repository Development and Maintenance: 243

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

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

• Implement data security measures to protect sensitive data. 249

• Develop and maintain data dictionaries and metadata documentation to facilitate data 250 understanding and usage. 251

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

Documentation and Training: 254

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

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

• Provide detailed documentation for future enhancements and maintainers of the 262 developed pipelines. 263

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

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

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

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

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

CADOM architecture is pictured in Figure 1 for reference. 274

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

Data Fidelity Scorecard. The contractor shall support AFCAA in collaborations with other cost 279 organizations to identify data sources for collection efforts. These include but are not limited to: 280 the Air Force Life Cycle Management Center, the Space Systems Command, the Air Force 281

Nuclear Weapons Center, the Air Force Sustainment Centers, the Air Force Rapid Sustainment 282

Office, the Naval Cost Agency, the Naval Systems Commands, the Deputy Assistant Secretary 283 of the Army for Cost & Economics, the OSD CAPE, the Department of Homeland Security, the 284

National Aeronautics and Space Administration, the National Reconnaissance Office, the Navy 285

Strategic Systems Program Office, and the Missile Defense Agency. 286

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

Data Fidelity Scorecard Task Objective: 290

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

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

Scope of Work: 304

The contractor shall develop use cases, dynamic analysis/predictive models, custom applications, 305 and conduct cost and technical studies as required per approved subtasks in the POA&M. The 306 subtasks in the POA&M, depending on the type of task, will include some combination of data 307 analysis, model development, application/tool development, and conducting targeted cost and/or 308 technical studies. Subtasks as defined in the POA&M could fall into one or more of these 309 categories as listed below. Each category is further defined below, along with potential 310 expectations and/or examples of what will be required (each subtask will be clearly defined 311 within POA&M). To facilitate planning and illustrate the scope of work under this task, a 312 representative list of example projects is provided in Appendix A. These projects are indicative 313 of the types of data-driven analyses, studies, and model development efforts that will be executed 314 annually for the base year and each subsequent option year. The Government will introduce new 315 projects each year. It is understood that project timelines will vary; some larger projects may 316 span several years, while others may be completed in less than a year. Furthermore, it is 317 acknowledged that for many of the studies undertaken, readily available data may not exist, and 318 data collection and normalization will be a key component of the research effort. 319

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

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

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

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

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

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

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

• Ensure all models are rigorously tested and validated using appropriate statistical 332 methods. 333

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

• Create interactive dashboards and visualizations that provide insights into key 336 performance indicators and trends. 337

Application and Tool Development: 340

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

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

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

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

CADOM architecture, data standards, and security requirements. 350

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

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

Final Product/Report/ Documentation: 356

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

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

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

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

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

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

Results/Conclusions/Recommendations. 373

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

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

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

Training and Knowledge Transfer: 382

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

• Provide deployment training to users and collect feedback to refine the original training 385 materials 386

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

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

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

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

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

Error! Reference source not found.. 398

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

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

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

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

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

d. Add new data to the database. Make corrections as needed to data records in the 408 database. 409

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

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

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

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

ii. Applying the data to cost estimating use cases to include products associated 417 with Task 4 or projects assigned when directed under this task (e.g., 418 engineering change order analysis from data). Error! Reference source not f419 ound. 420

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Board (CRSB) and working with the AFCAA CSDR Process Manager on CRSB 443 recommendations. 444

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

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

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

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

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

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

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

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

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

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

Knowledge, Skills, and Abilities (KSA) 478

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

General Requirements 482

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

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

Program Manager 489

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

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

Chief Cost Data Scientist 500

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

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

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

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

Scientist shall demonstrate the following: 512

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

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

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

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

e. Cost Estimating Experience – Knowledge and experience in performing cost 527 estimating and analysis on major defense systems including typical work breakdown 528 structures, standard cost data (e.g., CSDRs, O&S, EVM, SAR, Budget data), 529 development of cost estimating relationships and analogy estimating, and basic cost 530 estimating experience 531

Expert Cost Estimator/Analyst 532

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

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

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

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

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

Program Management Reports (IPMR)/Contract Performance Reports (CPR). 548

Extensive knowledge of DoW VAMOSC Systems, e.g., AFTOC, Navy VAMOSC, 549

OSMIS, EVAMOSC. 550

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

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

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

Senior Cost Estimator/Analyst 557

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

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

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

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

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

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

(CPR). Knowledge of DoW VAMOSC Systems, e.g., AFTOC, Navy VAMOSC, 573

OSMIS, EVAMOSC.Leading teams – Demonstrated ability to lead cost research 574 project teams to successful conclusions. 575

c. Data analysis and cost tools – Demonstrated knowledge and demonstrated 576 expertise/ability to analyze data and develop cost estimating methods and tool. 577

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

The contractor shall ensure they have identified individuals in each one of the following 579 categories for senior level cost and commodity specific Subject Matter Expertise (SME). One 580 individual may qualify for multiple commodity areas.