LARS_PD_13July23.pdf

PR: FD2060-23-30076 PD 1

Distribution Statement: C

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

Product Description

FOR

HC-130J Lightweight Airborne Recovery System (LARS) Software Update

FD2060-23-30076

28 June 2023

Prepared by:

Teresa D. Watson

AFLCMC/WIUAB

370 Richard Ray Blvd

Robins AFB, GA 31098-1670

PR: FD2060-23-30076 PD 2

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use; 20-11-20). Other requests for this document shall be referred to AFLCMC/WIUAB, Robins AFB, GA 31098-1670.

TABLE OF CONTENTS

SECTION TITLE PAGE

SECTION 1 PRODUCT DESCRIPTION 3

SECTION 2 PRODUCT SUMMARY 3

SECTION 3 TECHNICAL REQUIREMENTS 6

SECTION 4 GENERAL INFORMATION 11

SECTION 5 APPENDICES 14

PR: FD2060-23-30076 PD 3

1.0 Product Description

1.1 Objective(s): This Product Description (PD) describes the services required to upgrade the HC-130J Lightweight Airborne Recovery System (LARS) Software V2.3 applicable on all thirty-nine (39) HC-130J aircraft. These services include enhancing the capabilities of the LARS system to allow the Combat Systems Operator (CSO) to make operations faster and more user friendly and make it easier to pass information to the rest of the air assets when information is received on this system.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by making operations faster and more user friendly, so it is easier to pass information to the rest of the air assets when information is received on this system, therefore resulting in more saved lives.

1.3 Background: The current HC-130J Lightweight Airborne Recovery System (LARS) V2.3 does not have the current ability to display coordinates in Military Grid Reference System (MGRS), tune to every 406 Search and Rescue Satellite Aided Tracking (SARSAT) beacon frequency, retain encryption keys in memory, or retain messages from the survivors once a new message is received. This task saturates the CSO to convert coordinates to MGRS from DD.MM.SS.SS, input the encryption key every time LARS crashes, and write down every piece of information from the survivor before another message can be viewed. MGRS Coordinates are the primary coordinate format for every player that conducts Combat Search and Rescue (CSAR). The CSO is the single point of failure on the HC-130J regarding LARS as there is only one LARS Control Interface Unit (CIU) located at the CSO station. The software should be changed to allow the CSO to make operations faster and more user friendly, so it is easier to pass information to the rest of the air assets when information is received on this system.

2.0 Product Summary:

2.1 This Product Description (PD) establishes the Contractor's responsibility for providing an upgrade to the current LARS V2.3 software which will include but is not limited to:

• making MGRS the primary/default coordinate format.

• providing operator ability to input a SARSAT frequency instead of having to keep adding additional frequencies.

• adding “encryption key” into LARS memory to prevent loss of keys if the system crashes or is turned off (basically it will hold the 10 encryption keys).

• adding the capability to store messages in memory for each survivor indefinitely, thereby eliminating the auto delete function once a message is viewed; this keeps the data from being lost forever.

2.2 It is anticipated this software will consist of custom developed codes, non-developmental codes, and LARS licensable code; all integrated to provide the functionality the mission requires.

Additional tasks include the delivery of data, reports and other supporting technical materials as required.

PR: FD2060-23-30076 PD 4

2.3 The contractor shall provide personnel, services, and material; the contractor shall be responsibile for updating and supporting current and future software version(s), Contract Data Requirements Line Data and travel per the Joint Travel Regulations (JTR).

2.4 The contractor shall provide the personnel necessary to perform software support, iterative software releases, minor improvements, and system modernization, in addition to other customer specified requirements as agreed uponby the contractor and program office.

2.5 The contractor shall assist the Government and subcontractors with the installation, troubleshooting, and verification of existing and future deliverable software suites and hardware in which the contractor is associated with. The contractor shall conduct system performance analysis and checkouts as agreed upon, and shall investigate technical issues, identify solutions, and make recommendations for product enhancements. Support services may be delivered via telephone, technical report, product replacement, provision of field service personnel, any combination thereof, or other appropriate means. All support services executed under this PD shall be coordinated in advance with the Government.

