FINAL_CEM_Solicitation_20160627.pdf

6842591

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Program Management

CPFF

Program Management, Interfacing meetings and establishing the NonDisclosure

Agreements (NDAs) for CEM R&D effort IAW Para 3.0, 3.1.1 and 3.2.3.

FOB: Destination

TOTAL ESTIMATED COST

R&D Service Support

CPFF

Research and Development services in support of the following tasks:

Task 1 - Establish required NDAs IAW PWS Para 3.1.1

Task 2 - Develop a Plan of Action and Milestones (POA&M) IAW PWS Para

3.1.2

Task 3 - Data collection and normalization IAW PWS 3.1.4

Task 4 - Analysis of Data Sources and Data Availability IAW PWS 3.1.4

Task 5: Refine Existing Templates and Develop New Commodity Specific Data

Collection Templates (PWS 3.2.1)

Task 6: Develop Methods/Tools/CERs and Other Analytic Approaches for Cost

Estimating (PWS 3.3 to 3.3.2)

Task 7: Product Finalization (PWS 3.4 to 3.4.3)

TOTAL ESTIMATED COST

Data Support

Data support to CEM IAW Par 3.1 and 5.0. (NSP)

Travel

COST

Travel for the base year.

NOT TO EXCEED NSP

Other Direct Costs

COST

Other Direct Costs associated to the CEM support.

NOT TO EXCEED NSP

0006 Fixed Fee (CLINS 0001 to 0005)

See pricing worksheet for all elements

TOTAL FIXED FEE _____________

CEM R & D Surge Support

CPFF

CEM Research and Development Surge Support during the base year IAW all tasks areas and the guidance of the Government.

Fixed Fee

CPFF

FOB: Destination

See pricing worksheet for all elements to price for CLIN 0007a to 7d

TOTAL FIXED FEE _____________________________

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

AFDW/PKS

PWS

Research and Development for Cost Estimating Modeling (CEM)

Cost Data Improvement, Methods & Tools Development

For

Air Force Cost Analysis Agency (AFCAA)

27 June 2016

AFCAA Cost Estimating Modeling (CEM) Effort

1.0 INTRODUCTION/BACKGROUND: The DoD cost community including the Cost

Assessment and Program Evaluation (CAPE) office, 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 has recently identified numerous gaps in the databases (DBs), 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.

2.0 OBJECTIVE: The objective is to research, analyze, design and modernize current cost data and estimating methods and tools. In collaboration with the OSD Cost Assessment Data

Enterprise (CADE) project, this research, analysis and assessments 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. DoDI 5000.02) in support of the AF and DoD acquisition decisions, programming and execution decisions and Congressional mandates.

3.0 TASK REQUIREMENTS: The Contractor will collect data and populate government provided templates for designated weapon systems. While collecting data, the Contractor will also recommend changes to the templates, develop new templates as needed and quality check and normalize received data. Following data collection, the Contractor will use the data 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, timely delivery, high quantity, effective program cost estimates. 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.

Systematically and continuously document Air Force and associated joint service cost estimating data requirements, then collect, store, and retrieve the required data, and provide analysis and tools for use by cost estimators. Data will be collected using commodity specific data collection templates developed for AFCAA (see Attachments G) that identify and define the required cost, technical, schedule and programmatic data elements. This effort also includes making recommendations to improve data collection to make it more systematic and consistent, loading the collected data into the Cost Assessment Data Enterprise (CADE) managed by the OSD CAPE to centrally house and make data available to the entire cost community, and assisting the government in implementing approved recommendations. Templates will be provided by AFCAA for the following weapon system commodity groups:

1. Aircraft/Unmanned Air Vehicles (UAVs)

2. Missiles/Munitions

3. Intercontinental Ballistic Missiles (ICBMs)

4. Automated Information Systems (AIS) & associated equipment

5. C4I/Electronics and associated equipment

6. Software

7. Other Government Costs (OGC)

8. Operations and Support (O&S) Costs for All Commodities

