2027 PWS MPST 8 May 2026_mPDF.pdf

CUI

Performance Work Statement

Mission Planning Support Tools

72nd TES Whiteman AFB

8 May 2026

1.0 Mission

The Mission Planning Support Tool (MPST) is utilized by the 72d Test & Evaluation Squadron (TES) at Whiteman Air Force Base (WAFB). The required effort includes in-person and remote maintenance and support of the MPST system.

1.1 Scope

No tasks described within this Performance Work Statement shall be construed as inherently governmental. To ensure compliance with federal regulations regarding contractor support, the following limitations apply:

System & Data Validation: While the Contractor shall perform testing and provide performance data, the Government retains the absolute authority to officially verify, validate, and accept all mission planning databases, algorithms, and software.

Capability Representation: The Contractor shall propose technical models, but the Government is solely responsible for determining and certifying that those models accurately represent aircraft capabilities.

Assessment Metrics: The Contractor may draft and recommend metrics or assessment products; however, the Government retains the exclusive authority to approve the final criteria used to evaluate systems and mission effectiveness.

The Contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision and other items and services necessary to perform MPST maintenance and support services as defined in this PWS both at Whiteman AFB and remotely.

1.1.1 The contractor shall provide MPST database and software maintenance to ensure compatibility with upgrades to the B-2 Mission Planning System (MPS) software, hardware and databases or to USAF/DoW standardized Information System (IS) workstation configurations. The contractor shall also provide MPST database and software maintenance to accurately represent new and/or improved aircraft capabilities, and to correct errors and address limitations encountered during operational use. Activities shall include, but are not limited to:

Installing and verifying MPST software releases

Developing and maintaining 72 TES custom databases and software

Verifying MPST databases and algorithms

Providing demonstrations and training on MPST capabilities

Participation in meetings and working groups that impact mission planning processes or databases used in the MPST

1.1.2 The contractor shall support the operational use of MPST modeling and simulation capabilities to address 72 TES requirements. These activities include, but are not limited to

Conducting modeling and simulation studies

Reviewing or generating mission planning system inputs

Developing metrics and products for assessments

Generating briefings and reports for MPST evaluations

Performing pre-test predictions and post-test analysis with the MPST

Participating in open-air flight test activities

Validating MPST databases and algorithms

Attending meetings related to B-2 testing, mission planning and survivability

Delivering Monthly Status Reports detailing activities and any problem areas

1.1.3 The Contractor shall provide MPST distribution support on-site and at Temporary Duty (TDY) locations as needed. The software produced under this contract is Government-owned, and the Government retains all distribution rights. All distribution, support, and travel must be approved and coordinated with the Contracting Officer's Representative

(COR).

1.1.4 The contractor shall provide software upgrades to meet 72 TES requirements, including integrating new features available in the modeling and simulation engine, Suppressor or Advanced Framework for Simulation, Integration, and Modeling (AFSIM).

1.1.5 The contractor shall maintain the MPST software baseline, associated documents, and training materials.

1.1.6 The Contractor shall provide support for MPST installation, configuration, and training.

This involves installing MPST software, configuring existing databases for use in the MPST, and providing user training to enable other organizations at Whiteman AFB to use MPST as an interface to Suppressor or AFSIM. Support will be needed in both on-site and off-site locations.

1.1.7 The Contractor shall provide dedicated information system administration support as part of this contract. This requirement is necessary because newly developed software requires extensive operating system compatibility and interoperability checks before delivery. The Contractor will perform these functions to ensure all software arrives fully functional for Government use. This role must be part of the contract to enable troubleshooting of operating system and compatibility issues on the Contractor's side, preventing such problems from affecting Government systems. The Contractor will also provide support for the Modeling & Simulation Flight and its facility. Responsibilities include maintaining computer systems in accordance with approved security procedures through activities such as:

Maintaining user accounts and monitoring network and user access.

Performing computer system audits, security updates, and digital file transfers.

Upgrading or replacing system components.

Reporting security-related incidents to the Information System Security Officer

(ISSO).

Installing approved software, security patches, and deploying operating system upgrades.

Performing installation and verification testing for MPST upgrades.

2.0 Non Personal Services

The Government shall not supervise contractor employees or control their method of performance. The contractor is responsible for managing its employees and guarding against any actions that could be perceived as personal services. The contractor must immediately notify the Contracting Officer (CO) if it believes any such actions are occurring.

2.1 Business Relations

The contractor shall employ qualified personnel with the appropriate combination of education, training, and experience to accomplish all work.

