FINAL_PWS.pdf

FILE NUMBER: FD2060-12-32670/REVISION 0� ������

PERFORMANCE-BASED WORK STATEMENT (PWS)

For

ROYAL SAUDI AIR FORCE (RSAF) F-15C/D/S/SA AIRCRAFT

STRUCTURAL INTEGRITY PROGRAM (ASIP) FATIGUE

DAMAGE TRACKING (FDT) TASK

April 04, 2012

DISTRIBUTION CODE D: Distribution authorized to Department of Defense and DOD Contractors only, other requests shall be referred to

WR-ALC/GRMIA or higher DOD authority. Export controlled.

Prepared: WR-ALC/GRMIA F-15 Logistics Branch Robins AFB GA 31098

By: Angela Burks/ Program Manager

1.0 DESCRIPTION OF SERVICES.

1.1 Background:

1.1.1 Under Aeronautical Systems Center (ASC) contract F33657- 77-C-0200, McDonnell Douglas Corporation (MDC) performed a F-15A/B/C/D Damage Tolerance Assessment (DTA), developed an individual aircraft Fatigue Damage Tracking (FDT) system based on crack growth methodology, processed the usage data backlog, and, in October 1983, delivered the first F- 15A/B/C/D Service Aircraft Fatigue Estimate (SAFE) report based on crack growth. Shortly thereafter, in December 1983, the first RSAF F-15C/D SAFE report based on crack growth was delivered to the Royal Saudi Air Force (RSAF). Individual aircraft FDT of the RSAF F-15C/D fleet has been conducted ever since under a series of Technical Support Program (TSP) contracts between Warner Robins-Air Logistics Center (WR-ALC) and McDonnell Douglas Services (MDS), the latest of which was TSP IV [contract F09603-97-C-0268, Contract Line Item Number (CLIN) 0098], which expired in December 1999. RSAF F-15S usage data processing was also started under TSP IV. Implementation of a new UNIX/Oracle version of the RSAF F- 15C/D/S FDT system was accomplished at Boeing/MDC under contract F09603-99-G-0008- 0004-04.

1.1.2 Boeing/MDC accomplishes the FDT task using F-15 Signal Data Recorder Set (SDRS) and Standard Flight Data Recorder (SFDR). Data is provided by the RSAF through Oklahoma City- Air Logistics Center (OC-ALC) including Air Force Technical Order (AFTO) Form 239 Flight Log and Exceedance Counter Data Recorder, AFTO Form 238 Component Serialization Record, and AFTO Form 3 Inspection Tracking Record [United States Air Force (USAF) only in the past.]. Structural repair data and flight hour accumulation data is provided by the RSAF through WR-ALC on RSAF Form 1400-6, Monthly Maintenance Report Aircraft Accountability Summary. The OC-ALC data processing effort is accomplished using the Operational Fatigue Loads Computer Program (OFLCP) and associated databases provided/maintained by Boeing/MDC. The WR-ALC data processing effort is accomplished using the Web-based Service Aircraft Estimate (WEBSAFE) software and associated databases provided/maintained by Boeing/MDC. The Boeing/MDC data processing effort is accomplished using the Individual Aircraft Tracking Program (IATP) and associated databases developed/maintained by Boeing/MDC. The breakdown of responsibilities between the RSAF, USAF Air Force Logistic Commands (AFLCs), and Boeing/MDC is documented in the Peace Sun Aircraft Structural Integrity Program (ASIP) Plan, dated 2 March 2004 and delivered under Department of Defense (DD) Form 1423-1, Contract Data Requirements List (CDRL) Seq. No. A031 of contract F33657-01-D-0026-RJ13. The latest delivered CDRL is under Seq. No. A031 of contract F33657-01-D- 0026-RJ49, RJ57 and RJ65.

FILE NUMBER: FD2060-12-32670/REVISION 0� �����

1.1.3 Effective 1 January 2000, the contract vehicle for the RSAF F-15 individual aircraft FDT effort accomplished by MDC will be the Contract Engineering Task (CET) rather than the TSP vehicle used in the past. Boeing/MDC’s CY05-06 RSAF F-15C/D/S individual aircraft FDT effort, including Boeing/MDC’s maintenance of the required FDT software/databases in use at Boeing/MDC, King Adul Aziz Air Base /Aeronautical Engineering Squadron (KAAB/AES), OC-ALC, and WR-ALC, shall be covered by this CET.

