DRAFT_AFTOC_PWS.docx

PERFORMANCE-BASED WORK STATEMENT

For

Air Force Total Ownership Cost Decision Support System

(AFTOC DSS)

To Support

AFTOC Project Office

520 SMXS/MXDPC

Hill Air Force Base, Utah

21 Dec 2016

AFTOC

1.0 GENERAL

1.1 Purpose

The purpose of this contract is to provide sustainment support of the Air Force Total Ownership Decision Support System (AFTOC DSS) to the Air Force (AF). This contract will provide data collection, storage, handling, processing, integration and production for AF legacy and future enterprise-level systems. The AFTOC DSS serves as the authoritative Air Force data source for Operating and Support costs to Congress and all levels of Deptpartment of Defense (DoD). Congress and DoD requires each military service to create, operate and maintain a Visibility and Management of Operating and Support Cost (VAMOSC) system. AFTOC serves as the Air Force VAMOSC system provided by 520 SMXS/MXDPC since 1998, and captures and maintains Operating and Support (O&S) costs for all fielded Air Force systems.

The 520 SMXS/MXDPC provides DoD personnel with rapid access to cost and logistics information for cost estimating and DoD decision support analysis at the tactical, operational, and strategic levels. 520 SMXS/MXDPC provides support for the AFTOC DSS and teams with the contractor for functional data expertise, and subject matter experts not available within 520 SMXS/MXDPC civilian workforce.

1.2 Scope

This requirement is to obtain DoD functional data system expertise (accounting, supply, maintenance, personnel, fuel, etc.) to assist the 520 SMXS/MXDPC Software Support Flight. This requirement is between the 520 SMXS/MXDPC and the Contractor. The Contractor shall provide support to the 520 SMXS/MXDPC in direct support of this Performance Work Statement (PWS). The 520 SMSX/MXDPC will serve as liaison between SAF/FMC - the Government Program Management Office (PMO), and the Contractor. All communication relating to data requirements in this PWS between the Contractor and Government PMO must go through the 520 SMXS/MXDPC.

The Contractor shall provide database management as well as data production expertise to assist the 520 SMSX/MXDPC in the maintenance and update of the AFTOC DSS. The 520 SMSX/MXDPC is seeking functional expertise in understanding DoD data systems as well as the data contained within DoD data systems. The Contractor must have a detailed awareness of the AF financial and logistics 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 SMXS/MXDPC provides Information Technology (IT) and server support for the AFTOC DSS and will team up with the Contractor to obtain data system functional expertise not available within the 520 SMSX/MXDPC civilian workforce. AFTOC data is collected from several existing DoD data systems. The Contractor shall collect and processes this data on the web servers maintained on Hill Air Force Base (AFB), Utah.

The Contractor shall collect, standardize, and integrate several data systems, and maintain the business rules to continue operation of the AFTOC data warehouse as well as maintain the data tables and the business intelligence tools to access the data tables. User access to business intelligence tools and data is maintained on the AFTOC web site. Additionally, the Contractor shall provide training on data access, understanding the data and use of the data.

The Contractor, also shall provide the AFTOC user community with information on data changes appropriate to understanding the data sets and custom data reports upon request.

This PWS consists of contract services for functional expertise of the data systems and data contained within the United States Air Force (USAF) and DoD systems required to produce the Total Ownership Cost (TOC), and the Reliability, Maintainability, and Deployability (RM&D) and other factors driving the cost of Air Force weapon systems and programs.

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. Space launch and control, and C4I operations support,

6. Major automated information systems, as appropriate.

7. Special Operations.

1.3 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 (DoD 5000.4). To accomplish this objective, the 520 SMSX/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 (MAJCOMs), AF operating agencies, and other federal entities.

2.0 REFERENCE DOCUMENTS

2.1 Government Documents/Data Systems

DoD data systems, along with any additional sources to be identified, characterized and acquired, will be directly integrated under this effort. SAF/FMC and the 520 SMSX/MXDPC will coordinate authorization to allow the Contractor to access data from the following:

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

· 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

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

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

· D200 for depot requirements and consumption information (several modules)

· 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

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

· 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

· 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

· 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

· 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

· Total Human Resource Management Information System (THRMIS) for programmed personnel authorization information PEC, organization, base, etc.

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

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

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

· AF Primary Aircraft Authorization (PAA) inventory from AF/A8

