PWS for MABSM Expansion WR and OC AMXGs 20241011.pdf

PERFORMANCE-BASED WORK STATEMENT (PWS)

MAINTENANCE BUSINESS SYSTEM MODERNIZATION (MABSM)

IMPLEMENTATION & SUSTAINMENT FOR THE WR-ALC & OC-ALC

AIRCRAFT MAINTENANCE GROUPS (AMXG)

U.S. AIR FORCE

OO-ALC

Alexsys Record 12460

Updated 10/14/2024

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

MAINTENANCE BUSINESS SYSTEM MODERNIZATION (MABSM) IMPLEMENTATION &

SUSTAINMENT FOR THE WR-ALC & OC-ALC AIRCRAFT MAINTENANCE GROUPS (AMXG)

i

TABLE OF CONTENTS

1 DESCRIPTION OF SERVICES

2 BASIC SERVICES

2.1 IMPLEMENTATION

2.2 CUSTOMIZATION AND CONFIGURATION CONTROL

2.3 SUSTAINMENT

2.4 TRAINING

2.5 USER GUIDES

2.6 SPECIAL PROJECTS

2.7 OFF-RAMP

2.8 ADDITIONAL REQUIREMENTS (as required)

3 SERVICE SUMMARY

4 CDRL SUMMARY

5 GOVERNMENT FURNISHED PROPERTY (GFP) AND FACILITIES

6 GENERAL INFORMATION

6.1 INSTALLATION-SPECIFIC SAFETY AND HEALTH STANDARDS

6.2 TRAINING

6.3 SECURITY REQUIREMENTS

6.4 CONFLICTS OF INTEREST

6.5 QUALITY CONTROL PLAN

6.6 HOURS OF OPERATION

6.7 TRAVEL REQUIREMENTS

6.8 CONTINUATION OF ESSENTIAL DOD CONTRACTOR SERVICES DURING

CRISIS

6.9 REPORTING OF CONTRACT LABOR HOUR / MANPOWER REPORTING

6.10 CONSERVATION OF UTILITIES

6.11 FOREIGN OBJECT DAMAGE (FOD) AND TOOL CONTROL

6.12 INTELLECTUAL PROPERTY

6.13 INHERENTLY GOVERNMENTAL FUNCTIONS/PERSONAL SERVICES

6.14 GOVERNMENT PROGRAM MANAGEMENT

6.15 GOVERNMENT CONTRACT MANAGEMENT

6.16 RECORDS, FILES, AND DOCUMENTS

6.17 PHASE OUT PERIOD

6.18 APPENDICES

ii

APPENDIX A – ACRONYMS

APPENDIX B – TRAVEL

APPENDIX C – SAFETY

APPENDIX D – CONTRACTOR PROVIDED TRAINING

1 DESCRIPTION OF SERVICES

The purpose of this PWS is to implement and sustain the Maintenance Business System Modernization (MABSM), system of record name for the Ogden Air Logistics Center (OO- ALC) Maintenance Repair Overhaul (MRO) utilizing customized Impresa software, for the Aircraft Maintenance Groups (AMXGs) located at Oklahoma City Air Logistics Center (OC- ALC) and Warner Robbins Air Logistics Center (WR-ALC).

MABSM’s financial and timekeeping modules in the Government owned Impresa software may be implemented as identified as required at each ALC (see para 2.6 Special Projects).

The contractor shall provide on-site project management, analytical, implementation, technical services, training, and sustainment. The contractors shall provide skilled labor in support of business management oversight, data configuration management, process standardization, implementation services, and user/configuration functional training services specific to the MABSM application. The contractor shall plan, manage, organize, direct, schedule and control all resources, processes, activities, and tasks to accomplish the requirements of this PWS through specific task orders provided by the Government in a PWS or SOO.

2 BASIC SERVICES

The contractor shall implement, customize, configure, train, and sustain MABSM for the Aircraft Maintenance Groups (AMXGs) at Warner Robins Air Logistics Center (WR-ALC) and Oklahoma City Air Logistics Center (OC-ALC).

2.1 IMPLEMENTATION

2.1.1 The contractor shall implement MABSM into AMXGs as defined in the MABSM Integrated Master Schedule (IMS). Task Orders will be issued in accordance with (IAW) the IMS. Implementation will include but not be limited to the following:

2.1.1.1 Site Survey. Contractor shall evaluate and map existing processes to include any new interfaces with Air Force Legacy systems that are to be incorporated into MABSM.

2.1.1.2 Execute Implementation IAW Integrated Master Plan (IMS).

2.1.1.2.1 Details to be further defined at task order level.

2.2 CUSTOMIZATION AND CONFIGURATION CONTROL

2.2.1 ID Unique Attributes

2.2.1.1 Contractor shall manage MABSM to audit all NWRM serially controlled items and related attributes against the official published NWRM list. When official NWRM master listings are updated and distributed (at a minimum semiannually), the contractor shall update MABSM within 24-hours, to maintain item attribute and data accuracy (e.g. part number, National Stock Number (NSN), and descriptions).

