RFP_Attachment_1_AttachmentL1MPSCIV_PWS_19May22.pdf

MPSC IV PWS

Performance Work Statement for Mission Planning Support Contract IV

(MPSC IV)

Solicitation: FA8217-22-R-0001

Date: 19 May 2022

Table of Contents 1 Description of Services

1.1 Background

1.2 Supported Organizations

1.3 Supported Platforms

1.4 Mission Planning Definitions

1.4.1 Mission Planning Spectrum

1.4.2 Primary Customer

1.4.3 Secondary Customer

1.4.4 Hardware

1.4.5 Software

1.4.6 Mission Planning Environment (MPE)

1.4.7 Non‐Mission Planning Environment (Non‐MPE)

1.4.8 JMPS Open Mission Systems (JOMS) Deployment Environments

2 Requirements

2.1 General Requirements

2.1.1 Mission Planning System Technical Requirements

2.2 Mission Planning End-user Support

2.2.1 Helpdesk Call Capability

2.2.2 Team Support

2.2.3 Real Time Resolution

2.2.4 Trouble Reports

2.3 System Support Representatives (SSRs)

2.3.1 Standard USAF SSR

2.3.2 Assault Zone SSR

2.3.3 Combined Air Operations Center (CAOC) SSR

2.3.4 ACC Test SSR

2.4 Subject Matter Expertise (SME)

2.4.1 Platform SME

2.4.2 Command, Control, Communications, Computers, and Intelligence (C4I) SME

_Toc101877048

2.4.3 Cloud Computing SME

2.5 Configuration Management (CM)

2.5.1 Configuration Management Tasks

2.6 Technical Publications

2.6.1 Technical Publications Tasks

2.7 Hardware Support

2.7.1 Hardware Support Tasks

2.8 Software Security Team (SST)

2.8.1 SST Tasks

2.9 Information Systems Cybersecurity

2.9.1 Information Systems Security Officer (ISSO)

2.9.2 Information Systems Security Managers (ISSMs)

2.9.3 Information Systems Cybersecurity Tasks

2.9.4 MPC Cybersecurity Tasks

2.10 Mission Planning Support for Foreign Military Sales (FMS)

2.10.1 FMS SME Tasks

2.10.2 FMS Technical Publications Tasks

2.10.3 FMS Configuration Management Tasks

2.10.4 FMS Contract Administration Tasks

2.11 Mission Planning Central (MPC) Description

2.11.1 MPC General Tasks

2.11.2 MPC Configuration Management Tasks

2.11.3 MPC Site Administration

2.11.4 MPC System Administration

2.11.5 MPC Change Enhancements

2.12 Personnel Qualifications

2.12.1 Qualifications for SME

2.12.2 Qualifications for SSR support

3 Service Delivery Summary (SDS)

3.1 CDRLs

3.2 Labor Hours Reporting

4 Government Furnished Properties (GFP)

4.1 Initial Inventory

4.2 Annual Inventories

4.3 Close-Out inventory

5 Government Shared Property

5.1 Phase In

5.2 Phase Out

6 Minimum Government Compliance Documents

7 Acronyms

1 Description of Services The Mission Planning Support Contract (MPSC) ensures sustainment infrastructure is established to support all Mission Planning Environments (MPEs) and future JMPS Open Mission Systems (JOMS) deployment environments. Sustainment of MPEs includes configuration management and control, drafting and publishing of technical documentation, system checkout, fielding, supply, maintenance, supplemental training, customer assistance visits, a twenty‐four (24) hour/seven (7) day-a-week helpline, international sustainment and product familiarization, combined test force support, Mission Planning Central (MPC) sustainment and management, deployment and management of System Support Representatives (SSRs) to worldwide locations, transition to follow‐on MPEs, and sustainment support of all wing/unit level mission planning requirements and related efforts.

Worldwide requirements may increase depending on world events and future technological innovations. Additionally, support of non-MPE equipment may also be required.

1.1 Background

An MPE is a compilation of the software, hardware, data, training and logistics required to accomplish mission planning. The unit-level mission/combat planning process includes: receipt of tasking, mission concept development, detailed planning for platform (aircraft, weapon) departure, en-route, ingress, weapon/cargo delivery, egress, recovery, and de- confliction/coordination of assets, and certain post-mission activities. The Mission Planning System Support Facility (MPSSF) provides execution and sustainment for the supported organizations and foreign partners.

1.2 Supported Organizations

Supported organizations include all end users of the MPEs: Air Combat Command (ACC), Air Education and Training Command (AETC), Air Force Global Strike Command (AFGSC), Air Force Material Command (AFMC), Air Force Reserve Command (AFRC), Air Force Space Command (AFSPC), Air Mobility Command (AMC), Air National Guard (ANG), Pacific Air Forces (PACAF), United States Air Forces in Europe-Air Forces Africa (USAFE), and Foreign Military Sales (FMS) for several allied countries. The Joint Mission Planning System (JMPS) also includes Navy and Marine Corps users.

Test agencies are also supported and the primary groups are located at Eglin AFB, FL and Nellis AFB, NV. They include the Lead Developmental Test Organization (LDTO) 45th TS, 47th Cyber Test Squadron, Operational Test organizations to include Det 2 Air Force Operational Test and Evaluation Center (AFOTEC), HQ AMC Test and Evaluation Squadron, ANG & AFRC Test Center (AATC), and the 53rd Wing. Other test organizations may be supported, based on the needs of the specific airframe and its own phase of the lifecycle (e.g. Edwards AFB, Tyndall AFB).

1.3 Supported Platforms

Support is provided for all platforms that utilize the Mission Planning software. This list currently includes A-10, B-1B, B-2, B-52, C-21, C-27, C-5, C-17, C-130, CH-146, CH-147, HH-60G/W (Combat Rescue Helicopter), E-3, E-4, E-8, F-2, F-15, F-16, F-18, F-22, F-35, KC-10, KC-46, KC-135, MC-12, MQ-1, MQ-9, RC-135, RQ-4, T-1, T-6, T-7, T-38, U-2, U-125, UH-1N/TH-1H, and VIP Transport.

Currently, some of these platforms provide their own mission planning support (i.e. F-22 and F-35);

these platforms are listed to allow for support should it be needed at any point during this contract.

Additional platforms may be added at a later date. Support is also provided for Air Force Joint Mission Planning System (JMPS) MPE users who aren’t tied to a specific platform, but use JMPS independently of an aircraft platform.

1.4 Mission Planning Definitions

1.4.1 Mission Planning Spectrum

Activities related to the use of Mission Planning software and/or hardware accomplished throughout the planning, execution, and post‐mission phases of a specific mission, battle, or war.

1.4.2 Primary Customer

The provider of requirements and funding for a particular task order on the Mission Planning Support Contract.

1.4.3 Secondary Customer

The direct recipient of mission planning support, for example the Operations Group, Weapons Tactics, Homeland Defense, etc. Request for additional/changes to support requirements will be coordinated through the primary customer. The secondary customer is responsible for providing an adequate office environment and supplies for the SSR to perform the services to support the mission, and provide the necessary tools (to accomplish the mission services) that are not Mission Planning program office procured items (e.g. PCMCIA cards and card readers, external storage devices, Ethernet cables, power surge protection devices, tables to set-up the mission planning systems work stations, reams of paper, ink & toner cartridges for the printers, telephone, etc.). The tactics office is the typical on-site office where the SSR should be situated when performing the support duties;

although some units may choose another suitable alternative.

1.4.4 Hardware

The physical computers and associated peripherals used throughout the mission planning spectrum, as provided by the primary customer; or MAJCOM approved, third party or unit procured hardware supported as non-MPE hardware.

Mission Planning Systems Hardware – hardware that is specified in Annex A of the Mission Planning Environment Letter issued by the Mission Planning Program Office, currently AFLCMC/HBM.

1.4.5 Software

The computer programs and applications used throughout the mission planning spectrum, as provided by the primary customer; or mission planning related software which has been MAJCOM approved, third party or unit procured; and supported on non-MPE hardware.

Mission Planning Systems Software – software that is specified in Annex B of the Mission Planning Environment Letter issued by the Mission Planning Program Office, AFLCMC/HBM.

Mission Planning Systems Data – Data that is specified in Annex C of the Mission Planning Environment Letter issued by the Mission Planning Program Office, currently AFLCMC/HBM.

1.4.6 Mission Planning Environment (MPE)

A compilation of the software, hardware, data, training and logistics required to accomplish mission planning as identified on the certified MPE letter issued by the Mission Planning Program Office, AFLCMC/HBM.

1.4.7 Non‐Mission Planning Environment (Non‐MPE)

Computer hardware and software, not identified on the certified MPE Letter, which uses mission planning or mission planning related software as approved by the MAJCOM primary customer.

1.4.8 JMPS Open Mission Systems (JOMS) Deployment Environments JOMS represents a paradigm shift in MPS operations. The immediate need will be supporting the Ops portion of Mission Planning’s Dev/Ops process evolving into a Dev/Sec/Ops process. JOMS products are Cloud based application(s) that require the MPSC Contractor to be responsible for operations. Being responsible for operations includes Cloud deployment(s) and Edge server device(s) deployments and may include other deployment options. Software distribution to the Cloud, Edge and desktop/laptop devices will primarily be conducted over networks, not with disks as currently executed for JMPS MPEs. However, disconnected environments will also be supported.

This DevOps environment will include any combination of traditional JMPS, Mobile O/S and JOMS technologies operating on the approved mission planning hardware; JMPS only (blended environment); JMPS hardware/software and JOMS based Cloud infrastructure (Hybrid environment);

or accessing JOMS services through JOMS infrastructure with Edge servers or Edge devices to support the Warfighter. Support will require working closely with the Developer community (Dev) alongside the Information Technology (IT) Operations (Ops) communities to ensure the required IT architecture is maintained securely to enable fully networked JOMS Cloud operations.

2 Requirements

2.1 General Requirements

2.1.1 Mission Planning System Technical Requirements

2.1.1.1 Human Resources

The contractor shall provide the human resources necessary to recruit, hire, train, staff and retain a professional workforce necessary to complete all the requirements/tasks in accordance with this

PWS.

2.1.1.2 Planning and Reporting

The contractor shall provide an Integrated Master Plan (IMP) to describe all of the scheduled functions, duties, responsibilities, and procedures for the requirements/tasks listed in this PWS.

(CDRL: A001/B001) The contractor shall report the completion of the functions, duties, responsibilities, procedures and system availability metrics (including raw data for active MPE/non- MPE inventory at each site) for the requirements/tasks in the Monthly Activity Report (MAR).

Additionally, each MAJCOM may request tailorable items be added to the MAR through the Contracting Officer Representative (COR). (CDRL: A003/B003)

2.1.1.3 Supported Mission Planning Systems (MPS)

All MPSs shall be supported by contractor personnel. This includes UNIX‐Mission Planning System (UNIX‐ MPS) Core and all associated tools; Portable Flight Planning Software (PFPS) and all associated tools; Joint Mission Planning System (JMPS) MPEs to include Framework, common components (CCs) and all associated tools, Unique Planning Components (UPCs); Joint Precision Airdrop System (JPADS) Mission Support Equipment (MSE); JMPS Open Mission System (JOMS), Software and Data Update Service (SADUS) and all associated tools, MAFPS MPE (to include the JMPS FW software that gets loaded with the MAFPS AOC Client and associated JMPS CCs), other follow‐on mission planning systems, and upgraded systems as they become available. The contractor shall possess knowledge and experience capable of providing overall technical support; operational experience; software development, maintenance, supplemental training; logistics support; system administration; configuration control; quality assurance; and management. This knowledge and experience applies to all MPSs.

2.1.1.4 Experience – Required Skill Levels

2.1.1.4.1 Required Computer Skills

All contractor personnel shall, at a minimum, have skills in the latest versions of current software applications (generally available via the standard desktop configuration(s):

FUNCTION SOFTWARE

Operating Environment Windows

Electronic Mail Outlook

Presentation PowerPoint

Spreadsheet Excel

Word Processing Word

2.1.1.4.2 Required Communication Skill Levels

All contractor personnel shall have the skills to communicate professionally with customers and provide continuous interaction with MPS users: written, telephonic, interpersonal and electronic.

2.1.1.5 Security Requirements

All contractor personnel shall obtain current security clearances to the proper level(s) required to control classified information (data, manuals, and software) to include Top Secret, Special Access Required (SAR) clearances and Communications Security (COMSEC), including Not Releasable to Foreign National (NOFORN), as required by the MAJCOM POC. The contractor is responsible for complying with all applicable Department of Defense (DoD), United States Air Force (USAF), and installation security requirements. The following provides detailed justification regarding need to know. Contractor is tasked to provide systems administration and supplemental training on their specialized mission planning systems at their home bases and in their respective facilities. To ensure Mission Planning Systems (MPS) have the best intelligence support possible, as well as to support training for special mission and Intelligence Surveillance Reconnaissance (ISR) mission planning systems, it is important that current intelligence systems have the opportunity to influence future systems. Many intelligence discussions are at the SCI level and meetings are held at SCI facilities.

DOD intelligence agencies and AF/A2 disseminate key intelligence documents and hold video conferences on the Joint Worldwide Intelligence Communications Systems (JWICS). Additionally, systems administration and training for multiple USAF airframes supporting intelligence users and trainers in both ACC/A2 and AMC/A2, which must be conducted in a sensitive compartmented facility (SCIF). These responsibilities require frequent technical and analytical discussions with programs in areas that are both classified and compartmentalized with information on the threat systems, including parametric data and also platform-unique collection data. The incumbents are also responsible to provide the mission planning enterprise with detailed technical information regarding usability of Unique Planning Component (UPC) software modules for all Combat Air Forces (CAF) and Mobility Air Forces (MAF) aircraft and several ISR special mission aircraft as well as integrating mission planning software onto all current and predicted aircraft and weapons in the USAF inventory, as well as the Air Operations Centers (AOCs) and unit level intelligence systems. Access to Top Secret/SCI level may be required. Additionally, specific classified requirements, NATO training, restricted data, formally restricted data, and requirements for working with nuclear systems will be captured in the DD254.

2.1.1.6 Travel Requirements

Contractor personnel shall travel, as necessary, to both Continental United States (CONUS) and Outside Continental United States (OCONUS) locations to provide integrated hardware and software logistical support services to the customers. System Support Representatives (SSRs) and platform Subject Matter Experts (SMEs) travel shall also include attendance at workshops, test sites, training locations, and other symposiums, meetings and conferences as requested by the Government when alternate means such as Secure Video Teleconference (SVTC) or other web based communications are not sufficient to accomplish the travel objective. Only travel directed by the Government is billable against CLIN 0002 (Travel). The contractor shall submit a trip report at the completion of each Government directed travel event. (CDRL: A005/B005).

2.1.1.7 Unique Identification (UID) Policy

The contractor shall provide a DoD unique item identification, UID, or a DoD recognized unique identification equivalent for:

• All delivered items for which the Government’s unit acquisition cost is $5,000 or more;

• Items for which the Government’s unit acquisition cost is less than $5,000, when identified by the requiring activity as serially managed, mission essential, or controlled inventory;

• Items for which the Government’s unit acquisition cost is less than $5,000, when the requiring activity determines that permanent identification is required; and

• Regardless of value – (1) any DoD serially managed subassembly, component, or part embedded within a delivered item; (2) the parent item that contains the embedded subassembly, component, or part; and (3) any warranted special item.

2.2 Mission Planning End-user Support

2.2.1 Helpdesk Call Capability

The contractor shall provide a twenty‐four (24) hour/seven (7) day-a-week helpdesk call capability.

Mission Planning Users (even those in the field) will be able to call a toll-free number any day of the year (including holidays) and any time of the day, or night, and talk to a live person who is capable of addressing their issue(s) with a real-time/immediate response. For SAP related issues, Contractor has a 12 hour window to access correct facility and answer/respond/address pertinent issues.

2.2.2 Team Support

The contractor shall utilize other team members (as needed) to provide the best possible support in the most efficient manner. Mission Planning Users will only need to know one phone number; but the contractor shall have a process to direct issues to team members who can address technical matters and engage to resolve the identified issue(s). The team member(s) who may be engaged in issue resolution efforts may include (but are not limited to): Subject Matter Experts, System Support Representatives, Hardware Support, Mission Planning Central Helpdesk, Foreign Military Sales (FMS) Helpdesk, and other personnel on the Mission Planning Support Contract; but may also include team members who are funded by other contracts (i.e.: Army Helpdesk, Mission Planning Training Team, Unit Consolidated Helpdesks, etc.).

2.2.3 Real Time Resolution

When a timely response to an issue is required, and the “first contact” isn’t able to provide a full resolution to an issue; the contractor shall utilize team members who have the necessary technical knowledge, skills, clearances, permissions, and tools to provide immediate assistance/troubleshooting/research and resolution. In the event the SSR’s unit experiences the loss of a mission planning essential function, the SSR will immediately forward an incident report to the MPSSF who will coordinate with the respective MAJCOM.

2.2.4 Trouble Reports

The contractor shall create incident tickets for all issues/incidents reported via telephone, email, and other communication methods and document all the incidents/tickets in a database, or format that allows process tracking for each issue from identification through final resolution. This shall include review capability of resolution tracking for verified personnel for “live access” supporting the need for real-time situational awareness and should be capable of enabling members from outside the MPSC Team, to include MAJCOM POCs and others like IVV&E, and Operation Location-1 (OL1) access to tracking data (if permitted). Users may be registered/vetted before receiving access to the helpdesk tracking/reporting system. MAJCOMs and their representatives should have view access to the tracking system but will not input data. The ticket/issue/tracking system will also have the capability to securely track/monitor issues addressed and managed in SIPR realm. Reports will highlight tickets/unresolved issues in work longer than 10 days. The issue identification/process/resolution data shall be available to the MPSSF Government team and metrics shall be reported monthly and shall identify issues open/unresolved/in work longer than 10 days (CDRL A003/B003). Data may be used for analysis and trending. Issue tracking through resolution for SIPR issues will be tracked/reported in a secure system/manner with secure/vetted access.

2.3 System Support Representatives (SSRs)

2.3.1 Standard USAF SSR

1. A standard USAF SSR provides support for MAJCOM Certified MPE and individual MAJCOM approved non-MPE for full-support customers. They also provide administrative system functions/support for the complete spectrum of mission planning systems at various commands, including Combatant Command and USAF installations worldwide. Some of these systems may be virtually contained on cloud/edge servers.

2.3.1.1 Standard SSR Pricing Table Categories

There are currently two security pricing table categories for a Standard USAF SSR:

1. AF SSR T2‐S – Standard USAF SSR with Information Assurance Technician (IAT) Level 2 certification, Secret clearance required

2. AF SSR T2‐TS/SCI – Standard USAF SSR with IAT Level 2 certification, Top Secret/Sensitive Compartmentalized Information clearance required

3. In the event an AF SSR T3-S and/or AF SSR T3-TS/SCI requirement is identified after JOMS deployment, this will be negotiated using the Not-to-Exceed pricing structure when/if the time comes.

2.3.1.2 SSR Support Level

There are 4 levels of SSR Support that may be ordered for any given location:

1. Reach-back Support – MPEs are sustained without the SSR providing daily on-site support.

The Mission Planners are primarily responsible for sustaining their own systems. When a user has a question, or an issue, they are able to “reach-back” to the helpdesk through the phone or email and receive assistance from an SSR. Software is updated through remote methods, or by utilizing shipping services to distribute the media (i.e. hard drives or discs). The SSR shall provide limited on-site support when the systems cannot be managed through other means. There is no support provided for non-MPE systems. This is the lowest level of support.

2. Reach-back Plus Support – The Mission Planners are primarily responsible for sustaining their own systems. MPEs are sustained without the SSR providing daily on-site support. The SSR will conduct monthly scheduled site visits to accomplish required periodic updates, DAFIF, etc. When a user has a question, or an issue, they are able to “reach-back” to the helpdesk through the phone, email, or other collaborative methods to receive assistance from a SSR. Outside of scheduled site visits, software is updated through remote methods or by utilizing shipping services to distribute the media (i.e. hard drives or discs). The SSR shall provide limited unscheduled on-site support when the systems cannot be managed via any other means; response time will vary based on location and SSR availability, but should be within 72 hours, if possible. Exceptions to 72 hours will be evaluated on a case-by-case basis in conjunction with the Mission Planning Contracting Officer Representative. There is no support provided for non-MPE systems.

3. Basic On-site Support – All current MPEs shall be sustained by an on-site SSR. There is no support provided for non-MPE systems.

4. Full Support – All MPEs, as well as all non-MPEs shall be sustained by an on-site SSR.

2.3.1.3 Standard USAF SSR Tasks

The contractor shall perform the standard USAF SSR tasks at the sites identified on the task orders and at the SSR Support Level ordered.

1. The contractor shall maintain hardware/software configuration management and control of certified and/or MAJCOM‐approved MPEs, including all items listed on each MPE letter.

SSRs will use Enterprise/MAJCOM - approved procedures/methodology for hardware support and maintenance (e.g. cloning, TCTO updates, anti-virus, etc.). SSRs will use Enterprise/MAJCOM - approved procedures/methodology for software support and maintenance (e.g. JMPS Falconview MPE, AGM MPE, etc.)

2. The contractor shall maintain hardware/software configuration management and control of other mission planning spectrum applications as approved by applicable MAJCOMs/Combatant Commands (Non-MPEs).

3. The contractor will ensure all system reporting/system configuration specification information in the Fielded Reporting Tool (or other designated tracking tool utilized by the Govt for system configuration tracking/reporting) is current (verifying configuration update completion(s) with “current as of” dates submitted upon update(s). This tool provides real time information for every computer system that is sustained by each SSR. It includes (but is not limited to): MPE version, SDC version, date of latest TCNO patches, date(s) of data updates, type(s) of hardware, type of connection (including stand-alone), and other information about the Mission Planning Systems in the field. This information is reported in a searchable and filterable centrally accessible tool, which is currently MPC. A minimum of 90 percent of configuration dates/updates must be in compliance with approved configurations at all times.

4. For mission planning computer systems requiring further maintenance actions, the contractor shall exercise warranty actions/repairs, locally, or pack/ship unserviceable systems to be returned for disposition through the Government End Item Manager.

5. The contractor shall install MPE upgrades and aid in the disposition of equipment. The contractor shall comply with system Security Practices and Procedures (SPP) for Automated Information Systems (AIS) utilized for classified (Confidential, Secret, Top Secret, and Special Access Required security) Mission Planning purposes. SSRs shall be cognizant of mission planning equipment locations, requisitions for in‐coming mission planning hardware (Mission Planning Equipment peripherals), and software releases.

6. SSRs are not to be utilized as Equipment Custodians for accountable items listed on a CA/CRL (R14 Account) or Automated Data Processing Equipment (ADPE) inventory listing.

SSRs are not responsible for requisitioning equipment, or installation/configuration of non‐ MAJCOM approved mission planning spectrum software.

7. SSRs shall work closely with crew members to ensure the MPE supports the mission parameters to meet operational objectives and safety requirements based on technical knowledge and experience. SSRs shall apply advanced technical training and professional expertise in application of computerized Mission Planning spectrum support equipment for aircraft weapon systems requiring Data Transfer Device (DTD) initialization using specialized software and hardware systems. The contractor shall provide feedback to the MPSSF for future incorporation into the helpdesk tool Frequently Asked Questions (FAQs).

8. The contractor shall establish Mission Planning spectrum software user account profiles and system defaults, modify access and execution permissions, as required, and recommend refinement changes to the SPPs. The contractor shall reconfigure systems to effectively utilize removable components and networked resources.

9. The contractor shall define, implement, and execute procedures and practices for loading new or updated mission planning data (i.e. charts, mapping updates, and aeronautical information;

such as Digital Aeronautical Flight Information File (DAFIF) data). The contractor shall be responsible for verification of MPSSF distributed media; ensuring fielded systems meet MAJCOM certification requirements for installation/loading of MAJCOM approved mission planning spectrum software and tools (Common Components (CCs), Installable Software Modules (ISMs), Unique Planning Components (UPCs), Operating System (OS), etc.), and maintain software/data configuration control. The contractor shall support a secure digital data depot repository and transfer mechanism. SSRs will use Enterprise/MAJCOM-approved procedures and methodology for data administration (e.g. Data Depot, SADUS, EASE, etc.).

10. The contractor shall analyze software, hardware, and system problems identified by the user to provide problem identification, duplication and testing, resolution, and tracking (to include logging the problem) until a resolution is found. The contractor shall perform local analysis and collaborate with the remote technical support team at the System Support Facility (SSF). The contractor shall ensure the specific problem details are entered into a centrally accessible tool, currently Mission Planning Central (MPC). The contractor shall manage defects IAW TO 00‐ 35D‐54 and other Enterprise process documents. Contractor will notify MPSSF team if/when trends may be identified during the collection of issue/failure data.

11. The contractor shall provide supplementary Mission Planning training for users, when requested, and integrate mission system capabilities into operational scenarios.

12. The contractor shall update mission planning users when changes to the mission planning spectrum equipment, software, and data are made to the MPE.

13. The contractor shall set-up/install, configure, and ensure proper functionality of MPE in support of exercise events (e.g. Red Flag, Green Flag), daily operational training missions, deployments and real‐world contingencies. The contractor shall travel to any worldwide locations to establish operational mission planning systems in locations without local SSR support, or locations needing additional (temporary) SSR support to complete the task/mission. Some short-notice activations and certain worldwide locations, may require US military transportation. When not immediately available, an SSR shall respond to a Mission Planning User’s request within two (2) hours of initial contact. The Mission Planning User can establish their request through the Request for Services (RFS) process currently in use, and/or may call the 24/7 helpline for assistance regarding the RFS process.

MAJCOMs/Mission Planning users may request to utilize their unit SSR for real world operations rather than more geographically located personnel. In accordance with each MAJCOMs travel policy, the contractor shall consider facilitating these specific requests, when possible.

14. The contractor shall maintain control and cognizance over all classified data encountered as a result of support activities. Use of classified data may include technical briefings during deployments, as authorized by the local commander.

15. The contractor shall participate in meetings and generate mission planning related reports.

(CDRL: A006/B006)

16. The contractor shall participate in Operational Test (OT) events when requested by the Operational Test Agency (OTA) and or Primary Customer.

17. SSR tasks shall extend to transient mission planning units deployed to the SSR’s location, limiting interference to the primary customer. Prioritization of tasks is defined by the primary customer.

18. SSRs shall provide daily on-site administration and maintenance of Edge Devices.

19. SSRs at select locations, particularly ANG fighter locations, shall be authorized to open or close the door to the secure area, as is deemed necessary by local unit leadership.

Additionally, proper unit training will be made available to ensure SSRs understand proper procedures associated with this task. This is to allow flexibility for SSRs to perform tasks without the need to engage local unit personnel.

2.3.1.4 Additional/Ancillary System Maintenance

Some locations have additional systems, and/or software, as part of their mission planning spectrum.

The contractor’s proposed price in the pricing table shall factor in the additional efforts of sustaining these extra systems at various locations and for each SSR support level (previously described in paragraph 2.3.1.2). Additional systems/databases currently include: Briefing Room Interactive (BRI), Patriot Excalibur (PEX), Beyond Line of Sight‐Situational Awareness Enhancement (BLOS‐SAE), Crew Familiarization Module (CFM), Communication Navigation Surveillance/Air Traffic Management (CNS/ATM) Database, Geospatial Products Library (GPL), Centralized Aviation Flight Records System (CAFRS), Combat Support Database (CSDB), Common Mission Debrief Program (CMDP), , C-17 Terrain Awareness Warning System (TAWS), Digital Tactics Binder (DTD).

2.3.2 Assault Zone SSR

The Assault Zone SSR shall reside in HQ AMC in order to support the Combat Operations Division (AMC A3D) which owns the Assault Zone Program. Aviation/airdrop experience is desired for this position. Familiarization with the capabilities of current Air Force airdrop Mission Planning software is required.

2.3.2.1 Assault Zone SSR Pricing Table Category

There is one pricing table category for an Assault Zone SSR:

1. AF AZ SSR T2‐S – Assault Zone SSR with IAT Level 2 certification, Secret clearance required.

2.3.2.2 Assault Zone SSR Tasks

The contractor shall perform the Standard USAF SSR tasks and additional Assault Zone SSR tasks:

1. The Assault Zone SSR shall manage the drop zone/landing zone submission and validation process, maintain the Valid Zone Availability Report (ZAR) and Historical ZAR databases, and maintain the ZAR Web Site.

2. The Assault Zone SSR shall review, verify, and validate all information on incoming surveys.

Once the information has been reviewed by AMC A3TW (Weapon and Tactics) for accuracy and safety, the Assault Zone SSR shall post the information to the ZAR website to be accessed by DoD personnel.

3. The Assault Zone SSR shall make identified ZAR data elements available to USTRANSCOM Table Reference Data Model (TRDM) to be shared with MAF C2 capital systems (GDSS and Consolidated Air Mobility Planning System (CAMPS)).

4. The Assault Zone SSR shall maintain Falcon View imagery server files to ensure imagery files are current.

5. As directed by HQ AMC/A3TW (Weapons and Tactics), the Assault Zone SSR shall attend conferences/symposiums where the airdrop community is a major participant and present briefings on ZAR related issues.

6. The Assault Zone SSR shall be authorized to open or close the door to the secure area, as deemed necessary by HQ AMC/A3TW leadership.

2.3.3 Combined Air Operations Center (CAOC) SSR

CAOC SSRs are specific to Geospatial Information and Services (GI&S) and other mission planning related C2 systems including intelligence streams and live feeds for Intelligence/Surveillance and Reconnaissance (ISR) systems. The CAOC SSR must establish a working relationship with all CAOC divisions, particularly the C2, C3, C5, and C6 (as well as the ISR Division).

2.3.3.1 CAOC SSR Pricing Table Category

There is one pricing table category for a CAOC SSR:

1. CAOC SSR T2‐TS/SCI – CAOC SSR with IAT Level 2 certification, Top Secret/Sensitive Compartmentalized Information clearance required.

2.3.3.2 CAOC SSR Tasks

The contractor shall perform the tasks specific to the CAOC SSR.

1. The contractor shall coordinate intelligence system requirements with the CAOC/C2.

2. The contractor shall perform tasks as the GI&S manager for the Targeting cell. This includes loading data on the GPL SIPRnet server, coordinating download of NGA data via the Global Broadcast System (GBS). The CAOC SSR(s) shall also maintain close liaison with other Geospatial POCs in the AOR and coordinate JTF‐SWA theater Geospatial requirements with CENTAF POCs.

3. The contractor shall brief system demands on the network to the CAOC/C6 and provide system administration tasks including control of configuration management of software upgrades.

4. The contractor shall interface with national level/DoD agencies, military branches, and other agencies/contractors providing feeds, bandwidth, architecture, structure or data to CAOC ISR systems. This includes maintenance and management of PC-based tools for viewing Predator feeds.

5. The contractor shall maintain mission planning systems as designated by the CAOC/C6 (or designated representative). This includes updates, maintenance of Air Force Intelligence Surveillance and Reconnaissance (AFISR) Agency generated threat parametric databases, and maintenance of master databases of threat drawing files.

2.3.4 ACC Test SSR

An ACC Test SSR provides administrative system functions/support for the complete spectrum of mission planning systems for developmental and operational test in support of integrated testing.

These support requirements are unique in that hardware/software configurations and system loads/updates are not dictated by MAJCOM certified releases. The SSR will conduct their tasks in a test security environment that is significantly different from Combat Air Force security requirements at operational units; this extends to vaults and discussions. These positions will be located at various CONUS locations to include Eglin AFB and Nellis AFB.

2.3.4.1 ACC Test SSR Pricing Table Categories

There are two security pricing table categories for an ACC Test SSR:

1. ACC Test SSR SSR T2‐S – ACC Test SSR with Information Assurance Technician (IAT) Level 2 certification, Secret clearance required

2. ACC Test SSR T2‐TS/SCI – ACC Test SSR with IAT Level 2 certification, Top Secret/Sensitive Compartmentalized Information clearance required

2.3.4.2 ACC Test SSR Tasks

The contractor shall perform the following ACC Test SSR tasks:

1. The contractor shall maintain hardware/software configuration management and control of multiple MPEs per MDS as needed to meet test objectives. Includes variations between MPEs and unique one-off configurations requiring their own unique support requirements.

2. The contractor shall maintain hardware/software configuration management and control of other mission planning spectrum applications as needed to meet test objectives.

3. The contractor shall support unique flight requirements to meet test objectives. Includes supporting aircrew need for very specific configurations to gather the appropriate test data, often in the core file structure.

4. The contractor shall analyze software, hardware, and system problems to meet test objectives. Includes providing problem identification, duplication and testing, resolution, and tracking until a resolution is found. Includes support for emergent technologies, understanding the impact on MPE configurations and being able to load appropriate software modules to determine what is broken and what is considered normal operations based on the emergent technology.

5. For mission planning computer systems requiring further maintenance actions, the contractor shall exercise warranty actions/repairs, locally, or pack/ship unserviceable systems to be returned for disposition through the Government End Item Manager.

6. The contractor shall aid in the disposition of equipment. The contractor shall comply with system Security Practices and Procedures (SPP) for Automated Information Systems (AIS) utilized for classified (Confidential, Secret, Top Secret, and Special Access Required security) Mission Planning purposes. SSRs shall be cognizant of mission planning equipment locations, requisitions for in‐coming mission planning hardware and software releases as applicable.

7. SSRs are not to be utilized as Equipment Custodians for accountable items listed on a CA/CRL (R14 Account) or Automated Data Processing Equipment (ADPE) inventory listing.

SSRs are not responsible for requisitioning equipment, or installation/configuration of non‐ MAJCOM approved mission planning spectrum software.

8. SSRs shall work closely with aircrew members to ensure the MPE supports the mission parameters to meet test and/or operational objectives and safety requirements based on technical knowledge and experience. SSRs shall apply advanced technical training and professional expertise in application of computerized Mission Planning spectrum support equipment for aircraft weapon systems requiring Data Transfer Device (DTD) initialization using specialized software and hardware systems. The contractor shall provide feedback to the MPSSF for future incorporation into the helpdesk tool Frequently Asked Questions (FAQs).

9. The contractor shall establish Mission Planning spectrum software user account profiles and system defaults, modify access and execution permissions, as required, and recommend refinement changes to the SPPs. The contractor shall reconfigure systems to effectively utilize removable components and networked resources.

10. The contractor shall define, implement, and maintain procedures and practices for loading new or updated mission planning data (i.e. charts, mapping updates, and aeronautical information; such as Digital Aeronautical Flight Information File (DAFIF) data). The contractor shall be responsible for verification of MPSSF distributed media; ensuring test and fielded systems meet MAJCOM requirements for installation/loading of MAJCOM approved mission planning spectrum software and tools (Common Components (CCs), Installable Software Modules (ISMs), Unique Planning Components (UPCs), Operating System (OS), etc.), and maintain software/data configuration control. The contractor shall support a secure digital data depot repository and transfer mechanism.

11. The contractor shall provide supplementary Mission Planning training for users, when requested, and integrate mission system capabilities into operational scenarios as needed.

12. The contractor shall update mission planning users when changes to the mission planning spectrum equipment, software, and data are made to the MPE.

13. The contractor shall set-up/install, configure, and ensure proper functionality of MPEs in support of daily test missions, daily operational training missions (as needed), exercise events, and deployments as directed. The contractor shall travel to any worldwide location to establish the required mission planning systems in locations to meet test objectives.

14. The contractor shall maintain control and cognizance over all classified data encountered as a result of support activities. Use of classified data may include technical briefings during deployments, as authorized by the local commander.

15. The contractor shall participate in meetings and generate mission planning related reports as required. (CDRL: A006/B006)

16. SSR tasks shall extend to transient mission planning units deployed to the SSR’s location, limiting interference to the primary customer. Prioritization of tasks is defined by the primary customer.

2.4 Subject Matter Expertise (SME)

The MPSSF has many different roles and responsibilities in the sustainment of mission planning systems; including subject matter expertise, cloud computing support, configuration management, technical publications, system administration, software security, Foreign Military Sales (FMS), and

MPC.

2.4.1 Platform SME

The contractor shall provide knowledge and expertise to all end users utilizing the mission planning software on various platforms. These mission planning platforms currently include: A-10, B-1B, B-2, B-52, C-21, C-27, C-5, C-17, C-130, CH-146, CH-147, HH-60G/W (Combat Rescue Helicopter), E-3, E-4, E-8, F-2, F-15, F-16, F-18, F-22, F-35, KC-10, KC-46, KC-135, MC-12, MQ-1, MQ-9, RC-135, RQ-4, T-1, T-6, T-7, T-38, U-2, U-125, UH-1N/TH-1H, and VIP Transport. Currently, some of these platforms provide their own mission planning support (i.e. F-22 and F-35); these platforms are listed to allow for support should it be needed at any point during this contract. Other platforms may be added in the future.

2.4.1.1 Platform SME Tasks

Many of the Platform SME tasks are cross-functional in nature. The contractor shall provide knowledge and perform specific tasks, detailed below, specific to each particular platform. The contractor shall also provide support for Air Force MPE users who are not tied to a specific platform and use a Mission Planning MPE independent of a specific platform.

1. The contractor SMEs provide “Level II” support to the Mission Planning Helpdesk. The contractor SMEs shall coordinate with the Mission Planning Helpdesk to address/resolve issues/trouble calls (as needed).

2. The contractor shall document all reported deficiency reports using a centrally accessible tool, currently recorded through the Enterprise Deficiency Reporting (EDR) tool on Mission Planning Central. Deficiency Reports (DRs) shall be reported to the appropriate mission planning community members IAW TO 00‐35D‐54. (CDRL: A003/B003).

3. The contractor shall provide initial deficiency investigation(s) for software and systems that are fielded/sustained, and provide suggestions for problem resolution, which includes forwarding unresolved problems to the appropriate organization(s), logging the problem(s), duplicating through testing, and analyzing/tracking until a resolution is found. Resolutions will be reported and accompany the help desk issue tracking data.

4. The contractor shall perform validation/verification of the mission planning products which includes monitoring accuracy, reliability, performance, security, and other identifiable areas.

5. The contractor shall provide operational perspective of an MPE to testing activities and coordinate test problem reports with testers ensuring issues/deficiency data is captured and reported within deficiency reports. The contractor shall provide detailed deficiency descriptions so software developers will understand each deficiency as they work to achieve resolutions.

6. The contractor shall provide feedback on MPEs during development and sustainment activities including test and hardware evaluations.

2.4.2 Command, Control, Communications, Computers, and Intelligence (C4I) SME

The contractor shall stay abreast of research, development, acquisition, security, system interfaces and fielding issues associated with C4I systems relating directly to mission planning interfaces to include: Global Command and Control Systems (GCCS); Unit Level‐-Unit Command Control (UL‐UC2) Ops and Intel, Personal Computer Integrated Intelligence and Imagery (PCI3), Target Acquisition Weapon Software (TAWS), Infrared Target Scene Simulation (IRTSS), Cloud One, All Domain Common Platform, or other cloud capabilities that are part of the Joint All-Domain Command and Control (JADC2) construct, or any follow‐on mission planning systems, such as the Joint Mission Planning System (JMPS) Open Mission Systems (JOMS); C2 Networked helpdesk infrastructure; Air Force Intelligence Surveillance and Reconnaissance Agency (AFISRA), Plans Directorate; Air Operations Centers, (AOCs), AF Information Warfare Center, Technology Directorate; and activities and developments concerning the Air Force’s Battle Lab Test Centers for issues relating directly to mission planning technology interfaces.

2.4.2.1 C4I SME Tasks

The contractor shall perform the Platform SME tasks and additional C4I SME tasks:

1. The contractor shall maintain files and databases on C4I systems and mission planning interfaces (PFPS, JMPS, TAWS, IRTSS) containing as a minimum, milestones, technical issues (e.g. system architecture, compatibility, interoperability, and integration), and lessons learned.

2. The contractor shall act as primary Point of Contact (POC) for all MPS/C4I systems interface issues.

3. The contractor shall brief MPSSF on changes and status in C4I systems, as requested.

4. The contractor shall provide limited user support for UL/UC2, PFPS, TAWS, IRTSS, JMPS‐ MPE, Birddog, Personal Computer Integrated Intelligence and Imagery (PCI3), Mission Planning Cell (MPC) Tool, and additional tools, as needed.

2.4.3 Cloud Computing SME

2.4.3.1 Cloud SME Tasks

The contractor shall provide support for Mission Planning Cloud Computing and elements utilizing Cloud Computing/Edge Servers and any/all digital data transfer assistance requested by MPSSF:

SME Tasks

1. The contractor shall provide direct technical Subject Matter Expert (SME) support for the Mission Planning Systems/MPE evolution to/through JMPS/JOMS sustainment (including deployment of services to cloud environments and edge computing devices). JOMS is a cloud native application and will be deployed to multiple cloud environments (including IL5, IL6, TS/SAP) and multiple edge devices.

2. The contractor’s Cloud SME(s) personnel shall meet the requirements of Level 2 Information Assurance Technician (IAT) outlined in DoD 8140 either at contract award or within 6 months of start of employment with the contractor.

3. The contractor’s Cloud SME(s) shall provide technical expertise and global support for MPSSF users seeking Tier 1 & Tier 2 intervention for Mission Planning cloud connections/applications 24/7.

4. The Cloud SME shall run scripts to deploy, update and monitor container-based applications, as needed.

5. The Cloud SME must respond to issues for connected and disconnected NIPRnet & SIPRnet and TS/SAP systems (including isolated MP Networks/Resiliency with local cloud/edge server(s).

6. The Cloud SME shall provide user systems authentication and fielded user identification support/resolutions.

7. The Cloud SME shall support the efforts of the Govt Cloud SME/Technical Team to monitor system usage, identify, and resolve issues.

8. The Cloud SME shall provide sustainment support for systems and tools used to monitor the cloud environment and load balance (preventing system impingements/failures).

9. The contractor must utilize established security protocols.

10. The Cloud SME shall support and manage (as required) services/data in containers, connections and integration with the cloud, and ensure cyber resiliency.

11. The Cloud SME must coordinate global system use/access (with evolution to cloud posture) for Mission Planning users, through integration, test, production and fielding phases.

12. The Cloud SME shall support disconnected/occasionally connected PCs and mobile devices, ensuring that system functionality is not degraded when disconnected.

13. The contractor shall document automated…