Atch_3_PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

FIELD LEVEL TECHNICAL AND ENGINEERING SUPPORT

23 February 2015

Prepared By:

A-10 Division

Air Force Life Cycle Management Center (AFLCMC)/WWA A-10 System Programs Office (SPO)

Hill AFB, Utah 84056

Revision Record

Rev Date Description Pages

Table of Contents

1.0 PROJECT OVERVIEW

2.0 APPLICABLE DOCUMENTS

3.0 CONTRACTOR REQUIREMENTS

4.0 PROGRAM MANAGEMENT (PM)

5.0 CONTRACTING AUTHORITY

6.0 SERVICE SUMMARY

7.0 TRAVEL

8.0 GFE LIST

9.0 SPECIAL CONSIDERATIONS

10.0 SUPPLY/SUPPORT REQUIREMENTS, DATA RIGHTS, DRAWINGS

11.0 CONTINUATION OF MISSION ESSENTIAL SERVICES DURING CRISIS

12.0 STAFFING AND QUALIFICATION REQUIREMENTS

13.0 PERIOD OF PERFORMANCE AND DELIVERY SCHEDULE

APPENDIX A – TRAVEL REQUEST FORM

APPENDIX C ‐ SAFETY

1.0 PROJECT OVERVIEW

1.1 SCOPE

The scope of this Performance Work Statement (PWS) shall provide engineering services of various task requirements for continued technical and engineering support toward the sustainment of all configurations of the A-10 and weapon system. This document identifies those tasks and activities required to fulfill this role. This requirement will be an Indefinite Delivery Indefinite Quantity (IDIQ) requirement with a five year ordering period.

1.2 BACKGROUND

The A-10 aircraft is an aging weapon system that is technically complex. As a result, field-level problems relating to engineering deficiencies are often generated, requesting engineering support. This requires system level assessment, sustainment evaluation, and problem resolution expertise beyond what is available in the A-10 System Program Office (SPO). Using commands (such as Air Combat Command, Air Force Reserve Command, and Air National Guard) depend on A-10 engineering to analyze any system deficiency, develop repair procedures, and recommend alternative solutions for operational and maintenance related support issues regarding aircraft systems, products, and materials in a timely manner. This effort includes evaluating and testing of aircraft systems to determine if problems exist that are due to aging, obsolescence, sustainment, bad maintenance practices, or component failure issues.

2.0 APPLICABLE DOCUMENTS

DOCUMENT NUMBER TITLE DATE

TO 00-25-107 Maintenance Assistance 15 Aug 2011 AFMC Manual 21-1 AFMC TO System Procedures 15 Jan 2005 AFI 31-101 Security Integrated Defense 5 Sep 2014

AFI 31-113 AFMC

Supplement

Security Installation Perimeter Access Control

26 Jan 2012

AFI 31-501 Personnel Security Program Management

27 Jan 2005

MIL-STD-1796A Avionics Integrity Program 13 Oct 2011 Technical Order Library A-10 Technical Orders Various dates 08-A10DOC-001 A-10 Drawing Practices 11 Aug 2008

3.0 CONTRACTOR REQUIREMENTS

3.1 Maintenance Engineering and Technical Support

The Contractor shall assess and resolve engineering disposition requests from the field or depot for technical assistance, including: engineering analysis/study, design solution, installation, repair/troubleshooting procedures, and validation of proposed corrective actions. This support is specifically for A-10 aircraft system/subsystem deficiencies, its support equipment, and all related technical data. This technical support includes a combined average of 300 phone calls, e-mails, and desk visits per month with some requests coming outside normal business hours. The contractor shall provide 24/7 technical support during emergency and urgent requests. The contractor’s technical expertise is principally focused on keeping every A-10 aircraft fully mission-capable each day and sustaining it until it is retired. This support will include assessing deficiency indicators and identifying and evaluating alternative solutions, including designing, integrating, and validating various solutions. This shall include ability to analyze various data (Hexadecimal, ASCII, Integer, Binary, and Northrop Floating Point) and convert to specific system performance characteristics for trouble shooting deficiencies. With approval, the Contractor shall travel to the location of field discrepancies to provide on-site analysis, evaluation, fault isolation, and recommended solutions to the local organization.

