AEMI Draft PWS.pdf

Draft Performance Work Statement for

AFSOC Enhanced Mission Integration

(AEMI)

in support of

United States Air Force Special Operations Command

(USAFSOC)

19 November 2024

Table of Contents

1. Introduction

2. Description of Services

3. Service Summary

4. Government Furnished Property/Equipment

5. General Information Appendix A: Acronym List

1. Introduction

1.1. Background. A worldwide mission set, coupled with diverse support requirements lead to a wide variety of mission activities at eight (8) permanent locations as well as temporary locations throughout the world. AEMI provides support to AFSOC Special Operations Advanced Capability Squadron (SOACS), AFSOC operations centers, and secondary support to all other AFSOC Special Operations Wings (SOW), Special Operations Groups (SOG) and Special Operations Squadrons (SOS).

AFSOC’s core missions include Agile Combat Support, Aviation Foreign Internal Defense, Command and Control, Information Operations, Intelligence Surveillance Reconnaissance (ISR), Precision Strike, Specialized Air Mobility, and Special Warfare. Air Force Doctrine: Please refer to Annex 3-05 Special Operations for a detailed description.

AFSOC forces are distinct from conventional forces and are composed of special operations aviation units, special warfare ground teams, dedicated ISR units, aviation foreign internal defense units, and support capabilities. AFSOC requires unique training, education, development, acquisition, and employment of weapons and equipment not standard for conventional forces. Additionally, AFSOC routinely operates closely with other Government agencies, intragovernmental organizations, non- Governmental organizations, and other nations’ forces. AEMI provides specialized mission systems and services to support special operations throughout the range of military operations around the globe.

1.2. Transition.

There will be a two-month transition period during which the contractor is permitted to perform and invoice only for transition-related activities. Following this period, full responsibility for the AEMI requirement will be assumed by the incumbent. The contractor shall ensure the effective, efficient transfer of responsibility as well as technical data, tools, test equipment, and repair and spare parts.

Support is required throughout the phase-in and phase-out periods to minimize interruptions or delays to the AEMI mission.

1.3. Initial Business Meeting.

Within ten (10) workdays following the contract award, AFSOC will host a meeting with the contractor and the Contracting Officer to review goals and objectives of the contract, and to discuss technical requirements.

1..4. Phase-In.

The contractor shall develop a 'Transition-In Plan' to ensure a smooth transition from the incumbent contractor, who is operating under a previous contract/Performance of Work Statement (PWS), to the incoming contractor, who will assume full responsibility for the task order's scope of work at the start of the Period of Performance (PoP). This 'Transition-In Plan' is due five (5) working days after the contract award to facilitate discussions at the Initial Business Meeting.

The incoming contractor shall be responsible for accomplishing necessary administrative and logistical tasks necessary for the contractor to be fully functional in accordance with this task order, effective the start of the period of performance. Tasks that the incoming contractor shall need to accomplish during the “Transition In” time-period include, but are not limited to the following:

a) Conduct transition meetings with the Client and the outgoing contractor.

b) Provide training to incoming personnel on the AFSOC security aspects of the AEMI mission.

GUENTHARDT, LOGAN 1st Lt USAF AFMC AFICA/765 ESF Remove second 'The'�

c) Provide training on the unique Information Technologies supporting the AFSOC mission.

d) Take actions necessary to employ all required personnel with appropriate security clearances in time to be fully functional per the task order.

e) Prepare/credential/indoctrinate personnel through security and provide network access.

f) Provide training on the various AFSOC program processes.

g) Take actions necessary to employ all required personnel with appropriate security clearances in time to be fully functional by the start of the Base Year Performance Start Date.

h) Take necessary actions to obtain/produce Common Access Cards (CACs) and other documentation necessary to meet contractual requirements.

i) Conduct an inventory of Information Technology (IT) equipment, materials and tools, including software licenses, with the client and the outgoing contractor.

j) Remove any legacy, not in use, IT equipment from its fielded location and return into Hurlburt

Field for disposition within 120 days of contract award.

k) Assess equipment and Preventative Maintenance Inspection requirements (PMI).

During this transition period the outgoing contractor shall remain fully responsible for the work required by the contract that was awarded to that company.

1.5. Phase-Out.

The Contractor shall provide a Transition-Out Plan no later than ninety (90) calendar days prior to the expiration of the contract. This plan shall outline the contractor's approach to ensuring a seamless transition of responsibilities to the incoming contractor and/or Government personnel.

The Transition-Out Plan shall include the following elements:

• Coordination with the incoming contractor and/or Government personnel to transfer knowledge regarding:

o Project management processes o Points of contact o Location of technical and project management documentation o Status of ongoing technical initiatives

• Transition of key personnel

• Identification of schedules and milestones

• Identification of actions required of the Government

• Establishment and maintenance of effective communication with the incoming contractor/Government personnel through weekly status meetings during the transition period.

The contractor shall also ensure that all outstanding work requests, equipment, and Government-owned parts are transferred to the Contracting Officer's Representative (COR) during the phase-out period of the contract.

Additionally, the contractor shall prepare and deliver a 100% accurate update of all inventory assets, including location information (building/room numbers, etc.), to the COR at least ten (10) business days before the end of the contract.

