DRAFT_DSAM Effort_PWS.docx

Final Performance Work Statement (PWS) Research and Development for Cost Estimating Modeling (CEM) Datasets, Analysis and Methods (DSAM) Development Effort for Air Force Cost Analysis Agency (AFCAA)

December 4, 2020

Contents

SECTION I

INTRODUCTION/BACKGROUND:

1.1 General. The DoD cost community, the Office of the Secretary of Defense (OSD) Cost Assessment and Program Evaluation (CAPE), the service cost centers, and the Air Force Cost Analysis Agency (AFCAA) have committed to improving the efficiency and effectiveness of our cost estimating capabilities. The Air Force (AF) has identified numerous gaps in the databases, methods, and tools they regularly use for cost estimating and analysis. Although this effort addresses these gaps for the Air Force, the solutions will be made available to the entire cost community, leading to improved quality, timeliness and effectiveness of DoD acquisition program cost estimates.

1.1.1 Scope: The Contractor shall ensure Contractor personnel take action to fully integrate into this contract supporting ensuring a seamless Government-Contractor team. The Contractor shall manage contractor personnel. This is a follow-on requirement. The Dataset, Analysis & Methods (DSAM) Increment 2 effort begins new Research & Development similar in nature to the previous effort but focused on different gaps and requirements for dataset, tools, and methods development and associated knowledge based studies. AFCAA’s DSAM Effort provides and enhances Air Force-wide cost estimating capabilities by developing current cost data and estimating methods and tools. It develops/modernizes cost data, methods and tools throughout all major AF commodities for use by AF and DoD. In collaboration with the OSD Cost Assessment Data Enterprise (CADE) project, these products will improve the quality, timeliness, and effectiveness of the acquisition program cost estimates required by statute (e.g., 10 USC2366, 2433, 2434) and regulation (e.g., DoDI 5000.73, AFI 65-508) in support of Air Force and Department of Defense acquisition decisions, programming and execution decisions, and Congressional mandates.

1.2 Background: The objective is to research, analyze, design and modernize current cost, technical, and programmatic data and estimating methods and tools. In collaboration with the OSD Cost Assessment Data Enterprise (CADE) project, this research, analysis, and assessment will improve the quality, timeliness, and effectiveness of the acquisition program cost estimates required by statute (e.g., 10 USC 2366, 2433, 2434) and regulation (e.g., DoD Instruction 5000.02) in support of the Air Force and DoD acquisition decisions, programming and execution decisions, and Congressional mandates.

The current DSAM contract is supported by Tecolote Research, Inc. #FA7014-16-C-5009, period of performance is 30 September 2016 - 29 September 2021. In 2014, SAF/FM identified and funded the RDT&E cost estimating modeling (CEM) requirement, of which the DSAM effort is a major part. The 2018 National Defense Strategy (NDS) acknowledged one of the Department’s lines of effort is reforming its business practices to deliver performance at the speed of relevance, while using streamlined approaches. The DSAM effort actively updates datasets/methods/tools for emerging technologies/systems throughout all major AF commodities and supports the on-going development of the AF cost estimating infrastructure. Building credible and defensible cost estimates to support budget development and assess program affordability starts with thorough datasets, methods, and tools and enables the AF cost community meet its growing demands.

SECTION II

2.0 Task Descriptions: The contractor will use data collection efforts to develop methods and tools for use by cost estimators to meet the AFCAA CEM objectives of an up-to-date, searchable, user-friendly, centrally available data and method repository that enables higher volume and timely delivery of higher quality, effective cost estimates. In addition, the contractor will provide surge support as identified when required through an option Contract List Item Number (CLIN) that may satisfy AFCAA CEM requirements, other AFCAA or Secretary of the Air Force, Financial Management & Comptroller, Cost and Economics (SAF/FMC) mission requirements, or the requirements of other organizations (e.g., technical assessment for specific program estimate, AFCAA or program office estimating support for a specific special project, cost research of joint interest but for another cost organization). The contractor shall provide all deliverables, material, equipment, labor and supplies, tools, transportation, supervision and other expenditures necessary to fulfill this effort as described in the following tasks and subtasks for each of the weapon system commodity groups outlined below.