Performance Objective PD Reference

Performance Threshold

Quality of Lightweight Airborne Recovery System (LARS) Software Plan

4.2.3.7 Contractor shall deliver a Software Development

Plan (SDP) no later than sixty (60) days after award of contract.

Quality of CDRL deliverable 4.2.1 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 12 month award period. The Government will reject a deliverable if two (2) or more technical errors or three (3) or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within ten (10) business days of notification of Government rejection.

Receipt of CDRL Deliverable

4.2.2 There shall be no more than two (2) late

submission(s) of deliverables per 12 months.

3.0 Government Property

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

3.2 Government Property to be Provided: Government property to be provided for the Lightweight Airborne Recovery System (LARS) Software Upgrade program includes:

• Receiver/Transmitter Unit, Part Number 282650-3

• Control Display Unit, Part Number 282950-1.

PR: FD2060-23-30076 PD 5

3.3 Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://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 GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

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 Procuring Contracting Officer (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.

3.6 The Contractor shall identify a Program Manager and Deputy Program Manager to serve as a single focal point to interface with the Government and associate Contractors. Finance and Contracting personnel shall provide support to the required Program Management functions.

Contractor Program Management shall track program cost, schedule and overall performance to ensure software releases are successfully completed. The Contractor shall report current program status in the Monthly Program Status Reports. The report shall include, as a minimum, schedule, https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/

PR: FD2060-23-30076 PD 6

financial status, the status of software engineering, material procurement and associated issues, and cost status. The Contractor shall immediately notify AFLCMC/WIUKA of any projected schedule delays. The Contractor shall accept contract direction only from the AFLCMC/WIUKA Contracting Officer (CO) for specific areas of contract responsibility. Daily technical and programmatic issues shall be coordinated through the AFLCMC/WIU Program Manager.

(CDRL A001/B001, DI-MGMT 80368A, Program Monthly Status Reports (MSR)).

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract Period of Performance: The period of performance for the contract is a 24-month contract, 1 year basic contract plus 1 option year, after the award of the contract and will be completed by bluesuiters as mission and aircraft availability allows.

4.1.2 Place of Performance: These services will be performed at each base location by blue-suiters by attrition as the mission/flight schedule and workload permits.

4.2 Contract Data Requirements List (CDRL):

Document Identifier

2 year Base

Out Year Option Year 1

DID Title PD Reference(s)

A001 B001 DI-MGMT-80368A Program Monthly Status Reports

(MSR)

Para 3.6

A002 B002 DI-IPSC-81427B Software Development Plan (SDP) Para 4.2.3.7

A003 B003 DI-ILSS-80872 Training Material Para 4.2.7 A004 B004 DI-IPSC-81442A Software Version Description

(SVD)

Document (Release Notes)

Para 4.2.3.10 Para 4.2.5

A005 B005 DI-IPSC-81443A Software User Manual (SUM) (Per Release)

Para 4.2.5

A006 B006 DI-IPSC-81488 Computer Software Product (Tech Data)

Para 4.2.3.13

A007 B007 DI-SAFT-81563 Accident/Incident Report

Para 5.5.2

A008 B008 DI-QCIC-80553A Acceptance Test Plan Para 4.2.3.12

A009 B009 DI-MGMT-81845/T Information Assurance (IA) Design Review Information Package (DRIP)

Para 4.4

A010 B010 DI-MGMT-81844/T Information Assurance (IA) Test Plan

Para 4.4

A011 B011 DI-MGMT-81843 Information Assurance (IA) Test Report

Para 4.4

PR: FD2060-23-30076 PD 7

A012 B012 DI-MISC-80508B/T Technical Report – Study Services Para 4.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 12 month award period. The Government will reject a deliverable if two (2) or more technical errors or three (3) 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, PD 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.2.2 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Wide Area WorkFlow (WAWF) or Procurement Integrated Enterprise Environment (PIEE) 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 12 months. 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.2.3 Modification Details: The LARS Software shall be defined as the software developed to support all systems that interacts with it directly or indirectly on the HC-130J.

4.2.3.1 The Contractor shall provide program, technical, and software engineering management and system integration support to the Government. The Contractor shall provide all necessary labor, materials, and facilities required to perform the work described by this PD and meet the delivery requirements set forth by this PD. Any assistance, materials, and facilities to be provided by the Government, shall be as stated herein.

4.2.3.2 The contractor shall provide troubleshooting, verification, and evaluations of software releases as required. Travel may be requested and approved by program office as necessary. Test support requirements shall be identified in a timely manner permitting the Government to approve and schedule the required support.

4.2.3.3 Based on program requirements; The Contractor shall provide recommendations concerning optimization of the system software design, system software, and software requirements as applicable. The Contractor shall be responsible for final integration of the software upgrade to include but not limited to debugging, testing, troubleshooting, technical assistance, and documentation.

4.2.3.4 Contractor shall incorporate all previously developed software releases as required to meet the overall system’s intent. Subsequent versions shall provide more product maturity than the preceding software release. Contractor shall establish software releases corresponding to the schedule set-forth by the program office.

PR: FD2060-23-30076 PD 8

4.2.3.5 The Contractor shall analyze functional requirements and devise a design approach that is balanced between design constraints, risk aversion, and overall system capability.

4.2.3.6 The Contractor shall establish software releases that deliver new Government derived requirements and correspond to the schedule set-forth by the program office. The Contractor shall test and provide, as required, updates to ensure the fielded software functions appropriately and meets Information Assurance (IA) configurations for the mission system.

4.2.3.7 The Contractor shall deliver a Software Development Plan (SDP) no later than sixty (60) days after award of contract. The SDP shall document a software process that is balanced across design constraints, risk aversion, and overall system capability. (CDRL A002/B002, DI-IPSC- 81427B, Software Development Plan (SDP)).

4.2.3.8 The Contractor shall analyze functional requirements and devise a design approach that is balanced across design constraints, risk aversion and overall system capability. The Government or its other associated contractors may assist with certain designs as delineated by the approved SDP. Changes to the software design shall be integrated into the entire software upgrade that provides overall system functionality. The Contractor shall be responsible for final integration of the software upgrade to include but not limited to debugging, testing, troubleshooting, technical assistance and documentation.

A modular open systems approach shall be utilized to facilitate the incorporation of functionality enhancements and to simplify software debugging, testing and information assurance requirements. The inclusion or reliance on any licensable or proprietary software code shall be explicitly identified to the Government.

A human factors design shall be incorporated for the purpose of reducing operator fatigue, system operator errors and training.

4.2.3.9 The Contractor shall maintain a backlog of software capabilities and improvements. The Proposed Action List (PAL) shall serve as a list that identifies and prioritizes the items to be included in future software releases. The items on the PAL shall include software anomaly/deficiencies corrections and functionality updates. The Contractor shall update the PAL as frequently as necessary. The highest priority items on the PAL shall be selected for inclusion in the subsequent software suite release. The Approved Action List (AAL) shall define the scope of the requirements, capabilities, and content for each software release. The AAL shall be submitted to and approved by ACC.

4.2.3.10 The Contractor shall deliver successive software releases to correct deficiencies and provide functionality enhancements. The development of post-deployment software releases shall follow the same design rigor as required for development of the initial product release. The Contractor shall deliver each software release as an update to the entire software suite that contains all agreed upon products such that no additional software items are necessary. All releases should be in accordance with the SDP and the Software Version Description (SVD) (CDRL A004/B004, DI-IPSC-81442A, SVD-Release Notes).

PR: FD2060-23-30076 PD 9

A new software version identifier shall be assigned to the new software release. All software releases shall undergo acceptance testing at the Contractor’s or the Government’s facilities defined by the government prior to release and delivery. The Contractor shall obtain the Government’s concurrence for approval of the software version release. The contractor shall deliver updates to all technical data concurrently with each successive software release.

4.2.3.11 The Contractor shall use their existing configuration management and data management systems to accomplish identification, change control effectively, and change status accounting. The Government shall be provided an opportunity to review and request changes to the Contractor’s configuration control processes.

4.2.3.12 The Contractor shall develop test scripts, procedures, and conduct acceptance testing on each software version prior to release. The results of acceptance testing shall be provided to the Government in advance of the software release. The results of acceptance testing may be presented in any appropriate format. The Government shall be provided an opportunity to review and request changes to the Contractor’s acceptance test plan (ATP) and perform an acceptance test, if desired. The Government shall verify all requirements are satisfactorily met prior to software acceptance and release. (CDRL A008/B008, DI-QCIC-80553A, Acceptance Test Plan (ATP)).

4.2.3.13 The contractor shall deliver program specific application source code for the last major release and source code currently in development. Any other software developed that is not considered program application source code or covered above shall be delivered in the form of versioned obfuscated libraries. The Government may request copies of technical data the Contractor generated in the course of performing work under this PD. The Contractor shall provide any existing technical data in its original format and is not obligated to generate any new data to satisfy a data accession request. The Contractor’s generation or utilization of any proprietary data shall be coordinated in advance with the Government. (CDRL A006/B006, DI- IPSC-81488, Computer Software Product (Tech Data)).

4.2.4 Program Meeting Support: The Contractor shall be prepared to participate in the following meetings to support the program on an as-needed basis. The location of meetings may be at various CONUS sites and may occasionally be at the Contractor’s facilities. It is anticipated the Contractor will participate in a minimum of ten (10) meetings annually. Meetings may be technical reviews, program manager reviews, or other meetings supporting the project’s integrated product team. The Contractor’s participation in all meetings executed under this PD shall be coordinated in advance with the Government. The Contractor shall be responsible for recording action items and summarizing any agreements or technical decisions pertaining to work performed under this PD in meeting minutes. Meetings may include, but not limited to the following:

• Technical Interchange Meetings

• Network IPT (telecom)

• Software IPT (telecom)

PR: FD2060-23-30076 PD 10

• Training IPT (telecom)

• Crew Station Working Groups

• Program Management Reviews

• Configuration Control Board

• Preliminary Design Reiews/ Initial Concept Reviews

• Critical Design Reviews / Final Concept Reviews

• Software Design Reviews

• Capabilities Requirement Reviews

• Software Requirements Reviews

• Acceptance Test Procedures (ATP – per release)

• General Telecom Support

4.2.5 Documentation Support: The Contractor shall generate an updated Software Version Description document. The SVD (Release Notes) shall be updated on each occasion the deliverable software is changed. (CDRL A004/B004, DIIPSC-81442A, SVD-Release Notes).

The Contractor shall generate an updated Software User’s Manual (SUM). The contractor will provide updates as required in paper or electronic format. The SUM shall explain how to install, initialize, use, and troubleshoot the deliverable software suite in all of its intended modes of operation. (CDRL A005/B005, DI-IPSC-81443A, Software User manual (SUM) (Per Release)).

4.2.6 Training Support: The Contractor shall have a full-time trainer to provide scheduled and unscheduled training to the user or associated Contractor for the deliverable software as required.

It is anticipated the Contractor will not have to provide training classes, but will need to be prepared to do so if situations dictate. The Contractor is responsible for maintaining up-to-date training material. The Contractor shall provide training material to the customer when they are initially trained and provide updated training material to those previously trained (CDRL A003/B003, DI-ILSS-80872, Training Material).

4.2.7 Travel Support (Authorized): The contractor shall provide troubleshooting, verification, and evaluations of software releases as required. Mission support activities will be primarily conducted at the contractor’s facility, or aircraft home base locations. All travel must be requested and approved through the Program Office and PCO prior to costs being incurred and a minimum of ten (10) business days in advance of departure. All travel shall be reimbursable in accordance with the Joint Travel Regulation (JTR) rate when verified and approved by the Contracting Officer or the Contracting Officer’s designated representative.

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

PR: FD2060-23-30076 PD 11

4.4 Cybersecurity: The Contractor shall conduct all necessary Cybersecurity testing and provide supporting documentation in order to obtain cybersecurity approval. (CDRL A009/B009, DI- MGMT-81845/T, Information Assurance (IA) Design Review Information Package (DRIP)), (CDRL A010/B010, DI-MGMT-81844/T, Information Assurance (IA) Test Plan), (CDRL A011/B011, DI-MGMT-81843, Information Assurance (IA) Test Report), (CDRL A012/B012, DI-MISC-80508B/T, Technical Report – Study Services).

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Service Manager (FSM) has determined these services are not mission-essential and will not continue in the event of a crisis.

5.1.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, sub contracts, and information used in the performance of duties in support of Air Force requirements/missions. The Contractor shall ensure Contractor personnel who perform work on (or in) a Government facility comply with the OPSEC procedures and training requirements of the facility as specified in AFI 10-701.

5.1.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 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a).

