PWSdtd1jul2020.pdf

PR: FD2060-20-31109 PWS REVISION: 0

Distribution Statement: D

Performance-Based Work Statement for

Radar Warning Receiver (RWR) Programs Enterprise Integrated Support Station (ISS) Contract

Purchase Request: FD2060-20-31109

July 1, 2020

Distribution Statement D: Distribution authorized to U.S. Government Agencies and their Contractors (Critical Technical) (15 July 2013). Other requests for this document shall be referred to AFLCMC/WNYKB, 235 Byron St., Ste. 19A, Robins AFB, GA 31098-1670.

Questions concerning the technical content should be directed to AFLCMC/WNY.

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 DESTRUCTION NOTICE: Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

1.0 Description of Services

1.1 Objective(s): The purpose of this Performance-Based Work Statement is to provide for contract engineering services and technical support for the F-15 Tactical Electronic Warfare System (TEWS), AN/ALR-56M/56C Radar Warning Receiver (RWR) Integrated Support Station (ISS) and other interfaced systems and processes. The Contractor shall provide efforts required for engineering support for the RWR and associated software tools for the United States Air Force (USAF). The Contractor shall ensure that all delivered products meet the requirements as specified in this contract, including this PWS and Contract Data Requirements List (CDRL).

The scope of engineering support required is outlined by the work requirements set forth in Paragraphs 2.0 and 4.0.

The Contractor shall 1) Support, maintain, and upgrade RWR ISS hardware, software, and associated systems; 2) provide Independent Verification and Validation (IV&V) of Operational Flight Program (OFP), Mission Data File Generator (MDFG) software, and associated documentation for the RWR that is compatible with the Suite Avionics software load updates; 2) provide support for transition to organic software development; 3) assist the Government with future block cycle planning and conduct software project planning for the next OFP/MDFG block cycle; 4) provide radar characterization support, test and prime equipment support, and sustaining engineering support and provide interface to Combat Electromagnetic Environment Simulator (CEESIM) for integrated testing in a Radio Frequency (RF) dense environment.

1.2 Benefit to United States Air Force (USAF): The Contractor shall support AFLCMC/WNY, the Product Group Manager (PGM) for the RWR Systems, by participating in all phases of the multi-year sustainment effort. The end goal is to provide cost-efficient, quality software and hardware solutions that can be fielded in a timely manner and support the USAF and Foreign Military Sales (FMS) mission. AFLCMC/WNY is the overall system technical authority and has Operational Safety, Suitability and Effectiveness (OSS&E) responsibility. AFLCMC/WNY has program management responsibilities for all RWR Systems in its portfolio. All deliverables generated under tasks issued under this contract shall be forwarded to AFLCMC/WNY for final inspection and acceptance, unless otherwise specified. Copies of all transmittal letters, by which work products are forwarded to AFLCMC/WNY, shall be sent to the Procuring Contracting Officer (PCO) and to the appropriate Administrative Contracting Officer (ACO). Final inspection and acceptance of hardware items generated under tasks issued under this contract will be made by AFLCMC/WNY Lead Engineer. Shipping instructions, will be defined by AFLCMC/WNY as required. The Contractor shall not place any proprietary restrictions or markings on deliverable software, documentation, or other work products other than Commercial-Off-The-Shelf (COTS) products, except as explicitly approved by AFLCMC/WNY.

All work hereinafter specified shall be performed in the most economical and expeditious manner by skilled personnel and shall be in conformance with the highest engineering standards and practices.

1.3 Background: The RWR Systems is the system installed on the multiple DOD aircraft platforms that require engineering support. The Contractor shall provide a full range of program and support management, software development, program security, test & evaluation, and configuration management for RWRs and associated support systems. The Electronic Warfare Avionics Integrated Sustainment Facility (EWAISF) is responsible for ensuring the RWR

Systems is fully tested prior to releasing software updates. The ISS is the main software development station which is used in conjunction with the CEESIM RF threat generator. The Contractor shall perform tasks using Operation and Maintenance (O&M) 3400 funds and Research, Development, Test, and Evaluation (RDT&E) 3600 funds. The Contractor shall maintain AS9100 or industry equivalent Quality Management System (QMS) certification.