These tasks will systematically and continuously document Air Force and associated joint service cost estimating data requirements, then collect, store, and retrieve the required data, and provide analyses and tools for use by cost estimators. Data will be collected for all listed commodity areas in a manner that ensures collected data is documented fully and, based on sponsor approval, shared within OSD CAPE’s CADE system and/or the appropriately designated repository for these products. The following weapon system commodity groups are focus areas for the tasks described in this contract:

The contractor shall be directly responsible for ensuring the accuracy, timeliness, and completion of all tasks under this effort, none of which are considered inherently governmental functions as defined in FAR 2.101 or Subpart 7.5. Replacement or substitute personnel for vacancies shall be filled with qualified personnel within five (5) business days of vacancy, in accordance with paragraph 10.7 and paragraph 4.0 unless approved in writing or otherwise directed in advance by the Contracting Officer (CO) or the Contracting Officer Representative (COR).

The contractor shall meet with the AFCAA COR and AFCAA Program Manager (PM) to track performance, resolve issues and ensure compliance with this Performance Work Statement (PWS). The contractor shall provide meeting minutes. Meetings will include, as a minimum, an initial kick-off meeting within ten (10) business days after contract award, weekly status meetings between the contractor Integrated Technical Manager (ITM), Program Manager (reference paragraph 4.0) and AFCAA PM, weekly status meetings between the contractor commodity leads and the AFCAA commodity Technical Leads (TLs), and quarterly in-person/virtual formal reviews between the contractor and the entire AFCAA government team to include the AFCAA Technical Director (TD), AFCAA PM and the AFCAA TLs, interim/ad-hoc, in-person or teleconference meetings with the AFCAA TD, AFCAA/PM and AFCAA TLs as required, and an in-person final review at least 30 calendar days before the end of the period of performance. With the exception of the quarterly and final meetings, all other meetings will be informal and will use teleconferencing or government provided on-line conferencing resources as much as possible. Interim and final products will be presented. Meeting agenda and meeting minutes for this program are the contractor’s responsibility, as outlined in Section 5.0 – Deliverables.

2.1 Task Descriptions

2.1.1 Task 1 – Establish Required Nondisclosure Agreements (NDAs)

2.1.1.1 The contractor shall sign all required NDAs with AFCAA (see Attachment D). The contractor also shall sign all required NDAs with OSD CAPE for CADE (see Attachment E). The contractor will sign, as required, NDAs with other government organizations to support and fulfill all contract task requirements.

2.1.1.2 The contractor shall develop and sign NDAs with the source agencies (government, weapon system type and/or cost category vendors, commercial and non-government) to access and evaluate program data sources. During the period of performance for all tasks, the contractor will work with AFCAA to identify NDA requirements for all Original Equipment Manufacturer (OEM) contractors and major subcontractors, and ensure actions to complete NDAs are finalized. The contractor must, within six (6) months of contract award, have all necessary NDAs to ensure full and open access at a minimum to all Department of Defense (DoD) programs, past and present, with no limitations to the data within CADE. The contractor must assist in identifying other non-Air Force programs for data collection, and ensure full and open access to data subject to applicable security and/or proprietary rights for all identified OEM contractors and major subcontractors for those identified programs. NDAs must carry through the entire contract period of performance, including all option contracts (if applicable). The contractor is required to provide signed NDAs for all contractor and subcontractor personnel working on this contract to the COR.

2.1.2 Task 2 – Develop a Plan of Action and Milestones (POA&M) for the Tasks and Sub-tasks

The contractor shall develop and submit, for government review and approval, a POA&M describing the contractor’s approach to satisfy all task and elements for data, study or other subtask requirements within each weapon system commodity group within forty-five (45) calendar days after contract award. The contractor and AFCAA will meet within 14 calendar days after contract award to discuss POA&M development planning and subtasks for inclusion. A draft POA&M shall be delivered for review and comment no later than thirty (30) calendar days after contract award. A final POA&M approved by the AFCAA TD, TLs, PM, and COR shall be delivered no later than sixty (60) calendar days after contract award. The POA&M will include, as a minimum:

a. A detailed description of the approach to complete each task (with element level descriptions), and subtask to include any risk associated with each task and subtask and a template or example of the final deliverable.

b. Task and subtask activity and milestone schedule, including interim, draft, and final milestones, products, and contract project deliverables and a description of risk associated with completing the planned schedule. Interim milestones should include any events or progress points that would require a go or no-go decision from the government based on research to-date to move forward. The schedule will be used for tracking purposes and should be included in each monthly report (reference paragraph 5.1).