9. Space and Launch Systems

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 5 days of vacancy, in accordance with paragraph 4.7.1.1 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 PWS. The Contractor shall provide meeting minutes as required. Meetings will include, as a minimum an initial kick-off meeting within 10 days after contract award, weekly status meetings between the Contractor Integrated

Technical Manager (reference paragraph 4.0) and AFCAA PM, and quarterly in- person formal reviews between the Contractor and the entire AFCAA government team to include the AFCAA Technical Director (TD), AFCAA PM and the AFCAA Commodity Technical

Leads (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 days before the period of performance ends. 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 outlined in Section 5.0 –

Deliverables.

3.1 Data Collection Program

3.1.1 Task 1 – Establish Required Nondisclosure Agreements (NDAs) (Deliverable 3)

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 OEM Contractors and major subcontractors, and ensure actions to complete NDAs are finalized. The Contractor must, within

6 months of contract award have all necessary NDAs to ensure full and open access at a minimum to all Department of Defense (DoD) ACAT I program data, past and present, with no limitations. The Contractor must assist in identifying other non-AF 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 all contracts. The Contractor is required to provide signed NDA forms for all

Contractors and subcontractors working on this contract to the COR.

3.1.2 Task 2 – Develop a Plan of Action and Milestones (POA&M) for the tasks and subtasks. (Deliverable 4)

The Contractor shall develop and submit, for government review and approval, a POA&M describing the Contractor’s approach to satisfy all requirements that includes each weapon system commodity group within 30 calendar days after contract award. The POA&M shall include, as a minimum:

a. A detailed description of the approach to complete each task and subtask to include any risk associated with each task and subtask.

b. A task 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. 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 should track and align to the activity and milestone schedule outlined in paragraph 3.1.2.b. The plan should be specific in the Integrated Technical

Manager roles and activities (reference paragraph 4.1).

d. Support and refinement of CEM deliverables to the CADE program necessary to institutionalize the collection of CEM developed deliverables. These will include but are not limited to all documents, manuals, Data Item Descriptions, training material, dictionaries required to institutionalize the collection of the CEM 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 Technical Director. 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 by the

Government on the recommended changes/updates to this document.

3.1.3 Task 3 – Data Collection and Normalization

The Contractor shall work with the COR and the AFCAA PM to develop a data collection plan to collect data using the data collection templates in Task 5 for selected on-going and historical programs. The AFCAA PM 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 for the entire base period of this effort and identifying all potential sources. Prior to starting any data collection effort, the Contractor shall first compare existing data sources (e.g. as identified in Task 4) with data elements defined on the templates to identify specific data elements that have not yet been collected or are not already available from the CADE.

3.1.3.1 Data Collection: Following the COR or the PM approval of the schedule and approach recommended for each source, the Contractor shall collect time phased data from the AFCAA approved sources. Because the templates allow for data collection throughout the life cycle of a program, the templates can be used to capture data at any point in the program, to include initial estimated data based on initial requirements as well as actual data based on final designs and costs.

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. All information collected will be normalized to include the creation of metadata not collected via the raw data collection. The COR 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 AFLCMC and

SMC staff and program offices, NCCA, NAVAIR, DASA CE, OSD CAPE, and HQDA ASA.

3.1.3.2 Develop Organized Raw and Normalized Data Sets and Repositories: All raw and normalized data will be organized into searchable, user-friendly data repositories/databases for use in analysis by cost estimators. The contractor will provide AFCAA an analysis of options for organizing the data sets for storage, retrieval, and use by cost estimators. 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 the organized data sets and repositories/databases/tools. All approaches will be designed with the goal of ensuring the data can be easily integrated/incorporated into CADE. 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.

3.1.3.3 Documentation: All information collected will be documented to include collected data, data pedigree, data sources, and definitions (if not part of the template standard). The Contractor shall deliver the completed data collection templates to the COR or PM, along with an explanation of any issues, assumptions, or normalization affecting the reported data. Data sources used to populate the templates will be clearly identified and provided as reference material.

The data will be organized and provided in the current AFCAA approved format at the time of submission with the goal of ensuring the data is provided in a format that will be easily integrated/ incorporated into CADE. All normalization analysis must be fully documented in enough detail that the analysis can be recreated by another junior cost estimator and as such normalized data is fully traceable back to the raw data. Instructions/training materials must be fully documented for repositories/database/tools developed. In addition to providing the COR or PM with all information related to this effort, any and all data collected and developed during the course of completing the requirements of this contract must be deleted from the Contractor’s server’s and computers. All materials and information produced and/or required by the contractor in performance of the contract shall become the sole property of the government and will be turned in to the COR and Government PM at the end of contract in manner as described in the deliverable section of the PWS.

3.1.4 Task 4 – 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 this requirement.

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

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

Data quality – Accuracy, completeness, and fidelity of data;

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

Data availability – Security classifications, proprietary/competitive restrictions;

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

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

3.1.4.1 Documentation The Contractor shall summarize their review of each new data source, to include points of contact to include name, position, organization/company, telephone number, e-mail and mailing address for each source and provide this summary to the COR or PM. Their report shall also address potential data collection or data disclosure issues by source, and provide feedback on the status of Non-Disclosure Agreements (NDAs) initiated with potential sources. Subscription based data sources are not applicable for the data collection tasks.

3.2 Refine Existing Templates and Develop New Commodity Specific Data Collection

Templates

3.2.1 Task 5 – Existing Templates and Development of New Commodity Specific Data:

The Contractor will use any information gained from Task 4 to refine the existing data collection templates for the weapon system type and/or cost categories and develop any additional templates necessary to cover the full content of the commodities described in Paragraph 3.0.

3.2.1.1 Refine Templates: The Contractor shall work with COR or PM to refine cost/technical/ programmatic data collection templates. The templates will provide a standardized format that ensures the cost community will have the appropriate technical and programmatic data available for the weapon system type and/or cost categories as part of the cost reporting process. Templates will allow for collecting and documenting data by phase (development, production, operations and sustainment) and by fiscal year within each phase. The revisions shall be developed and delivered using Microsoft Office (Excel). Templates shall be compatible with the format being used by Defense Cost and Resource Center (DCARC) and/or CADE to collect and display cost data.

3.2.1.2 These revisions will include, as a minimum:

a) A cost work breakdown structure (e.g., tailored to Mil-Std-881C current O&S CAPE guide or

AFCAA Data Templates) to organize data by commodity for each weapon system type and/or cost category.

