Work Scope Draft (002).pdf

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

1.0 DESCRIPTION OF SERVICES

1.0.1 Scope. This requirement is to obtain 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 SAF/FM/AFCAA/FMCY Government Program Management Office (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 update of the AFTOC system. The PMO requires functional expertise in understanding DoD data systems as well as the data contained within 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 DoD decision support. The 520 SWES/MXDPC will provide Information Technology (IT) and server support for the AFTOC system in the DISA milCloud 2.0 environment, and Hill AFB UT enclave 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 in the DISA milCloud 2.0 environment created specifically for AFTOC or any other environment as designated by the PMO. The contractor shall ensure contractor personnel take action to fully integrate into the SAF/FMC/AFCAA and 520 SWES/MXDPC creating a seamless Government-Contractor team. The contractor shall manage contractor personnel. 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, 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.

1.1 Background. Office of Secretary of Defense (OSD) has directed the AF to maintain this system in order to capture and report operational and support cost by system and subsystem (DoDM 5000.04). To accomplish this objective, 520 SWES/MXDPC requires data system expertise in order to produce the data used in studies for understanding acquisition and sustainment costs associated with AF systems. The current contract provides the data repositories to help federal entities identify historical cost drivers (aircraft, munitions, space systems, C4I systems and other systems). The output data products of this contract are used in analyses directly supporting OSD, AF Air Staff, AF Major Command (MAJCOM), AF operating agencies, and other federal entities.

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

1.2 Roles and Responsibilities. The designated Air Force Total Ownership Cost (AFTOC) SAF/FMC/AFCAA Program Manager is responsible for providing program direction to the contractor and 520 SWES/MXDPC Software Support Flight in support of this requirement. The AFTOC Program Manager (PM) 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 Business Rules (BR) resulting from user requirements, changes in source data or newly acquired data must be approved 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 BRC’s.

SAF/FMC/AFCAA 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, and controlled 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 are 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; and

4. Ensuring required activities are executed.

SAF/FMC/AFCAA 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.

SAF/FMC/AFCAA 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.

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

1.3 Sustainment. The contractor shall collect, standardize, and integrate data from several information systems as well as maintain the established and documented business rules 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:

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; and

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, and project supervision, as required in connection with this Performance Work Statement

(PWS).

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, HQ AF and HQ SF, data

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX source system owners, DoD, other 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 AF weapon systems.

2.1.1 The contractor shall coordinate with appropriate DoD organizations maintaining the raw source data that are 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. 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.2 The contractor shall reference the role of SAF/FMC/AFCAA/FMCY in all AFTOC program support Memorandums of Agreement (MOA), Interface Control Documents (ICD), and Memorandums of Understanding (MOU) and outline the roles and responsibilities of the AFTOC PMO, the contractor team, and the 520 SMXS/MXDPC.

Below is the list of ICD, MOU, MOA, and Interface Requirements Agreement (IRA), as of August 2021 for which the contractor will update and maintain in order 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 (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

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX 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 task, hours, and supply information by aircraft. Data to be integrated with D035K data to provide a link between depot maintenance actions to supply actions;

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

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

12. 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;

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

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX 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) in order to capture munitions replacement costs by type for integration into the AFTOC financial products;

21. AF 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/AF data sources, and logistics cross reference tables;

22. Cost Per Flying Hours (CPFH) database for CPFH and flying hour program 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.

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

AFTOC Data Exchange Systems Acronym Type System General Accounting & Finace System - Rehost GAFS-R Accounting Transportation Working Capital Fund TWCF Accounting Comprehensive Engine Management System CEMS Aircraft Engines 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 (H303) Supply & Depot Maint FedLog - Master Identifcation System FEDlog - MIS Supply Interchangeabiltiy & Substitution Data D043 Supply Item Apllication Data D200A Supply Item Descriptive Data Table D200A Supply Master Item Identification Control System MIICS (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 Recieveing & Shipping WARRS (D035K) Supply Logistics Installations & Mission Support - Enterprise View LIMS-EV Maint - Statistics Reliability & Maintenance Informationn 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 Miltary 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 Munitions

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

The contractor will have a detailed and thorough understanding of the systems and data elements outlined in section 2.3 and shall investigate, document, design, implement and maintain an AFTOC feature that allows data reported from ERP system solutions developed by the AF and DoD for integration into the AFTOC data tables to be merged with data from legacy systems. The contactor shall develop business rules that provide for the review of data from both the legacy data systems and new ERP system data sets for comparison and

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX validation of weapon system costs. The contractor shall present any business rule changes to the Configuration Control Board 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 in order 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 AF 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 business rules adjustments in order to process all data from DEAMS in an SFIS/SLOA compliant format.

2. Autonomic Logistics Information System (ALIS) / Operational Data Integrated Network (ODIN) - This logistics systems 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 business rules adjustments to incorporate MROi into the AFTOC system product.

5. Other – The contractor shall respond to changes in AF 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 SAF/FMC/AFCAA/FMCY 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

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX source enhancements. The contractor will report progress on approved projects in monthly PMO Coordination Meetings.

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

1. Filter incoming source raw data;

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

3. Utilizing 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; and

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; and

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 appendix X).

2.3.1 Supply Data Table. The contractor shall:

1. Implement update, and maintain tables in the AFTOC Data Warehouse containing Standard Base Supply System (D002A/ESCAPE), Wholesale, and Retail Receiving/Shipping System (D035K) data that has been processed and integrated to support AF analytical communities;

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

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

b. Ensure transactions are processed against a series of supporting cross reference tables for MDS code

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX assignment (including the integration D043, FEDLOG, AF Accounting data, and other AF data sources information);

3. Ensure the cross reference table updates are complete with each data production run, and document all business rule changes; and

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

2.3.2 Maintenance Data Tables. 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 AF maintenance view;

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

3. Produce the Data 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; and

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

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 may be necessary. The contractor shall provide user training and support as may be necessary. The contractor shall provide documentation, which clearly explains how the linkages were established.

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 AF accounting records for supply centrally managed Depot Level Reparable (DLR) consumption by supply data in the Accounting record so that both supply and financial DLR consumption data are made available;

3. Augment the AF accounting records for fuel data from the

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

DLA fuel system for aircraft systems and integrate fuel costs into the accounting record so that 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 business rule changes to accommodate changes in the AF operational and organizational structure to include the update/maintenance of cross reference tables. Ensure any business rule changes are approved by the CCB prior to implementation; and

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

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 (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.

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 LIMS-EV engine actuarial data, and programmatic data (flying hours, inventory, and personnel) as appropriate.

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

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

1. Update and maintain the CMDU to support the processing of AF 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; and

2. Integrate the processed CMDU data to identify the training munitions costs by unit by 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.

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; and

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 user 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 views provided via MS Structured Query Language (SQL) Reporting Services. 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 facing business intelligence tools.

Provide ad hoc training sessions, webinars, and presentations.

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;

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

4. Develop at least two new dashboards/visualizations per period of performance;

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

and

6. Create, update and maintain the AFTOC Metrics Tool:

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

b. Enhance the existing visualizations and maintain robust documentation of all business rules associated with calculated metrics;

c. Provide new user and refresher training for the Tool;

d. Provide the Classified user community with a Quarterly extract of the Metrics tools that is easily transferrable to specified users via an unclassified data structure; and

e. 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 Government

Program Office 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

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

2.6 Task 6 - 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 NIST guidance);

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

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 AF financial, maintenance, supply, and logistics data;

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

2. Serve as CCB members in their respective functional areas in support the designated AFTOC Program Manager/Configuration Management Authority (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); and

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

2.8 Task 8 - Training and Users Group Meeting.

1. Training Products/Updates - The contractor shall:

1. Provide training for Users regarding the utilization of Business

Objects Web Intelligence, Tableau, and other web-based data products as determined by the PMO;

2. Recommend, design, and implement Program Management 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);

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

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

