PERFORMANCE WORK STATEMENT compare.pdf

(FOR OFFICIAL USE ONLY)

Solicitation Number: FA489020R0034

Contract Number: FA48902xC00xx (TBD)

Formatted: Font: 16 pt

Formatted: Right

Formatted: Font: 16 pt

Formatted: Font: 16 pt an

PERFORMANCE WORK STATEMENT

Air Combat Training Systems (ACTS)

OPERATIONS, MAINTENANCE, & ENGINEERING

(OM&E)

Revised 07 Sep 202020 May 2021

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

TABLE OF CONTENTS

PARAGRAPH TITLE PAGE

1 DESCRIPTION OF SERVICES

1.1 Scope and Introduction

1.2 Mission and System Description

2 APPLICABLE DOCUMENTS

2.1 General

2.2 Governing Documentation

3 REQUIREMENTS

3.1 ACTS OM&E Services

3.1.1 Requirements Overview

3.1.2 Services Summary

3.2 Operations

3.2.1 General Operations Activities

3.2.2 Airborne Instrumentation Systems (AIS) Operations

3.2.2.1 AIS Availability Criteria

3.2.2.2 External (Pod) AIS Operations

3.2.2.3 Internal AIS Operations

3.2.3 Portable Instrumentation Systems Operations

3.2.4 Ground Systems (GS) Operations

3.2.4.1 GS Availability Criteria

3.2.4.2 General Mission Support

3.2.4.3 Specific Systems Operation

3.2.4.3 Pre-Mission Activities

3.2.4.4 Live Mission Operations

3.2.4.5 Post-Mission Debrief

3.3 Maintenance

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.3.1 General Maintenance Activities

3.3.2 Airborne Instrumentation Systems (AIS) Maintenance

3.3.2.1 External (Pod) AIS Maintenance

3.3.2.2 Internal AIS Maintenance

3.3.3 Portable Instrumentation Systems Maintenance

3.3.4 Ground Systems Maintenance

3.3.4.1 General Maintenance Activities

3.3.4.2 Specific Systems Maintenance

3.4 Engineering

3.4.1 General Engineering Activities

3.4.2 Software

3.4.3 Radio and Transceiver Systems

3.4.4 Networks, Components, and Systems

3.5 Management

3.5.1 General

3.5.2 Program Management

3.5.3 Quality Management

3.5.4 Security Management

3.5.5 Maintenance Management

4 GOVERNMENT PROGRAM MANAGEMENT

4.1 Program Responsibility

4.2 Quality Assurance

4.3 Program Meetings

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Field Code Changed

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

LIST OF APPENDICES

APPENDIX TITLE PAGE

1 ACTS Equipment and Locations

1.1 ACTS Equipment

1.2 ACTS Locations

1.3 Additional Services

2 Governing Documentation

3 System Availability Definitions and Calculations

4 Workdays and Holidays

5 Definitions of Terms

6 Acronyms and Abbreviations

7 Government Furnished Property, Equipment, Facilities, and Services

8 Site Specific Items

8A – Eglin AFB, FL

8B – Langley AFB, VA

8C – Seymour Johnson AFB, NC

8D – Mountain Home AFB, ID

8E – Barksdale AFB, LA

8F – Shaw AFB, SC

8G - Spangdahlem AB, GE

8H - RAF Lakenheath, UK

8I - Aviano AB, IT

8J – Tyndall AFB, FL

8K – Ellsworth AFB, SD

8L – Dyess AFB, TX

8M – Nellis AFB, NV

8N – Gulfport CRTC, MS

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

8O – Volk CRTC, WI

8P – Alpena CRTC, MI

8Q – Savannah CRTC, GA

8R – AFCENT AWC, UAE

8S – JRB Fort Worth, TX

8T – Optional Site

1 ACTS Equipment and Locations

1.1 ACTS Equipment

1.2 ACTS Locations

1.3 Additional Services

2 Governing Documentation

3 System Availability Definitions and Calculations

4 Workdays and Holidays

5 Definitions of Terms

6 Acronyms and Abbreviations

7 Government Furnished Property, Equipment, Facilities, and Services

8 Site Specific Items

8A – Eglin AFB, FL

8B – Langley AFB, VA

8C – Seymour Johnson AFB, NC

8D – Mountain Home AFB, ID

8E – Barksdale AFB, LA

8F – Shaw AFB, SC

8G - Spangdahlem AB, GE

8H - RAF Lakenheath, UK

8I - Aviano AB, IT

8J – Tyndall AFB, FL

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

8K – Ellsworth AFB, SD

8L – Dyess AFB, TX

8M – Nellis AFB, NV

8N – AFCENT AWC, UAE

8O – Davis-Monthan, AZ (Optional)

8P – JRB Fort Worth, TX (Optional)

8Q – Optional Site

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

1 DESCRIPTION OF SERVICES

1.1 Scope and Introduction

1.1.1 This Performance Work Statement (PWS) Pricing Methodology. Unless otherwise stated in this PWS, all work and purchases are part of the Firm Fixed Price (FFP) portion on the contract.

1.1.21.1.1 This PWS establishes the government’s requirements for the acquisition of contractor services for the implementation of the Air Combat Training Systems

(ACTS) Operations, Maintenance, and Engineering (OM&E) program. The contractor shall support the ACTS equipment listed in Appendix 1, Table 1 at the locations listed in Appendix 1, Table 3. ACC/A3A may modify the ACTS OM&E program as operational needs dictate with submission of a modification request to the contracting office as required. Such modifications may include:

1.1.2.11.1.1.1 Additional sites (both CONUS and OCONUS) as determined by operational needs of ACC, other MAJCOMS (to include AETC, AFGSC, ANG, AFRC, PACAF, USAFE, AFCENT, AFSOC), or the Air Force.

Reference Appendix 1, Table 4 for a potential list of additional sites.

1.1.2.21.1.1.2 Additional ACTS equipment (legacy, upgraded, and new) as necessary to support air combat training on current and future airframes. Reference

Appendix 1, Table 2 for a potential list of additional equipment.

1.1.2.31.1.1.3 Additional support and/or services required to fulfill the ACTS mission for the CAF.

1.1.2.41.1.1.4 Reduction or elimination of sites, equipment, support, and/or services to manage fiscal restraints or operational priorities.

1.1.2 Unless otherwise stated in this PWS, all work and purchases are part of the Firm

Fixed Price (FFP) portion of the contract.

1.1.3 Unless otherwise stated in this PWS, all references to ‘days’ regarding timeframes and suspenses shall refer to calendar days.

1.2 Mission and System Description

1.2.1 The Air Combat Training System (ACTS) program supports pre-mission

Commented [A1]: Added statement to clarify the FFP nature of this contract up front

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt preparation, mission execution, and post-mission debrief to enhance the quality of aircrew and warfighter training in planning, conducting and assessing air combat maneuvers, weapons employment, and tactics implementation by presenting tailored data and focused displays showing an integrated operational picture with emphasis on airborne and ground training participants. To provide this capability, ACTS uses combinations of aircraft instrumentation (typically a pod or on-board airborne system), integrated data feeds, range systems, and a robust ground infrastructure to track participants in multiple domains (emphasis on air and ground) while all data is continually recorded via multiple sources. After the event, the recorded data allows complete reconstruction of participant activity.

1.2.2 The ACTS program provides these capabilities via multiple systems. Generically these are airborne, ground, communication, network, and integration systems. The

P5 Combat Training System (P5CTS) is one key system that is composed of both airborne and ground components. The P5CTS aircraft instrumentation system is the airborne component and provides high accuracy position tracking, real-time kill notification, air-to-air data link, onboard recording, downlink, and in-pod weapon simulations. The P5CTS ground equipment provides the capability for live mission control and post-mission debrief. P5CTS ancillary equipment includes radios, simulators, multiplexors, display software, and interfaces necessary for P5CTS to integrate with other live training systems and thus meet mission requirements.

1.2.3 Historically, ACTS functions have been referred to by multiple terms, including the generic term Air Combat Maneuvering Instrumentation (ACMI). Similarly, the key system (P5CTS) is often used generically as a substitute for the larger umbrella of the ACTS family of systems. For the purposes of this contract, the term ACTS encompasses all these legacy terms.

2 APPLICABLE DOCUMENTS

2.1 General. The contractor shall refer to documents, publications, and forms applicable to the services required, as identified throughout this PWS and in Appendix 2. The issue date, revision level, and changes to a particular document shall be that currently in effect.

The contractor shall contact HQ ACC/A3AR if unable to obtain required documents.

The contractor shall be familiar with and have the documents in Appendix 2 on hand as well as any other documents required for performing ACTS OM&E services.

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

2.2 Governing Documentation. The contractor shall obtain any required source material and any changes or updates to the source material as soon as possible after the change. The contractor shall follow all current and future technical data unless a waiver has been obtained. Changes (including revisions, supplements and amendments) to listed publications from any organizational level may be issued during the life of the contract.

2.2.1 Changes: The contractor shall implement changes in publications or technical data using the guidance in Appendix 2 paragraph 1.3.

2.2.2 Conflicts: In the event of conflict between the documents referenced herein and the contents of this PWS, the contents of the PWS shall be considered a superseding requirement except for the following:

2.2.2.1 Any conflict between U.S. and host nation regulations, the most stringent applies.

2.2.2.2 Any conflict between safety or security regulations and this PWS, the most stringent applies.

2.2.2.3 Any conflict between system technical manuals and this PWS, the technical manuals apply.

3 REQUIREMENTS

3.1 ACTS OM&E Services

3.1.1 Requirements Overview

3.1.1.1 The contractor shall provide qualified personnel in sufficient number to maintain and sustain ACTS equipment to meet requirements and capabilities in accordance with (IAW) operational and maintenance procedures in the applicable technical manuals. This includes all necessary tasks to ensure live operations execution and instrumented debrief capability. The contractor shall provide all necessary equipment, technical, and managerial personnel to ensure a total system performance IAW the specified system availability, this

PWS, and the appropriate equipment Technical Manuals as applicable. The contractor shall provide services IAW the guidelines and parameters listed in this PWS and each appendix to this PWS. The contractor shall ensure that all

ACTS data is provided IAW this PWS and system technical manuals for

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt warfighter mission requirements.

3.1.1.2 The contractor shall provide qualified operations and maintenance personnel in sufficient number to meet both the flying hour window and the debriefing window and to meet all requirements of this PWS. A typical flying hour window is ten (10) hours four days a week or eight (8) hours five (5) days a week. A typical debriefing window is ten (10) hours four (4) days a week or eight (8) hours five (5) days a week. Some sites don’t follow this typical window; refer to the site-specific requirements in Appendix 8 for further details.

3.1.1.3 A mission support day shall include the following:

3.1.1.3.1 Sufficient time prior to the flying window to ensure all pods that are delivered to the ramp have been fully tested using approved test equipment and procedures per the system technical manuals. Some sites do not allow pods to be left on aircraft overnight; refer to the site-specific requirements in Appendix 8 for further details.

3.1.1.3.2 Sufficient time during the flying window to swap operational pods for pods that fail after being uploaded on aircraft.

3.1.1.3.3 Sufficient time to initialize and check out the ground system, prepare files/data required for each mission, and load the recording devices with pre-mission data.

3.1.1.3.4 Availability to troubleshoot and arrive at a diagnosis within twenty (20) minutes of any ground system failure during mission debrief or analysis.

3.1.1.3.5 Sufficient time prior to the mission to operationally check equipment required for a Live Monitor mission, to include RRU’s (Remote Range

Units (RRUs) at those units with Live Monitor capability)..

3.1.1.3.6 Normal workdays are Monday through Friday of each week, or Sunday through Thursday in the UAE, with the exception of established federal holidays or other days proclaimed as official holidays by the government

(See Appendix 4). Mission schedules will occasionally require weekend and holiday work by the contractor and shall be considered part of the regular 40-hour work week. Regardless of flying schedule, contractors

Formatted: Highlight

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt will typically have a minimum of 12 hours turnaround time between daily shifts.

3.1.1.4 The contractor shall provide qualified engineering and specialist personnel in sufficient number to support required engineering tasks and shall maintain a core engineering capability as specified in this PWS to support the system evolution and upgrade expected during the course of this contract.

3.1.1.5 Not all OM&E services will be required at all locations. For example, at some locations, pod transport and loading may not be completed by government personnel rather than contractor personnel.required. The PWS main body

(paragraphs 1-4 and all sub-paragraphs) will cover all requirements and the site appendices will identify any site-specific differences and the contract

CLIN structure will support individualsupplemental site requirements. For the purposes of this PWS, all requirements in the PWS main body will apply to all locations unless specifically excluded in the site-specific appendices.

3.1.1.6 Mission Overtime. This PWS is structured to require the contractor to plan for and adjust employee work schedules using staggered shifts and flex-time to cost effectively support adjusted mission support requirements. However, there may be rare occasions when work is required outside of typical mission windows and variable scheduling is not an option. The contractor shall provide the capability to support flying schedules and debriefing schedules that exceed the normal 40-hour workweekwork week as provided under this contract. The government will fund an overtime CLIN to support these extended mission requirements on a cost reimbursable basis. . The contractor is not authorized to work overtime without prior approval of the Government

Program Manager., Lead COR, or Alternate.

3.1.1.7 Government Interface: This contract is broad and covers 11 time zones, 54

MAJCOMs, one coalition partner, and multiple mission sets. Such an effort requires a robust and delineated contractor-government interface. The contractor shall maintain an appropriate organizational structure to enable interface with the government at all levels. The contractor shall ensure these contractor personnel have a government common access card (CAC) and network account to enable secure contract communications with government

POCs. Refer to para 4.1.3 for government organization structure.

Commented [A2]: Pretty broad rqmt – can this be defined more or state where more specific rqmts are at in the PWS?

Commented [A3]: Is it possible to identify a certain number of overtime hours per location that is part of the FFP effort like with

PTR? OT hrs would still need to be tracked to make sure the total hours are not exceeded but would avoid the OT CLIN on a cost reimbursable basis

Commented [A4]: CO does not currently approve OT – I don’t see any reason to change this. I do recommend identifying a 2nd position, i.e. Deputy GOV PM, to approve OT in case the PM is not available to avoid a single pt of failure.

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.1.2 Services Summary

Requirement Reference Standard

Provide ACTS services IAW this

PWS and each PWS appendix for the appropriate base with

100% of required contractor personnel..

Para 3.1

AppxAppendix

Appx 8

Appendix 3

Appendix 8

Payments are based on availability rates as defined by paragraph Appendix 3 of this PWS. Payment for ACTS services at each installation will be based on the following:

Availability Rate % of CLIN Paid

95 - 100% 100%

85 - 94% 80%

80 - 84% 50%

75 - 79% 20%

Below 75% 0

Meet all security requirements as defined in PWS

Para 3.5.4 Contractor meets 100% of safeguarding, clearance, and inspection/reporting requirements

Meet all safety requirements as defined in PWS

Para 3.5.5.3 Contractor meets 100% of inspection and reporting requirements

Meet all training requirements as defined in PWS

Para 3.5.5.6 Contractor meets 100% of training requirements

Meet all PWS requirements for use and care of

Government Furnished

Property/Equipment

Para 3.5.2.10 and Appendix

Contractor fully complies with all requirements identified in the PWS

95% of the time.

3.2 Operations

3.2.1 General Operations Activities

3.2.1.1 The contractor shall setup, initialize, key, configure, and operate all ACTS

Commented [A6]: Recommend John Noble review for latest/greatest SS concepts

Commented [A5]: Recommend adding Deliverables as a SS

Item because they will end up as government owned (ref 3.5.2.6).

Define acceptable standard for submissions (i.e., no more than 1 deliverable per site per month to not meet timeliness, accuracy, or recipient standard as req’d)

Formatted Table

Commented [A7]: Superfluous. We care about the work being performed to the proper level regardless if they do it with 1% or

100% of the manpower.

If manpower is something we want to keep an eye on, it should be a separate SS item.

Commented [A8]: 100% compliance items are go-no and do not truly necessitate entry in the SS. Recommend removing these as SS items or rolling into a comprehensive 100% compliance SS item.

Commented [A9]: Do not use a percentage unless the monthly sample or lot size is 100+

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt equipment and software to support operational training activities and ensure successful accomplishment of the complete training mission. This includes all components of major systems (such as P5CTS) as well as all supporting ancillary ACTS equipment, software, and cryptographic devices necessary for a fully immersive training environment.

3.2.1.2 In any instance where the ACTS system does not fully meet the mission requirements, the contractor shall poll the aircrew during, or directly after, debrief using a Mission Evaluation Debrief Checklist. The contractor shall provide the SAR/COR a weekly summary of all Mission Evaluation Debrief

Checklists to the Site ACTS Representative (SAR) or Site Contracting

Officer’s Representative (COR). The contractor shall also report the number of checklists received and any significant feedback in the monthly system availability summary.

3.2.1.3 The contractor shall ensure that all scheduled ACTS hardware and software is fully operational not later than the scheduled mission time as published on the local daily mission schedule. For this requirement, each severable portion of the mission (pod loading, live monitor operation, post-mission debrief) may be treated as a separate mission time. The step, take-off, mission, and debrief times shall be based on the wing scheduling agency’s start and end flying periods as shown on the monthly flying schedule.

3.2.1.4 The contractor shall provide a single point of contact representative at each location to support scheduling, planning, and coordination activities necessary to fully support the training mission with all required ACTS services.

3.2.1.4.1 The contractor representative shall attend weekly and quarterly scheduling meetings and interface with the government scheduling manager to assist in developing weekly and daily ACTS schedules to include a total ACTS resource availability schedule that accounts for any

ACTS-related plans and projects.

3.2.1.4.2 The contractor representative shall call the appropriate single point flight scheduling activity each day to confirm the next day’s flight schedule and determine if any changes or deviations are needed from the published schedule.

Commented [A10]: Who determines the checklist is sufficient?

Is this an existing checklist or does the ktr need to develop one for use?

Commented [A11]: Recommend also requesting an alternate in caser he primary is not available to avoid a single pt of failure

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.2.1.5 At locations requiring an Exercise / Battlespace Coordination position, the contractor shall provide expanded exercise coordination based on the size, number, frequency, and scope of exercises at that site. The contractor shall coordinate participation/activities of various exercise components to include wings/squadrons, airspace and ranges, threats and emitters, and required battlespace. The contractor shall organize, conduct, and maintain methods for sharing coordination data to include video teleconference events and

SharePoint sites. Site specific aspects of exercise coordination are further delineated in the specific site appendices.

3.2.1.6 “Hub-and-Spoke” Operations Support – Some locations serve as a central

‘hub’ and provide operations, maintenance, and engineering support to

‘spoke’ units often far away. This structure provides great flexibility to units

(such as guard and reserve) that don’t otherwise warrant the full range of

ACTS support. For an example of this type of location, refer to Gulfport

CRTCShaw AFB (Appendix 8N).8F) which has remote support for McEntire

ANGB. The contractor shall support this operational structure by providing customized support as follows:

3.2.1.6.1 The contractor shall provide centralized system maintenance of ACTS equipment at hub locations to the greatest extent possible.

3.2.1.6.2 The contractor shall provide remote maintenance at the spoke units periodically as required by technical data and maintenance needs.

3.2.1.6.3 The contractor shall provide dedicated operations support at the spoke units as specified in the site appendices.

3.2.1.6.4 The contractor shall plan for additional time, travel, or rotable personnel/resources as needed to support this structure.

3.2.1.7 Deployment/Exercise Support: The contractor may be tasked to support exercises/operations both at the assigned location or the deployed location.

3.2.1.7.1 CONUS operations require contractor support for up to 35 annual deployments. These deployments shall require loading and debriefing support similar to that provided at home station. The contractor shall have to account for up to an average of 2070 deployed days, but these deployments will not normally overlap.

Commented [A12]: Is this a word? Do you mean “rotate’?

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.2.1.7.2 OCONUS operations require contractor support for 12-14 annual deployments. These deployments shall require loading and debriefing support similar to that provided at home station. The contractor will have to account for up to an average of 190196 deployed days with the possibility of up topotential for 2 concurrent deployment situationsdeployments.

3.2.1.7.3 Some unit deployments may not require contractor deployment. In such cases, the contractor shall be responsible for operational checkout and configuration of ACTS equipment and software before it departs home station, but the contractor is not responsible for deployed-location activities such as equipment maintenance, daily debrief, etc. Once the system is returned to its home station, the contractor shall troubleshoot and repair any malfunctions that occurred while the system was deployed.

This function will be considered a lower priority to supporting current operations.

3.2.1.8 The contractor shall coordinate with other units participating in exercises or missions to ensure mission building, data sharing, and post-mission debriefing provides a complete mission picture to both the local unit and the guest unit

(whether TDY locally or participating from another base) with the provision that appropriate security concerns have been addressed when dealing with foreign nations (Reference paragraphparagraphs 3.15.4.3 and 3.5.4.7).

3.2.2 Airborne Instrumentation Systems (AIS) Operations

3.2.2.1 AIS Availability Criteria

3.2.2.1.1 The contractor shall ensure that a sufficient number of fully functioning pods are available to load onto aircraft scheduled to fly an ACTS sortie as indicated on the daily flying schedule. The number of pods required varies daily based the mission schedule, event type, and specific location.

The timing of this task will be accomplished as advised by the SAR/COR.

3.2.2.1.2 If there are insufficient pods available to meet the requirements of the flying schedule, the contractor shall immediately notify the COR. The

COR will determine if the pod shortfall should result in excusable sorties.

3.2.2.1.3 Pods delivered to the ramp may be used for subsequent missions as long

Commented [A13]: Change to read “no more than 14”

Commented [A14]: “average” indicates more than 190 – so is it possible to state what the higher number will not exceed?

Commented [A15]: Confirm 3.1.7 addresses interactions with foreign nationals

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt as the contractor can confirm that the previous mission resulted in a successful debrief or that any problems were not attributable to the pod.

In this case, verifying the power on Built-In Test (BIT) and completing pre-flight checks are sufficient to verify pod operational functionality.

3.2.2.1.4 If an ACTS pod fails on the aircraft after power is applied and the aircraft is still available for load crew access; then the contractor shall make all practical attempts to provide a fully functioning pod to replace the malfunctioning pod before the mission commences. This shall include cross-loading (from a spare jet) or expediting a replacement pod from the storage area. If the contractor is unable to replace the pod, then the COR shall determine if the sortie is excusable or not.

3.2.2.1.5 The contractor shall ensure pod availability to meet a ten (10) hour flying schedule and ten (10) hour debriefing schedule four (4) days a week, or an eight (8) hour flying schedule and eight (8) hour debriefing schedule five

(5) days a week (as specified in the appendices to this PWS) and amended by a designated government representative; to meet schedule changes required to accommodate aircraft availability, operational requirements, and weather conditions; and to meet other changing mission factors. Some sites don’t follow this typical window; refer to the site-specific requirements in Appendix 8 for further details.

3.2.2.1.6 The contractor shall ensure that a sufficient number of fully functioning portable trackers are available to meet the site’s mission needs for ground participants or non-podded airborne participants. The number of portable trackers varies based on the specific location and mission needs.

3.2.2.1.7 If the contractor determines there are insufficient portable trackers to meet the site’s mission needs, they shall immediately inform the

SAR/COR/SAR and provide a recommendation of the type and quantity of portable device needed to support the mission.

3.2.2.1.8 The contractor shall provide a monthly summary system availability report. The contractor shall calculate System availability according to the definitions and guidelines specified in Appendix 3.

3.2.2.1.9 The SAR/COR will adjudicate all determinations of whether a non-

Commented [A16]: Added “SAR”

Commented [A17]: Can SAR do this as well?

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt effective sortie is chargeable using the guidance in this PWS.

3.2.2.2 External (Pod) AIS Operations

3.2.2.2.1 Pod Transport

3.2.2.2.1.1 The contractor shall transport all assigned pods according to the site-specific requirements in Appendix 8, and as directed by the designated

SAR/COR, to meet schedule changes required to accommodate aircraft availability, operational requirements, weather conditions, and other changing mission factors.

3.2.2.2.1.2 At each location where pod transport is required, the contractor shall provide sufficient personnel to transport the pods between the pod storage/maintenance shop and the flight line.

3.2.2.2.1.3 When approved by the COR, the contractor shall also support the movement of pods required for CAF-wide missions and exercises. This shall include preparation, packaging, transportation arrangements, receipt of shipment, and unpacking of pods. The contractor shall provide estimates for any shipping, travel, or other reimbursable costs to the COR for approval prior to accomplishing this work.

3.2.2.2.2 Pod loading/unloading

3.2.2.2.2.1 The contractor shall load and unload all assigned pods according to the site-specific requirements in Appendix 8 and as directed by the designated SAR/COR to meet schedule changes required to accommodate aircraft availability, operational requirements, weather conditions and other changing mission factors.

3.2.2.2.2.2 At each location where pod loading and unloading is required, the contractor shall provide sufficient personnel to perform all aircraft loading and unloading to meet the published wing flying schedule.

3.2.2.2.2.3 The contractor shall support pod loading for any required aircraft as determined by the SAR/COR. This shall include pod loading on aircraft not assigned to the individual base such as visiting USAF, joint, or coalition aircraft provided the pod is cleared for operation on that

Commented [A18]: Can SAR do this as well?

Commented [A19]: Can SAR do this as well?

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt aircraft type.

3.2.2.2.2.4 The contractor shall include a total count of all pod loads and a total count of all pod unloads (by location) performed by the contractor as part of the monthly summary system availability report. For the purposes of this report, a pod crossloadcross load (move from one plane to another) shall count as one upload and one download.

3.2.2.2.2.5 The contractor shall provide all necessary safety equipment for pod load crews.

3.2.2.2.2.6 Pods will be loaded/unloaded only if power is removed from the station;

aircraft load procedures and pod technical manuals prohibit “hot swaps”.

3.2.2.2.2.7 The contractor shall unload any pod suspected of contributing to a “non-effective” mission, place the pod in maintenance, and upload a fully operational replacement.

3.2.2.3 Internal AIS Operations

3.2.2.3.1 The contractor shall support the operational integration of live and post-mission data from host base and visiting participant aircraft who have internal AIS equipment such as the F-35 P5 Internal Mount (IM).

3.2.2.3.2 The contractor shall coordinate with internal AIS participants to ensure loading of accurate mission parameters and to de-conflict key parameters such as site or participant IDs.

3.2.3 Portable Instrumentation Systems Operations

3.2.3.1 The contractor shall support the operational integration of live and post-mission data from all ground and airborne participants (host base or visiting) who use portable (hand-carried) instrumentation devices (trackers) such as

Garmin or other GPS/Global Positioning System (GPS)/Cellular data pushers/loggers.

3.2.3.2 The contractor shall control and allocate all portable instrumentation systems assigned as GFE on this contract. This activity shall include advising warfighters on the available portable trackers best-suited to meet their mission needs and providing basic instruction on the operation of the device.

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.2.4 Ground Systems (GS) Operations

3.2.4.1 GS Availability Criteria

3.2.4.1.1 The contractor shall ensure complete ground system availability to provide overlapping and offset live operations windows and debriefing windows such as:

A ten (10) hour live ops schedule and ten (10) hour debriefing schedule four (4) days a week.

An eight (8) hour live ops schedule and eight (8) hour debriefing schedules five (5) days a week.

Similar split of live ops and debriefing as required by site mission parameters or requested by a designated government representative to meet schedule changes required to accommodate aircraft availability, operational requirements, weather conditions; and other changing mission factors.

3.2.4.1.2 In the event of a malfunctioning piece of local equipment (such as a

P5CTS LM), the contractor shall respond within 20 minutes of notification of the malfunction. The contractor shall restore the GS to full functionality not later than 30 minutes after arrival. If the contractor is not able to repair the malfunction and the aircrew is not able to accomplish an effective mission analysis, the COR will use these response/restore guidelines to determine if the contractor shall be held responsible for the malfunction.

3.2.4.1.3 In the event of a malfunctioning piece of remote equipment (such as a

Range Remote UnitRRU), the contractor shall be allowed sufficient time to travel to the remote location. The contractor shall restore the remote equipment to full functionality not later than 30 minutes after arrival. If the contractor is not able to repair the malfunction and the aircrew is not able to accomplish an effective mission analysis, the COR will use these response/restore guidelines to determine if the contractor shall be held responsible for the malfunction.

3.2.4.1.4 Note: In general, live monitor and debriefing support will take priority

Commented [A20]: Where are the guidelines provided?

Commented [A21]: Where are the guidelines provided?

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt over troubleshooting malfunctioning ground systems provided there is alternate/redundant capability available to continue supporting the mission.

3.2.4.1.5 The contractor shall provide a monthly system availability report. The contractor shall calculate system availability according to the definitions and guidelines specified in Appendix 3. The COR will adjudicate all determinations of whether a non-effective live ops or debrief is chargeable using the guidance in this PWS.

3.2.4.2 General Mission Support

3.2.4.2.1 The contractor shall perform ground systems operations for all ACTS equipment and software to include major systems (such as P5CTS) as well as all ancillary hardware and software collectively referred to as

“ground systems” in this PWS. Ground systems operations shall include all actions to power-on, setup, configure, initialize, operate, adjust, and monitor equipment and software required to support ACTS missions.

3.2.4.2.2 The contractor shall operate all ground systems whether centrally located in a War Room (or similar Ops Facility), dispersed to squadron vaults and debriefing rooms, or remotely located on or off base.

3.2.4.3 Specific Systems Operation: In addition to the core ground systems present at all locations, the contractor shall operate the following ground systems which may be present depending on site mission requirements as specified in the site appendices and site GFE inventories (Tech Exhibit 1). The complete

GFE inventory covers all required ground systems; however, paragraphs below highlight the major systems.

3.2.4.3.1 Remote instrumentation systems. Shall include, but not be limited to, the following:

Remote Range Units

3.2.4.3.2 Radio and Radio Management Systems. Shall include, but not be limited to, the following:

FM/HF/UHF/VHF/SATCOM radios (secure and non-secure)

Commented [A22]: Vague, difficult for workload analysis to determine appropriate workforce mix to meet PWS requirements

Commented [A23]: Vague, difficult for workload analysis to determine appropriate workforce mix to meet PWS requirements

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Digital Radio Management System (DRMS)

3.2.4.3.3 Datalink and Datalink Management Systems. Shall include, but not be limited to, the following:

Datalink terminals (Link-16, SADL, MIDS-JTRS, 5th Gen terminals)

Terminal interfaces (Joint Range Extension, Pocket-J)

Terminal control and constructive link injection (Ground Tactical

Datalink System)

3.2.4.3.4 Track Correlation Equipment. Shall include, but not be limited to, the following:

Radar Acquisition and Display System (RADS)

Multi-Source Correlator Tracker (MSCT)

3.2.4.3.5 Threat Control, Management, and Simulation Systems. Shall include, but not be limited to, the following:

Electronic Warfare (EW) Server/

Electronic Warfare Multiplexor (EW MUX)

Digital Integrated Air Defense System (DIADS)

3.2.4.3.6 Networking and Gateway Systems. Shall include, but not be limited to, the following:

Live Mission Operations Network (LMON) –site-level LMON node operations.

Cross-Domain Trusted Guards – Radiant Mercury, SimShield (within limits of security policy)

Backbone network systems such as routers, switches, and media converters.

Protocol gateways –Test and Training Enabling Architecture (TENA)

Commented [A24]: Vague, difficult for workload analysis to determine appropriate workforce mix to meet PWS requirements

Commented [A25]: Vague, difficult for workload analysis to determine appropriate workforce mix to meet PWS requirements

Commented [A26]: Vague, difficult for workload analysis to determine appropriate workforce mix to meet PWS requirements

Commented [A27]: Vague, difficult for workload analysis to

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt gateways and networks.

Network Portals –Distributed Mission Operations (DMO) portals.

3.2.4.3.7 Virtual/Constructive (V/C) Systems. Shall include, but not be limited to, the following:

Live, Virtual, and Constructive Network Control Suite (LNCS)

Network Integrated Constructive Environment (NICE)

Distributed Interactive Simulation/Graphical User Interface (DIS/GUI)

Performance Evaluation and Tracking System (PETS).

3.2.4.4 Pre-Mission Activities: The contractor shall provide operational support for activities which must be completed before the mission starts to enable an efficient and successful training mission.

3.2.4.4.1 Scenario Development - At all locations requiring Range Training Officer

–(RTO) - Tactics support, the contractor shall fully perform the role of

RTO (IAW AFIAFMAN 13-212212v1) as well as the additional duties of

RTO –- Tactics. These additional duties include training scenario development/execution, battlespace management planning, intelligence summaries creation, and mission order planning. Site -specific aspects of

RTO - Tactics are further delineated in the specific site appendices.

3.2.4.4.2 Ground System preparation – The contractor shall prepare all portions of the ground system to support the mission. This shall include building the mission line-up, assigning slots, checking radios, setting frequencies, loading profiles/scenarios, queueing synthetic entities, initiating recording, etc.

3.2.4.4.3 Mission Preparation - The contractor shall prepare recording devices

(P5CTS Data Recording Device, (DRD), Garmin, etc.) and live monitor systems for the scheduled missions. Recording devices for each sortie participant shall be loaded with the correct pre-mission data required for proper equipment function and distributed to mission participants.

3.2.4.5 Live Mission Operations

Commented [A28]: Vague, difficult for workload analysis to

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.2.4.5.1 At all locations requiring Live Mission Operations, the contractor shall ensure the Live Monitor ground system and all associated live monitor interface equipment is fully operational with all mission preparation complete not later than the scheduled mission takeoff time. The contractor shall record the mission, ensure proper ground system operation during the mission, and support warfighters RTOs managing the mission.

3.2.4.5.2 At all locations requiring RTO support, the contractor shall fully perform the role of RTO without government involvement when required for mission support. The contractor shall augment government RTOs who choose to lead the live training mission. In either situation, the contractor shall accomplish RTO duties IAW AFIAFMAN 13-212212v1.

3.2.4.5.3 At all locations requiring Tactical Data Link Manager (TDLM) support, the contractor shall routinely augment the government TDLM as needed to support the live mission. The contractor shall occasionally perform the role of TDLM without government involvement as required for mission support. In either situation, the contractor shall accomplish TDLM duties

IAW AFI 11-261AFMAN 13-116.

3.2.4.5.4 At all locations requiring Surface-to-Air-Missile (SAM) Operator support, the contractor shall routinely operate and control range threat emitters that have been appropriately configured for remote operation. The SAM

Operator shall also serve as an interface to on-range controllers for those threat emitters that are not configured for remote operations.

3.2.4.6 Post-Mission Debrief - The contractor shall provide mission file preparation and ground system setup for debriefing at ACTS locations.

3.2.4.6.1 Mission file preparation for debriefing shall include all necessary steps to validate mission datedata, merge multiple recording sources, produce a consolidated mission file, and quality check the output to produce a final mission file ready for warfighter playback during debrief.

3.2.4.6.2 Ground system setup for debriefing shall include all necessary steps for transferring the final mission file to the debriefing system, starting the display software, loading the mission file, and advancing to the mission

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt start time.

3.2.4.6.3 Dedicated Debriefing - At those locations with a dedicated debriefing function, the contractor shall provide expanded debriefing support of a full-time debriefing expert in the squadron areas to perform ground system setup, mission preparation, and ACTS debriefing within the constraints of security and International Traffic in Arms Regulations

(ITAR) boundaries. The dedicated debriefing function shall encompass all necessary mission file preparation and ground system setup and additionally will include running the debriefing software during the debrief. When the mission requires Live Monitor, the dedicated debriefing function shall also include Live Monitor preparation, control, and data merging unless the site also has a separate full-time live mission requirement.

3.2.4.6.4 Debriefing Software Support - The contractor shall provide operator-level support for the common debriefing software products listed below. The support shall include installation, setup, configuration, operation, and usage of the software product.

Individual Combat Aircrew Debriefing System (ICADS)

Integrated Tactics Assessment System (ITAS)

Personal Computer Debriefing System (PCDS)

3.3 Maintenance

3.3.1 General Maintenance Activities

3.3.1.1 The contractor shall schedule and perform all preventive maintenance as required by system technical manuals. For equipment without technical manuals (either government or commercial), the contractor shall use best commercial practices for preventive upkeep.

3.3.1.2 The contractor shall schedule and perform corrective maintenance necessary to provide the required operational capability without disruption to mission operations.

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt

3.3.1.3 The contractor shall schedule and perform configuration maintenance actions such as Time Compliance Technical Orders, approved modifications

(temporary and permanent), and one-time inspections within the suspense established by configuration directive.

3.3.1.4 The contractor shall provide organizational-level software maintenance support for all ACTS software to include installation, removal, loading, flashing, rebooting, configuring, and operator-level troubleshooting of software failures. Within the constraints of the ACTS equipment, the contractor shall maintain operational backups of properly configured ACTS software.

3.3.1.5 The contractor shall be responsible for storage of ACTS equipment using government furnished facilities and equipment as listed in Appendix 7.

3.3.1.6 The contractor shall be responsible for account management, maintenance, upkeep, testing, troubleshooting, and repair of all assigned ACTS equipment.

3.3.1.7 The contractor shall establish and maintain an Equipment Corrosion Control

Program IAW AFI 32-10541001 and other governing directives listed in

Appendix 2.

3.3.1.8 The contractor shall perform Equipment Status Reporting (ESR) for all assigned ACTS equipment. The contractor shall accomplish ESR by entry of weekly ACTS performance data into the Reliability, Accountability, and

Maintainability for Pods (RAMPOD) system.

3.3.1.9 The contractor shall report all incidents involving any equipment lost or damaged during aircraft flight or flight line operations to the SAR/COR within 24 hours of discovering the item was lost or damaged. The contractor shall document this on an incident report and include details describing the item, incident, and circumstance. The contractor shall comply with any required associated safety reporting or investigation.

3.3.2 Airborne Instrumentation Systems (AIS) Maintenance

3.3.2.1 External (Pod) AIS Maintenance

3.3.2.1.1 The contractor shall schedule maintenance activities to complete pod

Formatted: Highlight

Commented [A29]: Recommend accepting change to prevent misunderstanding. As written originally, it could be construed to mean that the contractor only needs to report it after they’ve found the missing item or found that the item was missing.

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt operational checks before pod transport and loading to ensure only fully functional pods are loaded on aircraft. The contractor shall use established ACTS test/support equipment with approved technical manual procedures to determine full pod functionality.

3.3.2.1.2 The contractor shall perform both On-Equipment (on the pod) and Off-equipment (SRA on the bench) pod maintenance per the system technical manuals and system maintenance concept.

3.3.2.1.3 The contractor shall maintain the capability to replace malfunctioning cards/components within each SRAShop Replacement Assembly (SRA) as allowed by technical manual reparability codes and the system maintenance concept.

3.3.2.1.4 For pod failures discovered during scheduled maintenance, the contractor shall immediately take action to troubleshoot and repair the failed pod.

3.3.2.1.5 If a pod has been returned to maintenance because it was associated with a non-effective sortie, the contractor shall perform a complete bench check to confirm pod operations. If the pod fails the bench check, the contractor shall immediately take action to troubleshoot and repair the failed pod.

3.3.2.1.6 If a pod failure results in insufficient pods to accomplish the mission schedule, the contractor shall immediately notify the SAR/COR.

3.3.2.1.7 For pod failures that cannot be duplicated during the maintenance check, the contractor shall take the following actions:

3.3.2.1.7.1 If a “non-effective” sortie can directly be traced to an aircraft related failure or improper procedure, the contractor shall report the tail number and pod number to the SAR/COR and the appropriate maintenance center. The contractor shall return the pod to operational service.

3.3.2.1.7.2 If a “non-effective” sortie cannot directly be attributed to external factors, and the pod has passed all operational checks, the contractor shall use the pod in question on the next available sortie on a different aircraft and provide the results to the SAR/COR. If the pod in question flies a successful subsequent sortie, without any repairs or adjustments, Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt the pod will remain in service and the previous failure will be attributed to the aircraft, annotated, and declared an excusable sortie. If the pod in question results in a non-effective sortie on the different aircraft, the pod will be returned to maintenance for further troubleshooting.

3.3.2.1.8 The contractor shall store all assigned pods in a manner where they will not be exposed to precipitation or adverse weather effects. For the purposes of this guidance, a pod loaded on an aircraft is not considered stored. Pods may be left on a trailer or truck overnight if the vehicle is garaged or otherwise protected from weather effects.

3.3.2.2 Internal AIS Maintenance

3.3.2.2.1 The contractor shall not be responsible for direct maintenance of internal

AIS equipment such as the F-35 P5 Internal Mount (IM) even though the contractor will integrate data from this source (as described in para

3.2.2.2).

3.3.2.2.2 The contractor shall coordinate with the appropriate avionics shop whenever an internal AIS participant fails to join, track, relay data, or perform other critical function necessary for the overall ACTS mission success.

3.3.2.2.3 The contractor shall jointly troubleshoot internal AIS failures with the appropriate avionics shop to eliminate any common interface failures.

Such failures may include improper Site/AIS ID deconfliction, crypto/keying issues, airborne network configuration errors, and similar internal AIS integration issues.

3.3.3 Portable Instrumentation Systems Maintenance

3.3.3.1 Data Recorder Maintenance – The contractor shall maintain and support various types of portable instrumentation systems (data trackers, recorders, loggers) to satisfy operational requirements. These portable systems may be

GPS, Cellular, or SATCOM based devices used to collect data for integration with mission debriefings.

3.3.3.2 The contractor shall inventory, control, inspect, sustain, maintain, and troubleshoot data recorder equipment (cases, shells, memory cards, antennas, Formatted: Highlight

Formatted: Font: 16 pt

Formatted: Font: 16 pt

Formatted: Font: 16 pt cables, recharging stations, and batteries).

3.3.3.3 The contractor shall identify any parts, supplies, or full replacements needed to sustain the inventory of portable devices. The contractor shall provide an estimate for purchase of any replenishment items to the CO/COR for approval.