FinalPWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

For

DVADR Interface with EW 1553 Bus

1 April, 2014

Prepared by:

A-10 Division

AFLCMC/WWA

Hill AFB, Utah 84056 PR Number:

JCN:

ACRONYM LIST

AATC Air National Guard/Air Force Reserve Command Test Center ACA Associate Contractor Agreement ACO Administrative Contracting Officer APPP Abbreviated Program Protection Plan AIS Automated Information System ATE Automatic Test Equipment CCB Configuration Control Board CDRL Contractor Deliverable Requirements List CMSC Counter Measure Set Control COR Contracting Officer’s Representative DID Data Item Description DoL Department of Labor DVADR Digital Video Air Data Recorder ECAP Electronic Combat Adaptive Processing EO Engineering Orders ESOH Environmental, Safety, and Occupational Health EW Electronic Warfare EW SPO EW System Program Office EWS Electronic Warfare System FAR Federal Acquisition Regulation GFE Government Furnished Equipment GFI Government Furnished Information GFM Government Furnished Material GFS Government Furnished Software IAW In Accordance With ICMP Integrated Configuration Management Plan IMS Integrated Master Schedule IPR In Process Review MCCR Mission Critical Computer Resources MSR Monthly Status Report NDA Non-Disclosure Agreement OUE Operational Utility Evaluation PCO Procuring Contracting Officer PMR Program Management Review PWS Performance Work Statement QAE Quality Assurance Evaluator SE Support Equipment SEP System Engineering Plan SPO System Program Office TCTO Time Compliance Technical Order TDP Technical Data Package T.O. Technical Order TOGC Technical Order Guidance Conference TOMP Technical Order Management Plan TOPP Technical Order Process Plan TOVP Technical Order Verification Plan VPP Voluntary Protection Program WR Warner Robins

Table of Contents

1.0 INTRODUCTION

1.1 Background

1.2 Purpose

1.3 Scope

2.0 APPLICABLE DOCUMENTS

2.1 Compliance Documents

2.2 Reference Documents

3.0 CONTRACTOR TASKING/REQUIREMENTS

3.1 Digital Video Airborne Data Recorder

3.2 Ground Install for Validation and Verification Support

3.3 Program and Engineering Management Support

3.4 Program Metrics

3.5 Data

3.6 Associate Contractor Agreement (ACA)

3.7 Quality Assurance Program

3.8 Art Work

4.0 DELIVERABLES (Contractor Data Requirements List)

4.1 Government Inspection and Acceptance of Deliverables

4.2 Delivery Requirements

5.0 ADMINISTRATIVE

5.1 Security

5.2 Access to Government / Contractor Facilities and Property

5.3 Government Furnished Information, Equipment, Materials, and Software

5.4 Travel Requirements

6.0 SERVICES SUMMARY

6.1 Services Summary Table

6.2 Government Quality Assurance Surveillance

6.3 Contractor Quality Assurance Requirements

6.4 Methods of Surveillance

7.0 STATEMENT OF MISSION ESSENTIAL SERVICE………………………………12

Appendix A – Safety Appendix B – Sample T-2

1.0 INTRODUCTION

1.1 Background

An initial Electronic Warfare System (EWS) Sustainment Operational Utility Evaluation (OUE) was completed in FY12 by 579 SMXS/MXDPC [organic source of Mission Critical Computer Resources (MCCR) and Automatic Test Equipment (ATE)], with support from Georgia Technical Research Institute (GTRI), and AFLCMC/WNY (EW SPO – Electronic Warfare System Program Office) to demonstrate basic functionality of an EWS preferred solution to address several areas of concern. This effort will herein be referred to as the Warner-Robins (WR) OUE, and the technical data from that previous T-2 modification will be provided for the completion of this effort.

This effort relates to the portion of the modification relevant to interfacing the Digital Video Air Data Recorder (DVADR) with the EW bus for the purpose of recording MIL-STD-1553 traffic on the EW bus. The Flight Test Report from AATC for the WR OUE (ACC 12-140R A-10C EWSS ALQ-213 CMS TAPE 4. 0E OUE FR) shows this interface, as tested, was satisfactory and effective.