When notified of required changes, the contractor shall complete updates to MABSM and report completion to the Government PM.

(CDRL A003)

2.2.1.1.1 The contractor shall collect Maintenance Data for repaired serialized/NWRM assets and upload to Reliability and Maintainability Information System (REMIS), IAW Technical Order (T.O.) 00-20-2, and as further defined at task order level.

2.2.1.1.2 The contractor shall work with Planners as they maintain BOM accuracy relative to NWRM and serialized items to include maintaining the integrity of parent-child relationship and assigning Standard Reporting Designators (SRD) and Work Unit Codes (WUC).

2.2.1.1.3 The contractor shall report deviations (errors) for both serialized items and NWRM items to government personnel when inconsistencies exist between Technical Data or official NWRM lists and Legacy systems (e.g. D043). Deviations must be reported to the Nuclear Weapon Related Material Accountable Officer (NWRMAO) upon finding and then reported in the monthly status report. (CDRL A001)

2.2.1.2 Org Builds

2.2.1.2.1 Architecture and Application Design

2.2.1.2.2 The contractor shall support the design and development of MABSM and MABSM integration into the overarching enterprise architecture. The contractor shall provide all required design and development documents, and supporting architectural documentation, for any frameworks

2.2.1.2.3 The contractor shall provide MABSM historical data, application functionality and usage, OO-ALC depot-level execution, and other relevant application aspects as required to support Maintenance, Repair, Overhaul initiative (MROi) build.

2.2.1.3 Unit Specific Modifications

2.2.1.3.1 Must be updated in user guides. (CDRL A011)

2.2.1.4 Test and Validation/Verification (VAL/VER)

2.2.1.4.1 Application Functionality testing and vulnerability migration.

2.2.1.4.2 The contractor shall perform application functionality user acceptance testing to verify software and external interface functionality. The contractor shall ensure customer verification, validation and approval of any system changes prior to any changes being implemented into the production environment.

Vulnerabilities identified during code security scans shall be mitigated IAW 75 ABW/SC processes and security policies prior to deployment.

2.2.1.4.3 A Software Version Description (SVD) document shall accompany each formal release to identify all changes that are incorporated into the release. (CDRL A006)

2.2.1.5 Production Configuration Management – Data Records and Configuration Lifecycle Management

2.2.1.5.1 The contractor shall provide data records management and configuration management. The contractor shall review, audit, validate, amend, and perform corrections to application data input in MABSM daily. The contractor shall identify inconsistencies and provide a recommendation for corrective actions.

2.2.1.5.2 The contractor shall manage the document control process that includes research, document development, test, release and archive using industry standards for records management. This will be included in the technical reports / white paper reports as required. (CDRL A003)

2.2.1.5.3 The contractor shall manage the lifecycle process for application and process development, improvements, upgrades, implementations, refreshes, sustainment and maintain certification Capability Maturity Model Integration (CMMI) Level II.

2.2.1.5.4 The contractor shall maintain Master Project plans for each group with detailed project tasks and work breakdown structures using industry standard project management techniques. The Master plan shall be coordinated with Group contractor PM to meet individual Group goals and milestones for implementation and sustainment. (CDRL A002)

2.2.1.5.5 The contractor shall maintain accurate lifecycle status for all tasks and projects. The contractor shall assign resources to project tasks and conduct regular progress meetings to ensure accurate project and lifecycle information, as well as identify tasks requiring escalation or reassessment.

2.2.1.5.6 The contractor shall create and sustain optimal structure and content for items, bills of material, shop routings, and other data critical to Material Requirements Planning (MRP) processing and material supportability.

2.3 SUSTAINMENT

2.3.1 Maintain 95% Up-Time

2.3.2 Interface Management

2.3.2.1 The contractor shall provide technical and/or specialized guidance in the operation and application of the MABSM software interfacing with other systems, both automated and manual.

2.3.3 New User Adds

2.3.3.1 The contractor shall add, delete, and modify user account information;

reset passwords; answer technical queries/reports; be responsible for documenting the system configuration; sustain application, troubleshoot, and resolve any reported problems; provide application performance tuning; provide functional assistance; and provide any reporting or query requirements summaries in the Monthly Status Report. (CDRL A001)

2.3.4 Database Management

2.3.4.1 Engineering Change Requests (ECRs)

2.3.4.1.1 The contractor shall coordinate with maintenance personnel to implement change requests, known as Engineering Change Requests (ECRs) in the MABSM Application. These ECRs may include, but are not limited to, working with the appropriate party to correct or amend errors in existing documents or data. The contractor shall ensure all ECRs are resolved, upon receipt of notification, based on the timelines outlined in Table 1 unless another time frame is mutually agreed upon by the Government and contractor. The contractor shall provide a monthly report of ECRs to include ECR activity/status to the COR. (CDRL A001)

2.3.4.1.2 The contractor shall provide direct support to Government personnel for minor changes and workarounds not requiring ECRs.

Table 1

NWRM Not To Exceed (NTE) 3 hours Work Stoppage NTE 8 business hours Urgent NTE 12 business hours Standard NTE 27 business hours