The Contractor shall have knowledge of the approved A-10C Mil-Std-1553B protocol and support equipment as well as standard Electrical Engineering lab equipment (multimeters, power supplies, oscilloscopes) to be used to analyze A/C deficiencies. The Contractor may be required to resolve A-10C aircraft discrepancies using troubleshooting methods outside of official AF Technical Orders.

The Contractor shall create a record of each TO 00-25-107, Air Force Material Command Form 202, AFTO 22/252, Product Improvement Working Groups (PIWG), Material Safety Task Groups, Safety Investigation analysis, evaluation, other projects, and disposition within the Government’s configuration database. (CDRL A002, A003, A004, and A005)

The Contractor shall follow Operational Safety Suitability and Effectiveness (OSS&E) policies and processes, the A-10 SPO policies, processes, A-10 Drawing Practices (document number:

08-A10DOC-001), Time Compliance Technical Order standards and regulations, and general Air Force Maintenance practices, procedures, and policies

The contractor shall provide technical engineering support on commodity/component failures, technical data deficiencies, on-site support, AFTO 22, technical meetings, design reviews, mishap/safety investigations, and OSS&E as described in sections 3.1.2-3.1.9.

Specifically, the Contractor shall be required to address and support any deficiencies in the following activities related to the A-10 Aircraft: Fire Control, Navigation, Communication, Datalink, Counter Measure, Engine, Electrical Power, Data Recording, Stores Management & Armament, Fuel Quantity Systems, Displays, Instruments &Lighting, Suite OFPs, and support equipment systems and tools.

- Fire Control systems, including (as a minimum):

o The Heads Up Display (HUD) o Low Alt Safety and Targeting Enhancement (LASTE)/Integrated Flight and

Fire Control Computer (IFFCC) system, o Central Air Data Computer o Stability Augmentation System o Combined Altitude RADAR Altimeter o Up Front Control o Pitot Static System o All instrumentation/displays, including (as a minimum):

• Attitude Direction Finding

• Horizontal Situational Indicator

• Accelerometer

• Vertical Velocity Indicator

• Airspeed Indicator

• Altimeter o Data/video recorder systems

- Navigation systems, including (as a minimum):

o Tactical Air Navigation System o Instrument Landing System o Heading/Attitude Reference System o Embedded Global Positioning System/Inertial Navigation System o Control Display Unit

- Communication Systems, including (as a minimum):

o AN/ARC-186(V) Very High Frequency(VHF)/Amplitude Modulation(AM) o AN/ARC-186(V) VHF/Frequency Modulation (FM) o AN/ARC-164(V) Ultra High Frequency(UHF)/Automatic Direction

Finder(ADF) o KY-58 Secure Speech System o AN/ARS-6(V) Lightweight Airborne Recovery System V12 with CSEL o Intercom o ARC-210 o Situational Awareness Data Link (SADL) o ARC-239 Systems

- Weapon Systems, including (as a minimum):

o Helmet Mounted Cueing System (HMCS)/Hybrid Optical-Based Inertial

Tracker (HOBIT) o Central Interface Control Unit (CICU) o Armament System o A/A49E-6 Internal Gun System o JDAM/LJDAM o APKWS o AIM 9 Missile Control System o Maverick

- Counter Measure Systems, including (as a minimum):

o The Electronic Warfare System o Chaff/Flare Dispensing System o AN/ALR-69 Radar Warning System o AN/AAR-47 Missile Warning System o ALQ-184 & 131 ECM pods o AN/ALQ-213 Electronic Countermeasures System o AN/ALR-46(V)-9 Radar Warning Receiver System o AN/ALE-47- Countermeasures Dispenser System

- TF34-GE-100 Turbofan Jet Engine, and all engine and aircraft monitoring systems as well as the support equipment & software tools, including (as a minimum):

o Turbine Engine Monitoring System (TEMS) and TF-34 Common Download Device (CDD) o TEMS/Air Data Recorder (ADR) and Windows TEMS/ADR Support Software (WINTASS) o Real Time Engine Data (RTED) and RTED Viewer o Aircraft Systems Information Support Tool (ASIST) o Improved Electronic Processor Unit (IEPU) o Engine gauges