2. Users Group Meeting (UGM) - The contractor shall:

1. Prepare for, organize, host, and present AFTOC User Group Meetings on an annual basis;

2. Prepare products in order to train AFTOC Users how to access the database, and web-based data products;

3. 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; and

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

2.8.1 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/Ender 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;

2. Answering questions regarding AFTOC system inputs, database content, data element definitions, cost data outputs, and AFTOC business rules:

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

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. Recommending 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. Staffing and maintaining the Helpdesk: tracking user accounts, user requests, maintaining user accounts, providing weekly report with user account status (disable warning, disable, delete)

6. Providing monthly / quarterly usage reports of AFTOC products

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

8. Providing user support through the UGM and other training

(reference section 2.8 Training and User Group Meeting)

9. Providing 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. Maintaining and report user access

11. Reporting user account status to the PMO weekly

12. Developing and maintain Helpdesk Standard Operation

Procedures manual.

1. User Account Maintenance. The contractor shall:

1. Review all DD2875 for completeness and accuracy

2. Maintain all approved user accounts

3. Notify users of account deactivation prior to the deactivation

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

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

6. Deactivate user accounts after 35 days of inactivity

7. Delete user accounts after 180 days of inactivity

8. Send user notifications for the following:

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.

2.10 Task 10 - Documentation – Process Documentation. The contractor shall:

Air Force Total Owner Cost Support Services (AFTOC) FA7014-22-X-XXXX

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, business rules, analogous data sources, cross-reference tables, as well as specific logic processes used to demonstrate “how”, “why”, and “what” is required to produce and publish AFTOC data;

2. Ensure all business rule changes are updated in the appropriate volumes as required;

3. Provide at least one fully updated volume per period of performance:

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

SAF/FMC/AFCAA/FMCY.