Adding the DVADR to the EW bus provides for a quick (less than 5 seconds) ground/inflight ALQ-213 CMS MDF reprogramming capability via DVADR. It also provides for a method to record traffic across the EW MIL-STD-1553 bus which allows for EW events (chaff/flare, decoy deployed, jamming employed, VECTS threats locations, and angle of attack cone) to be played back on the PCDS alongside current recorded flight data displays (IP-1310, CMSP and countermeasures set control [CMSC], VECTS threat location, VECTS threat state, and Electronic Combat Adaptive Processing [ECAP] priority threat).

1.2 Purpose

The purpose of this effort is to prepare a permanent modification package to allow for the connection of the EW 1553 bus to the DVADR.

1.3 Scope

This effort encompasses:

1.3.1 The creation, verification, and validation of the technical source data needed to support future kit procurement for permanent implementation of the interface of the EW 1553 bus and the DVADR.

The technical data package shall include updated Engineering Orders (EO), updated baseline engineering drawings and source data for applicable Technical Order (T.O.) updates for the following:

a. Connection to the EW 1553 bus to the DVADR

b. Modifications to Support Equipment (SE) as appropriate from the task above

The Contractor shall develop, integrate and validate technical data to an A-10C Suite 7B aircraft, in compliance with TCTO 1A-10C-564 (ALQ-213 Processor Upgrade).

2.0 APPLICABLE DOCUMENTS

2.1 Compliance Documents

a. AFI63-131, Modification Program Management, 19 Mar 2013

b. AFI 63-101, Integrated Life Cycle Management, 7 Mar 2013

c. A-10 OI 63-21, 1067 Process Management, 28 Jun 2011

2.2 Reference Documents

a. 08-A10DOC-001, A-10 Drawing Practice, 11 Aug 2008

b. 08-A10DOC-010, A-10 Integrated Configuration Management Plan (ICMP) Rev. E, 11 May 2012

c. 08-A10DOC-1084, A-10 Avionics System Architecture Roadmap Rev. C, 13 Nov

d. 09-A10DOC-006, A-10 System Engineering Plan (SEP) Rev. 2, 30 Sep 2008

e. 10-A10DOC-0001, A-10 Architecture Management Plan, 27 Jan 2012

f. 11-A10DOC-004, A-10 3D Modeling Specification, 22 Jun 2011

g. 11-A10DOC-005, A-10 NX Drafting Specification (for CAD generated drawings/sheets), 22 Jun 2011

h. 12-A10DOC-001, A-10 Abbreviated Program Protection Plan (APPP), 15 Dec 2011

i. 12-A10DOC-002, A-10 Data Exchange Specification, 26 Jan 2012

j. 12-A10DOC-009, A-10 3D Model Validation Specification, 16 Oct 2012

k. 13-A10DOC-001, A-10 2D Drawing to 3D Model Migration Specification, 7 Feb 2013

l. T.O. 00-5-1, Air Force Technical Order System, 1 May 2011

m. T.O. 00-5-3, Air Force Technical Manual Acquisition Procedures, 31 Dec 2009

n. TCTO 1A-10C-564, ALQ-213 Processor Upgrade,

o. MIL-HDBK-516B, Airworthiness Certification Criteria, 26 Sep 2005

p. C0020-A004-0006, A-10 Requirements Plan for A-10 Avionics System Architecture, Support Roadmap & Systems Integration Support, 18 May 2011

q. C0020-A004-0007, Architecture Management Plan for A-10 Avionics System

Architecture, Support Roadmap & Systems Integration Support, 19 May 2011

r. ASC Guide to Technical Reviews/Audit for Aeronautical Weapon System Acquisition, Jul 2006A-10 Technical Order Process Plan (TOPP)

s. A-10 Technical Order Verification Plan (TOVP)

t. A-10 Technical Order Management Plan (TOMP)

3.0 CONTRACTOR TASKING/REQUIREMENTS

3.1 Digital Video Airborne Data Recorder

