AFTOC PWS MR (002).pdf

CUI FA7014‐22-R-0015

CUI

PERFORMANCE WORK STATEMENT

FOR

Air Force Total Ownership Cost

(AFTOC)

AT

JOINT BASE ANDREWS, MARYLAND

January 2026

Controlled by: AFDW/PK CUI Categories: PROCURE Distribution/Dissemination Controls:

FEDCON AFTER AWARD

POC: Walter Cardenas (walter.cardenas@us.af.mil) mailto:(shuna.ross.1@us.af.mil

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

1.2 Background

1.3 Roles and Responsibilities

1.4 Sustainment

SECTION II

2.0 Task Descriptions

2.1 Task 1 – Data Acquisition

2.2 Task 2 - Data Source System Changes, Updates and Information Integration

2.3 Task 3 - Data Conversions, Validation, and Processing

2.4 Task 4 - Data Presentation (Universes, Reports, Dashboards)

2.5 Task 5 – Quality Assurance

2.6 Task 6 – CUI Data Markings

2.7 Task 7 – Configuration Control Board (CCB)

2.8 Task 8 – Training and User Group Meeting

2.9 Task 9 – Helpdesk Operations/End User Support

2.10 Task 10 – Documentation – Process Documentation

2.11 Task 11 - Database Administration (DBA)

SECTION III

3.0 SERVICE SUMMARY

SECTION IV

4.0 DELIVERABLES

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services

SECTION VI

6.0 GENERAL INFORMATION

6.1 Scheduling Concerns

6.2 Kickoff Meeting/Orientation Meeting

6.3 Transition-In Plan (A028)

6.4 Transition-Out Plan (A029)

6.5 Quality Control

6.6 Emergency Operations/Mission Essential Personnel

6.7 System for Award Management (formerly CMRA)

6.8 Security Instructions

6.9 Travel

6.10 Employee Accountability & Turnover

SECTION VII

APPENDIX 1

1.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

2.0 ACRONYMS

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General. The purpose of this contract is to provide sustainment support of the Air Force Total Ownership Cost system (AFTOC) for the Air Force Cost Analysis Agency (AFCAA).

AFTOC collects, compiles, stores, and standardizes data from more than 26 cost, logistics, and programmatic Department of the Air Force data sources. AFTOC combines and publishes summarized and detailed information to approved, registered DoD users and contractors with DoD sponsors. AFTOC satisfies the need to collect and manage comprehensive cost data as directed by Office of Secretary of Defense Cost Assessment and Program Evaluation (OSD CAPE) via DoDI 5000.73, Cost Analysis Guidance and Procedures. AFTOC provides detailed operations and support cost information on all major weapon systems and sub-systems, including aircraft, space systems, missiles, munitions, command and control, ground equipment, and Air Force infrastructure. The Headquarters United States Air Force AFCAA Operations and Support (O&S) Division, SAF/FMC/AFCAA/FMCY Program Management Office (PMO), is responsible for AFTOC.

1.1.1 Scope. This requirement is to obtain Department of the Air Force (DAF) and Department of Defense (DoD) functional (financial, supply, maintenance, logistics, personnel, fuel, etc.) and system subject matter expertise to support the AFTOC program mission. At the direction of PMO, the contractor shall assist the 520 SWES/MXDPC Software Support Flight with the collection, transformation, validation, and presentation of data utilizing tools and other government furnished equipment provided and designated by the PMO. The PMO will direct work and serve as the liaison between 520 SWES/MXDPC and the contractor. The contractor shall provide database management and data production expertise to assist the 520 SWES/MXDPC in the maintenance and updating of the AFTOC system. The PMO requires functional expertise in understanding DAF and DoD data systems as well as the data contained within DAF and DoD data systems. The contractor shall have a detailed understanding of the Air Force (AF) financial, maintenance, supply, and logistics systems and processes and the ability to integrate several ‘disparate’ data systems in order to provide DoD managers with access to integrated cost and logistics information used for DAF and DoD decision support. The contractor will assist the 520 SWES/MXDPC with Information Technology (IT) and server support for the AFTOC system at Hill AFB, UT enclave, as well as the agreed upon Common Computing Environment (CCE), as required. AFTOC raw data is collected from several existing DoD data systems. The contractor shall collect, test, transform, present, and archive this data on the web servers maintained at Hill AFB, and/or the CCE. The contractor shall ensure contracted personnel take action to fully integrate into the PMO and 520 SWES/MXDPC creating a seamless Government-Contractor team. The contractor shall interface and perform technical and programmatic liaison support with OSD CAPE conducting or interfacing with program or system requirements, operations, planning Research, Development, Test, & Evaluation (RDT&E), and system acquisition and sustainment. All products related to AFTOC including but not limited to the data obtained, software licenses, data code and scripts, Business Rules (BR), documentation, dashboards, reports, training materials, presentations, etc. are government property, and shall be returned to the government in entirety upon request and/or at end of the contract period in accordance with DFARS 252.227-7022.

1.2 Background. Office of Secretary of Defense (OSD) has directed the DAF to maintain this system to capture and report operations and support cost by system and subsystem (DoDM

5000.04 and DoDi 5000.73). To accomplish this objective, SAF/FM and AFCAA require data system expertise to produce the data used in studies for understanding acquisition and sustainment costs associated with DAF systems. The current contract provides data repositories to help federal entities identify historical cost drivers (aircraft, munitions, space systems, Command, Control, Communications, computers, and Intelligence C4I systems and other systems). The output data products of this contract are used in analyses directly supporting OSD, DAF Air Staff, AF Major Command (MAJCOM), Space Force (SF) Field Command (FLDCOM), DAF operating agencies, and other federal entities.

1.3 Roles and Responsibilities. The designated AFTOC PMO is responsible for providing program direction to the contractor and 520 SWES/MXDPC Software Support Flight in support of this requirement. The PMO is the Configuration Management Authority (CMA) for the AFTOC System and ensures that operational user requirements are properly identified, documented, approved, and implemented. Any changes to BRs resulting from user requirements, changes in source data or newly acquired data must be approved by the Configuration Control Board (CCB). The contractor shall participate in all CCB reviews and provide detailed analysis to the CCB regarding the proposed Business Rule Change (BRC). The contractor shall have voting rights to the CCB regarding proposed BRCs. PMO shall act as IT Sponsor/Configuration Control Authority (CCA) and have control of the design solutions to meet the needs of the operational user requirements. Control of functional changes to system design solutions, and the system’s accompanying technical documentation, must be approved by the IT sponsor/CCA as part of the CCB. The contractor shall act as Configuration Management Specialist (CMS) ensuring all elements of the change management process are followed and documented. All documentation is to be kept in a central location as designated by the government and operated by the CMS. Documentation is to be provided to the CCA upon request. The PM shall serve as the Change Control Manager (CCM) and will moderate meetings, review change requests and be the designated signing authority for all approved changes.

The contractor shall participate as CCB members representing each functional area of AFTOC responsible for the following:

1. Tracking and documenting project status updates

2. Identifying impacts of project and delivery schedule changes

3. Communicating required actions based upon project and delivery schedule changes

4. Ensuring required activities are executed.

The PMO may invite individuals from other organizations to serve as AD HOC CCB members as required to provide reviews, research, impact analysis, perform validation of identified problems or proposed changes, recommend implementation, and discuss impacts as necessary.

The PMO shall ensure the charter is up to date, at a minimum each year, and reflects the current CCB systems, members’ names, procedures, and that the repository of the documents are in place and up to date.

1.4 Sustainment. The contractor shall collect, standardize, and integrate data from several information systems as well as maintain the established and documented BRs to continue operation of the AFTOC data warehouse. The contractor shall maintain all related data tables and ensure the data tables are accessible via tools specified by the PMO (i.e., Business

Objects web intelligence and Tableau). The contractor shall assist the 520 SWES/MXDPC in maintaining user access to all designated tools and training maintained on the AFTOC website.

The contractor shall provide the AFTOC user community training related to data access, data comprehension, and use of the data. Further, the contractor shall provide the AFTOC user community with information regarding data changes, as appropriate, to understand all available data sets. The contractor shall create custom data reports as directed by the PMO. This requirement applies to all factors related to the cost of uniquely definable unclassified systems as follows:

1. Aircraft systems and associated aerospace ground equipment

2. Missile and weapon types (Intercontinental Ballistic Missile (ICBM) systems, counter air weapons, close air support weapons, interdiction weapons, munitions)

3. Base operating and support units

4. Strategic offense and defense Command, Control, Communications, Computers and

Intelligence (C4I) (ground, air, and space based), tactical C4I (ground, air, and space based, tactical surveillance (ground and airborne), mobility C4I (ground), AF wide C4I, weather, and navigation aids (ground and space)

5. United States Space Force systems

6. C4I operations support

7. Major automated information systems, as appropriate

8. Special Operations

9. Personnel Data – Military active and reserve, civilians, and Air National Guard.

SECTION II

2.0 Task Descriptions

The Contractor shall provide all services, materials, supplies, equipment, deliverables, and project supervision, as required.

2.1 Task 1 Data Acquisition: The contractor shall collect raw data from DoD systems; perform quality control checks on the raw data; store the raw data; process the baseline data; perform quality control and trend analysis on the processed data; and present the processed data to the user community via the AFTOC common computing environment. The contractor shall continually interface with and support AFTOC users, MAJCOMs/FLDCOMs, HQ DAF data source system owners, DoD, sister services, agencies, centers, laboratories, depots, etc. when performing research in support of analyses. The contractor shall support the PMO by providing technical and analytical analyses of issues associated with the representation of total ownership costs of DAF weapon systems.

2.1.2 The contractor shall coordinate with appropriate DoD organizations maintaining the raw source data required for integration into the data warehouse and arrange for timely transfer of the required raw data (reference Section 2.1) to be processed and integrated. This transfer shall use automated and secure protocols in all cases to collect all raw source data for the AFTOC System.

2.1.3 The contractor shall pursue new data from existing systems and potential new source systems in coordination with the PMO to add breadth and depth to the AFTOC system (current systems listed below). The contractor shall be the primary interface in the collection of data from Government Documents/Data systems DoD data systems, along with any additional sources to be identified, characterized and acquired.

2.1.4 The contractor shall reference the role of the PMO in all AFTOC program support Memorandums of Agreement (MOA), Memorandums of Understanding (MOU), Interface Control Documents (ICD), and Interface Requirements Agreement (IRA). The PMO will outline the roles and responsibilities of the PMO, the contractor team, and the 520 SMXS/MXDPC in all MOA/MOU/ICD/IRA and/or data interchange documents. Below is the list of MOA, MOU, ICD, and IRA, as of August 2025 for which the PMO will update and maintain in order for the contractor to import, manage, store and process the AFTOC source data.

The PMO may add or remove agreements as necessary. The PMO will coordinate authorization to allow the contractor to access data from the following:

1. General Accounting and Finance System – Rehost (GAFS-R) for general accounting system data

2. Defense Enterprise Management System for (DEAMS);

3. Core Automated Maintenance System (CAMS/G081) for historical maintenance actions to be integrated with Standard Base Supply System (SBSS) data to link maintenance and supply actions.

4. Integrated Maintenance Data System (IMDS) for historical maintenance actions to be integrated with SBSS data to link maintenance and supply actions.

5. Cost Accounting and Production Report System (CAPRS) H036A for depot level aircraft-related maintenance, supply and overhead costs by Mission Design Series (MDS).

6. D200 for depot requirements and consumption information (several modules).

7. SBSS/D002, Air Force Logistics Management Agency (AFLMA), Air Force Data Service (AFDS), General Support Division (GSD) transaction data and Material Support Division (MSD) supply transaction data.

8. Wholesale And Retail Receiving/Shipping System (D035K) for depot supply consumption data tables.

9. Programmed Depot Maintenance Scheduling System (PDMSS) (G097) for depot level aircraft tasks, hours, and supply information by aircraft.

10. Data to be integrated with D035K data to provide a link between depot maintenance actions to supply actions.

11. Defense Logistics Services Center for exchange pricing Federal Logistics Data (FED LOG) databases to collect end item designators, next-higher assembly MSD prices, vendors, and inventory control point information.

12. Master Item Identification Control System (MIICS)/(D043A) database to collect end item designators, next-higher assembly MSD prices, vendors, and inventory control point information.

13. E-300Z from the Advanced Personnel Data System (APDS) for actual manning data. Military Personnel Data System to provide manpower data by MAJCOM, operating location, Program Element Code (PEC), grade, Functional Account Code (FAC), Air Force Specialty Code (AFSC), and follow-on or augmenting personnel systems.

14. Fuel Automated System Enterprise System (FES), for aviation fuel gallons and cost by MDS, MAJCOM, operating location and integration.

15. Reliability, Maintainability Information System (REMIS), for flying hours, take-offs, landings by tail number and MDS.

16. Autonomic Logistics Information System (ALIS) F-35 report of flying hours and inventory.

17. AF Primary Aircraft Authorization (PAA) inventory from AF/A8.

18. Logistics, Installations, and Mission Support – Enterprise View (LIMS-

EV) data and actuarial information for building the engine data tables and integrated with CAPRS information.

19. Integrated Budget Documentation and Execution System (IDECS), identification and allocation of system modifications.

20. Theater Integrated Combat Munitions System Training System (TICMS) and MAJCOM representatives for munitions (flares, etc.) consumption patterns and the latest pricing information from the Theater Allocation Buy Budget System (TABBS) to capture munitions replacement costs by type for integration into the AFTOC financial products.

21. DAF Data Quality Service/Data Dictionaries, Accounting code packages, Operating Budget Account Number (OBAN), Responsibility Center (RC), Cost Center (CC), and Budget Program Activity Code (BPAC) listings, other cross reference tables/DAF data sources, and logistics cross reference tables

22. Cost Per Flying Hours (CPFH) database for CPFH and flying hour program (FHP) data.

23. Transportation Working Capital Fund (TWCF) financial information report/data.

24. SAF/FM published cost factors in AFI 65-503

25. Defense Manpower Data Center (DMDC).

26. Depot Maintenance Accounting and Production System (DMAPS) and

Depot Maintenance Systems Integration (DMSI)

27. Additional sources as identified by either the PMO or the contractor.

AFTOC Data Exchange Systems Acronym Type System General Accounting & Finance System - Rehost

GFAS-R Accounting

Transportation Working Capital Fund TWCF Accounting Comprehensive Engine Management System CEMS Aircraft Engine Integrated Budget & Execution System IDECS Budget Enterprise Business System - Fuel System EBS/DLA Fuel Program Depot Maintenance Scheduling System

PDMSS/G097 Maint - Depot

Depot Maintenance Accounting & Production System

DMAPS Maint - Depot

Depot Maintenance Systems Integration DMSI Maint - Depot Supply Requirements Review Board SRRB Supply

Keystone Decision Support KDSS Supply & Depot Maint

FedLog - Master Identification System FEDlog - MIS Supply Interchangeability & Substitution Data D043 Supply Item Application Data D200A Supply Item Descriptive Data Table D200A Supply Master Item Identification Control System MIIC (D043A) Supply Past Program Data D200F Supply RDB Engine & Table Data by MDS D200F Supply Standard Base Supply System SBSS

(D200A/ILS-S)

Supply

Standard Base Supply System - Missing Transactions

Supply

Wholesale & Retail Receiving & Shipping WARRS (D035K)

Supply

Reliability & Maintenance Information System REMIS (G099) Maint - Reliability - Programmatics

Core Automated Maintenance System For Mobility

CAMS-FM

(G081)

Maint - Field

Integrated Maintenance Data System IMDS Maint - Field Defense Military Joint Pay System DJMS Military Pay Defense Manpower Data Center DMDC Personnel Personnel E300z Personnel Total Human Resource Managers' Information System

THRMIS Personnel

ANG Personnel Supplemental Personnel Defense Civilian Personnel Data System DCPDS Personnel Military Personnel Data System MILPDS Personnel Theater Integrated Combat Munitions Training System

TICMS Munitions

Global Ammunition Control Point GACP Munitions Theater Allocation Buy Budget system TABBS TABBS

2.2 Task 2 - Data Source System Changes, Updates & Information Integration. (A020) The contractor will have a detailed and thorough understanding of the systems and data elements outlined in section 2.1.4 and shall investigate, document, design, implement and maintain an AFTOC feature that allows data reported from Enterprise Resource Planning (ERP) system solutions developed by the DAF and DoD for integration into the AFTOC data tables to be merged with data from legacy systems. The contactor shall develop BRs which enable the review of data from both the legacy data systems and new ERP system data sets for comparison and validation of weapon system costs. The contractor shall present all BR changes to the CCB for approval prior to implementation as referenced in Section 1.3 Roles and Responsibilities.

The contractor shall take all necessary steps to research, document, design, develop, implement, and deliver products to integrate data from various functional areas to produce new data relationships and analytical capabilities. Prospective new systems include but are not limited to the following:

1. DEAMS – This financial system is continuing to expand its coverage for DAF financial transactions. Some financial reports are currently translating and importing into GAFS-R. DEAMS is planned to replace GAFS-R, and the contractor shall accomplish appropriate translations and BR adjustments to process all data from DEAMS in an Standard Financial Information Structure/Standard Line of Accounting SFIS/SLOA compliant format.

2. Autonomic Logistics Information System (ALIS) / Operational Data Integrated Network (ODIN) - This logistics system is planned to provide the programmatic and logistics data for the F-35 program. Data normally provided by IMDS/REMIS/CEMS/SBSS will be obtained from ALIS/ODIN in entirely different formats and with different meanings. The Contractor shall provide technical consultation to ALIS/ODIN technical teams on the AFTOC data requirements and translate ALIS data reports into AFTOC data tables.

3. AF Integrated Personnel & Pay System (AFIPPS) - The Contractor shall accomplish appropriate translations, integration and business rules adjustments to incorporate AFIPPS into the AFTOC system product.

4. Maintenance, Repair, & Overhaul initiative (MROi) - Is a phased approach to replace major parts of the depot systems. There are three major pieces of these Capability Initiatives: MRO (Maintenance, Repair, & Overhaul); PLM (Product Lifecycle Management); SCM (Supply Chain Management). The contractor shall accomplish appropriate translations, integration and BR adjustments to incorporate MROi into the AFTOC system product.

5. Other - The contractor shall respond to changes in DAF or DoD source and feeder systems that replace or augment the current data systems.

2.2.1 The contractor shall investigate and develop recommendations for PMO’s consideration on new data sources or improvements of current data sources. For approved projects, the contractor shall take all steps to design, document, develop, acquire, import, implement, deliver and store the new/improved data sources in the AFTOC system. The contractor shall maintain these recommendations and provide updates quarterly on proposed and new data source enhancements. (A020).

2.2.2 The contractor will report progress on approved projects in monthly PMO Coordination

Meetings. (A015)

2.3 Task 3 - Data Conversions, Validation, and Processing. Following data transfer into the integrated data system, the contractor shall complete the following:

1. Filter incoming source raw data.

2. Convert the data files to standard file formats to enable validation/processing.

3. Utilize automation and repeatable processes to extract and validate the data through comparisons across sources, followed by summary calculation of data fields derived from the raw data elements.

4. Perform high-level validation of raw data to include file size comparison, valid values in raw data, and summarized calculations and retain this testing data for trend analysis.

5. Ensure the final product of this process consists of data files, which any commercially available software tools may use to read and query.

6. Generate, update, and maintain cross reference tables to automatically map general accounting system codes to cost elements and categories such as:

a. PEC to MDS

b. Element of Expense/Investment Code (EEIC) to Cost Assessment Program

Evaluation (CAPE) elements

c. EEIC and Resource Center/Cost Center (RCCC) to cost element

d. OBAN to Base

e. Operating Agency Code (OAC) to MAJCOM/FLDCOM

f. Equate part number, National Stock Number, Mission Design Series, Work

Unit Code, and nomenclature fields of individual equipment items (see Cross reference table listing Attachment 4 Cross Reference tables).

g. AFSC/FAC to CAPE

h. PEC TO RCCC

i. Others as required to create the quarterly AFTOC product

j. Others as outlined by the PMO

2.3.1 Supply Data Table (SDT). The contractor shall:

1. Implement update and maintain tables in the AFTOC Data Warehouse containing

SBSS (D002A/ILS-S), Wholesale, and Retail Receiving/Shipping System (D035K) data that has been processed and integrated to support DAF analytical communities.

2. Collect the various supply activity (daily, monthly, AFLMA, AFDS):

a. Integrate the data to ensure there are no exclusions to the supply transactions.

b. Ensure transactions are processed against a series of supporting cross reference tables for MDS code assignment (including the integration D043, FEDLOG, AF Accounting data, and other DAF data sources information).

3. Ensure the cross-reference table updates are complete with each data production run and document all BR changes.

4. Produce the SDT on a monthly, quarterly and annual basis to provide consumption patterns and cumulative financial reports.

5. Identify and report data anomalies and variances.

2.3.2 Maintenance Data Tables (MDT). The contractor shall:

1. Implement, update, and maintain an MDT based on the data extracts from IMDS, CAMS-FM, REMIS, and SBSS and integrate the data tables to provide the total DAF maintenance view.

2. Identify and implement methodology to join the MDTs and the SDT to provide complete maintenance and supply structured output.

3. Produce the MDT product update table on a quarterly basis.

4. Implement and maintain Programmed Depot Maintenance Scheduling System

(PDMSS) tables in AFTOC system to provide labor and material information by project Job Order Number (JON) and by serial number/MDS.

5. Integrate the PDMSS, Wholesale and Retail Receiving/Shipping System (D035K), and CAPRS data by JON, to provide access to depot maintenance wholesale information by serial number/tail number.

6. Identify and report data anomalies, and variances.

2.3.3 SDT/MDT Data Linkage. The contractor shall provide products that show data linked between the MDT and SDT. The contractor shall use intermediary data sources (such as IMDS, G081, and others) as necessary. The contractor shall provide user training and support as necessary. The contractor shall provide documentation, which clearly explains how the linkages were established, as required by the PMO.

2.3.4 Accounting Data Tables (ADT). The contractor shall:

1. Implement, update, and maintain an ADT based on the data extracts from the GAFS-R/DEAMS general accounting data, SBSS supply data, FES fuel data, TICMS munitions data, and E300Z personnel data/AFI 65-503 factors.

2. Augment the DAF accounting records for supply centrally managed Depot Level Reparable (DLR) consumption for supply data in the accounting record so both supply and financial DLR consumption data are made available.

3. Augment the DAF accounting records for fuel data from the Defense Logistics Agency DLA fuel system for aircraft systems and

a. integrate fuel costs into the accounting record so both fuel systems for fuel costs are presented in the accounting data table.

4. Calculate actual Military personnel costs with assigned personnel from the personnel system and integrated into the accounting record (location, CAPE element, weapon system, PEC, etc.).

5. Add training munitions consumption data to the accounting records by CAPE element and weapon system from the munitions data systems.

6. Integrate financial information from the Transportation Working Capital Fund (TWCF) to capture the cost of supporting the USTRANSCOM fleet into the AF accounting records.

7. Integrate Data tables with programmatic data flying hours (REMIS), inventory (REMIS), personnel (E300Z), modification data (IDECS) and engine actuarial data (CEMS) which will be used as the basis to allocate shared costs to the various weapon systems supported by the shared cost (allocation method is dependent upon the type of expenditure).

8. Develop and document quarterly BR changes to accommodate changes in the DAF operational and organizational structure to include the update/maintenance of cross reference tables. Ensure any BR changes are approved by the CCB prior to implementation.

9. Produce historical accounting data universe on a quarterly basis.

10. Identify and report data anomalies and variances.

2.3.5 Fuel Data Universe (FDU). The contractor shall:

1. Implement, update, and maintain an FDU based on the data extracts from the fuel data Enterprise Business System (EBS).

2. Integrate FDU with programmatic data (flying hours and inventory from REMIS) and other cross reference tables.

3. Develop the aviation fuel report to replace the AF accounting records in the ADT.

4. Provide cross reference tables to bring meaning to this data table with each data production.

5. Identify and report data anomalies and variances.

2.3.6 Engine Data Universe (EDU). The contractor shall update and maintain the EDU based on the data extracts from the GAFS-R Accounting data integrated with Basing & Logistics Analytic Data Environment (BLADE) engine actuarial data, and programmatic data (flying hours, inventory, and personnel) as appropriate.

2.3.7 Combat Munitions Data Universe (CMDU). The Contractor shall:

1. Update and maintain the CMDU to support the processing of DAF Munitions expenditure data, to include receiving and integrating the Munitions Expenditure File (MEF), Base Information File (BIF), Indicative Data Record (IDR), and Complete Round Code (CRC) tables.

2. Integrate the processed CMDU data to identify the training munitions costs by operational unit and category to support the CAPE reporting structure to include integrating the annual Ready Aircrew Forecasting Tool (RAFT) requirements to establish item cost ratios for locations supporting more than one weapon system that use common munitions components

3. Identify and report data anomalies and variances.

2.4 Task 4 - Data Presentation (Universes, Reports, Dashboards). The Contractor shall:

1. Maintain and enhance the customer interface and utilization capabilities for interacting with AFTOC data (interface/utilization tools are for acquiring data files and building ad hoc queries and reports for analyses).

2. Maintain and integrate new interface tools as technology changes provided in the technical report.

3. Develop, update, and maintain training content for all customer-facing business intelligence tools and reports.

2.4.1 Business Objects, Web Intelligence/Universe Generation. The Contractor shall:

1. Update and maintain Business Objects Web Intelligence, and all reporting tools approved by the PMO for AFTOC data to allow viewing from many users perspectives.

2. Ensure all applicable tools enable users to process ad hoc reports whereby data can be summarized, grouped, and ordered for user analysis.

3. Provide user access to standard report. Ensure the ability to create and export large reports in the SDT and MDT universes.

4. Develop, update, and maintain robust training and documentation for all user Business Intelligence (BI) tools. Provide ad hoc training sessions, webinars, and presentations.

5. Create and maintain a robust set of standard reports which will allow end users to query and expert data related to weapon systems.

6. Enhance standard reports as advised by the PMO

2.4.2 Tableau. The Contractor shall:

1. Develop and maintain a robust reporting mechanism and visualizations utilizing

Tableau Dashboards.

2. Enhance existing Tableau visualizations at the direction of the PMO.

3. Provide User and AFTOC usage metrics visualizations for use by the PMO.

4. Develop new dashboards/visualizations as outlined by the PMO.

5. Provide ad hoc training sessions, webinars, and presentations.

6. Update and maintain the AFTOC Metrics Tool:

a. Maintain a robust reporting mechanism and visualizations of Cost Per metrics for DAF Programs

b. Enhance the existing visualization.

c. Maintain robust documentation of all BRs associated with calculated metrics.

d. Provide new user and refresher training for the application.

e. Provide the Classified user community with a quarterly extract of the

Metrics applications that is easily transferrable to specified users via an unclassified data structure.

f. Create additional metrics as required by the PMO or approved user requirements.

2.5 Task 5 – Quality Assurance. The Contractor shall:

1. Execute a structured set of statistical quality assurance tools and techniques to identify the largest anomalies (unusual cost identified in source and processed data). Tools will include, and are not limited to:

a. Comparison of historical data between the current and previous quarter.

b. Comparison of related data sources.

c. Statistical analysis for year-to-year continuity of O&S costs.

2. Apply these tools prior to the release of the data to AFTOC users and summarize the results for further evaluation.

3. Automate the tools for efficient application and AFTOC data updates.

4. Recommend solutions for identified anomalies to the PMO for each issue prior to publication.

5. Conduct a pre-release meeting with the PMO prior to all Quarterly updates to present all results of the quality assurance findings. (A020).

6. Document the issues and provide analyst notes for the AFTOC users. (A020)

2.6 Task 6 – Controlled Unclassified Information (CUI) Data Markings. The contractor shall:

1. Comply with all requirements related to CUI markings of AFTOC data (all data will follow published DoDI, and National Institute of Standards and Technology (NIST) guidance).

2. Ensure CUI markings are clearly identified on all materials containing AFTOC data.

3. Ensure data encryption is utilized when sending AFTOC data via email or any other transfer mechanisms.

2.7 Task 7 – Configuration Control Board (CCB). The Contractor shall:

1. Provide Subject Matter Experts (SME) with a detailed understanding of the

DAF financial, maintenance, supply, and logistics data.

2. Serve as CCB members in their respective functional areas in support of the designated AFTOC Program Manager/CMA (as a CCB member, the contractor will have the collective responsibility to review and advise the CMA on change requests (CR) to the AFTOC information system).

3. Record meeting minutes and actions from all CCB meetings. (Reference Section 1.3 Roles and Responsibilities). (A013)

4. The contractor shall attend and participate in the CCB reviews and serve as voting members as outlined in the CCB Charter.

5. The Contractor shall provide the agenda prior to the meeting for review and approval by the PMO, and meeting minutes after meeting closure. (A013)

6. The Contractor shall provide a Configuration Management Plan and perform required updates to the plan as required (A004).

2.8 Task 8 – Training and User Group Meeting (UGM).

1. Training products /updates. The contractor shall:

a. Provide training for Users regarding the utilization of Business Objects Web Intelligence, Tableau, and other web-based data products as determined by the

PMO.

b. Recommend, design, and implement PMO approved training tools to provide the user easily accessible training and information on each of the AFTOC system products (these tools are intended to supplement recurring and annual in-person training).

c. Make the training products/events and Conference Reports available in accordance with schedules.

d. Post all training content on the AFTOC system site and maintain a comprehensive up to date training portal.

e. Obtain approval from PMO on Training agendas and recommended training materials (A013).

2. User Group Meeting (UGM). The contractor shall:

a. Prepare for, organize, host, and present AFTOC UGMs on an annual basis.

b. Prepare products to train AFTOC Users how to access the database and web-based data products.

c. Present the updates to the system, provide both financial and supply deep dive sessions, describe the data anomalies/issues for user consumption, and outline appropriate use of the data.

d. Present new products, data techniques, and provide technical/functional expertise for the AFTOC data.

e. Obtain approval from PMO on UGM agendas and recommended training materials (A013).

3. Training Library. The Contractor shall create, publish, and maintain a training library to house all training related to AFTOC (including but not limited to the UGM, User Specific Training, Tools training, Webinars, and Training Guides).

2.9 Task 9 – Helpdesk Operations/End User Support. The contractor shall provide user and PMO support to include:

1. Preparing briefing and advocacy materials on the status of the AFTOC system, as required by PMO. (A017)

2. Answering questions regarding AFTOC system inputs, database content, data element definitions, cost data outputs, and AFTOC BRs. The contractor shall provide end user support based on the following criteria:

a. All requests will be approved by the PMO for prioritization and determination of the reasonableness of the request.

b. The PMO will determine if the request should be supported and the delivery date of the response will be agreed upon between the PMO, the contractor, and the user.

3. Performing ad hoc database queries and develop reports to support data requests based on approval from the PMO.

4. Make recommendations to the PMO, based on evaluation of the user requests, additional cost data and information products, which may become part of the standard data reports available to end users.

5. Fully staffing and maintaining the Helpdesk, Monday through Friday, during business hours, to include, but not limited to the following:

a. tracking user accounts,

b. answering user requests,

c. maintaining user accounts,

d. providing daily report with user account status (disable warning, disable, delete). (A031)

6. Provide report that shows monthly and quarterly usage of AFTOC products. (A017)

7. Provide data orientation, and training to the user community on the utilization and operations of the AFTOC tools and databases.

8. Provide user support through the UGM and other training (reference section 2.8

Training and User Group Meeting (UGM)).

9. Provide services to support data requirements from other organizations as they pertain to AFTOC, based on data requests and trouble calls from the end users.

10. Develop and maintain Helpdesk Standard Operation Procedures manual. (A010)

2.9.1 User Account Maintenance. The Contractor shall:

1. Maintain all required cybersecurity certifications as outlined in the within the Risk

Management Framework (RMF) controls required to sustain the Authority to Operate (ATO) on Air Force and Common Computing Environments.

2. Review all DD2875 for completeness and accuracy.

3. Maintain all approved user accounts.

4. Notify users of account deactivation prior to the deactivation.

5. Notify users in advance of annual DD Form 2875 submission.

6. Notify users in advance of annual information assurance and data handling/distribution training requirements (such as CUI).

7. Deactivate user accounts after 35 days of inactivity.

8. Delete user accounts after 180 days of inactivity.

9. The contractor shall send user notifications based on the user’s profile:

a. Annual DD Form 2875

b. Annual Information Assurance certificates

c. Annual data handling/distribution requirements (such as CUI Certificates)

d. Contract expiration dates (contractor users)

e. Account deactivation due to inactivity

10. Provide PMO daily user status report. (A031)

2.10 Task 10 – Documentation – Process Documentation. The Contractor shall:

1. Maintain, update, and provide a documented description of the processes used in producing the AFTOC product. The documentation will detail all critical expertise, experience, BRs, analogous data sources, cross-reference tables, as well as specific logic processes used to demonstrate the requirements to produce and publish AFTOC data. Review documentation with PMO annually. (A005)

2. Complete and maintain comprehensive process, functional role, Quality Control, and system specific documentation which will facilitate cross training, and SME knowledge transition, similar to a Desk guide. (A005)

3. Ensure all BR changes are updated in the appropriate volumes below, as required.

4. Provide at a minimum one fully updated volume per period of performance, upon mutual agreement between Contractor and Government, from the list below (A006):

a. Data collection procedures

b. Raw data testing and validation procedures

c. Data validation and quality assurance procedures

d. Universe creation and reporting procedures

e. Helpdesk Standard Operating Procedures

f. Other areas as requested by PMO

2.11 Task 11 - Database Administration (DBA) – The Contractor shall:

1. Provide DBA support personnel responsible for overseeing the maintenance and security measures of AFTOC program databases. Knowledge of and experience with Federal security regulations, standards, DoD Security Technical Implementation Guide (STIGS) and processes including FISMA, FIPS, NIST, and FedRAMP.

2. Maintain the integrity, security, and availability of database(s).

3. Establish database user accounts

4. Administer, maintain, and implement policies and procedures for ensuring the security and integrity of the database(s)

5. Organize and format data for efficient query and storage processes

6. Evaluate requirements and recommend available DBMS products

7. Perform disaster recovery, performance analysis and tuning, index maintenance, and monitoring of data

8. Develop policies and procedures for ensuring the security and integrity of the database(s)

9. Perform database and software life-cycle activities to ensure highest level of system performance and availability

10. Support data modeling activities by way of prototype database implementations

11. Create data structuring/mapping, define data types and the connections between them

12. Create and manage multiple databases and assist in capacity planning and requirement gathering

13. Monitor, maintain database systems and troubleshoot problems that may arise

14. Maintain data integrity and security (manage roles and permissions of database users)

15. Generate traces, execution plans, identify performance issues, deadlocks/contention and resolve them

16. Create and manage constraints and indexes

17. Manage production, QA and development database environments

18. Create detailed documentation including diagrams of database infrastructure

19. Document relevant business processes and identify data flow, criticality and dependencies

20. Set up and maintain database infrastructure for the organization's (BI) needs

21. Support software developers with database operations including the development of complex Structured Query Language (SQL), tuning of Data Manipulation Language (DML) and the creation of stored procedures

22. Maintain security certifications

23. Ensure applicable STIGs are updated and applied to all databases quarterly

24. Provide completed Quarterly STIG checklists to AFTOC Information Systems Security

Manager (ISSM) (A024)

2.12 Knowledge, Skills & Abilities (KSAs) Required reference Appendix B for minimum experience requirements by labor category.

Contractor personnel performing under this contract shall possess:

2.13 The Contractor must demonstrate working knowledge of all systems outlined in section 2.1.4. Key Skillset requirements include:

2.13.2 Demonstrated engagement with feeder data systems for ensuring data feed timeliness and accuracy,

1. Identify data deficiencies, demonstrated approaches for managing data anomalies and deficiencies and leverage established relationships with providers for acquiring data in a timely and efficient manner.

2. Resolve any data discrepancies in the feed for timely production of AFTOC.

2.13.3 Demonstrated know-how of changes to the underlying feeder systems, and engagement with all stakeholders this is critical to the continuity of AFTOC data production.

2.13.4 Demonstrated understanding of the data in the underlying feeder systems critical to providing accurate and comprehensive data solutions and enhancing AFTOC end user products.

2.13.5 Demonstrated understanding and a vision for AFTOC in terms of depth and breadth of reporting within the framework of OSD O&S Cost Guide to integrate AFTOC with other environments to increase relevance through additional tools/interfaces/datasets

2.13.6 Prior work experience in relevant Air Force systems and agencies to provide subject matter expertise to develop appropriate business rules for ensuring correctness and accuracy of data.

Field level knowledge of how data is entered into the various systems, and an understanding of the shortcomings in the data, as it relates to system level mappings for ensuring accuracy/reasonableness of cost allocation to systems. Relevant hands-on experience fosters a deep understanding of data and how it is curated for creating business rules with the stated purpose of allocating costs to systems.

2.13.7 Demonstrated understanding of TOs, AFMANs and other regulations, instructions and resources applicable for deriving business rules applicable to AFTOC data processing.

Providing continuous improvement and recency for the stated purpose of mapping costs to systems.

2.13.8 Demonstrated understanding of the OSD O&S Cost Guide, Cost Per Flying Hour (CPFH) Program, Supply Requirements Review Board (SRRB), and data required to fulfill AFTOC’s charter. All of which are critical to evolving Visibility And Management of Operating Support Costs (VAMOSC) with updated CES while at the same time maintaining links to prior CES for comprehensive support to the user community. Critical to maintaining AFTOC Metrics Tool and providing support to the users in a manner suited for cost estimation. Critical to managing indirect costs.

2.13.9 Demonstrated understanding of the compliance requirements to include CUI, Standard Financial Information Structure (SFIS)/Single Line Of Accounting (SLOA), Risk Management Framework (RMF), and other applicable policies critical for maintaining the AFTOC Authority to Operate (ATO), compliance with DAF and DOW Security policies, as well as supporting financial audit requirements as outlined by OSW

2.13.10 Experience harvesting and implementing business rules via a structured mechanism for implementation of Business rules to maintain data accuracy and foster continuous product improvement.

2.13.11 Demonstrated capabilities in implementing robust statistical routines for ensuring data quality and data has been processed as defined in Task 3 & 4 sections 2.3 and 2.4 in the above paragraphs. Statistical routines will also be used to identify anomalies in the source data that could impact an AFTOC user’s analysis of the data

2.13.12 Ability to establish relationships with the AFTOC community to include data providers and consumers to have symbiotic relationships that allows proper usage of AFTOC data and a feedback loop that helps improve the AFTOC product.

2.13.13 Maintain an in-depth knowledge of data archives and data repositories for utilization as required based on changing rules within the Air Force that might require reprocessing of back-year data

2.13.14 Demonstrated expertise in the management of VAMOSC programs to ensure efficiently functioning teams, proper skill mix to support the program, manage communications with the CO and COR, transition planning, documentation, and timely resolution of issues.

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.

Performance Objective

PWS

Paragraph Performance Threshold Method of

Surveillance

SS-1 Provide and maintain qualified workforce

4.12, 6.10 Performance is acceptable when 85% of qualified personnel are on the job within two weeks of vacancy, unless approved by CO.

Periodic

SS-2 Process Documentation/Cross Training/transition plans

2.10, 4.12(6), 6.3, 6.4

Complete and maintain comprehensive process, functional role, QC, and system specific documentation which will facilitate cross training and transition of duties.

See PWS Para’s for delivery information.

Performance Threshold:

90% of upgrades delivered on or before the required delivery date during the evaluation period.

Bi-annually

SS-3 Timely Submission of deliverables

2.0 Deliverables processed

and published to the end user with less than 10% error. End User applications updated with monthly and quarterly product correctly and on time Performance Threshold:

90% of upgrades delivered on or before the required delivery

Quarterly

SS-4 Data retrieval and processing

2.0 As outlined in section

2.0 all data is retrieved, processed, backed up, and archived for recovery in case of system failure of database corruption. See PWS Para’s for delivery information.

Performance Threshold:

90% of upgrades delivered on or before the required delivery

SS-5 Database backups Quality Control testing/reporting

2.11 Outline of database

backup process and schedule. Backups to be performed weekly and reported to the PMO 100% threshold Performance Threshold:

90% of backups completed on or before the required delivery

Weekly

SS-6 CUI Data marking 2.6 All AFTOC data requests, end user applications which contain AFTOC data, Performance Threshold:

95% of documents marked correctly during the evaluation period.

Periodic

SS-7 STIG application 2.11 Provide quarterly STIG check list to ISSM and PMO 100%. (i.e. the 75th AFW or designated Common Computing Environment) Performance Threshold:

90% of STIG implementation delivered on or before the required delivery

SS-8 User Account Maintenance

2.9.1 User accounts are

disabled as outlined and compliant with Risk Management Framework requirements.

Performance Threshold:

90% of account monitoring on or before the required delivery date during the evaluation period.

100% Threshold

Periodic Surveillance

SS-9 Labor, travel, and Material

CLIN

invoices, Certificate of Conformance submitted timely and accurate

4.5 Provide detailed

monthly invoices, including hours by FTE, rates and all related fees to the PMO and COR 100% threshold

Monthly

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor, unless otherwise stated.

4.1 Contract Data Requirements.

Contract data products will be produced on and delivered to the AFTOC servers at Hill AFB UT.

Once CCE migration is complete all data production and delivery will be transitioned to the CCE environment. Other deliverables will be provided via DoD file transfer specifications to the AFTOC COR. The Government requires all deliverables that include Scientific and Technical Information (STINFO), as determined by the Government, be properly marked IAW DoD Directive 5230.24 and AFI 61-204 prior to initial coordination or final delivery.