Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

Quick Links
Radar Operation Center - Hotline
Hotline		 Radar Operations Center - Interface Control Documents
ICDs		 Radar Operation Center - Radar Build Status
Build Status		 Radar Operation Center - Radar Build Loaded at Each Site
Build Loaded		 Radar Operations Center - Wind Farms
Wind Farms		 Radar Operations Center - Modification & Software Notes
Mod/SW Notes		 Radar Operation Center - RMT Status
RMT Status

Radar Operations Center

WSR-88D Baseline Information

Configuration Baselines

The WSR-88D is formally documented by configuration identifications for both hardware and software. Configuration identification is defined as the selection of approved documents which completely identify and define the form, fit, and function of a system or portion thereof. It includes the documents themselves. The systems, or portions thereof, are referred to as configuration items (CIs). The WSR-88D contains hardware configuration items (HWCIs) and computer program configuration items (CPCIs). The CIs are identified down to the lowest hardware and software element that satisfies an end use. The identifier assigned to each CI allows traceability of changes to hardware and software items to their source. Each CI forms a portion of a particular WSR-88D baseline as described in the succeeding paragraphs.

Functional Baseline

The functional baseline (FBL), which is usually the product of the Conceptual Phase, is normally the first baseline established. It is established by authentication of the system specification. The WSR-88D System Specification (formerly the NEXRAD Technical Requirements (NTR)) with all approved changes, deviations, and waivers, the NEXRAD Algorithm Report, the Requirements Allocation and Analysis Report (RAAR), and the Systems/Subsystem Design Description (SSDD) form the functional baseline for the WSR-88D.The FBL serves as the technical base for accomplishing system requirements analysis and allocating functions to manageable configuration items.

Allocated Baseline

As requirements are allocated and grouped into specific functions or set of functions, a new CI is identified. The requirements allocated are then grouped into associated WSR-88D development specification (Part I); Type B Specification for hardware and Software Requirement Specification (SRS) for software. The hardware B Specification and the SRS contain the “design to” technical requirements for a single CI or CPCI and is the basis for detail design of that CI/CPCI. The grouping of Hardware B-Specifications, SRS, Interface Requirements specifications (IRS), and Interface Control Documents (ICDs) together become the allocated baseline (ABL). The WSR-88D ABL is established upon authentication of the Part I hardware development specification, SRS, IRS, and ICD. The ABL is dynamic in that it continues to grow as new critical items are identified or changed.

The NEXRAD WSR-88D Allocated Baseline consists of the following:

  • Type B - Development Specifications
  • Type B1 - Prime Item Development Specification
  • Type B2 - Critical Item Development Specification
  • Type B4 - Facility or Ship Development Specification
  • Type SRS - Software Requirements Specification
  • Type IRS - Interface Requirements Specification
  • Interface Control Documents (ICDs)

Product Baseline

The product baseline (PBL) documents the detailed design of the CI/CPCI. The hardware product specification (Part II), Type C Specification, and associated engineering drawings contain the “build to” technical requirements of the associated hardware CI. The Software Design Descriptions (SDDs), Interface Design Descriptions (IDDs), Database Design Descriptions (DBDDs) contain the “build to” requirements for Software CIs. The SDD, IDD, and DDBDD may be supplemented in accordance with J-STD-016.

The PBL is authenticated prior or during the Physical Configuration Audit (PCA). The PBL is also dynamic in nature due to the fact that a change in an associated baseline (FBL or ABL), software build, or major hardware upgrade will normally result in a change in the PBL. Because of this, there may be several iterations of the associated PCAs.

  • NTR with Requirements Allocation and Analysis Report (RAAR)
  • NEXRAD Algorithm Report
  • System Specification (SS)
  • System/Subsystem Design Description (SSDD)
  • Type C - Product Specification
  • Type C1 - Prime Item Product Specification
  • Type C1a - Prime Item Product Function Specification
  • Type C1b - Prime Item Product Fabrication Specification
  • Type C2 - Critical Item Product Specification
  • Type C2a - Critical Item Product Function Specification
  • Type C2b - Critical Item Product Fabrication Specification
  • Type SPS - Software Product Specification
  • Type SDD - Software Design Description
  • Type IDD - Interface Design Description
  • Type DBDD - Database Design Description
  • Type B - Development Specifications
  • Type B1 - Prime Item Development Specification
  • Type B2 - Critical Item Development Specification
  • Type B4 - Facility or Ship Development Specification
  • Type SRS - Software Requirements Specification
  • Type ICD - Interface Control Document
  • Type IRS - Interface Requirements Specification
  • Type SVD - Software Version Description
  • Type SAD - System Allocation Document
  • Test Plans
  • Test Procedures
  • Test Reports
  • Control Revision List
  • Engineering Drawings and Associated Lists
  • Technical Manuals
  • Commercial Off-the-Shelf (COTS) Manual