Attachment_J.1_-_Statement_of_Objectives_-_Amendment_0004.pdf

NATIONAL OCEANIC AND

ATMOSPHERIC ADMINISTRATION

(NOAA)

EA133W-15-RP-0044

U.S. DEPARTMENT OF COMMERCE

NATIONAL OCEANIC AND ATMOSPHERIC

ADMINISTRATION

NATIONAL WEATHER SERVICE

THE ADVANCED WEATHER INTERACTIVE

PROCESSING SYSTEM

STATEMENT OF OBJECTIVES

JULY 08, 2015

ACQUISITION AND GRANTS OFFICE

EASTERN ACQUISITION DIVISION

NORFOLK, VIRGINIA

ATTACHMENT J.1 – STATEMENT OF OBJECTIVES AMENDMENT 0004

SECTION C: STATEMENT OF OBJECTIVES (SOO)

1. OBJECTIVE

The intent of this Statement of Objectives (SOO) is to support the acquisition of Operations and Maintenance (O&M) services, hardware, software, communications, and architecture improvement services for the Advanced Weather Interactive Processing System (AWIPS).

AWIPS supports the Department of Commerce (DOC), National Oceanic and Atmospheric

Administration (NOAA), and the National Weather Service (NWS) mission for the protection of life, property, and the enhancement of the national economy. It is not the intent of the Government to provide detailed requirements or to describe how the work is to be accomplished. The Offeror shall use the information contained herein to propose a technical solution that addresses the goals and objectives described in this SOO in a Performance

Work Statement (PWS). Innovative solutions that will improve NOAA’s ability to deliver services efficiently, effectively and economically is highly encouraged. The contractor shall also use this SOO to develop a Quality Assurance Plan (QAP). The QAP shall specify the performance measurements to be applied to the Contractor’s effort, along with positive and negative incentives associated with successful or unsuccessful performance, to support the

NWS in accomplishing its organizational mission and program objectives.

2. OVERVIEW

NOAA/NWS (hereinafter referred to as NWS) requires a performance based contract for the

O&M and Product Improvement services for AWIPS. It is fundamental to this effort that the contractor understands that the Information Technology (IT) and related services required under this contract provide an important role in AWIPS program business functions. In addition, the performance-based arrangement provides that the Contractor's payment and incentives are based on meeting service levels necessary to efficiently, effectively, and economically support the NWS in the execution of its responsibilities.

The Contractor shall bring a mission focus that provides highly effective, secure, reliable management, and IT services along with a solid understanding of NWS provided services.

These services include, but are not limited to, providing forecasts, observations for the water, land, all levels of the atmosphere, and the sun. These forecasts and observations are tailored for diversity (weather, population, demographics), and include traditional areas such as severe weather, winter weather, tropical weather, aviation, “routine” weather, space weather, and tsunami. The Contractor shall also continuously identify methods to improve AWIPS which translates to improving NWS’s ability to execute its mission. The Contractor shall also identify methods to improve the NWS's ability to execute its mission throughout the performance of the contract. The NWS will use a best-value approach for this procurement, emphasizing a stable cost environment while maintaining or reducing the amount of risk to the AWIPS program.

AWIPS is a complex system with many users and stakeholders, and has a Federal

Information Processing Standards (FIPS) 199 security categorization of “High.” As such, the

O&M, development, Information System Security, and IT services are of critical importance.

3. AWIPS BACKGROUND AND CONCEPT

The first AWIPS contract, which defined the development, deployment, operation, and maintenance of the AWIPS system, was awarded in 1992. The development of the original

AWIPS system was completed in June of 1999, and was capable of supporting operations and full deployment to 141 NWS offices. The AWIPS system was first base-lined in August

2000. The current AWIPS prime contract was awarded on August 17, 2005. The AWIPS system is currently deployed at one hundred twenty-two (122) Weather Forecast Offices

(WFOs), thirteen (13) River Forecast Centers (RFCs), six (6) NWS Regional Headquarters

(HQs), eight (8) National Centers (NCs), and at a small number of test and training locations.

In addition, an AWIPS workstation is provided to the twenty-one (21) Center Weather

Service Units (CWSUs) across the country. A complete listing of current AWIPS sites is accessible online at:

https://vlab.ncep.noaa.gov/web/awips-technical-library/home

The AWIPS program installed two (2) AWIPS installations (e.g., operational and developmental) at each of the Tsunami Warning Centers (TWC) and will be installing two (s) installations (e.g., operational and developmental) at the National Water Center (NWC).

