Atch 1_RPATS_PWS (Rev22Dec22)_Amd 0002.docx

PERFORMANCE WORK STATEMENT (PWS)

For

REMOTELY PILOTED AIRCRAFT TRAINING SUPPORT

(RPATS)

Holloman AFB, NM 08 March 2022 For Updates, See Page 2

Reviewed:

MIRANDA.STEPHEN.M.1175452750 digitally singed 2022.03.08 11:19:50 STEPHEN M. MIRANDA, MAJ, USAF Date Contracting Officer’s Representative (COR) 16th Training Squadron

DINWIDDIE.KYLE.BRENDAN.1286285208 digitally singed 2022.03.08 13:38:16 KYLE B. DINWIDDIE, Lt Col, USAF Date Director of Operations (DO) 16th Training Squadron

REN.PATTI.J.1083572775 digitally singed 2022.03.08 14:48:27 PATTI J. REN, Civ, DAF Date Quality Assurance Program Coordinator (QAPC) 49th Contracting Squadron

Approved By:

ROBERTS.SALLY.D.1145173481 digitally singed 2022.03.08 14:40:10 SALLY D. ROBERTS, Civ, DAF Date Contracting Officer (CO) 49th Contracting Squadron

TABLE OF CONTENTS

Updates Changes are reflected by the symbol "|" in the right-hand margin.

Amd 0002 – 22 Dec 22 – Updates Sol. #, para. numbering 1.3.2.4.1 & 1.3.2.4.2, added para. 1.3.4.7

1.0 DESCRIPTION OF SERVICES

Holloman Air Force Base provides Remotely Piloted Aircraft (RPA) Training Support (RPATS) and has a requirement for non-personal training support services.

The Contractor shall provide all management, tools, supplies, equipment, supervision, labor, and all other items and services required to perform RPATS requirements. The Contractor shall provide enough personnel for 80 training events per day as either MQ-9 Aircrew Training Device (ATD) events (12 to 15 concurrent, up to 22 concurrent on non-flying days), MQ-9 flightline events (7 to 12 concurrent), or Desktop Trainer (DTT) events throughout a 16 hour training day. The Contractor shall also provide administrative support staff at the squadron level in accordance with (IAW) this Performance Work Statement (PWS).

1.1 REQUIRED PLANS

1.1.1 Management Plan. It is of the utmost importance that the Contractor be able to meet the staffing needs not only on a regular workday of expected work, but also if work increases throughout the contract period of performance

1.1.1.1 The Contractor must be able to provide a reliable infrastructure to manage their personnel in multiple different locations (subject to change) at Holloman AFB under the administrative control of the 49th Operations Group (OG). These locations currently are: Bldg 513 (16 Training Squadrion (TRS) & Unclassified Simulators), Bldg 513B (16 TRS Trailer), Bldg 319 (16 TRS & Classified Simulators), Bldg 45 (6th Attack Squadron (ATKS), 9th ATKS, 29th ATKS and Flying Operations).

1.1.1.2 The Contractor shall prepare and submit a management plan for the base and option years that will outline your method, approach, and procedures that will support the requirements of the PWS.

1.1.1.3 Teaming Agreement, Joint Venture, or Subcontracting: If multiple Contractors are proposed, the Contractor must explain in detail the management structure and how Quality Controls (QC) will be maintained IAW the requirements of the PWS.

1.1.2 Organizational Plan. The Contractor shall provide an organizational plan to include an adequate number of personnel to ensure mission success. At a minimum, the plan shall include an organizational chart with each position, outlined in the PWS, and state whether the position will be full or part time and the hours of operations. After award, the plan shall be updated to include the names, title and phone numbers of key personnel.

1.1.3 Staffing and Retention Plan. The Contractor shall employ hiring and retention practices that allow the Contractor to identify, screen, place, monitor, train, and retain qualified candidates to fulfill service requirements under this contract. Contractor shall propose personnel that are capable of passing a SECRET background clearance for the Site-Lead, Simulated Mission Operator (SMO), Simulator Tactical Programmer (STP), Integrated Mission Developer (IMD), and Simulator Duty Director (SDD), positions. Contractor Administrative Support composed of Mission Support Scheduler (MSS), Flight Training (DOT), Squadron Standardizations and Evaluations (Stan/Eval) (CCV), and Group Stan/Eval (OVG) does not require a security clearance. All Contractor employees, regardless of position or clearance requirements, must also pass the additional internal checks performed by Holloman AFB.

1.1.3.1 On day one of the contract, the Key person shall be cleared and ready to begin work. At least 50% of SMOs, STPs, and SDDs shall have an active SECRET or Interim SECRET clearance upon beginning the contract. The remaining personnel shall have an active SECRET or Interim SECRET clearance within 30 calendar days. During the performance of the contract, any vacancies and extended leave, (i.e. maternity, medical, etc.) must be filled by qualified personnel within 30 calendar days. Extended leave is any leave period beyond 21 calendar days. All Contractor employees shall obtain and maintain a final adjudicated SECRET clearance within six (6) months of first day of work in order to remain employed under this contract if required by their position.

1.1.3.2 Removal of Personnel: The Contractor will notify the 16 TRS Contracting Officer’s Representative (COR) immediately of all contract personnel working on this contract that were removed or resigned.

1.1.3.3 The Contractor shall prepare and submit a staffing plan for the base and option years that will outline your method, approach, and procedures in scheduling, staffing, and retention, that will support the requirements of the PWS.