b) A list of common data element names and definitions to ensure similar data from all sources can be normalized to the standard names and definitions.

c) A format to enter unique programmatic (i.e. schedule) and technical characteristics (such as:

size, weight, power, form factor, digital technology, nuclear hardening, and specialized security). The Contractor shall provide and use a consistent method of specifying weights and measures, electrical power (e.g. 220 volt, 60 Hz. AC) and other characteristics to ensure effective usage of each item for cost analysis and estimating.

d) Any additional data fields, changes in cost work breakdown structures, etc. need to be fully documented. New data fields will be evaluated for inclusion in all commodity templates, and if so will require consistent naming conventions and definitions in the commodity templates.

3.2.1.3 Develop New Templates: The Contractor shall develop, in accordance with the format and structure of existing templates, any new templates that are identified to cover the full content of the various commodity groups. These new templates may address expansion of templates to address subsystem level breakouts within each commodity, reworking of existing templates to cover variations within a commodity group (such as different mission types for aircraft), and reworking existing templates to ensure they adequately capture information associated with modification programs and minimize impacts on the use of existing templates that are not modified.

3.2.1.4 Documentation: The Contractor shall document the template revisions, such as new data elements and sources, and provide detailed instructions with examples for populating the templates, to include how to deal with issues identified during the Review and Analysis (Task 4).

The Contractor will identify how the templates differ from Mil-Std-881C formats, the O&S OSD

CAPE guide or AFCAA Data Templates (if differences exist).

3.2.1.5 Data Template Configuration Compliance: The contractor shall ensure the Integrated