· Consolidated Engine Maintenance System (CEMS) data and actuarial information for building the engine data tables and integrated with CAPRS information

· General Service Administration (GSA) Fleet Drive-thru data base for vehicle information to develop a fuel consumption report by vehicle/Vehicle Identification Number (VIN)

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

· Automated Budget Interactive Data Environment System (ABIDES) President’s Budget to provide extracts based on this data set

· Combat Ammunition System (CAS) 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.

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

· Cost Per Flying Hours (CPFH) database for CPFH and flying hour program data

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

· SAF/FM published cost factors in AFI 65-503

The list of data systems above will be subject to updates, changes, structural changes and data system replacements during the life of the contract.

3.0 PERFORMANCE REQUIREMENTS/ DESCRIPTION OF SERVICES

The Contractor shall provide software engineering and technical services for the effort described in this Section.

3.1 Contractor Requirements

3.1.1. General

The Contractor shall store raw and processed baseline data in a Government provided data warehouse, identify problem areas, and recommend solutions to rectify problems. The Contractor shall continually interface with and support AFTOC users and USAF, MAJCOM, agencies, centers, laboratories, depots, etc. when performing research in support of analyses. The Contractor shall support the 520 SMSX/MXDPC by providing technical and analytical analyses of issues associated with the representation of total ownership costs of AF assets. The Contractor shall provide to the Government, 30 calendar days prior to the end of the Government fiscal year, an estimate for next Fiscal Year’s sales rate inclusive of all direct, indirect, and overhead, normally incurred but exclusive of temporary duty (TDY), leases for the Government, and any other extraordinary costs.

3.1.2 Interface Control Document

The Contractor will reference Memorandums of Agreement (MOA), “Document on the Role of 520 SMXS/MXDPC in Air Force Total Ownership Cost (AFTOC) Program Support” and other Memorandums of Agreement (MOAs) as reference documents. The document provides a statement of 520 SMXS/MXDPC responsibilities. Below is the list of Interface Control Document (ICD) / Memorandum of Understanding (MOU) / Memorandum of Agreement (MOA) / Interface Requirements Agreement (IRA) for which the Contractor will need to be familiar with in order to import, manage and process the AFTOC source data.

*Note: Highlighted systems currently do not have a data exchange agreement with AFTOC.

3.1.3 Integrated Product Team

The Contractor shall support a joint contractor-government integrated product team (IPT). The Government will provide technical experts to guide the effort of this contractor-government IPT during the course of this project. The IPT is made up of the SAF/FMC government program office as lead, the government support team (520 SMXS/MXDPC), and the Contractor.

The work to be performed by the Government, specifically 520 SMXS/MXDPC, in accordance with the MOA between SAF/FMC and the 520 SMXS/MXDPC.

3.2 Data Production

3.2.1 Data Management

This effort includes the continuing operations and maintenance of the AFTOC DSS, system improvement and new development tasks.The Contractor shall collect and load the raw and processed data into the Government provided data warehouse for AFTOC use to determine Air Force total ownership cost for systems and infrastructure. The Contractor shall ensure the data is secure from unauthorized users with access restricted to government employees and government sponsored contractors with a need to know. The Contractor shall not release the program data for the Future Years Defense Program (FYDP) or wholesale depot maintenance data (CAPRS, PDMSS) to manufacturing contractors.

The Contractor shall ensure the integrated data system will store, manage, and process data using commercially available software products where possible. This will enable users to manipulate data, link data elements and design queries to support cost-of-ownership calculations, reports, PowerPoint slides, and subsequent analyses requiring this information.

The 520 SMXS/MXDPC will host the AFTOC hardware and web site and provide access to the data integrated under this PWS.

Data warehouse requirements are reviewed and approved by the Government.The Contractor shall provide support to the 520 SMXS/MXDPC as they conduct reviews. The Contractor shall provide their recommendation to the Government PM. The 520 SMXS/MXDPC will determine all future changes to the final architecture of the data warehouse in cooperation with the Contractor. The Contractor shall ensure the data warehouse is capable of being expanded and is based on open system architecture so that upgrades of hardware and software can be performed without interruption of the operation of the warehouse.

