Performance_Based_Work_Statement.pdf

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

EC-130J Engineering Services

FD2060-18-31041

PR Number

13 February 2018

Date

Prepared by:

AFLCMC/WIUAB

235 Byron Street, Suite 19A Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government agencies and their contractors (Critical Technology, Administrative or Operational Use; 15-07-01) (16 June 2016). Other requests for this document shall be referred to USAF AFLCMC/WIUAC.

Reproduction, disclosure, or dissemination of this document in whole or part, is prohibited except with permission

PR: FD2060-18-31041 PWS REVISION: 0

Distribution Statement: C

TABLE OF CONTENTS

SECTION TITLE PAGE

SECTION 1 DESCRIPTION OF SERVICES 3

SECTION 2 SERVICES SUMMARY 4

SECTION 3 GOVERNMENT FURNISHED PROPERTY 5

SECTION 4 TECHNICAL REQUIREMENTS 6

SECTION 5 GENERAL INFORMATION 11

SECTION 6 APPENDICES 15

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to provide Continental United States/Outside Continental United States (CONUS/OCONUS) system engineering services to support Air Force Special Operations Command (AFSOC) EC- 130J aircraft managed by the AFLCMC/WIU SOF/PR.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by providing long term sustainment of the AFSOC EC-130J aircraft. The PWS system requirements will encompass legacy systems and new requirements. The contractor shall perform complete, accurate, and timely system engineering and technical liaison services to support the EC- 130J aircraft system/subsystems and their integration into the aircraft. The task will comprise of engineering design and analysis, engineering studies, validation/verification kits that support Time Compliance Technical Order (TCTO) requirements (limited to three (3) per mission assignment (EC- 130J CS/EC-130J Super J; one (1) will support trial install, one (1) will support kit-proof, and one (1) will be a spare to support flight testing), test support, engineering drawings, technical order source data support and support for system/sub-system integration, operational capability improvements, reliability and maintainability improvements and avionics systems analysis. Additionally, the contractor shall provide punctual delivery of required data. This effort will benefit the Air Force by providing timely system engineering activities, improved capability to the war-fighter, and by helping to reduce down-time of Low Density/High Demand (LD/HD) aircraft.

1.3 Background: The EC-130J is a LD/HD use aircraft in which downtime and manpower are critical to time sensitive mission accomplishment. The EC-130J is undergoing several Special Operations Forces (SOF) unique development and modification programs over the Five Year Development Plan (FYDP). These programs and capabilities include Military Information Support Operations (MISO), Special Mission Equipment (SME) Sustainment, Block 7.0/8.1 Upgrade and EC-130J Integration Program (3D Scan) for new upgrades. These programs are highly interdependent, thereby requiring management at the platform level to ensure effective and efficient integration onto the EC-130J aircraft and training systems. EC- 130J Integration Program Office manages the planning and execution of the EC-130J modification line. The Program Office consolidates as many of the EC-130J SOF modifications installations into one (1) baseline install as possible, in accordance with the EC- 130J Program Managers integration plan.

1.4 Estimated changes to aircraft fleet size: There are no projected changes to fleet size. The current EC-130J Fleet is divided into two (2) distinct mission assignment groups. One (1) group consists of three (3) EC-130J equipped with SME. The second group consists of four (4) EC- 130J that are used to support mobility with projected future Military Information Support Operations (MISO) requirements. These aircraft are recognized as the Commando Solo Fleet.

2.0 Services Summary:

Performance Objective PWS

Reference Performance Threshold

Quality of CDRL deliverable

4.2.1 There shall be no more than one (1) rejection of each

deliverable. There shall be no more than three (3) total rejection(s) of deliverables per quarter. The Government will reject a deliverable if two (2) or more technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within three (3) business days of notification of Government rejection in accordance with the associated DD Form 1423 instructions/requirements.

Receipt of CDRL deliverable

4.2.2 There shall be no more than two (2) late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Mishap Notification and Reporting

5.5.2 The Contractor shall ensure the USAF is notified of

mishaps. The contractor shall notify the Contracting Officer (CO), within eight (8) hours of any damage to government property where the dollar value exceeds $500,000.00 and within two (2) workdays, for any damage to government property less than $500,000.00 during the execution of the contract.

Contractor Manpower Reporting Application

(CMRA)

5.6; 5.6.1;

5.6.2

Within 30 calendar days of contract/order award, the Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data and submit the annual report no later than October 31 of the following fiscal year.

Adherence to Contractor Quality Management System (QMS)

5.8 100% compliance with the QMS is required.

3.0 Government Property:

3.1 Government Property: Government property includes Government Furnished Property (GFP), Government Furnished Material (GFM), Government Furnished Equipment (GFE), special tooling, special test equipment, etc. GFP does include assets furnished for repair, maintenance, overhaul or modification. The Contractor shall be responsible for Government property in their possession in accordance with Federal Acquisition Regulation (FAR) Part 45, and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.2 Base Support: The Government will provide ground support equipment and personnel as needed to support troubleshooting and repair. The Government will provide the CLS team with access to the base and flight line area where the aircraft are located and phone access during the period of performance.

3.3 Reporting of Government Property: The contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of GFP in the Item Unique Identification (IUID) Registry. Government property shall be listed as a GFP attachment and is created as a fillable document at http://dodprocurementtoolbox.com

3.4 Loss of Government Property: Reporting Loss of Government Property, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. 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:

3.5.1 All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract 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 shall require modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO.

3.5.2 All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract. All Department of Defense (DD) Form 1423-1, Contract Data Requirements List (CDRL), and 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. The Contractor shall ensure http://dodprocurementtoolbox.com/ http://www.dcma.mil/aboutetools.cfm

Contractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the appropriate background check or security investigation conducted.

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

4.0 Technical Requirements:

4.1 Period and Place of Performance:

4.1.1 Contract/Order Period of Performance: The anticipated period of performance for the contract is 1 July 2018 through 30 June 2023.

Basic: 1 July 2018-30 Jun 19 Option I: 1 July 2019-30 Jun 20 Option II: 1 July 2020-30 Jun 21 Option III 1 July 2021-30 Jun 22 Option IV: 1 July 2022-30 Jun 23

4.1.2 Place of Performance: These services will be provided at the locations listed below Additionally, Contract Logistic Support (CLS) will be required at up to three (3) separate deployed locations (CONUS and/or OCONUS) simultaneously; however, deployments can be anywhere there is a need for Special Operations aircraft.

• Seven (7) EC-130J aircraft located at Harrisburg Air National Guard Base (ANGB), Pennsylvania

• The EC-130J Calendar inspections are performed at Hurlburt Field, Florida

• The EC-130J Depot level inspections and repair are performed at Robins AFB, Georgia

4.2 Contract Data Requirements List (CDRL):

Document Identifier

DID Title PWS Reference(s)

A001 DI-MGMT-80368A Status Report 4.4.1 ,4.4.5 A002 DI-MISC-80508B/T Technical Report – Study/Services 4.4.3 A003 DI-MISC-80508B/T Technical Report – Obsolescence Report 4.3.3 A004 DI-MISC-80508B/T Technical Report – Data Updates and Revisions 4.3.4 A005 DI-ADMN-81249B Conference Agenda 4.3.6, 4.4.4 A006 DI-ADMN-81250B Conference Minutes 4.3.6, 4.4.4 A007 DI-SESS-81000E/T Product Drawings/Models and Associated Lists 4.3.4 A008 DI-SAFT-82080/T Safety and Health Plan 5.5.3 A009 DI-DRPR-81961 Drawing Tree 4.3.4

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable.

There shall be no more than three (3) total rejection(s) of deliverables per quarter. The Government will reject a deliverable if two (2) or more technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within three (3) business days of notification of Government rejection. In accordance with the associated DD Form 1423 instructions/requirements.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Wide Area Workflow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) or be submitted directly to the MFT member identified on the CDRL. There shall be no more than two (2) late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date.