Applicable equipment shall be safeguarded, maintained and operated in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a).

5.1.4 Security Clearance: It is not expected that contractor/subcontractor personnel will require security clearances for proper accomplishment of contract/order requirements.

Contractor/subcontractor personnel shall not be authorized access to classified information and/or Controlled Unclassified Information (CUI) and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.1.5 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified information and/or CUI.

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

5.1.7 Access to Government Facility or Military Installation: Access to government facility or Military Installation will not be required to perform tasks under the contract.

PR: FD2060-23-30076 PD 12

5.1.8 Security of Contractor System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract. 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 or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2 Identification (ID) Card/Badge

5.2.6 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.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 Environmental, Safety, and Occupational Health 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 DoD Directive 4715.1E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan.

The Contractor shall require all subcontractors to comply with required safety, health and fire standards.

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. In the event of a mishap, the Contractor shall ensure the USAF is notified of the mishap. The Contractor shall contact the organizations listed below within four business hours. The

PR: FD2060-23-30076 PD 13

Contractor shall immediately secure the mishap scene (and damaged property) and impound pertinent maintenance and training records until released by the Government’s Safety Office (AFLCMC/SE). Such release shall be accomplished through the Contracting Officer. The Contractor shall cooperate and assist Government personnel in the investigation of the mishap and submit an Accident/Incident Report within 24 hours of the mishap to:

5.5.2.1. PCO,

5.5.2.2. MFT (COR, if available, or another MFT member),

5.5.2.3. The closest USAF base command post (to relay notification to AFLCMC/SE).

(CDRL A007/B007, DI-SAFT-81563 Accident/Incident Report).

5.5.3 Voluntary Protection Program (VPP): Contractor personnel performing work on a USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

5.5.4 VPP Description: In 1982, OSHA created the Voluntary Protection Programs (VPP) to recognize and partner with worksites that implement exemplary systems to manage worker’s safety and health. These sites implement comprehensive Safety and Health Management Systems that exceed basic compliance with OSHA standards. VPP applies to all personnel at Robins AFB - civil servants (both bargaining and non-bargaining), active duty (officer and enlisted), reservists and contractor employees. The Contractor shall ensure its employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. The Contractor, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, shall follow the safety and health rules of the installation or VPP site. Detailed information on VPP is available on the OSHA website at http://www.osha.gov/dcsp/vpp/index.html. The Contractor shall access the site to ensure their understanding of VPP and how their performance is linked to the Air Force installation’s pursuit of VPP recognition.

5.5.5 Department of Labor (DoL) Inspection of Contractor Operations. The Contractor is subject to DoL inspections and enforcement by OSHA health and safety officials while performing work on a Government installation. OSHA health and safety officials may access workplaces on Government installations at any time, scheduled or unscheduled, during regular work hours.