2.1.1 Identification of Contractor Employees: All contractor must identify themselves as such in meetings, when answering Government telephones, and in other situations where their status is not obvious. The Contractor shall ensure all documents or reports they produce are marked as Contractor products or that their participation is appropriately disclosed. An employee's "Contractor" status shall be predominantly displayed in all correspondence, including email signature blocks.

2.1.2 Contractor Required Identification: Contractor personnel shall wear identifying badges at all times. Although no specific dress code is required, they are expected to maintain a professional appearance, which extends to their personal workspace in government facilities.

3.0 Requirements

All Contractor personnel shall possess the computer programming skills required to fully support MPST software maintenance. Personnel must have a minimum of two years of operational experience working as or directly with aircrew. They must be trained as necessary on the latest and upcoming version of MPST. Personnel shall also be familiar with B-2 aircraft capabilities, survivability, ground and airborne threat systems, and intelligence products for B-2 mission planning. They must be able to successfully leverage the modeling and simulation capabilities of the MPST to meet 72 TES requirements and provide a timely response (within one business day) to all support requests.

4.0 Security and Safety

The Contractor shall wear appropriate security and line badges as required by the security procedures of the squadron where work is performed. Contractor personnel shall use company-owned or privately-owned vehicles for transportation on the installation and must meet unescorted installation requirements per AFI 31-101. Requests for installation identification must be submitted to the 509th Security Forces Squadron (SFS) at least 72 hours prior to requiring entry. Personnel not meeting the minimum standards will be denied access. The Contractor will provide employee information for an entry authorization list, in accordance with Whiteman AFB Security Forces instructions and any applicable REAL ID Act requirements. Information may include full name, Social Security Number, date of

4.0.1 On-site Contractor personnel must have a current, adjudicated background investigation and be eligible for access to Top Secret, SCI, and SAP information as required. The Contractor must also have the required facility clearance issued by the Defense Security Service. Security requirements are specified in the DD Form 254. The 72 TES Program Security Manager (PSM) will locally manage program access and clearances for Contractor personnel.

5.0 Period of Performance

On-site Contractor support is expected to be performed during regular working hours (0730 1600) on weekdays, excluding Federal holidays and Whiteman AFB down days.

Any on-site support required outside of regular hours will be coordinated with the COR.

The primary on-site work location will be Building 706, 72nd TES. The Government will provide office supplies, appropriate workspace, and access to unclassified and classified computer networks and databases as required.

5.0.1 Travel to Whiteman AFB (for off-site personnel) or other facilities may be required and. will be coordinated with the COR.

5.0.2 Travel to TDY locations requires pre-approval from the COR. Trip reports must be submitted within 5 business days after completion of travel.

6.0 Operational Security (OPSEC)

Purpose: This section provides OPSEC guidance to contractors and subcontractors to ensure the protection of critical information (CI).

Definition: OPSEC is a systematic process used to identify CI, analyze threats and vulnerabilities, assess risks, and implement countermeasures to protect information related to friendly intentions, capabilities, and activities. Unauthorized disclosure of CI could lead to mission failure. OPSEC supplements, but does not replace, traditional security disciplines.

Applicability: The 509th Operations Support Squadron (OSS) OPSEC Program Manager has determined that this contract requires additional safeguards. The Contractor shall adhere to the following minimum requirements:

The introduction of personal electronic devices into government spaces is strictly controlled and may be forbidden in certain areas.

Photography and recording are prohibited without an official permit.

Contractor personnel shall not discuss government operations in public or over unencrypted communications.

The Contractor shall not post to any media (websites, publications, etc.) any images or information that reveal sensitive government operations, personnel, equipment, or classified/controlled unclassified information. All company press releases related to this contract must be coordinated through the 509th Contracting Office.

Government-issued identification shall be concealed when off-station and must not be left in unprotected areas. Lost or stolen identification must be immediately reported to the 509th Security Forces at (660) 687-3700.

The Contractor shall implement countermeasures provided by the 509th OSS to protect CI. It is strongly recommended that the Contractor mark and protect internal production schedules, deliverables, and inventories as sensitive information (e.g., "Business Sensitive").

All critical and sensitive unclassified information shall be destroyed (e.g., shredded) when no longer needed to prevent inadvertent disclosure.

CI identified by the 509th OSS will be marked and handled as Controlled Unclassified Information (CUI). This includes, but is not limited to, system vulnerabilities and details of military operations, movements, and missions