1.2 Objective: The purpose of the ASIP is to maintain the structural health of the RSAF F-15 aircraft with the ultimate goal being fewer aircraft inspections, less maintenance, and reduced support costs while protecting structural integrity. This objective shall be achieved through the use of an individual aircraft FDT system based on crack growth methodology. The tools the Contractor should use include FDT analysis, data processing and other devices. The results and conclusions shall be delivered to the customer in the form of periodic reports and updates to those reports in a digital format.

2.0 SERVICES SUMMARY (SS).

2.1 The Contractor shall update the Peace Sun ASIP Plan as required. Reference CDRL A031 and document DI-MGMT-81384/T. The Contractor shall also update the FDT system, at a minimum monthly, through data processing and analysis in the FDT database and provide customer feedback, at a minimum, every two months via a Bimonthly Status Report and the Usage Data Feedback Report. (A031, DI-MGMT-81384/T) The Contractor shall also conduct all data processing required for preparation of the SAFE reports, and prepare the semiannual SAFE reports according to CDRL A028 and document number DI-MISC-80508/T including updated recommendations for hourly inspections.

2.2 Data processing shall include:

- AFTO Form 3 data processing including database incorporation of repairs affecting tracked locations

- AFTO Form 239 data processing

- F-15S SFDR data processing

- Monthly update of the flight hour accumulation Maintenance Aircraft Report Accountability Summary (RSAF Form 1300-6) database

- Database incorporation of aircraft status and base assignment changes

- Database incorporation of wing and vertical tail changes (AFTO Form 238)

- Database incorporation of new aircraft/spare components upon delivery

- IATP data processing and associated database maintenance

A waiver must be approved by the Contracting Officer’s Representatives [COR(s)] for a late input that would impact submission of reports.

2.3 The Contractor shall perform the tasks listed below based upon the priorities established by the F-15 Logistics Branch Chief.

FILE NUMBER: FD2060-12-32670/REVISION 0� �����

Performance Objective PWS Reference Performance Threshold

Provide responsive service to support customers.

4.1-4.2 The Contractor shall provide the U.S. Government rapid response to all requests for assistance within a two business day window. This includes questions via e-mail or telephone.

Update FDT system. 2.1, 2.2, 4.2.2.1, 4.2.2.2 The Contractor shall update the FDT system, at a minimum, monthly through data processing and analysis in the FDT database. Data processing shall include, at a minimum, inputs/updates identified in paragraphs 2.2 and 4.2.2.1. A waiver must be approved for a late input.

Provide delivery of Bimonthly Status Reports.

2.1, 4.3.4 The Contractor shall submit status reports, at a minimum, every two months with no more than one report per contract PoP requiring revision. Report requiring revision shall be revised within two business days.

Prepare Semiannual SAFE Reports.

2.1, 2.2, 4.2.2.1, 4.2.2.4, 4.3.3 Data processing for SAFE Reports shall include, at a minimum, inputs/updates identified in paragraphs 2.2 and 4.2.2.1. A waiver must be approved for a late input.

SAFE Reports shall include, at a minimum, data in paragraph 4.3.3.

Provide delivery of Semiannual SAFE Reports.

2.1, 4.2.2.4, 4.4 The Contractor shall submit SAFE Reports semiannually. T.O.

1F-15A/E-6 SAFE Report - F- 15C/D/S/SA is due by 183, 365 calendar days after the BOPOP.

Report requiring revision shall be revised within two business days.

3.0 UNITED STATES (U.S.) GOVERNMENT PROPERTY AND SERVICES.

3.1 U.S. Government-Furnished Property (GFP) is not authorized. The data will be provided to the Contractor on a disk.

3.2 OC-ALC will provide SFDR data output from the OFLCP quarterly, but in time to support the six month SAFE processing cycle as determined by Boeing/MDC and coordinated with OC- ALC. The U.S. Government retains ownership of the data once the contract is over.

3.3 All material generated under the contract becomes the property of the U.S. Government and shall be returned to the U.S. Government upon completion of the contract or as directed by WR- ALC/GRMIA. CDRL deliverables become the property of the U.S. Government upon receipt.