c. A management plan explaining the contractor’s approach to staffing, schedule management, business management and reporting. This plan will track and align to task and subtask activity and milestone schedule outlined in paragraph 3.1.2.b. The plan will be specific in the ITM/PM roles and activities (reference paragraph 4.1).

d. Plans to format and share DSAM deliverables as working documents and to finalize all products for upload onto the CADE system or other designated repositories that will host DSAM developed deliverables. These deliverables will include, but are not limited to, all datasets, databases, tools, models, reports, documents, manuals, Data Item Descriptions, training materials, and dictionaries required to upload and institutionalize the collection and sharing of the DSAM products.

The contractor shall be available to brief the POA&M to the government, along with any risk areas associated with completing the planned schedule, in person to the AFCAA TD, PM and COR. The POA&M is a ‘living document’ and the contractor will provide recommended changes/updates to the government at the quarterly meetings, or as needed, and will be given direction and/or approvals by the government on the recommended changes/updates to this document.

2.1.2.1 Specific Sub-task Plan. Each study or analysis sub-task requirement identified by the COR or PM under this task will be described to the contractor through a written request, to include the scope, objective, desired overarching schedule and desired outcomes for the study or analysis. The contractor will then provide a detailed Project Plan to describe the approach, staffing, scaling, detailed schedule, deliverables, expected difficulties and resources required for each sub-task. On the schedule, the contractor will provide a list of milestones that will be used to determine the project’s probability of success based on data availability.

2.1.2.2 Annual Reviews. The contractor shall hold an annual meeting with all of the AFCAA stakeholders to update, review, develop and provide recommendations to the government addressing new data collected, POA&M, and research roadmap. The COR will inform the contractor of the type of meeting, the subject matter, and what, if anything, will be needed to be provided at the meeting.

2.1.3 Task 3 – Perform Studies/Analysis, Develop Organized Datasets and Methods Tools, and Develop Other Analytic Approaches for Cost Estimating

The contractor shall perform data collection efforts for multiple weapon systems and commodities in order to develop datasets, databases, methods, models, and tools and to perform cost and technical studies and analysis to improve cost estimating methods. Per the POA&M requirements and approved subtask plans under this task, the contractor will collect data and perform all necessary analysis activities to complete the requirements. Each subtask project plan will provide further information on how the following elements will be accomplished, or as applicable identify which elements are not included as part of that subtask. All new raw and normalized datasets will be organized into searchable, user-friendly data repositories/databases for use in analyses by cost estimators. The contractor will provide AFCAA an analysis of options for organizing the datasets, databases, or other related tools for storage, retrieval, visualization, and use by cost estimators. Options will always include a CADE system option and Contractor off the Shelf (COTS) based approaches before considering non-COTS approaches. Pros/cons, risks/opportunities, and recommendations will be presented to AFCAA for decision before proceeding with a course of action for developing the organized datasets and repositories/databases/tools/models. Instructions/training materials will be developed and tested on small user groups to ensure accurate usability by cost estimators of repositories/databases/tools developed from this task.

2.1.3.1 Element 1 – Analysis of Data Sources and Data Availability While collecting data, the contractor shall continue to compare the data templates provided by the government against all data sources to identify gaps in the data available for existing programs, and use the information to develop data collection plans under Task 3. The contractor shall identify and recommend new studies, documents, or data sources found during this task that should be incorporated into plans to complete requirements.

The contractor’s review of any additional sources identified during this task shall establish, as a minimum:

a. Research of existing literature and data sets germane to the specific studies;

b. Data storage – how is data stored and maintained, and is the data accessible by the government (e.g., storage medium, non-disclosure requirements);

c. Data quality – accuracy, completeness, and fidelity of data;

d. Data normalization and the basis for the normalization (e.g., inflation/price escalation indices, work breakdown structures, cost element structures);

e. Data availability and access – security classifications, proprietary/competitive restrictions, access requirements and control information to include uniform resource locators (URL);

f. Other source database characteristics that will affect data collection, management and use by the government;

g. Ability to incorporate/integrate the data source into the CADE.