The AWIPS system as a whole consists of several high performance graphics workstations and servers at each location, linked in a high-availability configuration with a hybrid satellite terrestrial communication network. The hardware baseline consists of three (3) unique configurations which support the WFOs, RFCs, and NCs. The RFC and NC configurations contain additional servers necessary to support the expanded domain of these field offices and in the case of the NC configuration the additional data processing needs. The NC configuration is also located at two (2) WFOs (Honolulu, HI and Anchorage, AK) to support the quasi-national center requirements at these two (2) locations. The WFO configuration is installed in support of the TWCs and the RFC configuration at the NWC.

AWIPS has an extensive architecture that implements highly available, secure data communications, processing, meteorological, and hydrologic display capabilities in an integrated environment that supports an integrated field structure to enable the operational missions of the NWS and NOAA. The AWIPS program support NWS mission goals as well as NOAA and DOC strategic goals. Consequently, the efficient and effective operation and continuous improvement of the AWIPS system are critical to meeting these goals.

In the current environment, each AWIPS installation ingests observation, sensor, model data input, and processes this data into weather products, allows forecaster interaction in product creation, and disseminates these products to the public and specific stakeholders. The concept of operations may vary from day-to-day, based on the active weather concerns, and AWIPS system status (normal, degraded, service backup [SvcBU]). The concept of operations may also vary between each AWIPS site due to specific local forecast concerns or organizational mission of each site where AWIPS is deployed, and due to the use of local applications at each location within the AWIPS framework.

https://vlab.ncep.noaa.gov/web/awips-technical-library/

AWIPS must maintain the highest level of availability, throughput, and data quality in order to effectively complete its mission. The principal components of AWIPS are:

3.1.Network Control Facility (NCF)

The NCF manages the operational usage of AWIPS across the nation. The NCF provides monitoring and corrective activities for the operational hardware, software, and communications. The NCF is staffed 24/7 and provides troubleshooting services via a help desk function to the forecasters throughout the NWS. The NCF also provides central computing necessary to support SvcBU, collaboration, data delivery, and other capabilities. In addition, the NCF provides support for site upgrades of hardware and software. The primary NCF is located in Silver Spring, MD with the backup facility located in Fairmont, WV.

3.2.Communications

3.2.1. NOAAPort/NOAA Weather Wire Service

Point-to-multipoint satellite broadcast network that provides communications from the NCF to all NOAAPort and NOAA Weather Wire Service (NWWS) users to distribute weather model, satellite imagery, and most other NWS observational, forecast, and warning information. NOAAPort, or the Satellite

Broadcast Network (SBN), provides a critical data feed to other Government and private sector customers. A separate channel supports NWWS distribution of forecast and warning information to the NWWS users.

3.2.2. Wide Area Network (WAN)

Terrestrial network designed to support the distribution of point-to-multipoint data among all AWIPS sites. This data includes products, messages and observation and forecast data generated or received by local AWIPS offices from systems external to AWIPS, such as the Automated Surface Observing System, Next Generation Doppler Radar, and Upper Air Observation Systems. The WAN provides an infrastructure for an AWIPS site to provide backup support for other

AWIPS sites if an operation failure occurs. AWIPS currently uses Government furnished terrestrial telecommunication services.

3.2.3. Very-small Aperture Terminal (VSAT) WAN Backup (Fly Away Kit)

This capability provides connectivity to the NCF during a major communications outage via a deployable VSAT. These kits must be pre-deployed to locations where there is a high risk of a major communications outage due to extreme weather conditions or other circumstances. Dedicated satellite space segment is provided for up to four (4) deployments during a given year. In addition, this capability supports the Radar Operations Center sending remote radar data to the

WFO.

3.2.4. Local Area Networks (LAN)

Establishing local communications at NOAA and NWS sites, the LAN provides concurrent transmission of data at 1000 Megabits per second (Mbps). The workstations, data servers, and applications servers utilize a 1000 Mbps environment. All other equipment (printer, communications processors, text displays, etc.) also concurrently utilize a 1000 Mbps environment.

3.3.Software

The current AWIPS software baseline contains approximately 8 million lines of code with over 2 million lines of code from legacy applications. The AWIPS software baseline has been developed within a Service Oriented Architecture (SOA). AWIPS software baseline has been designed to be reliable, efficient, maintainable, flexible, modular, and extensible. New capabilities are being added to the AWIPS software baseline multiple times each year. The baseline software release number is Software Version Document