3.4 U.S. Government Systems: The U.S. Government will provide Contractor personnel access to systems necessary to perform tasks under the contract. The Contractor shall ensure Contractor personnel who require access to a U.S. Government Automated Information System (AIS) have a Department of Defense (DoD) National Agency Check Plus Written Inquiries (DNACI) conducted in accordance with DoD 5200.2-R, Personnel Security Program. The U.S.

Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract or transfer/termination of Contractor personnel, the system account will be closed.

3.5 Wide Area Workflow (WAWF): In accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests, the Contractor shall submit/process payment requests (invoices, Receiving Reports or combos), Receipt/Acceptance documents, and CDRL, deliverables via WAWF. Contractor personnel shall register to access Wide Area Workflow-Receipt and Acceptance (WAWF-RA) at https://wawf.eb.mil and designate an Electronic Business Point of Contact (EB POC) in the Central Contractor Registration (CCR) site at http://www.ccr.gov within ten calendar days after award of the contract.

4.0 GENERAL INFORMATION.

4.1 ASIP Services Required:

4.1.1 The Contractor shall review the latest revisions of the F-15 ASIP Plans to determine the necessary sections to be updated. The Contractor shall provide to the U.S. Government a rapid response to all requests for assistance within a two business day window. This includes questions via email or telephone.

4.1.2 The Contractor shall gather the necessary information from all Boeing/MDC and U.S.

Government sources required to provide an accurate account of the major historical and future events during the life of the F-15 aircraft. This data gathering shall include up to two technical conferences or meetings with USAF/WR-ALC/GRMI personnel which must be approved in advance by the Procuring Contracting Officer (PCO).

4.1.3 The Contractor shall make a list of all the information gathered and will prioritize this list of data with the ASIP manager at WR-ALC/GRMIA. Additional items that arise during the contract Period of Performance (PoP) will also be prioritized with the ASIP manager. (DI-

MISC-81384/T)

4.1.4 The Contractor shall review major structural problems/actions taken as provided to the Contractor, and make recommendations for the future structural repairs or modifications which are required to continue the operational readiness of the F-15.

4.1.5 The Contractor shall review all aspects of the ASIP of the F-15 as defined in Air Force Instruction (AFI) 63-1001, Aircraft Structural Integrity Program. This review shall include evaluation of the individual programs that make up the overall ASIP. Each program area shall be evaluated and have recommendations made to improve the overall effectiveness of the aircraft and to improve these programs. These programs include, but are not limited to, Durability and Damage Tolerance Analysis (DADTA), the Individual Aircraft Tracking (IAT) program, the Loads/Environment Spectra Survey (L/ESS), maintenance data collecting and reporting. (DI-

MISC-81384/T)

4.1.6 The Contractor is encouraged to deliver all data electronically and in the most cost effective media possible, such as CD-ROM, web pages, etc. If required, the Contractor’s electronic submission shall be in accordance with the American National Standards Institute (ANSI) Accredited Standards Committee (ASC) x 12 Electronic Data Interchange (EDI) Standards.

4.1.7 The Contractor shall support up to two meetings with WR-ALC/GRMIA personnel for the purposes of providing additional guidance on how to perform the ASIP for the RSAF F-15 updates to compliment the Contractor effort.

4.1.8 The Contractor shall support up to two meetings with WR-ALC/GRMIA personnel for the purposes of providing a semi-annual review on the current state of the F-15 ASIP contract and obtaining additional guidance and direction on continued ASIP performance.

4.2 FDT Objectives and Services Required:

4.2.1 Objectives:

4.2.1.1 The Contractor shall continue to complete updates and assist WR-ALC/GRMIA with any FDT-related task.

4.2.2 Services Required:

4.2.2.1 The Contractor shall conduct all data processing required for preparation of the SAFE reports and Technical Order (T.O.) 1F-15A/E-6 IAT inspection requirements updates. Data processing shall include:

- Inspection feedback (AFTO Forms 3 and 95) data processing including database incorporation of repairs affecting tracked locations

- AFTO Form 239 data processing using the fully automated Flight Log and Exceedance Counter data record (FLEC)-II process developed under contract F33657-01-D-0026-RJ33

- SFDR Operational Fatigue Loads Computer Program (OFLCP) output data processing

- Semiannual update of AFTO Form 239 Recording Rates in the SAFE Report

- Monthly update of SFDR Recording Rates database

- Database incorporation of aircraft status and base assignment changes and preparation/distribution of the Aircraft Inactive Status Report as changes occur

- Database incorporation of wing and vertical tail component changes

