Performance Work Statement

PERFORMANCE WORK STATEMENT

SOLICITATION FA8217‐10‐R‐5022

For

MISSION PLANNING SUPPORT CONTRACT II (MPSC II)

29 NOVEMBER 2010

1 Description of Services

1.1 Introduction

1.1.1 Program Description

The Mission Planning Support Program ensures that adequate sustainment infrastructure is in place or programmed for all Mission Planning Systems (MPS) and will be accomplished through the planning, programming, management, and budgeting for basic sustainment of the MPS. Sustainment of MPS includes providing configuration management and control, drafting and publishing of technical documentation, system checkout, fielding, supply, maintenance and repair, training support, customer assistance visits, a twenty‐four (24) hour / seven (7) day a week help line, international support and training, combined test force support, Mission Planning Central (MPC) development and management, deploy and manage the MPS System Support Representatives (SSRs) at worldwide locations, transition to follow‐on systems and support of all wing / unit level planning requirements and related efforts.

1.2 Mission Planning Definitions

1.2.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.2.2 Primary Customer ‐ The provider of requirements / funding for a particular task order on the

Mission Planning Support Contract.

1.2.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.2.4 Hardware – The physical computers and associated peripherals used throughout the mission planning spectrum, as provided by the primary customer.

1.2.5 Software – The computer programs and applications used throughout the mission planning spectrum, as provided by the primary customer.

1.2.6 Mission Planning Environment (MPE) – A compilation of the software, hardware, data, training and logistics required to accomplish mission planning.

1.2.7 Operations Tempo – average number of hours each contractor is intended to work per week

(Monday – Sunday). This is not intended to define the total number of hours required to support mission planning systems at a particular location.

1.2.7.1 Low Operations Tempo – average 20 hours per work week (Monday – Sunday) for each contractor assigned to location.

1.2.7.2 Medium Operations Tempo – average 40 hours per work week (Monday – Sunday) for each

1.2.7.3 High Operations Tempo – average 60 hours per work week (Monday – Sunday) for each

1.2.8 Pricing Table Categories:

1.2.8.1 AF SSR T1‐S – Basic USAF SSR with Information Assurance Technician (IAT) Level 1 certification, Secret clearance required.

1.2.8.2 AF SSR T1‐TS/SCI – Basic USAF SSR with IAT Level 1 certification, Top Secret/Secret

Compartmentalize Information clearance required.

1.2.8.3 AF SSR T2‐S – Basic USAF SSR with IAT Level 2 certification, Secret clearance required.

1.2.8.4 AF SSR T2‐TS/SCI – Basic USAF SSR with IAT Level 2 certification, Top Secret/Secret

Compartmentalize Information clearance required.

1.2.8.5 AF SSR T2‐FL‐TS/SCI – Basic USAF SSR with IAT Level 2 certification, Flight Line access, Top

Secret/Secret Compartmentalize Information clearance required.

1.2.8.6 CAOC SSR T2‐TS/SCI – CAOC SSR with IAT Level 2 certification, Top Secret/Secret

Compartmentalize Information clearance required.

1.2.8.7 TBMCS CAT SSR T2‐TS/SCI – TBMCS Capability Application Trainer SSR with IAT Level 2 certification, Top Secret/Secret Compartmentalized Information clearance required.

1.2.8.8 TBMCS SAT SSR T2‐TS/SCI – TBMCS System Administrator Trainer SSR with IAT Level 2 certification, Top Secret/Secret Compartmentalized Information clearance required.

1.2.8.9 AF AZ SSR T2‐TS/SCI – Assault Zone SSR with IAT Level 2 certification, Top Secret/Secret

Compartmentalized Information clearance required.

1.2.8.10 AF MT SSR T2‐TS/SCI – Mobility Test SSR with IAT Level 2 certification, Top Secret/Secret

Compartmentalized Information clearance required.

1.2.8.11 Army SSR – Basic Army SSR, Secret clearance required.

1.2.9 Non‐Mission Planning Environment (Non‐MPE) – computer hardware, not identified on the certified MPE Letter, which uses mission planning software.

1.3 Scope of Work

The scope of work for the MPSC is any work deemed necessary by the Government to attain the program goals and objectives stated in the following paragraphs.

1.3.1 Program Goals

a. Provide technical expertise, training, support operations, and logistics management for sustained automated mission planning spectrum capability in the operational community.

b. Provide quality workforce that meets Mission Planning System Support Facility (MPSSF) worldwide requirements.

c. Allow for flexibility to incorporate additional mission planning Wing or unit level planning related workload across DoD and international customers.

1.3.2 Objectives

a. Support MPSSF mission accomplishment by continuously adapting services and service levels to meet changing mission requirements.