Technical Manager is responsible for ensuring there is commonality and configuration compliance within all of the Data Templates. The contractor is responsible for ensuring template integration amongst all of the weapon system commodity groups (reference paragraph 3.0). The contractor is responsible for ensuring the templates consider and adjudicate findings across the services, data collection working groups, DCARC, CADE contractors, OSD CAPE, and other organizations whose products/services provide input into potential data template final configurations.

3.2.1.6 Coordination and Approval: The Contractor shall present the finalized revised and new templates and instructions to the COR or PM to ensure complete understanding of the data fields and structure of the templates. The Contractor will present the templates and deliverables as well as interim results/changes from this project to the COR or PM identified working groups, IPTs, or other forums with the purpose of collecting feedback to refine the templates and get government and industry coordination and approval of the products. The Contractor will continue to document a full representation of OSD, Air Force, Navy, and Army cost community concerns as well as industry concerns. The Contractor will fully support coordination activities with industry and other

DOD organizations to accomplish a seamless transition and integration of the final template products into OSD CADE.

3.3 Task 6– Perform Studies/Analysis and Develop Methods and Other Analytic

Approaches for Cost Estimating: As data for multiple Air Force weapon systems and commodities are collected, and as required by the COR or PM, the Contractor shall use the data to perform studies and analysis to improve cost estimating methods. The Contractor will develop/validate cost estimating benchmarks, methods, CERs, factors or other estimating approaches. As required by the COR or PM, methods (e.g. CERS, factors, benchmarks) will be organized into searchable, user-friendly tools for use in analysis by cost estimators. The contractor will provide AFCAA an analysis of options for organizing the methods in tools for use by cost estimators. 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.

3.3.1 Task Specific Project Plan. Each study or analysis 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 schedule and desired outcomes for the study or analysis. The Contractor will then provide a detailed Project Plan to describe the approach, staffing, scaling, schedule, deliverables, expected difficulties and resources required for the task. Following the COR or PM approval, the Contractor will be allowed to execute the task as additional CEM related efforts throughout the full five (5) year base period.

3.3.2 Documentation. All studies, analyses and other reports generated by the Contractor under this task will be documented by a formal report delivered to the COR or PM no later than 10 days after the end of the study. 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, and

Analytic methods), Risk/Uncertainty, Results/ Conclusions/ Recommendations. Tools will be fully documented to include user instructions/training materials.

3.4 Task 7 - Product Finalization

3.4.1 The Contractor shall continue their current efforts to update, provide Lessons Learned while finalizing all studies, analysis, and templates based on all areas of the PWS to include addressing and meeting all objectives for each phase. The Contractor shall prepare the policies, white papers, briefings, and reports as instructed by the Government for the data collection conducted for this contract. These DRAFT policies, white papers, briefings, and reports will be due 60 days prior to the contract ending in the last year of the base period 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.

3.4.2 The Contractor shall periodically hold meetings throughout the last year of performance with all of the AFCAA stakeholders to update, review, develop and provide recommendations to the Government addressing any new data collected and the impact it might have to the AFCAA organization as designated by AFCAA. 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.

3.4.3 The Contractor shall ensure that all policy reports, white papers, briefings, and other reports as instructed by the Government are finalized no-later-than (NTL) 60 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 60 days to ensure that all information is received and stored for the permanent records.

4.1 Knowledge Skills and Abilities (KSA). The following KSA’s are required and applicable

For each task and subtask to accomplish and achieve overall success. Specific KSA’s 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 addressed below:

4.1.1 General Requirements. At a minimum, Contractor shall:

Provide a Management Capability Plan (MCP – Deliverable 10) to manage all PWS tasks per POA&M requirements (reference paragraph 3.1.2c)

Provide a primary point of contact to work with the Government on all CEM issues which would be the Project Manager and Technical Lead for each of the commodities outlined below.

The contractor shall provide an Integrated Technical Manager and Commodity Leader 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.

4.1.2 Overall Integrated Technical Manager

Personnel in this category must have a minimum of 3 years managing projects of comparable scope to the CEM effort. Must have a minimum of 8 years as a cost estimator or cost estimating experience. 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 Performance Work Statement (PWS). The Integrated Technical Manager’s responsibilities include ensuring there is commonality and configuration compliance within all of the Data Templates, per paragraph 3.2.1.5. Administrative and clerical support under this contract shall not be considered a direct task or labor category.

