1AttachmentL1MPSCIIIPWS25Oct16.pdf

Performance Work Statement for

Mission Planning Support Contract III

(MPSC III)

Solicitation: FA8217-17-R-5000

25 October 2016

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 System Support Representatives (SSRs)

2.2.1 Standard USAF SSR

2.2.2 Assault Zone SSR

2.2.3 Combined Air Operations Center (CAOC) SSR

2.3 Subject Matter Expertise (SME)

2.3.1 Platform SME

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

2.4 Mission Planning Training (MPT)

2.4.1 MPT Tasks

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 MPSSF Computer Systems Administration (CSA)

2.8.1 MPSSF CSA Tasks

2.9 Software Security (SS)

2.9.1 SS 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 Control 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 Cybersecurity Tasks

2.11.4 MPC System Administration Tasks

2.11.5 MPC Sustainment Tasks

2.11.6 MPC Supplemental Tasks

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

6 Transition Period

6.1 Phase In

6.2 Phase Out

7 Acronyms

1 Description of Services The Mission Planning Support Contract (MPSC) ensures sustainment infrastructure is in place (or planned) for all Mission Planning Environments (MPEs). Sustainment of MPEs includes providing configuration management and control, drafting and publishing of technical documentation, system checkout, fielding, supply, maintenance, repair, training, customer assistance visits, a twenty‐four (24) hour/seven (7) day-a-week helpline, international sustainment and training, 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.

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. The Mission Planning System Support Facility (MPSSF) provides execution and sustainment to the supported organizations.

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 Material Command (AFMC), Air Force Reserve Command (AFRC), Air Force Space Command (AFSPC), Air Force Special Operations Command (AFSOC), Air Mobility Command (AMC), Air National Guard (ANG), Pacific Air Forces (PACAF), United States Air Forces in Europe (USAFE), and 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 Development Test (DT) Responsible Test Organization (RTO), the 46th Test Squadron, and the Operational Test (OT) organizations to include Det 2 Air Force Operational Test and Evaluation Center (AFOTEC), HQ AMC Test and Evaluation Squadron, 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-130, C-17, C-21, C-27, C-5, CSAR-X, E-3, E-4, E-8, F-15, F- 16, F-22, F-35, HH-60, JPADS, KC-10, KC-135, KC-46, MC-12, MQ-1, MQ-9, RC-135, RQ-4, T- 38, U-2, UH-1N, 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 later.

Support is also provided for Air Force 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 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 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.

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.

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 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, and procedures for the requirements/tasks in the monthly Activity Report.

(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 capabilities (CCs), and Unique Planning Components (UPCs); Joint Precision Airdrop System (JPADS); 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 for overall technical support; operational experience;

software development, maintenance, 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:

FUNCTION SOFTWARE

Operating Environment Windows

Electronic Mail Outlook

Graphics 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, and electronic.

2.1.1.5 Security Requirements

All contractor personnel shall obtain security clearances to the proper level 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.

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 to workshops, test sites, training locations, and other symposiums, meetings and conferences as requested by the Government when an alternate means such as Secure Video Teleconference (SVTC) or other web based communications are not sufficient to accomplish the travel objective. The contractor shall prepare a trip report at the completion of Government directed travel. (CDRL:

A005/B005)

2.1.1.7 Unique Identification (UID) Policy

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

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

2.1.1.7.2 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;

2.1.1.7.3 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

2.1.1.7.4 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 System Support Representatives (SSRs)

2.2.1 Standard USAF SSR

A standard USAF SSR provides system administrative functions to the complete spectrum of mission planning systems at Combatant Command and USAF installations worldwide.

2.2.1.1 Standard SSR Pricing Table Categories

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

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

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

2.2.1.2 SSR Support Level

There are 3 levels of SSR Support which may be ordered for a given location:

2.2.1.2.1 Reach-back Support –MPEs are sustained without the SSR being on-site daily.

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 to get help 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.2.1.2.2 Basic On-site Support – All current MPEs shall be sustained by an on-site SSR.

2.2.1.2.3 Full Support – All MPEs and all non-MPEs shall be sustained by an on-site SSR.

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

2.2.1.3.1 The contractor shall maintain hardware/software configuration management and control of certified and/or MAJCOM‐approved MPEs.

2.2.1.3.2 The contractor shall maintain hardware/software configuration management and control of other mission planning spectrum applications as approved by applicable MAJCOMs/Combatant Commands.

2.2.1.3.3 For mission planning computer systems requiring further maintenance actions, the contractor shall exercise the warrantee locally or pack up unserviceable systems to be returned for disposition through the Government End Item Manager.

2.2.1.3.4 The contractor shall install MPE upgrades and aid in 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 of in‐coming mission planning hardware, and software releases (includes dropsondes and laptop connection cables).

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

2.2.1.3.6 SSRs shall work closely with crewmembers 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).

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