Tasks that the out-going Contractor shall need to accomplish during the “Transition Out” time-period include, but are not limited to the following:

• Finalizing deliverables

• Preparing/conducting transition briefings

• Completing cyber security scans/documentation

• Conduct security out briefings/programmatic de-briefings

• Conduct network out processing

• Update briefings, documentation, & technical data for IT systems and networks

During this transition period the outgoing contractor shall remain fully responsible for the work required by the task order that was awarded to that company. The outgoing Contractor shall Not Separately Price (NSP) the client/Government for any Phase-Out requirements.

NOTE: If the incumbent contractor is awarded this new task order, there is no need for a transition between companies. The contractor shall not need to have any significant transition time and will remain responsible for performing the requirements in the applicable contract for the performance periods stated in the respective contract. However, the contractor shall be responsible for the development of a Transition-Out Plan NLT ninety (90) calendar days prior to expiration of the contract in performance.

2. Description of Services

2.1. General Description.

The contractor shall provide reliable O&M of AFSOC’s specialized integrated mission systems. Ensure continuity of operations, system expertise and maintenance capabilities in routine and in-extremis world-wide operations at deployed locations. Provide the ability to support special projects: The development of capabilities in response to operational requirements as identified by the Client including enhancements & upgrades to existing capabilities, development of new capabilities. Provide support for IT projects for AFSOC. Support AFSOC in the identification of capability shortfalls. Support AFSOC in the identification of new concepts and IT solutions to support AFSOC Missions. This support shall include IT analytical and technological analysis support, assistance with operational development, integration, installation, testing, and Risk Management Framework (RMF) of IT and computer-based systems. Provide program management and unit support to the client.

The AEMI requirement includes systems engineering support for development, prototyping, sustainment, test and evaluation, and technology transition of C2 Mission Systems, sensors and networks associated with meeting the mission requirements stated herein. Major planned AEMI Initiatives include:

1) Airborne Broadband Beyond Line of Sight (AB2)

2) Operational Development, Test & Evaluation, and integration support

3) Operations Center (OC) Support

4) SAMS-FOS

5) Cybersecurity

6) Electronic Flight Bags (EFBs)

2.2. Period of Performance.

This task order will have a nine (9) month base year period of performance with four (4) 1-year options.

There will be a two (2) month Transition Period, ending on 31 July 2026. The four (4) 1-year option periods, if exercised by the Government, shall begin on 1 May 2027 and end four years thereafter for a maximum basic period of performance of four years and nine months. There will be a six (6) month extension exercised if needed.

Table 1: Period of Performance

Period of Performance Start End 2 Month Transition 1 Jun 2026 31 Jul 2026 Base Year 1 Aug 2026 30 Apr 2027 Option Year One 1 May 2027 30 Apr 2028 Option Year Two 1 May 2028 30 Apr 2029 Option Year Three 1 May 2029 30 Apr 2030 Option Year Four 1 May 2030 30 Apr 2031 Six-Month Extension 1 May 2031 31 Oct

2.3. Place of Performance:

The following are CONUS and OCONUS permanent and known temporary locations. Performance at geographically separated locations is allowable with pre-coordination and acceptance by the Contracting Officer.

Permanent:

1) Hurlburt Field, FL (multiple) – Primary Location

2) Cannon AFB, NM (AFSOC/OL-D)

3) Kadena AFB, Japan (AFSOC/OL-A)

4) RAF Mildenhall, United Kingdom (AFSOC/OL-B)

5) Yokota AB, Japan

6) Harrisburg ANGB, PA

7) Davis – Monthan AFB, AZ (AFSOC/OL-E)

8) Kirtland AFB, NM

NOTE: Contractors may be directed to travel to those and other unknown/classified locations to provide temporary services during exercises and contingency operations.

2.4. Mission Systems O&M

The contractor shall provide on-site support at AFSOC permanent operating locations identified in Section 2.3 to ensure they are fully operational and maintained. A listing of AEMI products and services, locations, and units to be supported will be provided in a Work Breakdown Structure (WBS).

In general, provide database, server, network, radio, and client administration, operations, maintenance, and engineering support in accordance with governing publications. Support will also include interfacing and coordinating with spectrum management agencies and POCs with respect to Area of Responsibility (AOR) and theater frequency requirements. These functions apply to all designated locations as needed. The contractor shall perform services during normal business hours as defined in Section 5.1 and on call (30-minute response) during weekends and holidays at all AFSOC Operating Locations (OL). The contractor shall provide services 24 hours a day, 7 days a week, when required by the Government. The contractor shall provide support outside normal business hours and travel as required to support contingency and crisis operations.

2.4.1. Global AFSOC AEMI Reach-Back Support (Help Desk).

The contractor shall provide reach-back support from Hurlburt Field, FL for forces at other in-garrison and deployed sites across the world, including support for all systems operated by AFSOC SOACS and used by OCONUS and CONUS-based AFSOC units. This support shall include the operation of the Mission Systems Support Center (MSSC) and its associated hotline, which serves as a global Service Desk for C2 Mission Systems issues for all AFSOC units. The contractor shall provide Tier 1, 2, and 3 support for all Mission Systems, including account administration, data tracking and analysis, advanced troubleshooting, touch maintenance, and end-to-end troubleshooting. The contractor shall log, track, and coordinate Mission Systems issues raised by AFSOC personnel and units, ensuring timely resolution.