- Stores Management System, including (as a minimum):

o Digital Video Airborne Data Recorder o Upgraded Data Transfer Unit o Scan Converter

- Fuel System, including (as a minimum):

o Fuel Quantity Indicator o Digital Fuel Quantity Indicator

3.1.1 Engineering Support Requests

Contractor shall resolve 107 & 202 Engineering Support requests, as required. Contractor shall initially respond to a field depot engineering support requests within the constraints specified in sections 3.1.1.1 and 3.1.1.2. Contractor shall expeditiously analyze the deficiency, respond, and address the course of action within the timeframe specified in sections 3.1.1.1 and 3.1.1.2 by analyzing potential solutions with recommended corrective action to A-10 Engineering and the requested customer. All analysis, associated data, and contractor recommendations shall be presented in a technical report for each engineering disposition. The goal is to return an aircraft and the faulty system or subsystem to full mission-capable status as soon as possible. The Contractor shall keep the Government engineer informed of the status of the deficiency and of all potential solutions as specified in sections 3.1.1.1 and 3.1.1.2 (CDRL A002, A003, A004, A005).

3.1.1.1 AFMC Form 107 Requests

The contractor shall coordinate 107 requests IAW TO 00-25-107 except as stated in sections

3.1.1.1.1 & 3.1.1.1.2. The amount of 107 support requests and the degree of difficulty of each request may vary. Historically, with the current effort, seventy-eight (78) 107 support requests were handled in the first year, one-hundred (100) in the second year, fifty-one (51) in the third year, and fifty-eight (58) in the fourth year, all with varying degrees of difficulty.

3.1.1.1.1 Within four hours of receipt of a deficiency report for an emergency field condition the Contractor shall contact the deficiency initiator and identify the individual responsible for analyzing the engineering disposition request. The Contractor shall respond and address the course of action within 24 hours by reviewing associated failure data, designing repair solutions for corrective action, developing validation procedures, and including all associated documentation in a technical report. (CDRL A002, A003, A004, A005)

3.1.1.1.2 Within one business day of receipt of a deficiency report for a non-emergency field condition the Contractor shall contact the deficiency initiator to identify the individual responsible for analyzing the engineering disposition request. The Contractor shall respond and address the course of action within three business days by reviewing the associated data, designing repair solutions for corrective action, and developing validation procedures, including all associated documentation in a technical report. (CDRL A002, A003, A004, A005)

3.1.1.2 AFMC Form 202 Requests

The contractor shall coordinate 202 requests IAW AFMC Manual 21-1 except as stated in sections 3.1.1.2.1 & 3.1.1.2.2. The amount of 202 support requests and the degree of difficulty of each request may vary. Historically, with the current effort, thirteen (13) 202 support requests were handled in the first year, three (3) in the second year, forty-seven (47) in the third year, and fifty-one (51) in the fourth year, all with varying degrees of difficulty.

3.1.1.2.1 Within two hours of receipt of a request for assistance on a work stoppage condition the Contractor shall contact the initiator to identify the individual responsible for analyzing the engineering disposition request. The Contractor shall respond and address the course of action within 24 hours by reviewing associated failure data, designing repair solutions for corrective action, developing validation procedures, and including all associated documentation in a technical report. (CDRL A002, A003, A004, A005)

3.1.1.2.2 Within three business days of receipt of a request for assistance on a non-work stoppage condition the Contractor shall contact the initiator to identify the individual responsible for analyzing the engineering disposition request. The Contractor shall respond and address the course of action within five business days by reviewing associated failure data, designing repair solutions for corrective action, developing validation procedures, and including all associated documentation in a technical report. (CDRL A002, A003, A004, A005)

3.1.2 Avionics and Mechanical Sub-System Commodity/Component Failures

The Contractor shall conduct up to 50 analyses as required for avionics and mechanical sub-system commodity/component failures. If during an analysis the Contractor determines that the aircraft deficiencies are related to a subsystem failure within an existing avionics or mechanical system, the Contractor shall notify the applicable commodity owner within two weeks from discovery. After the failure analysis, the Contractor shall make a recommendation to A-10 Engineering within three weeks regarding the analysis and testing performed by the Contractor.

