DA Requirements PWS dated 6 Oct 2025 Draft.pdf

Performance Work Statement Data Analysis Requirements

Bldg 706 72 TES Whiteman AFB 6 October 2025

1.0 SCOPE/General Description

Continue support of the war fighter through future development data analysis services including software development, data analysis, systems engineering, ground support, and analysis tools, and ground support tools, as well as design services for systems and tools to facilitate data analysis, ground support, and analysis tools. Support of the war fighter through development and use of those models in flight line support equipment. Develop a path forward to meet requirements of data analysis of war fighter environment. Maintain necessary expertise for moving forward with the data analysis effort utilizing software and data contributing all aspects of systems data to ensure data analysis portrays the required picture of real time scenarios of systems utilizing truth data. Utilize data analysis, and truth data output to provide confidence that the warfighter will satisfy the objectives required to accomplish the mission.

1.2 Period of Performance. The Period of Performance (PoP) shall be one base year of 12 months and four 12-month option years for a total period of five years. Extensions up to six months at the end of this period of performance may be determined to be in the best interest of the Government. See FAR 52.217-8. The award document will call out the PoP and is the definitive performance period.

1.3 Work Requirements. Work requirements are outlined in this Performance Work Statement (PWS) and will be further detailed by the issuance of individual Task Orders.

2.0 Non-Personal Services

The government shall neither supervise contractor employees nor control the method by which they perform the required tasks. Contractor personnel will be escorted into the required areas to complete the work. The contractor will coordinate any requirements with security personnel in Bldg. 706, 72TES security personnel.

3.0 Task Order Process

3.1 Request for Proposal (RFP). As the need exists for performance under the terms of this contract, the Contracting Officer, or his/her authorized representative, will notify the Contractor of a new requirement by issuance of a written Request for Proposal (RFP).

3.1.1 The RFP will indicate the date and time of request, proposed period of performance, and description of services. The Contractor will receive a statement of work (SOW) further describing the requirement. This SOW could include, but not limited to, the description of work including or other information necessary to execute the requirement as applicable.

3.1.2 Upon establishing the scope of the individual requirement, the Contractor shall then prepare a fully detailed proposal to complete the requirement based on the contract line items

(CLINS).

3.1.3 The time allowed for submittal of the Contractor’s quote for individual requirements will be specified in each RFP but will be 30 calendar days unless otherwise stated. All proposals must be on Contractor letterhead.

3.1.4 Negotiation. Upon receipt of the Contractor’s proposal, the Government will review the proposal for completeness and accuracy. The Contracting Officer or authorized representative will negotiate with the Contractor the appropriateness of the selected CLINS, the quantities and measurements, and the period of performance. These negotiations can take place in person, by conference call, or via email.

3.1.5 After negotiations and upon agreement on a project cost and period of performance by the Contracting Officer or his/her authorized representative, the Contractor shall provide the Contracting Officer with one (1) electronic copy of all agreed upon line items and quantities.

3.2 Task Order (TO). After negotiations are complete, and the Government and the Contractor have agreed to the CLINS, the quantities and measurements, price and period of performance, the Contractor shall be issued an individual TO for the requirement. The Contractor will then be issued a Notice to Proceed (NTP) by the Contracting Officer or his/her authorized representative. This NTP will state the agreed upon period of performance, and the Contractor will be required to complete all work within that stated period, to include all submission and approval of submittals, and delivery of all materials.

3.2.1 Communication. The Contractor shall keep the Government informed of any changes in work schedule, environmental conditions, or other conditions that could affect the contractor’s performance or completion of the TO.

4.0 Requirements

The Contractor shall provide tasks per the RFP for tasks as described below.

4.1 Proposed Tasks. The Contractor shall provide the 72 TES the ability to analyze and plot developing trends and issues from the data gathered during flight.

• Software Development - Be able to develop software to support development of new capabilities for ground support and analysis tools

• Data Analysis - Preform data analysis of existing test data

• Systems engineering - Perform system engineering in support of data analysis, ground support and analysis tools

• RF engineering - Perform RF engineering in support of data analysis, ground support and analysis tools

• Design - Perform design of systems and tools to support data analysis, ground support and analysis tools.