2.1.3.3 Element 2 – Data Collection, Normalization, and Dataset/Database Development The contractor shall work with the AFCAA COR, PM, and TLs to develop a data collection plan to collect data for selected on-going and historical programs. The PM with the AFCAA TLs will identify the programs to be pursued given the time and resources available. The data collection plan will describe the approach to collect the data, which includes developing a schedule across the entire contract period of performance and identifying all potential sources. It is important that time phased as well as total data requirements are fully considered and included in data source evaluations and are described in the data collection plan. Prior to starting any data collection effort, the contractor shall first compare existing data sources (e.g., as identified in Element 1, in CADE, or from other sources) to identify specific data elements that have not yet been collected/organized into a useable dataset according to this contract’s requirements.

Following the COR or the PM approval of the schedule and approach recommended for each source, the contractor shall collect data from AFCAA approved sources. The precedence for data collection will be Air Force programs and databases; other DoD sources; other government sources; weapon system type and/or cost category vendor databases; all other commercial (non-government) sources. Government sources and databases will be used to the maximum extent practical before evaluating non-government sources. Existing data sources for available data will be used to the fullest extent possible prior to contacting government program offices or industry data sources for missing, incomplete or inaccurate data elements. The COR and/or TL and the contractor will jointly decide which programs and associated government/industry organizations/agencies will be contacted.

The contractor shall collaborate with other cost organizations in data collection efforts to include but not limited to Air Force Life Cycle Management Center, Space and Missile Systems Center, Air Force Nuclear Weapons Center, Air Force Sustainment Center, Air Force Rapid Capabilities Office and Air Force Rapid Sustainment Office staff and program offices, Naval Center for Cost Analysis, Naval Air Systems Command, Deputy Assistant Secretary of the Army for Cost & Economics, OSD CAPE, Department of Homeland Security, National Aeronautics and Space Administration, National Reconnaissance Office, Navy Strategic Systems Program Office, and the Missile Defense Agency. All information collected will be normalized to include the creation of metadata not collected via the raw data collection. Data normalization plans must be provided for approval by the AFCAA TL and PM prior to the start of normalization analysis and normalization dataset/database creation.

2.1.3.3 Element 3 – Studies, Analysis, Methods, and Tools Development The contractor shall perform cost and technical studies and analysis as required per approved subtasks in the POA&M. The contractor shall develop/validate cost estimating benchmarks, methods, Cost Estimating Relationships (CERs), Schedule Estimating Relationships (SERs), technical data, factors or other analysis/estimating approaches per subtasks approved in the POA&M. Documentation must clearly trace all developed methods, benchmarks, CERs, SERS, or other analysis back to the originating data used as a basis. As required by the COR or PM, datasets with methods models/tools (e.g. CERs, factors, benchmarks) will be organized into searchable, user-friendly models/tools for use in analysis by cost estimators. Datasets with methods model/tool options will always include a CADE system option and COTS based approaches before considering non-COTS approaches. Pros/cons, risks/opportunities, and recommendations will be presented to AFCAA for decision before proceeding with a course of action for developing these analysis tools. All approaches will be designed with the goal of ensuring the tools can be easily integrated/incorporated into CADE. Instructions/training materials will be developed and tested on small user groups to ensure accurate usability of methods and tools developed from this task by cost estimators Datasets/Databases/Tools/Models will be fully documented to include user instructions/training materials, tool maintainer standard operating procedures/instructions/materials, study abstract, and metadata/key word search criteria based on the template provided in Attachment I. For tools and models, instructions/training materials will be developed and tested on small user groups to ensure accurate usability of repositories/databases/tools developed from this task by cost estimators. All models/tools are to use data that are clearly accessible and traceable to the raw and normalized datasets used as a basis for methods.

2.1.3.4. Documentation. All studies, analyses, datasets, databases, methods tools, analytic approaches, and other reports generated by the contractor under this task will be documented by a formal report and/or database delivered to the COR and PM no later than ten (10) business days after the end of the study or data collection effort, and in accordance with (IAW) all documentation deliverables required per the POA&M. Datasets/Databases/Tools/Models will be fully documented to include user instructions/training materials, dataset/database/tool maintainer standard operating procedures and instructions/materials, study abstract, and metadata/key word search criteria based on the template provided in Attachment I. Additional guidance is below for reports and datasets/databases:

2.1.3.4.1 Report. Each report will be in the contractor’s recommended format, but will include as a minimum the following sections: Purpose, Background, Scope and Limitations, Ground Rules and Assumptions, an explanation of the Methodology (Data, Normalization process, normalized data, and Analytic methods), Risk/Uncertainty, and Results/Conclusions/ Recommendations. Data sources used to populate the data collection will be clearly identified and provided as reference material, to include the source data extracted and used when required. The data will be organized and provided in the current AFCAA approved format at the time of submission. All normalization and analysis must be fully documented in enough detail that the analysis can be recreated by another junior cost estimator and normalized data is fully traceable back to the raw data. Instructions/training materials must be fully documented for repositories/databases/tools developed. Source data and normalized data will be provided in the final deliverable report or delivered dataset/database/tools.

2.1.3.4.2 Datasets / Databases / Tools. The contractor shall summarize its use of each data source, to include points of contact (name, position, organization/company, telephone number, e-mail and mailing address) and electronic access information (e.g., URLs), and provide this summary to the COR and PM. The report should address lessons learned on issues obtaining data due to inability to get NDAs or missing data due to inability to get NDAs. For data within the dataset/database, a report shall also address identified potential data collection or data disclosure issues by source, and provide information on requirements associated with achieving NDAs for any requests for data or access to data sources. Subscription based data sources may be used if approved as a viable source of data for the activity or task. All information collected will be documented to include collected data, data pedigree, data sources, appropriate proprietary data markings, and definitions (see example template standard in Attachment J). In addition, the contractor must include sufficient documentation to facilitate ease of use by the cost analyst users and also separate documentation for use by dataset/database/methods/tools future enhancers/maintainers. Tools developed to facilitate dataset/database/model/tool development, enhancement and future sustainment in the process of creating these datasets/databases/models/tools must be delivered with the documentation (e.g., data scrapers for 1921 forms, automated data input quality validation tools).

2.1.4 Task 4 – Product Finalization

2.1.4.1 The contractor shall continue efforts to update, provide lessons learned while finalizing all studies, analysis, templates, documentation, and deliverables based on all areas of the PWS to include addressing and meeting all objectives. The contractor, in coordination and with government guidance, shall develop and obtain PM and COR approval for the procedures for finalization NLT six months prior to contract completion. Procedures will outline all required finalization white papers, briefings, and reports for tasks and subtasks conducted for this contract. The government will make the final determination on the content requirements and will review and approve all deliverables, including any of the product finalization papers, briefings and reports before signing off and accepting as the final submission. Draft papers, briefings, and reports will be due no later than 60 days prior to the contract ending so that the government can review the documents and provide feedback to the contractor to update, revise and provide the final documents to close out this final phase. As required, if significant comments were provided on the first draft submittal, a second draft submittal should be provided within fifteen (15) business days of receiving the comments from the government or NLT fifteen (15) business days prior to contract end date (whichever is sooner).

2.1.4.2 The contractor shall ensure all papers, briefings, and other reports as approved by the government are finalized and accepted by the government no later than (NLT) ten (10) business days prior to the end of the contract. The contractor shall also provide the COR with all passwords to the systems, data collected, processes utilized and any other information obtained throughout the period of performance. The COR will meet with the contractor within the sixty (60) business days to ensure all information is received and stored for the permanent records. Once confirmed, the contractor will send an endorsement letter to the COR confirming that paragraph 6.0 requirements were completed NLT five (5) business days prior the end of the contract.

2.1.5 Task 5 – Surge Support (Option CLIN)

During the course of performance identified in this PWS, it is possible that the effort could potentially expand the anticipated, on-going support. This task refers to a level of effort that the government may exercise at its discretion to provide cost estimators and technical subject matter experts for surge support. The government will define specific task descriptions and add these to this contract via this option CLIN. The support required may include requirements for cost and/or technical/programmatic assessments/estimates (e.g., program software sizing estimates or assessments, program schedule estimates or assessments) from cost, schedule, engineering, or software subject matter experts. The decision to invoke the task shall be based on the level of support that is required, project length, and the amount of available project funding.

The government may exercise the option CLIN more than once or in any combination thereof the price of the baseline contract.

2.6 KNOWLEDGE, SKILLS, and ABILITIES (KSA): The following KSAs are required and applicable for each task and subtask to accomplish and achieve overall success. Specific KSAs are identified below by labor category for each of the weapon system commodity groups identified in paragraph 3.0. The contractor is responsible for ensuring its assigned personnel (to include subcontractors) fully comply with the minimum experience and knowledge described in the following paragraphs. The contractor shall provide personnel to perform as Integrated Technical Manager, Program Manager, and Commodity Leaders for each of the weapon system commodity groups identified in paragraph 3.0. The Commodity Leaders shall be responsible for the performance of the work under their applicable weapon system commodity area and must be at minimum qualified as a Senior Cost Estimator/Analyst, in accordance with paragraph 4.3. Integrated technical management support is required to manage and oversee all activities performed by contractor personnel, including subcontractors, to satisfy the requirements identified in this PWS. The Integrated Technical Manager’s responsibilities include ensuring there is technical content quality, commonality and configuration compliance within all task and subtask deliverables as applicable, in particular tasks and subtasks under Task 3 and 4. As approved by the AFCAA/TD or delegated authority and the COR, personnel may be assigned to several areas of performance as long as the person meets the required KSAs in each category (e.g., one person may serve as both the Aircraft/UAV and Missile Commodity lead, one person may be assigned both the ITM and PM roles). Waiver considerations for years of experience may be granted if the candidate possesses unique or hard to find skills. Waivers must be approved by AFCAA/TD or delegated authority and the COR. Administrative and clerical support under this contract shall not be considered a direct task or labor category. Table 1 provides a summary outline of the KSA for each position.

Table 1: KSA Summary Outline

Product Support

Launch Vehicle

2.2.1 General Requirements. At a minimum, contractor shall:

a. Provide a management capability plan to manage all PWS tasks per the POA&M requirements (reference paragraph 3.1.2c)

b. Provide a primary point of contact to work with the government on all CEM issues

c. Multiple KSAs may be achieved by an individual FTE

2.2.2 Overall Integrated Technical Manager. Personnel in this category must have a minimum of three (3) years managing projects of comparable scope to the CEM effort and a minimum of eight (8) years as a cost estimator or cost estimating experience.

2.2.3 Program Manager. Personnel in this category must have a minimum of eight (8) years managing projects of comparable scope to the CEM effort. The Program Manager manages the coordination and completion of tasks and subtasks/projects on time within budget and within scope. The PM works with project leads and the ITM to set deadlines, assign responsibilities and monitor project timelines. He or she prepares reports regarding the status of each project. The person in this category requires a bachelor's degree and five (5) years or more experience in the program management field or in a related area, and familiarity with a variety of the program management field's concepts, practices and procedures. He or she will lead and direct the work of others. A wide degree of creativity and latitude is expected.

2.3 Technical Experts

2.3.1 Software Engineer/Systems Analyst. Must have at least ten (10) years of recent experience in the following subject areas:

a. Technical Software Engineering/Analyst – software system-specific requirements analysis, software design, software analysis, software development paradigms to include agile, computer programming, engineering, system design, integration of software and system, test of software and system, management of information technology systems.

b. Cost– knowledge on the impacts of technical areas as cost drivers and application to cost estimating methodologies.

2.3.2 Product Support Analyst/Expert. Must be able to integrate with the experts in the other commodity systems to incorporate understanding of product support, technical aspects, and management. Must have seven (7) years of DOD program (e.g., Navy, Army, Missile Defense Agency (MDA), Air Force) technical analysis/management experience in product support areas like supply chain management, depot workload and activation requirements, support equipment, training devices, publications/technical data, and initial/other sparing.

2.4 Senior Cost Estimator/Analyst. Must have experience in cost analysis principles including, but not limited to:

a. Cost estimating – Demonstrated expertise in commodity/system-specific estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of commodity/system-specific programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle.

b. Data collection – Demonstrated expertise collecting and normalizing cost, technical, and programmatic data from Government and Industry entities. Knowledge of the Defense Cost and Resource Center (DCARC) data collection process and demonstrated experience in use of and analysis of the Cost and Software Data Reports (CSDRs) and Integrated Program Management Reports (IPMRs)/Contract Performance Reports (CPRs). Knowledge of data sources such as CADE and AFTOC.

c. Leading teams – Demonstrated ability to lead cost research project teams to successful conclusion.

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

e. Must have at least ten (10) years of technical cost analysis experience.

2.4.1 Aircraft/UAV and Associated Subsystems. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level aircraft/UAV acquisition program cost analysis experience.

2.4.2 Missiles/Munitions. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level missile/munitions acquisition program cost analysis experience.

2.4.3 AIS. Must have at least ten (10) years of technical cost analysis experience. These professional(s) must comply with the following knowledge and experience: Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level AIS program cost analysis experience.

2.4.4 C4I. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level C4I systems cost analysis experience.

2.4.5 ICBM. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level ICBM acquisition program cost analysis experience.

2.4.6 O&S. Must be able to integrate with the experts in the other commodity systems to incorporate technical understanding into the O&S solution. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level acquisition program O&S cost analysis experience.

2.4.7 Space and Launch. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or similar space (satellite/ground) acquisition program cost analysis experience.

2.4.8 Weapon System Software. Must have at least ten (10) years of technical cost analysis experience. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level weapon system acquisition program software cost analysis experience.

2.4.9 Large Enterprise Resource Planning (ERP) or Business Management System Software. Must have at least ten (10) years of technical cost analysis experience. Must have at least five (5) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I level automated information system (ERP type) program software cost analysis experience.

2.4.10 Other Automated Information System/Information Technology System Software (i.e., C2 Centers, C4I Systems, and Mission Planning Systems). Must have at least 10 years of technical cost analysis experience. Must have at least 7 years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force automated information system acquisition program software cost analysis experience.

2.4.11 Cross-cutting. Must have at least ten (10) years of technical cost analysis experience. Must have experience in areas common to many commodities, such as program schedule analysis and program cost analysis for other government costs, test and evaluation, etc. Must have at least seven (7) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level acquisition program cost analysis experience.

2.5 Journeyman Level Engineer/Cost Estimator

a. Cost/Technical – Commodity/system-specific cost/engineering experience to be able to identify appropriate acquisition and O&S cost drivers and document current technology issues/trends/changes driving costs.

b. Cost Estimating – Demonstrated understanding of the connections of cost drivers and estimating the acquisition and O&S costs of aircraft/UAV systems and subsystems.

c. Data collection – Demonstrated ability to collect and normalize cost, technical, and programmatic data from Government and Industry entities. Knowledge of the Defense Cost and Resource Center (DCARC) data collection process and demonstrated experience in use of and analysis of CSDRs and CPRs. Knowledge of the DCARC data system(s) (i.e. DACIMS, CADE). Knowledge of AFTOC.

d. Data analysis & cost tools – Demonstrated ability to analyze data and develop cost estimating methods and tools.

2.5.1 Aircraft/UAV - O&S. Must have at least five (5) years of technical cost analysis experience. These professional(s) must comply with the following knowledge and experience: Must have at least four (4) years of progressive O&S cost analysis experience on major DoD or Air Force ACAT I/II threshold level aircraft/UAV programs.

2.5.2 Missiles/Munitions. Must have at least five (5) years of technical cost analysis experience. Must have at least two (2) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I/II threshold level missile/munitions cost analysis experience.

2.5.3 CBM. Must have at least five (5) years of technical cost analysis experience. Must have at least two (2) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level ICBM cost analysis experience.

2.5.4 Space (Satellite/Ground). Must have at least five (5) years of technical cost analysis experience. Must have at least two (2) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or similar space (satellite and ground systems) cost analysis experience.

2.5.5 Launch Vehicle. Must have at least five (5) years of technical cost analysis experience. Must have at least two (2) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level launch vehicle cost analysis experience.

2.5.6 Cross-Cutting Areas. Experience in areas common to many commodities, such as program schedule analysis and program cost analysis for other government costs, test and evaluation, etc. Must have at least four (4) years of progressive cost analysis experience.

2.5.7 Software. Must have at least five (5) years of technical cost analysis experience. Must have at least two (2) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level software cost analysis experience.

2.5.8 Automated Information Systems (IS)/Information Technology (IT). Must have at least 5 years of technical cost analysis experience. Must have at least 2 years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level AIS cost analysis experience.

2.5.9 AIS/IT – O&S. Must have at least four (4) years of progressive O&S cost analysis experience on major DoD or Air Force ACAT I/II threshold level AIS programs.