2.0 Services Summary

Performance Objective PWS Reference

Performance Threshold

Identify and Document ISS Required Changes

4.0.1 95% of ISS problems or issues shall be documented in problem trouble reports (PTR) within five business days of discovery. The remaining 5% shall be documented within 10 business days. This metric will be calculated per contract year.

PTRs shall be technically accurate and in sufficient depth for understanding.

ISS software updates 4.0.1 90% of software changes shall pass testing and be documented within five business days after changes have been demonstrated to the satisfaction of the user. The remaining 10% shall be allowed one rework per update to be completed within 15 business days and shall be documented within five business days after changes have been demonstrated to the satisfaction of the user. This metric will be calculated per contract year.

Request for assistance 4.0.2 The Contractor shall initially respond to a request for assistance within 48 hours. Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

Deviation from the cost or schedule as defined by the monthly status report

4.2.1.1 The Contractor shall deviate no more than 10% from

the cost and schedule baselines. If cost or schedule deviates more than 10% from the baseline, then the Contractor shall be in non-compliance. This metric will be calculated per month.

Submission and Receipt of CDRL Deliverable

4.2.2 Contract Data Requirements List (CDRL)

deliverables shall be submitted via Procurement Integrated Enterprise Environment/Wide Area Workflow (PIEE/WAWF) and be submitted directly to the Multi-Functional Team (MFT) member identified on the CDRL. The CDRL will determine submittal requirements. There shall be no more than five late receipt(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.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR), all other applicable Government regulations and as specified in the contract/order.

3.2 Government Property to be provided: Government property to be provided includes access to facilities, equipment, software and documentation when necessary for the Contractor to perform under the requirements of this contract. The Government will make all equipment in the AN/ALR-56M and F-15 TEWS Engineering Laboratories within the EWAISF laboratory available on a shared, non-interference basis with other on-going activities. Equipment utilization will be jointly planned on a weekly basis. All equipment and/or Government personnel are subject to being allocated to other higher priority projects on a no notice basis.

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 Government-Furnished Property (GFP) in the Item Unique Identification (IUID) Registry. Government property shall be listed as a GFP attachment and created as a fillable document at http://dodprocurementtoolbox.com/.

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 in the Government-Furnished Property (GFP) Module of PIEE.

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 by the PCO, 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 http://dodprocurementtoolbox.com/ contract/order becomes the property of the Government and shall be returned to the Government as directed by the PCO, 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 Contractor shall, in general, adapt and perfect the performance of the ISS and shall specifically:

A. Assist Government personnel in a MFT approach to identify and fix ISS software deficiencies, enhance existing capabilities, add new capabilities, and produce documentation.

B. Track and document the status of ISS changes using Project Task Requests (PTR).

C. Provide technical assistance and instruction to Government personnel as necessary in the day-to-day operation of the ISS systems, subsystems, components, interfaces, and connections to enhance the Government’s organic ability to independently make changes to perfect the ISS testing environment.

D. Develop a comprehensive Combined Software Development and Configuration Management Plan (CSD&CMP) to provide processes and procedures for control and accountability over ISS changes.

E. Establish and convene a Configuration Control Board (CCB) which has the overall change management responsibility for all established PTRs, including reviewing, determining priorities, maintaining status, and providing recommendations for PTRs.

F. Generate and submit general and/or special status reports as required.

G. When tasked by the Government, the Contractor shall maintain, repair, or replace hardware components of the ISS, as well as, purchase components required for ISS upgrades.

H. Update and maintain ISS software to the CEESIM interface to control hardware resources for generating RF signals into the 56M system.

4.0.1 Identify, Document and Make Required ISS Changes: Through normal day-to-day utilization of the ISS with Government personnel, the Contractor or Government personnel will identify ISS problems or issues. The Contractor shall document the related problems as PTRs.