- IATP workflow processing

- Projection of IAT inspection requirements

A waiver must be approved by the COR(s) for a late input that would impact submission of reports.

4.2.2.2 FDT Database: The Contractor shall maintain an FDT database. The database shall be easily accessible to WR-ALC/GRMIA. The database shall be updated, at a minimum, monthly.

The Contractor shall collate Contractor and U.S. Government data, including FDT data, and provide compilation to WR-ALC/GRMEC. The Contractor shall support the generation of new Microsoft Office reports and graphs based on information in the FDT database.

4.2.2.3 The Contractor shall support up to two conferences or meetings with USAF personnel which must be approved in advance by the PCO. At the completion of this task, all software

FILE NUMBER: FD2060-12-32670/REVISION 0� �����

updates shall be summarized in the Final Engineering Report. Boeing/MDC shall deliver to the USAF the source code, compiled binary executable files, and a user’s manual to all software updates made to OFLCP. The source code shall be produced in a clear, professional manner to facilitate future development by the USAF. (DI-MISC-81384/T)

4.2.2.4 The Contractor shall prepare and submit the F-15C/D/S SAFE report (by electronic means, either mailed on CD/DVD or via a secure, access-controlled website) and T.O. 1F- 15A/E-6 IAT Inspection Requirements updates semiannually based on the fatigue damage calculations and RSAF damage rates. Any report requiring revision shall be revised within two business days. (DI-MISC-80508)

4.2.2.5 The Contractor shall update the FDT system, i.e., the tracked locations and the associated programs, and maintain the system at a level in-line with other F-15 customer systems. The Contractor shall provide a summary of these changes in the Final Engineering Report. The Contractor shall provide the U.S. Government rapid response to all requests for assistance within a two business day window. This includes questions via email or telephone. (DI-MISC- 81384/T)

4.3 Reports and Technical Data: The Contractor shall submit the following reports and technical data. Data submittals shall be provided electronically if possible.

4.3.1 Contract Funds Status Report - This report shall be provided for the travel CLIN. It should contain contract number, contract type, and contract funding type such as multi-year procurement, incrementally funded contract, or contract for a single year or fiscal year.

4.3.2 Service Engineering Reports:

4.3.2.1 Service Engineering Reports / Interim Engineering Report - The Interim Engineering Report shall be submitted concurrent with computer software delivery and installation. (DI-

MISC-81384/T)

4.3.2.2 Service Engineering Report / Final Engineering Report - This report shall consist of a brief description of the changes to the Fatigue Tracking System and the databases. (DI-MISC- 81383/T)

4.3.3 Service Life Analysis and Parametric Calculations of Fatigue Damage Report / SAFE Report - The following information shall be provided in the SAFE Report via CD/DVD. (DI

MISC 80508)

4.3.3.1 Damage index figures shall be reported on each and every operational aircraft by tail number. Additionally, the report shall estimate the point at which fatigue damage will require inspections to be performed to ensure safe operational usage of the aircraft. Extrapolation shall be made based upon the most recent calculated damage rate. The report shall also show the average rate of damage for the most critical location for each type of mission. (DI MISC 80508)

4.3.3.2 Service aircraft fatigue estimates shall cover specific fatigue critical locations on all major airframe assemblies. (DI MISC 80508)

4.3.3.3 If a revision in the methodology to calculate damage indices occurs, all accumulated damage figures issued in reports after the revision shall reflect the effects of this revision. The damage figures shown in subsequent reports shall be based on the revised methodology for all previous service usage, as well as, current usage. (DI MISC 80508)

4.3.3.4 In conjunction with the production of these reports, the Contractor shall maintain, for the record, the stress time history files from which the SAFE report data were derived. (DI MISC 80508)

4.3.3.5 The SAFE report and/or CD/DVD/web-access of FDT database on-demand query/reporting functionality shall provide the following figures and tables at a minimum:

4.3.3.5.1 Flight Hour Distribution based on Counting/Accelerometer (C/A) data.

4.3.3.5.2 Flight Hour Summary figures by mission type based on C/A data from the four most recent quarters with Conformal Fuel Tanks (CFTs) and without CFTs.

4.3.3.5.3 Flight Summary figures by mission type based on C/A data from the four most recent quarters with CFTs and without CFTs.

4.3.3.5.4 Distribution of F-15 Expended Crack Growth Life figure based on C/A data.