4.2 Port Flightline Test Set (FLTS) Graphical User Interface (GUI) to be hosted on the platform Linux environment, and implement action items from the Lab Demonstration of the GUI software. Modify the FLTS GUI to be able to exercise platform’s System Under Test (SUT) for the emulation and archival of SUT performance. If directed to ship and demonstrate the FLTS at WAFB, create a draft User’s Guide for the FLTS as well as draft Test or Demonstration Procedure and, if different than the demonstration procedure, a checkout procedure so the unit may be validated in the field. Conduct a field or lab demo of the FLTS software and capture any redlines and feedback.

4.3 Development of the FLTS GUI. Final state of the FLTS shall be captured via demonstration with an optional customer audience. Customer will be notified of final demonstration 30 days in advance. Artifacts will include the submission of a final report capturing demonstration results.

4.4 Identify and procure a suitable commercial rackmount personal computer (PC) for hosting the Flight Line Test Set (FLTS) Graphical User Interface (GUI) and controlling the FLTS Integration, Verification and Validation (IV&V) test equipment. Contractor shall identify and acquire a prototype flight line suitable transit case to host the computer, keyboard, pointing device, and display for operator use. Contractor shall identify and procure the cabling between the transit case with the PC and the IV&V test equipment. Contractor shall provide drawings and/or photos showing the intended installation and orientation of the equipment in the transit case.

4.5 Create and deliver artifacts in support of delivering a Body of Evidence (BOE) for government creation and approval of an Authorization to Operate (ATO) for the FLTS System.

The Body of evidence shall include the following; Draft System Security Plan (SSP), Draft Risk Assessment Report (RAR), Draft Plan of Actions and Milestones (POAM), Draft Architecture Analysis Report (AAR), and Draft Security Controls Traceability Matrix (SCTM). Deliverables shall be in Microsoft Office electronic format, suitable for editing upon receipt.

4.6 Clean up action items from the Lab Demonstration of the FLTS hardware and software.

Complete a drawing package for the hardware and draft and execute a build procedure for the GUI. Create a User’s Guide for the FLTS as well as an Acceptance Test Procedure (ATP) and a checkout procedure so the unit may be validated in the field. Conduct a field demo of the FLTS hardware and software and capture any redlines and feedback.

4.7 Sustain contractor developmental information system (IS) to CORE to ensure access to data analysis to 72 TES personnel.

4.8 If directed to ship and demonstrate the data analysis products at WAFB, create a draft User’s Guide for the developed software/tools, as well as draft Test or Demonstration Procedure and, if different than the demonstration procedure, a checkout procedure so the software may be validated in the field. Conduct a field or lab demo of the software and capture any redlines and feedback.

4.9 Contractor shall provide necessary cyber and physical security support required to maintain approvals required for CORE and Video Teleconferencing (VTC) capabilities established during Data Analysis 12 contract.

4.10 Contractor shall account for additional support as required including one Mission Data File (MDF) delivery, one Technical Interchange Meeting (TIM) at each of the following locations: Las Vegas, Nevada, and Kansas City, Missouri.

4.11 Training may be requested by local organizations as well as organizations outside the local area requiring personnel to travel TDY. Training material used shall be provided to the Contracting Officer Representative (COR) as well as the government entities that received the training.

5.0 Deliverables

Deliverables required will be specified per each RFP. These may include but are not limited to monthly reports of number and type of hours worked. Document Formats. Documents, plans, reports, etc., will be provided electronically using Microsoft Office products to the CO/CA unless forms already exist in Adobe Acrobat PDF format.

6.0 Primary Contact Person/CM

The Contractor shall notify the CA and CO of any changes to the Contractor’s primary point of contact within 2 business days.

7.0 Security and Safety

Contractor shall wear appropriate security badges, line badges, identification and/or name tag as required by the security procedures of the squadron where performance takes place. Contractor personnel shall meet established unescorted installation entry requirements pursuant to AFI 31- 101 before base identification will be issued. Contractors shall submit requests for installation identification to 72 TES security personnel. Personnel not meeting the minimal standards will not be issued an installation pass and will not be allowed access to the installation. The contractor will provide employee information for an entry authorization listing to gain entry onto the base strictly for the time period of the work to be accomplished. The information that needs to be provided will be Full Name, Social Security Number, Date of Birth, Driver’s License Number, State, .and citizenship.

8.0 Operational Security

8.1 Purpose. The following information provides Operations Security (OPSEC) guidance to Government Contractors and subcontractors awarded Government contracts at Whiteman AFB.

Government Contractors are provided this guidance to ensure compliance and protection of critical information that may be a threat to national security. All OPSEC briefs and updates will be conducted by 72TES security personnel after arrival at 72TES and before performing necessary duties.

8.2 Definition. OPSEC is a methodical process to identify Critical Information (CI), identify threats to that CI and the related vulnerabilities and risks of exploitation to that CI, and identify, develop, and implement countermeasures to protect that CI. CI is specific facts about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment. CI includes those facts, which individually, or in the aggregate, reveal sensitive details about US Government, i.e. Whiteman AFB or the contractor’s security or operations related to the support or performance of the Statement of Work (SOW)/Performance Work Statement (PWS), and thus require a level of protection from adversarial collection or exploitation not normally afforded to unclassified information. OPSEC supplements, but does not replace traditional security practices such as Physical Security and Information Security.

OPSEC is essential to ensure the initial and continued success of our mission, operations, systems, and procedures.

8.3 OPSEC Applicability. The 509 OSS OPSEC Program Manager has determined that additional safeguards are essential for this contract, and imposes OPSEC as a requirement in the responsibilities of this contract. During the course of this contract, in addition to those restrictions, instructions and guidelines defined in the contract Statement of Work and/or other references provided the contractor will adhere to the following minimum requirements in support of the 509 OSS OPSEC Program. Introduction of personnel electronic devices into government spaces, laptops, tablet PCs, cellular phones, cameras, recording devices, and data recording/storage devices is STRICTLY controlled and forbidden in some areas of Whiteman AFB. Photography and recording is not allowed except for official use and by permit only.

(Unless otherwise stipulated in the contract). Contractor personnel shall not discuss government operations in public or over unprotected or unencrypted communications. Official business, controlled unclassified information may only be transmitted as directed in the SOW/PWS. The Contractor shall not post to company websites, publications, newsletters or other media any images, data or information that reveal sensitive government operations, personnel, equipment, and/or classified or controlled unclassified information, refer to paragraph (d) below. When in doubt, company press releases related to this contract should be coordinated through the 509th Contracting Office. Because observation of events, operations, physical changes, etc. may reveal National Security information, specific restrictions are needed to preclude unintentional release of this information to unauthorized parties. (Unauthorized disclosure and transfer of National Security Information is punishable under 18 USC § 793.) Therefore, contractor personnel shall not disclose to unauthorized third parties, post to unofficial sites (including Social Networking sites) any images, data or information, or observed events that reveal sensitive government operations, personnel, or equipment. Government issued badges, identification shall be removed and/or concealed from plain sight when off station and shall not be left in vehicles or unprotected. Badges and passes may not be duplicated or copied or loaned to others. Lost or stolen identification badges, vehicle passes etc. will be immediately reported to the 509th Security Forces LE Desk at (660) 687-3700. Practice OPSEC and implement countermeasures to protect CI and other sensitive unclassified information and execution of military operations performed or supported by the contractor in support of the mission. Protection of CI will include the adherence to and execution of countermeasures which has been provided by the 509 OSS. It is strongly recommended the contractor mark and protect related internal production schedules, deliverables, inventories and shortages and identified vulnerabilities related to production of government material. Internal company markings e.g., Business Sensitive, etc., are appropriate for identifying the aforementioned as sensitive information. Specific Government-provided information, drawings etc., will be protected in accordance with guidance in applicable paragraphs of the SOW. Destroy (burn, shred, etc.) critical and/or sensitive unclassified information no longer needed to prevent the inadvertent disclosure and/or reconstruction of this material. Critical information(CI) identified by 509 OSS will be marked and handled appropriately as Controlled Unclassified Information (CUI). Government CI includes but is not limited to: known or probable vulnerabilities to any U.S. system and their direct support systems, details of information about military operations, unit, vessel, aircraft movements/arrivals, missions and exercises, etc.

10.0 Example Template Bid Schedule

Region Bid Codes

Job Code

Job Description 2025 2026 2027 2028 2029

Job Category 1 XI Job 1 XII Job 2

Job Category 2 XIII Version B Job 1 XIV Version B Job 2