2.2.1.3.8 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), Aircraft/Weapons/Electronics (A/W/Es), Operating System (OS), etc.), and maintain software/data configuration control.

2.2.1.3.9 The contractor shall analyze software, hardware, and system problems found 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 analysis locally and in conjunction 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. The contractor shall manage defects IAW TO 00‐35D‐54 and other Enterprise process documents.

2.2.1.3.10 The contractor shall provide supplementary mission planning training for users when requested and integrate mission system capabilities into operational scenarios.

2.2.1.3.11 The contractor shall create and deliver technical briefings for mission planning users when changes to the mission planning spectrum equipment, software, and data are made to the MPE.

2.2.1.3.12 The contractor shall set-up, configure, and ensure proper functionality of an MPE in support of exercises (e.g. Red Flag, Green Flag), daily operational training missions, deployments and real‐world contingencies, as directed. The contractor shall travel to 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. For some short-notice activations or certain worldwide locations, US military transportation may be necessary. 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 make their request known through the 24/7 helpline.

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

2.2.1.3.14 The contractor shall participate in meetings and generate mission planning related reports. (CDRL: A007/B007)

2.2.1.3.15 The contractor shall participate in Operational Test (OT) events when requested by the Operational Test Agency (OTA).

2.2.1.3.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.2.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), Warfighter’s Edge (WEdge), Beyond Line of Sight‐Situational Awareness Enhancement (BLOS‐SAE), Crew Familiarization Module (CFM), Personal Computerized Debriefing System (PCDS), Commercial Navigation System/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).

2.2.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 of the capabilities of current Air Force airdrop mission planning software is required.

2.2.2.1 Assault Zone SSR Pricing Table Category

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

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

2.2.2.2 Assault Zone SSR Tasks

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

2.2.2.2.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.2.2.2.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.

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

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

2.2.2.2.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.2.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.2.3.1 CAOC SSR Pricing Table Category

There is one pricing table category for a CAOC SSR:

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

2.2.3.2 CAOC SSR Tasks

The contractor shall perform the tasks specific to CAOC.

2.2.3.2.1 The contractor shall coordinate intelligence system requirements with the

CAOC/C2.

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

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

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

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

The MPSSF has many different roles and responsibilities in the sustainment of mission planning systems; including subject matter expertise, training, configuration management, technical publications, system administration, software security, foreign military sales (FMS), and MPC.

2.3.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-130, C-17, C-21 C-27, C-5, CSAR-X, E-3, E-4, E-8, F-15, F-16, F-22, F- 35, HH-60, JPADS, KC-10, KC-135, KC-46, MC-12, MQ-1, MQ-9, RC-135, RQ-4, T-38, U-2, UH-1N, and VIP Transport. Other platforms may be added later.

2.3.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 JMPS MPE users who aren’t tied to a specific platform, but use JMPS independent of a platform.

2.3.1.1.1 The contractor shall provide a twenty‐four (24) hour/seven (7) day-a-week helpline. While users 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 has basic knowledge and expertise of Mission Planning, their issue may require resources that are only available during MPSSF office hours. The MPSSF office hours are 0600-1800 hours Mountain Time, Monday through Friday (excluding holidays).

2.3.1.1.2 The contractor shall provide initial deficiency investigation for software and system problems found by the user/test communities and provide suggestions for problem resolution; which includes forwarding unresolved problems to the appropriate organization, logging the problem, duplicating through testing, and analyzing/tracking until a resolution is found.

2.3.1.1.3 The contractor shall document all validated trouble calls using a centrally accessible tool, currently Enterprise Deficiency Reporting (EDR) Mission Planning Central. If the trouble call results in a Deficiency Report (DR), it shall be reported to the appropriate mission planning community members IAW TO 00‐35D‐54.

2.3.1.1.4 The contractor shall access and update the centrally accessible deficiency database, coordinate with user support personnel on trouble call details, serve as the point of contact for problems or improvements, and prepare monthly call summaries and metrics.