If Government engineering requests further contractor support, the Contractor shall assess whether the issue is a problem that can be resolved with repair and/or component replacement within four weeks. If the Contractor can identify a more robust design solution, this recommendation shall be included in the technical report within six weeks. (CDRL A002, A003, A004, A005)

3.1.3 Technical Data Deficiencies

The Contractor shall provide recommended solutions for up to 300 deficiencies as required to correct, improve, and sustain aircraft documentation within four weeks of deficiencies identified in technical data (such as engineering drawings and Technical Orders). As required, the Contractor shall develop corrected technical data for inclusion in engineering orders (EOs) and Technical Orders (T.O.s) to improve and document the technical data for publication within six weeks. The Contractor shall comply with aircraft maintenance and operation safety restrictions imposed by the T.O.s and local organizational policies. (CDRL A002, A004, A005)

3.1.4 AFTO 22/252

The Contractor shall provide engineering support for up to 30 Air Force Technical Order Forms 22/252 as required, submitted by the Technical Content Manager (TCM) for analysis and approval. (CDRL A002, A004, A005)

3.1.5 Technical Meeting Support

The Contractor shall participate in user technical support forums as required, such as PIWG, In Progress Review (IPR), Aircraft System Requirement Review Conference (ASRRC), and Material Safety Task Groups. The Contractor shall investigate and provide, by the due date defined in technical support forums, recommended disposition for up to 50 action items as required, arising from these forums. (CDRL A002, A003, A004, A005)

3.1.6 Design Review

The Contractor shall analyze up to 50 proposed design changes to improve A-10 sustainment and operational issues as required. The Contractor shall identify both positive and potential negative impacts to the field’s ability to maintain the weapon systems that are generated by these design changes and provide recommendations by the due date. (CDRL A002, A003, A004, A005)

3.1.7 Mishap/Safety Investigations

The Contractor shall support mishap/safety investigations as required to determine its cause and analyze action items and recommendations generated by the mishap investigation board. (CDRL A002)

4.0 PROGRAM MANAGEMENT (PM)

4.1 The Government PM for this delivery order is within the A-10 SPO. The PM will coordinate with the Government contracting office and Contractor Program office regarding administrative matters relative to this task.

4.2 The Contractor shall designate a PM to integrate overall task performance through effective and efficient planning. The Contractor shall be responsible for the overall schedule and resources management for the accomplishment those tasks identified by the Government under this performance work statement.

4.2.1 Program Management Reviews. The Contractor shall arrange and attend meetings to support various related tasks, as determined by the Government. The Contractor shall include any significant issues from these meetings in the Monthly Status Report (MSR) (CDRL A001).

4.2.2 Monthly Status Report. The Contractor shall provide a MSR that, at a minimum, shall include a monthly status summary, open correspondence issues, contractor travel projections, and contract fund status. (CDRL A001)

4.2.3 Task Status. Each month, the Contractor shall summarize the status of each task, the activities completed during the previous month, the tasks started and those in progress, and the tasks to be started in the following month. Any project or task issues or concerns that may impact performance or schedule shall also be identified, along with recommended corrective action(s). (CDRL A001 & CDRL A002)

5.0 CONTRACTING AUTHORITY

The Procuring Contract Officer (PCO) is responsible for management of this contract. Only the PCO can make changes affecting the contract. Any instances where implied or explicit direction is received from any Government representative other than the PCO, and perceived by the Contractor to affect performance of tasks under this contract, or to have a material impact on costs incurred in association with this contract, shall be brought to the immediate attention of the PCO for disposition and direction before proceeding with any work thus affected.

5.1 CONTRACTOR MANPOWER

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the A-10 via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. 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 reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

*Reporting Period: Contractors are required to input data by 31 October of each year.

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

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.0 SERVICE SUMMARY

Performance Objective PWS Para. Performance Threshold Method of

Surveillance Quality of Resolution of TO 00-25-107 and Form 202 Problems; Contractor’s technical approach and solution must be safe, suitable, and effective.

