16-70386_PWS_Final_(Revision_0)_00.pdf

PR: FD2060-16-70386 PWS REVISION: 0 1

Performance Work Statement for

MHU-196A/M

Engagement Force & User Evaluation

Feedback Implementations Heavy Munitions Lift Trailers IPT

FD2060-16-70386

February 4, 2016

1.1 Description of Services

1.2 Objective(s): This Performance Work Statement (PWS) describes the services required to provide a solution for the engagement force system and implementation of user evaluation feedback on the Wyle prototype trailer MHU-196A/M. These services are hardware and software changes to the configuration baseline.

1.3 Benefit to United States Air Force (USAF): This effort will benefit the USAF by completing the upgrades required on the trailers to produce a safe, suitable, and effective trailer. The resulting prototypes will serve as production samples for the follow on depot upgrade program to be performed on the trailer fleet.

1.4 Background: The MHU-196 munitions handling trailers are support equipment used to load nuclear and conventional munitions on B-1B, and B-52 aircraft. These trailers are between 20 and 30 years old and were identified in the Air Force Comprehensive Assessment of Nuclear Sustainment (AFCANS) report as requiring modernization.

1.4.1 The trailer has a lifting system which places munitions packages into the bomb bay of USAF heavy bombers, and in the case of the MHU-196, places pylons on the wing of the B-52.

Due to the large weights of these packages, significant forces are developed in the hydraulic lift system which can damage airframes if not properly controlled. The requirement for the control system is to inhibit any further lifting if the lift force exceeds 4000 pounds above the weight of the package on the trailer. In order to accomplish this, the trailer must accurately measure the load to be lifted. In the case of lowering the load, user input will be substituted for a measured weight.

To date there has been a great deal of data generated during testing of the lift system. This data includes load cell data from the Scott Russell linkage, as well as pressure data from the lift cylinders and the jack cylinders. None of the data has produced clearly recognizable results which could lead to accurate and consistent control of the lift force. In order to more quickly develop a solution, alternative approaches will be considered.

PR: FD2060-16-70386 PWS REVISION: 0 2

1.4.2 The trailers underwent user evaluation from Jan-May 15, followed by a meeting between the users and the program management office (PMO) to discuss the results and potential actions.

It was agreed upon that the PMO will pursue improvements on the portable control unit (PCU) to include necessary software and/or hardware modifications.

2.0 Services Summary

Performance Objective PWS

Reference Performance Threshold

Error-free solution for MHU-196A/M trailer to accurately measure the load to be lifted, implementation of solution, and full integration into Hardware/Software (HW/SW) system

4.2 - 4.2.4 Contractor shall demonstrate that the engagement force solution meets performance requirements of the PWS.

Acceptance of Portable Control Unit (PCU) by user community including integration of upgrades into HW/SW system

4.2 - 4.2.4 PCU solution, including implementing and fully integrating into HW/SW system, will be widely accepted by user.

Adherence to program schedule

4.7.2 Contractor shall provide monthly status reports

to Government program manager (PM) which reflect adherence to program schedule.

Integrated Master Schedule (IMS)

4.7.1 Contractor shall provide IMS within 30

calendar days of contract award. IMS shall demonstrate timely completion of project milestones within contract period of performance.

3.1 Government Property and Services

3.2 Government Property to be Provided: The Government will provide access to a MHU- 196A/M at Hill Air Force Base (AFB), Utah. Assistance in operation of the trailers will be provided by Government personnel. A copy of the software running on the trailer will be provided. In addition a prototype Portable Control Unit (PCU) will be provided to facilitate PCU improvements. A legacy PCU (P/N 60244-45300-10) will also be provided.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property

PR: FD2060-16-70386 PWS REVISION: 0 3

(GFP) in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements

3.4 Reporting Loss of Government Property: In accordance with DFARS 252.245-7002, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.5 Return/Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. Retention of the property by the Contractor will require modification of both losing and gaining contracts in accordance with the FAR and applicable supplements. All Government property shall be returned at the Contractor’s expense to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract. All Department of Defense (DD) Form 1423-1, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt.

3.6 Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the Contractor shall ensure the system account(s) are closed.

4.1 Technical Requirements

4.2 Period and Place of Performance

4.2.1 Contract/Order Period of Performance: The period of performance for the contract/order extends for twelve (12) months. Excluding unknown events that may affect the critical path, it is expected that the prototype installation, Contractor format drawings, and technical source data will be accomplished by mid-December 2016, with final document submission to be completed by 30 March 2017.