(CDRL: A003/B003)

2.3.1.1.5 Platform SMEs shall supplement the training team when additional knowledge is needed by the mission planning users. The contractor shall train end users on aircraft/mission specific aspects of the MPE (CWDS, CAT, A/W/E, TAWS, etc.).

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

2.3.1.1.7 The contractor shall provide operational perspective of an MPE to testing activities and coordinate test problem reports with testers on problem details for boarding of deficiency reports. The contractor shall describe specific details of deficiencies with enough detail that software developers will understand as they work to achieve resolution.

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

2.3.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.3.2.1 C4I SME Tasks

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

2.3.2.1.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.3.2.1.2 The contractor shall act as primary point of contact for all MPS/C4I systems interface issues.

2.3.2.1.3 The contractor shall monitor progress of replacement of Theater Battle Management Core System TBMCS‐FL and UL and UL/UC2 and bring problems to the attention of MP team leadership.

2.3.2.1.4 The contractor shall periodically brief MPSSF on changes and status in C4I systems.

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

2.4 Mission Planning Training (MPT)

The primary training audience will consist of military members who use mission planning software for operational mission planning and shall be limited to those services, commands, and weapon systems supported by the MPSSF. The contractor shall train SSRs and government system administrators in the administration of mission planning systems. The contractor shall also train developers and members of the test community to directly support the development and test process for mission planning MPEs. The contractor shall liaise with members of the test community to ensure necessary training is provided for the testing of MPEs.

2.4.1 MPT Tasks

The contractor shall provide training services to the mission planning community. Trainers require IAT Level 2 certification and TS/SCI clearances. Training materials shall be developed in accordance with the USAF’s Instructional Systems Development (ISD) process. (CDRL:

A006/B006) The training shall be provided as self-paced, computer based, electronic learning (e-learning) instruction; or instructor-led classes. Instructor-led training shall be available to mission planners via classes held at centralized training locations (e.g. Eglin AFB, FL) and/or at a unit’s home station. All training material developed under this effort shall be in accordance with the Government Purpose License Rights paragraph of the Mission Planning Enterprise Business and Technical Rules. Training materials are property of the United States Government (USG) and will be available through MPC to the mission planning community, including mission planning contractors, their sub‐contractors, and other government agencies, for the purposes of self‐paced study and the development of other mission planning training material.

The contractor shall develop training focused on a platform’s MPE. The contractor shall have the training package (user and system administration) ready when the MPE enters operational test (OT). (CDRL: A006/B006) Training provided to units at their home station shall be based on their fielded MPE. To support practical class loads, training at centralized locations may be aggregated at “mission” levels such as fighter/bomber or tanker/airlift.

Specific training tasks include:

2.4.1.1 The contractor shall work with users and software developers to establish a thorough understanding of the components of the MPE.

2.4.1.2 The contractor shall analyze training requirements of the MPE and build objective‐ based modular training. The contractor shall write syllabi that provide a summary of course content, optimum class structure, time management, and required resources.

2.4.1.3 The contractor shall develop supporting materials (instructor guides, presentation slides, student exercises, passive and interactive computer presentations, reference guides, etc.).

2.4.1.4 The contractor shall maintain a separate JMPS MPE training course that includes key Common Capabilities (CCs), such as weather and threats. The contractor shall tailor the course toward aviation as well as non-aviation USAF users (e.g. Intel) and other DoD/Government agencies.

2.4.1.5 For each MPE, the contractor shall develop both a Mission Planning User’s course and MPE System Administrator’s course.

2.4.1.6 For each MPE, the contractor shall provide guidance, expertise, and materials for “train the trainer” concepts and requests.

2.4.1.7 For each new MPE delivery, the contractor shall provide comprehensive MPE training to the operational test community as a part of the operational test.

2.4.1.8 Based on requirements from the applicable MAJCOM and/or operational units and the advice of the contractor with applicable SME, the contractor shall provide training to users and/or SSRs (or other Systems Administrators) at bases worldwide in‐conjunction with fielding efforts.

2.4.1.9 The contractor shall deliver training relative to all mission planning software.

2.4.1.10 The contractor shall maintain web‐based documentation to provide effective training content and materials for distance learning.

2.4.1.11 The contractor shall create and utilize feedback instruments for students to report satisfaction with their training experience and provide contract and Government leadership with feedback data and other reports.

2.4.1.12 The contractor shall analyze student feedback to make improvements in course content and presentation.