Support activities shall include solving issues on the phone, via remote computer access, and on-site if applicable, and contacting internal or external agencies and on-call experts as needed. The contractor shall also provide operations and maintenance of Mission Systems OL services in support of AFSOC units at sites without dedicated Mission Systems support, with services available up to 24 hours a day, 7 days a week at Hurlburt, FL (AFSOC/SOACS).

2.4.2. Core Services and Infrastructure.

The contractor shall provide for all aspects of O&M, including Core Services and Infrastructure as identified in the WBS. The vendor shall administer, maintain, monitor, protect, and report on all network hardware, systems and clients. The provider must apply industry standard network administration, systems administration, and client administration services. The contractor shall ensure Core Services and Infrastructure systems comply or mitigate risks with Security Technical Implementation Guidelines (STIGs), other Government publications, and industry best practices and manage and forecast system lifecycle to include tech refresh.

Core Services activities include, but are not limited to: managing accounts, user and group maintenance, configurations, file transfers, scripting, service management, patching, updating, directory service management, security sweeps, network scans, vulnerability reports, hardware usage scans, disk status, permissions, database management, resource management, automated monitoring, and continuous reporting. The contractor shall monitor all systems for health and compliance with applicable Department of Air Force Instructions (DAFI) and governing publications and provide Core Services and Infrastructure activity data in a manner auditable by the Government and produce reports in an approved format.

The contractor shall support the evolution of Core Services per AFSOC requirements and integrate other COTS/GOTS products to extend Core Services capabilities per AFSOC requirements. The contractor shall perform analysis, compatibility testing and provide COA recommendations on implementation of incremental upgrades, including expansion of networks and development of new networks and ensure new capabilities securely interfaces between existing networks and applications in accordance with Government regulations and policy.

The vendor shall be familiar with and deliver Core Services and Infrastructure according to an industry standard (such as Information Technology Infrastructure Library). Specific areas of expertise required include, but not are not limited to: Cloud Applications & Infrastructure (e.g. Amazon Web Services, Azure, Google Cloud), Microsoft Windows, Windows Server, Linux (e.g. Red Hat, CENTOS), mobile (e.g. iOS, Android), next generation firewalls and web application firewalls (e.g. ISE, Palo Alto), network hardware (e.g. CISCO, Aruba, Juniper, HP), virtual machines and environments (e.g.

VMWARE, VCENTER, VSPHERE), network monitoring tools (e.g. Splunk, Solarwinds, Wireshark), HBSS tools (e.g. McAfee), and automation tools (e.g. Ansible Tower).

The vendor shall provide dedicated operations and maintenance support for in-garrison AEMI services at Hurlburt Field, and all other permanent locations as needed (para 2.3), which include, but are not limited to:

1) SAMS-C2 Server Suite Services

2) Global SATCOM/KuSS gateway Services

3) EFB

4) SAMS-Mission Enclave Services

5) SAMS-ME Wireless Services

6) SAMS-TGGRS Services

7) AOC WS Services

8) Global Tactical RF/Datalink Services

9) RF Email/Address book Management Services

10) Streaming Media/FMV Services

11) HF Radio Services

12) Device Management System (DMS)

13) Aircraft Status Tracker (AST)

14) Cursor-on-Target (CoT) Router

15) Joint Range Extension (JRE)

AEMI will provide services hosted on SIPRNet, NIPRNet and SAMS-ME enclaves and associated wireless services including those without dedicated AEMI support services.

2.4.3. Cybersecurity Services.

The provider shall ensure all AEMI systems and solutions are approved and secure for operation on Air Force, USSOCOM, and other networks across the globe. The contractor will be required to:

Prepare, submit, and coordinate DoD RMF products and follow SOCOM and Air Force portfolio processes. This includes ensuring all RMF Assessment and Authorization (A&A), and cyber security activities for all AFSOC AEMI occur in accordance with applicable governing publications. Support the Government in coordinating and completing any required RMF A&A actions in conjunction with other contracts, and routinely administer and execute the monthly AEMI update and vulnerability management program. Register in SNAP and implement STIGs, audits, annual Federal Information Security Modernization Act (FISMA) requirements, Cyber Security Service Provider (CSSP), Privacy Impact Assessment (PIA)s, and System of Records Notice (SORNs) as appropriate. Perform systems security analysis to assess vulnerability using gov procedures and software to develop and distribute monthly and in-extremis AEMI updates and patches as directed by the Government. Provide these services at Hurlburt Field, FL (AFSOC SOACS) during routine business hours. Provide support outside these hours and at other locations to support operations when required by the Government.

2.4.4. Client Services.

The vendor will be required to provide client systems technicians (CSTs) support for all networks as directed for AFSOC SOACS and the AFSOC Headquarters (HQ) Operations Center (OC). CSTs may be required to support COOP/HUREVAC relocations and operate at alternate locations.

2.4.5. Operations Center.

The contractor shall: Provide for all aspects of O&M for AFSOC OC products and services as identified in, but not limited to, the WBS. Support the AFSOC OC Weapons System to include Tier 1, Tier 2, and Tier 3 support to the AFSOC OC.