4.3.3.5.5 Figure of AFTO Form 239 versus flight hour reporting data.

4.3.3.5.6 Figure of the AFTO Form 239 Recording Rates.

4.3.3.5.7 Figure of the F-15 Standard Data Recorder (SDR) Recording Rate.

4.3.3.5.8 Tables of F-15 Usage Summary by mission type for current reporting period and cumulative to date based on SDR data and based on C/A data.

4.3.3.5.9 Tracked locations summary tables.

4.3.3.5.10 Transfer locations and constants tables.

4.3.3.5.11 Summary of Average Damage per 1000 Flight Hours tables for Direct Locations for F-15 Usage with CFTs, current reporting period and cumulative to date, and without CFTs, current reporting period and cumulative to date.

4.3.3.5.12 Fleet Summary of Damage Indices for Individual F-15 Aircraft tables.

4.3.3.5.13 Summary of Damage Indices for Individual F-15 Aircraft Grouped by Wing tables.

4.3.3.5.14 Summary of Maximum Damage Indices at Selected Locations tables.

4.3.3.5.15 Number of Aircraft Requiring Inspections by Locations table.

4.3.4 Bimonthly Status Reports: The Contractor shall submit status reports, at a minimum, every two months with no more than one report per contract PoP requiring revision. Report requiring revision shall be revised within two business days.

4.4 ASIP Completion Dates: The following dates are the milestones for accomplishment of this task and shall be due based on the contract Beginning of Period of Performance (BOPOP):

Deliverable: Update Frequency:

- Monthly Status Letters 60 Calendar Days BOPOP/Monthly

- Contract Funds Status Report (Travel CLIN) 90 Calendar Days BOPOP/Quarterly

- Interim Engineering Reports As Required

- Final Engineering Report 183 Calendar Days BOPOP

- SAFE Report (via electronic means 183, 365 Calendar Days BOPOP with supporting data) - F-15C/D/S/SA

4.5 Ceiling Price: The ceiling price shall not be exceeded, except at the Contractor's risk, unless and until the Contractor has notified the PCO through the Administrative Contract Officer (ACO), in writing, of the additional funds required with adequate justification and the PCO has notified the Contractor, in writing, that the ceiling price has been increased.

4.6 Organization(s): WR-ALC/GRMIA

4.7 U.S. Government Security Requirements:

4.7.1 U.S. Government Security Regulations: The Contractor shall ensure personnel, information, system, facility, and international security requirements are met in accordance with DoD 5200.22-M, National Industrial Security Program Operating Manual (NISPOM), DoD 5200.2-R, AFI 31-101, Integrated Defense, and Robins Air Force Base Instruction (RAFBI) 31- 101, Installation Security.

4.7.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. Critical information is defined as information about USAF missions or activities the adversary needs to achieve their goals. The Contractor shall ensure compliance with OPSEC requirements including procedures to protect classified and/or sensitive, but unclassified, U.S. Government projects and/or programs. The Contractor shall ensure Contractor personnel who perform work on Robins Air Force Base (AFB) or another U.S. Government facility comply with the OPSEC procedures of the facility.

4.7.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified and/or sensitive, but unclassified, information in accordance with DoD 5200.22-M.

4.7.4 Security Clearance: Contractor personnel are not required to have a security clearance.

Contractor personnel shall not be authorized access to classified and/or sensitive, but unclassified, information and materials or be permitted to work on classified and/or sensitive, but unclassified, projects and/or programs without proper security clearances and a need-to-know.

4.7.5 Access to U.S. Government System: The U.S. Government will provide Contractor personnel access to systems necessary to perform tasks under the contract. The Contractor shall ensure that Contractor personnel who require access to a U.S. Government AIS have a DNACI conducted in accordance with DoD 5200.2-R. The U.S. Government will provide system access subject to approval of the DD Form 2875. Upon completion/termination of the contract or transfer/termination of Contractor personnel, the system account will be closed.

4.7.6 Access to U.S. Government Facility: The Contractor shall ensure Contractor personnel who require access to Robins AFB or another U.S. Government facility comply with the security procedures of the facility. If Contractor personnel require repeated access to Robins AFB or another U.S. Government facility over the life of the contract, the Contractor shall ensure they complete, as applicable, a DD Form 1172-2 (Application for Department of Defense Common

FILE NUMBER: FD2060-12-32670/REVISION 0� �������

Access Card – DEERS Enrollment) to obtain a Common Access Card (CAC) or an Air Force Materiel Command (AFMC) Form 496 (Application for AFMC Identification Card) to obtain a Contractor identification card. The DD Form 1172-2 or AFMC Form 496 shall be submitted to the PCO. Upon completion/termination of the contract/order or transfer/termination of the Contractor personnel, the CAC or Contractor identification card/badge shall be returned to the

PCO.

4.7.7 Security Incident or Violation: The Contractor shall immediately notify the U.S.

Government Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified and/or sensitive, but unclassified, information.

4.8 Continuation of Mission-Essential Services During a Crisis:

4.8.1 Definition of Mission-Essential Services: In accordance with DFARS 252.237-7023(a), Continuation of Essential Contractor Services / Definitions, “‘Essential contractor service’ means a service provided by a firm or individual under contract to DoD to support mission-essential functions, such as support of vital systems, … associated support activities, … and similar services provided to foreign military sales [FMS] customers under the Security Assistance Program. Services are essential if the effectiveness of defense systems or operations has the potential to be seriously impaired by the interruption of these services, as determined by the appropriate functional commander or civilian equivalent.”

4.8.2 Designation of Services as Mission-Essential: In accordance with DFARS 252.237- 7023(a), Continuation of Essential Contractor Services / Definitions, and AFI 10-403, Deployment Planning and Execution, paragraph 1.6.1.25, the GRMIA Functional Commander (FC) or civilian equivalent has determined that these services are not mission-essential and will not continue in the event of a crisis.

4.9 U.S. Government Environmental Management System (EMS):

4.9.1 Executive Order (E.O.) 13423, Strengthening Federal Environmental, Energy, and Transportation Management, and E.O. 13514, Federal Leadership in Environment, Energy, and Economic Performance, establish the requirements for an Environmental Management System (EMS) and obligate federal [U.S. Government] agencies to implement sustainable practices.

4.9.2 In accordance with the Secretary of the Air Force (SAF) Policy Letter, Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations, dated 11 Dec 06, and the Air Force Materiel Command/Vice Commander (AFMC/CV) Policy Letter, Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations, dated 1 Aug 07, Contractor personnel who perform work on any USAF installation shall comply with the EMS requirements established by the installation.

4.9.3 Contractor personnel who perform work on Robins AFB shall complete Robins AFB EMS General Awareness Training prior to beginning work. EMS General Awareness Training will be provided by the 78th Civil Engineering Group Environmental Management Division (78 CEG/CEV). Contractor personnel can satisfy the EMS General Awareness Training requirement by any of the following means:

4.9.3.1 With a CAC, access the 78 CEG/CEV website, select EMS General Awareness Training, choose option 1.

https://geobase.robins.af.mil/emstraining/EMSTrainingOptions.aspx

4.9.3.2 Without a CAC, request a copy of Robins AFB EMS General Awareness Training via the 78 CEG/CEV Workflow Mailbox.

78ceg.cev.FrontOfc@robins.af.mil�

4.9.3.3 If a company is International Organization for Standardization (ISO) 14000 certified, Contractor personnel do not have to complete Robins AFB EMS General Awareness Training;

however, the Contractor must provide documentation of ISO 14000 certification to the PCO.

4.9.4 The prime Contractor shall ensure subcontractors comply with the EMS requirement.

4.10 U.S. Government Green Procurement Program (GPP): Under Secretary of Defense Memorandum, Establishment of the DoD Green Procurement Program, dated August 27, 2004, establishes the requirement for a GPP. The GPP is a mandatory federal [U.S. Government] acquisition program that focuses on the purchase and use of environmentally-preferable products and services. Federal Acquisition Regulation (FAR) 23.404, Agency affirmative procurement programs applies.

FMS Exemption: The GPP requirement applies only to acquisitions using U.S.

Government funds; therefore, the GPP requirement does not apply.

4.11 Inspection of Services:

4.11.1 In accordance with FAR 52.246-4, Inspection of Services - Fixed-Price, the Contractor shall maintain a quality inspection process acceptable to the U.S. Government.

4.11.2 In accordance with FAR 52.246-4, the U.S. Government reserves the right to inspect Contractor performance.

4.12 Safety and Health