b. Provide U.S. Government with best value sustainment services for mission planning support.

c. Maintain support throughout the mission planning spectrum.

2 Service Delivery Summary (SDS)

The Service Delivery Summary is composed of two components. The first component includes the MPSC performance objectives which define the services required and are contained in paragraph 2.1. The second component includes the required performance thresholds which define the specific standard of performance.

2.1 Performance Objectives

2.1.1 Mission Planning System Technical Requirements

2.1.1.1 Supported Mission Planning Systems (MPS)

The following MPSs shall be supported by contractor personnel: UNIX‐Mission Planning System (UNIX‐

MPS); Portable Flight Planning Software (PFPS); Joint Precision Airdrop System (JPADS); Joint Mission

Planning System (JMPS); other follow‐on mission planning systems and upgraded systems as they become available. The contractor shall possess knowledge and experience within the following areas:

overall technical support; operational experience; software development, maintenance, training;

logistics support; system administration; configuration control; quality assurance; management. This knowledge and experience applies to all MPSs.

2.1.1.2 Experience – Required Skill Levels

2.1.1.2.1 Required Computer Skills

All contractor personnel shall, at a minimum, have skills in the following current software applications:

FUNCTION SOFTWARE

Operating Environment Windows

Electronic Mail Outlook

Graphics PowerPoint

Spreadsheet Excel

Word Processing Word

2.1.1.2.2 Required Communication Skill Levels

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

2.1.1.3 Security Requirements

All contractor personnel shall obtain security clearances to the proper level required to control classified information (data, manuals, software) to include Top Secret, Special Access Required (SAR) clearances and Communications Security (COMSEC), including Not Releasable to Foreign National (NOFORN), as required, unless otherwise specified by the primary customer. The contractor is responsible for complying with all applicable Department of Defense (DoD), United States Air Force (USAF) / United

States Army (USA), and installation security requirements.

2.1.1.4 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 to the customers.

2.1.2 Overall Technical Support

The Mission Planning System Support Facility (MPSSF), including System Support Representatives (SSRs), has many different roles and responsibilities in the sustainment of mission planning systems. These roles and responsibilities include: user support; training; Combined Test Force (CTF) support; duplication and distribution of software; software support (installation, configuration, troubleshooting, etc.);

administrative support; database development; and logistical support.

Although the overall duties and responsibilities described in the following paragraphs are specific to each area, the mission planning tasks are cross‐functional and cannot be delineated by a particular specialty. Contractor personnel shall be contributing members of various Integrated Product Teams

(IPTs). The contractor shall provide objective performance metrics of current processes and procedures and provide periodic analysis, assessment, and suggest changes to ensure continuous improvement of service to the warfighter. In addition to an individual’s specialty, contractor personnel shall perform duties and responsibilities in related areas, as required.

2.1.2.1 Mission Planning (MP) User Support

2.1.2.1.1 Aircraft Subject Matter Expert (SME) Duties and Responsibilities

The following duties and responsibilities shall be performed:

a. User support shall be provided from 0600‐1800 hours Mountain Time, Monday through Friday with after‐hours on‐call capability (evenings, weekends and holidays).

b. Provide initial deficiency investigation for software and system problems found by the user / test communities and provide problem resolution, which includes but is not limited to forwarding unresolved problems to the appropriate organization. Other examples include logging the problem, duplicating through testing, and analyzing until a resolution is found. Analysis is based upon MP training, experience, various software / system tools or documentation, or other means available. Track the status of the reported problem to closure.

c. Document all validated trouble calls using a centrally accessible tool, currently Mission Planning

Central. If the trouble call results in a Deficiency Report (DR), it must be reported to the appropriate mission planning community members IAW TO 00‐35D‐54.

d. Maintain the centrally accessible deficiency investigation tool, 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. The current metrics include, but are not limited to, number of calls per month, category each call falls under (i.e. platform, T.O., CM), and amount of time calls are open.

e. Assist in the improvement of the user’s MP training as required by the user community.

f. Perform validation / verification of the mission planning products to ensure the user’s requirements were met which includes monitoring accuracy, reliability, performance, security, and other identifiable areas.

g. Support CTF test activities, to include but not limited to, CTF test problems by providing an operational perspective on their MPE. Assist the developers to achieve resolution of reported problem(s) identified during the CTF test activity.

h. Coordinate mission planning software CTF test problem reports, including input of data, coordination with testers on problem details, and boarding of problem reports.

i. Provide feedback on MPEs during development and sustainment activities, which may include but may not be limited to test and hardware evaluation.

j. Training end users on aircraft / mission specific aspects of the MPE (CWDS; CAPS; CAT; A/W/E;

TAWS; etc.).

The contractor shall provide SME support for the following platforms:

a. A‐10