4.2.2 Place of Performance: These services shall be performed at Hill AFB, Utah, and the Contractor’s facilities in Warner Robins, Georgia. The actual development of solutions will be at the Contractor’s facilities while the study and implementation of these solutions will take place at Hill AFB, Utah.

4.2 Technical Requirements Description

http://www.dcma.mil/aboutetools.cfm

PR: FD2060-16-70386 PWS REVISION: 0 4

4.2.1 The Contractor shall provide a comprehensive analysis of the Scott Russell lift linkage which demonstrates resultant forces for any given input force (weight on lift beams). This model which of necessity shall be idealized will be used to determine areas of the current real world design which could explain the data developed to date. Once the delta between the idealized and real world performance of the trailer is established, the Contractor shall propose likely corrective actions to address these deltas. Should the corrective actions not be acceptable, the Contractor shall proceed to research state-of-the-art engagement force measurement alternatives including, but not limited to, an evaluation of load cell replacements including alternative instrumentation, software changes, and mounting features. The proposed solution shall be capable of detecting (within 12 inches of upward or downward travel), precisely controlling (within plus or minus 500 pounds), and limiting resultant engagement forces to less than 4000 lbs, for any loading scenario up to the maximum weight of 40,000 pounds. Given the uncertainties of the required technologies, stated requirements will be placed in a trade space in order to meet cost and schedule requirements. As part of the testing, influence of lift speed on engagement force will be examined. Further, the Contractor shall provide studies, tests, and associated methodologies used to support theoretical or laboratory proof of concept regarding functionality, subsystem integration, and system compatibility. Proposed solutions will be briefed to the Government for evaluation and down select before proceeding with concept development, test and demonstration.

Proposed solutions shall include costs, complexity, and degree of modifications to the trailer required to implement each proposed solution. With Government concurrence, the Contractor shall develop comprehensive equipment retrofit procedures, suitable for USAF depot-level personnel, and implement the selected alternative onto the MHU-196A/M prototype trailer to support technology demonstration within a relevant environment. All data produced or acquired due to this effort shall be provided in-full to the Government with unlimited use rights. [DI- MISC-80508B, Technical Report - Study/Services(A008); DI-GDRQ-80650/T, Design Data and Calculations(A011)]

4.2.2 Upon Government concurrence, the Contractor shall install and evaluate the proposed/alternative force engagement subsystem(s) fully integrated with the existing control software. The extent of changes to the control software is dependent upon Contractor solutions developed per 4.2.1 requirements; the Contractor shall be responsible for software change and integration of the new technology into the existing system. The package weight information shall continue to be displayed on the OMU Operator Screen Data acquired from this effort will be contrasted against pre-test simulated or theoretical/laboratory information; if discrepancies are found to exist, the Contractor shall perform an iterative study to address inconsistencies until computational analysis aligns with physical output. All data regarding these efforts, along with lessons learned, shall be supplied to the Government for final evaluation and review. [DI-NDTI- 81307A, Prototype Test Plan(A006); DI-NDTI-80809B, Prototype Test/Inspection Report (A007)]

4.2.3 The Contractor shall research and propose alternative display screen, joystick and mode selector switch for the PCU along with required software interface changes required to improve tactile and visual (PCU screen) feedback. A legacy PCU will be provided for baseline comparison. For the final proposal, the Contractor shall provide studies, tests, and associated methodologies used to support theoretical/laboratory proof of concept regarding functionality, subsystem integration, and system compatibility. With Government concurrence, the Contractor shall develop comprehensive equipment retrofit procedures, suitable for USAF depot-level

PR: FD2060-16-70386 PWS REVISION: 0 5

personnel. Furthermore, the Contractor shall implement the design alternative onto the MHU- 196A/M prototype trailer to support technology demonstration. All data produced or acquired due to this effort shall be provided in-full to the Government. [DI-MISC-80508B, Technical Report - Study/Services (A008); DI-GDRQ-80650/T, Design Data and Calculations (A011)]

4.2.4 The Contractor shall develop and the Government will approve comprehensive test procedures to demonstrate the performance of the redesigned engagement force system and PCU components. Operation of the trailer will be performed by Government personnel. This test will demonstrate that the performance of the new design is equal to or better than the legacy design. This test procedure shall be signed by the Government representative prior to execution of the test. After the test, a final report shall be prepared to document the findings.

[DI-NDTI-81307A, Prototype Test Plan (A006); DI-NDTI-80809B, Prototype Test/Inspection Report (A007)]

