PWS_DA13.pdf

Performance Work Statement Data Analysis 13

Bldg 706 72 TES Whiteman AFB 9 July 2024

1.0 SCOPE/General Description

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

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 Requirements

Proposed Tasks for DA13 Flightline Maintenance and Employment Provide the 72 TES the ability to analyze and plot developing trends and issues from the data gathered during flight. Provide the ability to automatically archive the necessary data in the appropriate archive folder with a standardized naming convention. Sustain contractor developmental information system (IS) to CORE to ensure access to data analysis to 72 TES personnel.

The Contractor will 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.

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

Contractor shall continue development of the FLTS GUI, including at a minimum any actions taken during the Data Analysis 13 (DA13) Technical Interchange Meeting (TIM) held at the contractor facility that were deemed mandatory. 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.

Contractor shall account for additional support as required including one Mission Data File (MDF) delivery, one TIM at each of the following locations; Las Vegas, Nevada, and Kansas City, Missouri, and one operator or maintainer training session in Nashua, NH.

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

5.0 Period of Performance

Contractor shall perform installation on the system during regular working hours (0730-1600) only on weekdays excluding Federal Holidays or Whiteman AFB down days without prior coordination. If events like weather or Air Force exercises prevent compliance with that timeline personnel in Bldg. 706 will be contacted as soon as possible. All work will be conducted in Bldg.

706 72TES. Date and time will be set up between the contractor and security personnel in Bldg.

706.

6.0 Operational Security

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.

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.

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 identified by 509 OSS will be marked and handled appropriately as FOR OFFICIAL USE ONLY (FOUO). 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.