The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Contractor Logistic Support

4.3.1 CLS shall consist of CONUS and OCONUS technical and material support for the EC- 130J systems/subsystems.

4.3.2 The Contractor shall identify and document system level discrepancies and comply with new requirements.

4.3.3 Obsolescence Management: The Contractor shall establish and implement an obsolescence management program. The Contractor shall investigate, evaluate, and recommend actions as suitable for obsolete and non-obtainable parts/components for the EC-130J systems. Further, the Contractor shall recommend engineering changes, which would improve technical performance, improve reliability and maintainability, or reduce operating costs. Recommendations and technical solutions to obsolescence issues shall be evaluated by the Government before any changes are implemented.

(CDRL A003, DI-MISC-80508B/T, Technical Report)

4.3.4 Engineering/Technical Data Updates and Revisions: The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. The TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Material (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 design activity or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems and/or components. 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 created IAW the following American Society of Mechanical Engineers (ASME) standards: ASME Y14.100-2013, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for this task to create and deliver Product Drawings Models and Associated Lists (Engineering Data) under this contract. Data set classification code marking IAW Appendix F of ASME Y14.100- 2013 is required. CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL-STD- 130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be IAW document 9579777 Revision B (CAGE 98752) The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752), reference attached DD Form 1423 Block 16. The contractor shall submit an engineering drawing tree identifying all system, subsystem and equipment drawings as part of the drawing package prior to FCA/PCA. (CDRL A007, DI-SESS-81000E/T, Product Drawings/Models and Associated Lists; CDRL A009, DI-DRPR-81961, Drawing Tree; CDRL A004, DI-MISC- 80508B/T, Technical Report)