4.3 Engineering Data: The Contractor shall develop, produce, maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models (parasolid files or IGES files), model based definition data sets, Gerber data, Engineering Change Proposals (ECP), Notice of Revision (NOR) and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection, or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision M (CAGE 98752), reference attached DD Form 1423 Block 16. [DI-SESS- 81000E/T, Product Drawings/Models and Associated Lists (A005), DI-SESS-80639D, Engineering Change Proposal (ECP)(A010), DI-SESS-80642D, Notice of Revision

(NOR)(A009)]

4.3.1 Engineering Data Guidance Conference: The Contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 calendar days after contract award, the Preliminary Design Review (PDR) 135 calendar days after Contract Award (CA), and the Critical Design Review (CDR) 225 calendar days after CA. The PDR shall describe the Contractor’s proposed solution. The proposed solution shall incorporate the tenants of the PWS. The CDR shall be based on insights gained from the PDR and requirements of the PWS. On approval of the CDR by the Government, the CDR design shall be used in production of the prototype. The Conference shall be convened at a site and on a date agreed upon by the Government Procuring Contracting Officer (PCO) and the Contractor. The Contractor shall prepare an agenda and record the minutes of the Guidance Conference. The Contractor shall

PR: FD2060-16-70386 PWS REVISION: 0 6

address, discuss, and provide status on the following: [DI-ADMN-81249A, Conference Agenda(A002); DI-ADMN-81250A, Conference Minutes(A003)]

a. Understanding of all CDRL requirements, applicable Data Item Descriptions (DIDs), specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. The Contractor’s drafting practices/procedures/ TDP drawing formats/CAD programs.

e. The Contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The Contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital TDP deliverables.

Note: Guidance Conference may be held in conjunction with other meetings or conferences.

4.4 In-Process Review (IPR) of the TDP: The Contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the Contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The Contractor shall notify AFLCMC/LZPEM a minimum of 30 calendar days prior to the anticipated date of completion point. The IPR shall focus on the Contractor's progress in the preparation of the TDP. The Contractor shall support and provide the necessary resources, e.g., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The Contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. [DI- ADMN-81249A, Conference Agenda(A002); DI-ADMN-81250A, Conference Minutes(A003)]

PR: FD2060-16-70386 PWS REVISION: 0 7

4.4.1 Relationship of Contractor with Subcontractors/Vendors: The Contractor shall levy on subcontractors and vendors the same requirements for Technical Data Packages (TDP) as are levied on them by this contract. This requirement shall apply at all tiers of subcontractor/vendor levels associated with the program.

4.5 Engineering Data Updates and Revisions: The Contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 calendar days after engineering release/USAF concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the Contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

4.6 Travel: Travel requests for Contractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of five business days in advance of departure.

Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs. Following each trip, a trip report shall be provided to the Government Program Manager.

[DI-MISC-81943, Trip/Travel Report (A012)]

4.7 Schedule

4.7.1 The Contractor shall provide an IMS within 30 calendar days of contract award. The IMS shall project timely completion of project milestones within the contract period of performance.

[DI-MGMT-81861, Integrated Master Schedule (IMS)(A004)]

4.7.2 The Contractor shall report adherence to program schedule in monthly status reports.

[DI-MGMT-80227, Contractor’s Progress, Status, and Management Report (A001)]

5.1 General Information

5.2 Continuation of Mission-Essential Services during a Crisis

PR: FD2060-16-70386 PWS REVISION: 0 8

5.2.1 Definition of Mission-Essential Services: In accordance with the Defense Federal Acquisitions Supplement (DFARS) 252.237-7023(a)(1), Continuation of Essential Contractor Services, “ ‘Essential Contractor service’ means a service provided by a firm or individual under contract to the Department of Defense (DoD) to support mission-essential functions, such as support of vital systems, … associated support activities, … and similar services provided to foreign military sales 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.”

5.2.2 Designation of Services as Mission-Essential: In accordance with DFARS 237.7602(a), Continuation of Essential Contractor Services, DFARS 252.237-7023(a)(2), and Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2, the Functional Commander (FC) or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Actual knowledge and/or generation of classified information and/or Controlled Unclassified Information (CUI) are not expected to be necessary for performance of the contract/order. Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property and facility security requirements are met. The Contractor shall comply with Government security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM); DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual.

5.2.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.) Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.2.4 Security Clearance: It is not expected Contractor personnel will require security clearances for proper accomplishment of contract/order requirements. Contractor personnel shall not be authorized access to classified information and/or CUI and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.2.5 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

PR: FD2060-16-70386 PWS REVISION: 0 9