The Contractor shall provide configuration management, optimization, and maintenance of the servers and software on which the integrated database is hosted. The Contractor shall perform data administration, product distribution, and implement a configuration management plan for organizing all file data and perform miscellaneous tasks (such as back-ups) required to maintain the system for storing and querying Air Force data to support cost and reliability reports and analyses. The Contractor shall provide full documentation of the processes, procedures and actions used to accomplish the aforementioned duties. The Contractor shall document all business rules and make them available to the 520 SMXS/MXDPC. The Contractor shall assist in operating the data warehouse, and control access to the data that will be limited to authorized users with a need to know.

The Contractor shall provide technical support, which consists of maintenance and modification of the data warehouse, data acquisition from the various USAF standalone data systems, data processing, and on-line reports and file downloads for authorized Government personnel. The Contractor shall implement user interface to support the web site and establish links to other pertinent data sources/systems.

Direct access to the data warehouse site will be provided to the Contractor to transmit and receive data. The Government program manager will approve the provision and control of passwords to authorized DoD and AF users.

The Contractor shall provide analytical support in evaluating changes in execution documentation and reporting, source data systems and their impact on AFTOC DSS. This support shall also include: interfacing with Air Force and DoD functional staff (logisticians, cost/finance analysts, manpower, mission operations, etc.); preparing materials for and participating in service reviews focus groups and modernization studies; and advising the 520 SMSX/MXDPC of matters concerning the distributing of AFTOC products and reporting cost data. The contractor shall provide conference agendas, meeting minutes, and conference reports for Program Management Review (PMRs), training events, and meetings as they relate to data management. (CDRL A001, A002, A003, A004, A011)

The Contractor shall support a migration to a DISA hosted server environment if this becomes necessary during time covered by this contract or option periods

3.2.2 Data Acquisition

The Contractor shall coordinate with appropriate DoD organizations maintaining the raw source data that are required for integration into the data warehouse and computation of total ownership and cost per flying hour or operating hour, and arrange for timely transfer of the required raw data (reference Section 2.1) to be processed and integrated. This transfer shall be automated to the greatest degree practical. The Contractor shall process all pertinent and appropriate data, including data yet to be accessed, and obtain and load the data into the integrated data system.

3.2.3 Data conversion, validation and “cleaning”

The Contractor shall ensure the data system consists of raw data from USAF and DoD sources, processed data and meta data. After loading incoming data into the integrated data system, the Contractor will filter incoming “raw” data, convert the data files to standard file formats, and clean and validate the data through comparisons across sources, followed by calculation of additional data fields derived from the raw data elements. The Contractor shall automate, to the greatest extent practical, these data validation and cleaning procedures. The Contractor shall ensure the final product of this process consists of data files that can be read and queried by any commercially available business intelligence software tools. (CDRL A010)

The Contractor shall generate cross reference tables to automatically map general accounting system codes to cost elements and categories (e.g., PECs to MDS, Element of Expense/Investment Code (EEIC) to Cost Analysis Improvement Group (CAIG) elements, EEIC and Resource Center/Cost Centers (RCCCs) to cost elements, OBANs to bases, Operating Agency Code (OACs) to MAJCOMS, etc.) and equate part number, National Stock Number, Mission Design Series, Work Unit Code, and nomenclature fields of individual equipment items. The Contractor shall maintain and update each quarter all cross reference tables necessary to define, standardize, integrate, and report Operating & Sustainment costs for AF systems and subsystems. (CDRL A010)

3.2.4 Interface and Utilization Tools

The Contractor shall implement and maintain a 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. The Contractor shall design, develop and integrate new interface tools as technology changes provided in the technical report. (CDRL A009, A010, A011)

3.2.5 Supply Data Table (SDT)

The Contractor shall implement and maintain tables in the AFTOC Data Warehouse containing usable Standard Base Supply System (D002A) and Wholesale and Retail Receiving/Shipping System (D035K) data that has been processed and integrated to support AF analytical communities. Supply Data Table (SDT) integration means collecting the various supply activity (daily, monthly, AFLMA, AFDS) and integrating it to ensure no supply transactions are excluded. Each transaction is processed against a series of supporting cross reference tables for MDS code assignment and includes integrating D043, FEDLOG, AF Accounting data, and other AF data sources information. The Contractor shall compute the appropriate net cost field to present the cost of AF weapon system sustainment. The Maintenance Data Table and SDT have integrated data element relationships for cost reporting. The Contractor shall ensure the cross reference table updates are made with each data production run. The Contractor shall provide technical support and consultation to the user community on the meaning of this data set and provide tailored reports upon request. The Contractor shall ensure the SDT are accessible by static reports (Reporting Services) and the Account tool (Microsoft Access Database) for user access to this information. The Contractor shall produce the Data table on a monthly, quarterly and annual basis to provide consumption patterns and cumulative financial reports. (CDRL A009, A010, A011)