2.3.4.2 Request for Change (RFC) Receipt /Routing to CCB/Steering Committee

2.3.4.2.1 The Government or contractor shall identify potential application design changes, enhancements or upgrades for the MABSM application. This applies to both hardware and software. The contractor shall properly annotate and compile all RFCs to the MABSM application and obtain approval through the CCB. The CCB consists of Government personnel from various functional areas, including a CCB Chairperson who is the approval authority for any configuration changes to the application. 75 ABW/SC and/or Air Force approval are required before implementation of the changes. Upon Government request, the contractor shall participate in the CCB process as a technical advisor and shall attend CCB meetings. The contractor shall ensure that no RFCs are implemented without the approval of the CCB.

2.3.4.2.2 The contractor shall compile and analyze data, provide options to validate concept reviews and improvements to the CCB that facilitate life cycle management of the MABSM software. The coordination and concurrence of the CCB shall be required before the contractor begins design changes, enhancements, or upgrades. Any design change, enhancement, or upgrade shall be compatible with other systems and components. The contractor shall verify functionality of any potential design change, enhancement, or upgrade through testing. The contractor shall also perform in-depth security testing of any potential design change, enhancement, or upgrade, and report any findings to the Government PM. The contractor shall ensure that the function, supportability, and performance of the MABSM application are not degraded by any approved changes. Approved application design change enhancements or upgrades to the MABSM application shall be updated in the applicable user guides within 30 calendar days of implementation. (CDRL A011 & A012)

2.3.4.2.2.1 The contractor shall be required to assist the

Government in providing information for the Control System Requirements Document (CSRD) process through the Information Systems Management Tool

(ISMT).

2.3.5 Security Patching

2.3.5.1 Notify the Host (HEDC/Cloud/Oracle) and Functional Management Office (FMO)

2.3.5.2 Contractor shall code per FMO approval/direction

2.3.5.3 Contractor will ensure information systems are made available to the government for continuous updates with the latest software and security patches to minimize security vulnerabilities. Information systems, desktops, and supported peripherals shall be certified and accredited to comply with the DoD system security policies before they can be added to the network IAW DoDI 8510.01; RMF for DoD IT Services.

2.3.5.3.1 The contractor shall protect system information and resources according to established security policies and procedures and ensure application code is updated with the latest security patches to minimize security vulnerabilities.

2.3.5.3.2 SECTION 7 General, lists a lot of information that should be broken into the appropriate areas for Security, patching, 75 Coord/approvals, etc.

2.3.6 Supporting Software Updates

2.3.6.1 The contractor shall perform software updates with zero impact to Government workload unless approved by the Government program manager.

2.4 TRAINING

2.4.1 Application Training

2.4.1.1 The contractor shall provide training for all levels of MABSM users.

The contractor shall provide formal classroom training, On the Job Training (OJT), monthly user training, and create and update user guides. The contractor shall possess an in-depth understanding of MABSM and how it interfaces with other systems. The contractor shall assign course numbers in order to standardize training and provide training oversight and tracking. The contractor shall document each training session conducted; reporting attendees, time, date, changes made, and overview of what was trained, and provide a comprehensive training plan for group training requirements for each year in the Monthly Status Report. As required, the contractor shall provide any required documentation to the appropriate Production Acceptance Certification Standard System (PAC)/Training Schedule System (TSS) representative for tracking of training completion. (CDRL A001, A004, & A011)

2.4.2 Formal Classroom Training

2.4.2.1 The contractor shall provide formal classroom training to designated personnel using Government facilities. The minimum required training for new users shall be covered as outlined in the topics listed in Appendix E. All training shall contain the “how to” performance functions in area such as queries, reports, asset visibility, job routing procedures, application reporting, scheduling and planning procedures, material ordering and how the integration between MRO and Impresa are inter-linked. Course material shall be made available to government training agencies to correlate with existing government courses (i.e., gates, WCD courses, planning/scheduling courses, etc.). (CDRL A004)

2.4.3 On the Job Training

2.4.3.1 The contractor shall provide one-on-one and small group training to cover specific issues as requested by MABSM users. (CDRL A001)

2.5 USER GUIDES

2.5.1 The contractor shall develop and implement a system for creating or expanding upon existing user guides. The contractor shall include an overview, interim summary and conclusion to each topic presented in a user guide. User guides shall include, but are not limited to, documented User Guides and any of the reports within MRO Applications. User Guides shall be written from an understanding of the basic user to that of an expert.

2.5.2 The contractor shall ensure that the user guides provide detailed, step by step, comprehensive instructions and explanations of all MABSM functions. User guides shall explain how the MABSM data input affects legacy systems and all areas within MABSM.

2.5.3 The existing user guides shall be audited within the MRO Applications Reporting system. When a new application is created, a user guide shall be provided to the Government within sixty (60) calendar days of application creation. When a RFC is completed, the existing user guide shall be updated within thirty (30) calendar days of implementation. The contractor shall create and update the master user guide list to be included in the monthly status report. (CDRL A001 & A011)

2.5.3.1 A master user guide list shall be updated and provided in the monthly status report. (A001 & A011)