b. F‐22

c. B‐1B

d. F‐16

e. F‐15

f. RC‐135

g. E‐3

h. E‐4

i. E‐8

j. RQ‐4

k. C‐130

l. HH‐60

m. KC‐135

n. KC‐X

o. C‐5

p. KC‐10

q. C‐17

r. U‐2

s. B‐52

t. B‐2

u. MC‐12

v. F‐35

w. JPADS

x. T‐38

2.1.2.1.2 Command and Control, Communications, Computers and Intelligence (C4I) SME Duties and

Responsibilities

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, Theater Battle

Management Core System (TBMCS), Personal Computer Integrated Intelligence and Imagery (PCI3), Target Acquisition Weapons Software (TAWS), Infrared Target Scene Simulation (IRTSS) or any follow‐on mission planning systems, such as the Joint Mission Planning System (JMPS)‐ Solo; C2 Networked Help

Desk 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. Specific duties include, but are not limited to:

a. Maintain files and databases on C4I systems and mission planning interfaces (PFPS, JMPS, TAWS, IRTSS) that contain, as a minimum, milestones, technical issues (e.g. system architecture, compatibility, interoperability, and integration), and lessons learned.

b. Act as primary point of contact for all MPS / C4I systems interface issues.

c. Monitor progress of replacement of Theater Battle Management Core System (TBMCS)‐FL and UL and UL/UC2. Bring problems to the attention of MP team leadership.

d. Periodically brief MPSSF on changes and status in C4I systems.

e. Provide training and user support for UL/UC2, TBMCS, PFPS, TAWS, IRTSS, JMPS‐Solo, Birddog, Personal Computer Integrated Intelligence and Imagery (PCI3), and additional tools.

2.1.2.1.3 Mission Planning Training (MPT) Duties and Responsibilities

The MPSSF shall support the mission planning community with professional training services. Training materials shall be developed in accordance with the USAF’s Instructional Systems Development (ISD) process and delivered by professional, qualified instructors. Training shall be available to mission planners via classes held at centralized training locations (e.g. Hill AFB, UT and Eglin AFB, FL), classes held at unit’s home station, as requested. 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 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 development of other mission planning training material.

Training shall be developed and focused on a weapon system's MPE. The contractor shall have the training package (user and system administration) ready when the MPE enters operational test (OT).

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.

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 MPSC. MPT shall train SSRs and government system administrators in the administration of mission planning systems. MPT shall also train developers and members of the test community, as required, to directly support the development and test process for mission planning

MPEs. MPT shall liaise with members of the Eglin Test Facility (ETF) to ensure necessary support is provided for the testing of MPEs. If SSR duties, for any government customer, are transitioned from contractor to government, the contractor shall provide initial MPE training to those government personnel upon government request. Specific training duties include, but are not limited to:

a. Work with users and software developers to establish a thorough understanding of the components of the MPE.

b. Analyze training requirements of the MPE and build objective‐based modular training. Write syllabi that provide a summary of course content, optimum class structure, time management, and require resources.

c. Develop supporting materials (instructor guides, presentation slides, student exercises, passive and interactive computer presentations, reference guides, etc.).

d. Develop, as requested, a standalone JMPS framework training course, including key Common

Capabilities (CCs), such as weather and threats. The course shall be tailored toward DoD and other Government agencies.

e. For each MPE, develop both a Mission Planning User’s course, and MPE System Administrator’s course.

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

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

h. Based on requirements from the applicable MAJCOM and / or operational units and the advice of the applicable SME, MPT shall be capable of providing training to users and / or SSRs (or other

Systems Administrators) at bases worldwide in‐conjunction with fielding efforts.

i. Deliver training relative to all mission planning software to include local / off‐station classrooms.

j. Maintain web‐based documentation on MPC to provide effective training content and materials for distance learning.

k. Create and utilized feedback instruments for students to report satisfaction with their training experience. Provide contract and Government leadership with feedback data and other reports, as requested.

l. Analyze student feedback to make improvements in course content and presentation.

m. Coordinate with users to arrange facilities and equipment for local and off‐station training;

schedule instructor(s) to support each off‐station training request to include preparation, shipment, and set‐up of MPT‐owned training hardware.

n. Develop and maintain a training support plan specifying mission planning training objectives, resources, and methods. Coordinate plan with DoD agencies, military services and military major commands to ensure that MP training is meeting stated objectives.

o. Maintain a current working knowledge of personal computer technologies, to include hardware, operating system software (client and server), networking, and application software.

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

q. As requested, facilitate the integration of MP training into existing formal military training (e.g.

aircraft replacement training units, intelligence career field technical training).

r. Perform periodic reviews of MP Enterprise training approach and make recommendations to the

Government for continued efficiencies and improvements.

The secondary training audience for MPT will consist of military members and associated government personnel representing the countries under contract for Foreign Military Sales (FMS).

2.1.2.1.4 Estimated Workload

2.1.2.1.4.1 Aircraft and C4I Subject Matter Experts

The contractor is responsible for manning the helpdesk with SMEs from 0600 – 1800 hours Mountain

Time, Monday through Friday with after‐hours on‐call capability, (evenings, weekends and holidays).

This support shall be provided via telephonic and electronic means. The contractor is responsible for providing on‐call support during off hours, 24 / 7 / 365. MPSSF receives an average of 140 calls / emails per month, with each issue taking an average of one (1) man‐hour to resolve. While SMEs are not addressing deficiency investigation calls / emails they shall perform their remaining PWS tasks, within a work week with a medium operations tempo.

2.1.2.1.4.2 MPT

The training schedule shall consist of at least one (1) PFPS course per month, one (1) JMPS course per month and MPS‐UNIX or MPS follow‐on system courses, as required. Each course offering shall accommodate up to 12 students. These courses may be either operator or system administrator courses (depending upon customer needs). The contractor shall support on‐site (i.e., at the customer's location) training throughout the world for United States (US) and international customers.

2.1.2.1.4.3 Fielding

The MPSSF is responsible for supporting approximately 56 individual MPEs. These MPEs currently use

UNIX‐MPS, PFPS and JMPS. Contractor shall field and support these MPEs and / or follow‐on mission planning systems. MPE changes are driven by aircraft Operational Flight Program (OFP) changes, weapon system changes, core changes (UNIX "Core", JMPS "Framework" and PFPS updates), Integrated

Software Modules (ISMs) and Common Capabilities (CCs) changes, etc. This support may include on‐site fielding, migration of old data, and initial or familiarization training for both users and systems administrators. The number of MPS users / bases varies with platforms. With JMPS, many aircraft are planning for nearly annual updates to their fielded MPEs.

At the end of 2010, the following platforms will be fielded on the specified mission planning systems below:

JMPS: F‐15 C/E, B‐1B, RC‐135, F‐16 Blk 40/50, A‐10, and F‐22A

MPS‐UNIX: B‐2, U‐2 and B‐52

PFPS: All others

By the end of 2011, the following additional platforms are scheduled to be fielded on JMPS: E‐3 and F‐16

Blk 30.

By the end of 2012, the following additional platforms are scheduled to be fielded on JMPS: E‐8 and RQ‐

4.

The MPSSF is responsible for maintaining changes in the field to include hardware and software upgrades / modifications.

2.1.2.2 System Support Representatives (SSRs)

This task provides Systems Administration and mission planning spectrum support at Combatant

Command, USAF and USA installations. These system administrators shall be identified as SSRs and serve as representatives of the MPSSF. Additional sites may be identified at a later date based upon evolving mission requirements.

2.1.2.2.1 Basic USAF / Combatant Command SSR Duties and Responsibilities

The following duties and responsibilities shall be performed:

a. Maintain hardware / software configuration management and control of certified and / or

MAJCOM‐ approved MPEs.

b. Maintain hardware / software configuration management and control of other mission planning spectrum applications as approved by applicable MAJCOMs / Combatant Commands, when necessary.

c. Receive and install MPE upgrades, support and aid in disposition of equipment, ensure MPE versions are functional and related systems remain interoperable. Implement 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 should be cognizant of mission planning equipment locations, requisitions of in‐coming mission planning hardware and software releases (includes dropsondes and laptop connection cables). However, 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.

d. Work closely with crewmembers to ensure the MPE supports the mission parameters to meet operational objectives and safety requirements based on technical military knowledge and experience. 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 identified as currently provided system. Support mission planning and mission analysis tasks incorporating weapon system knowledge and expertise, combined with mission planning system expertise and software training, to develop suitable mission solutions as required. Provide feedback to the MPSSF for future incorporation into the helpdesk tool Frequently Asked Questions (FAQs).

e. Establish mission planning spectrum software user account profiles and system defaults, modify access and execution permissions, as required, and implement / refine SPPs. Reconfigure systems to effectively utilize removable components and networked resources.

f. 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). 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), ISMs, Unique Planning Components (UPCs), Aircraft/Weapons/Electronics (A/W/Es), Operating

System (OS), etc.), and maintain software / data configuration control.

g. Analyze software, hardware and system problems found by the user to provide problem identification, resolution and tracking to include logging the problem, duplicating through testing and analyzing until a resolution is found. Analysis shall be performed locally and, when necessary, in conjunction with remote technical support team at the System Support Facility (SSF). Ensure the specific problem details are entered into a centrally accessible tool. Defects shall be managed IAW

TO 00‐35D‐54 and other Enterprise process documents.

h. Provide supplementary MP training for mission planning users, as required. Individual training and classroom training at the assigned location, as required. Integrate mission system capabilities into operational scenarios, as appropriate.

i. Create and deliver technical briefings for mission planning spectrum equipment, software and data for mission planning users, as required by software / hardware updates, etc.

j. Support exercises (e.g. Red Flag, Green Flag), daily operational training missions, deployments and real‐world contingencies, as directed. Deploy worldwide to establish operational mission planning systems, as required. User support for mission planning shall be provided within two (2) hours of initial contact, if the SSR is not deployed with the unit.

k. Maintain control and cognizance over classified data which they may encounter as a result of their support activities. Use of classified data may include, but is not limited to, technical briefings and during deployments as required by the local commander.

l. Set up, conduct and support mission planning spectrum equipment and system demonstrations, as required. Assist with site planning for mission planning activities, as requested, and support site activations (short‐notice, worldwide travel) using US military transportation and / or commercial carrier as directed.

m. Support meetings and generate mission planning related reports, as required.

n. Support Operational Test (OT) events, as required.

o. Support transient mission planning units deployed to the SSR’s location, limiting interference to the primary customer. Prioritization of support is defined by the primary customer.

2.1.2.2.2 Basic US Army Aviation SSR Duties and Responsibilities

The primary duties of the Army Aviation SSRs are to provide support of mission planning systems, which includes PFPS / Falconview, Army Mission Planning System (AMPS) fielded hardware, Electronic Data

Managers, UAS control stations and ancillary systems as designated by the Program Executive Officer‐

Aviation (PEO‐AVN), Product Director Aviation Networks and Mission Planning (PD ANMP). SSRs are not intended to replace knowledgeable mission planning personnel within the unit. Unit members must know how to operate, update, and deploy their mission planning systems without outside assistance.

a. Ensure hardware / software configuration management and control of PEO‐AVN‐defined mission planning systems is implemented.

b. Ensure policies related to hardware / software configuration management and control of other mission planning spectrum applications are in place.

c. Receive and install MPE upgrades, support equipment, disposition; ensure MPE versions are functional and related systems remain interoperable. Implement system Security Practices and

Procedures (SPP) for Automated Information Systems (AIS) utilized for classified (Confidential and

Secret) mission planning purposes. SSRs should be cognizant of mission planning equipment locations, requisitions of in‐coming mission planning hardware and software releases. However, SSRs are not to be utilized as Equipment Custodians for accountable items as 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‐mission planning software.

d. Work closely with crewmembers on a daily basis to ensure the mission planning suite supports the mission parameters to meet operational objectives and safety requirements based on technical military knowledge and experience. Apply advanced technical training and professional expertise in application of computerized Mission Planning Spectrum Support Equipment for aircraft weapon systems requiring Data Transfer Device initialization using specialized software and hardware systems identified as currently provided system. Support mission planning and mission analysis tasks incorporating weapon system knowledge and expertise, combined with mission planning system expertise and software training, to develop suitable mission solutions as required. Provide feedback to the MPSSF for future incorporation into the helpdesk tool Frequently Asked Questions

(FAQs).

e. Assist in establishing user account profiles and system defaults, modify access and execution permissions, as required, and implement / refine SPPs. Reconfigure systems to effectively utilize removable components and networked resources.

f. 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)). SSRs will not generally be designated to perform monthly / periodic updates. Given their rotational nature, these tasks will be the responsibility of the units. However, should a particular visit coincide with the arrival of monthly / periodic updates, the SSR may assist the unit.

g. Responsible for verification of MP distributed media, ensuring deployed systems meet certification requirements for installation / loading of new MP‐related software and tools (Common Capabilities

(CCs), ISMs, Unique Planning Components (UPCs), Aircraft/Weapons/Electronics (A/W/Es), Operating System (OS), etc.), and maintain software / data configuration control.

h. Analyze software, hardware and system problems found by the user at the unit to provide problem identification, resolution and tracking to include logging the problem, duplicating through testing and analyzing until a resolution is found. Analysis is based on MPS technical training provided by product vendors / experts, professional experience, use of specialized software / system tools or documentation and working in conjunction with remote technical support team at the System

Support Facility (SSF). Ensure the specific problem particulars are entered into the Mission Planning

Central (MPC) Enterprise Deficiency Reporting (EDR) or other directed deficiency reporting tool. All

Category I and II DRs entered into the MPC EDR must be reported IAW T.O. 00‐35D‐54, and other

Enterprise process documents, to the appropriate mission planning community members within twenty‐four (24) and forty‐eight (48) hours, respectively.

i. Provide supplementary MP training for force and unit level members, as required. Utilize knowledge of US military tactics and doctrine and technical expertise to integrate mission system capabilities into operational scenarios, as appropriate.

j. Create and deliver technical briefings for mission planning spectrum equipment, software and data for unit personnel, as required.

k. Support unit exercises (e.g. NTC, JRTC), daily operational training missions, deployments and real‐ world contingencies, as directed. Deploy worldwide to establish operational mission planning systems, as required. Deployment of Army SSRs will be handled on a case by case basis through the

MPSSF and PEO‐AVN. Deployments should be scheduled in advance with the SSR, and the other units assigned to that SSR. The advanced scheduling will be at least 45 calendar days in advance, or the deployment will risk not being supported. Additionally, OCONUS deployments require coordination with the PTM and will generally require unit funding. The PTM will pass the request to

PEO‐AVN for final decision. User support for mission planning shall be provided within two (2) hours of initial contact, if the SSR is not deployed with the unit.

l. Maintain control and cognizance over classified data which they may encounter as a result of their support activities. Use of classified data may include, but is not limited to, technical briefings and during deployments as required by unit commander.

m. Set up and support equipment used within the mission planning spectrum and conduct system demonstrations, as required.

n. Assist with site planning for mission planning activities, as requested, and support site activations

(short‐notice, worldwide travel) using US military transportation and / or commercial carrier as directed.

o. Support meetings and generate mission planning related reports, as required.

p. Provide on‐site presence in mission planning areas for technical support and assistance. Support transient units deployed to the SSR’s location, limiting interference to the primary customer.

Prioritization of support is defined by the primary customer.

q. The PTM will create a “Book of Knowledge” (BOK) template. Each SSR will use this template to create a standardized BOK for each assigned unit, detailing location of mission planning systems, configuration information, network names and other information to assist unit members in self‐help and provide continuity between visits and / or with other SSRs.

r. The SSR at the U.S. Army Aviation Center of Excellence (USAACE), Ft. Rucker, AL shall provide direct support to the Concepts and Requirements Directorate (CRD) for operational requirements generation and management, and the Aviation Center Battle labs and the Directorate of Training, Doctrine, and Simulation (DOTDS) on various concept experimentation programs in efforts to digitize the battlefield for Army Aviation. S/he shall serve as the defacto U.S. Army Aviation Mission

Planning Officer for the CRD during those periods when Army personnel are unavailable to perform this function. S/he shall serve as an advisor and counselor to the CRD on matters relating to automated mission planning systems and subsystems, and serve as the PEO‐AVN principal SME regarding the digitization of aviation mission planning for Army Aviation.

2.1.2.2.3 Assault Zone SSR Duties and Responsibilities

The Assault Zone SSR shall have the same duties and responsibilities as a Basic USAF / Combatant

Command SSR. They shall reside in HQ AMC in order to support the Combat Operations Division (AMC

A3D) which owns the Assault Zone program. A3D and the AMC SSR are responsible for providing the

AMC assault zone database and mobility configuration instructions for the Mobility Air Force. Primary

POC for all issues related to the Drop Zone and Landing Zone validation process.

a. The Assault Zone SSR will provide the Mobility Air Force with support for 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. All submitted surveys will be reviewed for accuracy and safety prior to being posted for use by DoD personnel.

b. The Assault Zone SSR is responsible for supporting all Active Duty organizations which require PFPS in order to support the war fighter. Organizations include but are not limited to the 618 Tanker

Airlift Control Center (TACC), US Transportation Command (USTRANSCOM), the AMC Inspector

General’s (IG) Office, and the 375 Air Mobility Wing (AMW).

c. The Assault Zone SSR is responsible for maintaining the FalconView Imagery Server and ensuring all imagery files are current at all times.

d. The Assault Zone SSR will attend conferences/symposiums where the airdrop community is a major participant and present briefings on ZAR related issues.

2.1.2.2.4 Mobility Test SSR Duties and Responsibilities

The mobility test SSR shall have the same duties and responsibilities as a Basic USAF / Combatant

Command SSR but shall reside in AMC / TES to support operational evaluations of mobility mission planning systems. They shall provide the mobility Air Force with support for AMC / TE directed tests and evaluations conducted by AMC / TES.

2.1.2.2.5 Combined Air Operations Center (CAOC) SSR Duties and Responsibilities

The primary duties of the CAOC SSRs are to provide support to the CAOC for the following: Geospatial

Information and Services (GI&S), PFPS software, 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).

a. Coordinate intelligence system requirements with the CAOC/C2.

b. Perform duties 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.

c. Brief system demands on network to the CAOC/C6 and provide system administration duties including control of configuration management of software upgrades.

d. 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 management of Predator Initiative enhancement feeds.

e. Provide support of mission planning systems, which includes PFPS and ancillary 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.1.2.2.6 Theater Battle Management Core Systems – Unit Level (TBMCS‐UL) SSR Duties and

Responsibilities

The SSR(s) shall be a mix of System Administrator Trainers (SAT) and Capability Application Trainers

(CAT). An on‐site training concept shall be used to train all work centers needing access to TBMCS‐UL. If applicable, a “train the trainer” concept can be used where key unit personnel shall be trained by the

CATs and SATs. The key individuals shall, in‐turn, train other unit personnel.

a. Operator training to ensure the operators can effectively utilize the TBMCS‐UL systems (CATs). CATs shall train operators from various unit functional areas in daily procedures. This includes, but is not limited to, wing staff, schedulers, security police, hospital personnel, munitions, duty desk personnel, flight records, maintenance, and SRC.

b. System administrator training, including all aspects of TBMCS‐UL system administration including initial setup, troubleshooting, helpdesk support, and development support as part of the TBMCS‐UL locations worldwide to perform on‐site set / troubleshooting of TBMCS‐UL systems. SATs shall interface directly with TBMCS Configuration Manager, TBMCS Center of Excellence, AC2ISRC, and external organizations / contractors.

2.1.2.2.7 Position Specific Additional Duties and Responsibilities

SSRs may support additional mission planning spectrum systems / databases to include, but not limited to:

e. Briefing Room Interactive (BRI)

f. Patriot Excalibur (PEX)

g. Warfighter’s Egde (WEdge)

h. Beyond Line of Sight‐Situational Awareness Enhancement (BLOS‐SAE)

i. Crew Familiarization Module (CFM)

j. Personal Computerized Debriefing System (PCDS)

k. Commercial Navigation System / Air Traffic Management (CNS/ATM) Database

l. Geospatial Products Library (GPL)

m. Centralized Aviation Flight Records System (CAFRS)

n. Improved Many on Many (IMOM)

o. Combat Support Database (CSDB)

p. Common Mission Debrief Program (CMDP)

q. Order of Battle Management Tool (OBMT)

2.1.2.2.8 Temporary Coverage of SSR Responsibilities

In cases when SSR duties, whether government or contractor, are temporarily interrupted (i.e.

employee termination, resignation, leave, etc), the contractor shall ensure coverage is maintained for units / locations supported. In the case of an absence for a government SSR, the contractor shall provide temporary coverage within 10 calendar days for CONUS or 15 calendar days for OCONUS locations upon request from the government program office. The government estimate for temporary coverage of government SSRs is one location per month for five (5) business days. Temporary coverage for contractor SSRs must begin within 10 calendar days for CONUS locations or within 15 calendar days for

OCONUS locations from the start of the SSR absence. Any temporary coverage for government or contractor SSRs shall include the same duties, responsibilities and minimum qualifications as the position requiring coverage. This includes, but is not limited to, security clearance, DoD 8570.01‐M, Change 2, Apr 2010, Information Assurance certification, general system / platform knowledge, etc.

2.1.2.2.9 Estimated Workload

The number of unit assigned SSRs is defined by the contractor but is expected to meet all requirements of this PWS. It is estimated each SSR in the field shall have either a low, medium, or high operations tempo, as defined in Paragraph 1.2 of this PWS. When supporting exercises or contingencies the work hours may increase. The operations tempo found in the Pricing Table is an estimate of the normal requirement. Use of the time and materials Surge CLIN shall be limited to support, outside of the normal requirement, which could not be anticipated by either the USG or the Contractor. Examples of this include, but are not limited to, preparation for a new wartime requirement and natural disaster response.

2.1.2.3 Logistics Support Requirements

Logistical support includes development and maintenance of technical publications, logistics analysis suitability, supply and provisioning support, hardware support, IT support, configuration management, and systems management of mission planning systems.

2.1.2.3.1 Configuration Management (CM) Duties and Responsibilities

a. Manages MPE deliveries, estimates workload requirements, and acts as the communications and distribution hub for all Mission Planning configuration management related items. The scope of this requirement is to provide communication pathways for elevation of sustainment CM issues and support to the Mission Planning Enterprise.

b. Act as the primary focal point for all Mission Planning CM communications post‐Formal Qualification

Test (FQT) / fielded systems and support enterprise meetings, as required e.g Engineering Review

Boards (E‐ERB) and Configuration Control Boards (E‐CCB) by validating the MPE letters prior to the board meeting.

c. Act as the primary MPSSF focal point for validation / verification of MPE configuration and control.

d. Research any fielded software and hardware incompatibility issues and establish baselines.

Contractor shall work with the base Software Control Center (SCC) to assign Computer Program

Identification Numbers (CPIN) to MPE software.