3.1 90% of the problem solutions provided to the initiating organization shall be accurate, timely, and satisfactory. 95% of the problem solutions tendered shall be safe to operators, maintainers, and the overall weapon system. Any errors found shall be corrected within 7 days without cost to the Government

Periodic (Quarterly)

Speed of response to 107 requests

3.1.1.1 Initiator shall be contacted within 4

hours of receipt for emergency 107 requests and within 1 business day for non-emergency 107 requests with no more than 2 customer complaints per quarter

Customer complaint, 100% inspection

Speed of response to 202 requests

3.1.1.2 Initiator shall be contacted within 2

hours for work-stoppage 202 requests and within 3 business days for non-work-stoppage 202 requests with no more than 2 customer complaints per quarter.

Customer complaint, 100% inspection

Quality of data products:

Contractor must submit complete and accurate data/technical reports in accordance with the CDRL A002

3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.2, 3.1.1.2.2, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 4.2.1

90% of data products must meet contract requirements upon initial submission.

No more than 10% of technical reports/data products shall be submitted late.

Periodic (Quarterly)

Product Drawings/ Models & Associated Lists CDRL A005

3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.2, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6

Submitted on time 100%. Any errors found shall be corrected within 7 days without cost to the Government.

100% inspection

Test Plan CDRL A003

3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.2, 3.1.2, 3.1.5, 3.1.6

Submitted on time 100%. Any errors found shall be corrected within 7 days without cost to the Government.

100% inspection

Contractor Progress – Monthly Status Reports

CDRL A001

4.2.1, 4.2.2, 4.2.3, 7.0

Submitted on time 98% of the time according to the DD Form 1423

100% inspection

7.0 TRAVEL

Historically, the average amount of contractor (temporary duty) TDYs per year has been 13;

however, the exact amount of TDYs required per year is not known due to unknown future workload requirements. The Contractor may be required to travel in support of all activities listed in section 3. Travel will be required when all other forms of technical support (email, phone, etc.) have been exhausted and a solution has not been determined. When the Contractor determines that travel is required, the Contractor shall get concurrence with the lead SPO engineer.

When travel is required, the Contractor shall submit a Travel Request Form (see Appendix A) and submit the form to the Government Program Manager. Contractor travel shall be approved in writing (or via e-mail) by the Government Program Manager and authorized by the Government Contracting Officer. The Contractor shall document all travel in the form of a Trip Report and delivered to the Government Program Manager as an attachment to the MSR. Airfare for travel and per diem shall be billed IAW Federal Travel Regulations (FTR) and FAR 31.205-

46. The Contractor is responsible for making all necessary travel arrangements. (CDRL A001)

The Contractor shall submit a projection in the MSR for the anticipated travel requirements for the next 30 days (succeeding month). The Contractor shall summarize funds expended to date and funds remaining on a monthly basis for any cost reimbursable items as part of the MSR

(CDRL A001)

8.0 GFE List

ITEM # NSN NOUN PART # QUANTITY SERIAL # CPIN #

001 N/A Improved

Ethernet Processor Unit

(IEPU)

200222868-50 1 045 N/A

002 N/A ASIST 17838-SW-

001d

1 N/A 88T-

A10C/ASI

ST-S001-

00A

9.0 SPECIAL CONSIDERATIONS

9.1 When work under this contract requires unescorted entry into controlled or restricted areas, the Contractor shall comply with AFI 31-101 and AFI 31-113, Installation Security, and AFI 31-501, Personnel Security Program Management, Hill AFB Supplement. Upon completion or termination of the contract or expiration of the identification passes, the Contractor shall ensure that all base identification passes issued to employees are returned to the issuing office.

9.2 Contractor personnel requiring access to any Air Force Base or computer network to accomplish the requirements of this contract shall have in place the following prior to receiving such access:

9.2.1 Hill Air Force Base (HAFB) contractor personnel requiring IT-III level access to a Government computer will need at least a National Agency Check plus Written Inquiries and Credit Checks (NACI) or higher investigation IAW AFI 31-501 Personnel Security Program Management, Hill AFB Supplement 2.4.3.1.

