MROi OSFOS PWS.docx

PERFORMANCE-BASED WORK STATEMENT (PWS)

MAINTENANCE, REPAIR AND OVERHAUL initiative (MROi) ON-SITE FUNCTIONAL OFFICE SUPPORT (OSFOS)

U.S AIR FORCE

OO-ALC/Hill Air Force Base WR-ALC/ Robins Air Force Base OC-ALC/ Tinker Air Force Base AMARG/Davis Monthan AFB

8/31/2022

MAINTENANCE, REPAIR AND OVERHAUL initiative (MROi) ON-SITE FUNCTIONAL OFFICE SUPPORT (OSFOS) i Contents

DESCRIPTION OF SERVICES

The purpose of this Advisory and Assistance Services (A&AS) contract is to provide the Air Force Sustainment Center (AFSC) Maintenance, Repair, and Overhaul initiative (MROi) Functional team on-site functional support. The contractor shall be required to be knowledgeable of both AFSC Depot operations, to include financials and maintenance, and the corresponding AFSC legacy logistics Information Technology (IT) systems supporting those business operations. The contractor shall assist government personnel in ensuring planning and requirements for the future MROi system operations and business process changes are addressed as the Government plans for the implementation of MROi. The development of the MROi system is a separate Air Force Lifecycle Management Center (AFLCMC)/HI-managed acquisition contract with a separate development contractor, currently Accenture Federal Services (AFS), and that effort shall not be confused with this requirement for A&AS support to the AFSC’s MROi Functional Management Office (FMO) team. The contractor’s expertise on this On-Site Functional Office Support (OSFOS) effort shall include; schedule management; legacy systems transition analysis and support during execution; and Doctrine, Organization, Training, Leadership, Personnel, Facilities - Policy (DOT_LPF-P) efforts, all to prepare and support AFSC’s organic depot complexes for planning and execution of the implementation of the MROi solution and new business processes. The final aspect of this effort will be a support role assisting government personnel in preparing the sites for synchronization of DOT_LPF-P efforts and implementation preparation activities which must be completed and in place to support the fielding of the MROi software solution. This requirement will not include personal services or inherently governmental functions.

BACKGROUND

AFSC’s Depot Operations

Organic depot maintenance supporting Air Force operations are managed within Air Force Materiel Command’s (AFMC’s) AFSC. AFSC’s depot operations are organized under three (3) Air Logistics Complexes (ALCs): Warner Robins ALC (WR-ALC), located at Robins Air Force Base (AFB), GA; Oklahoma City ALC (OC-ALC), located at Tinker Air Force Base, OK; and Ogden ALC (OO-ALC), located at Hill Air Force Base, UT. OO-ALC also operates the Aerospace Maintenance and Regeneration Group (AMARG) in Tucson, AZ, and other Geographically Separated Units (GSUs). Each of the three (3) Complexes further manage their operations by dividing work, to include but not limited to, the following maintenance groups:

The Complexes are large-scale industrial facilities responsible for billions of dollars of depot-level repair, each without enterprise level direction. Without this direction, depot maintenance repair organizations were compelled to develop multiple-site, weapon system, and repair line-unique processes and systems to fulfill individual and specific functional needs. The situation has been evolving for the past 20 years and thus, AFMC has been unable to standardize enterprise processes or leverage proven commercial best practices and advancing technologies in enterprise solutions.

AFMC and AFSC management and Complex Commanders are committed to reengineering business processes and standardizing operations. While the core focus of MROi entails integration of the full breadth of maintenance planning, scheduling, and execution mission functions, with integrated financials at the point of work, it also includes the touch points with supply supportability, product data and engineering processes. MROi fully integrates maintenance and Air Force (AF) Working Capital Fund (AFWCF) financials in a single solution. AFMC/FMF, AFSC/FM, and AFSC/LG are responsible for managing a cohesive functional team, and need supplemental contractor expertise to provide on-site support to the government functional team. The collective MROi functional team encompassing all sites is hereafter called the FMO.