OSHA health and safety officials must meet security requirements to enter restricted or classified areas. The Contractor shall immediately notify the COR and the contracting unit’s Safety Office upon notification of a visit.

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 Service Contract Reporting (SCR): The contract does not meet the DoD Contract Reporting criteria or reporting dollar threshold; therefore, SCR does not apply.

5.8 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

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

PR: FD2060-23-30076 PD 14

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

DoD 5220.22-M

National Industrial Security Program Operating Manual

(NISPOM)

February 28, 2006 Change 1 - March 28, 2013 Para 4.3

DoDD 4715.1E

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

DoDD) 5205.02E

DoD Operations Security (OPSEC) Program October 29, 2020 Para 5.1.2

DoD Manual 5205.02-M

DoD Operations Security (OPSEC) Program Manual October 29, 2020 Para 5.1.2

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

OSH Act of 1970 | Occupational Safety and Health Administration

December 29, 1970 as amended through January 1, 2004 Para 5.5.1

6.2 Appendix B: Acronyms

AED Automated External Defibrillator AFI Air Force Instruction AFMAN Air Force Manual AFMC Air Force Material Command AFOSH Air Force Occupational Safety and Health AIS Automated Information System AMU Audio Management Unit ATACNAV Advance Tactical Navigation BER Beyond Economical Repair CAC Common Access Card CAP Contractor Acquired Property http://www.state.gov/j/tip

