DRAFT_RFP_Attachment_1_AttachmentL1MPSCIVPWSDRAFT1Nov21.pdf

MPSC IV PWS

Performance Work Statement for Mission Planning Support Contract IV

(MPSC IV)

Solicitation: FA8217-22-R-0001

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)

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.4 Subject Matter Expertise (SME)

2.4.1 Platform SME

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

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

3.2.1 Reporting Inputs

3.2.2 Uses and Safeguarding Information:

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). 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.

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 (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, 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, CSAR-X, E-3, E-4, E-8, F-2, F-15, F-16, F-18, F-22, F-35, HH-60/Combat Rescue Helicopter, 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.

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.

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.

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 a certified MPE letter.

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.

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/C001) The contractor shall report the completion of the functions, duties, responsibilities, procedures and system availability metrics for the requirements/tasks in the Monthly Activity Report (MAR). (CDRL: A003/B003/C003)

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 capabilities (CCs), and Unique Planning Components (UPCs); Joint Precision Airdrop System (JPADS); JMPS Open Mission System (JOMS), Airdrop Item Tracking System (AITS), 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). 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 is required.

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/C005)

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.

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. (For information only: i.e. there are 3 Air Force bases located at 8 hr time zone intervals around the globe: Hill AFB, Utah; Spangdahlem AFB, Germany; and Kadena AFB, Japan).

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. The issue identification/process/resolution data shall be available to the MPSSF Government team and metrics shall be reported monthly (CDRL A003/B003/C003). Data may be used for analysis and trending.

2.3 System Support Representatives (SSRs)

2.3.1 Standard USAF SSR

A standard USAF SSR provides 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 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

2.3.1.2 SSR Support Level

There are 3 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. Basic On-site Support – All current MPEs shall be sustained by an on-site SSR.

3. Full Support – All MPEs and 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.

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 (including dropsondes and laptop connection cables), 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 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 fielded systems meet MAJCOM certification requirements for installation/loading of MAJCOM approved mission planning spectrum software and tools (Common Capabilities (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.

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, as directed. 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 24/7 Helpline.

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/C006)

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.

2.3.1.4 Additional System Maintenance

Some locations have additional systems 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.2.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), Personal Computerized Debriefing System (PCDS), Communication Navigation Surveillance/Air Traffic Management (CNS/ATM) Database, Geospatial Products Library (GPL), Centralized Aviation Flight Records System (CAFRS), Improved Many on Many (IMOM), Combat Support Database (CSDB), Common Mission Debrief Program (CMDP), Order of Battle Management Tool (OBMT), C-17 Terrain Awareness Warning System (TAWS), Vector Vertical Obstruction Data (VVOD).

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 A3D 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/A3D, the Assault Zone SSR shall attend conferences/symposiums where the airdrop community is a major participant and present briefings on ZAR related issues.

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.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, CSAR-X, E-3, E-4, E-8, F-2, F-15, F-16, F-18, F-22, F-35, HH-60/Combat Rescue Helicopter, 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. 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/C003)

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), or any follow‐on mission planning systems, such as the Joint Mission Planning System (JMPS)‐‐MPE; 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), and additional tools, if 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 mechanisms for deployment, monitoring, management, and maintenance of cloud environments, as needed.

14. The Cloud SME shall support the Govt Cloud SME/Technical Team in efforts to diagnose and remediate technical problems.

15. The Cloud SME shall support the Govt Cloud SME platform usage and capacity metrics data capture and analysis, as needed.

16. The Cloud SME shall contribute to redundancy planning/backup and disaster recovery planning.

17. The Cloud SME shall interact with vendors and service providers to resolve system related problems and work with Development Team and Cloud vendors to implement deployment pipelines.

2.5 Configuration Management (CM)

The systems engineering process for establishing and maintaining consistency of Mission Planning performance, functional and physical attributes with its requirements, design and operational information throughout its life (aka configuration management responsibility) is retained at the Mission Planning Enterprise level.

The contractor shall be responsible for configuration control including the evaluation of all change requests and change proposals, their subsequent approval or disapproval of CM requests, and the process of controlling modifications/versioning of mission planning hardware, software, and documentation.

2.5.1 Configuration Management Tasks

The contractor shall perform the CM tasks.

1. The contractor shall manage MPE deliveries, estimate workload requirements (CDRL:

A001/B001/C001), and act as the communications and distribution hub for all fielded mission planning configuration management related items. The contractor shall provide communication pathways for the elevation of sustainment configuration issues to the Mission Planning Enterprise.