2.6 SPECIAL PROJECTS

2.6.1 Application Enhancements

2.6.2 Interface Management

2.6.2.1 The contractor shall be responsible for the Impresa or other chosen COTS MRO processes and must be intimately familiar with the inner workings of the MABSM software. The contractor shall use Air Force Legacy IT systems knowledge to establish and maintain many interfaces between the COTS MRO solution and the Legacy system environment.

The contractor is responsible to provide management reports integrating the data from Legacy systems. The contractor shall be responsible to provide automated queries and processes to support the induction and sales process to eliminate duplication between the MRO solution and the Legacy environment. This includes the required updates and maintenance to support the interface with Exchangeable Production Support (EPS) (G402A and Inventory Tracking System (ITS). The contractor shall incorporate new concepts in manufacturing and repair/overhaul supporting Lean/Continuous Process Improvement principles.

2.6.3 Art of the Possible (AoP) Management Required Changes

2.6.4 Wireless Implementation

2.7 OFF-RAMP

2.7.1 Hand off to the Government

2.8 ADDITIONAL REQUIREMENTS (as required)

Any additional requirements necessary to complete the activities identified in this PWS will be executed at the task order level utilizing this section reference.

3 SERVICE SUMMARY

SS

Performance

Objective

PWS

Paragraph

Performance Threshold

#1

Contractor shall maintain Master Project plans for each group with detailed project tasks and work breakdown structures using industry standard project management techniques. The Master plan shall be coordinated with Group contractor PM to meet individual Group goals and milestones for implementation and sustainment.

2.2.1.5.4

Contractor shall deliver Master Project Plan and revised plans within 15 business days. Acceptable quality level is 100%. (CDRL A002)

#2 The contractor shall provide a monthly report of ECRs to include ECR activity/status to the COR.

2.3.4.1.1.

Contractor shall deliver the ECR report by the 5th business day of each month. No more than one late delivery in a 12 month period. (CDRL A001)

#3 The contractor shall provide support for minor changes and workarounds not requiring ECRs according to Table 1.

2.3.4.1.2 & Table 1

Contractor shall maintain a 95% compliance rate with timeframes specified in Table 1 with the exception of NWRM which shall maintain a 100% compliance rate.

(CDRL A001)

#4 When official NWRM master listings are updated and distributed the contractor shall update MABSM within 24 hours.

2.2.1.1, 2.4.2.1 NWRM items shall be updated within 24 hours with a 100% compliance rate. (CDRL A003)

#5

The contractor shall document each formal training session conducted reporting attendees, time, date, and overview of what was trained, IAW the approved Training Plan and provide the status in the Monthly Status Report.

2.4.1.1

Contractor shall deliver this report on or before the 5th business day of each month. No more than one late delivery in a 12 month period. (CDRL A001)

#6

Provide user guides within the MRO Application Reporting system. Create and update the master user guide list to be included in a monthly status report.

2.4.1.1, 2.5.3

Contractor shall provide a new user guide within 60 calendar days of a newly created application and 30 days for an update to a current application.

(CDRL A001) (CDRL A011)

#7

The contractor shall provide a comprehensive Training Plan that at a minimum will cover required training for new users as outlined in the topics listed in Appendix D

2.4.1.1

The contractor shall deliver the Training Plan not later than 15 days after notification of contract award.

(CDRL A004)

4 CDRL SUMMARY

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 4- 1 (below). The contractor shall have no more than one (1) error per quarter for all CDRL submittals. The contractor shall submit CDRLs according to the due date indicated and have no more than one (1) CDRL per quarter submitted after the identified due date. Grammatical errors do not count as an error. Substantive mistakes shall be corrected within two (2) working days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Reporting: All reporting requirements listed below are applicable, unless omitted at the TO level and shall include current site-specific information.

Table 4-1

Exhibit Title PWS Paragraph

Delivery

A001 Status Report 2.2.1.1.3, 2.3.3.1, 2.3.4.1.2.

2.4.1.1, 2.4.3.1, 2.5.3, 2.5.3.1, 6.7.1.2

As Required

A002 Master Project Plan 2.2.1.5.4 As required

A003 Technical Report/White Paper 2.2.1.1, 2.2.1.5.2 As required

A004 Training Plan 2.4.1.1, 2.4.2.1 15 days after notification of contract award

A005 TCIR/DART 6.1.1.3 Annually

A006 Software Version Description (SVD) 2.2.1.4.3 As Required

A007 Contract Labor Hours 6.9.2 no later than 31 October of each calendar year

A008 Accident/Mishap Report 6.1.2.1, 6.3.6.1.2 As required

A010 Quality Control Plan 6.3.5.2.1, 6.5.1 10 days after notification of contract award

A011 User Guide(s) 2.2.1.3.1, 2.3.4.1.1, 2.3.4.2.2, 2.5.3, 2.5.3.1 As Required

A012 MABSM Application Sustainment 2.3.4.2.2 As Required

5 GOVERNMENT FURNISHED PROPERTY (GFP) AND FACILITIES

5.1.1 The Government will provide workspace, working supplies, furniture, and access to business telephones. Government provided desktop 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.

5.1.2 All property provided by the Government, including applications, and any property acquired by the contractor under this contract remains the property of the Government and shall be returned to the Government upon completion of the requirement unless alternate disposition instruction is provided. The contractor shall protect Government property to prevent damage during the period the property is in the possession of the contractor. All Government property shall be returned to the Government in working condition (serviceable). The contractor shall report within 2 business days to the Contracting Officer (CO) and COR all available facts relating to each instance of damage to Government property.

5.1.3 Safeguarding

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

5.1.4 Virtual Private Network

5.1.4.1 The contractor shall not use contractor-owned equipment for Virtual Private Network (VPN) access. In accordance with AFI 17-100, only Government owned equipment may be used to access VPN. The contractor shall submit requests for VPN access in writing to the 75 ABW/SC Functional Director. The request shall include justification and specific personnel that require access. If approved, the Government will provide sufficient equipment for the contractor to use. The equipment will remain Government property and reside on the contractor’s Automated Data Processing Equipment (ADPE) account for the duration of the approved period.

5.1.5 Contractor Representation and Presentation

5.1.5.1 When using Government furnished communication devices or processes (e.g., the Voice Over IP (VOIP) network, telephones, e-mail, etc.) the contractor and its employees shall take all reasonable precautions to ensure that the persons or entities with whom the contractor or its employees are communicating are placed on notice that they (the persons or entities with whom the contractor or its employees are communicating) are communicating with a contractor, not the Government. These precautions are necessary to preserve the arms-length relationship which must always exist between the Government and the contractor, and to eliminate or minimize the risk that persons or entities with whom the contractor is communicating will mistakenly believe they are communicating with the Government and inadvertently disclose information that the contractor is not authorized to receive.

Such precautions shall include, at a minimum:

5.1.5.1.1 An express verbal statement by the contractor and its employees at the beginning of each telephonic or VOIP or similar audio communication that clearly informs the other party they are communicating with the contractor or one of its employees, and

5.1.5.1.2 A conspicuous written notice including contact information on all email and other written communications sent by the contractor and its employees that clearly and immediately informs the other party that the sender is a contractor and/or contractor employee.

6 GENERAL INFORMATION

6.1 INSTALLATION-SPECIFIC SAFETY AND HEALTH STANDARDS

6.1.1 Volunteer Protection Program (VPP)

6.1.1.1 Hill AFB, along with the entire Air Force, has adopted the VPP as recognized by Occupation Safety Health Association (OSHA).

Consequently, VPP impacts all “applicable contractors” operating on Air Force Installations. It is the contractor’s responsibility to ensure its employees and managers 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 such as construction or repair, must follow the safety and health rules of the installation or VPP site.

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

6.1.1.3 Contractors are required to provide from their OSHA 300 information the Total Case Incident Rate/Days Away Restricted or Transferred (TCIR/DART) rates and submit them to the CO as part of the installation’s annual OSHA VPP self-evaluation report. (CDRL A005) http://www.osha.gov/dcsp/vpp/index.html

6.1.2 Safety Program

6.1.2.1 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 three calendar days to the Government Representative, who will forward it to OO-ALC/SEG safety office. (CDRL A008)

6.2 TRAINING

6.2.1 Site Specific / Regulatory Requirement Mandated Training

6.2.1.1 The contractor shall attend various site-specific systems program training courses provided by the Government as needed. If a new requirement for training has been mandated universally by the government post award, courses may be provided by the Government as required to contractors as soon as it is reasonable.

6.2.1.2 Contractor employees shall attend Government-furnished Contractor New Hire training. This initial contractor new hire course will not consist of all training requirements specific to individual work areas, yet this requirement will provide a solid foundation for the employee to be immediately successful in completing his/her position requirements.

POP start dates will be aligned with Contractor New Hire training dates, which are typically twice a month.

6.2.1.3 The contractor shall ensure that contract employees attend the required mandatory training courses provided by the Government. The Government will provide adequate notice prior to training. The contractor shall provide a training roster of all contractor employees trained, the type of training (Government provided or contractor-provided), date trained, and what course(s) they were trained on within fifteen (15) days after training occurs. (CDRL A00X)

TABLE 7.2

Below illustrates a sample of the Contractor Required Training (CRT). Additional or specific training requirements will be further detailed in the individual TO.

COURSE NAME (EXAMPLE

LIST)

(Provided by Government except where noted)

Government Provided

Contractor Provided NOTES

Initial Fire Safety and Prevention Training X Contractor New Hire Training

Foreign Object Damage (FOD) and Dropped Object (DO) Awareness X Contractor New Hire Training

Environmental, Safety and Occupational Health X Contractor New Hire Training

Required “Block” Training X Varies by Group and position

Security Overview for New Hires X

Computer Security X

Voluntary Production Plan (VPP) X

Security Training X

Privacy Act Training X

DoD Information Assurance Cyber Awareness Challenge X All contractor personnel requiring computer access

Information Protection X

Hazardous Chemical, Handling & Storage of (Initial/Recurring) X

Force Protection X

Operations Security (OPSEC) Awareness

X

Initial Tool Control and Equipment Management/Accountability X

AFTO Form 244 Training X

Work Control Documentation for Maintenance Personnel X

AS9100 X

Production Acceptance Certification (PAC) Program X

Controlled and Restricted Area Training X

All contractor Personnel Requiring Access to Controlled Areas

AMARG Emergency Procedures X All AMARG contractor Personnel

Explosive Safety X For those who handle, use, or are potentially exposed to explosive materials

Controlled Unclassified Information

(CUI) X

Hazard Training (HAZCOM) X For employees who handle, use, or are potentially exposed to hazardous materials

Lockout/Tagout Program X

Confined Space X

6.3 SECURITY REQUIREMENTS

The contractor shall comply with all Security, Force Protection, and Antiterrorism requirements enforced at each installation. The contractor shall comply with local unit in and out-processing procedures for all contractor personnel to ensure proper security-related briefings and debriefings are accomplished.

6.3.1 BASE ACCESS

6.3.1.1 The efforts required for this contract are expected to be UNCLASSIFIED and should not require the contract personnel to obtain a security clearance.

6.3.1.1.1 CLASSIFIED security may be required to execute this PWS at WR-ALC/AMXG or OC/AMXG. Any clearance requirements above UNCLASSIFIED shall be identified at the task order level.

6.3.1.2 The contractor shall be required to obtain security clearances for all employees. In addition, the contractor shall be required to obtain a facility clearance of SECRET. A DD Form 254 will be required for contract.

6.3.1.3 The contractor shall complete a “Request for Identification Credential (Hill AFB Form 496)” and Optional Form 36, for each employee requiring access to Hill AFB. The requests shall be submitted to the COR or GR for signature then to OO-ALC/OMD Security for processing. The Hill AFB Form 496 can be used to obtain a Base and Government computer Common Access Card (CAC), Defense

Biometric Identification System (DBIDs) Access ID, and/or 1199 Flight-Line Badge

6.3.1.4 The contractor shall obtain a Building ID and access card from the appropriate Building Security Manager for all their employees.

6.3.1.5 All contractors needing a CAC must visit the ADLS website and create an account to complete their initial Cyber Awareness Challenge training. This training completion date is requiring on the AF Form 2875 which is submitted to create a government computer profile and email account. contractors with Government computer access are required to complete all training by completing computer-based training (CBTs) using Hill AFB’s TSS and ADLS training websites. Contractors with DBIDS base access IDs will review all training power-point slide shows and sign a training roster annually.

6.3.2 CONTROLLED AREA BADGE (CAB) PROCESS

6.3.2.1 Controlled area badge (CAB) requests shall be completed by the group SM, who shall complete an AF Form 2586, Unescorted Entry Authorization Certificate, for each employee requiring entry into controlled/restricted areas. The contractor employee shall carry the AF Form 2586 to Security Forces (building 430). The AF Form 2586 will be returned to the issuing SM for accountability.

6.3.2.2 Employees without a current DBIDS, or denied access to the installation, will not be issued a CAB until all issues are resolved. The contractor shall provide, through the COR, written justification with employee full name, Height, Weight, Eye Color, Hair Color, contract number with expiration date and areas needing access to the issuing SM to initiate a request for a badge.

6.3.2.3 CABs will not be issued for the convenience of having to be escorted.

6.3.2.3.1 While in the Controlled Areas, contractor employees shall display the CAB in a badge holder, furnished by the contractor company, between the shoulders and above the waist and in the front of the body whenever inside an identified controlled area.

6.3.2.3.2 When outside controlled areas, the CAB will be placed out of sight.

6.3.2.3.3 Security Education and Motivation training shall be completed, initially and annually thereafter to obtain, and maintain, a CAB. Employees who fail to meet training requirements will have their credentials removed and installation access revoked.

6.3.2.3.4 Training can be expected to last one and one half to two hours long, initially, and annually. Training is scheduled with the Group SM and requires a passing score to receive approval for a CAB.

6.3.3 DISABLING ACCOUNTS

6.3.3.1 The contractor shall report personnel who no longer need network or Automated Information System (AIS) access to the appropriate Security Manager (SA) and Functional System Administrator (FSA) within two

(2) calendar days of completion of contractor access requirement.

6.3.4 CHECKLISTS

6.3.4.1 The contractor shall complete 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.

6.3.5 PHYSICAL SECURITY

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

6.3.5.2 Lock Combinations

6.3.5.2.1 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 A010)