2.4.1.13 The contractor shall coordinate with users to arrange facilities and equipment for local and off‐station training. The instructor(s) shall be scheduled to support each off‐station training request to include preparation, shipment, and set‐up of training hardware.

2.4.1.14 The contractor shall develop and maintain a training support plan specifying mission planning training objectives, resources, and methods. The contractor shall coordinate the plan with major commands to ensure that MP training is meeting stated objectives. (CDRL A001/B001)

2.4.1.15 The contractor shall maintain a current working knowledge of personal computer technologies, to include hardware, operating system software (client and server), networking, and application software.

2.4.1.16 The contractor shall respond to requests from individuals regarding course content and availability, scheduling students for classes, and generate training certificates and documentation, to include trainee attendance lists.

2.4.1.17 As requested, the contractor shall facilitate the integration of MP training into existing formal military training (e.g. aircraft replacement training units, intelligence career field technical training).

2.4.1.18 The contractor shall perform periodic reviews of MP Enterprise training approach and make recommendations to the Government for continued efficiencies and improvements.

(CDRL: A004/B004)

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. Configuration control includes the evaluation of all change requests and change proposals, and their subsequent approval or disapproval. It is the process of controlling modifications/versioning of mission planning hardware, software, and documentation.

2.5.1 Configuration Management Tasks

2.5.1.1 The contractor shall manage MPE deliveries, estimate workload requirements (CDRL: A001/B001), and act as the communications and distribution hub for all mission planning configuration management related items. The contractor shall provide communication pathways for elevation of sustainment configuration issues to the Mission Planning Enterprise.

2.5.1.2 The contractor shall act as the primary focal point for all mission planning configuration communications after an MPE completes Formal Qualification Test (FQT). The contractor shall review and collaborate on MPE letters prior to board review meetings (e.g.

Enterprise Engineering Review Boards (E‐ERB) and Enterprise Configuration Control Boards (E‐CCB)). The contractor shall track MPE configurations, to include versions of individual components and software (e.g. device drivers).

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

2.5.1.4 The contractor shall research any 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 (CPIN) to MPE software.

2.5.1.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 post‐FQT software (as identified on the appropriate MPE letter) and distribute the MPE via appropriate means to internal and external agencies.

2.5.1.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 impact on fielded systems; paying 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.

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

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

2.5.1.9 The contractor shall maintain currency of the CM library within the centrally accessible tool. This includes entering all data, software, and documentation received by the

MPSSF.

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

2.5.1.11 The contractor shall use the Automated Computer Program Identification Number System (ACPINS) 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.

2.5.1.12 CM shall be responsible to duplicate and distribute MPE test packages to the appropriate test agencies by the test start date. These test packages may be a combination of

Blu-Ray Disks, CD‐ROM, DVD, floppy discs, 4mm tape, and hard drives. The contractor shall ensure that the media being sent to the test agencies installs properly prior to shipment. Note:

the contractor must be aware of, and follow Hill AFB mailroom deadlines. This is especially important when shipping classified software.

2.5.1.13 The contractor shall monitor product line requests on MPC and process those requests in accordance with mission planning software CM procedures and product line versioning rules.

2.5.1.14 The contractor shall encrypt media 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 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 A009/B009)

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

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

2.6.1.3 The contractor shall utilize military standards/TOs to develop quality technical publications processes and procedures.

2.6.1.4 The contractor shall create, update, validate and verify TCTO for all mission planning post‐FQT software in accordance with military standards and TO 00‐5‐1‐15. (CDRL:

A009/B009)

2.6.1.5 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:

A009/B009)

2.6.1.6 The contractor shall create, update, validate, and verify TOs for all mission planning hardware in accordance with military standards and TO 00‐5‐1. (CDRL: A009/B009)

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

2.6.1.8 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

2.7.1.1 The contractor shall act as the primary logistic and technical focal point 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 take support 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 relative to ensuring safe and effective operation of Mission Planning Equipment items.

The contractor shall document reported problems, deficiencies, troubleshooting notes and solutions into the appropriate system 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 Unit (LRU) 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. 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) to needed audiences.

2.7.1.2 The contractor shall act as the primary focal point for the return of unserviceable mission planning hardware from end users through USAF Supply System. 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. Outbound shipments of mission planning end items are accomplished only upon the direction of the United States Air Force. The contractor shall coordinate repair of unserviceable equipment items with third party support organizations provided/directed by the United States Air Force.

2.7.1.3 The contractor shall participate in and make recommendations during hardware technical specification discussions supporting the acquisition of new Mission Planning Equipment. The contractor shall travel to support enterprise meetings and other meetings requiring hardware support such as, fielding events and inspections for quality control with a vendor before asset delivery. (CDRL: A011/B011) 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: A010/B010)

2.7.1.4 The contractor shall coordinate with Configuration Management function and provide inputs 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 setup and maintenance of Mission Planning Equipment.

2.7.1.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 Enterprise and MAJCOMs relative to improving or enhancing overall equipment or software lifecycle. (CDRL: A004/B004) 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)

2.8 MPSSF Computer Systems Administration (CSA)

2.8.1 MPSSF CSA Tasks

2.8.1.1 The contractor shall provide computer system administration support/sustainment to all MPSSF servers (NIPRnet/SIPRnet/local net). This will include all servers used by the MPSSF Government personnel as well as the MPSSF contractor personnel.

2.8.1.2 The contractor shall maintain a file backup server for the files of all MPSSF computers and servers. As a minimum, the files shall be backed up on a daily incremental basis.

2.8.1.3 The contractor shall maintain and track MPSSF support equipment inventory. This includes software, hardware, and associated documentation.

2.8.1.4 The contractor shall maintain and track the warranties, software licenses, and maintenance agreements of the MPSSF support resources.

2.8.1.5 The contractor shall develop/maintain MPSSF Business Continuity Plans. This includes disaster recovery plans, identification of priority resources, and user account management plans.

2.8.1.6 The contractor shall sustain all MPSSF network support resources. The contractor shall troubleshoot issues that may arise. The contractor shall compile, analyze, consolidate, and/or develop reports of potential deficiencies and determine corrective action and coordinate prioritized recommendations.

2.8.1.7 The contractor shall monitor MPSSF support resources and Mission Planning Systems for viruses and take corrective action, when necessary.

2.8.1.8 The contractor shall maintain technology currency and make recommendations for required network updates.

2.8.1.9 The contractor shall implement, maintain, and provide configuration management of software and hardware installation/de‐installation scripts on support resources.

2.8.1.10 The contractor shall create/maintain network security accreditation in accordance with DoD, USAF, and Hill AFB requirements. This includes DoD 8570.01‐M, Change 4 (or latest revision).

2.9 Software Security (SS)

2.9.1 SS Tasks

2.9.1.1 The contractor shall provide Time Compliance Network Order (TCNO) sets per MPE on at least a monthly recurring basis. 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 COTS software environment identified in the MPE. The contractor shall make TCNO sets available to the Mission Planning Enterprise via a centrally managed MPSSF website.

2.9.1.2 The contractor shall create, provide, and configuration-control Group Policy Objects (GPOs) and associated files for all MPEs residing on the Department of Defense Information Network (DoDIN), or AF‐approved follow‐on system. The contractor shall make these GPOs available to the Mission Planning Enterprise via a centrally managed MPSSF website.

2.9.1.3 The contractor shall perform security hardware evaluations against all potential hardware being considered by the Mission Planning Enterprise for fielding use.

2.9.1.4 The contractor shall conduct MPE security reviews of MPE System Security Authorization Agreements (SSAA) and related documentation. The contractor shall track this information per MPE, as applicable, in the Enterprise Information Technology Data Repository (EITDR), Enterprise Mission Assurance Support Service (eMASS), and/or Risk Management Framework (RMF) systems.

2.9.1.5 The contractor shall provide dedicated on-site support at the Integrated Network Operations and Security Centers (INOSC-East at Langley AFB, and INOSC-West at Peterson AFB) to monitor, track, and control the configuration and use of MPS Organizational Units (OUs) for operational units in the field. The contractor shall coordinate with AF network personnel to maintain the integrity of Mission Planning Systems across the Air Force.

2.9.1.6 The contractor shall provide software security expertise to end users and SSRs concerning all approved/certified MPEs.

2.9.1.7 The contractor shall review Standard Desktop Configuration (SDC)/Federal Desktop Core Configuration (FDCC) images, and associated updates for potential negative impact on approved/certified MPEs.

2.9.1.8 The contractor shall provide reports and status on data and metrics to include MPE TCNO evaluation data, project status, trip reports, and hardware evaluation data. (CDRL:

A005/B005)

2.9.1.9 The contractor shall travel to and participate in…