2. The contractor shall act as the primary focal point for all mission planning configuration communications after an MPE completes formal testing. The contractor shall review and collaborate on MPE letters prior to board configuration review meetings. The contractor shall maintain current tracking/reporting of MPE configurations CM data, to include versions of individual components and software (e.g. device drivers).

3. The contractor shall act as the primary MPSSF focal point for validation/verification of MPE configuration(s) and control.

4. The contractor shall research fielded software and hardware incompatibility issues and establish baselines. The contractor shall work with the base Software Control Center (SCC) to assign Computer Program Identification Numbers (CPINs) to MPE software.

5. The contractor shall manage and validate the configuration of MPE letters in accordance with the Enterprise MPE Letter Process throughout a system’s lifecycle. The contractor shall duplicate software (as identified on the appropriate MPE letter) and distribute the MPE via appropriate means to internal and external agencies.

6. The contractor shall designate one primary and at least one alternate Sustainment Screening Point in accordance with T.O. 00‐35D‐54. The Sustainment Screening Points shall review all new discrepancy reports (DRs) for their impacts on fielded systems; focusing particular attention to high priority DRs IAW T.O 00‐35D‐54. The Sustainment Screening Point is the designated focal point for the receipt and processing of MPE sustainment DRs. The sustainment Screening Point reviews the DR for proper categorization, validity, correctness of entries, accuracy and completion of information addresses; determines and transmits the DR to the proper Action Point within or outside the organization and/or component.

7. With Government oversight, the contractor shall research, facilitate, and document the evaluation of all sustainment DRs within the DR management system via the sustainment deficiency review board process.

8. The contractor shall monitor the lifecycle status of software to be released and generate the release package for duplication and distribution to the field upon receipt of the distribution letter.

9. The contractor shall maintain currency of the information associated with the CM library, the centrally accessible tool, which is currently MPC. This includes entering all data, software, and documentation received by the MPSSF.

10. The contractor shall maintain and track mission planning software and documentation library.

This includes logging and filing incoming information (data, media, and official documentation), informing mission planning personnel of library additions, locating requested information, maintaining archives, and periodically purging obsolete information and ensuring compliance with all data/media capture/archive/filing/destruction regulations.

11. The contractor shall use the Enhanced Technical Information Management System (ETIMS) for managing Computer Program Identification Numbers (CPINs) and interface with the SCC on base for distributing scheduled software updates and urgent patches as required or for generating lists of users who are on requirement for specific software.

12. CM shall be responsible to duplicate and distribute MPE test packages to the appropriate test agencies before test start date(s), upon request. Test packages may contain a combination of Blu-Ray Disks, CD‐ROM, DVD, and hard drives. The contractor shall ensure that the media sent to the test agencies installs properly (prior to shipment). Note: the contractor must be aware of, and comply with Hill AFB mailroom requirements. This is especially important when shipping classified software. Contractor will ensure compliance with all necessary courier and transportation regulations and have all necessary documents and authorizations.

13. Contractor shall manage the product line information on MPC and ensure the records are updated with the latest inputs from requests that are submitted (information managed/reported by PL Manager shall be accurate/current). The Product Line Manager shall process requests for new products (or changes to the current product line items) in accordance with mission planning software CM procedures and product line versioning rules.

14. The contractor shall ensure media is properly encrypted prior to distribution in accordance with the Mission Planning Program Protection Plan. The contractor shall maintain a database of passphrases, MD5 checksums, and SHA-256 checksums for all encrypted files (including files that are encrypted at the MPSSF and files that arrive from the developer already encrypted). The contractor shall also document the MD5 and SHA-256 checksums of the various versions of encryption software. This database shall be accessible by the Government Passphrase Custodian.

2.6 Technical Publications

2.6.1 Technical Publications Tasks

The contractor shall perform the technical publications tasks

1. The contractor shall develop and modify mission planning, Technical Orders (TOs), Time Compliance Technical Orders (TCTOs), and supporting documentation for USAF mission planning systems per applicable directives. (CDRL A008/B008/C008)

2. The contractor shall act as the primary focal point for all mission planning technical publications communications for fielded systems and maintain configuration control of the TOs supported; to include modifications, baselines, updates, releases, lessons learned, and process documentation.

3. The contractor shall review vendor provided documentation and initiate actions tailored to mission planning standards. Information from vendor provided documentation may be needed for validation, verification, peer reviews, and provisioning conferences.

4. The contractor shall utilize military standards/Technical Orders to develop accurate technical publications, processes, and procedures.

5. The contractor shall create, update, validate and verify Time Compliance Technical Orders (TCTOs) for all mission planning software in accordance with military standards and TO 00‐5‐

15. (CDRL A008/B008/C008)

6. The contractor shall create periodic TCTO documentation disks. The contractor shall deliver draft installation TCTOs (instructions for installing mission planning software) for DT and OT events and finalized versions of TCTOs shall be provided for fielding events. (CDRL A008/B008/C008)

7. The contractor shall create, update, validate, and verify TOs for all mission planning hardware in accordance with military standards and TO 00‐5‐1, AF Technical Order System. (CDRL A008/B008/C008)

8. The contractor shall create documentation packages containing work packs for all hardware TOs and the interconnect TOs, and provide packages to applicable Government authorities.

9. The contractor shall create, update, and validate Quick Reference Guides (QRGs)/JMPS Reference Guides (JRGs) for Mission Planning Systems.

2.7 Hardware Support

2.7.1 Hardware Support Tasks

The contractor shall perform hardware support tasks.

1. The contractor shall act as the primary logistics and technical focal point/POC for all Mission Planning Equipment items and software. The contractor shall participate in hardware deficiency investigations to resolve issues with fielded systems. The contractor shall receive support desk/help desk calls and reported system deficiencies from operational users, and others within the Enterprise. The contractor shall analyze and provide technical solutions to software, hardware, and system problems to ensure safe and effective operation of Mission Planning Equipment items. The contractor shall document reported problems, deficiencies, troubleshooting notes and solutions into the appropriate systems of record. The contractor shall coordinate warranty support between vendors and end-users for Mission Planning Equipment. When directed, the contractor shall perform intermediate user or Line Replaceable Units (LRUs) maintenance using equipment or components provided by the Government, e.g., removal and replacement of user replaceable components within an end item where some level of disassembly and reassembly may be required. Also, when directed by the government the contractor will coordinate the set-up of third party hardware repair for assets and needed. Funding for this effort will be provided by the proper MAJCOM/Government, but the contractor will oversee the effort from set-up to repair. The contractor shall elevate urgent hardware and software issues to the Enterprise and the MAJCOMs. The contractor shall provide briefings/communication to fielding team members in support of fielding events. The contractor shall provide briefings and other communications (written and/or oral). When directed by the government, the contractor will coordinate the set-up of third party hardware repair for assets as needed. Funding for this effort will be provided by the proper MAJCOM/Government, but the contractor will oversee the effort from the set-up to repair

2. The contractor shall interface with the Item Manager and support the return of unserviceable mission planning hardware from end users. The contractor shall receive equipment from operational units, maintain inventory records for all Mission Planning Equipment items or components within the contractor’s control, and document all shipments of government property from facility. The contractor shall not act as equipment custodian for the United States Air Force. Outbound shipments of mission planning end items are accomplished upon the direction of the United States Air Force. The contractor shall coordinate the repair of unserviceable equipment items with third party support organizations provided/directed by the United States Air Force.

3. The contractor shall participate in hardware technical specification discussions supporting the acquisition of new Mission Planning Equipment. The contractor may travel to support enterprise meetings and other events requiring hardware support such as, fielding events and inspections for quality control with a vendor before asset delivery. (CDRL: A010/B010/C010) The contractor shall provide recommendations concerning replacement or modifications to fielded systems. The contractor shall conduct First Article inspections for new hardware and evaluate the physical configuration of the new hardware for conformance with Government specifications (i.e. applicable AF/DoD requirements). (CDRL: A009/B009/C009)

4. The contractor shall coordinate with Configuration Managers and provide input to Configuration Management and Technical Publications to ensure the associated documentation is correct for the fielded systems. The contractor shall provide training for SSRs, Air Force personnel, and others (as directed by the Government) regarding the proper installation/testing and maintenance of Mission Planning Equipment.

5. The contractor shall monitor and analyze hardware and software support data. The contractor shall report relevant problems and trends to the Enterprise and MAJCOMs. The contractor shall provide recommendations to the Enterprise and MAJCOMs to improve or enhance the overall equipment or software lifecycle. (CDRL: A004/B004/C004) The contractor shall collect Operational Safety Suitability and Effectiveness (OSS&E) metrics according to internal and enterprise-level processes for risk management and engineering control boards. (CDRL:

A003/B003/C003)

2.8 Software Security Team (SST)

2.8.1 SST Tasks

The contractor shall perform SST tasks.

1. The contractor shall provide Time Compliance Network Order (TCNO) sets within one week of release date. The TCNOs may be organized by Framework/Standard Desktop Configuration (SDC) pairing as long as each MPE is represented. The contractor shall analyze these TCNO sets for applicability and evaluated for impact before being released. The contractor shall also coordinate with the Systems Engineering and Integration Contract (SEIC) contractor for further evaluation. The contractor shall build each TCNO set according to the Commercial-Off- The-Shelf (COTS) software environment identified in the MPE.