PR: FD2060-23-30076 PD 15

CAR Contract Action Reports CBT Computer Based Training CCB Configuration Control Board CCI Controlled Cryptographic Items CDRL Contract Data Requirements List CLS Contractor Logistics Support COMSEC Communications Security CONUS Continental United States COR Contracting Officer Representative CSO Combat Systems Officer CUI Controlled Unclassified Information CVS Contractor Verification System DCMA Defense Contract Management Agency DCU Digital Crew Unit DMCU Digital Master Control Unit DoD Department of Defense DSU Defensive System Upgrade ECP Engineering Change Proposal EMS Environmental Management System EPA Environmental Protection Agency FC Functional Commander FSR Field Service Representative FST Field Service Technician FUT Fuselage Trainer GFE Government Furnished Equipment GFM Government Furnished Material GFP Government Furnished Property GMOP GPS Enhanced Mission Operator Pallet GPS Global Positioning System GTR Gun Training Room GWS Gun Weapons System HAZMAT Hazardous Materials HMD Helmet Mounted Display HUD Heads-Up Display System ICS Digital Intercommunications System IETM Interactive Electronic Technical Manuals IMDS Integrated Management Data System IPT Integrated Product Team IRSS Infrared Suppression System ISR Intelligence, Surveillance, and Reconnaissance

PR: FD2060-23-30076 PD 16

KuSS Ku Band Spread Spectrum MIP Mission Interface Panel MOP Mission Operator Pallet MPF Military Personnel Flight NACI National Agency Check with Inquiries NFPA National Fire Protection Agency NISPOM National Industrial Security Program Operating Manual NSWC Naval Surface Warfare Center O&A Over and Above OCONUS Outside Continental United States OEBGD Overseas Environmental Baseline Guidance Document OEM Original Equipment Manufacturer OJT On the Job Training OPSEC Operational Security PCA Physical Configuration Audit PCO Procurement Contracting Officer PD Product Description PoP Period of Performance PSP Precision Strike Package PWS Performance Work Statement QA Quality Assurance QCM Quality Control Manual QMS Quality Management System RAPIDS Real Time Automated Personnel Identification Documentation System RMA Return Material Authorization S&H OI Safety & Health Operating Instruction SADL Situation Awareness Data Link SB Service Bulletin SCM Stack Control Module SDB Small Diameter Bomb SIL Software Integration Lab SIU Switch Interface Unit SMP Special Mission Processor SOPGM Special Operations Precision Guided Munition SSDL Small Secure Data Link STT Small Tactical Terminal TCTO Time Compliance Technical Order TDY Temporary Duty TGM Trainable Gun Mount TO Technical Order

PR: FD2060-23-30076 PD 17

UPNR Unit Possessed Non Reportable USDA United States Department of Agriculture UTC Unit Type Code VPP Voluntary Protection Program