2.4.6. EFB Services for Mobile Device Management/ Mobile Content Management (MDM/MCM) Hosted Outside of a AEMI Managed Environment

When EFB MDM/MCM is provided outside of an AEMI-managed environment, in a cloud/software as a service construct, the contractor will be provided with a full suite of MDM/MCM services from an external service provider. These services will include, but are not limited to:

• A functioning and compliant cloud environment

• Patched and compliant compute and storage services supporting MDM and MCM (e.g., Workspace One, CHub, GIANT Reports)

• Associated cloud environment ports, protocols, and services

These services are essential to an overall functioning EFB program.

Additionally, ensure that mobile systems adhere to relevant STIGs and other government publications, as applicable, based on the level of Tier 2 administrator permissions/privileges granted by the AFSOC/SOACS local policy.

The contractor is expected to provide both Tier 1 and Tier 2 support as defined by the AFSOC/SOACS local policy.

Tier 1 support for the EFB is defined as:

1) AFSOC EFB users will contact the AFSOC SOACS MSSC for Tier 1 user account, device specific, or other applicable using organization issues. These items will be worked at the local level. Higher level tier requirements will be registered and tracked per AFSOC/SOACS local guidance.

2) The MSSC is expected to elevate service request tickets in accordance with AFSOC/SOACS local guidance.

Tier 2 support for the EFB is defined as:

1) AFSOC EFB Account management

2) AFSOC EFB Application management

3) SOACS MDM profile management

4) SAMS-ME WiFi Services

5) iPad Inventory Distribution (Unit Level)

Specific Contractor Requirements:

1) Possess in-depth knowledge of all Mobile Device Management (MDM) technologies, with a specific focus on VMWare Workspace One (formerly AirWatch) software, and its integration with Apple's Volume Purchase Plan (VPP) technology.

2) Possess the ability to configure and manage a wide range of mobile devices, including but not limited to smartphones, tablets, and other mobile platforms, to support the unique requirements of Air Force Special Operations Command (AFSOC).

3) Evaluate and assess Commercial Off-the-Shelf (COTS) and Government Off-the-Shelf (GOTS) applications for implementation, identifying potential issues, concerns, and security vulnerabilities. Manage the secure distribution and deployment of approved applications to mobile devices, ensuring compliance with relevant security standards and regulations.

4) Perform thorough testing of new Operating System (OS) builds on various hardware and software configurations to ensure compatibility and smooth functionality, with a focus on identifying potential issues or conflicts prior to deployment in the AFSOC environment.

5) Perform configuration management of AFSOC EFB mobile devices and software.

6) Identify non-compliance with mobile system policies and perform enforcement/corrective actions, as required.

7) Provide for all aspects of O&M of the AFSOC EFB device build.

2.4.7. Airborne Broadband Beyond Line-of-Sight (AB2).

The contractor shall provide comprehensive Operations and Maintenance (O&M) support for all Airborne Broadband Beyond Line-of-Sight (BBLOS) systems, including but not limited to those identified in the Work Breakdown Structure (WBS). This shall include:

• Providing Tier 1 support for Global Satellite Communications (SATCOM) services, including Ka/Ku-Band Spread Spectrum (KuSS) gateway services, Mobile User Objective System (MUOS) Services, and Low Orbit Points of Presence (LEO PoP)

• Configuring, testing, sustaining, fielding, and upgrading BBLOS systems as required

• Providing Tier 2 and Tier 3 support for all AFSOC aircraft platforms

• Delivering streaming media and Full Motion Video (FMV) services as identified in the WBS

The contractor shall augment Government resources as needed to ensure seamless O&M support for these critical systems.

2.4.7.1. Manned Asset Network Engineering Tier 3 Support.

Provide Air Force Special Operations Command (AFSOC) with Airborne Beyond Line-of-Sight (AB2) Tier 3 support for all aircraft and airborne intelligence, surveillance, and reconnaissance (AISR) platforms, with a focus on Network Engineering subject matter expertise at HQ AFSOC, Hurlburt Field, FL. This support encompasses a range of systems and assets, including but not limited to:

• SATCOM-capable aircraft and platforms

• Ground-based gateways, such as:

o USSOCOM Regional Ground Entry Points (RGEPs) o DISA's AISR Satellite Gateways

• Associated transport infrastructure services, including:

o Satellite communications o Terrestrial networks

• Program Management Office (PMO) and System Program Office (SPO) support

• DoD sensor data distribution systems, solutions, and interfaces

The contractor shall provide expert-level support to ensure the seamless integration and operation of these critical systems, leveraging in-depth knowledge of network engineering principles and practices.

The manned asset network engineering support will be home-based at Hurlburt Field, FL, and support enterprise baseline and capability development with the ability to deploy both CONUS and OCONUS on an as required basis—specifically, to USSOCOM’s RGEPs at Pope AAF, NC; Ramstein AB, Germany; Kadena AB, Japan; Camp Lemonnier, Djibouti; Al Udeid AB, Qatar; and Sigonella, Sicily, (Italy); at a minimum. The Network Engineer(s) may also be required to deploy to conduct inspections, assessments, and to provide system level engineering assistance visits. There are five (5) primary areas of support required:

1) Identify and recommend courses of actions to rectify and/or improve existing operational performance degradation, system level vulnerabilities/deficiencies, and system level inefficiencies.

2) Assist AFSOC in establishing, documenting, integrating, and maintaining recommended system level best practices, enhancements, and enterprise baselines.

3) Provide AFSOC program management, project management.

4) Develop/maintain training material and provide Government personnel with training and assistance on new and existing technologies.

5) Ensure all enterprise baseline configuration management and architectural documentation and drawings are accurately updated as required.

Extended hours for troubleshooting, testing, implementation, and assessment may be supported as required by operations.

2.4.7.2. AB2 Sustainment for CV-22 aircraft.

Provide day-to-day maintenance and troubleshooting of CV-22 AB2 equipment at RAF Mildenhall.

Support will consist of the following:

1) Perform repair/replace maintenance for up to, but not exceeding, 4 CV-22 KuSS kits for in-garrison training, exercises as required, and deployed operations until all kits attrit due to irreplaceable core component failures or are replaced by a new permanent technical solution.

Maintenance is limited to:

a. Remove/reinstall B-Kit, as needed.

b. Troubleshoot and replace Line Replaceable Units (LRU) when they fail. LRUs will not be repaired. A and B kit cables and antennas can be repaired, if possible.

2) Submit SARs directly to USSOCOM SATOPs.

3) Coordinate with each Aircraft Maintenance Unit scheduler for weekly schedules.

4) Coordinate with the equipment owner to facilitate turn-in/disposition of non-functioning equipment, as appropriate.

5) Load configurations and support training of the operational end users by demonstrating proper setup, configuration, basic troubleshooting, and operation of the BLOS system, as required.

6) Deploy with a War Readiness Spares Kit (WRSK). The spares kit will be made up of needed parts (currently existing only) to maintain the system while deployed or on a contingency/crisis operation only.

2.4.8. Specialized Automated Mission Suite (SAMS)-Family of Systems (FoS).

Provide Tier 1, 2, and 3 support as identified in the WBS for all SAMS-FoS, C2, Enhanced Situational Awareness (ESA), Tactical Ground Gateway Receiver Suite (TGGRS), and Mission Enclave (ME) (covered in para 2.5). Provide support for all SAMS-FoS equipped aircraft, carry on kits, and aircrew trainers and simulators. Provide support for all SAMS-FoS Airborne Mission Networking (AbMN) systems including troubleshooting, repairs, installation, and removal of equipment/wiring. Document performed work on aircraft and simulator maintenance forms in Integrated Maintenance Data System

(IMDS).

2.4.8.1. SAMS-ESA.

Provide Tier 1, 2, and 3 support for SAMS-ESA fielded systems, which includes operational development, test, integration, sustainment, upgrading, and fielding of SAMS-ESA builds as identified in, but not limited to the WBS. Comply with cyber security requirements and support internal and external (i.e. System Program Office (SPO) hosted) Configuration Control Boards (CCBs). Support operational development and testing and to include determining how systems can work together, engineering hardware and software solutions, analyzing systems and requirements, experimenting, and testing solutions, and developing integration and interoperability courses of action. Additionally, perform engineering analysis of mission systems, mission network employment, and tactical datalinks on AFSOC platforms. Activities include analyzing aircraft existing mission systems architecture and development and documentation of technical solutions and courses of action for employment of mission systems and mission network employment. Develop and maintain schematics. Implement a process to solicit and disposition feedback from the customer through crew working groups and deficiency reports.

Maintain SAMS-ESA support systems which include, but not limited to, Tactical Datalinks (TDL) Line-of-Sight/Beyond Line-of-Sight (LoS/BLOS), AbMN, FMV, MIL-STD 1553, Global Positioning System (GPS), client and aircrew monitors. Maintain all SAMS-ESA trainers and simulators at all permanent sites. Provide Tier 3 and lab equipment support for the HC-130J SAMS-ESA Client as required in support of Air Combat Command (ACC) SAMS-ESA personnel working in the SAMS-ESA lab.

Provide as needed, but not limited to, all Product Engineering, Integration & Testing support, Certification & Accreditation artifacts, baseline SAMS-ESA client software image, and support execution of Assured Compliance Assessment Solution (ACAS) scanning. The contractor may be required to provide additional supporting documentation for ACC’s configuration control board.

2.4.8.1.1 Link-16.

Provide Tier 1, 2 and 3 support for AFSOC Link-16 systems integrated with SAMS-FoS, as identified in, but not limited to, the WBS. Provide O&M support services to AFSOC Link-16 radios, software, clients, and infrastructure. Maintain an appropriate technical refresh cycle, comply with DoD and Air Force mandates, and communicate with the appropriate Government lead for funding procurement.

2.4.8.2. SAMS-TGGRS.

Provide Tier 1, 2 and 3 support for SAMS-TGGRS fielded systems as identified in, but not limited to, the WBS. Provide troubleshooting, repair, and maintenance of all TGGRS equipment to include clients, network devices, and radio equipment. Manage network diagrams and update changes as completed.

Manage software/hardware integration updates, tech refresh cycles, and notify the appropriate Government lead of required equipment for purchase. Manage Authority to Operate (ATOs) and RMF packages associated to TGGRS.

2.4.8.3. SAMS-C2.