After the PTRs and associated evaluations are reviewed as a function of the configuration Management Process, and based on Government direction, the Contractor, shall remedy, test, and demonstrate the problem correction to the Government. This includes updating ISS configuration item documentation. The Contractor shall:

A. Assist Government personnel as required in the day-to-day utilization of the ISS systems to identify anomalies, investigate, and document recommended changes to the ISS and associated support equipment to increase its utility and usability.

B. Update existing documentation as necessary to maintain program continuity.

C. Maintain a Project Workbook containing “working” documents and other pertinent documents as specified in the PWS.

D. Identify the ISS changes required to support any proposed AN/ALR-56M, F-15 TEWS, and related system changes.

E. Determine capabilities which fall short of the functional requirements manifested through experience with the ISS in its role of supporting the AN/ALR-56M, F-15 TEWS and related systems.

F. Analyze data collection capabilities that are incompatible with changed AN/ALR-56M, F- 15 TEWS, and related system hardware and software.

G. Adapt the ISS database engine to remain compatible with changed AN/ALR-56M, F-15 TEWS, and related system hardware and software.

H. Add data collection capabilities to speed the investigation of AN/ALR-56M, F-15 TEWS, and related system problems. These additions may include the addition of new tables, queries, and reports that are compatible with AN/ALR-56M, F-15 TEWS, and related system changes.

I. Optimize software algorithms and test methodologies to increase performance and reduce the risk of unexpected or inadequate results.

J. Design capabilities to perfect the ability of the ISS or associated support equipment to support AN/ALR-56Mand F-15 TEWS closed-loop testing.

K. Correct software problems with the RF stimulus equipment installed within the ISS and with the ISS interfaces to the stimulus equipment.

L. Adapt software to analyze the data collected with the ISS and associated support equipment.

M. Identify the ISS changes to improve the reliability of the ISS to support overnight, unattended testing activities.

N. Identify ISS software incompatibility due to CEESIM OS or hardware updates.

O. Operate in an MFT environment by involving Government personnel in the thought processes, design, coding, and documentation of an ISS change; i.e., in every step of the way, from conceptualization to implementation, of any approved PTR.

P. Travel may be required to support engineering evaluation.

Q. Address issues identified in AN/ALR-56M, F-15 TEWS, and related system related PTRs.

These activities shall include investigation of identified issues, preparing corrective actions, prototyping activities to quantify the effectiveness of candidate corrective actions, and installing and testing final corrective actions. The following testing documentation/procedures are required:

1) Non-deliverable test procedures and test reports shall be documented and prepared for each PTR, as applicable.

2) These procedures and reports shall be kept electronically on a Government computer associated with the ISS.

3) Government personnel shall be allowed to review a PTR’s test report and execute a PTR’s associated test procedures before a PTR is signed and closed by the Government.

Ninety-five percent (95%) of ISS problems or issues shall be documented in problem trouble reports (PTR) within five business days of discovery. The remaining 5% shall be documented within 10 business days. This metric will be calculated per contract year. PTRs shall be technically accurate and in sufficient depth for understanding to the satisfaction of the user.

Ninety (90%) of software changes shall pass testing and be documented within five business days after changes have been demonstrated to the satisfaction of the user. The remaining 10% shall be allowed one rework per update to be completed within 15 business days and shall be documented within five business days after changes have been demonstrated to the satisfaction of the user. This metric will be calculated per contract year.

4.0.2 Provide Technical Support for ISS Daily Operation: One of the goals of this contract is to enable Government personnel to independently operate the ISS in any configuration and to become more self-sufficient in utilizing the many features of the ISS to effectively test changes made to the AN/ALR-56M, F-15 TEWS and related systems. To meet this goal, the Contractor shall:

A. Provide hands-on demonstrations as required to any Government personnel who are not familiar with the operation of the ISS and its components and interface connections.

B. Provide hands-on demonstrations as required to any Government personnel who are not familiar with the operation of the ISS operating system and explain how to perform testing under all scenarios and how to utilize all the various software capabilities of the system.