4.3.5 Engineering Data Guidance Conference: The contractor shall support and co- chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. 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 Technical Data Package (TDP) deliverables.

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

(CDRL A007, DI-SESS-81000E/T, Products/Drawings and Associated Lists: CDRL A005, DI-ADMN- 81249B, Conference Agenda: CDRL A006, DI-ADMN-81250B, Conference Minutes)

4.3.6 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). Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), These shall consist of the Native, Neutral, Word Searchable PDF, HPGL, Metadata Spreadsheet, BOM, Gerber Data, and Software/memory Device Data. The contractor shall notify AFLCMC/LZPEM a minimum of 30 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, i.e., 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. (CDRLA005, DI-

ADMN-81249B, Conference Agenda, CDRL A006, DI-ADMN-81250B, Conference Minutes)

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

4.3.8 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:

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

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

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

4.3.8.4 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.4 Program Management

4.4.1 The Contractor shall provide a single point of contact for this task. The level of program management shall support financial controls, material and logistics management, scheduling, security, data management and reports, and task proposals. The contractor shall provide periodic status reports detailing accomplishments within the reporting period. The contractor shall maintain a schedule addressing significant milestones for the effort. The contractor shall submit a status report by the 15th calendar day of the delivery month. The contractor’s report shall be complete and accurate, so that the number of report rejections shall not exceed one (1) per each six (6) month period. Rewritten reports shall be resubmitted to AFLCMC/WIU within five (5) business days of notification that a rewrite is required. The Contractor shall develop management plans, as necessary, to ensure that all elements of this effort are successfully executed within the program budget and schedule. The Contractor shall also ensure that complete financial accountability is maintained by contract line item and that all CDRL items are delivered to the Government in accordance with the CDRL requirements. The Contractor shall notify the Government of any program issues that may impact the execution of this PWS. The Contractor shall conduct program meetings and reviews as required by this PWS. Where feasible, meetings should be combined. The Contractor and the Government will mutually agree upon locations and dates of program meetings and reviews. (CDRL A001, DI-MGMT-80368A, Monthly Status Report)

4.4.2 Systems: The contractor shall provide system engineering and technical services to support AFLCMC/WIU managed systems/subsystems and their integration into aircraft associate interfaces, trainers, and support equipment for the EC-130J aircraft. Additionally, the contractor shall support new integration efforts that occur during the period of performance.

4.4.3 Service Engineering: The contractor shall perform system engineering and technical liaison services to support the aircraft system/subsystems and their integration into the aircraft. These system services include analytical engineering, system integration engineering, independent engineering tests, aircraft performance engineering, and the development of engineering design packages. The contractor shall perform co-site de- confliction for legacy and future systems and their integration into EC-130J Commando Solo (CS) aircraft. The contractor shall perform Free Space catalog 3-D Scan on EC-130J Commando Solo aircraft. Additionally, engineering shall support accident investigations, failure analysis, and aircraft trainers’ One- time damage analysis and damage tolerance assessments may be required as well as on-the-spot design of temporary and permanent repairs. Engineering services shall support testing of systems and subsystems, development and qualification of replacement parts, updating of drawings and specifications, technical data, and updating support equipment. This engineering services effort will encompass approximately 5,480 hours of labor per year, across multiple disciplines, to complete. Upon notification by AFLCMC/WIU of a technical report, the contractor shall provide reports within two (2) workdays of the request. The contractor’s report shall be delivered complete and accurate by the specified due date so that the number of report rejections, due to omitted or inaccurate technical information, shall not exceed one (1) per submittal.