4.2 Subject Matter Expert (SME)

4.2.1 SMEs/Technical Experts on Large DOD/AF Weapon System Programs: Personnel in this category serve as subject matter experts to provide, as needed, a technical understanding of major DOD or AF weapon system technologies/designs/manufacturing experience and to help identify key parameters and cost drivers that affect life cycle cost. The contractor personnel must have reach-back access, as needed to experts with knowledge related to each of the specific commodity areas located in paragraph 3.0. These professional(s) must comply with the following knowledge and experience:

a. Must have at least five (5) years of progressive systems engineering, design engineering, or manufacturing.

b. Must have experience in the following subject areas:

1) Technical – major DOD or AF weapon system requirements analysis, systems analysis, engineering, system design.

2) Cost – Knowledge of technical cost drivers and how they are used in common cost estimating methodologies

4.3 Senior Cost Estimator/Analyst

4.3.1 Aircraft/UAV and associated subsystems: Must have at least ten (10) years of technical cost analysis experience; of which, at least seven (7) years must be progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level aircraft/UAV acquisition program cost analysis experience. Must have experience in cost analysis principles including, but not limited to: (a) Cost estimating – demonstrated expertise in aircraft/UAV/related subsystem estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of aircraft/UAV 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 CSDRs and CPRs. Knowledge of data sources such as

DACIMS, 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.

4.3.2 Missiles/Munitions: Must have at least ten (10) years of technical cost analysis experience;

of which, at least seven (7) years must be of progressive DOD, e.g., Navy, Army, Missile

Defense Agency, and other DOD organizations or AF ACAT I level missile/munitions acquisition program cost analysis experience. Must have experience in cost analysis principles including, but not limited to: (a) Cost estimating – demonstrated expertise in missile/munition related subsystem estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of missile/munition 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 CSDRs and CPRs. Knowledge of data sources such as DACIMS, 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.

4.3.3 AIS: Must have at least ten (10) years of technical cost analysis experience; of which, at least seven (7) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level missile/munitions acquisition, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level AIS program cost analysis experience. Must have experience in cost analysis principles including, but not limited to: (a) Cost estimating – demonstrated expertise in AIS/DBMS systems and equipment estimating methodologies that will facilitate identification of data collection parameters.

Includes an in-depth understanding of AIS system 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 CSDRs and CPRs. Knowledge of data sources such as DACIMS, CADE, and AFTOC.

Leading teams – demonstrated ability to lead cost research project teams to successful conclusion. Cost tools – demonstrated knowledge and demonstrated expertise/ability to analyze data and develop cost estimating methods and tools.

4.3.4 C4I: Must have at least ten (10) years of technical cost analysis experience; of which seven

(7) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other

DOD organizations or AF ACAT I level C4I systems cost analysis experience.

Must have experience in cost analysis principles including, but not limited to:

(a) Cost estimating – demonstrated expertise in C4I/Electronics systems and equipment estimating methodologies that will facilitate identification of data collection parameters.

Includes an in-depth understanding of C4I 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

CSDRs and CPRs. Knowledge of data sources such as DACIMS, CADE, and AFTOC. Leading teams – demonstrated ability to lead cost research project teams to successful conclusion.

Cost tools – demonstrated knowledge and demonstrated expertise/ability to analyze data and develop cost estimating methods and tools.

4.3.5 - ICBM: Must have at least ten (10) years of technical cost analysis experience; of which, at least seven (7) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level ICBM acquisition program cost analysis experience. Must have experience in cost analysis principles including, but not limited to: Cost estimating – demonstrated expertise in ICBM related subsystem estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of

ICBM programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle. 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 CSDRs and CPRs. Knowledge of data sources such as DACIMS, CADE, and AFTOC. Ability to lead teams – demonstrated ability to lead cost research project teams to successful conclusion. Data analysis & cost tools – demonstrated knowledge and demonstrated expertise/ability to analyze data and develop cost estimating methods and tools.