C. Work in an MFT environment as much as possible and apply principles of systems engineering to determine the most effective approach to perform new and innovative testing requirements.

D. Respond to a request for assistance within 48 hours. Follow-up assistance, if required, shall be provided by the suspense date acceptable to the Government.

4.0.3 Provide Technical Support in the Continued Development of an Auto Test Tool (ATT): An additional goal of this contract is to enhance the ability of Government personnel to operate the ISS with greater efficiency and with greater test coverage for the software/hardware systems under test through the implementation and use of an Auto Test Tool. Said test may be geared toward development, flight or release testing of the software/hardware in any configuration with a goal to become more self-sufficient in utilizing the many features of the ISS and ATT to effectively test changes made to the F-15 TEWS and related system. To meet this goal, the Contractor shall:

A. Provide support for organic development, implementation maintenance of an ATT capability for the F-15 TEWS lab as directed by AFLCMC/WNY to increase test efficiencies for new hardware/software products within the F-15 TEWS, and related systems.

B. Maximize ATT’s use of existing SW and test products currently in use on other USAF programs within the lab area.

C. Ensure the ATT tool is tailored toward the specific needs of the related systems as they evolve.

D. Enhance the automation of the test efforts in relation to the specific functions F-15 TEWS and related system and support equipment in use by the Government.

4.0.4 Provide IV&V of OFP, MDFG, and related system software: Due to the continuously evolving electronic warfare environment, the AN/ALR-56M and F-15 TEWS system software must undergo updates to resolve potential operational deficiencies. These modifications to the OFP, mission data, mission data generation software, and related systems require IV&V prior to final release of the software. To support IV&V efforts for the RWR, the contractor shall:

A. Review documentation changes and updates which relate to the RWR software.

Documents shall be reviewed for completeness and accuracy, and to verify that the version release requirements are accurately documented and match the code implementation.

B. Perform software testing to demonstrate that the RWR software is, or is not, reasonably free of serious errors and meets the requirements of the version release. The Contractor shall examine test results and identify deficiencies in the system. In the event that a deficiency is discovered, the Contractor shall document the conditions under which the deficiency was discovered in a software test report. (CDRL A00A DI-IPSC-81440A/T, Software Test Report)

C. The Contractor shall diagnose errors and recommend changes to the system software where the source of the deficiency is evident from the test results.

4.0.5 Provide ISS Software Development and Configuration Management: As the AN/ALR- 56M, F-15 TEWS, and related system matures on its varied operational platforms, the software changes shall drive new configurations of the ISS systems. In order to allow the ISS systems to support the potentially varied configurations, the Contractor shall:

A. Update the existing Software Development Plan (SDP), and ensure the plan describes the software development procedures and the configuration management of the ISS systems and defines the processes and procedures by which all identified problems are documented, tracked and reported. (CDRL: A001 DI-IPSC-81427A, Software Development Plan)

B. Create a Software Version Description (SVD) for the current version(s) of the ISS. The SVD shall be updated whenever the version changes as determined by the configuration management process. (CDRL: A002 DI-IPSC-81442A, Software Version Description)

C. Participate in Configuration Control Board (CCB) meetings as required with Government personnel. These meetings will be used to communicate the current technical status of all on-going PTRs and to assign PTR priorities. Proposed PTRs will also be discussed and categorized (e.g., Open, Investigate, and Discard). Meeting minutes shall be included in the Status Reports. (CDRL: A003 DI-MGMT-80368A Monthly Status Reports)

Table of Product Documents

Identifier

Previous Delivery Date Title 1H754-A002-RU1001-- 26 Jul 2007 F-16 Simulation Software

Design Document for the

Northrop Grumman Technical Services

AN/ALR-56M(V) Radar Warning Receiver Integrated Support Station (ISS)

1H754-A004-RU1003--

Northrop Grumman Technical Services

15 Jun 2007

Interface Design Description (IDD) for the AN/ALR-56M (V) Radar Warning Receiver Integrated Support Station.