5.2.6 Access to Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure Contractor personnel who require access to an unclassified or classified Government automated information systems (AIS) have the respective background check or security investigation conducted. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.7 Release or Removal of Information. Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems.

Contractor personnel shall not bring any photographic equipment (to include cellphones) into the work area. All requests for information/photographs shall be forwarded to the MHU Support Equipment Program Manager.

5.2.8 Standards of Conduct. 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. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct.

5.2.9 Access to Hill Air Force Base, UT: The Contractor shall ensure Contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation. Below is the noted process for Hill AFB:

5.2.9.1 Entry to Hill Air Force Base, UT. The contracted company representative shall check in at the South Gate Visitor Center. They shall have a valid vehicle registration, driver’s license, and proof of insurance.

5.2.9.2 Missile Maintenance Group (309 MMXG) Building 847 Access. The contracted company representative shall provide a Visit Request to the 309 MMXG Security Office located at Hill Air Force Base, UT, Building 847, Room 9A. The Visit Request shall be on corporate letterhead and shall contain the following information: Name, Social Security Number, Place of Birth, Date of Birth, and Dates of Visit. The Visit Request must be signed by the Contractor’s Security Manager or management. The completed Visit Request can be delivered via Fax, Email, or through the Joint Personnel Adjudication System (JPAS) to the 309 MMXG Security Officer, . The Fax number is (801) 586-3233; the email address is and the JPAS SMO Code is:

HP1MFD5P. If you have questions or need assistance, the 309 MMXG Security Manager’s telephone numbers are: (801) 777-1293 or (801) 775-2134.

5.2.9.3 The contracted company representative will be accessing Hill Air Force Base, Building 847 to provide assistance with MHU Support Equipment Engineering Support as required. The Contractor will not be accessing classified or CUI information. They do not require computer access. They will be escorted into Building 847 areas.

PR: FD2060-16-70386 PWS REVISION: 0 11

5.2.9.4 The MHU Support Equipment is located in the Missiles Maintenance Group, Building

847. The contractor shall coordinate access with the MHU Support Equipment Program Manager, OO-ALC/OBP, (801) 586-8460 or DSN 586-8460.

5.2.9.5 Base or Area Badges and Access to Facilities. The 309 MMXG Security Manager will assist Contractor personnel in processing the necessary Department of Defense (DoD) forms to obtain base or area badges for access to Government facilities and property. Access to Government facilities is limited; therefore, the Contractor shall coordinate required access/usage times and dates through the 309 MMXG Security Manger at least fifteen business days prior to the need date. Control of the facilities shall remain with the Government.

5.2.10 Identification of Contractor Personnel Requiring Access: The efforts required for this task are expected to be UNCLASSIFIED and should not require the Contractor personnel to obtain a security clearance.

5.2.11 Common Access Card (CAC): Common Access Cards will not be required.

5.3 Environmental Management System (EMS)

5.3.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 requirement for an EMS.

5.3.2 In accordance with the Assistant 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.

5.3.3 Contractor personnel shall complete EMS training prior to beginning work on any USAF installation. The EMS training requirement may be satisfied by any of the following means:

a. If the Contractor is International Organization for Standardization (ISO) 14000 (Environmental management) certified, Contractor personnel do not have to complete EMS training; however, the Contractor shall provide documentation of ISO 14000 certification to the PCO.

b. If Contractor personnel possess CACs, they may complete Advanced Distributed Learning Service (ADLS) ZZ133070, Environmental Management System - General Awareness Training at the ADLS site below. The Contractor shall provide their certificate(s) to the PCO. https://golearn.adls.af.mil/?strCourseID=C04132

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

https://golearn.adls.af.mil/?strCourseID=C04132

PR: FD2060-16-70386 PWS REVISION: 0 12