Using the source data from WR OUE for MIL-STD-1553 bus wiring to the DVADR, the

Contractor shall develop a technical data package sufficient to support future kit procurement and permanent modification. (CDRL A082)

3.1.1. Updating or creating 2D drawings with or without 3D CAD models shall be accomplished using one of the methodologies listed in the A-10 2D Drawing to 3D Model Migration

Specification 13-A10DOC-001. For updating, creating, and/or migrating 2D drawings into 3D models, one or more of the specifications listed below will be required by each methodology to ensure a complete and accurate engineering Technical Data Package (TDP). 3D models will only be required for structural parts (i.e. mounting brackets). (CDRL A201)

A-10 3D Modeling Specification 11-A10DOC-004

A-10 3D Model Validation Specification 12-A10DOC-009

A-10 NX Drafting Specification 11-A10DOC-005 (for CAD generated drawings/sheets)

A-10 Drawing Practice 08-A10DOC-001

3.1.2. The Contractor shall provide all source documentation required for releasable Time

Compliance Technical Order (TCTO) updates and for T.O. updates to support future kit procurement and permanent modification for the MIL-STD-1553 bus wiring to the DVADR modification of the WR OUE. This source documentation shall allow for independent implementation of these modifications. (CDRL A209)

3.1.2.1. The Contractor shall update existing documents and provide source data to the

Government as indicated in the TM-86-01N. Additionally, the Contractor shall correct prior technical data documentation that is found to be erroneous/inaccurate in any paragraph updated/changed by this task order.

3.1.2.2. The Contractor shall deliver source data for all existing A-10 Operational, Maintenance, and Commodity T.O.s affected by this upgrade IAW the TM-86-01N. T.O.s updated as a result of this study shall show before and after data, as well as effectivity in the technical documentation. T.O.s shall be In Accordance With (IAW) T.O. 00-5-1, TO 00-5-3, and TM-86-

01.

3.1.2.3. The Contractor shall plan and host two In-Process Reviews (IPR) in accordance with the TM 86-01N. The Contractor shall provide resources for the Technical Order Review Team at formal IPRs as defined by the A-10 Technical Order Process Plan (TOPP).

3.1.2.4. The Contractor shall provide all T.O.s that incorporate the results of the Technical Order

Guidance Conference (TOGC) efforts as validated. The Contractor shall perform T.O. validation

(certification) on all affected manuals.

3.1.2.5. An addition of two 1553 couplers (for redundancy) to the EW 1553 bus is required for this modification. These couplers will connect to the DVADR. The location of these couplers used during the reference OUE is no longer an option. The Contractor shall find a new location for the new couplers. The A-10 SPO recommends either in the right hand console in the cockpit to be near the DVADR or the in bay F105 to be near existing EW 1553 couplers. Alternate locations may be recommended by the Contractor to be considered. Location decision shall prioritize minimizing installation time. A final decision on the location shall be coordinated with

A-10 SPO personnel."

3.2 Ground Install for Validation and Verification Support

3.2.1 The Contractor shall complete a ground install and check of the DVADR. The

Government will make a test aircraft available at Davis Monthan AFB, AZ during which time

Contractor shall support a ground install that includes a T-2 modification package for the task identified for the purpose of validating the technical data

3.2.2.1 Contractor shall notify government no later than three (3) months prior to required test date. This date will be supported by program schedules developed in accordance with paragraph 3.5.1.

3.2.2.2 Contractor shall submit test plans, Airworthiness related documentation, and T-2 modification packages to the Government for technical evaluation and approval by the A-10

Configuration Control Board (CCB) 90 days prior to aircraft installation. The Contractor shall support the draft T-2 packages during the review processes (i.e. Peer Review Board process, Technical Engineering Review Board process, and Configuration Control Board process). A sample template for the required T-2 modification packages is provided as an attachment to this

PWS.

3.2.3 Contractor shall be responsible for all materials not provided as Government Furnished

Material (GFM), but which are required to perform the ground install. All additional material required for completing the ground installs procured by the Contractor shall be delivered to the

Government at contract completion as a Group A kit.

3.2.4 To support the ground install for the DVADR-EW 1553 modification, the Contractor shall develop and submit T-2 modification packages for Government approval. The Contractor also may use, as applicable, the data provided by the WR OUE to support the creation of these T-2s.

The T-2 modifications shall be developed IAW AFI 63-131 & AFMCI 21-126 and shall include the following attachments, as required by the A-10 CCB and the A-10 Chief Engineer: (CDRL

A157, A158, A203)

a) Safety & Hazard Analysis

b) Weight & Balance Analysis

c) Structural Loads Analysis

d) Electrical Loads Analysis

e) Modification / De-Modification Procedures

f) Installation Drawings & Wiring Diagrams

g) Maintenance Procedures

h) Component Qualifications

i) Test Run Cards for Lab/Ground Test

j) Bench Level/Lab Test Results (HW & S/W)

k) Software Version Description

l) Airworthiness Certification

3.2.5 The Contractor shall support the Government verification of the technical source data and

T-2 packages, and shall make any corrections resulting from verification. Verification will take place at Davis Monthan AFB, AZ.

3.3 Program and Engineering Management Support

3.3.1 PM Deliverables

The Contractor shall establish and use disciplined, comprehensive, systematic program management practices. The Government will review the Contractor's plans for measuring schedule and performance to be used in tracking program status at the Kickoff Meeting.

(CDRLs A100 & A116)

3.3.2 Meetings

Kick-off Meeting The Contractor shall host a contract kick-off meeting within 14 days of task order award.

Program Management Review (PMR) The Contractor shall hold two PMRs at 4 and 8 months ARO Contract. Teleconference is acceptable to host PMRs. At a minimum, the Contractor shall present program status, schedule, milestone status, risk/problem areas and recommended corrective actions for Government review.

In-Process Reviews The Contractor shall plan and host two IPRs at or around the local Hill AFB area.

Technical Order Guidance Conference (TOGC) The Contractor shall plan and host a TOGC (via teleconference) no later than thirty (30) calendar days after contract award, to support the development of the TM-86-01N for this effort. The meeting shall review the impacts of this effort to applicable TOs. The meeting shall also review the program Integrated Master Schedule (IMS) and overall TO IMS to identify possible conflicts with other modifications. (CDRL A209)

3.4 Program Metrics

3.4.1 Program Schedule

The Contractor shall develop, update, and manage an execution schedule for the work to be accomplished under this task order. The schedule shall integrate the tasks of all members of the Contractor's team and allow critical path methodology to determine/track the program's critical elements. The schedule shall contain all control points (milestones) plus all requirements for reviews, audits and meetings required by this PWS. The schedule shall be maintained in Microsoft Project (*.mpp) format and submitted as part of the Monthly Status Report and reviewed during PMR’s. (CDRL A100)

3.4.2 Risk Management

The Contractor shall sustain a Risk Management process that meets MIL-STD-882D, Standard Practice for System Safety, for environment, safety, and occupational health risk management.

The objective of the risk management process is early identification, continuous tracking, and systematic reduction of elements that could impact the Contractor's ability to meet its technical, cost, or schedule objectives. A Risk Matrix shall be included to identify potential risk and mitigation plan as part of the Monthly Status Report. (CDRL A100)

3.4.3 Status Report

The Contractor shall provide a Monthly Status Report that, at a minimum, shall include a monthly status summary, GFE/GFM/GFP issues, program risk, open correspondence issues, schedule, and the status of technical data and other CDRLs. (CDRLs A100 and A116)

3.5 Data

3.5.1 Data Rights

All data generated under the tasks defined in this PWS shall be developed for the A-10, and the Government shall receive unlimited/unrestricted data rights.

3.5.2 Configuration Management

The Contractor shall implement configuration management practices throughout the life of this effort which meet the requirements of the current A-10C Integrated Configuration Management Plan Doc No. 08-A10DOC-010.

3.6 Associate Contractor Agreement (ACA)

The Contractor shall establish ACA’s as necessary to affect the design and to accomplish the requirements of this program. Non-Disclosure Agreements (NDA) shall be established with the vendors as required in order to support the task identified in this PWS.