4.12.1 U.S. Government Safety and Health Regulations: The Contractor shall comply with Public Law 91-596 as amended by Public Law 101-552, Occupational Safety and Health Act (OSHA) and OSHA Standard 29 Code of Federal Regulations (CFR), Part 1910, Occupational Safety and Health Standards. The Contractor shall comply with DoD Directive 4715.1E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall comply with AFI 91-301, Air Force Occupational and Environmental Safety, Fire Protection, and Health (AFOSH) Program.

4.12.2 Safety and Health Plan/Program: The Contractor shall establish and maintain a Safety and Health Program in accordance with the requirements listed in the contract Appendix C, Industrial Safety Requirements. Prior to contract award, the Contractor shall submit a Safety and Health Plan for review and acceptance by the U.S. Government Safety Office.

4.12.3 Mishap Notification/Investigation: The Contractor shall notify the U.S. Government Safety Office (478-926-6271) within four cumulative business hours of a mishap involving U.S.

Government property provided under the contract. There shall be no more than one late mishap notification per contract year. If requested by the U.S. Government, the Contractor shall immediately secure the mishap scene and/or damaged property and applicable records until released by the investigating Safety Office. If the U.S. Government investigates the mishap, the Contractor and subcontractors shall cooperate fully and assist the U.S. Government personnel until the investigation is completed.

The Contractor is not expected to have U.S. Government property in their possession for the contract PoP.

4.13 Travel:

4.1.7 The Contractor shall support up to two meetings with WR-ALC/GRMIA personnel for the purposes of providing additional guidance on how to perform the ASIP for the RSAF F-15 updates to compliment the Contractor effort. Travel must be approved in advance by the PCO.

4.1.8 The Contractor shall support up to two meetings with WR-ALC/GRMIA personnel for the purposes of providing a semiannual review on the current state of the F-15 ASIP contract and obtaining additional guidance and direction on continued ASIP performance. Travel must be approved in advance by the PCO.

4.13.1 Travel requests for Contractor personnel shall be submitted to the PCO for approval prior to costs being incurred and a minimum of 14 business days in advance of departure. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46 - Travel costs.

4.13.2 Travel by U.S. Government DoD civilian personnel will be conducted in accordance with Joint Travel Regulations (JTR), Volume 2, Department of Defense Civilian Personnel.

5.0 APPENDICES.

Appendix A: References

Publication Title of Publication Date of Publication (Basic and Latest

Revision)

Applicable Sections

AFI 10-403 Deployment Planning and Execution

13 January 2008 Paragraphs 1.6.1.25 and 1.6.1.26.

FILE NUMBER: FD2060-12-32670/REVISION 0� ������

DoD 5200.22-M National Industrial Security Program Operating Manual

(NISPOM)

February 28, 2006 All

DoD 5200.2-R Personnel Security Program Original January 16, 1987

Rev. 1 – 12 February 1990

Rev. 2 – 14 July 1993

Rev. 3 – 23 February 1996

All

AFI 31-101 Integrated Defense 8 Oct 2009 All

RAFBI 31- 101 Installation Security 28 Feb 2008 All

E.O. 13423 Strengthening Federal Environmental, Energy, and Transportation Management

January 24, 2007 All

E.O. 13514 Federal Leadership in Environment, Energy, and Economic Performance

5 October 2009 All

Under Secretary of Defense Memorandum

Establishment of the DoD Green Procurement Program

August 27, 2004 All

SAF Policy Letter Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations

11 December 2006 All

AFMC/CV Policy Letter Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations

1 August 2007 All

AFI 91-301 Air Force Occupational and Environmental Safety, Fire Protection, and Health (AFOSH) Program

1 June 1996 All

DoD Directive 4715.1E Environmental, Safety, and Occupational Health

(ESOH)

March 19, 2005 All

OSHA Standard 29 CFR, Part 1910

Occupational Safety and Health Standards http://osha.gov/ All

Public Law 91-596 as amended by Public Law 101-

Occupational Safety and Health Act of 1970

December 29, 1970, amended November 5, All

Joint Travel Regulations

(JTR)

The Joint Travel Regulations (JTR), Volume 2, Department of Defense Personnel

1 June 2009 All

Aircraft Structural Integrity AFPD 63-10 Original – 1 October 1995

Rev. - 1 November 1997

All

Aircraft Structural Integrity Program

AFI 63-1001 Original - 1 November

Rev. - 18 April 2002

All