1.1.4 Contingency Plan. The Contractor shall submit a contingency plan for weather or maintenance that could cause delays, recalls, or cancellations as well as a contingency plan for syllabus updates. This contingency plan will address the allocation of personnel, the potential impact to the 80 daily required events, and the duration of impact if necessary. The Contractor will maintain an up-to-date contingency plan for the MSS and SDD to reference as needed.

1.1.5 Contractor Continuation Training (CCT) Plan. The CCT Plan is a Contractor developed, COR approved, qualification training plan to ensure that all SMOs are initially trained in all events and maintain proficiency in all events required in the MQ-9 Syllabus. The CCT Plan will include, at a minimum: training plan for new SMOs; definitions between experienced/inexperienced SMOs; the frequency of event types for experienced/inexperienced SMOs; a method for tracking continuation training (CT); and a re-qualification plan for non-current personnel.

1.1.5.1 The CCT Plan will include a general training plan for new syllabus releases, as well as ATD, Flightline, and DTT hardware or software updates. If an updated syllabus, new hardware, or software updates require training for SMOs, the Site-Lead will notify the COR and 16 TRS/DO of the training requirements and submit a training plan per the CCT to have 50% of affected personnel trained within ten (10) business days and 100% within twenty (20) business days of the first day of implementation.

1.1.5.1.1 If additional training results in reduced event capacity, the Site-Lead will notify the COR with the training plan, hours allotted, and await CO approval prior to proceeding.

1.1.5.2 Within calendar 30 days after award, the Contractor will submit a CCT Plan to the COR. The COR will review the plan, provide the Site-Lead with feedback or corrections as required, and approve the plan.

1.2 KEY PERSONNEL

1.2.1 Site-Lead

The Site Lead is a Full Time Equivalent (FTE) position and shall not be performed as an additional duty by another employee.

1.2.1.1 The primary duty is to provide supervision and positive control of the Contractor’s workforce, provide administrative support to ATD programs (e.g. Predator Mission Aircrew Training System (PMATS), Medium Altitude Long Endurance Tactical (MALET) Joint Technology Center (JTC) Systems Integration Laboratories (JSIL) Aircrew Trainer (MJAT) Standalong Aircrew Trainer (MSAT), or equivalent) and provide support to squadrons’ technical programs. The Site Lead is the Contractor’s primary point of contact and shall be empowered to make decisions related to the day-to-day administration of the Site and the contract. However, the Site Lead is not expected to make decisions that will cause financial obligations on the Contractor.

1.2.1.2 The Site Lead shall be responsible for meeting the requirements of the PWS and deliverables. Duties include but are not limited to:

1.2.1.2.1 Ensuring the Syllabus Event Allotment List (SEAL) is followed. The COR or 16 TRS Director of Operations (DO) will provide a list of syllabus mission events that require less oversight as well as an event count qualifier for such an event type (i.e.: Transition (TR) event that requires only setup and 15 minutes of additional oversight during can count as 1/2 or 0.5 events. Such an event, can be run simultaneously by one SMO on two simulators; Kill Chain (KC) event only requires a single additional asset while flying. Such an event can count as 1/3 or 0.33 events and the SMO can simultaneously support another event).

1.2.1.2.1.1 The SEAL will only reduce the workload of simultaneous events. For example, three (3) TR events executed concurrently in the same simulator bay will count as one (1) event towards the 80 events. Three (3) TR events executed consecutively will count as three (3) events towards the 80 events.

1.2.1.2.1.2 The SEAL will also include requirements for non-syllabus events such as, but not limited to, CT, Launch and Recover (LR), or Distinguished Visitor (DV) visits.

1.2.1.2.1.3 The SEAL is based off the current MQ-9 Syllabus. The MQ-9 Syllabus may be updated as often as every six (6) months to every two (2) years.

1.2.1.2.2 Modify the current CCT Plan or develop a new CCT plan, as required, in accordance with Para 1.1.5.

1.2.1.2.2.1 The COR may request a modification (less than 25% change or syllabus update) to the CCT Plan from the Site-Lead at any time. Upon request, the COR will establish a due-date for a modified CCT Plan draft, no earlier than ten (10) business days from request.

1.2.1.2.2.2 The COR may request a new (25% or more change, not syllabus specific) CCT Plan developed. Prior to request, the COR must consult the Contracting Officer (CO) regarding purpose for new development. Upon CO approval, the COR will notify the Site-Lead and establish a due-date for a new CCT Plan, no earlier than 30 calendar days from notification.

1.2.1.2.3 Debrief Forms. The Site-Lead is responsible for developing and maintaining the 16 TRS Maintenance (MX) Debrief Form and 16 TRS Scenario Debrief Form. The purpose of these forms is to capture either maintenance or scenario discrepancies that detract from efficient learning. At any point, the Site-Lead may update these forms to increase or decrease data collection, as required. The COR or 16 TRS/DO may direct updates as well.

1.2.1.2.4 The Site-Lead will keep an updated list of contingency plans for the MSS and SDD to reference as required. If a contingency plan is executed, the Site-Lead will report to the COR or 16 TRS/DO the results from the day and will make corrections or additions to the contingency plans, as required.

1.2.1.2.5 The Site-Lead will maintain and post a Letter of Xs (LOXs) detailing the current status of qualifications for all individuals qualified to perform SMO duties. The LOXs will be visibly posted after a change in personnel or contractor completion of training per the CCT (para. 1.1.5) and sent to the COR within two (2) business days. Reference Appendix C for an example LOXs.

1.2.1.2.6 The Site-Lead may perform MSS duties in the absence of the MSS.

1.2.1.2.7 Produce weekly summary of ATD utilization reports IAW government needs.

1.2.1.2.8 Periodically inspect the all contract positions listed in this PWS to ensure they are complying with this PWS.