4.3.6 - OGC: 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, Missile Defense

Agency, and other DOD organizations or AF ACAT I level acquisition program cost analysis experience. Must have experience in cost analysis principles including, but not limited to: (a)

Cost estimating – demonstrated expertise in at least one OGC cost estimate for major weapon system and automated information system estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of programmatic and technical cost drivers associated with missile/aircraft/UAV systems test and depot activation costs. (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 CSDRs and CPRs. Knowledge of data sources such as DACIMS, 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.

4.3.7 - O&S: Person must be able to integrate with the experts in the other commodity systems to incorporate technical understanding into the O&S solution. This professional must comply with the following knowledge and experience: Must have at least seven (7) years of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level acquisition program O&S cost analysis experience. Must have experience in cost analysis principles including, but not limited to: Cost estimating – demonstrated expertise in O&S estimating methodologies used to prepare budget or milestone cost analysis. Demonstrated an in-depth understanding of programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle. 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 CSDRs and CPRs.

Knowledge of data sources such as DACIMS, CADE, and AFTOC. Must have demonstrated knowledge of and expertise in using AFTOC and other service VAMOSC systems. Leading teams – demonstrated ability to lead cost research project teams to successful conclusion. Cost tools – demonstrated knowledge and expertise of O&S cost estimating models and tools.

4.3.8 - Space: Must have at least ten (10) years of technical cost analysis experience; of which, at least seven (7) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or similar Space (satellite/ground) acquisition program cost analysis experience. Must have experience in cost analysis principles including, but not limited to: Cost estimating – demonstrated expertise in space subsystem estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of space programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle. 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 CSDRs and CPRs. Knowledge of data sources such as DACIMS, CADE, and AFTOC. Leading teams – demonstrated ability to lead cost research project teams to successful conclusion. Data analysis & cost tools – demonstrated knowledge and demonstrated expertise/ability to analyze data and develop cost estimating methods and tools.

4.3.9 - Weapon system software: Must have at least ten (10) years of technical cost analysis experience; of which at least seven (7) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level weapon system acquisition program software cost analysis experience. Must have experience in cost analysis principles including, but not limited to: Cost estimating – demonstrated expertise in software estimating methodologies that will facilitate identification of data collection parameters.

Includes an in-depth understanding of programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle for software. Must have knowledge of the major activities performed in software development to include large weapon system software requirements analysis, systems analysis, software design, software coding and testing, software analysis, computer programming, engineering, system design, and management.

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 (specifically the SRDRs) and demonstrated experience in use of and analysis of the CSDRs and CPRs. Knowledge of data sources such as

DACIMS, CADE, and AFTOC. Leading teams – demonstrated ability to lead cost research project teams to successful conclusion. Data analysis & cost tools – demonstrated knowledge and ability to analyze software data and develop software cost estimating methods and tools.

4.3.10 - Large Enterprise Resource Planning (ERP) or Business Management system software: Must have at least ten (10) years of technical cost analysis experience; of which, at least five (5) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level automated information system (ERP type) program software cost analysis experience. Must have experience in cost analysis principles including, but not limited to: Cost estimating – demonstrated expertise in software estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle for software. Must have knowledge of the major activities performed in software development to include large weapon system software requirements analysis, systems analysis, software design, software coding and testing, software analysis, computer programming, engineering, system design, and management. 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 (specifically the SRDRs) and demonstrated experience in use of and analysis of the CSDRs and CPRs. Knowledge of data sources such as DACIMS, CADE, and AFTOC. Leading teams – demonstrated ability to lead cost research project teams to successful conclusion. Data analysis & cost tools – demonstrated knowledge and ability to analyze software data and develop software cost estimating methods and tools.

4.3.11 - Other Automated Information System/Information Technology System Software

(i.e., C2 Centers, C4I Systems, Mission Planning Systems): Must have at least ten (10) years of technical cost analysis experience; of which, at least seven (7) years must be of progressive

DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level automated information system acquisition program software cost analysis experience. Must have experience in cost analysis principles including, but not limited to: Cost estimating – demonstrated expertise in software estimating methodologies that will facilitate identification of data collection parameters. Includes an in-depth understanding of programmatic and technical cost drivers associated with both acquisition and operating & support phases of the life cycle for software. Must have knowledge of the major activities performed in software development to include large weapon system software requirements analysis, systems analysis, software design, software coding and testing, software analysis, computer programming, engineering, system design, and management. 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 (specifically the SRDRs) and demonstrated experience in use of and analysis of the CSDRs and CPRs. Knowledge of data sources such as DACIMS, CADE, and AFTOC. Leading teams – demonstrated ability to lead cost research project teams to successful conclusion. Data analysis & cost tools – demonstrated knowledge and ability to analyze software data and develop software cost estimating methods and tools.

4. 4 Software Engineer/Systems Analyst:

4.4.1 - Automated Information Systems/Information Technology Systems and Software:

These professional(s) must comply with the following knowledge and experience: Must have at least five (5) years of progressive systems engineering experience. Must have experience in the following subject areas: 1) Technical – AIS/DBMS system requirements analysis, systems analysis, software design, software analysis, computer programming, engineering, system design, management of information technology systems. 2) Cost – Knowledge of cost drivers that drive common cost estimating methodologies.

