APPENDIX A - ASOS Software Baseline Management SOO V2.pdf

APPENDIX A

National Oceanic and Atmospheric Administration (NOAA)

National Weather Service (NWS)

STATEMENT OF OBJECTIVES (SOO)

for

Automated Surface Observing System (ASOS)

FY25 - FY30 Software Baseline Management

V.2

1. Purpose:

Programmatic objectives for this requirement are to allow the Vendor maximum flexibility to innovatively manage the projected schedule, performance, risks, warranties, subcontracts, and data to provide the goods or services that satisfy the government’s performance requirements. This requires a tailored approach to meet the specific program needs below. The ASOS Program Office requires ASOS 2.0 hardware and software integration of new sensors over the next five years and needs operating system licensing and node management for the Campbell Scientific Inc (CSI) ASOS system to support operations and maintenance during the same period.

2. Mission:

As a primary support component for surface weather observations at approximately one thousand locations, ASOS provides air traffic management of the current weather conditions in support of the national airspace, safety of the flying public and Navy, Marine Corps, and Army operational airfields. The surface weather observation is a crucial component of day to day operations at these locations. The absence of ASOS observations at a location can delay flight operations, prevent air traffic from landing or taking off and cause second and third order effects that prevent passengers and cargo from reaching their final destinations on schedule, precipitate economic consequences or worse in the case of contributing to an aircraft mishap.

3. Period and Place of Performance:

The period of performance will be five years beginning upon contract award. Services will be performed at the vendor’s facility and at the NWS Sterling Field Support Center (Sterling, VA) as requested by the government. Vendors may participate in Government Validation and Verification activities during the first article acceptance process. Deliverables will be in the form of Software updates and engineering changes.

Software version updates for changes to the baseline AERO application shall be based on ASOS Program

Management Committee (APMC) approved software baseline requests for change. Server operating system licensing and support services renewal shall be provided. Deliverables shall be in the form of documented software updates for baseline synchronization between the government and the OEM vendor.

All services provided shall use the vendor’s engineering development model.

4. Background:

As an operational system in the field for nearly 30 years, ASOS failure rates are increasing, system outages are lasting longer and replacement equipment is suffering from Diminishing Manufacturing Sources and

Material Shortages (DMS/MS) making it more difficult to procure and deliver parts to effect repairs.

Original Equipment Manufacturer (OEM) vendors for the current sensor array have announced end of lifecycle support for some ASOS sensors with more coming. Numerous sensor obsolescence and end of life support from OEM vendors manifests itself in the form of increased operational sensor failure rates and ASOS component attrition. These sensor obsolescence issues are secondary to the deterioration of the data processing and dissemination technology ASOS uses that was developed in the 1980’s.

The ASOS is undergoing a service life extension to extend the systems lifecycle beyond 2040. A phased approach to the upgrade is underway and includes the replacement of the data collection, system processing and dissemination subsystems in addition to all sensors on the sensor group. The ASOS program requires Hardware and Software support services for the operations and maintenance of the

Campbell Scientific Acquisition Control Unit, Data Collection Package, and the Single Cabinet

(ACU/DCP/SCA). The ASOS Program is in the midst of sensor replacement projects that require hardware and software integration into the new CSI systems while under warranty. The sensor HW/SW upgrades to

ASOS are treated as system baseline changes approved by the APMC for the continued service life of the system for the Departments of Commerce, Transportation and Defense.

5. Performance Objectives:

With the introduction of a FISMA Moderate security posture across an end-to-end high availability network with redundant embedded controllers running Red Hat Enterprise Linux (RHEL) Server at each

ASOS site, the program must account for and manage approximately 1,514 RHEL server license instances globally.

The Vendor shall provide the ASOS PMO with documented software baseline updates based upon approved requests for change. The baseline updates to software which shall be provided in accordance with Mil Spec 31000 & ASME 14.1 and enable the government to update its baselines under configuration management. Comprehensive release notes describing the baseline changes shall be provided.

In the case of RHEL Server licensing and support renewal, no lapse in licensing or support can occur and must be transparent to the government in execution.

6. Deliverables / Schedule:

Written milestone deliverables are required in draft form within 15 calendar days from date declared in the approved project plan provided by the vendor. The government shall have 14 days to review the draft formatted deliverable for comments whereupon the final delivery shall occur NLT 30 calendar days after government comments are formally received. The final version of the deliverables, as stated in ‘Tables 6.2

& 6.3’, shall be delivered within 30 days of government comments. All written deliverables shall be phrased in layperson language.

6.1. Annual RHEL Licenses:

The table below is an estimate of the number of RHEL Licenses to be renewed based on the first year paid for by CSI and when the ASOS Program will pick up RHEL licensing costs.

Table 6.1 Annual RHEL License renewal

Key Deliverables

Item No. Deliverable Objective Due

Maximum of 50 RHEL

Server License

Renewals

Manage the RHEL server license subscription renewal transparent to ongoing operations permitting continuous ASOS operations at all

ASOS 2.0 sites during FY24

Upon expiration of the preceding year’s license subscription

Maximum of 200

RHEL Server License

Renewals

Manage the RHEL server license subscription renewal transparent to ongoing operations permitting continuous ASOS operations at all

ASOS 2.0 sites during FY25

Upon expiration of the preceding year’s license subscription

Maximum of 800

RHEL Server License

Renewals

Manage the RHEL server license subscription renewal transparent to ongoing operations permitting continuous ASOS operations at all

ASOS 2.0 sites during FY26

Upon expiration of the preceding year’s license subscription

Maximum of 1400

RHEL Server License

Renewals

Manage the RHEL server license subscription renewal transparent to ongoing operations permitting continuous ASOS operations at all

ASOS 2.0 sites during FY27

Upon expiration of the preceding year’s license subscription

Maximum of 1514

RHEL Server License

Renewals

Manage the RHEL server license subscription renewal transparent to ongoing operations permitting

Upon expiration of the preceding year’s license subscription

Item No. Deliverable Objective Due continuous ASOS operations at all

ASOS 2.0 sites during FY28

6.2. Operating System Update Mechanism

Management of the ASOS RHEL nodes requires controlling software for the purpose of installing

Operating System Security and system software patches, at each ASOS site. This capability can include firmware upgrades of system components capable of receiving firmware upgrades. This would be germane to the Ansible playbook approach to systems administration at each ASOS site.

Operating system security updates shall be tested and approved for release in accordance with

FISMA moderate baseline and NOAA IT Security requirements for timely security patching.

Table 6.2 Operating System Update Mechanism

Item

No.

Deliverable Objective Due

Project Plan

Draft

A draft, comprehensive scope and schedule to fulfill software integration efforts containing the deliverables in this table.

Immediately upon notification of a security path requirement.

Project Plan

Final

A final, comprehensive scope and schedule to fulfill software integration efforts containing the deliverables in this table.

5 days after receiving the comments from the government

RHEL

Operating

System Security

Patch

Test report and formal recommendation from the implementation of a security patch issued by Red Hat describing any performance anomalies in the fully implemented and tested security path issued from Red Hat on the CSI ASOS EDM.

Based on the priority of the security patch issued by Red Hat and corroborated by ASOS

ISSO

Software

Release Notes

A comprehensive summary of the software changes germane to the integration of the new sensor sufficient to accommodate information needs for training and education of technicians and operational users.

Based on the priority of the security patch issued by Red Hat and corroborated by ASOS

ISSO

Software User

Manual Update

Provide operators and maintainers germane, salient changes to the baseline software interfaces. All changes to the software user manual germane to the software operations for both users and maintainers.

Based on the priority of the security patch issued by Red Hat and corroborated by ASOS

ISSO

Installation instructions &

Modification

Note

Enable the efficient installation of the newly integrated sensor by field technicians. Step by step instructions on how to effect the installation of the hardware and software to achieve an updated ASOS system in the field. Any and all steps needed to achieve the baseline upgrade for both hardware and software.

Uninstallation of legacy sensors need not be covered in these instructions.

Based on the priority of the security patch issued by Red Hat and corroborated by ASOS

ISSO

Factory

Acceptance

A formal, written procedure that validates the baseline changes to both hardware and software to prove out that the ECNs

Based on the priority of the security patch issued by Red Hat and

Item

No.

Deliverable Objective Due

Testing

Procedures affected function with the OEM baseline engineering model.

corroborated by ASOS

ISSO

Compliance

Testing

Summary

A summary of test procedures and results performed by engineering or compliance that are not covered by the FAT to demonstrate completion of developmental testing is complete.

Based on the priority of the security patch issued by Red Hat and corroborated by ASOS

ISSO

FAT Test

Results

Demonstrate the FAT test result output satisfies the operating system functions as designed on the ASOS integrated system.

Based on the priority of the security patch issued by Red Hat and corroborated by ASOS

ISSO

6.3. All other Software Applications Update Mechanism

Updates to the AERO software and all other software applications germane to the ASOS will require system compatibility testing for functionality before they can be accepted into the baseline and put into the production environment. The Vendor shall provide this in accordance with ‘Table 6.3’ requirements.

Table 6.3 - Other Software Update Mechanism

No.

Deliverable Objective Due

Project Plan

Draft

A draft, comprehensive scope and schedule to fulfill software integration efforts containing the deliverables in this table.

5 days from task start

Project Plan

Final

A final, comprehensive scope and schedule to fulfill software integration efforts containing the deliverables in this table.

10 days after receiving the comments from the government

AERO

application software bug fixes

Test report and formal recommendation from the implementation of an AERO software update issued by Campbell

Scientific describing any performance anomalies in the fully implemented and tested software update on the CSI ASOS

EDM.

Within 60 calendar days of bug identification

Software

Release Notes

A comprehensive summary of the software changes and the components of the application that are needed to understand the changes sufficient to accommodate information needs for training and education of technicians and operational users.

With the ECN for

Government approval

Engineering

Change Notice

A formal request to change the software baseline to synchronize the configuration managed baselines between the government and the OEM.

With the ECN for

Government approval

Software User

Manual Update

Provide operators and maintainers germane, salient changes to the baseline software interfaces. All changes to the software user manual germane to the software operations for both users and maintainers.

With the ECN for

Government approval

Deliverable Objective Due

Installation instructions &

Modification

Note

Enable the efficient installation of the newly integrated sensor by field technicians. Step by step instructions on how to effect the installation of the hardware and software to achieve an updated ASOS system in the field. Any and all steps needed to achieve the baseline upgrade for both hardware and software.

Uninstallation of legacy sensors need not be covered in these instructions.

With the ECN for

Government approval

Factory

Acceptance

Testing

Procedures

A formal, written procedure that validates the baseline changes to both hardware and software to prove out that the ECNs affected function with the OEM baseline engineering model.

With the ECN for

Government approval

Compliance

Testing

Summary

A summary of test procedures and results performed by engineering or compliance that are not covered by the FAT to demonstrate completion of developmental testing is complete.

With the ECN for

Government approval

FAT Test

Results

Demonstrate the FAT test result output satisfies the design requirements of the integrated sensor.

With the ECN for

Government approval

Updated AERO

Software

Release

Fully tested and delivered AERO software update with the new code, drivers, features, configurability and processing for the dissemination of baseline software weather products identified in the data distribution algorithm.

With the ECN for

Government validation and verification

6.4. Tasks and Associated Deliverables:

Timely submission of deliverables is essential to successfully completing this requirement. Schedules for deliverables for all items enumerated in section 6.1, 6.2 & 6.3 of the SOO shall be spelled out in the approved project plan at project inception. All deliverables shall be prepared and submitted according to format, content, and schedule described in the SOO.

6.5. Reporting Requirements:

The Vendor shall provide monthly written progress reports for the duration of time it takes to deliver data items of section 6.1, 6.2, & 6.3 of this SOO. All reporting requirements are required digitally and shall not be delivered in hard copy. The progress report shall cover all work completed during the specified period and shall present the work to be accomplished during the subsequent period. This report shall also identify any problems that arose and a statement explaining how the problem was resolved. This report shall also identify any problems that have arisen but have not been completely resolved and provide an explanation.

Table 6.5 - Reporting Deliverables

Deliverable/

Item Title

Description

Frequency

Reference

Delivery

Format

Due By

1 Combined

Monthly

Status Report

Monthly report documenting tasks and issues identified during the month

Once per

Month

Ref. SOO, section 6.1, Section 6.2 and Section

6.3

Via email to

COR, PM,

CHENG

The first wednesday at

1200 ET each month after contract award

2 Monthly

Status

Meeting

Meeting with PM, CHENG, COR briefing the

Combined Monthly

Status Report

Once per

Month

Ref. SOO, section 6.1, Section 6.2 and Section

6.3

PDF

package via

Teams, Meet, in person etc.

The second

Wednesday at

1200 ET each month after contract award

7. Operating Constraints: In accordance with NWSI 60-703 MAY 12, 202, security patches required by the government have suspense timelines within the security patch that must be effected to the systems based upon the severity of the implied risk to the systems.