Rewritten reports shall be resubmitted to AFLCMC/WIU within five (5) business days of notification that a rewrite is required. (CDRL A002, DI-MISC-80508B/T, Technical Report)

4.4.4 Program Management Reviews (PMR): The Contractor shall conduct a PMR 30 days after contract award. Thereafter the Contractor shall conduct quarterly PMRs. During each PMR, the Contractor shall brief the Government on the current program schedules, action items, problem areas, and problem resolutions. The PMR shall also include a discussion of Contractor Performance Assessment Reports (CPARs) rating areas. The Contractor shall provide an agenda no later than five

(5) workdays prior to the review and PMR minutes within ten (10) workdays of successful PMR completion. (CDRL A005, DI-ADMN-81249B, Conference Agenda; CDRL A006, DI-ADMN- 81250B, Conference Minutes)

4.4.5 Monthly Status Reports (MSR). The Contractor shall provide MSRs to the Government.

These reports shall cover the engineering and technical support provided by the contractor during the last monthly period. The contractor shall document task status, data deliverables, contract issues and actions and expenditure data, as well as anticipated task requirements during the next reporting period. Regular updating of cumulative cost versus estimated total cost shall be submitted in the monthly status reports. A fund expenditure chart that plots actual and planned expenditures and man-hours against time will be included with each monthly status report. In addition, all problem areas shall be addressed, with recommended solutions and the outcomes after solutions are implemented.

Reports shall include a “Burn Rate” chart that plots actual versus proposed expenditures, man-hours by labor category, and cumulative man-hours. The MSR’s shall be delivered no later than the 15th of each month. The report shall be complete and accurate; the number of report rejections shall not exceed one (1) per quarter. The Contractor shall have five (5) working days to correct identified deficiencies after receipt of Government rejection letter. (CDRL A001, DI-MISC-80368A/T, Monthly Status Report)

4.5 Travel: Contractor personnel, in conjunction with engineering services, shall be required to travel to other Government installations or to contractor facilities to observe and conduct tests, ensure compatibility or configuration changes and other integration services, and to furnish technical guidance as required. Trips, numbers and types of personnel shall be limited to the minimum required to accomplish work requirements in accordance with the Joint Travel Regulation (JTR). The contractor shall be responsible for arranging all contractor personnel travel during the program effort.

The contractor shall use the lowest cost mode of transportation commensurate with the mission requirements and good traffic management principles. Possible travel locations may include but are not limited to the 193 Special Operations Wing (SOW) at Harrisburg PA, Robins Air Force Base, GA and Hurlburt Field, FL. The Contractor shall travel as required by this PWS. The Contractor shall notify the Government Program Manager (PM) by email with the names of travelers, travel dates, purpose for travel, expected duration of the trip, estimated cost, and an itinerary. Contractor shall request authorization to travel No Later Than (NLT) seven (7) business days prior to the planned travel. Urgent travel requests may be submitted for approval in a shorter timeline and will be considered on a case by case basis. All travel must be approved in advance by the PCO. All travel expenses are limited by the FAR and must comply with the Joint Travel Regulations (JTR). (CDRL A001, DI-MGMT-80368A, Status Report)

4.6 Counterfeit Electronic Parts: The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory. The system shall incorporate processes/procedures to address the requirements listed in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government's review of the Contractor’s system will be accomplished as part of the evaluation of the Contractor’s purchasing system in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.0 General Information:

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander (FC) or civilian equivalent has determined these services are not mission- essential and services will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 General: The Contractor shall comply with the provisions of the National Industrial Security Program Operating Manual (DOD 5220.22-M). The Contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances, for protecting Government property, and for the security of Automated and Non-Automated Information Systems (AIS) and data are fulfilled. The Contractor’s AIS shall be protected such that unauthorized disclosure of classified information and or sensitive information is prevented. Contractors that do not require access to classified information but do require access to AIS are required, at a minimum, to have a Government adjudicated SECRET security clearance.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property, 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; DoD Manual 5205.02-M, and 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, DoD Directive for Operations Security (OPSEC) and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual to protect United States (U.S.)

Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government Installation comply with the OPSEC procedures.

5.2.4 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or CUI in accordance with DoD 5220.22-M, National Industry Security Program. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.2.5 Security Clearance: The Contractor shall ensure applicable Contractor personnel have security clearances at a minimum of SECRET level for proper accomplishment of contract requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items. Contractor inability to obtain proper employee security clearances shall not constitute an excusable delay in contract performance.

5.2.6 Security Incident or Violation: The Contractor shall immediately notify the unit security manager and Government supervision, of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

5.2.7 Security of Contractor System: The Contractor shall ensure the security of AIS’s at the Contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified information and/or CUI.

5.2.8 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 AIS have the appropriate background check or security investigation conducted. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). 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.9 Access to Government Facility or Military Installation: Access to Robins Air Force Base (AFB): 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. The Contractor shall ensure Contractor personnel who require access to a USAF installation comply with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.2.10 Common Access Card (CAC)

5.2.10.1 The Contractor shall ensure a CAC is obtained / maintained and managed by all contractor/subcontractor personnel who require a CAC for access to DoD computer networks and systems, for DoD installation entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.2.10.2 The employee's Contracting Company's Security Point of Contact shall forward a CAC request to the appropriate Government Contracting Officer (CO). The Government CO will sign and submit request to the Government Contracting Officer Representative (COR) requesting concurrence for the issuance of a CAC. The COR will forward the CAC request to the Government Trusted Agent (TA) for processing. Email notification will be provided by the TA to contractor employee once information is loaded in Trusted Associate Sponsorship System (TASS). Contractor has thirty (30) days to complete application process. User ID and Temporary Password will be provided and the Contractor has seven (7) days to initially log into TASS system.

5.3 Environmental Management System (EMS): These services shall not be performed at a Government facility; therefore, the EMS requirement does not apply.

5.4 Agency 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 bio-based product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or bio-based 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.

5.4.1 In accordance with FAR 23.404(a)(iii), the Contractor shall provide estimates and verification of recovered material for EPA-designated CPG products and certification for both EPA-designated CPG products and USDA-designated bio based products. In accordance with the Robins Air Force Base, Georgia/Green Procurement Program (GPP) Plan, the Contractor shall provide estimates and certifications to the Government for completion of the applicable attachment(s) to be included in the Purchase Request (PR) package.

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: The Contractor shall report mishaps including 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 Government operations. The Contractor shall ensure the Safety Office and the Procuring Contracting Officer (PCO) are notified of mishaps.

http://www.epa.gov/cpg/products.htm http://www.biopreferred.gov/

The Contractor shall contact the MFT (Contractor Officer Representative (COR), if available, or another MFT member) by telephone within eight (8) business hours. The Contractor shall cooperate with Government safety investigation.

5.5.3 Safety and Health Plan: The contractor shall submit a Safety and Health Plan to the Multi- Function Team (MFT) or as indicated by CDRL instructions, the contractor shall establish and maintain a safety program in accordance with the contract/order, applicable Government regulations and the Safety and Health Plan. (CDRL A008, DI-SAFT-82080/T, Safety and Health Plan)

5.5.4 Voluntary Protection Program (VPP): The USAF is a participant in the OSHA VPP.

Contractor personnel performing work on a USAF installation shall participate in the local VPP.

Additional information regarding VPP is available at the site below.

http://www.osha.gov/dcsp/vpp/index.html

5.6 Contractor Manpower Reporting: In accordance with the Contractor Manpower Reporting / Contractor Quick Reference Guide, the Contractor shall establish a record for the contract/order in the Enterprise-wide Contractor Manpower Reporting Application (eCMRA) no later than 30 calendar days after contract/order award. In accordance with the Contractor Manpower Reporting / Contractor User Guide, the Contractor shall enter Order Data, Contact Data and Location Data.

5.6.1 In accordance with the Secretary of the Air Force for Acquisition (SAF/AQ) Memorandum, Implementation of FY11 National Defense Authorization Act (NDAA) 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/subcontractor 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).

5.6.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 eCMRA site below. Reporting shall be conducted for each fiscal year, which extends October 1 through September 30. While inputs may be made any time during the fiscal year, all data shall be reported no later than October 31 of the following fiscal year.

The Contractor may direct questions to the help desk at the eCMRA site. http://www.ecmra.mil