3.7 Quality Assurance Program

The Contractor shall assure quality through implementation of a quality program IAW ISO 9001- 2008, or AS9100:2009 “AS9100 Rev C” standards. The quality program shall ensure that solutions, products, and services fully satisfy Government specified requirements, and are of the highest level of quality.

3.8 Art Work

The contractor shall develop and modify line drawings, schematics, and diagrams. Art work shall be IAW MIL-STD-38784 and be compatible with all deliverable requirements. All new graphics shall be delivered as vectorized CGM files. (A201)

4.0 DELIVERABLES (Contractor Data Requirements List)

The Contractor shall prepare and deliver data in accordance with references in earlier sections.

All Data Item Descriptions (DID) in the Contractor Data Requirements List, as contained in the following table, shall be used as guides in developing the data. Distribution and Number of Copies: All CDRL items will be logged into and maintained in the Contractor's electronic library, and a cover letter paper submittal will be provided to the Government's contracting officer identifying the data item and its configuration identification (date and revision level). In the event of a conflict between the CDRL and the PWS, the PWS shall take precedence. Late submittals shall be coordinated through the Government Procurement Contracting Officer (PCO).

CDRL

Description Data Item Description

Paragraph Reference

A082 System/Subsystem Specification DI-IPSC-81431A 3.1

A100 Monthly Status Reports DI-MGMT-80368A 3.3.1, 3.4.1, 3.4.2, &

3.4.3

A116 Data Accession List DI-MGMT-81453A 3.3.1, 3.4.3

A157 Test Plan DI-NDTI-80566A 3.2.4

A158 Test Procedure DI-NDTI-80603A 3.2.4

A201 Product Drawings/Models & Associated Lists DI-SESS-81000E 3.1.1, 3.8

A203 Temporary Non-Standard Modification

Documentation and Marking Requirements

DI-MISC-81562 3.2.4

A209 Air Force Technical Manual Requirements TM-86-01N 3.1.2, 3.3.2

4.1 Government Inspection and Acceptance of Deliverables

The Government Primary and Alternate Contracting Officer’s Representative (CORs) will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Contractor will be notified in writing by the Government CORs of the specific reasons why the deliverable was rejected. The Government shall have the right to require that the Contractor make changes to any technical submissions as a result of technical or program reviews, until the final CDRL submissions have been accepted.

4.2 Delivery Requirements

All data deliverables in this PWS shall be formatted for import into the A-10 TeamCenter environment using the “A-10 Data Exchange Specification” 12-A10DOC-002. In addition, drawing deliverables shall also be formatted for import into JEDMICS using the Ogden Air

Logistics Complex, Engineering, “Digital Delivery Requirements and Metadata Instructions”.

Data delivery schedule/frequency requirements are found in the CDRL for each specific task.

5.0 ADMINISTRATIVE

5.1 Security

Contractor shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be coordinated and approved by the Government.

5.1.1 Safeguarding Information

The Contractor shall not divulge any information regarding files, data, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor shall abide by all Government rules, procedures, and standard of conduct. The Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed, after task order award but prior to AIS access. When the period of performance is complete and/or Contractor personnel leave work on this project they will have 5 days to terminate all their network user accounts and to return all access cards and base identification badges.

5.2 Access to Government / Contractor Facilities and Property

5.2.1 Government Facility Access

The Government Program Manager will assist Contractor in processing the necessary DoD forms to obtain base or area badges for access to Government facilities. The Contractor shall obtain base identification for all Contractor personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the task order. Contractor personnel are required to wear or prominently display installation identification badges or Contractor-furnished, Contractor identification badges while visiting or performing work in the installation. Access to Government facilities is limited. Control of the facilities shall remain with the Government.

5.2.1.1 ID/CAC Cards

For AFMC ID or CAC Cards, if required, the Contractor shall submit a written request on company letterhead to the A-10 SPO PCO listing the following: contract/task order number, location of work site, start and stop dates, and names of employees needing access to the base. The letter will also specify the individual(s) authorized to sign for a request for base identification credentials. When reporting to the registration office, the authorized Contractor individual(s) should provide a valid driver’s license, current vehicle registration, and valid vehicle insurance certificate. During performance of the task order, the Contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site.