Provide Tiers 1, 2 and 3 support for Specialized Automated Mission Suite-Command Control (SAMS- C2) Client as identified in, but not limited to, the WBS. Provide, but not limited to, all Product Engineering, Integration & Testing, Certification & Accreditation which includes monthly updates and STIG compliance, Readiness & Sustainment activities, and building SAMS-C2 client software images.

Provide Client System Technician (CST) support, as described in an approved Memorandum of Agreement (MOA). Other work required includes Continuity Workbooks, Software Description Documents, CCB briefing slides, support and execution of ACAS scanning. The contractor maybe required to coordinate with outside agencies to build and or troubleshoot SAMS-C2 client software images.

2.4.9. Logistics.

Provide comprehensive logistics support for AEMI products and services fielded by AFSOC SOACS at all permanent places of performance, reach back support for deployed locations and “surge capability” for short notice real world requirements. Manage the AEMI warehouse (located at Hurlburt Field) and associated systems, software, hardware, components to meet asset management and inventory management programs, including, but not limited to, DLA Disposition Services process and Defense Property Accountability System (DPAS). Document completed work and equipment will be cleared for use in compliance with documented US Air Force maintenance processes and practices, to include TO 00-20-1 and DAFI 21-101.

2.4.10. Government Programs & Additional Duty Support.

As required, perform or assist in the performance of additional duties that are not specifically mandated to be performed by Government personnel. Additional duties may include but are not limited to the following: Technical Orders, Facilities, Safety, Security, Consolidated Tool Kits, Vehicles, Equipment Custodian, Test, Measurement, Diagnostic Equipment, Integrated Maintenance Data System monitor, and Electrostatic Discharge Sensitive (ESDS), Emissions Security (EMSEC), Communications Security (COMSEC). Provide support in focus areas as directed by the Government.

2.4.10.1. Security Management Support.

Ensure requirements for safeguarding classified information/classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting Government property, and for the security of automated and non-automated management information systems and data are fulfilled. Immediately notify an appropriate Government official if any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information.

Provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases. The contractor personnel will be authorized to courier classified information up to the SECRET level in performance of official duties upon approval of and designation by the COR.

2.4.10.2. Tool Program.

Ensure all Government procured tools are tracked and maintained in accordance with DoD, Air Force and local regulations. All non-Government tools shall be identified separately from Government resources. Ensure all personnel have been trained on proper tool procedures. Tool procedures training shall be documented for all personnel within 30 days of being assigned to the task order. Contractor personnel shall be briefed on the operational hazards and safe operating procedures for specialty tools such as power tools, soldering irons, and others prior to them being used. Document the training on an Air Force Form 55. Government and contractor spot inspections shall be completed and documented quarterly to ensure proper tool procedures are used. Maintain a tool program continuity binder and make it available upon request for inspection by Government representatives.

2.4.10.3.Electro-Static Discharge (ESD) Program.

Maintain ESD workstations at applicable locations in accordance with all Air Force and local regulations. Ensure all personnel are trained on the proper handling of ESD sensitive components, proper wrist strap procedures, proper grounding of equipment, and the proper ESD cleaning of all ESD workstations. Oversee and ensure annual ESD refresher training is documented and tracked for all applicable personnel. ESD training is required for all contractor personnel prior to working on any Government owned equipment and within 30 days of being assigned to the task order. Government and contractor spot inspections will be completed and documented quarterly to ensure proper ESD procedures are used. An ESD continuity binder will be maintained and available upon request for inspection.

2.4.10.4. Test, Measurement and Diagnostic Equipment (TMDE) Program.

Use and maintain GFE provided TMDE in accordance with all applicable DoD, Air Force, and other applicable Government governing guidance. TMDE shall be certified by the servicing TMDE agency.

All TMDE shall be tracked and certified. Assign, document, and train a primary and alternate TMDE monitor for each area that utilizes test equipment that requires calibration. Maintain a TMDE continuity binder and make it available upon request for inspection by the Government.

2.4.10.5. Spectrum Management Program Support.

Coordinate and communicate Radio Frequency (RF) spectrum requirements and assignments at each operating location in accordance with applicable DoD, AIR FORCE, USSOCOM, and local governing publications. Provide a communications spectrum plan in traditional AIR FORCE and Special Operations communications matrix formats. The communications matrix will be published and distributed monthly or upon change, whichever is sooner, to all affected operating and support units as it relates to AEMI services.

2.4.10.6. Lock-Out/Tag-Out (LOTO) Program.

Establish a LOTO program for all applicable sites in accordance with DoD, AIR FORCE, USSOCOM, and local guidance. Document procedures and provide them to Government representatives upon request.

2.4.10.7. Technical Order Distribution Office (TODO) Program.

Ensure a unit TODO program is established and maintained for all assigned supported units. Ensure TODO is established per DoD, Air Force, USSCOM, or local guidance. A Government-approved system of record, such as the Enhanced Technical Information Management System (ETIMS) or an equivalent Government-approved system, will be used to centrally manage all Technical Orders. Ensure Technical Orders are current and up to date at all times. Prepare a TODO continuity binder and make it available upon request by the Government. Conduct training on such procedures, and applicable governing publication guidance within 30 days of being assigned. Government and contractor spot inspections will occur quarterly to ensure compliance.

Work Order Residue Program.

Ensure each applicable operating location has a centralized storage location for all Government procured work order residue items. Items sensitive to static discharge will be stored properly in ESD bags and labeled according to DoD, Air Force, USSOCOM, and local regulations. Establish a work order residue equipment inventory for all equipment and updated any time equipment is added or deleted from the inventory list. Inventories will be centralized and available for inspection by the Government upon request. A 100% accuracy is expected to properly fund and purchase supply items. DD Form 1574, 1577-2 and 1577 will be utilized extensively and attached to all equipment to identify its operational status: Serviceable, Unserviceable/Repairable and Unserviceable Assigned. Government and contractor spot inspections will occur quarterly to ensure compliance.

2.4.10.8. Maintenance Data Collection (MDC) and Preventive Maintenance Inspection (PMI) Programs within IMDS.

Ensure all Government-owned equipment is loaded and maintained in IMDS or a Government-approved system of record. Equipment PMIs will be loaded against all equipment in accordance with applicable Technical Orders or commercial-off-the-shelf manuals. In the absence of specific equipment PMI guidance, establish PMI requirements and inspection cards for COR approval. Once approved, ensure the PMIs are loaded against the applicable equipment. An IMDS continuity binder will be maintained by the contractor for this program and available upon request for inspection. The contractor is responsible for ensuring all required personnel acquire access to IMDS and are trained on its operational use. IMDS procedures will be briefed by the contractor to all personnel within 30 days of assignment to associated task order duties. Ensure all personnel are trained and familiar with proper maintenance practices in accordance with industry and Government standards.

Provide dedicated resources within the contractor team to track all equipment PMIs and publish them in an approved maintenance and communications support plan sent out monthly while assisting in the capture and information management of this critical information, essential to reporting requirements outlined by the Government.

2.4.10.9. Emissions Security (EMSEC).

Support and comply with Wing EMSEC programs, at all applicable operating locations.

2.4.10.10. Communications Security (COMSEC).

Designate primary and alternate communications security officers at each applicable operating location to support associated AEMI. Perform all associated COMSEC duties to ensure all AEMI radios and cryptographic equipment (e.g. KGs) can run and be supported by the task order team in classified encrypted modes. The COMSEC programs will be run in accordance with applicable DoD, Air Force, USSOCOM, local, and other governing publications.

2.4.10.11. Custodian Authorization/Custody Receipt Listing (CA/CRL).

Designate primary and alternate CA/CRL equipment custodians. Perform all associated CA/CRL duties to ensure all AEMI can be operated and supported effectively. The CA/CRL programs will be run in accordance with applicable DoD, Air Force, USSOCOM, local, and other governing publications.

2.4.10.12. Information Technology Asset Management (ITAM).

Designate primary and alternate Information Technology Equipment Custodians (ITEC) at each operating location to support associated AEMI systems. Perform and manage all associated ITAM responsibilities. The ITAM program will be run in accordance with applicable DoD, Air Force, USSOCOM, local, and other governing publications.

2.4.11. Contract Management.

Provide contract planning and management support, ensuring that all contractual obligations are met.

This includes providing project management support for the development of plans, milestones, budgets, schedules, and program reviews as required.

The contractor shall be responsible for:

• Origination, finalization, and distribution of monthly status reports, Contract Funds Status Report (CFSR), test reports, meeting minutes, and action items

• Providing financial support, including planning, projecting, tracking, maintaining, and reporting of the financial status of projects

• Ensuring compliance with all contractual requirements and obligations

• Verifying that all deliverable products meet the requirements outlined in the contract

• Managing contractor performance and ensuring that all personnel meet education, experience, and security requirements

• Taking corrective action as necessary to ensure contractor compliance and satisfactory performance

2.4.12. Project Management.

The AEMI Work Breakdown Structure will serve as an authoritative source document for AEMI capabilities. Utilize the WBS as an integral part of the project management process and in accordance with industry best practices. New capabilities, modifications, and updates to O&M capabilities identified in the WBS shall be done through the CCB process. New operational development & engineering projects will be added to the WBS upon project completion.

2.4.13. Capability Lifecycle Management.

Assist Client in defining Systems Architectures and Technology Roadmaps that align with AFSOC strategic vision and ensures AFSOC AEMI efforts are coherent with command initiatives. Ensure project efforts conform to the DoD acquisition process to the extent practicable to maximize long-term Return On Investment (ROI) through repeatable delivery of AEMI capabilities to in-garrison, airborne, ground-based, and mobility environments. This includes but is not limited to the development/refinement of early documentation such as Initial Capabilities Document/Capabilities Development Document/Capability Production Document (ICD/CDD/CPD)s, Concept of Operations/Concept of Employment (CONOP)s/CONEMPs, & Doctrine, Organization, Training, material, Leadership, Personnel, Facilities, Policy (DOTmLPF+P) analyses through explicit consideration and documentation of fielding and transition issues (e.g. sustainability, supportability, maintainability, interoperability, etc.).

2.4.13.1.Systems Engineering.

Ensure systems engineering principles are applied to operational development, engineering, and integration efforts (Section 2.8), generally as identified in EIA-632 Processes for Engineering a System (or similar standard) and specifically as it pertains to execution. Employ the technical management processes of requirements management, configuration management, and data management at a minimum. Conduct proper integration activities when designated the responsibility. All projects shall be properly documented and in accordance with a standard approved by the Client. This includes the development of Department of Defense Architecture Framework (DoDAF) artifacts.

2.4.13.2. Configuration Management.

Ensure all AEMI capabilities follow proper CM practices according to industry standards (e.g. EIA 649). This includes tracking of hardware in use, software in use, licensing, respective passwords and accounts, and any technical documentation for AEMI capabilities. Project documentation shall be stored in the CM repository. Coordinate configuration boards, document and publish approved configurations, and coordinate changes with global AFSOC, other support agencies, and agencies of interest.

2.4.14. Platform and Software Engineering Support.

Provide for all aspects of O&M for Software and Platform Engineering as identified in the WBS. Must be well versed in and apply industry standard software development and systems engineering processes, with emphasis on requirements management and refinement. Specific areas of expertise required include but are not limited to Cloud Applications & Infrastructure (e.g. Amazon Web Services), Windows, Linux (e.g. Red Hat), mobile (e.g. iOS, Android), aircraft integration, airworthiness, and datalinks (e.g.

Link-16, SADL, Integrated Broadcast Service (IBS), Harris SA, PDA-184, FMV, VMF, MANET). Act as Subject Matter Expert (SME)s supporting AFSOC/SOCOM technical working groups.

Apply knowledge of AFSOC platforms to perform technical assessments. Perform analysis of hardware/software solutions, conduct market research and technical evaluations, support vendor demonstrations, develop Application Programming Interface (API)s to interface with systems and perform integration activities with Commercial Off the Shelf/Government Off the Shelf (COTS/GOTS).

The contractor shall plan, interface, collaborate, coordinate with other program offices, Government, and commercial entities on engineering projects as required. Proper configuration management for platform engineering hardware/software is required. Management and forecasting of system lifecycle to include technical refresh and obsolescence is required. The contractor shall practice rigorous requirements management, project management, change control management and testing during software development efforts to ensure:

1) Deployment of high-quality code that meets the requirements

2) Successful releases without introduction of unexpected problems

3) Minimal need for emergency/corrective maintenance

4) Minimal need to fix the same issue multiple times

5) Maximum value out of limited IT budget resources

Generalized requirements for all projects in this task include the following, but are not limited to:

1) Assignment of a project manager (and a technical subject manager expert, when appropriate), who will interface with the assigned Government point of contact for the project.

a. Manage project execution, milestones and provide a method for continuous/real-time status accounting.

b. Develop deliverables according to the AFSOC D&E process and systems engineering principles.

c. Propose and document a method to produce reliable project estimates/completion dates for new projects, appropriately accounting for utilization of resources.

2) Conduct testing of build compatibility on hardware and software as revisions are released.

3) Ensures engineered systems (hardware and software) comply or mitigate risks with STIG and other Government publications (e.g. RMF).

4) Provide for management and forecasting of system lifecycle to include technology refresh.

5) Ensure sufficient and appropriate documentation for all systems produced and maintained.

2.4.14.1. Systems Integration Laboratory (SIL)

Provide scalable engineering services to develop new Mission Systems capabilities, with the ability to expand capacity as needed to support emerging priorities.

The Client may provide additional resources to pursue high-priority projects above the baseline capacity.

All projects will be prioritized by the Client based on operational needs and modernization requirements and may apply to any AFSOC mission set.

The following are the generalized requirements for all projects under this task, although specific requirements may vary:

1) Contractor personnel working in this functional area will be able to engineer and solve time critical problems.

2) Ensure all operating mission nodes (operations centers, airborne weapon systems, ground teams, and other AFSOC) can interoperate and execute synchronized mission activities via their mission systems, connected through various mission networks.

3) Ensure systems are interoperable and networked within and external to AFSOC, especially between Air Force and SOF systems.

4) Integrate conventional, special operations, and other systems and applications into light, lean, integrated, interoperable, and scalable packages that are used in-garrison and deployed; by providing higher order systems, IT engineering, analysis, and baseline systems development for AFSOC Mission Systems employment.

5) Develop and implement computer and device configurations, builds, and system tests to ensure seamless integration and operation of Mission Systems, while providing in-depth security analysis to identify and mitigate potential vulnerabilities. Additionally, support Mission Systems training initiatives by developing relevant training materials and programs, and develop and maintain Mission Systems standards for Government approval, including establishing standard system architectures and attributes for developed hardware and software solutions, to provide a framework for the development and implementation of Mission Systems that ensures consistency, security, and operational effectiveness.

6) Practice rigorous requirements management, project management, change control management and testing during software development efforts to ensure:

a. Deployment of high-quality code that meets the requirements

b. Successful releases without introduction of unexpected problems

c. Minimal need for emergency/corrective maintenance

d. Minimal need to fix the same issue multiple times

e. Maximum value out of limited IT budget resources

7) Provide services at Hurlburt Field, FL (AFSOC/SOACS) during routine business hours. Support outside these hours and at other locations may be required as identified by the Contracting Officer.

2.4.14.2. Fabrication Lab (Forge).

All projects under this task will be prioritized by the Client based on operational needs…