1J268-A005-RU1007--

Northrop Grumman

16 Apr 2008

Technical Report - Study/Services for the Express Version of the AN/ALR-56M(V) Radar Warning Receiver Integrated Support Station (ISS)

1H754-A006-RU1005--

Northrop Grumman

27 Jul 2007

ISS Express Software Design Description (SDD) for the AN/ALR-56M(V) Radar Warning Receiver Integrated Support Station (ISS)

1J268-A007-RU1009--

Northrop Grumman

16 Oct 2007

Software Development Plan (SDP) for the AN/ALR56M (v) Advanced Radar Warning Receiver Integrated Support Station (ISS) Engineering and Technical Services Program.

1J268-08-002 25 Jul 2008 ALR-56M ISS Data package/schematics (Draft)

1H754-A003-RU1002-01

Northrop Grumman Technical Services

27 Jul 2007 Software Version Description (SVD) for the ALR-56M Integrated Support Station

F-15 TEWS ATT related documents shall be maintained once created

None

Under Development

4.0.6. Status Reports: The Contractor shall generate and submit to the Government monthly status reports, which shall consist of data from products normally produced by the Contractor for his internal use. These reports shall be submitted by the 15th of the following month. (CDRL:

A003 DI-MGMT-80368A Monthly Status Reports)

A. Projected program spending profile (cumulative dollars by month) B. Actual costs incurred C. Estimated cost at completion D. A summary of the prior period's activities E. Report of the number of PTRs and their current status F. Identification of potential problems, concerns and enhancements G. Minutes of any Program/Technical Reviews H. Minutes of CCB meetings

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the IDIQ contract/order will extend for 57 months with a basic for nine months from 30 Sep 2020 – 30 Jun 2021 and 4-12 months ordering periods from 29 Jun 2021 – 30 Jun 2025 after receipt of contract award.

4.1.2 Place of Performance: This engineering services support will be performed at AFLCMC/WNY EWAISF Laboratory and the Contractor’s facilities.

4.2 Contract Data Requirements List(s) (CDRL)

The Contractor shall prepare new and updated documentation for the ISS systems, including updates to existing documentation needed as a result of changes by the Contractor or MFT, and additional documentation prepared as a result of the changes to the ISS. The Contractor shall prepare new documentation, and updates to existing documents to the same format and contents as documentation delivered under the previous ISS contract.

Specific documentation that shall be updated and maintained by the Contractor shall include, at a minimum, the documents listed below.

Document Identifier

DID Title PWS Reference(s)

A001 DI-IPSC-81427A Software Development Plan 4.0.5 A002 DI-IPSC-81442A Software Version Description 4.0.5 A003 DI-MGMT-80368A Monthly Status Report 4.0.5, 4.0.6 A004 DI-IPSC- 81435A Software Design Description 4.0.5 A005 DI-MISC-80508B Technical Report-Study/Services 4.0.5 A006 DI-IPSC-81443A Software User’s Manual 4.0.5 A007 DI-SESS-81002F Developmental Design Drawings/Models and

Associated Lists 4.0.5

A008 DI-ENVR-81840 Programmatic Environmental Safety and Health Evaluation (PESHE) Plan

5.5.2

A009 DI-IPSC-81436A Interface Design Description 4.0.5 A00A DI-IPSC-81440A/T Software Test Report 4.0.4

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any single deliverable. There shall be no more than a total of five rejection(s) of deliverables per contract year.

The Government will reject a deliverable if any technical errors or five 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 exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 15 business days of notification of Government rejection.

4.2.1.1 Contractor shall deviate no more than 10% from the cost and schedule baselines. If cost or schedule deviates more than 10% from the baseline, then the Contractor shall be in non-compliance. This metric will be calculated per month.