1.2.1.2.9 Contractor shall provide a Monthly Activity Report detailing duties performed to the COR not later than seven (7) business days after the end of the reporting month. The COR may adjust these requirements at any time. At a minimum the report will include:

1.2.1.2.9.1 Number of Contractor personnel assigned by duty position and qualifications

1.2.1.2.9.2 ATD, Flightline, and DTT summary

1.2.1.2.9.2.1 Events requiring support (gross and net) and the number of events supported for each type

1.2.1.2.9.2.2 Total support hours for each type (partial support will list as partial hours)

1.2.1.2.9.2.3 Summary of Day of Execution (DOE) add-ons or changes

1.2.1.2.9.3 Simulator Tactical Programmer scenarios complete, revised, and uploaded to simulators

1.2.1.2.9.4 Administrative Support Summary

1.2.1.2.9.4.1 MSS Support

1.2.1.2.9.4.1.1 Summary of CTT activities

1.2.1.2.9.4.1.2 Number and type of CCT Deviations

1.2.1.2.9.4.1.3 Days where squadron schedule was released or there was a change after 1530 Local (L)

1.2.1.2.9.4.2 DOT Support Activities

1.2.1.2.9.4.3 CCV Support Activities

1.2.1.2.9.4.4 Group CCV Support Activities

1.2.2 Simulated Mission Operator (SMO)

Formerly Simulator Console Operator (SCO) and GCS Scenario Support (GSS)

1.2.2.1 The primary duty of the SMO is to provide real time training event mission support for either ATD events, MQ-9 flightline events, and/or DTT events. SMOs support will include Emergency Procedure Evaluations (EPE) (ATD only), LR (ATD only), CT, MQ-9 Formal Training Unit (FTU) syllabus missions, student practice missions (ATD only), debriefs, and DV and/or guest demonstrations. Events will last between 2.0 to 3.0 hours. Events exceeding 3.0 hours will count as an additional event per the SEAL for every additional 3.0 hours.

1.2.2.1.1 ATD. ATDs are located in either Building 513, Building 319 (classified simulators), or inside a Ground Control Station (GCS). The SMO shall arrive 15 minutes prior to the scheduled start time of the event and is responsible for loading the appropriately scheduled missions ahead of the arrival of the instructor and student crew scheduled for the simulator. The SMO shall provide troubleshooting assistance for maintenance or programming issues that may occur. The SMO shall coordinate with the Simulator Duty Director to resolve malfunctions. The SMO shall ensure that any maintenance or system malfunctions are captured and written on the 16 TRS ATD MX Debrief Form after each Sim.

1.2.2.1.2 Flightline. The SMO shall be available 15 minutes prior to the scheduled start time of the event and is responsible for coordinating with the MQ-9 instructor. The SMO will create a realistic approximation of real-world combat operations by simulating the functions of other entities via Intercom or mIRC software.

1.2.2.2 DTT. The SMO shall be trained to operate DTT events. DTT events are comprised of up to ten (10) small student ATDs and up to two (2) instructor ATDs in a single room designed to run concurrently. When scheduled as a syllabus or CT event, the DTTs running concurrently in a single room will count as a single event within the timeframe listed in paragraph 1.2.2. The SMO will ensure the proper scenario is loaded into each DTT at least 15 minutes prior to the start of the event. From 0600 to 1800 when no events are scheduled, the DTTs will be pre-loaded with profiles as directed by the COR for student or instructor walk-ins.

1.2.2.1.1 The 6 ATKS, 9 ATKS, and 29 ATKS have individual standalone DTTs ready for instructor or student practice. From 0600 to 1800, the DTTs will be pre-loaded with a profile as directed by the COR for crew practice. Additionally, the Contractor will provide a setup binder for each squadron DTT to reduce Contractor oversight of the device. The binder will include at the minimum, instructions to begin a scenario, reload weapons, change weather, ending a scenario, and the SDD contact information. A SMO may be requested to help diagnose any maintenance or scenario with the DTT. If a SMO is requested, they will report to the squadron’s DTT within 20 minutes of the request. Support for squadron DTTs does not count towards daily events.

1.2.2.2 SMOs will maintain an immediate presence during the conduct of scheduled mission events in order to provide real-time tactical adjustments as directed by the instructor or CT crew in accordance with the SEAL.

1.2.2.3 The SMO will inject pre-planned inputs taken from scripts provided by the Government via voice communications, via the multi-user Internet Relay Chat (mIRC) program, or directly into the ATD. During the event, the SMO will manage a government provided real-time flight tracking program (such as Zeus) by having the software loaded and configured for the event. The SMO will simulate Air Traffic Control (ATC)/Control and Reporting Center (CRC) and provide threat updates per scripts or instructor injects. Additionally, SMOs will function as Joint Personnel Recovery Center (JPRC), intelligence coordinators, intelligence screeners and other players that normally interact with RPA mission crews as detailed in the mission scenario dance cards and instructor pilot/sensor guidance.

1.2.2.4 Use current joint close air support doctrine (from Joint Publication (JP) 3-09.3) brevity terms (from Air Land and Sea Applications (ALSA) brevity), current Tactics, Techniques, and Procedures (TTPs) (such as Air Force Tactics Techniques and Procedures (AFTTP) 3-1.MQ-9 or AFTTP 3-3 MQ-9, etc.) and other applicable doctrine. Follow current Wing guidance from 49th Wing FTU Special Instructions (SPINS) and Weapon Attack Guide (WAG).

