Performance Work Statement (PWS) for

Road Weather Information System (RWIS)

Maintenance

Rev 4 dated 27 April 2026

Revision History

Date Reason for Changes Revision No.

11 September 2025 Base contract award 3

27 April 2026 Adds upgrade of the second RPU and installation of three additional sensors

Commented [TF1]: Continue to update this date until document is final so that we can keep track of edits.

Commented [TF2]: Continue to update this date to align with document date in title.

1.0 Scope

The Road Weather Information System (RWIS) at Wright-Patterson Air Force Base

(WPAFB) consists of proprietary equipment and software. Through a series of atmospheric sensors and sensors buried in the runway pavement, data is collected by

Remote Processing Units (RPUs) which transmit the data over radio to a Central

Processing Unit (CPU). The CPU converts the data which is displayed in tables, charts, and maps. The information provided to the CPU displays the surface temperature and provides the chemical factor of the runway pavement at the sensors. Sensors indicate whether dry, wet, chemicals, or presence of ice. Using this data, new pavement freezing temperatures can be calculated through algorithms contained in the software. The atmospheric sensors record and maintain the history of pavement surface conditions. The hardware/software for this system is licensed by Vaisala Inc.

There are currently seven (7) sensors located on runway (RWY) 05L/23R which collect the runway surface condition information that relay real time information back to one of the two (2) RPU sites located on the airfield. Each RPU site house contains one (1)

Vaisala LX model motherboard which collects all seven (7) sensor readings and transmits real time data back to the main server located in England and provided to the Government through a web-based program called Navigator 2.0. Navigator 2.0 is being phased out and will be replaced by WX Horizon. The Vaisala LX RPUs have exceeded their expected end of life and replacement parts are no longer available.

The scope of this contract includes a base year (nine months) and four (4) option years of data management and preventative maintenance services, the upgrade of two (2) RPUs from the LX to RWS200 system, and the installation of three (3) in-pavement sensors on the smaller parallel runway (runway 5R/23L)

2.0 Period of Performance

This contract will have a period of performance of a nine (9) month base year from approximately 30 September 2025 through 31 May 2026, as well as four (4) 1-year

Option Years to follow with twelve (12) month period of performances from 1 June to 31 May each respective year.

The period of performance for the upgrade of the RPU systems and installation of three

(3) sensors is six months from contract execution to project completion.

3.0 Requirement

The contractor shall install two (2) in-ground pavement sensors and one (1) in-ground subgrade sensor into runway 5R/23L at locations coordinated with 88 Operations Support

Squadron Airfield Management personnel. One (1) sensor will be located on the North end of the runway and be connected to the North RPU. The remaining two (2) sensors will be located on the South end of the runway and connected to the South RPU.

The contractor shall upgrade the two (2) RPUs from LX to RWS200 hardware reutilizing the currently installed infrastructure as much as possible.

The contractor shall provide extended warranty coverage for the duration of the contract for the RWIS hardware only. The current LX RPU specific hardware is not included in the extended warranty coverage due to exceeding end of life however the RWS200 would be covered after installation. All initial repair service will be handled by 88 OSS/OSM personnel. This contract shall include one (1) annual preventive maintenance visit each year. The cost of labor and installation are at the government’s expense for any in-ground installation work and any costs related to visits exceeding the one (1) annual preventative maintenance visit.

The contractor shall provide an upgrade from the existing Navigator Data Management and Communication (Navigator) system to WX Horizon. This shall include one (1) virtual training session and one (1) on-site training session.

The contractor shall provide the cellular charges to communicate with the two (2) server sites. Contractor shall provide technical support and monitor the Data Management system (Navigator or WX Horizon) twenty four hours a day, seven days a week (24/7).

Contractor shall immediately reset and troubleshoot system and notify the user of status or situation. Catastrophic failure shall be addressed immediately. If contractor determines equipment failure, parts shall be identified and shipped to 88 OSS/OSM for installation.

a. Replacement Parts, Tools, and Instruments: Only new standard parts or parts equal in performance to and interchangeable (without alteration) within new parts shall be used in performing repairs. Installed and replaced parts shall become property of the

Government.

b. Point of Contact: The Contractor shall identify a single Point of Contact for service calls.

c. Contractor Response Time: The Contractor shall respond to all service requests by telephone notification/acknowledgement within 24 hours after the call is placed. The

Contractor shall assist in maintenance trouble-shooting and repair of equipment via telephone within the first 24 hours. If contractor is unable to troubleshoot and assist 88

OSS/OSM in resolving the issue, contractor shall respond for a reactive on-site repair visit within five (5) business days.

4.0 Special Requirements

Software Maintenance: The contractor shall keep current on all software updates issued by Vaisala Inc and notify 88 OSS/OSAM and OSS/OSM when software updates are issued. The Contractor shall maintain data updates via remote locations. Onsite will be maintained by OSS/OSM personnel at the direction of contractor. Notification shall include description of change and recommendation if it should be installed. The

Contractor shall implement software updates. Installed software updates become property of the Government.

Commented [TF3]: Extended warranty language is already included

5.0 Installation Access

a. Security Clearance: Requirement for security clearance is not anticipated. If, however, security clearance is determined to be necessary, the Contractor shall ensure that maintenance personnel complete all security forms (personal history, fingerprint card, and other applicable details) within thirty (30) calendar days following notification of the requirement from the Government.

b. Laws and Regulations: All contractor personnel performing work under this contract shall comply with all applicable Federal, State, and local laws, as well as all Air Force and local regulations. Of specific concern are regulations regarding security, wearing of badges, access lists, and safety.

c. Contractor Access: Subject to security regulations, the Government will permit the

Contractor access to the equipment to be maintained.

d. Delivery Procedures for Commercial Vehicles: All vehicles larger than a large pick-up truck are required to be inspected by the Wright-Patterson Air Force Base

Commercial Vehicle Delivery Gate (CVDG) prior to entering the Installation.

Vehicles to be inspected include, but are not limited to, the following:

1. Step van/panel truck

2. Tractor/trailer, box and flat-bed containing cargo

3. Tanker trucks

4. Box trucks

5. Tour buses

6. Garbage/recycled waste trucks

7. Concrete trucks/mixers, dump trucks

8. Cranes, recreational vehicles, petroleum tanker

This inspection will be conducted at Gate 26A located off State Route 235. The following are exemptions to vehicles utilizing the CVDG:

If the vehicle has the product inside (concrete and asphalt trucks) and timely delivery is necessary due to product deterioration, it does not need to enter the CVDG. To bypass the CVDG, the contractor shall submit a list containing drivers’ names, social security Numbers, and the state in which the driver's license is held for those drivers who will be entering the base. This shall be accomplished 24 hours prior to requested entry time. If entry is requested on Monday, this list must be submitted by Friday at

1630 hours. All lists shall be submitted to the 88th ABW/CE Directorate contract inspector. The only gates that may be used under this exemption shall be 15A, 26A, 38A, and gate 1B. If the driver's name is not on the list, he/she will not be allowed access to the installation through these gates and the base will not assume liability for denied access. If a delivery vehicle must exit, and then re-enter the base to complete its route, the vehicle shall be resealed upon exiting the base. After initially passing through the commercial vehicle delivery gate, trucks shall be resealed at Gates 15A, 38A and 22B. The resealing of the trucks will allow them to continue to any other area of the installation (Areas A, B, or Kitty hawk) without reprocessing through the

CVDG. To receive resealing assistance, the drivers shall physically stop at one of the three authorized gates and request the installation entry controller to reseal their truck and provide the next location of their delivery. The controller will reseal the truck and give the delivery driver a pre-clearance form. The driver shall present the pre-clearance form to the entry controller at the next point of installation entry. This reentry can be through any base gate.

Vehicles maybe subject to an inspection at any of installation entry control points during a directed random antiterrorism measure (RAM). Any commercial vehicle, regardless of size, can be directed to the CVDG at the discretion of the installation entry controller.