5.2.2 Restricted Areas

When work under this task order requires unescorted entry to controlled or restricted area, the Contractor shall comply with AFI 31-101, Volume 1, The Air Force Installation Security Program, and the AFI 31-501, Personnel Security Program Management, as applicable.

5.3 Government Furnished Information (GFI), Property, Materials, and Software

All products developed under this task order shall be considered Government work and shall have no license encumbrances. All Government Furnished Property (GFP) and Government Furnished Software (GFS) shall be returned to the Government upon completion of this task order. Any and all material required for installation that is not provided by the Government shall be the responsibility of the Contractor. The Government will provide a list of all available GFP/GFS/GFI (see attachment A).

5.4 Travel Requirements

Teleconferences will be the primary means for conducting all meetings. No separate travel line item will be incorporated into this effort. If instances arise in which the Contractor determines it is in their best interest to send a representative, the Contractor shall submit a Base Access Request to the PM and PCO in order to have the individuals properly cleared to attend the event. All costs for any such travel shall be borne by the Contractor.

6.0 SERVICES SUMMARY

6.1 Services Summary Table

Performance Objective PWS Para.

Performance Threshold Method of Surveillance

Quality of Data Products:

Contractor must submit complete and accurate data products in accordance with the applicable CDRLs.

3.1.1, 3.1.2, 3.2.3, 3.3.1, 3.3.2, 3.4.3, & 3.5.2

Data products must meet contract/task order requirements upon initial submission 97% of the time.

No more than 3% of data products shall be submitted late.

No more than 3% of data products shall have to be reworked more than once for acceptability.

Periodic (Quarterly) 100% Inspection

Correct engineering data discrepancies

3.1.1, 3.1.2, 3.2.3, 3.3.1, 3.3.2, 3.4.3, & 3.5.2

Contractor shall support Government reviews of the effort’s engineering data, associated lists, and documentation 100% of the time.

The Contractor shall make corrections and resubmit to the Government within 10 business days, unless otherwise stated by the Government.

100% Inspection

Program Management Status Monthly Status Report (MSR), Integrated Master Plan/ Integrated Master Schedule

3.4.1, 3.5.1, 3.5.2, & 3.5.3

Submitted on time 100% according to PWS or Government direction.

Contractor shall identify schedule and performance discrepancies on a monthly basis 100% of the time and recommend corrective actions.

Periodic (Monthly) Inspection

6.2 Government Quality Assurance Surveillance

The role of the Government quality assurance is to ensure that the contract/task order standards are achieved. In this task order, the quality control program is the driver for service quality. The COR will review comments from Functional and Technical Experts and the Contract Negotiator. Contractor will be notified of comments/corrections as required. For all tasks the Contractor shall perform systems engineering and quality assurance processes to ensure thoroughness, accuracy, and completeness during the development of all deliverables under this PWS and to ensure the delivery of near error free, high quality technical data.

6.3 Contractor Quality Assurance Requirements

The Contractor shall devise, implement, and maintain a comprehensive systems engineering and quality control process for this effort.

6.4 Methods of Surveillance

6.4.1 One-Hundred Percent Inspection

This method implies inspecting every time the requirement occurs. Use of this technique may be appropriate when performance has an especially critical impact on mission accomplishment or safety, occurs infrequently or contains stringent requirements.

6.4.2 Periodic Surveillance/Inspection

Periodic surveillance/inspection is the type of surveillance that is based upon selecting samples for evaluation on other than 100% inspection or on a statistically random basis. Periodic surveillance can be accomplished periodically using a checklist method. Surveillance will be accomplished monthly through a written status report and program management reviews (via teleconference or in person per the PWS).

7.0 STATEMENT OF MISSION ESSENTIAL SERVICES

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

Appendix A – Safety

1. Environmental, Safety, And Occupational Health (ESOH): The contractor is solely responsible for compliance with all federal, state and local laws, the Occupational, Safety and Health Act (Public Law 91-596) and the resulting standards, OSHA Standards 29 CFR 1910 and 1926, as applicable, and the protection of their employees. Additionally, the contractor is responsible for the safety and health of all subcontractor employees.

2. Voluntary Protection Programs (VPP): The Air Force is part of OSHA’s VPP. All contractors are required to familiarize themselves with the requirements of VPP. Information on VPP can be accessed at http://www.osha.gov. The intent of the Air Force Safety Program is to prevent injuries and to communicate our safety expectations with potential offerors as well as those contractors awarded a government contract. The Air Force’s interest is to protect personnel working in or around contractor operations, and to protect Air Force equipment/property.

3. Contractor Employees: Compliance with OSHA and other applicable laws and regulations for the protection of contractor employees is exclusively the obligation of the contractor. Note:

Air Force Occupational Safety and Health Standards (AFI’s) are annotated because many of the Air Force Standards exceed the OSHA standard criteria. If a conflict is noted, the most stringent requirement takes precedence. 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) Part 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.

4. Inspections: Air Force Environmental, Safety, Occupational Health and Fire protection officials or responsible Quality Assurance Evaluator (QAE) may periodically enter a contractor’s workplace to verify working conditions of Air Force personnel. If an Air Force employee observes improper procedures or unsafe conditions exits which place Air Force personnel or equipment/facilities in jeopardy, the contractor will remove personnel and/or equipment from the unsafe condition and immediately notify the Contracting Officer and the Installation Safety Office. Department of Labor (DoL), OSHA inspectors are authorized right of entry to inspect any place of employment operated by an Air Force contractor. They can be considered “no notice” inspections. Noncompliance with safety requirements can result in work stoppage, inexcusable delays, and/or costly fines issued by the DoL. The government shall assume no liability or responsibility for the contractor's compliance or non-compliance with such requirements. Fines and additional costs for violations levied against the contractor as a result http://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=0 http://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=0 of OSHA findings, and/or installation safety, fire, health or environmental are the sole responsibility of the contractor and shall not be passed through to the Government.

5. Mishap Notification: The contractor shall notify the AFLCMC Safety Office telephonically at

(937) 904-3386 during duty hours and (937) 510-1184 after hours. Also notify the contracting units safety office at (801)-777-3333 during duty hours and Hill AFB Command Post at (801)- 777-3007 after hours, within four (4) hour after initial notification of all mishaps or incidents for damage to DoD property (material plus labor) entrusted by this contract and employee injuries as a result of the contract operation. A follow-up (written or e-mail) of this mishap/incident notification shall be sent within three calendar days to the Government Representative, the PCO or the Administrative Contracting Officer (ACO) (with a copy to program manager), who will forward it to the Installation Safety Office. The information that is not available at the time of the initial notification shall be provided within 20 calendar days after the mishap. Mishap notification 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. Impound Authority Name and Phone Number (as applicable)

g. Nomenclature of equipment and personnel involved in accident/incident

h. Corrective actions (taken or proposed)

i. Other pertinent information

Note: If requested by Government Personnel (PCO/ACO), the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the investigating safety office. If the government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the government personnel until the investigation is finalized and closed out.

6. Impoundment Procedures: The contractor shall establish written impoundment procedures, as part of their Safety and Health Plan. Impound data must be included in the Mishap Notification Procedures as applicable. As a minimum, the procedures must address:

a. Appointment of Impound Authority in writing (copy faxed to QAP and Safety Office)

b. Impound Authority e-mail address and phone numbers

c. Specific instructions (cordon, facility locked facility, etc.) to secure the site or government asset, to prevent tampering with the aircraft, site or government assets

d. Specific instructions or measures to ensure only authorized personnel directly involved in management, SAFING, troubleshooting, or repair of aircraft or equipment gain access to the impound site

e. Additional guidance is located within AFI 21-101, AFMC Supplement 1

Appendix B – Sample T-2

TEMP_MOD_DIRECTI

VE_TEMPLATE_(5_Mar_13).doc