1.2.2.5 The maximum number of simulator events any SMO can operate simultaneously is three (3), regardless of SEAL event type. Any simultaneous simulators must be operated within the same bay/hallway where the SMO can respond immediately to an instructor request. SMOs will not simultaneously support a simulator and an airborne flightline event. Additionally, any flightline simulator event (when simulator is physically located in a GCS) will count as a single event and will not be operated by a single SMO simultaneously with another event, regardless of SEAL event type.

1.2.2.6 The SMO will make the 16 TRS Scenario Debrief Form available to the crew upon completion of the event. The SMO shall also ensure that any forms from the crew are turned into the Simulator Duty Director (SDD) desk and that the SDD understands the issues before the end of the training day.

1.2.2.7 If an event is cancelled, the SMO will contact the MSS or SDD, notify him/her of the cancelled event and justification, then will await further tasking from the MSS.

1.2.2.8 Trained to open and close areas certified for SECRET open storage and be able to maintain a presence in the storage area during the 16 hour training day.

1.2.2.9 ATD, Flightline, and DTT system or software updates. When additional capabilities or software updates require training for SMOs, the Contractor will follow the CCT.

1.2.2.10 The government is prepared to execute, via modification, optional Contract Line Item Numbers (CLINs) to increase the number of supported SMO daily events due to a workload increase. The optional CLINs are structured as follows:

OPTION CLIN: Increase maximum number of daily SMO daily events by 5 to 85 OPTION CLIN: Increase maximum number of daily SMO daily events by 5 to 90 OPTION CLIN: Increase maximum number of daily SMO daily events by 5 to 95 OPTION CLIN: Increase maximum number of daily SMO daily events by 5 to 100 OPTION CLIN: Increase maximum number of daily SMO daily events by 5 to 105 If any of these Optional CLINs are executed, the Contractor shall have 60 days from CLIN execution to train new personnel and execute the new event totals. Each Option CLIN will remain in effect until the end of the current period of performance.

1.2.3 Simulator Tactical Programmer (STP)

The primary duty is the construction, maintenance adaption, correction and troubleshooting of ATD and DTT mission scenarios for all training events. STPs will be trained and qualified to perform as SMOs for either simulator events or flightline simulator events. STPs may be trained to perform SDD duties.

1.2.3.1 ATD mission scenarios will include air to ground munition (AGM) 114, Guided bomb unit (GBU)-12, and GBU-38 weapons profiles, robust target array visual setups to include explosions, patterns of life, vehicular travel, city construction, road patrols with Improvised Explosive Devices (IEDs), and other real-world scenarios in accordance with (IAW) training syllabi, real time flight tracking program updates, and map updates to the ATD. The scenarios for the STPs to build will be provided by the government, and will be accepted by the appropriate military subject matter expert (SME) as determined by the 16 TRS/DO. The tactical programmer shall also transfer files as requested by instructors between the base network and the simulator dedicated network prior to scheduled events so they are available in the ATD during training.

1.2.3.2 At least one STP will be available during all operating hours. The STP will assist the SDD as needed for simulator maintenance, DTT support, or to perform SDD duties as needed if the SDD is not available.

1.2.3.3 STPs may perform as SMOs on either simulator events or flightline simulator events. An STP will not be scheduled more than two (2) simulator events per week. In the event of MQ-9 flightline airborne events converting to flightline simulator events, an STP may be utilized as additional support on the flightline to meet scheduling adjustments. While filling in as an SMO, the Contractor is still required to meet the STP workload.

1.2.3.4 The programmer(s) will also ensure to applicable associated publications. technical orders, and checklists are up to date on ATDs and DTTs (if required) when changes are released IAW lists from the 49th OGV shop. STPs will review the 49 OGV Master Publication Index (MPI) at least monthly to verify products are up to date.

1.2.3.5 At least one programmer will attend weekly Phase Manager meetings when scheduled.

1.2.4 Integrated Mission Developer (IMD)

Formerly Tactical Scenario Support (TSS) The primary duty of IMD is to ensure both simulator and flight mission scenarios are vetted and standardized across the 6th ATKS, 9th ATKS, and 29th ATKS. IMDs will observe full events to ensure products meet the requirements for training. IMDs will also be trained and qualified to perform as SMOs for either simulator events or flightline simulator events. IMDs may be trained to perform SDD duties. The normal duty day for these positions is M - F 0730 – 1630L.

1.2.4.1 To meet MQ-9 Syllabus requirements, simulator and flight scenario products include, but are not limited to: Mission Briefs; Threat Briefings; detailed Mission Scenario plans (“dance card”/scripts); and Tactical Situational Awareness Tool (TACSIT) profiles. Duties may include coordinating with training shops, weapons shops, and stan/eval for scenario standardization and compliance. IMDs will coordinate with Joint Tactical Air Controllers (JTACs), SMOs, and STPs as needed for scenario feedback clarification. Additionally, they will coordinate with STPs to ensure simulator scenarios are updated and implemented. IMDs will ensure that mission products are formatted and posted to the appropriate locations per the 16 TRS COR.

1.2.4.2 IMDs will continuously review products produced.

1.2.4.2.1 An IMD shall schedule to observe a full event (prebrief, brief, mission, debrief) at least once per week. The event will be with at least one (1) experienced MQ-9 instructor (pilot or sensor operator). Event observations will be conducted evenly between ATDs and Flightline, with no more than 60% of either observed, with at least one (1) DTT observed, per calendar quarter. IMDs will interview the instructors for their inputs on any given scenario. They must observe at least one of each type of syllabus event per calendar quarter and will prioritize event types through the 16 TRS COR. An event types list shall be provided by the 16 TRS COR no later than ten (10) business days before the beginning of the next quarter. Within two (2) business days after an event, the IMD will report to the 16 TRS COR and 16 TRS Weapons and Tactics (OSK) the findings of the observation, make recommendations, and then implement improvements as directed.

1.2.4.2.2 IMDs will review and input all 16 TRS Scenario Debrief Forms weekly into a tracker and submit them to the 16 TRS COR and OSK.

1.2.4.3 IMDs may perform as SMOs on either simulator events or flightline simulator events. An IMD will not be scheduled more than two (2) simulator events per week. In the event of MQ-9 flightline airborne events converting to flightline simulator events, an IMD may be utilized as additional support on the flightline. Flightline airborne events converted to flightline simulator events have priority over IMD observations. While filling in as an SMO, the Contractor is still required to meet the IMD workload.

1.2.4.4 If trained, the IMD may perform SDD duties as needed if the SDD is not available.

1.2.4.5 At least one IMD will attend weekly Phase Manager meetings when scheduled.

1.2.5 Administrative Support, Mission Support Scheduler (MSS) The MSS is a required position and will not be the primary duty of any other Contractor.

The primary duty is to provide efficient and effective scheduling of support for 49 OG mission supported events. The MSS will maintain communication with the FTU squadron scheduling shops. The MSS will compile the daily event support schedule after the daily schedule for all flying squadrons are released, usually by 1500 local. The MSS shall assign SMOs to ATD missions, flight events, DTT events, and any CTT training as required. The MSS will post the schedule NLT 1630 local and the schedule shall be made available to the 16 TRS/COR and 16 TRS/DO for periodic review.

1.2.5.1 A typically schedule will require daily support for 50-60 ATD events and 20-30 flightline events per day for a 80 event per day maximum. These events are 100% interchangeable at the government’s discretion. If at any point, the combination of events requested by the FTU squadron scheduling shops exceed 80 events per the SEAL, the MSS will immediately notify the 16 TRS/COR or 16 TRS/DO for resolution. The MSS will not directly adjust crews to meet SEAL requirements. The MSS can coordinate with FTU squadron scheduling shops to help meet SEAL requirements.

1.2.5.1.1 In the event of a late schedule release or change, the MSS will maintain the ability to update the daily event support schedule if affected.

1.2.5.1.2 On days when weather, maintenance, or other unplanned events affects the schedule, the MSS will be prepared to coordinate with the SDD to execute the appropriate contingency plan. No later than the next duty day, the MSS will report to the Site-Lead the results of executing the contingency plan.

1.2.5.2 On days where less than 80 events are requested, the MSS will ensure a at least one SMO is available for walk-in support for student practice events or other events from 0700-1700. This requirement is not a priority over scheduled syllabus missions and is not intended to extend support hours past 80 total events daily.

1.2.5.2.1 Additionally, the MSS will ensure remaining SMOs are scheduled to follow the CCT plan. The MSS will submit any deviations from the CCT plan to the Site-Lead and COR.

1.2.5.3 Air Education and Training Command (AETC) Family Days, No-Fly days, Training days, etc. On days where zero (0) events are requested, the MSS will verify with the COR whether or not to have ATD bays prepared for walk-ins. Additionally, the MSS will submit a training plan for the day, approved by the site-lead, to the COR and 16 TRS/DO no later than 1600L two (2) business days prior to the training day. Such training can include, but is not limited to, mandatory government training (briefings, CBTs, etc), addressing and resolving 16 TRS ATD MX Debrief Form critiques, practicing recently developed scenarios, evaluating performance, or CCT as described in the CCT plan.

1.2.5.4 Will ensure that STPs and IMDs are not scheduled more than two (2) times a week per STP or IMD for SMO duties. Any additional scheduling the day prior requires COR approval.

1.2.5.4.1 If an unscheduled event (weather, maintenance, unscheduled absence, etc) occurs and an STP or IMD is necessary to support the mission event based off the current day’s event support schedule, the MSS will schedule the STP or IMD. Such an occurrence will count towards the STP and IMD weekly total. If the total weekly events for the individual scheduled is more than the two (2) authorized, the MSS will send email notification to both the COR and Site-Lead.

1.2.6 Administrative Support, Flight Training (DOT) Program

The primary duty is to provide administrative support to each of the flying squadron’s (6 ATKS, 9 ATKS, 29 ATKS) training programs at the direction of the ATKS DO. The normal duty day for these positions is M - F 0730 – 1630L. The duties include:

1.2.6.1 Reviews and updates student and permanent party flight training grade books via paper binders or digital records in a government-provided Training Management System IAW Air Force Manual (AFMAN) 11-202V1, AFMAN 11-2MQ-9V1, associated Holloman Air Force Base (AFB) supplements, locally developed guidance, and per the direction of their assigned ATKS DO.

1.2.6.1.1 Maintain a log of grade book discrepancies and submits finding to their assigned ATKS DO and 16 TRS/COR monthly, NLT five (5) business days after the month has ended.

1.2.6.2 Upon instructor or student flying qualification change, generate an AF 4324, Aircraft Assignment/Aircrew Qualification worksheet. Submit form to the local Squadron Avaition Resource Management (SARM) or Host Aviation Resource Management (HARM) as required.

1.2.6.3 Generates training aids for training days as requested.

1.2.6.4 Performs regular currency check of personnel training (including ancillary) and notifies ATKS DO of overdue training. ATKS DO may request a specific frequency of currency checks through the 16 TRS/COR, not to be accomplished more often than once per week.

1.2.6.5 Prepares and executes periodic training schedule.

1.2.6.6 Generates ATKS bi-monthly LOXs.

1.2.6.7 Operates various office equipment such as faxes, copiers, phones, and computers.

1.2.6.8 Prepares reports, memos, letters, forms, briefings, and other documents utilizing Microsoft Word, Excel, Access, and Power-Point.

1.2.6.9 Greets RPA students, answers phone call from instructors/students, and handles their inquiries.

1.2.6.10 Establishes and maintains both paper and electronic filing systems IAW Air Force Instruction (AFI) 33-322, AFI 33-332, and associated Holloman AFB guidance.

1.2.6.11 Opens, reads, routes, and distributes incoming paper and electronic correspondence.

1.2.6.12 Prepares routine letters, reviews documents for correct grammar and spelling and ensures compliance with group, wing, and Higher Headquarters (HHQ) instructions.

1.2.7 Administrative Support, Squadron Standardization and Evaluation (CCV) Program The primary duty is to provide administrative support to each of the Flying Squadron’s (6 ATKS, 9 ATKS, 29 ATKS) Stan/Eval shops. The normal duty day for these positions is M-F 0730-1630. The duties include:

1.2.7.1 Management and control of the MQ-9 flight testing materials. Administers testing for permanent party and students.

1.2.7.2 Updating testing and flight evaluation data in the Patriot Excalibur (PEX), Graduate Training Integration Management System (GTIMS), and any other locally developed software.

1.2.7.3 Reviews and updates student and permanent party stan/eval folders.

1.2.7.3.1 Folders are updated IAW AFI 11-202V2, AFMAN 11-2MQ-9V2, associate Holloman AFB supplements, and locally developed guidance.

1.2.7.3.2 Generate, review, track, and update evaluation documentation (Form 8s, 1522s, etc) and submit to their respective SARM office, as required.

1.2.7.4 Operates various office equipment such as faxes, copiers, phones, and computers.

1.2.7.5 Prepares reports, memos, letters, forms, briefings, and other documents utilizing Microsoft Word, Excel, Access, and Power-Point.

1.2.7.6 Greets RPA students, answers phone calls from instructor/students, and handles their inquiries.

1.2.7.7 Establishes and maintains both paper and electronic filing systems IAW USAF AFI 33-322, 33-332 and other associated Holloman AFB guidance.

1.2.7.8 Opens, reads, routes, and distributes incoming paper and electronic correspondence.

1.2.7.9 Prepares routine letters, reviews documents for correct grammar and spelling and ensures compliance with group, wing, and HHQ instructions.

1.2.8 Administrative Support, Standardizations and Evaluations Lead (OGVL) The primary duty is to provide administrative support to 49th Operations Group Standardization and Evaluation (49 OGV), act as the main Point of Contact (POC) for OGV, and provide oversite for Administrative Support Standardization and Evaluation (CCV). The OGVL will be competent in fulfilling all the requirements of Administrative Support CCV (PWS 1.2.7). Additionally, the OGVL will be the SME for the current flight training software (GTIMS) and will provide training to other Contractors in this PWS, as required. The normal duty day for these positions is M-F 0730-1630.

1.2.8.1 Ensures draft Form 8’s from Squadron CCV shops meet AFI 11-202V2, AFMAN 11-2MQ-9V2, associated Holloman AFB supplements, and locally developed guidance. Validates all non-standard entries with OGV personnel and returns feedback to the squadron CCVs.

1.2.8.1.1 Will maintain an archive of non-standard Form-8s. All Form 8s in archive will have all names and Personally Identifiable Information (PII) redacted prior to placement into the archive. The archive will be maintained at the direction of the Chief of OGV and be made available to the COR upon request.

1.2.8.2 The OGVL will validate available digital libraries per the Master Publication Index (MPI) at least quarterly. Any discrepancies will be reported to OGV. The OGVL will maintain the ability to update the digital library at the direction of OGV.

1.2.8.2.1 The OGVL will not inspect the contents of the publications inside the digital library beyond the title page of the document.

1.2.9 Simulator Duty Director (SDD)

The primary duty is to execute the simulator schedule in accordance with guidance provided by the 16TRS/DO and to provide administrative accountability to ATD programs. Starting 15 minutes prior to published simulator hours and until the end of published simulator hours, the SDD will maintain a presence at the Step Desk next to the simulators. Prior to each simulator event the SDD will brief the incoming crew on the availability of their simulator and ensure instructors are qualified to perform the day’s events. After each simulator event, the SDD will collect any noted discrepancies and record mission effectiveness.

Additional duties include but are not limited to:

1.2.9.1 Update time trackers, and record and track debrief forms daily.

1.2.9.2 Contact and work directly with 6th, 9th and 29th ATKS scheduling shops and Top-3 to manage the training in real-time and coordinate to make changes when able to maximize simulator training. Manage and adjust when necessary the schedule of SMOs against events.

1.2.9.3 Schedule/assign briefing/debriefing rooms to crews on the daily schedule to maximize effective training. Send End of Day report to Site-Lead and COR regarding effectiveness of ATD training.

1.2.9.4 Maintain and distribute forms to crews or SMO.

1.2.9.4.1 Will ensure all crews receive and return the 16 TRS ATD MX Debrief Form. Upon form return, records all discrepancies are captured. Any non-effective events due to MX will be submitted in an End of Day report.

1.2.9.4.2 Will ensure the SMO has a 16 TRS Scenario Debrief Form for crews. Collects both blank and filled out forms. Ensures all completed 16 TRS Scenario Debrief Forms are given to the IMDs no later than the next duty day.

1.2.9.4.3 Maintain blank AFTO 781s and deliver to respective SARM office NLT next duty day as applicable (i.e. network degraded requiring paper 781s).

1.2.9.4.4 Store and update (as changes are introduced) “paper” copies of required flying publications (checklists and In-Flight Guides) for the ATD when/if provided by the Government.

1.2.9.4.5 Collect and review paperwork packet to ensure paperwork is complete. Confirm if each mission crew submitted paperwork. If any crew’s packet is missing, send notification to crews and crews’ ATKS DO.

1.2.9.5 Assist crews with locating maintenance, SMOs, STPs, or simulator MX support when necessary to troubleshoot a malfunction. This position is intended to be the primary point of contact for crews if they have any trouble with their simulator.

1.2.9.6 Sign out headsets for daily use, as required. Contractor is not financially liable for headset loss, however, they will ensure all headsets are signed out in a log.

1.2.10 Simulated Air Traffic Control Center (SATCC)

10. The primary duty of the SATCC is to provide real time communcations support for only ATD or DTT events. SATCC support may include the following types of events when accomplished in ATD or DTT setting: EPE, LR, CT, MQ-9 Formal Training Unit (FTU) syllabus missions, student practice missions, and DV and/or guest demonstrations. Events will last between 2.0 to 3.0 hours.

10. SATCC will maintain a constant presence during the execution of the scheduled mission events in order to provide real-time tactical communications as directed by the instructor or CT crew in accordance with the SEAL.

10. The SATCC will inject pre-planned inputs taken from scripts provided by the Government via voice communications (radio) and MIRC. The SATCC will simulate Air Traffic Control (ATC) that normally interacts with RPA mission crews as detailed in the mission scenario dance cards and instructor pilot/sensor guidance.

10. The SATCC will cover a 16 hour training day and support 5 simultaneious events, as directed by the FTU. Normal operational times may be shifted to support exercises. The FTU will provide the contractor one week notice prior to the schedule change.

10. The government is prepared to execute, via modification, optional Contract Line Item Numbers (CLINs) to increase the number of supported daily events due to a workload increase. The optional CLINs are structured as follows:

OPTION CLIN: Increase maximum number of simultaneous events by 5 to 10 OPTION CLIN: Increase maximum number of simultaneous events by 5 to 15 OPTION CLIN: Increase maximum number of simultaneous events by 5 to 20

If any of these Optional CLINs are executed, the Contractor shall have 60 days from CLIN execution to train new personnel and execute the new event totals. Each CLIN will remain in effect until the end of the current period of performance.

1.3 CONTRACTOR QUALIFICATIONS

1.3.1 Site-Lead (1.2.1)

1.3.1.1 Shall have a minimum of three (3) years’ experience with flight training simulators.

1.3.1.2 Minimum of SECRET Security Clearance.

1.3.1.3 Six (6) months experience in schedule execution with one of the following; PEX, GTIMS, or other scheduling software tools.

1.3.1.4 The candidate must be able to multi-task and coordinate with multiple other units on a daily basis.

1.3.1.5 Must have an Intermediate Level Proficiency of Microsoft Office suite of products.

1.3.2 SMO (1.2.2), STP (1.2.3), IMD (1.2.4)

1.3.2.1 Minimum of SECRET Security Clearance.

1.3.2.2 Must have at least one of the following:

1.3.2.2.1 One (1) year of MQ-1 or MQ-9 simulator (ATD) experience

1.3.2.2.2 Two (2) years of experience executing military flight simulator training

1.3.2.2.3 Two (2) years of Close Air Support (CAS) operational experience as a qualified aircrew member, intel support, or JTAC. Ideal candidates will have MQ-1/9 experience.

1.3.2.3 Experience working in a dynamic high stress environment.

1.3.2.4 Desired Qualifications:

1.3.2.4.1 Familiarity with MQ-9 TACSITs, mIRC, and normal government software (i.e. Microsoft Office products) and hardware.

1.3.2.4.2 Previously qualified as MQ-1 or MQ-9 mission intelligence coordinator, pilot, sensor operator or air battle manager.

1.3.3 DOT (1.2.6), CCV (1.2.7), OGVL (1.2.8)

1.3.3.1 Must have an Intermediate Level Proficiency of Microsoft Office suite of products.

1.3.3.2 At least one of the following:

1.3.3.2.1 Six (6) year of administrative support experience with PEX, GTIMS, or similar commercial flight scheduling software.

1.3.3.2.2 Six (6) months of records management experience.

1.3.4 MSS (1.2.5), SDD (1.2.9)

1.3.4.1 Must have at least six (6) months experience in scheduling and schedule execution with either of the following: PEX, GTIMS, or other similar scheduling tools.

1.3.4.2 Must have six (6) months experience managing resources or people.

1.3.4.3 Must be able to multi-task and coordinate with multiple other units on a daily basis.

1.3.4.4 Must have an Intermediate Level Proficiency of Microsoft Office suite of products.

1.3.4.5 Six (6) months of records management experience.

1.3.4.6 A military background with MQ-1/9s is desired, but not required.

1.3.4.7 Minimum of SECRET Security Clearance

1.3.5 SATCC (1.2.10)

1.3.5.1 Minimum of SECRET Security Clearance.

1.3.5.2 Must have at least one of the following:

1.3.5.2.1 One (1) year of Air Traffic Control experience.

1.3.5.2.2 Two (2) years of experience as a professional aviator communicating with ATC and Radar Approach Control RAPCON .

1.3.5.3 Experience working in a dynamic high stress environment (i.e. real world military or civilian ATC, or TACP experience).

1.3.5.4 Desired Qualifications:

1.3.5.4.1 Familiarity with MQ-9 TACSITs, mIRC, and normal government software (i.e. Microsoft Office products) and hardware (i.e. military computer procedures and SCIF procedures).

1.4 CONTRACTOR TRAVEL

1.4.1 The Government may elect to send one (1) Contractor on Temporary Duty (TDY) to become a SME for new software, hardware, or syllabus changes. Such updates may include, but are not limited to: new scheduling software; new simulator hardware; or a Syllabus Review Board (SRB).

1.4.1.1 The SME is expected to train other Contractors upon return.

1.4.1.2 If the SME is terminated from the contract, the Government will not send another Contractor TDY to become a new SME.

1.5 SERVICE CONTRACT REPORTING

1.5.1 Per DFARS 252.204-7023, Reporting Requirements for Contracted Services, the Contractor shall report ALL Contractor labor hours (including subContractor labor hours) required for performance of services provided and total dollar amount invoiced under this contract for services at Holloman Air Force Base, NM via a secure data collection site. The Contractor is required to completely fill in all required data fields at https://sam.gov.

1.5.2 Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the SAM.gov help desk.

1.5.3 *Reporting Period: Contractors are required to input data by 31 October of each year.

2.0 SERVICE SUMMARY

SS-1

Contractor trains and maintains qualified personnel IAW CCT. Contractor effectively trains and certifies its SMOs, STPs, and IMDs

SS-2

Contractor meets all security requirements. Contractor ensures all employees adhere to the security requirements identified in this PWS.

1.1.3 4.0 100%

SS-3

Contractor meets all safety requirements. Contractor maintains a safe working environment IAW this PWS.

SS-4

Contractor publishes and maintains LOXs for each qualified SMO, STP, and IMD

SS-5

SMOs maintain an immediate presence IAW the SEAL and provide sufficient real time training event mission support.

1.2.2.2 1.2.2.3 No more than 2 validated complaints a month on SMO performance of duties.

SS-6

STP maintains current publications IAW with MPI loaded into the ATDs.

No more than 10% discrepancies of other publications.

SS-7

IMD successfully observes and reports required events at least once per week.

SS-8

Contractor provides MSS with zero STP/IMD overschedules without COR approval.

SS-9

Monthly Activity Report

3.0 GOVERNMENT SERVICES

The government shall provide office space, desks, chairs, and internet services via base Non-Secure Internet Protocol Route (NIPR) services. The government shall also provide applicable computer workstations and computers, printers, copiers, faxes, software, and shredders applicable to normal USAF office operations. The government shall also provide, as necessary, applicable classified storage facilities. Personal and unrelated use of government supplied equipment listed herein is prohibited. All property and equipment provided to the Contractor for the purpose of supporting this contract remain the property of the government and must be maintained within serviceable standards until termination of the contract (barring normal wear and tear of furniture and computers and accepting the expenditure of normal office supplies such as paper, pens, ink, toner, etc.). One workstation per four SMOs shall be provided by the government under this contract. One workstation per remaining contract employee shall be provided by the government under this contract.

4.0 GENERAL INFORMATION

4.1 SECURITY REQUIREMENTS

4.1.1 Visitor Group Security Agreement. The Contractor shall enter into a long term visitor group security agreement if contract performance is on base for 90 days or more. This agreement shall outline how the Contractor integrates security requirements for contract operations with the Air Force to ensure effective and economical operation on the installation. The agreement should address:

4.1.1.1 Security support provided by the Air Force to the Contractor to include storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badging, base visitor control, investigation of security incidents, base traffic regulations, the use of security forms, and conducting inspections required by Department of Defense (DOD) 5220.22 Volume (V)2 AFI 16-1406 V2, National Industrial Security Program: Industrial Security Procedures for Government Activities.

4.1.1.2 Security support requiring joint Air Force and Contractor coordination includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks, and internal security controls for protection of classified material and high value pilferable property.

4.1.1.3 On base, the long term visitor group visitor group security agreement may take the place of a Standard Practice Procedures (SPP).

4.1.2 Clearance Requirements. The Contractor shall possess a Facility Clearance at the classification level of SECRET at the time of the proposal due date. The Contractor shall apply for appropriate personnel security clearances within 5 days after award of the contract. Contractor employees must have a SECRET clearance at a minimum for the positions which require such clearance. The Government shall conduct and assume all costs for the background investigations for the required clearances. Due to costs involved with security investigations, requests for Contractor security clearances shall be kept to an absolute minimum necessary to perform contract requirements.

4.1.3 Notification. The Contractor shall notify the 49th Wing Information Protection Office (49 WG/IP), 681 Second Street, Building 222, Suite 100, Holloman AFB, NM 88330-8277, 30 days before on base performance of the contract. The notification shall include:

4.1.3.1 Name, address, and telephone number of company representatives.

4.1.3.2 The contract number and contracting agency.

4.1.3.3 The highest level of classified information which Contractor employees require access to.

4.1.3.4 The location(s) of contract performance.

4.1.3.5 The date contract performance begins.

4.1.4 Listing of Employees. The Contractor shall maintain a current listing of employees that require access to Holloman AFB. The list shall include the employee's name, social security number and level of security clearance. The Contractor’s home office shall submit a visit request annually for assigned on-base employees to the sponsoring activity unit security manager and 49 WG/IP utilizing the Joint Personnel Adjudication System (JPAS). An updated listing shall be submitted when an employee’s status or information changes (e.g., terminated for cause, retirement, etc.) or a new employee is added. The Contractor’s home office shall submit a visit authorization letter (VAL) on company letterhead annually for assigned on-base employees to the sponsoring activity unit security manager and 49 WG/IP if JPAS is unavailable or when an employee is not reflected in JPAS. The VAL shall be validated and signed by the Facility Security Officer. An updated VAL shall be provided when an employee's status or information changes or when a new employee is added.

4.1.5…