5.4 Affirmative Procurement Programs: In accordance with FAR 23.404, Agency Affirmative Procurement Programs, 100% of purchases of Environmental Protection Agency (EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list [http://www.epa.gov/cpg/products.htm] and/or United States Department of Agriculture (USDA)-designated products included in the biobased product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or biobased content, respectively, unless an item cannot be acquired competitively within a realistic timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price. The prime Contractor shall ensure subcontractor(s) comply with the affirmative procurement requirement.

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH). OSHA and ESOH requirements shall be incorporated into the Contractor’s safety program.

5.5.2 Mishap Notification/Investigation

5.5.2.1 In accordance with AFI 91-204, Safety Investigations and Reports, paragraph 2.4.6.1.1, the Contractor shall report mishaps involving damage or injury to USAF interests. In accordance with AFI 91-204, paragraph 1.3.1.1, damage or injury includes: damage to DoD property;

occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by USAF operations.

5.5.2.2 In accordance with AFI 91-204, paragraph 2.4.6.1.1, the Contractor shall ensure the USAF [Safety Office] and the applicable contract management authority are notified of mishaps.

The Contractor shall contact the Multi-Functional Team (MFT) [Contracting Officer’s Representative (COR), if available, or another MFT member] by telephone within three business days. The MFT will notify the Safety Office and the PCO.

5.6 Inspection of Services: In accordance with FAR 52.246-5, Inspection of Services - Cost- Reimbursement, the Government reserves the right to inspect Contractor performance. In accordance with FAR 52.246-5, the Contractor shall maintain an inspection process acceptable to the Government and records of inspections which shall be made available to the Government as long as the contract requires.

5.7 Trafficking in Persons: The Contractor shall comply with the FAR and applicable supplements as it relates to Trafficking in Persons. Additional information about Trafficking in http://www.epa.gov/cpg/products.htm http://www.biopreferred.gov/

PR: FD2060-16-70386 PWS REVISION: 0 13

Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. http://www.state.gov/j/tip

5.8 Contractor Manpower Reporting

5.8.1 In accordance with the Secretary of the Air Force for Acquisition (SAF/AQ) Memorandum, Implementation of FY11 NDAA [National Defense Authorization Act] Section 8108 [of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Act, 2011], Contractor Inventory, dated Nov 13 2012, the Contractor shall provide an annual count of Contractor personnel performing work if the DoD is the requiring activity, if the acquisition is using U.S. Government appropriated funds, and if the acquisition is equal to or greater than the Simplified Acquisition Threshold (SAT) [currently $150,000.00].

5.8.2 In accordance with the Office of the Secretary of Defense (OSD) Memorandum, Enterprise-wide Contractor Manpower Reporting Application, dated Nov 28 2012, the Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract at the Enterprise-wide Contract Manpower Reporting Application (eCMRA) site below. Reporting shall be conducted for each fiscal year (FY), which extends October 1 through September 30. While inputs may be made any time during the FY, all data shall be reported no later than October 31 of the following FY.

The Contractor may direct questions to the help desk at the eCMRA site below.

http://www.ecmra.mil

5.9 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) in accordance with the DFARS.

http://www.state.gov/j/tip http://www.ecmra.mil/

PR: FD2060-16-70386 PWS REVISION: 0 14

6.1 Appendices

6.2 Appendix A: References

Publication Title of Publication

Date of Publication Section(s) that Apply

AFI 91-204 Safety Investigations and Reports

12 February 2014 Corrective actions applied on 10 April http://www.e-publishing.af.mil/

Paragraphs 1.3.1.1, 2.4.6.1.1- 2.4.6.1.2

Assistant Secretary of the Air Force Policy Letter

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

11 Dec 06 Entire

DoDD 4715.1E Environmental, Safety, and Occupational Health (ESOH)

March 19, 2005 http://www.dtic.mil/whs/directives/corre s/pub1.html

Entire

DoDD 5205.02E DoD Operations Security

(OPSEC)

Program

June 20, 2012 http://www.dtic.mil/whs/directives/corre s/pub1.html

Entire

DoD Manual 5205.02-M

DoD Operations Security

(OPSEC)

Program Manual

November 3, 2008 http://www.dtic.mil/whs/directives/corre s/pub1.html

Entire http://www.e-publishing.af.mil/ http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html

PR: FD2060-16-70386 PWS REVISION: 0 15

Publication Title of Publication

Date of Publication Section(s) that Apply

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

5 October 2009 http://www.whitehouse.gov/assets/docum ents/2009fedleader_eo_rel.pdf

Entire

FAR and supplements

Federal Acquisition Regulation http://farsite.hill.af.mil

Sections applicable to contract and

PWS

OSD

Memorandum

Enterprise-wide Contractor Manpower Reporting Application

Nov 28 2012 http://www.acq.osd.mil/dpap/policy/polic yvault/Enterprise-wide_Contractor_Manpower_Reporting_ Application_memorandum.pdf

Entire http://www.whitehouse.gov/assets/documents/2009fedleader_eo_rel.pdf http://www.whitehouse.gov/assets/documents/2009fedleader_eo_rel.pdf http://www.whitehouse.gov/assets/documents/2009fedleader_eo_rel.pdf http://farsite.hill.af.mil/ http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf