MRO_PWS__12_month_4Dec2017.docx

PERFORMANCE BASED WORK STATEMENT

FOR

Maintenance, Repair, and Overhaul (MRO) Software Sustainment Support

4 December 2017

TABLE OF CONTENTS

1. Description of Services

The objective of this effort is to provide continued sustainment support for the existing maintenance, repair, and overhaul (MRO) system for an additional 12 months. There will be no option during this 12 month period for implementation for any 309 MXW groups. The contractor shall maintain and sustain the government’s MRO application which is necessary for supporting on-time shipements of products to assigned customers. The contractor shall be responsible for sustaining the application enchancements, and managing system interfaces with Air Force legacy and other systems. The contractor shall implement in accordance with (IAW) AFI 20-110 and AFMCI 20-110 supplemental, or as policies revise and Nuclear Weapons-Related Material Management (NWRM). The contractor shallo provide MRO specific training for Government employees, program management oversight, data configuration management, process standardization, and technical expertise for MRO application usage. The contractor shall train organic personnel to the standard defined within this performance work statement (PWS).

2. Overview

The objective of the PWS is to maintain and upgrade the existing MRO application utilized by 309th CMXG, 309th MMXG, 309th EMXG for (523 EMXS, 524 EMXS, and 526 EMXS), and the 309th MXSG in order to accomplish their mission. The contractor shall also provide training to organic users in the analystical and basic MRO application requirements. The contract shall train planners, schedulers, and Producation Support technican (PST) with industy best practices and government standards of work. The contractor shall provide support to track assets which include end items and parts at the subcomponent level (End items may include full weapon system and subcomponents that consist of an end item). The contractor shall maintain the NWRM assets accountability and trackability. The contractor shall maintain, train, create and sustain interface for Impresa, the government owened MRO software application.

3. Scope

The scope of this PWS covers all the information technology solution services required to carry out the objective. The required disciplines include program management, training, application support, technical editing, data base administration, logistics management, and software access setup. Services required are:

· Maintain/Sustain the business operations of the MRO data systeme/database as changes are approved by the Government.

· Create program interfaces with other Government data systems as required to maintain the Government MRO System.

· Maintain software documentation and configuration management records

· Provide production planning, training, and process control support to the Government in order to keep Government personnel up to date with the MRO system

· Collect, analyze, and report manpower, material, scheduling, inventory and production data as required by the Government.

· Provide required/requested charts and graphs for periodic Program Management Reviews (PMR) to Wing and Group level managers.

· Recommend maintenance process improvements incorporating industry best practices

· Implement changes in maintenance/production policy and procedures as required by the Governemnt.

· Provide training of both users and customers in the area of application utilization and visibility, job routing procedures, supply integration, systems reporting, scheduling procedures, planning procedures, material ordering, and other specialized handling and knowledge of issues surrounding NWRM components in the MRO.

· Provide remote and onsite customer support as required for both local and remote units.

· Provide NWRM support to establish visibility reporting tools and ensure system integrity of NWRM items for MRO including modification, repair, test/evaluation, and demilitarization effort

4. Service Requirements

4.1 MRO Application Sustainment Effort

4.1.1 The contractor shall provide expertise in the technical areas of system administration for the maintenance, sustainment, and day-to-day operation of the MRO system..

4.1.2 The contractor shall provide program management oversight for daily operations for contract personnel; provide technical programming and software life-cycle management IAW industry best practices.

4.1.3 The contractor shall participate in Kaizen and Lean team events.

4.1.4 The Contractor shall provide consolidation from several data sources that include various Legacy data stored in Government owned Data base Management Systems or Oracle

4.1.5 Contractor shall be required to work with various system points of contact to determine the best data sources.

4.1.6 The contractor shall be a team member on the function review Boards, (Sustainment, Implementaion, etc.), and the Changes Contract Board, (CCB). Shall take notes, make recommendation, create and upate documents related to each board which historically meets 3 times per week.

4.1.7 The contractor shall develop application enhancements, (historically 100 Request For Changes per month), coordinated with and approved by the government. Application enhancements include creating program specifications and test criteria, code and test programs, and producing program documentation; using applicable structured process improvements and object-oriented principles and tool suites; Configuration Management policies including source code management. The contractor shall perform work above IAW DoD, Air Force, and AFMC architectures, policies and standards. (DoD 5000.1, DODI 5000.2 and DODI 8580.1)