9.2.2 Completion of Network User Licensing Computer Based Training (CBT), AFI 33-115 Volume 2, Paragraph 4.1.

9.2.3 The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor personnel shall abide by all Government rules, procedures, and standard of conduct.

9.3 The Contractor shall report in a timely manner to the appropriate security manager and Functional System Administrator those personnel who no longer require network access.

9.4 Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the A-10 SPO PCO.

9.5 Some tasks that are to be completed at Temporary Duty locations may require a SECRET clearance using a DD Form 254.

9.6 See Appendix C for Safety, Fire Protection, and Health Specification Industrial Safety Requirements.

10.0 SUPPLY/SUPPORT REQUIREMENTS, DATA RIGHTS, DRAWINGS

All data produced by the Contractor in support of these tasks shall be non-proprietary and shall be available without limitation to the Government. All products developed under this contract shall be considered Government work and shall have no license encumbrances. The Government will receive unlimited/unrestricted rights to all data developed under this contract IAW DFARS 252.227-7013.

10.1 All data generated under the tasks defined within this PWS or any subsequent task order shall be developed for the A-10 aircraft at U.S. Government expense and the U.S. Government shall have unlimited rights in all such data as defined in DFARS 227.7103-5 and DFARS 252.227-7013(a)(15). And despite DFARS 252.227-7013(f), all such documents shall be marked 'unlimited rights' as follows:

UNLIMITED RIGHTS

Contract No.

Contractor Name Contractor Address

The Government's rights to use, modify, reproduce, release, perform, display, or disclose these technical data are unlimited. No restrictions apply.

11.0 CONTINUATION OF MISSION ESSENTIAL SERVICES DURING CRISIS

All Services performed under this PWS are not considered mission essential during crisis situations.

12.0 STAFFING AND QUALIFICATION REQUIREMENTS

As required, the Government will provide office space and computers for contractor support.

13.0 PERIOD OF PERFORMANCE AND DELIVERY SCHEDULE

13.1 Location

Work will be required at Hill AFB and at various active duty, guard and reserve A-10 bases, and other locations within the continental United States, as requested by the A-10 SPO.

13.2 Period of Performance (PoP)

This is an ID/IQ for a 5-year ordering period and a 6-month optional ordering period. PoP will begin fourteen (14) calendar days after the effective date of award. Each order is anticipated to last 12 months. The anticipated date of award is June 2015.

13.3 Transition Period

A transition period not to exceed fourteen (14) business days will be authorized to allow the Contractor to establish operational capabilities, which includes manpower and other required resources.

13.4 Contract Data Requirements List (CDRL) Deliverables

The Contractor shall prepare and deliver data IAW references in earlier sections. All Data Item Descriptions (DID) in the CDRL, as contained in the following table, shall be used as guides in developing the data. Distribution and Number of Copies: all CDRL items shall be delivered to the Government IAW the CDRL, and a cover letter paper submittal shall be provided to the Government's Contracting Officer identifying the data item and 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 PM and the PCO.

Distro-Stmt CDRL Description Data Item Description PWS Para Reference(s) D A001 Contractor Progress, Monthly

Status Report DI-MGMT-80227 Error! Reference source not found., 4.2.2, 4.2.3, Error! Reference source not found.

D A002 Technical Report – Study/Services DI-MISC-80508B 3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.23.1.1.2.2, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 4.2.1

D A003 Test Plan DI-NDTI-80566A 3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.2, 3.1.2, 3.1.5, 3.1.6

D A004 Temporary Non-Standard Modification Documentation and Marking Requirements

DI-MISC-81562 3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2,

3.1.1.2.1, 3.1.1.2.2, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6

D A005 Product Drawings/Models & Associated Lists

DI-SESS-81000E 3.1, 3.1.1, 3.1.1.1, 3.1.1.1.2,

3.1.1.2.1, 3.1.1.2.2, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6

Appendix A: Travel Request Form

Appendix C – 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. 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 (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 Procurement Contracting Officer (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 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. The Contractor shall coordinate with the hosting unit to properly handle personal injury, lost tools/equipment, or the aircraft mishap process.