5.7 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area Work Flow e-Business Suite/ Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) in accordance with all applicable clauses located in the basic contract.

5.8 Quality Management System (QMS): The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan (QCP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required.

http://www.osha.gov/dcsp/vpp/index.html http://www.ecmra.mil/

5.9 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in 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

6.0 Appendices

6.1 Appendix A: References

Publication

Title of Publication

Date of Publication

Section(s) That Apply

FAR and supplements

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

Sections applicable to contract and

PWS

DoD 5220.22-M National Industrial Security Program Operating Manual

(NISPOM)

February 28, 2006 Change 1 - March 28, 2013 http://www.dtic.mil/whs/directives/corr es/pub 1.html

Entire

MIL-STD- 1686C Department of Defense Standard Practice / Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices

Revision C October 25, 1995 Entire

FAR and supplements

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

Sections applicable to contract and

PWS

DoD 5220.22-M National Industrial Security Program Operating Manual

(NISPOM)

February 28, 2006 Change 1 - March 28, 2013 http://www.dtic.mil/whs/directives/corr es/pub 1.html

Entire

MIL-HDBK-

263B

Military Handbook / Electrostatic Discharge Control Handbook for Protection of Electrical and

Revision B July 31, 1994 Entire http://www.state.gov/j/tip http://farsite.hill.af.mil/ http://farsite.hill.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://farsite.hill.af.mil/ http://farsite.hill.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

Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices).

DoDI 1100.22 Policy and Procedures for Determining Workforce Mix

12 Apr 2010 Entire

DFARS 237.76 Continuation of Essential Contractor Services

24 Nov 2010 Entire

DoDD 5205.02E DoD Operations Security (OPSEC) Program

June 20, 2012 http://www.dtic.mil/whs/directives/corr es/pub 1.html

Entire

DoDD 5200.2-R Department of Defense (DoD) Personnel Security Program

1/1/87 Change 1 - 2/12/1990 Change 2 - 7/14/1993 Change 3 - 2/23/1996

Entire

DoDD 5205.02- M

DoD Operations Security (OPSEC) Program Manual

November 3, 2008 http://www.dtic.mil/whs/directives/corr es/pub 1.html

Entire

Public Law 91-

Occupational Safety and Health Act

(OSHA)

December 29, 1970 as amended through January 1, 2004

Entire

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

March 19, 2005 Entire

AFI 91-204 Safety Investigations and Reports

April 10, 2014 Entire

Air Force Pamphlet

(AFPAM) 91-210

Contract Safety February 14, 1994 Paragraph 6.4

6.2 Appendix B: Applicable Standards

MIL-HDBK-

454B

General Guidelines for Electronic Equipment

15 Apr 2007 Entire http://www.dtic.mil/whs/directives/corres/pub%201.html http://www.dtic.mil/whs/directives/corres/pub%201.html http://www.dtic.mil/whs/directives/corres/pub%201.html http://www.dtic.mil/whs/directives/corres/pub%201.html

MIL-STD-

461F

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

10 Dec 2007 Entire

MIL-STD-

464A

Electromagnetic Environmental Effects Requirements for Systems

19 Dec 2002 Entire

MIL-STD-

1553B

Digital Time Division Command/Resp onse Multiplex Data Bus

21 Sep 1978 Entire

MIL-HDBK-

General Guidelines for Airborne Electronic Equipment

30 Nov 1995 Entire

MIL-STD-7080 Selection and Installation of Aircraft Electrical Equipment

31 May 1994 Entire

6.3 Appendix C: Technical Orders (T.O.s)

NUMBER DATE TITLE

00-5-1 14 Jun 16 Air Force Technical Order System

00-20-1 11 Jul 16 Aerospace Equipment Maintenance Inspection, 00-20-2 15 Mar 16 Documentation, Policies, and Procedures Maintenance Data Documentation

00-25-234 22 Sep 13 General Shop Practice Requirement for Repair, Maintenance and Testing of Electrical Equipment

1-1A-8 01 Jun 06 Engineering Manual Series Aircraft and Missile Repair Structural Hardware

1-1A-14 25 Apr 14 Install Practices for Aircraft Electrical and Electronics Wiring

1-1B-50 01 Aug 15 Basic TO for USAF Aircraft Weight and Balance

1-1-691 02 Nov 09 Aircraft Weapons System Cleaning and Corrosion Control

2.0 Services Summary: