About this file

Performance Work Statement Rev 2

View the file

Other files for this federal contract opportunity

Other files attached to Sustaining Engineering Services in Support of the Advanced Architecture Phase, Amplitude and Time Simulator (A2PATS), newest first.
File Type Posted
19-30178_JA.pdf PDF
Attach_1_-_PWS.pdf PDF
Attach_2_-_CDRLs.pdf PDF
FA8523-19-R-0008.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Indefinite Delivery Indefinite Quantity Performance Work Statement for A2PATS Sustainment Support Services

FD2060-19-30178

30-July-19

PREPARED BY: SYSTEM ENGINEERING PROCESS GROUP

ENGINEERING

EW/AVIONICS DIVISION

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

APPROVED BY:

JACKIE RINGLEY

EW TEST & EVALUATION

EW & AVIONICS SYSTEM PROGRAM OFFICE

Distribution Statement D: Distribution authorized to U.S. Government Agencies and their contractors (Critical Technical) (24 January 2013). Other requests for this document shall be referred to AFLCMC/WNKD, Robins AFB, GA 31098-5365. Questions concerning the technical content should be directed to AFLCMC/WNYE.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or the Export Administration Act 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violators of these export laws are subject to severe criminal penalties.

HANDLING AND DESTRUCTIVE NOTICE: Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

PR: FD2060-19-30178 PWS REVISION: 2

Distribution Statement: D

1.0 Description of Services

This Indefinite Delivery Indefinite Quantity (IDIQ) Performance-based Work Statement (PWS) defines the broad scope of services required to provide engineering sustainment support services for Textron Systems’ products and related support equipment in the AFLCMC/WNY Electronic Warfare Avionics Integration Support Facility (EWAISF). While the scope of this IDIQ PWS is broad in nature, the expertise required is specific to the support of Textron Systems’ products.

Engineering services required in support of the EWAISF’s Advanced Architecture Phase Amplitude and Time Simulator (A2PATS) network will entail, at a minimum, sustaining engineering services consisting of offsite repair of all A2PATS Circuit Card Assemblies (CCA) and components, A2PATS technology refreshes consisting of both hardware and software updates, system familiarization, parts obsolescence resolution, provision for basic test equipment kit to support the EWAISF A2PATS network, on-call support, onsite support when required, procurement of A2PATS Maintenance cabinets, Stimulus cabinets, Synthetic Stimulus Instruments (SSI) or CCAs contained therein, and A2PATS spares kits.

1.1 Specific Tasks

1.1.1 REPAIR SERVICES

The Contractor shall provide hardware and software repair services. Repair services shall consist of technical telephone services, parts repair evaluation, parts repair to include major and minor SSI repair, other repair, and occasional on-site hardware/software troubleshooting and/or repair support.

Contractor shall deem the repair Major, Minor, or Other based on the definitions below.

Synthetic Source Instrument (SSI) components:

- Harmonic Filter Assembly (HFA) 40324-41307-10

- RF Upconverter Assembly 40324-41305-10

- Band Expander Assembly 40324-41001-10

- RF Controller Assembly 40324-41015-10

Definition of Major Repair: Two of the four SSI components require repair.

Definition of Minor Repairs: One of the four SSI components require repair.

Definition of Other Repairs: Non-SSI related repair.

No A2PATS radio frequency (RF) port shall remain inoperable for greater than 10 consecutive business days when funding and parts are available.

The Contractor shall be available to provide repair technical support services Monday through Friday, 8:00 a.m. to 5:00 p.m. EST (except Federal Holidays) via telephone and/or email. A Repair Problem Report shall be created for each telephone and/or email occurrence and submitted as an attachment to the Monthly Status Report (MSR). (CDRL A001, DI- MGMT-80368A, Status Report)

Utilization of the offsite “Helpdesk” service (whether via email or telephone) will generate a Repair Problem Report for each incident. Incidents will be tracked through completion. All incidents shall be reported as status changes within the MSR. Maintenance data collection for repair parts shall be collected and maintained in like fashion. A summary of all incidents, open or closed shall be maintained for the duration of the Contract and updated monthly via the MSR.

Repair Problem Reports should include, at a minimum, the following information: part name, part number, serial number, date of failure, detailed repair action, failure location, repair facility’s evaluation results if available, date of repair, turnaround time (TAT), and other details deemed relevant to continuous process improvement. More often than not, the Repair Problem Report will be generated by the EWAISF’s on-site support personnel which will require the Contractor’s assistance to accurately complete.

The Contractor shall provide on-call repair support to the Government after telephone and/or email notification by the Technical Point of Contact (TPOC) indicating equipment is inoperative.

For urgent requests, the Contractor shall inform the TPOC within 48 hours of initial notification of the sub-system level fault, e.g., Run-Time Simulator, Stimulus Controller, SSI, etc., and proposed solution, and document in the Repair Problem Report.

When a component is returned for repair, the Contractor shall inspect, test and evaluate to determine the extent of the repair required to make the component ready-for-issue and ascertain all associated costs included in the repair for estimate purposes. The Contractor shall include a Beyond-Economical-Repair (BER) analysis in the evaluation which the EWAISF will set at 75% of the replacement cost for the item. For routine requests, the estimated cost for the repair/s will be proposed to the Government within 10 business days of receipt of component. Upon receipt of the repair estimate, the TPOC will make the decision of whether or not to proceed with the repair of the component. The Contractor shall provide parts and materials to repair and/or replace failed equipment unless stated otherwise. Once initial part repair evaluation is complete, if authorized by TPOC, the Contractor shall repair the part, perform functional testing and return repaired components to the EWAISF. First time repair shall restore Full Operational Capability (FOC) status 80% of the time. TATs from receipt of component to shipping and actual cost of the repair versus estimated repair cost shall be reported per individual repair and tracked in the MSR. The Contractor shall accomplish 90% of all repairs within 21 calendar days from date all required parts are available. (CDRL A001, DI-MGMT-80368A, Status Report)

The Contractor shall on occasion provide on-site repair services support to address maintenance actions beyond the scope of Helpdesk support and/or EWAISF onsite A2PATS support. On-site support shall include troubleshooting and corrective actions as required. This support shall be performed by a qualified Contractor technician. On-site support will be coordinated with the Contracting Officer’s Representative (COR).

1.1.2 MATERIALS

Materials generally refer to those materials required to assist in the repair of A2PATS components; however, replacement material for items that are considered BER or spares under the threshold of $250,000 may be acquired. Materials may be purchased individually or under package pricing, as negotiated between the Government and Contractor. In addition, the Government may purchase materials to augment/upgrade current capability, develop a pool of spares, or replace unrepairable components.

Shipping. The Contractor shall provide return shipping for items to be repaired as needed between Hunt Valley, MD and Robins Air Force Base (AFB), GA, or a designated destination provided in writing by the COR.

1.1.3 A2PATS Technology Refreshes and Upgrades

It is envisioned that the EWAISF’s A2PATS network will require various technology refreshes, additional Stimulus and Maintenance cabinets, initial spares kits, and CCA upgrades over the course of the IDIQ contract to support a growing mission within the EWAISF. The Contractor shall furnish all material, parts, components, engineering and technical services necessary to modify and/or develop variants of the A2PATS network. The Contractor shall provide internal and existing technical documentation required to support EWAISF operation and maintenance of any hardware or software modifications incurred through technology refreshes and/or A2PATS upgrades. (DI-IPSC-81443A, Software User Manual)

In the event of a technology refresh or significant A2PATS upgrade, the Contractor shall complete a Facility Acceptance Test Plan to ensure the EWAISF’s A2PATS continue to meet specifications. Completed upgrades/modifications shall be further tested and verified on the A2PATS network within the EWAISF through Contractor conducted onsite acceptance testing and subsequently documented in a Test/Inspection Report. (CDRL A002, DI-QCIC-80553A, Acceptance Test Plan) (CDRL A003, DI-NDTI-80809B, Test/Inspection Report)

1.1.4 TRAVEL

The Contractor may be required to travel during the performance of this contract to provide onsite support, attend meetings/conferences, and conduct training. The Contractor will be authorized travel expenses consistent with and no higher than the substantive provisions of the Joint Travel Regulation (JTR), Federal Acquisition Regulation (FAR) 31.205-46 Travel Costs, and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification of the COR, or if delegated, the TPOC. Each request shall be submitted prior to costs being incurred and a minimum of five business days in advance of departure. The Contractor shall courtesy copy the Procuring Contracting Officer (PCO) on all travel requests made to the COR or TPOC. All invoices for travel reimbursement shall be accompanied by supporting receipts. Each travel request shall minimally consist of:

Date of Request Employee(s) Date and duration of proposed travel Purpose of travel Destination Cost estimate (airfare, per diem, car rental, miscellaneous expenses) Total travel allowance on the CLIN at the request Total travel cost expended to date Approval signatures

Upon completion of each trip, the Contractor shall submit a trip report as an item referenced in the next delivered Monthly Status Report.

1.2 Objective(s)

It is envisioned that the work outlined in the description of services section will meet all of the sustainment support services required for the EWAISF’s A2PATS network within an agreed upon budget and schedule.

1.3 Benefit to United States Air Force (USAF)

The A2PATS network contributes to the EWAISF’s capability to more faithfully characterize signals used in modeling and simulation (M&S) of the EMS environment. Through rigorous Test and Evaluation (T&E) made possible by M&S, deficiencies are discovered which eventually lead to software and hardware updates of electronic equipment encompassed in the system under test (SUT). These updates usually result in increased aircraft survivability and more effective Electronic Warfare (EW) capabilities which ultimately support the mission of the USAF to fly, fight and win in air, space and cyberspace.

1.4 Background

USAF mandatory Program Management Directive (PMD) for Electronic Warfare Avionics Integration Support Program provided direction to develop and sustain system engineering and logistical support for EW system and software reprogramming. This capability is essential to maintain combat effectiveness of EW systems in the face of a changing threat environment. The EWAISF is the primary support facility in the development, configuration management, maintenance and testing of USAF EW system hardware, software and reprogramming support tools. EWAISF supporting activities are required to enact Air Force Instruction (AFI) 10-703, Electronic Warfare Integrated Reprogramming (EWIR). EWIR’s ultimate objective is the production and delivery of software and hardware changes to electronic equipment used to provide an awareness and response capability within the electromagnetic (EM) spectrum.

The EWAISF hardware-in-the-loop EW system test requires that generated threats signals have all the characteristics to accurately stimulate and meet the fidelity requirements of all EW systems which the EWAISF supports. This EWAISF testing involves M&S of the transmission and/or reception of adversary EM energy. In order to support additional M&S requirements, the

EWAISF took delivery of a Textron manufactured A2PATS in 2015.

The A2PATS provides exceptional signal fidelity in terms of coherency and coordinated phase-amplitude-time modulation of complex signals. All modulations are digitally applied, and every signal, at every frequency, is continuously aligned to maintain previously unobtainable port-to-port accuracies. The A2PATS offered unique capabilities derived from its innovative direct-port architecture, made possible by Textron’s internally developed and manufactured SSI. The SSI is a phase-coherent, wide-band (20 MHz – 22 GHz) Direct-Digital Synthesizer (DDS). The direct-port architecture of the A2PATS provides exceptional modularity and the EWAISF has taken advantage of this capability by procuring additional Maintenance cabinets thereby creating multiple A2PATS systems located throughout the EWAISF’s labs often referred to as the A2PATS network.

2.0 Services Summary

The Contractor service requirements are summarized into performance objectives that relate directly to the success of the mission. Unless indicated elsewhere these performance objectives will be measured quarterly. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

The following performance objectives listed in the Services Summary table will be utilized to evaluate the Contractor’s effectiveness in meeting the sustainment support services defined in the contact. Performance objectives will be evaluated quarterly in the form of Performance Assessment Reports (PAR). Re-performance of unacceptable services at no additional cost is the preferred course of action when appropriate. In the case of issued Corrective Action Reports (CAR), the PCO shall take appropriate measures according to the “Inspection of Services” clause.

SS# Performance Objective PWS Reference Performance Threshold

1. Contractor shall ensure the operability of each A2PATS RF port in the network

1.1 No one A2PATS RF port shall remain inoperable for greater than 10 consecutive business days when funding and parts are available.

2. Contractor shall perform repairs of failed/returned components consistently

1.1 First time repair shall restore FOC status 80% of the time. This metric will be calculated quarterly and per contract year.

3. Contractor shall perform repairs of failed/returned components in a timely fashion

1.1 Contractor shall accomplish 90% of all repairs within 21 calendar days from date all required parts are available. This metric will be calculated quarterly and per contract year.

4. Contractor shall provide written/verbal notification upon receiving A2PATS CCA/component

1.1 Contractor shall issue written notification of repairable/BER determination with estimate to the COR and/or COR designee (TPOC) within 10 business days of receipt of CCA/component for routine requests. (typical)

Contractor shall respond within 48 hours from initial notification with subsystem level fault and proposed solution, and document in Repair Problem Report in the event of urgent email/telephone notification.

(atypical)

5. Contractor shall provide accurate repair estimates

1.1 Actual repair costs shall not exceed 20% of the estimate more than three times over the course of the contract year.

6. Contractor shall provide timely and error free Monthly Status Reports

1.1, 4.2, 4.6, 4.7 11 out of 12 MSRs per contract year shall be received on time.

10 out of 12 MSRs per contract year shall not contain technical errors.

Any MSR containing technical errors shall be corrected and returned within five business days of notification.

7. Adherence to Contractor

QMS

5.9 Prior to contract/order award, the Contractor shall submit a QCP, for acceptance by the Government MFT. 100% compliance with the QMS is required.

8. Contractor Manpower Reporting

5.7 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.

The Contractor shall provide a count of contractor/subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

* A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and/or complete in accordance with the CDRL, PWS, or contract.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the FAR and as specified in the contract/order.

3.2 Government Property to be Provided: Government-Furnished Property (GFP) will include CCAs and other components shipped for repair.

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.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access To eTools.

3.5 Return or Retention of Government Property: All property provided by the Government remains 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 property for continued use under a successor contract. All Government property shall be returned 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.

4.0 Technical Requirements

The IDIQ contract will consist of a basic ordering period of 12 months plus four ordering periods that are 12 months duration each. Thus, the total ordering period for the IDIQ contract is 60 months. The Contractor shall perform individual tasks to the milestone schedule associated with each individual task order. In the event that an individual task does not specify a period of performance, the period of performance for that task will be 12 months after receipt of order (ARO). All work shall be completed within 78 months ARO the basic IDIQ contract.

4.1 Program Management

For each task order, the Contractor shall assign a Program Manager (PM) to manage the work required. The PM shall have overall authority and responsibility for performing all required work, which includes ensuring that all contractual deliveries as well as technical requirements are in compliance. The PM shall be the primary point of contact to the USAF regarding program and technical issues of this task; therefore, the Contractor shall identify the assigned PM and associated contact information to the USAF’s PCO, COR, and TPOC. The Contractor shall implement a financial tracking system to track expenditure of contract funds over the period of performance per task order and document in the MSR.

4.2 Monthly Status Report (MSR)