e. Manage and validate the configuration of MPE letters IAW Enterprise MPE Letter Process throughout a system’s lifecycle, duplicate post‐FQT software (as identified on the appropriate MPE letter) and distribute the MPE via appropriate means to internal and external agencies.

f. A member of CM shall be designated as the sustainment Screening Point IAW T.O. 00‐35D‐54; one primary and at least one alternate to ensure coverage. Screening Points shall review all new DRs for their impact on fielded systems, paying particular attention to high priority DRs IAW T.O 00‐35D‐54.

g. With Government oversight, the Contractor shall research, facilitate and document the evaluation of high priority and sustainment Deficiency Reports (DRs) within the DR management system via the sustainment deficiency review board process

h. Monitor the life cycle status of software to be released. Generate the release package for duplication and distribution to the field on receipt of distribution letter. On a case‐by‐case basis, when an MPE certification is imminent and there is a need to expedite the release of a MPE, the contractor could be directed by the government to prepare the release package, to include acquiring the CPIN

i. Maintain currency of the CM library within the centrally accessible tool. This includes entering all data, software, and documentation received by the MPSSF.

j. Maintain and track mission planning software and documentation library, including logging and filing incoming information (data, media, official documentation), informing mission planning personnel of library additions, locating requested information, maintaining archives, and periodically purging obsolete information.

k. ACPINS – CM shall use the Automated Computer Program Identification Number System (ACPINS) to determine which users are on requirement for specific software. Knowing who is on requirement for specific software is key to distributing scheduled software updates and urgent patches as required.

l. CM shall be responsible to duplicate and distribute MPE test packages to the appropriate test agencies by test start date. These test packages may be a combination of CD‐ROM, DVD, floppy discs, 4mm tape, and hard drives. Future distribution via the Internet is also envisioned. CM shall work with the appropriate Subject Matter Expert(s) to ensure that the media being sent to the test agencies installs properly prior to shipment.

NOTE: Contractor must be aware and follow Hill AFB mailroom deadlines. This is especially important when shipping classified software.

2.1.2.3.2 System Technical Support Duties and Responsibilities

a. Act as the primary focal point for all Mission Planning hardware communication for fielded systems and the communications hub for all Mission Planning hardware related items. Elevate hardware issues to the Enterprise and the MAJCOMs; briefings / communication to fielding team members in support of fielding; briefings / communication to MPSSF management and teams with regards to current and future systems.

b. Support the internal and Enterprise‐level processes such as Risk Management and Engineering

Control Boards.

c. Act as the primary focal point for logistics support of proposed mission planning hardware. Duties include but are not limited to:

1. Travel to support enterprise meetings and other meetings that require hardware support such as fielding events, and acceptance Inspections for quality control with a vendor before asset delivery.

2. Provide necessary personnel to assist MAJCOMs with Hardware Requirements definition and candidate system evaluations for replacements / modifications to fielded systems.

3. When and where directed by the Mission Planning SPO, conduct first article inspections for new hardware and evaluate the physical configuration of the new hardware for conformance with applicable AF / DoD requirements

d. Prior to fielding, the Contractor shall support other teams, i.e. Government, MPSC Configuration

Management and Technical Publications as needed for hardware support and ensure the configuration and associated documentation is correct for the fielded systems and participate in fielding of new systems as needed to include, but not be limited to training Systems Support

Representative / Communication Squadron members on setup and maintenance of new hardware as needed.

e. Participate with hardware deficiency investigation, and resolve issues with fielded systems, solve end user issues, provide conduit for communications between warranty vendor and end users for warranty work on systems. Document deficiency investigation calls / tickets in appropriate tool and provide analysis of call data such as trends and recommendations to government representatives of systems / components that are reaching end of useful lifecycle.

2.1.2.3.3 Estimated Workload

The MPSSF is responsible for maintaining approximately 56 independent MPEs and is subject to change.

MPEs typically go through periodic updates. MPEs range from 15‐45 individual pieces of media.

Common types of media used are: CD‐ROMs / DVDs / 4‐mm tapes / 3 ½ inch disks. There are three (3)

MPE baselines: UNIX‐MPS, PFPS and JMPS. In all cases, Technical Orders (TOs) / Time Compliance

Technical Orders (TCTOs) shall be reviewed, updated, and rewritten as necessary. The software and documentation shall be grouped together into either test or certified packages for distribution to the appropriate organizations.

2.1.2.3.4 Technical Publications (Tech Pubs)

2.1.2.3.4.1 Technical Publications Duties and Responsibilities

Technical Publications is responsible to develop and modify Mission Planning, Technical Orders (TOs), Time Compliance Technical Orders (TCTOs), and supporting documentation for USAF Mission Planning systems per applicable directives. Technical Publications shall:

a. 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,…