(SVD) OB14.4.1. The entire contents -- listing, actual source code, development environment, installation instructions, etc. can be found on the AWIPS Technical

Library. AWIPS software runs on a RedHat Enterprise Linux platform while a portion of it, the Thin Client software, also runs on Windows operating system (OS). The software baseline does not include local applications developed by the operational units, which are the responsibility of the Government.

The NWS requires the AWIPS software baseline to remain essentially a non-proprietary software package for the following reasons:

a) It allows our partners, such as government laboratories, academia, and others, to use and add value to the software for scientific and technical improvements without concern for safeguarding any proprietary code.

b) It allows for the potential for other government users to utilize the software for their missions.

c) It allows open commerce for use in niche markets in need of this type of capability.

This requirement does not include existing third-party software platforms and applications needed to allow AWIPS to operate, such as the underlying operating system, or any capabilities used by AWIPS for NWS-specific architecture or infrastructure needs.

3.4.Hardware

Commodity hardware has enabled NWS to use the NOAA logistics infrastructure, including the National Logistics Support Center and National Reconditioning Center.

AWIPS hardware is warrantied and on a continuous (staggered) refresh cycle which is typically five (5) years depending on the hardware component.

AWIPS, as the cornerstone of a modernized NWS, must continue to evolve to accommodate new science and technology to meet NWS, NOAA, and DOC strategic goals. Continued improvements in the areas of hardware, software, and communications shall be required to avoid system obsolescence.

4. GOALS AND PERFORMANCE OBJECTIVES

Meeting the objectives of a system in a highly data-dynamic environment represents a substantial task. The NWS has made extensive investments in modeling techniques, satellite instrumentation, surface and upper air observation capabilities, and radar detection improvements to bring forecasters the data and information required to improve forecast accuracy and warning lead times.