2.5.10 C4I Systems. Must have at least five (5) years of technical cost analysis experience. Must have at least two (2) years of progressive DoD, e.g., Navy, Army, MDA, and other DoD organizations or Air Force ACAT I threshold level C4I cost analysis experience.

2.5.11 C4I – O&S. Must have at least four (4) years of progressive O&S cost analysis experience on major DoD or Air Force ACAT I/II threshold level C4I programs.

2.6 Junior Cost Estimator. General Cost Experience – Must have at least two (2) years of progressive large DoD or Air Force acquisition program cost analysis experience. Must have experience in cost analysis principles including, but not limited to:

a. Cost/Technical – Knowledge of weapon system and/or automated information system acquisition and operations and sustainment cost, technical and program data.

b. Cost estimating – Knowledge and understanding of estimating methodologies that may drive data collection.

c. Data collection – Ability to collect and normalize cost, technical, and programmatic data from government and industry entities.

d. Data analysis & cost tools – Ability to analyze data and develop cost estimating methods and tools.

2.7 Key Positions/Personnel. In order to complete the desired task requirements and support these tasks in a timely manner, it is critical that the contractor have personnel assigned to this requirement provide an NDA with AFCAA and with OSD CAPE for access to CADE.

2.7.1 The contractor shall provide an Integrated Technical Manager (ITM) and Program Manager who shall be responsible for the performance of the work. The ITM shall have full authority to act for the contractor on all contract matters relating to the daily operation of this contract. The contractor shall adhere to all scheduled timelines, milestones, delivery schedules, and administrative requirements to include scheduled on-time delivery of reports, data products, billing invoices, staffing of personnel, and action item completion. The ITM shall be available between the hours 8:00 a.m. – 4:30 p.m., Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. The contractor may combine one or more of the Commodity Lead positions.

The following personnel are considered key personnel by the Government:

SECTION III

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “Acceptable” or “Unacceptable” basis. These thresholds are critical to mission success.

Threshold

SS – 1

Provide qualified people at start of Task Order

a) qualified personnel are on the job at contract Start unless previously negotiated by the CO and

b) the mission is not impacted due to position vacancies or personnel qualifications

Failure to meet the delivery date within 75% staffed on day 1 and 100% staffed within five (5) days for Key Personnel, IAW, PWS 4.6.1 will result in a reduction of the fixed fee amount by 20% of quarterly fixed fee amount.

SS – 2

Maintains a stable workforce (Highly Specialized Technical and Cost Analysis Expertise)

SS – 3

Replacement and/or substitute personnel

a) vacancies are filled with qualified personnel within 5 days of resignation notification by incumbent personnel to the Contractor or immediately after departure of incumbent personnel or whichever is earlier unless negotiated by the CO and

b) the mission is not impacted due to position vacancies or personnel qualifications

Periodic Surveillance Performance of this objective will be annotated in the Contractor Performance Assessment Reporting System (CPARS) Rating.

Failure to meet the delivery date within 5 days for Key Personnel and 8 days for all other Personnel will result in a reduction of the fixed fee amount by 15% of quarterly fixed fee amount, if standards are not met.

SS – 4

Develop and submit all required deliverables

a) 100% of all deliverable requirements are met and received on time.

b) accurate information for mission critical tasks as defined each task section.

100% Surveillance

Reperformance, CPARS, Exercise Option, Monetary Deduction which will be under the direction of the COR. See fee schedule example for monetary deductions. If the contractor has had negative trending performance, then surveillance will increase and if positive trending performance is found, then surveillance will be reduced, etc.

Failure to meet the delivery date within 10 days will result in a reduction of the fixed fee amount by 10% of quarterly fixed fee amount, if standards are not met.

SS-6 Provide final documents and deliverables based on POA&M action items as directed by Task Direction Memorandums (TDMs)

PWS Para 3.1.2, 5.0 and Para 10.6

Failure to meet the delivery date will result in a reduction of the fixed fee amount by 25% of quarterly fixed fee amount, if standards are not met.

SECTION IV

4.0 DELIVERABLE(s): The contractor shall provide deliverable(s) described in Table 2 in a format mutually agreed upon by the government and the contractor. All deliverables shall be in electronic format. Cost collection database formats shall be compatible with paragraph 3.2.1.5. Text and graphics shall be in native format compatible with MS Office and a copy in PDF.

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor. The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date.

Table 2: Task Order Deliverables