MROi Overview

AFSC’s MROi program is a transformation and standardization of both the business processes and enabling materiel solution. This will provide AFSC with an integrated capability for planning, scheduling, and executing organic depot maintenance. MROi will replace legacy system-driven processes and create a more efficient workforce by optimizing resource consumption and workload assignment, facilitating what-if planning and reducing rework by integrating quality and maintenance-driven financial processes within depot maintenance operations.

MROi will use the Commercial-Off-The-Shelf (COTS) software product consisting of the Oracle complex Maintenance, Repair, and Overhaul (cMRO) module plus ~23 other related E-Business Suite (EBS) modules (hereafter referred to as the MROi solution). The MROi solution requires the development of non-COTS Report, Interface, Conversion, Extension and Workflow (RICE-W) objects. The aforementioned separate acquisition development contractor is responsible for developing and implementing the end MROi solution consisting of the COTS software and RICE-W objects.

The FMO team must support the MROi acquisition program’s use of Scaled Agile Framework (SAFe) for Agile development activities. The initial implementation effort will include a subset of the total functionality and occur at PMXG at OC-ALC, Tinker AFB, OK. The second stage will provide the entire functionality and be implemented incrementally at all ALC Maintenance Groups (MXGs). Figure 1 shows the organizations to which MROi will implement. Figure 2 provides the current MROi schedule as of 2 Nov 2021, subject to change.

Figure 1

Figure 2

BASIC SERVICES

Upon day one of the Period of Performance (PoP), the combination of personnel at each site shall have the following knowledge base:

Functionality of the systems listed in Appendix B.

Extensive knowledge of ALC depot maintenance and financial management operations.

General knowledge of the MROi acquisition program and SAFe agile development principles and roles.

The contractor shall assist the government in the creation and modification of transition plans for systems MROi will subsume (Appendix B). The contractor shall be required to provide site specific information for the transition plans. The contractor shall use support of government on-site personnel as sources where necessary. The contractor shall ensure site specific plans are current based on any modifications to both MROi and those systems to be subsumed and provide updates to site specific plans on semi-annual basis. (CDRL A001) The contractor shall provide site specific insight into the MROi site activation plans during FMO reviews. Activation plans will cover steps up to a year prior to the start of a site’s actual implementation. The contractor shall assist the Government on-site personnel in tracking government-required steps within the Activation Plan.

The contractor shall review user test plans and scripts, as well as detailed system step-by-step procedures and provide recommended changes to the MROi FMO. The test scripts for each Government Integrated Test (GIT) event shall be reviewed and inputs provided approximately two (2) to three (3) months prior to the GIT event. There are currently four (4) GIT events scheduled. This may increase to six (6) GIT events.

The Contractor shall review AF-provided business processes, policies, and procedures, and provide recommendations to the FMO team in accomplishing business process changes, business rules that need to be documented, and Legal Regulatory and Policy (LRP) implication requirements. The contractor shall support the on-site government teams in ensuring all local, AFSC, AFMC, and AF policies that may require changes due to MROi future business operations, are identified, and recommended changes are drafted. There will be no more than 20 policies per ALC to be reviewed annually.

The Contractor shall collaborate with the FMO in developing agile scrum team level test scripts and perform test and design analysis activities within the program’s agile design and development framework.

The Contractor shall provide analyses and research findings on government-provided operational, transitional, and data exposure interface requirements. There are currently estimated no more than 50 trading partners with which MROi will exchange information. Analyses shall include reviewing data object/element information associated with incoming and outgoing data flows for each interface. (CDRL A001) The Contractor shall maintain a master site-by-site implementation planning spreadsheet which includes, but is not limited to, major workload data by operating/using location, organization hierarchy, user roles and EBS licensing estimates, quantities of users by role, and IT resources. (CDRL A001) The Contractor shall review user training documentation developed by AFS and provide inputs to the FMO-Wright-Patterson AFB, OH team on products related to user training and communication products.

The Contractor shall provide support to MROi Government Product Managers, Product Owners, and government subject matter experts on scrum teams in support of the MROi development effort. The support shall include assisting Government Product Managers and Product Owners with providing requirements clarifications during scrum team activities. This support shall be on a non-interference basis to all previous requirements in paragraphs 3.2 to 3.9.

Minimum Team Complement (MTC) The MTC is defined as the required minimum amount of staffing necessary for effective performance. The Government will solely determine the MTC. The contractor shall ensure the MTC specified is maintained throughout the PoP.

The contractor shall designate one (1) of the nine (9) contractors as a Project Lead and each site shall have a designated Site Lead.

TABLE 1 - MTC

OC-ALC

Tinker AFB, OK

OC-ALC

Tinker AFB, OK

OO-ALC

Hill AFB, UT

OO-ALC

Hill AFB, UT

AMARG

Davis-Monthan AFB, AZ

WR-ALC

Robins AFB, GA

WR-ALC

Robins AFB, GA

Skill Category Descriptions Senior Functional Analyst II Minimum/General Experience A minimum of eight (8) years’ experience, of which at least six (6) years must be specialized. Specialized experience includes: superior functional knowledge of task-order-specific requirements, or developing functional requirements for complex integrated IT systems. Must demonstrate the ability to work independently or under only general direction.

Functional Responsibility Analyzes user needs to determine functional and cross-functional requirements. Performs functional allocation to identify required tasks and their interrelationships. Identifies resources required for each task. Provides daily supervision and direction to support staff. Specialized experience includes: analysis of business applications on MRO/ERP systems, analysis experience, assess MRO/ERP against business processes and identify business process changes needed, and support migration from legacy systems to enterprise system implementation.

Senior Functional Analyst III Minimum/General Experience A minimum of ten (10) years’ experience, of which at least eight (8) years must be specialized. Specialized experience includes: superior functional knowledge of task-order-specific requirements, or developing functional requirements for complex integrated IT systems. Must demonstrate the ability to work independently or under only general direction on requirements that are complex to analyze, plan, and program.

Functional Responsibility Analyzes user needs to determine functional and cross-functional requirements. Performs functional allocation to identify required tasks and their interrelationships. Identifies resources required for each task. Provides daily supervision and direction to support staff. Specialized experience includes: analysis of business applications on MRO/ERP systems, analysis experience, assess MRO/ERP against business processes and identify business process changes needed, and support migration from legacy systems to enterprise system implementation.

REPORTING REQUIREMENTS AND DELIVERABLES

Technical Report The Contractor shall develop technical reports, white papers, and presentations as requested by the AFSC/LZDB Government leads In Accordance With (IAW) paragraphs 3.2 through 3.10 of this PWS. (CDRL A001) Monthly Status Report (MSR) The Contractor shall prepare an MSR summarizing at a minimum; progress of the previous month, status of contract milestones, cost status, schedule status, current efforts, completion/expiration dates, any problems encountered, and plans for the following month. (CDRL A002) Program Management Plan (PMP) The Contractor shall develop a PMP that shall contain at a minimum; major milestones expected, resource management strategy and planning for the project and project assumptions/constraints. (CDRL A003) Table 2 - SERVICE SUMMARY

The Contractor shall provide technical reports IAW PWS.

- Up to 10 documents: No more than one document is returned by the government for rework

- From 11-20 documents: No more than two documents are returned for rework -More than 20 documents: No more than 10% of the documents are returned for rework

(CDRL A001)

The Contractor shall provide a PMP containing major milestones expected, resource strategy and planning for the project, and key assumptions/constraints.

3.12.3 To be submitted to the AFSC/LZDB Government leads and COR 20 business days after contract award and 10 business days after revision due to necessary government comments incorporation. Document contains required information and contains 90% of required management detail and actionable Government dependencies if assumptions/constraints are government related. (CDRL A003)

CONTRACT DATA REQUIRMENTS LIST (CDRL)

CDRL requirements. Contract information data shall be delivered, as assigned by the Ordering Activity, electronically IAW the corresponding requirement for each Data Item listed in Table 5-1 (below). The Contractor shall submit CDRLs according to the due date indicated and have no more than one CDRL per quarter submitted after the identified due date. Substantive mistakes shall be corrected within times annotated on the CDRL forms and corrective action taken to prevent recurrence of inaccurate and/or late CDRLs.

Table 3 - CDRLs

GOVERNMENT FURNISHED PROPERTY (GFP) AND FACILITIES

GFP is not anticipated on this contract IAW Federal Acquisition Regulation (FAR) 45.000(b)(5); however, common office equipment and other Government property are available for use by the Contractor in the performance of the contract. All Government property is incidental to the place of performance and will remain onsite and accountable to the Government. The Government will provide workspace, working supplies, furniture, access to business telephones, and computers. Government-provided computers to facilitate network connectivity, computer facilities, and computer time are for business purposes only. All Government Furnished Equipment (GFE), Government Furnished Software (GFS) and Government Furnished Material (GFM) shall be returned to the Government upon completion of this contract. The location of the government provided office space listed in Table 1 is subject to change.

Table 4: Government-provided office space

(Bldg & Base)

(Furnished by the Government)

Hill AFB, UT

Office space, desk, chair, file cabinets, bookcases, telephone, e-mail, and Internet access. A computer with Windows and Microsoft Office, and Microsoft Project software, and a connection to a printer on the Local Area Network (LAN).

Davis-Monthan AFB, AZ

Office space, desk, chair, file cabinets, bookcases, telephone, e-mail, and Internet access. A computer with Windows and Microsoft Office, and Microsoft Project software, and a connection to a printer on the LAN.

Robins AFB, GA

Office space, desk, chair, file cabinets, bookcases, telephone, e-mail, and Internet access. A computer with Windows and Microsoft Office, and Microsoft Project software, and a connection to a printer on the local area network LAN.

Tinker AFB, OK

All data, information, reports, analyses, briefings, property, etc. provided or created by the Government, including applications, and any property acquired by the Contractor under this contract remains the property of the Government and shall be provided or returned to the Government upon completion of the requirement unless alternate disposition instruction are provided. The Contractor shall protect Government property to prevent damage during use by the Contractor. All Government property shall be returned to the Government in working (serviceable) condition. The Contractor shall report within two (2) calendar days to the Contracting Officer (CO) and/or COR all available facts relating to each instance of damage to Government property.

GENERAL INFORMATION

INSTALLATION-SPECIFIC SAFETY AND HEALTH STANDARDS

Volunteer Protection Program (VPP)

The Air Force has adopted the VPP as recognized by Occupation Safety Health Association (OSHA). VPP impacts all “applicable contractors” operating on Air Force Installations. It is the Contractor’s responsibility to ensure all of its employees performing work have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. Detailed information on VPP is available on the OSHA website (http://www.osha.gov/dcsp/vpp/index.html). Contractors, whether regularly involved in routine site operations or engaged in temporary projects, must follow the safety and health rules of the installation or VPP site.

VPP requirements apply to contractors whose employees work more than 1,000 hours per quarter. The Contractor shall flow-down these requirements to all sub-contractors who qualify as applicable contractors under this contract.

Safety Requirements

In the event of an accident/mishap, the Contractor shall take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence. A written or email copy of the mishap/incident notification shall be sent within two (2) calendar days to the COR, who will forward it to the appropriate safety office for that location. (CDRL A004)

SECURITY REQUIREMENT

The contractor shall comply with Department of Defense (DoD) and AF location specific security requirements that pertain to this contract. The contractor must meet the same security requirements as Government employees for access to the Government installation’s network, Automated Information Systems (AIS), and controlled access areas.

The efforts required for this contract are expected to be UNCLASSIFIED and should not require the contract personnel to obtain a security clearance. In the event circumstances change, the Program Manager and/or COR will coordinate the procedures to obtain any clearances. The contractor shall ensure that sufficient personnel have an appropriate clearance to obtain and maintain requirements for any level of access required. Contractor personnel shall hold appropriate security clearances when required to access AF networks.

Common Access Card (CAC)

A CAC card shall be required for all tasks under this effort. It should be noted that this process might take a minimum of four (4) weeks to complete. Contractor personnel must obtain and maintain a base e-mail account ".mil” email address.

The contractor shall comply with the respective facility’s instruction, Issue of Common Access Cards to contractors (Contractor Verification System), and must meet investigation and comparable security checks commensurate with the level of access required.

The contractor shall comply with Air Force Manual (AFMAN) 17-1301, Computer Security (COMPUSEC), relative to access to Information Systems and training requirements commensurate with the level of access required.

Refer to Air Force Federal Acquisition Regulation Supplement (AFFARS) clause 5352.242-9001, Common Access Cards (CAC) for contractor personnel for additional instructions and procedures that apply to obtain and manage CACs. One of the provisions of this clause is that the Contractor shall provide a listing of personnel who require a CAC to the CO. In addition, the contractor shall also submit the listing to the Program Manager (PM) and COR.

At the end of the contract period, or when an employee’s employment has concluded the contractor shall out process each employee and ensure all media such as entry cards and CAC cards are turned in to the PM and/or COR.

The Contractor shall obtain a Building Identification (ID) and access card from the appropriate Building Security Manager for all their employees.

NETWORK

The contractor shall complete Network User Licensing Computer Based Training (CBT) per Air Force Instruction (AFI), Technical Order (T.O.) 00-33A-1001 Technical Manual Methods and Procedures General Cyberspace Support Activities Management Procedures and Practice Requirements. Contractor employees requiring a Government provided e-mail account shall annually complete the DoD Information Assurance Cyber Awareness Challenge training.

DISABLING ACCOUNTS

The Contractor shall report personnel who no longer need network or Automated Information System (AIS) access to the appropriate Security Manager and Functional System Administrator (FSA) within two (2) calendar days of completion of contractor access requirement.

PHYSICAL SECURITY

The Contractor shall be responsible for safeguarding all GFP provided for contractor use. At the close of each work period, Government facilities, property, and materials shall be secured.

Lock Combinations

The Contractor shall establish and implement methods of ensuring any lock combinations are not revealed to unauthorized persons. The Contractor shall ensure lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan. (CDRL A005)

Conservation of Utilities (OO-ALC)

The Contractor shall ensure that contractor employees follow applicable Air Force base utilities conservation practices to reduce waste as much as practicable. The contractor personnel on Hill AFB shall be aware of OO-ALC Energy Policy. A copy shall be provided upon request. Link: https://usaf.dps.mil/sites/OOALC/mass%20announcements/oo-alc%20energy%20policy.pdf Contractors contribute to the effectiveness of the OO-ALC Energy Management System (EnMS), including the achievement of its objectives and energy targets. Through this contribution, the benefits of improved energy efficiency are realized. It is expected that the contractor ensures their activities are in line with improving OO-ALC energy performance. Contractors found negligent of these requirements can have a negative impact.

The Contractor shall be responsible for operating under conditions that prevent the waste of utilities, which include the following:

Lights shall be used only in areas where and when work is actually being performed.

Mechanical equipment controls for heating, ventilation, and air conditioning systems shall not be adjusted by the contractor or by contractor employees unless authorized.

Water faucets or valves shall be turned off after the required use.

Government telephones, computers, fax machines, copy machines, and other equipment shall be used only for official Government business.

QUALITY CONTROL PROGRAM (QCP)

The Contractor shall establish a complete QCP via a Quality Management Program to ensure the requirements of this contract are provided as specified. The Contractor's quality management program shall comply with the minimum quality management systems elements specified in the American National Standards Institute (ANSI), American Standards Organization (ASO), and International Standard Organization (ISO) family of standards. (CDRL A005)

QUALITY ASSURANCE

Upon award the CO will appoint the COR in the Procurement Integrated Enterprise Environment (PIEE), Joint Appointment Module (JAM).

The COR is responsible for providing continuous technical oversight of the Contractor’s performance. The COR(s) or alternate(s) will inform the Contractor when discrepancies occur and will request corrective action. The services to be performed by the Contractor during the period of this contract are at all times and places subject to review by the CO or authorized representative(s).

GOVERNMENT OBSERVATION

The COR will be tasked by the CO to perform periodic visits to the Contractor for the purpose of observing how work is performed. Government personnel, other than the CO and CORs, may from time-to-time, with CO coordination, observe contractor operations. These personnel may not interfere with Contractor performance or make any changes to the contract.

HOURS OF OPERATION

The Contractor is responsible for designating work hours for their employees, but at a minimum shall be available as required by the Government, this may vary depending on location, project, or event. Government’s normal hours of operations fall between 6:00 a.m. – 6:00 p.m., Monday through Friday.

Unless otherwise required by the Government, the Contractor shall not have access to Government facilities to work on the following federal holidays: New Year’s Day, Martin Luther King, Jr.’s Birthday, President’s Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans’ Day, Thanksgiving Day, and Christmas Day. If the holiday falls on Sunday, it is observed on Monday. If the holiday falls on Saturday, it is observed on Friday.

If required to work from home or an alternative location due to any reason, the contractor will be notified by the COR, or government site lead.

PLACE OF PERFORMANCE

Work shall be performed at the following Government locations. Specific on-base locations are subject to change:

Tinker AFB, OK 73145 Robins AFB, GA 31098-1607

(405) 736-4220 478-926-3722

REPORTING OF CONTRACT LABOR HOURS

The Contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.sam.gov/SAM/pages/public/index.jsf.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 01 October through 30 September. While inputs may be recorded anytime during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Sam.gov website or the Fed helpdesk.

Uses and Safeguarding Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

PUBLICATIONS

The Contractor shall comply with AF publications, regulations and operating instructions in the use of materials, procedures, and processes applicable to the work requirements.

The Contractor shall perform all services IAW the latest applicable regulations, policies, and guidance. Air Force Instructions (AFIs) can be obtained from the Internet web site, http://www.e-publishing.af.mil. The Contractor shall be responsible for researching and abiding by all applicable supplements.

INHERENTLY GOVERNMENT FUNCTIONS/PERSONAL SERVICES

None of the functions to be performed under this requirement are inherently Governmental. Additionally, no part of this PWS or the basic contract shall be construed to require the Contractor to provide personal services to the Government. The Contractor shall comply with this PWS in its entirety.

The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes or has reason to believe any actions constitute or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the PM, COR, and CO immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

BASIC OR APPLIED RESEARCH

This requirement includes basic or applied research that will result in new or original works, concepts or applications.

INTELLECTUAL PROPERTY

Data Rights

All intellectual property (hardware, firmware, or software) developed as part or result of this contract shall be the property of the Government. Similarly, all data rights from products developed as part or result of this contract shall be the property of the Government.

Nondisclosure Agreement (NDA)

The Contractor shall agree to and sign NDA to protect sensitive information, procurement data contract information, plans, and strategies, etc. as required.

GOVERNMENT PROGRAM MANAGEMENT

The PM, COR, and/or CO will provide the Contractor access to all technical data required to perform tasks. Only the COR and/or CO, in coordination with application managers, has authority to review and approve contract deliverables.

The overall Program Management responsibilities for this contract reside with the following office:

AFSC/LZDB

5215 Thurlow Drive Building 70C

WPAFB, OH 45433-5750

GOVERNMENT CONTRACT MANAGEMENT

Responsibility for contracting activities rests solely with the CO. No conversation, recommendations, or direction, whether given directly by, or implied by Government personnel shall be acted upon by the Contractor unless specifically approved by the CO. The Contractor shall address all areas pertaining to contract scope, schedule, or price of the contract covered by this PWS exclusively with the CO.

RESOURCE MANAGEMENT

The Contractor shall have in place a human resource management program to ensure qualified candidates are identified, screened, placed, monitored, and trained/retained to fulfill service requirements. The Contractor shall accomplish all tasks by employing and utilizing qualified personnel with appropriate combinations of education, experience, knowledge, training, abilities, and skills. The Contractor shall maintain clear organizational authority and responsibility to effectively manage contractor personnel without the engagement of Government employees in the Contractor’s operational or human resource management processes.

The Contractor shall establish and provide all reasonable means to ensure performance of this contract is fully complementary with, and does not run counter to, any written local operating procedures or policies. This is consistent with the Contractor’s exclusive right and authority to supervise and control its employees.

CONTRACTOR KEY PERSONNEL

In the event of a key personnel change (i.e. contractor employees located on a Government site), the Contractor shall immediately provide notification to the CO and COR.

CHECKLISTS

The Contractor shall complete any and all in-processing, in-house transfer, and out-processing base or organizational checklists upon employee hire, moves, and/or termination and notify the COR of any staffing changes. Prior to any contractor personnel’s leaving the program, computers and CACs will be returned to government personnel.

GOVERNMENT PROVIDED SERVICE PLAN

When work is to be performed at the Government’s location, the Government will prioritize service requirements based on operating requirements. The Government will provide the Contractor’s technical lead a generalized projected service plan which may be reviewed and revised by the Government PM as necessary. The purpose of the plan is to prioritize Government service requirements and provide the Contractor with the information required to effectively manage their personnel.

The Contractor shall provide total task management and supervise contractor personnel. The Contractor’s technical lead shall serve as the primary point of contact for all technical aspects of the required work. This lead shall also be a prime provider of the required technical services. No personal services shall be performed.

RECORDS, FILES, AND DOCUMENTS

All official records (regardless of media) as defined in 44 U.S.C. Part 3301 / AFI 33-322, Records Management Program and Information Governance Program, and are the property of the U.S. Government and shall remain so beyond termination or completion of this contract.

TRAVEL REQUIREMENTS

The Contractor may be required to travel on an as need basis to support the objectives of this PWS. Estimated annual travel requirements may include four (4) trips, each five (5) days in duration to WPAFB, or other ALC locations or AMARG. The Contractor shall obtain approval from the PM and/or COR 14 days in advance before traveling unless otherwise directed. The contractor shall inform the government when travel funds are less than 20% of the period total. Request for approval shall include the following:

· Date and Location of Travel

· Event (Purpose of Travel) and anticipated itinerary

· Number of Travelers

· Name and Title (Labor Category) of Travelers

· Goals and Desired Outcomes of Trip

· Why Alternate Methods are not Viable Options (i.e. Video Teleconference (VTC), Telecom, etc. are not options to accomplish purpose and goals)

· Total Estimated Cost of Trip The contractor shall be responsible for making all necessary travel, car rental, lodging arrangements, and subsistence requirements. Contractor shall use FAR 31.205-46 and the DoD Joint Travel Regulation (JTR) as a guide regarding air fares, per diem, allowances and reimbursement of travel expenses. Travel is restricted to round trip coach airfare tickets, economy class car rental, and per diem rates not-to-exceed Federal Travel Regulation (FTR) rates for the Temporary Duty (TDY) location. Airfare for travel and per diem shall be billed IAW FAR 31.205-46.

Trip Reports will be included in the appropriate Monthly Status Report (CDRL A002)

APPENDICES

APPENDIX A – ACRONYMS

APPENDIX B – SUBSUMPTION AND INTERFACING SYSTEMS

Systems to be subsumed:

Notes: DSD = Data System Designator. System used across full Center (AFSC) unless annotated. The list is subject to change:

1. ABOM: Automated Bill of Material (Part of DMAPS)

1. ABS: AMARG Business System – AMARG only

1. ALSDS (DSD E046B): AFMC Labor Standards Data System (Part of DMSI)

1. AMREP (DSD A030D): Aircraft Maintenance Production/Compression Report System

1. APOFS (DSD J025): APOFS – Automated Project Order Form System

1. DIFMS: Defense Industrial Financial Management System (Part of DMAPS)

1. DMAPS IE: DMAPS Integration Engine (Part of DMAPS)

6. FITS: Funding Initiation Tool System

6. RSCS: RCC/Skill Code System

6. JOST: Job Order Status Tool

6. SPGS: Sales Price Generator System

6. CONEN: Conversion Engine

6. DDS: DMAPS Data Store

6. CPBM (DSD H033): Cost Production and Budget Module

1. DMMSS (DSD G005M): Depot Maintenance Materiel Support System (Part of DMSI)

1. DMWPCS (DSD G004C): Depot Maintenance Workload Planning and Control System

1. EMIS: Enterprise Management Information System - at Robins AFB

1. EPS (DSD G402A): Exchangeable Production System (Part of DMSI)

1. ITS (DSD G337): Inventory Tracking System (Part of DMSI)

1. JOPMS (DSD G004L): Job Order Production number Master System (Part of DMSI)

1. KPM: Kadenza Propulsion Management, only at OC-ALC/PMXG

1. LDMS: Lean Depot Management System (partial subsumption) - WR-ALC and OC-ALC/CMXG

1. MABSM (aka Impresa): Maintenance and Business System Modernization - in CMXG/EMXG/MMXG/AMXG at OO-ALC

1. NIMMS: NAVAIR Industrial Material Management System (Part of DMAPS)

1. PDMSS (DSD G097): Programmed Depot Maintenance Scheduling System (Part of DMSI)

1. TAAS (aka TAA): Time and Attendance System (Part of DMAPS)

APPENDIX B (CONT)

Potential Interfacing systems

Notes: Some systems may require transitional interfaces before full subsumption occurs. The list is subject to change:

1. AXOL - Access On-Line – US Bank Cardholders

2. CCaR - Comprehensive Cost and Requirement System

3. CEFT - Centralized Electronic Funds Transfer

4. CEMS (DSD D042) - Comprehensive Engine Management Systems

5. CON-IT - Contracting Information Technology

6. Concur

7. CPBM (DSD H033) - Cost Performance and Budget Module

8. CSWS DE (DSD D375) - Contractor Supported Weapon Systems Data Exchange

9. DAAS - Defense Automated Address System

10. DCPDS (DoD) - Defense Civilian Personnel Data System

11. DCPS (DoD) - Defense Civilian Payroll System

12. DDRS - Defense Departmental Reporting System

13. DDS - DMAPS Data Store

14. DEAMS (AFMC FM) - Defense Enterprise Accounting and Management System

15. DPAS (DoD) - Defense Property Accountability System

16. DRILS (DSD G200) - Defense Repair Information Logistics System

17. DTIM - DFAS Transaction Interface Module

18. EXPRESS (AFSC) (DSD D087X) - Execution and Prioritization of Repairs Support System

19. FEM (DSD D130) - Facilities and Equipment Maintenance

20. FIABS (DSD D035J) - Financial Inventory Accounting and Billing System

21. G-Invoicing (US Treasury)

22. ILS-S (DSD D200A) - Integrated Logistics System - Supply

23. iRAPT - Invoicing, Receipt, Acceptance and Property Transfer

24. MIICS (DSD D043) Master Item Identification Control System

25. mLINQs - move Government Relocation Accounting Software

26. MOCAS - Mechanization of Contract Administration Services

27. MPS (DSD D230) - Material Processing System

28. MyInvoice

29. PLM (AFLCMC) – Product Lifecycle Management

30. REMIS (DSD G099) Reliability and Maintainability Information System

31. SAM System for Award Management

32. SAMIS (FMS) (DSD W001) - Security Assistance Management Information System (via WebRoR)

33. Syncada (US Bank)

34. TDO - Treasury Disbursing Office (US Treasury)

35. WARRS (DSD D035K) - Wholesale And Retail Receiving and Shipping

36. WMS - Warehouse Management System image1.jpeg image2.jpg image3.jpg