The Government Performance and Results Act (GPRA) of 1993, (found at https://www.whitehouse.gov/omb/mgmt-gpra/gplaw2m) requires the NWS to improve

AWIPS throughput, add new and improved science and technologies, and exploit more accurate and higher resolution data and weather forecast model information. AWIPS must be enhanced in order to continue to meet or exceed the GPRA goals and objectives. In addition, AWIPS must continue to evolve to ensure alignment with other NWS and NOAA architectures and continue to be extensible to other potential missions in the Federal

Government.

4.1.AWIPS Program Objectives

4.1.1. Establish a stable (uniform and consistent) cost model that sustains high quality

O&M services while introducing new technology and capabilities to support evolving NWS needs and requirements.

4.1.2. Provide 24/7/365 O&M support to all NWS operational sites, including the one hundred twenty-two (122) WFOs, thirteen (13) RFCs, eight (8) NCs, two (2)

TWCs, twenty-one (21) CWSUs, the NWC, and six (6) regional HQs.

4.1.3. O&M and security support shall meet or exceed the Service Level Agreements

(SLAs) specified in Table – 1 Mandatory and Table – 2 Mandatory but subject to adjustment, below.

4.1.4. Provide IT solutions that are compliant with security requirements as defined in paragraph 4.3 below. In the event that any of the security requirements change over the period of performance of the contract, the solution shall also include identification, evaluation of impact on AWIPS and the proposed remediation.

4.1.5. Implement and maintain mechanisms to enhance, manage, and maintain AWIPS baseline software to meet or exceed the SLAs in Table – 1 Mandatory and Table –

2 Mandatory but subject to adjustment, below. Currently, the AWIPS baseline software includes all software and scripts necessary to build, execute and support the system including AWIPS specific applications, Commercial-Off-the-Shelf

(COTS), Free and Open-Source Software (FOSS), and Operating System (OS) software. All software furnished under the AWIPS contract must be extensible, so that it is readily expandable, well documented, and updated regularly through interactions with the larger research community. It is the Government’s intention https://www.whitehouse.gov/omb/mgmt-gpra/gplaw2m that the AWIPS baseline software will be made available to users on an “open source” basis, however it intends to exercise complete rights to the data, including ownership rights as stated below, to ensure the success of its program. Only certain commercial data and software currently used on the AWIPS system listed in the Request for Proposal clause H.21 Section 4 or expressly accepted by the

Contracting Officer (CO) in writing will be utilized by the Government subject to limited rights. The Government has unlimited rights and ownership to all data and associated documentation produced or delivered under this contract. All data and documentation includes but is not limited to the source code of any software produced under this contract, executables, related scripts needed to build, test, execute, and run the AWIPS software, utilities, documentation, deliverables, and reports, and shall be Government owned and the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the

Government. This software and related materials may not be used or sold by the

Contractor without written permission from the Government Contracting Officer

(CO). All materials supplied to the Government shall be the sole property of the

Government. These data rights are necessary to enable a smooth transition to another provider as necessary, to ensure continuity of service in the event of contract termination, or upon contract re-competition.

4.1.6. Maintain interoperability with other NWS and Government systems to support

AWIPS operations, including, but not limited to, communication systems, observation systems, satellite systems, radar systems, and modeling and data systems. A list of such known systems may be found in the AWIPS Technical

Library at https://vlab.ncep.noaa.gov/web/awips-technical-library/home.

4.1.7. Establish necessary governance, processes, work flows, and tools via NWS

Virtual Lab (VLab) (https://vlab.ncep.noaa.gov) as the integrator of AWIPS baseline software, and provide an AWIPS development and test environment that supports distributed and collaborative development and testing of AWIPS software amongst the contractor, NWS, Government and other Government organizations; such as Labs in NOAA’s Office of Oceanic and Atmospheric

Research, National Aeronautics and Space Administration, and collaborative partners including but not limited to academia. Any required and recommended changes to NWS VLab governance, processes, work flows, and tools shall be implemented via the AWIPS program and VLab management. Changes must be approved by the AWIPS Program Management Office (PMO).

4.1.8. Develop an implementation plan that reduces the AWIPS hardware footprint such that the proposed solution meets or exceeds the established SLAs in Table – 1

Mandatory and Table – 2 Mandatory but subject to adjustment, below, improves

SvcBU and Continuity of Operations, secures existing remote intra-AWIPS access, drives towards Government initiatives such as the 2010 Federal Data

Center Consolidation Initiative (available online at https://cio.gov/wp-content/uploads/downloads/2012/09/FAQ-May-2012-Update-V1.pdf), and https://vlab.ncep.noaa.gov/web/awips-technical-library/home https://vlab.ncep.noaa.gov/ https://cio.gov/wp-content/uploads/downloads/2012/09/FAQ-May-2012-Update-V1.pdf https://cio.gov/wp-content/uploads/downloads/2012/09/FAQ-May-2012-Update-V1.pdf reduces system downtime during installations, while minimizing operational risks, data latency, and required up-front investment.

4.1.9. Develop an implementation plan for the AWIPS architecture that allows the users to visualize data required for the mission that is anticipated to increase by a magnitude of at least 12 while meeting or exceeding the SLAs in in Table – 1

Mandatory and Table – 2 Mandatory but subject to adjustment, below. This would include, but is not limited to, gridded model data, radar data, satellite data, lightning data, the National Digital Forecast Database (NDFD), and locally ingested data.

4.1.10. Develop an implementation plan to significantly reduce the AWIPS Discrepancy

Report (DR) backlog without sacrificing the support for current operations and newly discovered DRs. The plan shall also detail how the Contractor plans to reduce the DR inventory. Current list of AWIPS DR backlog is located on the

AWIPS Technical Library at https://vlab.ncep.noaa.gov/web/awips-technical-library/home.

4.1.11. Maintain open source nature of AWIPS including, but not limited to, source code, executables, related scripts, utilities, documentation, deliverables, and reports by providing appropriate data rights and use agreements, as well as enable a smooth transition to another provider, to ensure continuity of service in the event of contract termination, or upon contract re-competition. These rights and agreements shall include language which allows the Federal Government to freely distribute AWIPS software and related materials described above to its partners and any other interested parties. The AWIPS full data rights shall be provided to include all scripts and software needed to build, test, configure, execute, and run the software. Only certain commercial data and software currently used on the

AWIPS system listed in the Request for Proposal clause H.21 Section 4 or expressly accepted by the Contracting Officer (CO) in writing will be utilized by the Government subject to limited rights.

4.1.12. Develop approach to continually enhance the AWIPS baseline (e.g., hardware and software) such that AWIPS evolves to meet the emerging requirement of the

NWS over the life of the contract.

4.1.13. Develop a Transition Plan that describes an approach to perform an orderly three

(3) month transition-in and an orderly three (3) month transition-out of the period of performance for this contract.

4.1.14. Utilize subcontract and teaming arrangements effectively under the Small

Business Program, Federal Acquisition Regulation (FAR) Part 19.

https://vlab.ncep.noaa.gov/web/awips-technical-library/home https://vlab.ncep.noaa.gov/web/awips-technical-library/home

4.2. DOC, NOAA, and NWS Strategic Goals and Objectives

NOAA/NWS has the responsibility to provide data and products that form a national information database used by other Government agencies, the private sector, the public, and the global community.

The successful Offeror shall not only exhibit the ability to meet or exceed the performance goals and objectives for the AWIPS program, but also design a solution that considers and supports the following higher level strategic goals and objectives:

4.2.1. DOC Strategic Objectives

The DOC’s strategic objectives may be accessed online at:

http://www.commerce.gov/sites/default/files/documents/2014/march/doc_fy2014-

2018_strategic_plan.pdf. They include:

4.2.1.1.Objective 3.1: Advanced the understanding and prediction of changes in the environment through world class science and observations.

4.2.1.2.Objective 3.2: Improve preparedness, response, and recovery from weather and water events by building a Weather-Ready Nation.

4.2.1.3.Objective 3.3: Strengthen the resiliency of communities and regions by delivering targeted services to build capacity.

4.2.1.4.Objective 4.1: Transform the Department’s data capacity to enhance the value, accessibility and usability of Commerce data for Government, business and the public.

4.2.1.5.Objective 4.3: Collaborate with the business community to provide more timely, accurate, and relevant data products and services for customers.

4.2.1.6.Objective 5.1: Strengthen organizational capabilities to drive customer-focused, outcomes-driven mission performance.

4.2.2. NOAA Strategic Objectives

The Agency’s strategic objectives may be accessed online at http://www.ppi.noaa.gov/, and include:

4.2.2.1.Reduce loss of life, property, and disruption from high-impact events

4.2.2.2. Evolve NOAA’s weather services to become more effective, efficient, and agile.

4.2.3. NWS Strategic Objectives

The NWS’s strategic objectives may be accessed online at http://www.nws.noaa.gov/com/weatherreadynation/, and include:

4.2.3.1.Improve weather decision services for events that threaten lives and livelihoods.

http://www.commerce.gov/sites/default/files/documents/2014/march/doc_fy2014-2018_strategic_plan.pdf http://www.commerce.gov/sites/default/files/documents/2014/march/doc_fy2014-2018_strategic_plan.pdf http://www.ppi.noaa.gov/ http://www.nws.noaa.gov/com/weatherreadynation/ http://www.nws.noaa.gov/com/weatherreadynation/

4.2.3.2.Improve sector-relevant information in support of economic productivity

4.2.3.3.Enable integrated environmental forecast services supporting healthy communities and ecosystems

4.2.3.4.Sustain a highly skilled, professional workforce equipped with the training, tools, and infrastructure to meet our mission.

4.3.AWIPS IT Security Requirements

The Contractor shall remain proactively vigilant throughout the life of the AWIPS contract with respect to existing, emerging, anticipated, and evolving threats, and shall alert AWIPS program management to any potential impact upon the AWIPS system or its components, providing proposed mitigation as well as the cost and projected schedule for implementation.

All current security requirements and specifications are delineated in Attachment J.3 -

Contract Data Requirements List dated July 08, 2015, which is provided in the solicitation/contract.

5. CONSTRAINTS

NOAA and NWS, and therefore the successful Contractor, are constrained by the following requirements:

5.1.For the purposes of this acquisition, the Government will provide terrestrial WAN telecommunications to the Offeror with constrained bandwidth. The typical WFO has 768 kbps or half of a T1 circuit dedicated to AWIPS.

5.2.For the purposes of this acquisition, the Offeror must separate the SBN from the other parts of the overall O&M contract, and track and cost it independently in the Work

Breakdown Structure, since the SBN component may transition to another contract during the period of performance of the AWIPS contract.

5.3.The Contractor shall adhere to NOAA/NWS configuration management and change request policies and procedures

5.4.The NWS will not be able to make accommodations for any additional facilities (e.g., IT equipment, office space, telephones, desk space, etc.) for the AWIPS contractor onsite at

Government-owned or Government-leased properties, beyond those already in use by the

24/7/365 help desk and maintenance support personnel at the AWIPS Network Control

Facility (ANCF), the Backup Network Control Facility (BNCF) and the Silver Spring, MD facility. See Attachment J.8 - Government Furnished Property for a list of all

Government furnished property.

5.5.ANCF is located on the 6th floor of the Silver Spring Metro Complex—Building 2 at

1325 East-West Highway, Silver Spring, MD. The BNCF facility is located at 100

University Drive, Fairmont, WV.

6. DATA AND DELIVERABLES

All deliverables are delineated in Attachment J.3 - Contract Data Requirements List dated

July 08, 2015, which is provided in the solicitation/contract.

7. MEETINGS AND OTHER REQUIREMENTS

All Government-mandated meetings are delineated in Attachment J.3 - Contract Data

Requirements List dated July 08, 2015, which is provided in the solicitation/contract.

8. AWIPS SYSTEM PERFORMANCE REQUIREMENTS

The following are the System Requirements for the AWIPS. Table - 1 below shows which of these system performance requirements are mandatory to be included at the specified Acceptable Performance Level and those in Table – 2 that are mandatory, but subject to adjustment based on the Offeror’s proposed solution. Once these requirements are negotiated, and agreement reached between the Offeror and the

Government, these shall be incorporated into the contract as SLAs as part of the QASP. The solutions shall meet or exceed the requirements specified in in Table – 1 Mandatory and Table – 2 Mandatory but subject to adjustment, below.

Table – 1 Mandatory

Number Title Definition Acceptable Performance Level

On-Time delivery of Contract

Deliverables without any changes or modifications

Delivery of all contract deliverables on-time and accepted the first time by the Government

100% accepted on-time, first time each month

SBN and Master Ground

Station (MGS) Availability

SBN MGS availability is defined as uninterruptible access to the MGS capability 99.99% per month

3 SBN Data Availability

SBN Data Availability is the measure of the amount of data that is transmitted successfully across the

AWIPS SBN.

99.90% per month

Number Title Definition Acceptable Performance Level

Average Message Timeliness

Average Message Timeliness is defined as a performance metric to identify timeliness of weather products being delivered from a WFO to NWS customers via the SBN.

99.95% of Priority 1 messages returned to WFO via SBN within ten

(10) seconds after message is transmitted via Message Handling

System (MHS), logged and time stamped per month.

99.95% of Priority 2 messages returned to WFO via SBN within thirty (30) seconds after message is transmitted via MHS, logged and time stamped per month.

99.85% of Priority 3 messages returned to WFO via SBN within sixty (60) seconds after message is transmitted via MHS, logged and time stamped per month.

Service Restoration (Response to Trouble Tickets)

A measure of the time required to restore services to the sites during a time of service interruption.

Level 1 (Sites in Critical Weather

Status): <3 minutes, 95% of the time per month.

Level 2 (Comparable to critical priority; but for sites not in Critical

Weather Status): <10 minutes 95% of the time per month.

6 System Performance (User

Experience)

Measures the system performance and data latency at the WFOs, RFCs and NCs. Table 3 contains specific performance metrics supporting this SLA.

Meet 98.00% performance objectives or better.

7 Vulnerability Scan to Inventory

Ratio

The ratio of devices scanned to total scanable devices in inventory 98% or better

Plan of Action and Milestones

(POA&M) Resolution Rate

The percentage of POA&Ms assigned to the contractor for resolution which are completed and closed by the due date

100%

Table – 2 Mandatory, but subject to adjustment based on the Offeror’s proposed solution

Implementation of new software capabilities into O&M

Ability to implement new capabilities into operations within cost, schedule, and performance.

Includes capabilities developed by AWIPS prime contractor as well as the integration of capabilities developed by other organizations. Large enhancement projects are defined to be projects that require the addition and modification of more than

12,500 Software Lines of Code (SLOC), Medium enhancement projects are defined to be projects that require addition and modification of more than

8,000 SLOC. Small enhancements projects are defined to be projects that require the addition and modification of 8,000 or less SLOC.

Incorporate each year:

2-4 large enhancements

5-10 medium enhancements

10-20 small enhancements

Message Distribution to

National Digital Forecast

Database (NDFD) for WFOs

Delivery time begins when the messages are received from the WFO through rsync to the

AWIPS WAN and stored on the NDFD Servers at the primary and backup NCFs.

Delivered within10 minutes on average per month.

3 WFO SvcBU (Site

Redundancy)

WFOs require other sites to be able to take over once a SvcBU has been declared for a site. Each site has a primary, secondary and third backup site identified.

Upon initiation of SvcBU, 10 minutes for backup site to be fully operational for the down site

Software Quality—Minimize

AWIPS Deficiency Reports

(DRs) Released to Operational

Sites

Measures software quality by minimizing DRs released to operational AWIPS sites taking into account the DRs priority and impact on operations.

This metric measures how many new DRs are introduced to operations by any release to operations, e.g., major content releases, emergency releases, patches, etc. It does not address backlog

DRs. The classification schema for AWIPS DRs is in the AWIPS Technical Library.

The maximum DR thresholds introduced into a release of AWIPS Software to the operational site is:

Critical-1 = 0

Critical-2 <= 2

High-2 <= 5

Critical-3 + High-3 +

Major-3 <= 20

Moderate-4 + Moderate-5 <= 25

5 AWIPS Software Upgrade

Time

Establishes the maximum time in minutes it takes to successfully install a release of AWIPS software returning an operational site to full operational status. The scope of this metric includes all AWIPS baseline supported software including AWIPS applications, COTS and FOSS packages and security patches. The metric addresses upgrades associated with new content or corrective releases and patches including those associated with required security updates. The scope does not include upgrades associated with major OS upgrades, e.g., Linux 6.x to 7.x.

30 minutes or less

Vulnerability Resolution Rate

The percentage of vulnerabilities detected by the previous scheduled vulnerability scan which were remediated by the current scheduled scan each month

Routine Patching: 100% of Critical and High vulnerabilities and 95% of

Medium and Low vulnerabilities as measured by Common Vulnerability

Scoring System (CVSS) remediated within 30 days of scan deadline (or patch availability if issued after detection)

Emergency patching: 100% of

Critical vulnerabilities determined by the Government to need immediate attention due to unacceptable risk to the system are remediated within two

(2) days upon availability of patch by the vendor

7 Maximum Vulnerability

Resolution Duration

The longest length of time measured in days from detection that a vulnerability can remain unpatched once discovered, by severity (as measured by

CVSS)

30 days or less from the scan deadline date for all Critical and High vulnerabilities, 40 days or less for Medium and Low vulnerabilities.

8 POA&M Effectiveness Rate

The percentage of POA&Ms from the previous assessment which were deemed closed by the contractor, but whose weaknesses were found again in the next annual assessment

5% or less

TABLE 3 – SYSTEM PERFORMANCE AND DATA LATENCY

The test procedures associated with these Test Steps may be found on the AWIPS Technical

Library.

Table 3 – System Performance And Data Latency

Test Step Name

Acceptable

Performance Level

(ms)

D2DLoadStdEnvDataPackage 10,600

FFMPA Step01.1 12,600

FFMPA_Step01.2_ImageLoading 4,100

FFMPA_Step01.2_TableLoading 6,600

FFMPA_Step01.3_ImageLoading 4,100

FFMPA_Step01.3_TableLoading 6,600

FFMPA_Step06.2 5,976

FFMPA_Step06.3 4,100

FFMPA_Step06.4 4,100

FFMPA_Step07.1 4,100

FFMPA_Step07.2 4,100

FFMPA_Step07.3 2,500

FFMPA_Step08.2 5,100

FFMPA_Step08.3 4,100

FFMPA_Step08.4 4,100

FFMPA_Step08.7 4,100

FFMPA_Step09.3_SmallHeadWater 2,500

FFMPA_Step12.1 5,100

FFMPA_Step12.2 5,100

FFMPA_Step13.1 4,100

FFMPA_Step13.2 5,100

FFMPA_Step14.3 2,500

GFELoadingMaps 3,600

GFELoadGrids 4,600

GFEPopulateGrids 7,600

GFESmartTool_AdjustUp 9,600

GFEInterpolateGrids 32,600

GFESaveGrids 18,600

GFEPublishGrids 12,600

GFEZFPTextFormatter_19Zones 33,100

GFESmartTool_TCMWindTool 22,270

GFEISCLatency_ifpnetCDF 4,100

GFECheckTandTd 25,600

GFEISCLatency_iscMosaic 6,800

Acceptable

Performance Level

(ms)

GFEZFPTextFormatter_6Zones 25,600

GFEQPF_SnowAmt 61,600

Hydro—Time Series Table 2,500

Hydro—MPE Editor 16,600

Hydroview – View 2,500

Ingest_Latency_BINLIGHTNING 3,792

Ingest_Latency_BUFRNCWF 2,509

Ingest_Latency_BUFRUA 1,266

Ingest_Latency_GOESSOUNDING 10,430

Ingest_Latency_OBS 3,040

Ingest_Latency_REDBOOK 1,151

Ingest_Latency_SATELLITE 12,280

Ingest_Latency_SFCOBS 1,103

Ingest_Latency_GRIB1 1,476

Ingest_Latency_GRIB2 5,021

Ingest_Latency_RADAR_LOCAL 1,216

Ingest_Latency_RADAR_SBN 1,210

Ingest_Latency_SHEF 5,300

SCAN_Step01.1 4,100

SCAN_Step01.2 2,500

SCAN_Step03.3 6,600

SCAN_Step05 2,500

SCAN_Step06.1 2,500

SCAN_Step08.2 3,146

SCAN_Step08.3 3,249

SCAN_Step09.2 2,500

SCAN_Step09.4 2,500

SCAN_Step11.1a 2,500

SCAN_Step11.3a 3,912

SCAN_Step11.3b 3,913

SCAN_Step12.1a 2,500

SCAN_Step12.3a 3,911

SCAN_Step12.3b 3,919

SCAN_Step16.1 4,100

SCAN_Step16.2 4,100

SCAN_Step16.3 4,100

SCANDMD_Step01 2,500

SCANDMD_Step02.a 2,500

SCANDMD_Step02.b 2,500

Acceptable

Performance Level

(ms)

SCANDMD_Step03 2,500

SCANDMD_Step04.1 2,500

SCANDMD_Step04.2 2,500

SCANDMD_Step05.1 2,500

SCANDMD_Step06 2,500

SCANDMD_Step08.1 2,500

SCANDMD_Step09.1 2,500

SCANDMD_Step09.2 2,500

SCANDMD_Step10.1 2,500

SCANDMD_Step10.2 2,500

SCANDMD_Step11.1 2,500

SCANDMD_Step11.2 2,500

SCANDMD_Step12.1 2,500

SCANDMD_Step12.2 2,500

SCANDMD_Step13.2 2,500

SCANDMD_Step13.3 2,500

SCANDMD_Step13.4 2,500

WarnGenLightLoad_AddOrRemoveCounty 2,500

WarnGenLightLoad_DragToPolygonShown 2,500

WarnGenLightLoad_FollowUpActionCON 2,500

WarnGenLightLoad_TypeTornadoToSVS 2,500

WarnGenLightLoad_TypeSVRToTornado 2,500

WarnGenLightLoad_SendProductTOR 4,727

WarnGenLightLoad_SendProductSVS 4,167

WarnGenLightLoad_LocalCWAUpdate 12,600

WarnGenLightLoad_WarnGenButton (first run) 2,500

WarnGenLightLoad_WarnGenButton (subsequent run) 2,500

WarnGenLightLoad_CreateTextTOR (first run) 2,500

WarnGenLightLoad_CreateTextTOR (subsequent run) 2,500

WarnGenLightLoad_CreateTextSVS (first run) 2,500

WarnGenLightLoad_CreateTextSVS (subsequent run) 2,500

NCPLoadNHCEnvDataPackageMax_SPC_Step5 180,000

NCPLoadNHCEnvDataPackageMax_NHC_Step5 180,000

NCPLoadSoundingForPoint_Step7 100

CAVENCPSurfacePlot_Step5 2,000

CAVENCPSurfacePlot_Step6 2,000

CAVENCPSurfacePlot_Step7 2,000

CAVENCPSurfacePlot_Step8 2,000

CAVENCPSurfacePlot_Step9 2,000

Acceptable

Performance Level

(ms)

CAVENCPSurfacePlot_Step10 2,000

CAVENCPSurfacePlot_Step11 2,000

CAVENCPSurfacePlot_Step12 5,000

CAVENCPUpperAirPlot_Step5 2,000

CAVENCPUpperAirPlot_Step6 3,000

CAVENCPUpperAirPlot_Step7 3,000

CAVENCPUpperAirPlot_Step8 2,000

EDEXUGDIngest_Test_Procedure1_Step1 30,000

EDEXUGDIngest_Test_Procedure2_Step1 30,000

EDEXSatIngest_Test_Procedure1_Step1 1,000

EDEXSatIngest_Test_Procedure2_Step1 900,000