6.3.6 Building ID and Vindicator Access Card

6.3.6.1 As required, the contractor employee shall also obtain a Building ID and/or vindicator access card from the appropriate Building Facility/SM. Access to controlled/restricted areas will not be granted without a CAB/RAB badge and proper authorization for required areas.

6.3.6.1 Lost Badges or Access Cards

6.3.6.1.1 Lost badges shall be reported to the Group Security Officer or Complex Security Manager within one working day of loss.

After receiving a Lost Identification Letter from the issuing security office, the contractor is required to fill out an AF Form 1168 through the Security Forces Squadron. The contractor must bring AF Form 2586 to the Security Forces Offices to be issued a new badge then return form to the Group Security Office.

6.3.6.1.2 The contractor shall create an Incident/Mishap report when a contract employee loses a CAC or Restricted/Controlled Area Badge Line badge. The Incident/Mishap report must be submitted no later than 1 business day. (CDRL A008)

6.3.7 Display of Identification

6.3.7.1 When contractor employees are inside a secure work area within Hill AFB, they shall wear visible Government-provided identification either as a part of or attached to their outer clothing. The identification shall clearly identify the individual as being a contractor employee.

6.3.8 Network Access

6.3.8.1 Contractor employees shall maintain completed and current Network User Licensing Computer Based Training (CBT) as required for compliance with all applicable initial and annual network-related access and security training. Contractor employees requiring a Government provided email account shall be subject to the same restrictions and conditions imposed upon Government employees. Contractor employees shall complete all required forms prior to receiving access to networks, Government email, and systems including, but not limited to, AF4394, Air Force User Agreement Statement-Notice and Consent Provision and DD2875, System Authorization Access Request (SAAR).

6.3.8.2 For those contractor employees who require Government computer access only, a National Agency Check with written Inquires (NACI) must be accomplished through the Government.

6.3.8.3 Contractor employees requiring a government-provided email account, shall complete initial and annual Information Assurance Awareness Training IAW AFI33-200, Information Assurance Management and Air Force Instruction (AFI) 33-152 User Responsibilities and Guidance Information System. Interim access may be granted by Designated Approving Authorities only after submission of the NACI and favorable fingerprint determination has been received by the applicable security manager.

6.3.9 Security Incidents

6.3.9.1 Should a security incident occur, the contractor shall:

6.3.9.1.1 Immediately report to the site location Group Security Manager all available facts related to each instance.

6.3.9.1.2 Take such precautions as the Security Manager may reasonably require for security purposes.

6.3.9.1.3 Take reasonable and prudent action to establish control of the scene, prevent further violation, and to preserve evidence until released by proper authority.

6.3.9.1.4 Cooperate fully and assist Government personnel as the Government investigates the violation.

6.3.9.1.5 Participation shall last until the investigation is complete.

6.3.10 Communications Security

6.3.10.1 All communications with DoD organizations are subject to Communications Security (COMSEC) review.

6.3.10.2 The DoD authorizes the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations.

6.3.10.3 The Government advises the Contractor that at any time they place a call to, or receive a call from, a DoD organization, they are subject to COMSEC procedures.