3.2.6 Maintenance Data Tables (MDT)

a. The Contractor shall implement, 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. The Contractor shall incorporate the MDT into data cubes, static reports (Reporting Services) and the Account tool (MS Access Base) for user access. The Contractor shall ensure that the MDT be capable of being joined to the SDT (supply) for a complete maintenance picture. The Contractor shall produce the Data product update table on a quarterly basis. (CDRL A010)

b. The Contractor shall implement and maintain PDMSS tables in AFTOC DSS to support static reports (Reporting Services) and data cubes to provide labor and material information by project Job Order Number (JON) and by serial number/MDS. The Contractor shall integrate the PDMSS, Wholesale and Retail Receiving/Shipping System (D035K), and CAPRS data by JON, as much as possible, in order to provide reasonable access to depot maintenance wholesale information by serial number/tail number. The Contractor shall incorporate the depot data into data cubes, static reports (Reporting Services) for user access and produce the Data tables on an annual basis. (CDRL A011)

3.2.7 Accounting Data Tables (ADT)

The Contractor shall implement and maintain an ADT based on the data extracts from the GAFS-R general accounting data, SBSS supply data, FES fuel data, CAS munitions data, ABIDES budgetary data, and E300Z personnel data/AFI 65-503 factors. The Contractor shall 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. The Contractor shall augment the AF accounting records for fuel data from the DLA fuel system for aircraft systems and integrate fuel costs into the accounting record so that both fuel systems view the accounting system view for fuel costs are presented in the accounting data table. The Contractor shall calculate Military personnel costs with assigned personnel from the personnel system and integrated into the accounting record (location, CAIG element, weapon system, PEC, etc.). The Contractor shall add training munitions consumption data to the accounting records by CAIG element and weapon system from the munitions data systems. The Contractor shall integrate financial information from the Transportation Working Capital Fund (TWCF) to capture the cost of supporting the TRANSCOM fleet into the AF accounting records. The Contractor shall join ABIDES future year budgetary data to historical accounting records (appropriation, PEC, weapons system, OAC). The Contractor shall 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). The Contractor shall make quarterly business rule changes to accommodate changes in the AF operational and organizational structure to include the update/maintenance of cross reference tables. The Contractor shall prepare data tables in the unclassified environments. The Contractor shall produce historical accounting data table on a quarterly basis. The Contractor shall produce budgetary/future financial tables on an annual basis after the release of the President’s Budget (PB). The Contractor shall incorporate the SDT into data tables for access by static reports (Reporting Services) and the OnLine Analytical Processing Tool (OLAP) tool (MS Excel) for user access to this information at all intervals. (CDRL A010, A011)

3.2.8 Fuel Data Tables (FDT)

The Contractor shall implement and maintain an FDT based on the data extracts from the fuel data (EBS) and will integrate it with programmatic data (flying hours and inventory from REMIS) and other cross reference tables. The Contractor shall develop the aviation fuel report to replace the AF accounting records in the ADT. The Contractor shall provide cross reference tables to bring meaning to this data table with each data production. The Contractor shall produce data tables on a monthly, quarterly, annual basis and publish them to Online Analytical Processing (OLAP) and Excel based fuel reports for publication on the AFTOC DSS web page. (CDRL A009, A010)

3.2.9 Engine Data Table (EDT)

The Contractor shall update and maintain the EDT based on the data extracts from the GAFS-R Accounting data integrated with CEMS engine actuarial data, and programmatic data (flying hours, inventory, and personnel) as appropriate. The Contractor shall produce data tables at all available intervals and publish them to OLAP. (CDRL A010)

3.2.10 Combat Munitions Data Table (CMDT)