The Contractor shall prepare and deliver a status report on a monthly basis throughout the period of performance of each individual task order. In some instances with Government approval, it may be cost effective to combine multiple task orders into a single status report. In that particular case, the financial reporting shall be documented to clearly differentiate between the different task orders.

The report is to be used by the Contractor/Government team to verify attainability of program objectives, evaluate the progress of the Government and Contractor team toward meeting the program objectives, and to integrate program schedule among all related components.

The following types of information shall be included in the MSR:

• Simulator status information

• Summary of work accomplished and any recommendations or conclusions

• Documentation of all corrective maintenance tasks performed

• Problems encountered and proposed resolutions (Repair Problem Reports)

• Summary of estimated component repair costs

• Summary of actual material & labor costs versus estimated cost

• Trip reports for any contract related travel during the reporting period

(CDRL A001, DI-MGMT-80368A, Status Report)

PR: FD2060-19-30178 PWS REVISION: 1

4.3 Technical Interchange Meetings (TIM) and Program Reviews

The Contractor shall support, participate in, and as directed by AFLCMC/WNY, chair formal program reviews in accordance with the requirements defined herein as well as each individual task order. The Contractor shall conduct an Orientation Review within 45 calendar days ARO each individual task order placed under the IDIQ contract. TIMs will be scheduled by WNY on an as needed basis. The various program reviews shall alternate between the Contractor’s facility and the EWAISF unless otherwise approved by WNY. The Contractor shall deliver presentation material, formal agenda, and minutes for each review except as otherwise noted herein. Approval of the formal minutes by the contract’s COR shall constitute permission for the Contractor to continue with work as defined herein. A program schedule organized by Contract Work Breakdown Schedule (CWBS) shall be provided by the Contractor prior to each new task’s Orientation Review and shall be discussed at all subsequent reviews. The Contractor may combine program reviews with other reviews required to minimize cost. (CDRL A004, DI- ADMN-81249B, Conference Agenda) (CDRL A005, DI-ADMN-812505A, Conference Minutes) (CDRL A006, DI-ADMN-81373, Presentation Material) (CDRL 7, DI-MGMT- 81334D, Contract Work Breakdown Structure)

4.4 Period and Place of Performance

The Contractor shall perform the services in the PWS at the Contractor’s facility with occasional travel to Robins AFB, GA or other locations as deemed necessary during performance. The IDIQ contract for A2PATS Sustainment Support Services is expected to award in August of 2019 and will consist of a total of five ordering periods or 60 months.

4.5 Contract Data Requirements List(s) (CDRL)

Document Identifier

DID Title PWS Reference(s)

A001 DI-MGMT-80368A Status Report 1.1.1, 4.2 A002 DI-QCIC-80553A Acceptance Test Plan 1.1.3 A003 DI-NDTI-80809B Test/Inspection Report 1.1.3 A004 DI-ADMN-81249B Conference Agenda 4.3 A005 DI-ADMN-81250B Conference Minutes 4.3 A006 DI-ADMN-81373 Presentation Material 4.3 A007 DI-MGMT-81334D Contract Work Breakdown Structure 4.3

4.6 Quality of CDRL Deliverable

There shall be no more than one rejection of any deliverable. There shall be no more than two total rejections of deliverables per contract year. The Government may reject a deliverable containing any technical errors or three or more minor errors 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 exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

4.7 Receipt of CDRL Deliverable

CDRL deliverables may be submitted via Procurement Integrated Enterprise Environment (PIEE) / Wide Area WorkFlow (WAWF) or be submitted directly to the Multi-Functional Team (MFT) member identified on the CDRL. There shall be no more than one late submission(s) of deliverables per contract year. 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.8 Packaging

The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with Department of Defense (DoD) 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

4.9 Counterfeit Parts Prevention

The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronic parts being installed in end items or otherwise entering the USAF/DoD inventory.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis

The Functional Commander 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 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: DoD 5200.2-R, Personnel Security Program; DoD 5220.22-M;

DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual; and applicable Security Classification Guides as stated in the Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification.

5.2.2 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 comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.)

Government interests.

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

5.2.4 Security Clearance: The Contractor shall ensure applicable contractor/subcontractor personnel that intend to visit the EWAISF (229S) to provide sustainment support services for the A2PATS network have security clearance(s) at the secret level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the DD Form 254.

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.

5.2.6 Access to Government System(s): Access to Government system(s) will not be required to perform tasks under the contract/order.

5.2.7 Access to Robins Air Force Base (AFB): The Contractor shall ensure contractor/subcontractor personnel who require access to Robins AFB comply with the security requirements of the installation. The Contractor shall provide the PCO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.

5.2.8 Identification (ID) Card/Badge

5.2.8.1 The Contractor shall ensure an ID card is obtained by all contractor/subcontractor personnel who require recurring access to a Government facility, but not local area network (LAN) access. The Contractor shall submit a letter to the PCO listing all contractor/subcontractor personnel requiring access to the facility. The PCO will approve the request and forward it to the issuing/registration office for processing. Contractor/subcontractor personnel shall report to the issuing/registration office to obtain the ID card(s).

5.2.8.2 The Contractor shall submit a letter to the PCO immediately if contractor/subcontractor personnel no longer require access, upon transfer/termination of contractor/subcontractor personnel or upon completion/termination of the contract/order. The letter shall identify the name(s) and social security number(s) of the contractor/subcontractor personnel. The Contractor shall return the ID card(s) to the issuing/registration office upon expiration, upon transfer/termination of contractor/subcontractor personnel, or once contractor/subcontractor personnel no longer require access to the facility. The Contractor shall return any and all ID cards to the issuing/registration office upon completion/termination of the contract.

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

This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products;

therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, Public Law 91-596 as amended by Public Law 101-552 [Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

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 PCO are notified of mishaps. The Contractor shall contact the MFT (COR, if available, or TPOC) by telephone within eight business hours. The Contractor shall cooperate with Government safety investigations.

5.6 Inspection of Services

In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Contractor Manpower Reporting

In accordance with 10 United States Code 2330a, the Contractor shall provide an annual count of contractor/subcontractor personnel performing work for each fiscal year if the DoD is the requiring activity, if the acquisition is using U.S. Government appropriated funds, and if the acquisition is in excess of $3,000,000.00. The Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract in the Enterprise-wide Contractor Manpower Reporting Application (eCMRA).

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 shall establish a record for the contract/order in eCMRA no later than 30 calendar days after contract/order award. The Contractor shall enter Order Data, Contact Data and Location Data.

5.8 Invoicing/Payment and Receipt/Acceptance

The Contractor shall submit/process payment requests and receipt/acceptance documents via

PIEE) / WAWF.

5.9 Quality Management System (QMS)

The Contractor shall ensure the quality of services through a quality and/or inspection system.

Prior to contract/order award, 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. 100% compliance with the QMS is required.

5.10 Trafficking in Persons

The Contractor shall comply with the requirements of FAR 52.222.50, Combating Trafficking in Persons.

6.0 Appendices

6.1 Appendix A, Reference(s)

Publication Title of Publication Date of Publication Sections(s) that Apply

DoD 5220.22-M

National Industrial Security Program Operating Manual

(NISPOM).

February 28, 2006 Change 1 - March 28, 2013

5.2

DoDD 4715.1E

Environment, Safety, and Occupational Health (ESOH) March 19, 2005 5.5

DoDD) 5205.02E

DoD Operations Security (OPSEC) Program June 20, 2012 5.2

DoD Manual 5205.02-M

DoD Operations Security (OPSEC) Program Manual November 3, 2008 5.2

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

Occupational Safety and Health Act of 1970 December 29, 1970 as amended through January 1, 2004

5.5

File details come from the government source that posted it.