4.1.7.1 The contractor shall provide on-site support for the sustainment of the MRO application and the associated enhancements.

4.1.7.2 The contractor shall report all status changes in application enhancements in their Monthly Status Report. (CDRL A001)

4.2 Project Management

4.1.1 The contractor shall provide an on-site Program Manager to the point of contact for the Government Program Manager, the Functional Commander / Functional Director (FC/FD), and Group level management. Program management shall be responsible for establishing and implementing work standards and processes, delegating contractor/subcontractor assignments, supervising contractor personnel and communicating policies, purposes, and goals to subordinates, and overall surveillance and operational success of assigned tasks. Ultimately, this position shall be responsible for overall contract/contractor performance and customer satisfaction.

4.1.2 Program management shall provide the business expertise and operational sustainment for the overall requirement to contract personnel. The program manager shall have APICS professional certification.

4.1.3 Program Manager shall manage all areas of the required IT services, Program Manager, AFSO 21 initiatives, and APICS.

4.1.4 Program Manager shall provide direction and priority to contract core individuals to excute plans from Group to Group.

4.2 Project Leads

4.2.1 The contractor shall provide sufficient number of Leads to accomplish the work below to the Group, and Squadron level. Project Leads will act as first-line Point of Contact for contract support within each Group / Squadron. The contractor Project Leads shall delegate work assignments to contractors and manage information flow between the Government and the contract employees. This position shall be responsible for establishing and implementing existing work standards and processes to the government in various training forums and shall resolve customer concerns or complaints regarding application performance.

4.2.2 Each Group and Squadron has specific meetings that require contractor support. These meetings include but are not limited to: staff meetings, production meeting, configuration review boards, product focus team meeting (multiple meetings per squadron), and other scheduling, planning, and material meetings. Historically the number of meetings per squadron has varied from 30 to 80 meeting per month. The contractor shall support meetings with organizations outside the Group and Wing regarding MRO applications and methods. Dedicated squadron staffing is critical to the day to day operation of the production organizations. The contractor will be given 24 hours advanced notice of meetings they will be required to attend.

4.2.2.1 Occasionally there are special circumstances in which critical responses are required by groups to provide updates or certifications in meetings. Notification may be made at the last minute to attend these meetings and support is required.

4.2.3 The Contractor Project Lead shall provide oversight and training to a wide variety of government managers and suggest implementation and sustainment for all MRO application operations. Report and manage compliance issues or concerns to group management, the MMXG Contract Project Lead (in accordance with AFI 20-110), and provide recommendations/resolutions for deficiencies. The contractor shall make recommendations to incorporate efficiencies and industry best practices into processes IAW AFSO 21 initiatives.

4.3 Requirements Management

4.3.1 The contractor shall provide business process improvement recommendations that include all activities involved in helping improve customer data systems through business process redesign, including rethinking program design, and aligning information technology with business missions, goals, and objectives.

4.3.2 The contractor shall provide highly technical and/or specialized guidance concerning Business Systems Solutions (automated and manual) to complex information processing problems related to the subject matter field. Performs analyses and studies, prepares reports and presentations to provide functionalities to government management.

4.3.3 The contractor shall compile data and provide options to the government for conducting surveys, document reviews, and consultations for supporting organizations.

4.3.4 The contractor shall provide organizational facilitation support including aiding and building cross-functional teams within organizations and components of organizations.

4.3.5 The contractor shall perform manual and automated modeling activities, including requirements, processes, activities, and data.

4.3.6 The contractor shall perform business process reengineering.

4.4 Application Administration

4.4.1 The contractor shall monitor the MRO software application, document and analyze problems, publish maintenance schedule, and provide resolution to ensure the consistent availability and operation of the MRO software application. Historically reviews 10 issues per month.

4.4.2 The contractor shall run updates, historically 2 a month, that affect system performance with zero impact to Government workload unless approved by the Government program manager. The contractor shall maintain an MRO system availability rate of 99%.

4.4.3 The contractor shall add, delete, and modify user account information; establish/reset passwords, historically 60 updates per month, answer technical queries/reports; document 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 summary in the Monthly Status Report. (CDRL A001)

4.4.4 The contractor shall develop technical reports, studies, white papers, and presentations to support Air Force systems and processes. Historically 60 per month. Time frame will be determined by the complexity of the requirement. The contractor will work with the requiring group to determine completion date. (CDRL A002)

4.4.5 The contractor shall review the governing regulations (AFI21-101, AFI20-110, AFI21-204, AFI21-102, DoDI8500.2, DoD 5000.1, DODI 5000.2 and DODI 8580.1) to ensure proper program support, initiating MRO policy/procedural changes and changes are incorporated into the training guides. This timeframe is negotiated with the PM. Currently there are 325 user guides with 25 updates per month historically.

4.4.6 The contractor shall coordinate with management to identify, make recommendations, and implement the management tools, business practices, and MRO software needed to improve and maintain "on time" deliveries to the 309th MXW customers.

4.4.7 The contractor shall provide required updates and maintenance to support all used interfaces. The contractor shall monitor, update and maintain existing Legacy environment software systems interfaces to ensure that the interfaces exchange data properly and to support the current Legacy environment. Shall incorporate new concepts in manufacturing and repair/overhaul supporting Lean/Continuous Process Improvement principles. Historically 24 hours a month is spent monitoring interfaces.

4.5 Configuration Management

4.6.1 Data Records and Configuration Lifecycle Manager

4.5.1.1 The contractor shall provide sufficient number of Configuration Managers to the Wing, Group, and Squadron level. Create and maintain user guides for the MRO system and processes. All changes must be documented in the Monthly Status Report. (CDRL A001)

4.5.1.2 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 A002)

4.5.1.3 Manage the lifecycle process for application and process enhancements, improvements, (historically 100 changes per month) implementations, refreshes and sustainment. Maintain wing level Configuration Management CMII certification.

4.5.1.4 Manage the MRO release change process. Receive and process ‘Requests for Change’ (RFC) and route through appropriate personnel based on request type. (historically 100 changes per month) Conduct technical and Functional Feasibility meetings to determine scope and priority for projects and tasks. Summary of all RFC’s shall be reported in the Monthly Status Report.

4.5.1.5 Maintain Master Project Plans for each Group with detailed project tasks and work breakdown structures using industry standard project management techniques. Master plan will be coordinated with Group contractor project lead to meet individual Group goals and milestones for implementation and sustainment.

4.5.1.6 Maintain accurate lifecycle status for all tasks and projects. Assign resources to project tasks and conduct regular progress meetings to ensure accurate project and lifecycle information and identify tasks requiring escalation or reassessment.

4.5.1.7 Facilitate data records management following industry and Air Force best practices.

4.5.2 Contractor shall audit serialized items in the MRO system and related attributes against source data (e.g. Tech data, drawings, D043, FLIS, REMIS). (CDRL A001)

4.5.2.1 Contractor shall manage MRO application to audit all NWRM serialized controlled items and related attributes against official published NWRM list. When official NWRM master listings are updated, and distributed, contractor shall update MRO application to maintain item attribute and data accuracy (e.g. part number, NSN and descriptions). As changes occur, the contractor shall report updates to MRO application to NWRM responsible officer within 24 hours. (CDRL A002)

4.5.3 Contractor shall interface with Government Planners and System Program Office (SPO) to maintain the Bill of Material (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).

4.5.4 Contractor shall report deviations (errors) for both serialized items (within 30 days) and serialized NWRM items (within 24 hours) to NWRM Responsible Officer when inconsistencies exist between Technical Data or official NWRM lists and Legacy systems (e.g. D043).

4.5.5 The contractor shall coordinate with planning, scheduling and shop floor personnel to process MRO Engineering Change Requests (ECR) for over 262 ECRs per month, running reports, and ensure configuration management data is accurate (i.e., attributes are representative, documentation is available).

4.5.6 The contractor shall create and sustain optimal structure and content using industry best practices and IAW government standards of work for BOM, shop routings, and other data critical to Material Requirements Planning (MRP) processing and material supportability.

4.5.7 The contractor shall make recommendations to modify or implement business processes to industry best practices with Configuration Control Board (CCB) approval.

4.5.8 The contractor shall perform complex testing on configuration software and process improvements.

4.5.9 The contractor shall follow applicable Configuration Management policies including source code management per 75 ABW/SC policy IAW DoD Policy 8570.1-M, Referenced in Para 7.2.6 of this PWS.

4.6 Application and System Training

4.6.1 The contractor shall provide formal and On the Job Training (OJT) for MXSG and 709 MXSS leadership. Formal training shall be conducted in a classroom or similar environment. The contractor shall also conduct one-on-one and group training when requested by Government personnel. Historically the Government has requested formal classroom training once a month.

4.6.2 The contractor shall document each formal training session conducted reporting attendees, time, date, and overview of what was trained, IAW submitted Training Plan and provide the status in the Monthly Status Report. This is a stand-alone section in the Monthly Status Report. All training shall be conducted IAW the approved Training Plan submitted and accepted by the government.(CDRL A001)

5 Services Summary

Contractor shall provide Monthly Status Report.

4.1.7.2 4.5.3 4.6.1.1 4.6.2 4.7.2 Delivered on or before the 5th business day of each month with a one day deviation. (CDRL A001)

4.6.1.2 As Required; Contractor must provide documents by negotiated date to Program Management Office. (CDRL A002)

Contractor shall provide Monthly Status Report.

4.1.6.2 4.5.3 4.6.1.1 Delivered on or before the 15th business day of each month with a one day deviation. (CDRL A001)

6 Government Furnished Property and Services The Government will provide workspace, working supplies, furniture, access to business telephones, laptops with internal Wireless Card to contractors the Government deems necessary to have remote access and Virtual Private Network (VPN) access to the base network, desktop computers to facilitate network connectivity for business purposes only, computer facilities and computer time as required. 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.

7 General Information

7.1 Installation-Specific Safety and Health Standards

7.1.1 VPP

7.1.1.1 Hill AFB, along with the entire Air Force, has adopted the Voluntary Protection Program (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.

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

7.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. Submit to the CO as part of the installation’s annual OSHA VPP self-evaluation report. (CDRL A003)

7.1.2 Safety Program

7.1.2.1 The contractor shall implement a safety program that ensures protection of Government personnel and property. (See Appendix C)

7.1.2.2 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 309 MXW safety. (CDRL A004)

7.2 Security Requirements

7.2.1 The contractor shall complete a "Request for Identification Credential (AFMC Form 496)" for each employee of the contractor requiring access to Hill AFB. The requests shall be submitted to the contracting office for signature then to Pass and Registration (South or West Gate Visitors Center).

7.2.2 The Contractor shall complete a DD1172-2 to obtain a Base Common Access Card (CAC) card for all of their employees and submit to the appropriate security manager. The contractor shall obtain a Building ID and access card from the appropriate Building Security Manager for all of their employees.

7.2.3 The contractor administrator shall complete an “Unescorted Entry Authorization Certificate” (AF Form 2586) for each employee requiring entry into controlled areas. The request shall be submitted to the contracting office for signature then Pass and Registration (Gates Visitor Center).

7.2.4 The Contractor shall be required to fulfill the necessary facility clearances for all areas within the contract which will include NACI to Secret clearances. A DD254 is applicable and will be completed by the government.

7.2.5 All contractor personnel shall be qualified and maintain certifications as listed throughout this PWS and IAW DoD 8570.1-M Information Assurance Workforce Improvement Program, Chapters 3-4 and Appendix 3 and 4 at time of contract award and throughout the duration of the contract. See Chapter 2, Figure 1 (C2.F1) for the Overview of Work Force Structure by contract start date.

7.2.6 Personnel providing service under the basic contract shall be required to currently have the DoD 8570.1-M certifications, as shown in the following table on the first day of performance on this contract:

7.3 Quality Control

7.3.1 The contractor shall establish a complete Quality Control Plan pre-award to ensure the requirements of this contract are provided as specified; Contractor format is acceptable. The Contracting Officer (CO) will notify the contractor of acceptance or required modifications to the plan before the contract start date. The contractor shall make appropriate modifications (at no additional cost to the Government) and obtain acceptance of the plan by the CO before the start of the first operational performance period. (CDRL A005)

7.4 Quality Assurance

7.4.1 Quality Assurance is the contractor’s responsibility. In order to monitor Quality Assurance, the Government will evaluate the contractor’s performance by appointing a representative to monitor performance and to ensure services are received. The Government representative will evaluate the contractor’s performance through intermittent on-site inspections and receipt of complaints from MXW personnel. 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. Likewise, the Government may decrease the number of quality control inspections if merited by performance. The Government will also investigate complaints received from various customers located on the installation. The contractor shall be responsible for initially validating customer complaints. However, the CO shall make final determination of the validity of customer complaint(s) in cases of disagreement with customer(s).

7.5 Contracting Officer’s Representative

7.5.1 The Contracting Officer’s Representative (COR) is the authorized Government representative(s) who will perform assessments of the contractor’s performance. Each Group will have their own primary COR with the lead COR being from the Acquisition Management Support Office (AMSO). Subsequent to contract award, the identity of the COR, along with their duties and authority, will be provided in the Quality Assurance Surveillance Plan (QASP)

7.5.2 The COR or alternate(s) will inform the contract manager when discrepancies occur and will request corrective action. The COR or alternate(s) will make a notation of the discrepancy on their assessment checklist with the date and time the discrepancy was noted and will request the FC/FD to initial the entry on the checklist.

7.5.3 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the CO and not to the COR’s.

7.5.4 The services to be performed by the contractor during the period of this contract shall at all times and places are subject to review by the CO or authorized representative(s).

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

7.6.1 Key Control

7.6.1.1 The contractor shall establish and implement methods of ensuring that all keys/key cards issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons. (NOTE: ALL REFERENCES TO KEYS ALSO INCLUDE KEY CARDS. NO KEYS ISSUED TO THE CONTRACTOR BY THE GOVERNMENT SHALL BE DUPLICATED. THE CONTRACTOR SHALL DEVELOP PROCEDURES COVERING KEY CONTROL THAT SHALL BE INCLUDED IN THE QUALITY CONTROL PLAN. SUCH PROCEDURES SHALL INCLUDE TURN-IN OF ANY ISSUED KEYS BY PERSONNEL WHO NO LONGER REQUIRE ACCESS TO LOCKED AREAS).

7.6.1.2 The contractor shall immediately report the occurrences of a lost or duplicate key to the Government Program Manager.

7.6.1.3 In the event keys, other than master keys, are lost or duplicated, the contractor shall, upon written direction of the CO, rekey or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform rekeying. When the replacement of locks or rekeying is performed, the total cost of rekeying or the replacement of the lock or locks shall be borne by the contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the contractor.

7.6.1.4 The contractor shall prohibit the use of keys issued by the Government by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor’s employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the CO.

7.6.2 Lock Combinations

7.6.2.1 The contractor shall establish and implement methods of ensuring that any lock combinations are not revealed to unauthorized persons. The contractor shall ensure that 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.

7.7 Hours of Operation

7.7.1 Normal Hours of Operation. The contractor shall perform the services required under this contract within the following hours: Monday through Friday 0500–1800 – EXCEPT FEDERAL HOLIDAYS. Contract personnel will work the same hours as government employees in the organization the contractor is assigned to. Work provided outside of normal hours shall be preapproved by the Program Manager.

7.7.2 Emergency Services. On occasion, services may be required to support an activation or exercise of contingency plans outside the normal duty hours described above. The contractor shall be on call 24 hours daily to include Saturdays, Sundays and Holidays to facilitate system availability.

7.7.3 Government Closures. Unless required under the terms of the contract or authorized by the CO, the contractor shall not work at any Government facility, nor should any deliveries under this contract be made to any Government facility, on any of the following holidays:

· New Year’s Day – 1 January

· Martin Luther King, Jr.’s Birthday – 3rd Monday in January

· President’s Day – 3rd Monday in February

· Memorial Day – Last Monday in May

· Independence Day – 4 July

· Labor Day – 1st Monday in September

· Columbus Day – 2nd Monday in October

· Veteran’s Day – 11 November

· Thanksgiving Day – 4th Thursday in November

· Christmas Day – 25 December

· Any other day designated by Federal Statute, Executive Order or Presidential proclamation.

7.7.3.1 When a holiday falls on a Sunday, the following Monday will be observed as a legal holiday. When a holiday falls on Saturday, the preceding Friday is observed as a holiday by U.S. Government agencies.

7.7.3.2 When the Government grants administrative leave to Government employees as a result of inclement weather, potentially hazardous conditions or other special circumstances, contractor personnel working at the specific facility/location granted administrative leave should also be dismissed. The costs associated with the period of any such Agency closure shall not be a direct reimbursable cost under this contract. If authorized in accordance with the contractor’s normal accounting procedures, these costs MAY be reimbursable as an indirect cost using established indirect cost pools.

7.8 Conservation of Utilities

7.8.1 The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions which prevent the waste of utilities. Government telephones shall be used only for official Government business.

7.9 Government Observations

7.9.1 Government personnel, other than CO’s and quality assurance personnel (COR’s), may from time to time, with CO coordination, observe contractor operations. However, these personnel may not interfere with contractor performance or make any changes to the contract.

7.10 Training

7.10.1 From time to time the Contractor shall be asked to complete training required for base access, network access, safety, etc. Contractors will be advised as to whether or not the training is mandatory or encouraged and shall only be required to participate in mandatory training. 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 so that a supplemental agreement may be reached.

7.11 Travel Requirements

7.11.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 fourteen days in advance before traveling unless otherwise directed. As part of the PMR, a trip report is required. Airfare for travel and per diem shall be billed IAW FAR 31.205-46. The contractor is responsible for making all necessary travel arrangements. (Appendix F)

7.12 Continuation of Essential DOD Contractor Services During Crisis IAW DoDI 3020.37. IAW AFI 63-124, paragraph 2.7.1, and DODI 3020.37, this requirement is not considered mission essential.

7.13 Phase Out Plan

7.13.1 If there is a change in contractor or if the operation reverts to in-house, the incumbent contractor will provide familiarization, to the Government or the follow-on contractor, whichever the case may be. During the phase-out familiarization period, the incumbent will be fully responsible for all requirements of this contract.

7.13.2 The Government reserves the right to conduct site visits in all contractor operated facilities in conjunction with the solicitation of offers for the follow-on contract. In the event the follow-on contract is awarded to other than the incumbent, the incumbent contractor will cooperate to the extent required to permit an orderly change over to the successful contractor. With regard to the successor contractor’s access to incumbent employees, a recruitment notice may be placed in each facility.

7.14 Publications

7.14.1 Compliance with publications, regulations and operating instructions provided by the Government is required when:

7.14.1.1 They pertain to the procedures for materials expediting herein and where the contractor is authorized by the statement of work to accomplish the work specified in the publication, regulation or operating instructions.

7.14.1.2 The publications prescribe USAF policies, use of materials, procedures and processes applicable to the work requirements.

7.14.1.3 The contractor is required to acquire and work according to the latest version of the publication.

APPENDIX A

ACRONYMS AND ABBREVIATIONS

APPENDIX C

SAFETY, FIRE PROTECTION AND HEALTH

SPECIFICATION

INDUSTRIAL SAFETY REQUIREMENTS

OGDEN AIR LOGISTICS COMPLEX

UNITED STATES AIR FORCE

HILL AIR FORCE BASE, UTAH 84056

(MRO) Software Sustainment Support for OO-ALC

22 Nov 2017

OO-ALC/SE

Control Number: TH171109

SECTION I - GENERAL REQUIREMENTS

A. Safety Program Requirements.

The contractor will implement a safety program that ensures protection of Government personnel and property. The program will consist of, as a minimum:

1. Mishap reporting, as defined in paragraph B1 below.

2. Routine and recurring surveillance to ensure the safety requirements of this contract are enforced.

3. Identification of segregated work site locations for operations that cannot be co-mingled with general industrial operations and the process for ACO approval of operations and changes at these specific sites.

4. All contractor personnel shall be trained and qualified to perform their duties safely.

5. The contractor shall include a clause in all subcontracts requiring the subcontractors to comply with the safety provisions of this contract, as applicable.

6. Per AFPAM 91-210, para 6.4, due to non-hazardous nature of work, a Safety Plan and corresponding site specific checklist is not required.

B. Mishap Notification

1. The contractor shall notify OO-ALC/SE (801-586-6038) or the Hill AFB Command Post (801-777-3007) after normal duty hours, and the designated Government Representative (GR), i.e., the ACO, PCO, or DCMA COR (Contracting Officer's Representative) within one (1) hour of all mishaps or incidents at or exceeding $2,000 (material + labor) in damage to DOD property entrusted by this contract, even if the government is wholly or partially reimbursed. This notification requirement shall also include physiological mishaps/incidents. A written or email copy of the mishap/incident notification shall be sent within three calendar days to the GR, who will forward it to OO-ALC/SE. For information not available at the time of initial notification, the contractor shall provide the remaining information no later than 20 calendar days after the mishap, unless extended by the ACO.

Mishap notifications shall contain, as a minimum, the following information:

(a) Contract, Contract Number, Name and Title of Person(s) Reporting

(b) Date, Time and exact location of accident/incident

(c) Brief Narrative of accident/incident (Events leading to accident/incident)

(d) Cause of accident/incident, if known

(e) Estimated cost of accident/incident (material and labor to repair/replace)

(f) Nomenclature of equipment and personnel involved in accident/incident

(g) Corrective actions (taken or proposed)

(h) Other pertinent information

2. The contractor shall cooperate with any and all government mishap investigations. Additionally if requested by government personnel or designated government representative (GR), i.e., the ACO, PCO, or DCMA COR (Contract Officers Representative), the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by safety investigators.

3. The contractor shall provide copies of contractor data related to mishaps, such as contractor analyses, test reports, summaries of investigations, etc. as necessary to support the government investigation.

4. The contractor shall support and comply with the safety investigation and reporting requirements of AFI 91-204, Chapters 1 – 5.

C. General Safety Requirements:

Contractor personnel must receive Explosive Safety Awareness Training if their duties require entry into the Explosive Clear Zone. This training will be provided by the OO-ALC Safety Office. Contact Eric Covington at 586-0168.

A Risk Assessment will be required prior to any work being accomplished, if munitions will remain in the facility.

Compliance with OSHA and other applicable laws and regulations for the protection of contractor employees is exclusively the obligation of the contractor. Note: The government shall assume no liability or responsibility for the contractor's compliance or non-compliance with such requirements. The contractor shall furnish to each of his/her employees a place of employment, which is free from recognized hazards. The contractor shall brief his/her employees on the safety requirements of this contract and on hazards associated with prescribed tasks. The contractor is responsible for compliance with OSHA Public Law and the resultant standards identified within. In addition, the contractor is required to flow down the safety requirements/specification to all subcontractors. This applies to Federal Acquisition Regulation (FAR) 12 commercial acquisitions as well. This contract shall in no way require persons to work in surroundings or under working conditions which are unsafe or dangerous to their health. The contractor must coordinate and perform work so as not to impact the safety of government employees or cause damage to government property. This requires providing personnel with protective equipment and associated safety equipment as may be necessary. The contractor must also protect personnel from hazards generated by the work. If the contractor employs BILINGUAL speaking employees, they must post bilingual signs and have written procedures for specific tasks in applicable languages.

SECTION II – SPECIFIC REQUIREMENTS

PEDESTRIAN CROSSWALKS: All contractor personnel are required to use the closest crosswalk, or traffic controlled intersection when crossing the road. Pedestrians must look both ways to ensure the coast is clear before stepping out into the crosswalk. Pedestrians DO NOT have the right of way unless they are already in the crosswalk. Contractor vehicle operators have the same responsibilities as pedestrians, to share the road and mutually observe and yield to pedestrians.

MOTOR VEHICLES: Contractor shall comply with the standards in: DoD Directive 5525.4, Enforcement of State Traffic Laws on DoD Installations", Nov 2, 1981, Para 3-4; DODI 6055.4, DoD Traffic Safety Program, 20 Jul 99; AFI 91-207, USAF Traffic Safety Program, 22 May 07; and AFI 91-207 AFMC SUP1, The US Air Force Traffic Safety Program, 1 Oct 07. Each applies to all persons at any time on an Air Force Installation and includes all leased, owned, or privatized property including housing areas. In addition: AFI 13-213, Airfield Management, applies to all contractors, sub-contractors, vendors, commercial delivery companies, and all other private business vehicles who operate anywhere on Hill Air Force Base, including the airfield (to include the industrial areas and any buildings or hangars located upon the airfield) in support of their mission.

HOUSEKEEPING: Housekeeping shall be conducted according to the requirements in OSHA Standard 29 CFR 1910.141. CLEAN AS YOU GO will be enforced.

Element/Requirement Referenced Benchmark

Contract Safety AFPAM 91-210 Para. 6

Facility Fire Protection NFPA 13, 70, & 72

NFPA 409/410

AFI 91-203 Chapters 6, 22

Handling, Storage and use of Flammable/ NFPA 30, 33

Hazardous Material Management AFI 32-7086 HAFBSUP 1

Storage and Materials Handling DoDI 4140.62 image1.png