The Contractor shall update and maintain tables to support the processing of AF Munitions expenditure data. This includes receiving and integrating the Munitions Expenditure File (MEF), Base Information File (BIF), Indicative Data Record (IDR), and Complete Round Code (CRC) tables. The Contractor shall integrate the processed CMDT data to identify the training munitions costs by unit by category to support the CAIG reporting structure. This process includes 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. The Contractor shall incorporate the CMDT into data cubes, static reports (Reporting Services) for user access. The Contractor shall produce the data table on a quarterly basis. (CDRL A010)

3.2.11 Business Intelligence Tools/Cube Generation

The Contractor shall update and maintain an OLAP tool for AFTOC data that allows for viewing from many perspectives, through the familiar Microsoft (MS) EXCEL interface. The Contractor shall ensure the OLAP enables users to process ad hoc reports whereby data can be summarized, grouped and ordered in a layout most useful to the user. The Contractor shall provide user access to standard report views provided via MS Structured Query Language (SQL) Reporting Services. SDT and MDT can create large reports which are provided via the ACCOUNT tool and the contractor will provide user access via this tool. The Contractor will research commercial off the shelf (COTS) products in search of tools that can provide large data download capability for the AFTOC. The Contractor will replace the ACCOUNT tool when technology becomes available.

3.2.12 Quality Assurance of Processed AFTOC Data

The Contractor shall execute a structured set of statistical quality assurance tools and techniques to identify the largest anomalies in the source data and processed data. An anomaly is an unusual cost identified in the data that is analyzed by the Contractor’s statistician. The Contractor shall ensure the tools include a comparison of historical data between the current and previous quarter; a comparison of related data sources; and statistical analysis for year to year continuity of O&S costs. The Contractor shall apply these tools prior to the release of the data to AFTOC users and summarize the results for further evaluation. The Contractor shall automate the tools so that they can be applied quickly to avoid delays in AFTOC data updates. After the Contractor has identified the issues, they will make a recommendation to the Program Office for each issue. The Contractor shall recommend the solution to the problem before publication or defer the solution and document the issue as a note for the AFTOC users. (CDRL A010)

3.2.13 Web Operations

The Contractor shall assist and coordinate with the 520 SMXS/MXDPC in the maintenance of the AFTOC web site and the quarterly distribution of the AFTOC DSS product for user consumption. Such support includes integrating and aggregating the standard product output tables to produce the web site. This includes On-line Analytical Processing tools, Reporting Service data updates, ACCOUNT Tool, usage reports. This includes minor changes to code, web pages, new usage report requirements, and new security requirements. The Contractor shall maintain web access controls, security and assistance in performing help desk duties. (CDRL A010)

3.2.14 ABIDES

As required the Contractor shall implement a solution to provide access to the budgetary information from ABIDES data in the Non-classified Internet Protocol Router Network (NIPRNET) environment. This will include historical GAFS-R data processed on NIPRNET and ABIDES PB data (appropriations data table only). Data will be processed at least once per year when the President’s Budget is released and the file is available within ABIDES (or follow-on data system). Additional processing will be accomplished on an as required basis (e.g., weekly processing during the budget cycle). Reference optional tasks for schedule and applicability.

3.2.15 Process Documentation

The contractor shall provide continuity a documented description of the processes used in producing the AFTOC product. The documentation will detail the all critical expertise, experience, and specific processes used to demonstrate “how” , “why”, and “what” is required for producing the AFTOC DSS. (CDRL A015)

3.2.16 Information Assurance (IA)

Contractor personnel shall be in compliance with IA requirements:

a. AFI 33-115V2 - “Before becoming an Air Force network user an individual must have a favorable background investigation, be trained, and licensed.” And “In accordance with Chairman Joint Chiefs of Staff Manual (CJCSM) 6510.01, Defense in Depth: Information Assurance (IA) and Computer Network Defense (CND), all DoD military, civilian, and contractors will receive documented IA training prior to receiving access to the network”.

b. AFI 33-200 - IA Training and Certification. Depending upon assigned duties, all military, civilian, and Contractor personnel performing IA roles and responsibilities with Air Force Information System (ISs) require specialized IA training and certification.”

3.2.17 Assistance with the Risk Management Framework (RMF) and Federal Information Security Management Act (FISMA) survey, documentation, and requirements.

The Contractor shall assist the 520 SMXS/MXDPC in documenting the AFTOC system/server suite for compliance with requirements for the authority to operate (ATO) on the AF global information grid (GIG). This support will include providing answers to questions from the RMF certification processes with information concerning AFTOC security and IT architecture.

3.3 User Support

3.3.1 Normal User Support

The Contractor shall provide user and program office support to include the preparation of briefing and advocacy materials on the status of the AFTOC DSS system.

The Contractor shall provide support to AFTOC users to include performing ad hoc database queries, answering questions regarding AFTOC system inputs, database content, data element definitions, cost data outputs, and AFTOC costing algorithms. The Contractor shall, for other than routine requests, contact the 520 SMSX/MXDPC for prioritization and determination of the reasonableness of the request. The 520 SMSX/MXDPC will in turn coordinate with the Government Program Management Office (PMO) to 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. The Contractor shall recommend to the 520 SMXS/MXDPC, based on evaluation of the user requests, additional cost data and information products which can become part of the standard data reports available to end users.

The Contractor shall provide orientation training to the Government and User community on the utilization and operations of the AFTOC tools and databases. The Contractor shall provide user support through the User’s Group Meeting (UGM), and other training. (CDRL A005)

The Contractor shall provide a formalized user support process that meets the needs of the customer. The Contractor shall provide, based on data requests and trouble calls from the end users, the necessary services to support data requirements from other organizations as they pertain to AFTOC DSS. The Contractor shall be prepared to liaise, make database queries, advise, provide temporary support, and conduct analyses to help utilize AFTOC information or capabilities.

3.4 Specialized User Support

3.4.1 Specialized Data Delivery

From time to time, user requests will require the development of specialized data cubes or other formats in order to organize and deliver the information in a usable manner. The Contractor shall, as directed by the 520 SMXS/MXDPC, consult with appropriate users and design, develop, and deliver data cubes to the user’s specifications.

3.4.2 Systems Management

The Contractor shall support the 520 SMSX/MXDPC in complying with the various administrative reporting and information assurance security and access requirements. Organizations that may levy these requirements may include the Air Force Network Integration Center (AFNIC), AF CIO, OSD, OMB, Congress, and others.

3.4.3 Process Maintenance

The Contractor shall continuously review processes to improve the quality of the data and information delivered to the user to reduce the cost of the AFTOC DSS operations. This includes the review of business rules, data sets, assumptions, and ground rules; update and improvement of metadata and other documentation associated with the AFTOC processes. Which includes, the data contained in the AFTOC DSS source data changes and rehosting; conduct reviews; develop appropriate documentation and meta data; and define and propose new initiatives for Program Office approval to improve AFTOC operations costs. AFTOC documentation volumes and meta data will be delivered quarterly based on the schedule and priority provided by the 520 SMXS/MXDPC. (CDRL A011)

3.4.4 System Improvements and Enhancements

To increase the functionality and/or scope of the AFTOC DSS product, The Contractor shall track by individual cost accounts for cost reporting of the separately identifiable scopes of work to the 520 SMXS/MXDPC.

3.4.5 Data Acquisition

The Contractor shall investigate and develop recommendations for 520 SMXS/MXDPC Program Office consideration on new data sources or improvements of current data sources. For approved projects, The Contractor shall take all steps to design, develop, acquire, import, implement, deliver and store the new/improved data sources in the AFTOC DSS.

3.4.6 Enterprise Resource Planning (ERP) Changes and Updates

The Contractor shall investigate, 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 validation of weapon system costs.

Current Systems Are:

a. DEAMS – This financial system has been initiated and financial reports are currently translated and imported into GAFS-R. At some point in time DEAMS is planned to replace GAFS-R, and the Contractor shall accomplish appropriate translations and business rules adjustments.

b. Enterprise Business System (EBS) - The Contractor shall provide technical consultation to EBS technical teams on the AFTOC data requirements so that EBS data can be read and integrated. The Contractor shall translate EBS data reports into AFTOC data tables.

c. Autonomic Logistics Information System (ALIS) - 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 though in entirely different formats and with different meanings. The Contractor shall provide technical consultation to ALIS technical teams on the AFTOC data requirements and translate ALIS data reports into AFTOC data tables.

d. AF Integrated Personnel & Pay System (AFIPPS) - Reduces thousands of monthly payroll errors, predominantly induced by inconsistencies with personnel information; improves delivery of Personnel and Pay services to the AF Family; replaces antiquated and inflexible legacy systems that are increasingly difficult and expensive to maintain; provides an integrated solution that automates military pay internal controls and enables efficient audit of end-to-end processes. The Contractor shall accomplish appropriate translations, integration and business rules adjustments to incorporate AFIPPS into the AFTOC DSS product.

e. Maintenance, Repair, & Overhaul in an integrated (MROi) - Is a phased approach to replace major parts of the depot systems. There are three major pieces of these Capability Initiatives are: MRO (Maintenance, Repair, & Overhaul); PLM (Product Life Cycle Management); SCM (Supply Chain Management). The Contractor shall accomplish appropriate translations, integration and business rules adjustments to incorporate MROi into the AFTOC DSS product.

f. Other – The Contractor shall respond to changes in AF or DoD systems as discovered over as they fall within the scope of this PWS in paragraphs 3.4.5 and 3.4.6.

3.4.7 Information Integration

The Contractor shall take all necessary steps to research, design, develop, implement, and deliver products to integrate data from various functional areas to produce new data relationships and analytical capabilities.

4.0 CONTRACTOR STAFFING REQUIREMENTS

4.1 Staffing

The contractor shall establish and provide a qualified workforce capable of performing the required tasks. The contractor shall use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, support management and decision-making and facilitate communications. The contractor shall identify risks, resolve problems and verify effectiveness of corrective actions. The contractor shall institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance shall be tracked, and lessons learned incorporated into applicable processes. The contractor shall establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all contract efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness, and consistently high-quality delivery.

The contractor shall provide the results/status of the projects performed via status report to the assigned Contract Officer Representative (COR). The contractor shall provide all deliverables and status of technical tasks as defined in Section 3.2 of this PWS. This information shall be submitted IAW DD Form 1423, Contract Data Requirements List (CDRL A009, A010, A011).

4.1.1 Contractor Identification

All contractor/subcontractor personnel shall be required to wear Air Force (AF)-approved or provided picture identification badges so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation.

5.0 CONTRACTUAL REQUIREMENTS

5.1 Place of Performance

AFTOC data products will be produced on the AFTOC servers (currently located at Hill AFB). The contract team members can be located where determined appropriate and secure by the AFTOC Contracting Officer Representatives (COR).

5.2 Data Deliverables

5.3 Period of Performance

The contract period of performance will be 30 Jun 2017 through 29 Jun 2022. The contract will include a basic year and four option years.

5.4 Deliverables

Detailed Contract Data Requirements List is provided below IAW DFAR 204.7105 on DD Form 1423-1, FEB 2001. The Contractor shall deliver the financial data products in four phases coinciding with each quarterly update. The Contractor shall deliver the supply and fuel products in 12 phases coinciding with each monthly update of the SDT. 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. Failure to mark deliverables as instructed by the Government will result in non-compliance and non-acceptance of the deliverable. The Contractor shall include the proper markings on any deliverable deemed STINFO regardless of media type, stage of completeness, or method of distribution. Therefore, even draft documents containing STINFO and STINFO sent via e-mail require correct markings.

Contract data products will be produced on, and delivered, to the AFTOC servers at Hill AFB. Other deliverables will be provided the AFTOC Extranet file structure or emailed to the AFTOC CORs.

5.4.1 Program Plan and Schedule

The Contractor shall develop a plan for accomplishing the project tasks described in Section 3.2. This plan may be in Contractor’s format but will include an estimated time line and effort (in hours) to complete each individual element identified in the list of tasks for each government fiscal year. (CDRL A012)

5.4.2 Monthly Status/Cost Report

The Contractor shall prepare a monthly status report , summarizing work performed in the previous month, cost status, schedule status, and plans for the following month. (CDRL A006)

5.4.3 Program Management Review (PMR)

The Contractor shall prepare a detailed status report to be presented four times a year, unless otherwise scheduled by the Government PM. The PM and Contractor will meet at a mutually agreed place and time. The meeting shall follow an agreed upon format and summarize work performed to-date, cost/schedule status, program issues, and future plans. (A001, A002, A003, A007)

5.4.4 Technical Interchange Meetings (TIMs) (Agenda and Meeting Minutes) The Contractor shall conduct TIMs as required with the attendees to be coordinated with the 520 SMXS/MXDPC. The Contractor may be required to participate in monthly business meetings to discuss work issues, and also to attend and participate in the configuration control board and for management/compliance of the system IT processes with AF policy. The Contractor shall provide the agenda prior to the meeting and meeting minutes after. The Contractor shall provide required updates to the configuration management plan. (CDRL A001, A002, A004)