4.2.2 Submission and Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via PIEE / WAWF and be submitted directly to the MFT member identified on the CDRL. The CDRL will determine submittal requirements. There shall be no more than five late receipt(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.3 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as directed by the Contractor. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.4 Travel: Travel requests for contractor/subcontractor 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. Receipts must be presented with the invoice for reimbursement of actual travel costs.

5.0 General Information

5.1 Continuation of Mission-Essential Support 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 all applicable Government 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.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 Department of Defense Directive (DoDD) 5205.02E, DoD OPSEC Program, and DoD Manual 5205.02, DoD OPSEC Program Manual, to protect United States (U.S.)

Government interests. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

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 all applicable contractor/subcontractor personnel have security clearances at the appropriate level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification.

Contractor/subcontractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and classified items.

5.2.5 Security Incident or Violation: The Contractor shall notify the Government Contracting Activity and the Government Security Office within 48 hours of any incident involving the actual or suspected compromise/loss of classified information to enable the Government to conduct immediate assessments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW DFARS Clause 252.204-7012.

5.2.6 Security of Contractor System(s): The Contractor shall ensure the security of Automated Information System(s) (AIS) at the Contractor’s facility to preclude all potential security incidents or violations including potential unauthorized disclosure or compromise of classified information and/or CUI in accordance with DoD 5220.22-M and all other applicable Government regulations.

5.2.7 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.8 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.9 Identification (ID) Card/Badge

5.2.9.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.9.2 The Contractor shall ensure contractor/subcontractor notify the PCO immediately if they lose their ID card(s).

5.2.9.3 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.2.10 Common Access Card (CAC)

5.2.10.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DOD computer networks/systems, for DOD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

5.2.10.2 The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

5.3 Environmental Management System (EMS): Contractor/subcontractor personnel who perform work on any Government facility shall comply with the EMS requirements established by the facility. Contractor/subcontractor personnel may be required to complete EMS training prior to beginning work.

5.4 Agency Affirmative Procurement Programs: In accordance with FAR 24.4004, 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.

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

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with all applicable Government regulations including, but not limited to, 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). The Contractor shall be solely responsible for the protection of their employees and the safety and health of all subcontractor employees. The Government will assume no liability or responsibility for the Contractor's compliance or non-compliance with such requirements. The Contractor shall furnish to each of his/her employees a place of employment, which is free from recognized hazards. The Contractor shall brief his/her employees on the safety requirements of this contract and on hazards associated with prescribed tasks In addition, the Contractor shall flow down the safety requirements/specification to all subcontractors.

5.5.2 Safety and Health Plan/Program: If the Contractor does not have a Safety and Health Plan previously and currently approved by the MFT, they shall submit a Safety and Health Plan as indicated by CDRL instructions. The Contractor shall establish and maintain a safety program in accordance with the contract/order, all applicable Government regulations including, but not limited to, OSHA and ESOH, and the Safety and Health Plan. (CDRL: A008 DI-ENVR-81840 Programmatic Environmental Safety and Health Evaluation (PESHE) Plan)

5.5.3 Mishap Notification/Investigation: The Contractor shall report mishaps including involving damage or injury 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 another MFT member) by telephone within four (4) 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 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. CDRL deliverables shall be submitted using PIEE/WAWF and be submitted directly to the applicable MFT member. The CDRL will determine submittal requirements.

5.9 Quality

5.9.1 Quality Management System (QMS): The Contractor shall ensure the quality of services through an internal quality and/or inspection system. The QMS should address 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 QMS should include a schedule of quality assurance/control inspections.

5.9.2 Quality Standard(s): The Contractor shall maintain AS9100 or industry equivalent QMS certification.

5.10 Trafficking in Persons: The Contractor shall comply with all applicable Government regulations including, but not limited to, 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 2 – May 18, 2016

5.2.1

DoDD 4715.1E

Environment, Safety, and Occupational Health

(ESOH)

March 19, 2005 Change 1, August 31, 2018

5.6.1

DoDD) 5205.02E

DoD Operations Security (OPSEC) Program June 20, 2012 Change 1, May 11, 2018

5.2.1

DoD Manual 5205.02

DoD Operations Security (OPSEC) Program Manual

November 3, 2008 Change 1, April 26, 2018

5.2.2

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

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

5.6.1