6.3.10.4 The Contractor assumes the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoD information.

6.3.11 Operations Security (OPSEC)

6.3.11.1 Contractors who have access to Ogden Air Logistics Complex (OO- ALC) facilities or critical information shall have OPSEC training IAW AFI 10-701, Operations Security (OPSEC), (Complete reference in Appendix E). Initial training will be provided by Group SM and lasts approximately one hour, with recurring annual training lasting approximately one-half hour. Contractors shall immediately comply with Installation and Group OPSEC programs.

6.3.11.2 Public release of any information is not authorized and, if requested, will comply with Public Affairs and all other OPSEC measures to ensure the best balance of lawful disclosure for the American public and denial of advantage for our adversaries.

6.3.11.3 No photography, or videotaping, is allowed on the installation without approval from the owning organizations Group Director/Commander on an approved photography letter from Public Affairs. This includes the use of personal cell phones with picture and video capability.

6.3.11.4 Critical Items/Information shall not be discussed outside normal contract conditions. A Critical Items/ Information List (CIL) can be provided and should not be considered all inclusive.

6.3.12 Controlled Unclassified Information (CUI) generated by the contract, and its employees, shall ensure protective measures are applied. ALL DoD unclassified information MUST BE REVIEWED AND APPROVED FOR RELEASE before it’s provided to the public in accordance with DoDD 5230.09, Reference J.

6.3.12.1 Disclosure of information is prohibited for release of unclassified information to the public without approval of the contracting activity.

6.3.12.2 Contractors will comply with CUI requirements detailed in DoDM 5200.01-V4, DoD Information Security Program: Controlled Unclassified Information (CUI).

6.3.13 Security Training

6.3.13.1 Contractor employees who have access to Hill Air Force Base, government facilities or critical information shall be trained on Operations Security (OPSEC), human relations, and security education and motivation within 90 days after initial assignment of the contract IAW AFI 10-701 Para. 4.1-4.2.

6.3.13.2 The contractor shall complete the following initial security training and retraining annually:

6.3.13.2.1 Operations security (OPSEC) (everyone)

6.3.13.2.2 Antiterrorism and Force Protection (AT/FP) Level 1 (everyone)

6.3.13.2.3 Security Education and Motivation Phase 1 & 2 (for line-badges only)

6.3.13.2.4 Energy Management Program Awareness Training (everyone)

6.3.13.2.5 Scientific Technical Information (STINFO) Training (everyone)