5.4.5 Quarterly Data Product Updates

The Contractor shall prepare quarterly updates to the database, the on-line analytical processing application, and the web-based data products. The Contractor shall produce a report describing the updates at the same time the updates are published. (CDRL A010)

5.4.6 Data Exports to Other Systems and Organizations

The Contractor shall prepare, organize, and export the following data to other DoD organizations and data systems:

· Monthly fuel consumption report to SAF/FMC

· Monthly supply consumption report to KDSS data system (AFMC/A4)

· Quarterly financial data feed for MS SQL database (SAF/FMC, AF/A9)

· Quarterly financial data feed for LIMS-EV Balanced Score Card data system (AF/A4)

5.4.7 Users Group Meetings, Training Products/Updates

The Contractor shall prepare for, organize, and present AFTOC User Group Meetings on an annual basis. The Contractor shall prepare products in order to train AFTOC Users how to access the database, the on-line analytical processing application, and other web-based data products. The Contractor shall present the updates to the system and describe the data anomalies and issues for user consumption and appropriate use of the data. The Contractor shall present new products and data techniques and provide technical/functional expertise for the AFTOC data.

The Contractor shall provide training for Users on how to access on-line analytical processing application and other web-based data products.The Contractor shall recommend, design and implement 520 SMSX/MXDPC approved training tools to provide the user easily accessible training and information on each of the AFTOC DSS products and how to use those products. These tools are intended to supplement recurring and annual classroom training. The Contractor shall make the training products/events and Conference Reports available in accordance with schedules (A001, A002, A003, A005).

5.4.8 Contractor Personnel Roster

The Contractor shall provide a personnel roster of all of the contractor’s employees to the Contracting Officer, Contracting Officer’s Representative within 3 days after the award. If there are subsequent changes in personnel during the period of performance of the contract, the Contractor shall provide an updated copy of the personnel roster with 3 days of these changes (A016).

6.0 SPECIAL CONSIDERATIONS

6.1 Security

6.1.1 Release/Removal of Documentation

The Contractor shall not release or remove system documentation, data, or reports generated by or through use of any Government systems including system information or data used to develop PWS related information. Release of data will be approved in advance by the government Program Manager.

6.1.2 Security Clearances

The AFTOC web system is an UNCLASSIFIED system, as are the data that populate this system. However, Contractor personnel shall hold appropriate security clearances when required to access the AF networks and websites.

6.1.3 OPSEC Requirement

The Contractor shall familiarize all new employees and conduct refresher sessions as needed in the areas of Operations Security. The Contractor shall comply with Operations Security requirements IAW AFI 10-701, OPSEC Security as supplemented, and AFI 31-401, Information Security Program, Standards for Storage and Handling Classified Material as supplemented.

6.1.4 Computer and Information Security

The Contractor shall be required to access the Hill AFB computer network to accomplish the requirements of this PWS and complete the following prior to receiving access:

· For those Contractor employees who require Government computer access only, a National Agency Check with written Inquiries (NACI) will be submitted. For those Contractor employees who require a higher level of investigation for a security clearance and Government computer access, a National Agency Check with Local Agency Checks and Credit Check (NACLC), a Secret or a Single Scope Background Investigation (SSBI) will be submitted IAW AFI 31-501, Personnel Security Management Program, and AFSSI 8522, Access to Information Systems.

· Contractors shall complete all required training via TSS. This training is currently available at: https://ooafmctss.hill.af.mil/TSSPortal/

· If a Government provided e-mail Account is required, The Contractor shall take Information Assurance Awareness Training prior to receiving access to that Account, and annually thereafter.

Contractors shall report in a timely manner to the appropriate security manager & Functional system Administrator (NLT 3 days IAW AFI 33-201, Computer Security).

· The Contract Administrator will complete a Request for Identification Credential (AFMC Form 496) for each Contractor employee requiring access to Hill AFB. The requests will be submitted to Pass and Registration (South Gate Visitors Center located at Hill AFB Utah.)

6.1.5 Government Assistance

The 520 SMXS/MXDPC will assist Contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government facilities and web sites/systems.

6.1.6 Confidentiality

The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information.