4.4.2 – OTHER SOFTWARE:

4.4.2.1 Specialized C4I: Personnel in this category will serve as subject matter experts to provide a technical understanding of Specialized C4I Software, and to help identify key equipment parameters and cost drivers that affect life cycle cost. These professional(s) must comply with the following knowledge and experience: a. Must have at least five (5) years of progressive systems engineering and/or cost analysis experience. b. Must have experience in the following subject areas: 1) Technical – Specialized C4I Software requirements analysis, systems analysis, software design, software analysis, computer programming, engineering, system design, management of information technology systems. 2) Cost – Knowledge of cost drivers that drive common cost estimating methodologies.

4.4.2.2 Major DoD or AF Weapon System Software: Personnel in this category will serve as subject matter experts to provide a technical understanding of major DOD or AF weapon system software, and to help identify key equipment parameters and cost drivers that affect life cycle cost. These professional(s) must comply with the following knowledge and experience: These professional(s) must comply with the following knowledge and experience: a. Must have at least five (5) years of progressive systems engineering and/or cost analysis experience. b. Must have experience in the following subject areas: 1) Technical – major DOD or AF weapon system software requirements analysis, systems analysis, software design, software analysis, computer programming, engineering, system design, management of information technology systems. 2)

Cost – Knowledge of cost drivers that drive common cost estimating methodologies.

4.5 Journeyman Level Engineer/Cost Estimator:

4.5.1 – Aircraft/UAV and associated subsystems: Must have at least five (5) years of technical cost analysis experience; of which, at least two (2) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level aircraft/UAV cost analysis experience Must have experience in cost/engineering principles in the following areas: Cost/Technical - Aircraft/UAV/associated subsystems cost/engineering experience to be able to identify appropriate acquisition and O&S cost drivers and document current technology issues/trends/changes driving costs. Cost Estimating – demonstrated understanding of the connections of cost drivers and estimating the acquisition and O&S costs of aircraft/UAV systems and subsystems. 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. Data analysis & cost tools – demonstrated ability to analyze data and develop cost estimating methods and tools.

4.5.2 - Missiles/Munitions: Must have at least five (5) years of technical cost analysis experience; of which, at least two (2) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level missile/munitions cost analysis experience. Must have experience in cost/engineering principles in the following areas: Cost/Technical - missile/munitions subsystems cost/engineering experience to be able to identify appropriate acquisition and O&S cost drivers and document current technology issues/trends/changes driving costs. Cost Estimating – demonstrated understanding of the connections of cost drivers and estimating the acquisition and O&S costs of missile/munitions systems and subsystems. 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. Data analysis & cost tools –

4.5.3 - ICBM: Must have at least five (5) years of technical cost analysis experience; of which, at least two (2) years must be of progressive DOD, e.g., Navy, Army, Missile Defense Agency, and other DOD organizations or AF ACAT I level ICBM cost analysis experience.