6.3.13.2.6 Information Security (INFOSEC) (for contractors with a SECRET clearance and access in Joint Personnel Adjudications System (JPAS)

6.3.13.3 The contractor shall ensure contractor personnel receive adequate training (safety, security, etc.). The Government will provide training on a space available/no charge basis when it is the only source of such instruction.

6.3.13.4 The contractor shall maintain training and briefing records for all personnel attending Government furnished training and briefings and provide the COR a roster of trained personnel upon request.

6.3.13.5 Mandatory Training. The contractor shall ensure contractor personnel attend at Contractor expense all applicable training required by law, Office of Personnel Management, Department of Defense (DoD), and/or AF policy (including command and local policy).

6.3.13.6 Occasionally, the contractor may be asked to complete additional training required for base access, network access, safety, etc. The contractor will be advised as to whether the training is mandatory or encouraged and shall only be required to participate if mandatory. As training requirements arise, the contractor shall promptly notify the CO if compliance with the requirement will cause an increase in cost to the Government prior to attendance; the contractor may not attend trainings which increase costs without reaching a supplemental agreement.

6.4 CONFLICTS OF INTEREST

6.4.1 The contractor shall not assign to contract or task order performance any person, including any employee of the U.S. Government, if employing that person would create a conflict of interest under any law, regulation, or policy of the United States Government. Additionally, the

6.4.2 Contractor shall not assign to contract or task order performance, any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoD Directive 5500.7-R and any other applicable regulation or policy of the Department of the Air Force or its subordinate commands, as applicable, including but not limited to Air Force Materiel Command.

6.5 QUALITY CONTROL PLAN

6.5.1 The contractor shall establish a complete Quality Control Program (QCP) via a Quality Control Plan 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. The report shall be submitted to the Unit/Organization Safety POC NLT 30-days after contract award. (CDRL A010)

6.5.2 Quality Assurance

6.5.2.1 The Contracting Officer Representative (COR) is the authorized Government representative(s) who will perform assessments of the Contractor’s performance. After contract award, the identity of the COR(s), with a letter defining duties and authority, will be promptly furnished to the Contractor.

6.5.2.2 The COR(s) or alternate(s) will inform the task manager in person when discrepancies occur and will request corrective action. The COR(s) or alternate(s) will make a notation of the discrepancy on the assessment checklist with the date and time the discrepancy was noted and will request the task manager (or authorized representative) to initial the entry on the checklist.

6.5.2.3 Any matter concerning a change to the scope, prices, terms, or conditions of this contract shall be referred to the Contract Officer (CO).

6.5.2.4 The services to be performed by the contractor during the period of this contract are always subject to review by the CO or authorized representative(s).

6.5.2.5 The Government will periodically evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The Government representative will evaluate the contractor’s performance through inspections and receipt of complaints from base personnel.

6.5.2.6 The Government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints.

6.5.3 Government Observations

6.5.3.1 The COR will perform periodic surveillance 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. The CO will authorize any changes to the contract verbally and/or in writing.

6.6 HOURS OF OPERATION

6.6.1 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 5:00am – 5:00 pm, Monday thru Friday.

6.6.2 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’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.

6.6.2.1 Good Friday is regarded as a holiday by the Utah Wage Determination;

however, Good Friday is not a Federal Holiday so the Government facilities will be open for work that day. The contractor shall plan on employees working business as usual on that day, unless the Government supervisor or section chief determines that such services are either unnecessary or will be less than a full normal workday.

6.6.3 Down Days/Weather Days. The Government will notify the contractor when official notice has been given for Energy/Weather Down days. The contractor is not expected to work on any Energy/Weather Down days.

6.6.3.1 Rescheduling. Down Days/Weather days may be rescheduled if conditions/emergency operations require.

6.7 TRAVEL REQUIREMENTS

6.7.1 The contractor may be required to travel to support the objectives of this PWS.

The contractor shall obtain approval from the Government Program Manager / Contracting Officer Representative (COR), 14 days in advance before traveling unless otherwise directed.

6.7.1.1 Airfare for travel and per diem shall be billed IAW FAR 31.205-46. The contractor is responsible for making all necessary travel arrangements.

6.7.1.2 Trip Reports shall be included in status reports. (CDRL A001)

6.8 CONTINUATION OF ESSENTIAL DOD CONTRACTOR SERVICES DURING

CRISIS

6.8.1 IAW AFI 63-124, paragraph 2.7.1, and DODI 3020.37, this requirement is not considered mission essential.

6.9 REPORTING OF CONTRACT LABOR HOUR / MANPOWER REPORTING

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

6.9.2 Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 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 FedDesk, see http://www.sam.gov/SAM/pages/public/index.jsf.

(CDRL A007)

6.9.3 Uses and Safeguarding Information: Information from the secure web site is 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’s name and contract number associated with the data. User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

6.10 CONSERVATION OF UTILITIES

6.10.1 The contractor shall ensure that contractor employees follow applicable Air Force base utilities conservation practices to reduce waste as much as practicable. The contractor shall be aware of OO-ALC Energy Policy IAW OO-ALC21-110, paragraph 9.2.