November 5, 1984

TO:              All Holders of Operations Manual

SUBJECT: Transmittal Memorandum for Operations Manual Issuance 84-16

1.    Material Transmitted:

Revised WSOM Chapter A-20, AFOS Program Management.

2.    Summary:

This revised Chapter:

        a. Reflects the addition of the Directors of the Eastern, Southern, Central, and Western Regions to the AFOS Change Management Board in October 1982.

        b. Reflects the NWS organization and routing code changes made in December 1982.

        c. Reflects the transfer of the following responsibilities from the Office of Systems Development to the AFOS Operations Division, Office of Technical Services: (1) the maintenance and development of improvements to the AFOS field software (February 1983) and (2) the operation of the Integrated Test Bed functions (August 1983).

        d. Updates the AFOS Handbook Series inventory and status.

        e. Reflects the current AFOS network topology.

3.     Effects on Other Instructions:

This Chapter supersedes WSOM Chapter A-20, Issuance 82-13, dated August 6, 1982.

Richard E. Hallgren
Assistant Administrator
for Weather Services

Issue Date Org. Code         NATIONAL WEATHER SERVICE    Part     Chap.
11-5-84      W/OTS5                          Operations Manual                A          20

Table of Contents:

1.     Purpose

2.    AFOS Overview

*      2.1   AFOS Network
        2.2  Operations Concept
        2.3  Operations Priorities
*      2.4  Change Management

3.     Roles and Responsibilities

         3.1  National Headquarters
                3.1.1 Assistant Administrator for Weather Services
*              3.1.2 AFOS Program Manager
*              3.1.3 AFOS Operations Manager
                3.1.4 Office Directors
        3.2   Regional Headquarters
*              3.2.1 Regional Director
                3.2.2 Regional AFOS Systems Manager
        3.3   AFOS Field Site
                3.3.1 Meteorologist in Charge-Area Manager/Hydrologist in Charge
                3.3.2 AFOS Systems Manager
                3.3.3 AFOS Systems Technician
        3.4   National Headquarters/Regional AFOS Systems Interface

4.     AFOS Directives

        4.1 Operations Manual
*      4.2 Handbooks

Exhibits:

* A-20-1     AFOS Regional Distribution Circuit/State Distribution Circuit Network
* A-20-2     NWS Operational Roles
* A-20-3     AFOS Program Management Structure

1. Purpose. This chapter defines organizational roles and responsibilities in the National Weather Service (NWS) management of the Automation of Field Operations and Services (AFOS) program and establishes the AFOS directives series.

2. AFOS Overview. This section provides an overview of the AFOS network, the concept and priorities for operation of the system, and the process for managing change to the system.

* 2.1 AFOS Network. The AFOS system hardware consists of computers and display equipment installed at about 200 NWS field sites and a small number of other agency sites within the lower 48 states. The AFOS communications network consists of four closed loop Regional Distribution Circuits (RDC) which terminate at the Systems Monitoring and Coordination Center (SMCC) and interconnect all Weather Service Forecast Offices (WSFO) within the Eastern, Southern, Central, and Western administrative regions. In addition to WSFO's, the National Hurricane Center is a node on the Southern Region RDC and the National Severe Storms Forecast Center and National Aviation Weather Advisory Unit are nodes on the Central Region RDC. The National Meteorological Center (NMC), Weather Service Nuclear Support Office at the Department of Energy in Las Vegas, Army Corps of Engineers' Water Resources Data Center, and National Aeronautic and Space Administration's Johnson Space Flight Center are connected directly to the SMCC. AFOS equipped Weather Service Offices (WSO) and River Forecast Centers (RFC) are connected to their "parent" WSFO in a star network configuration by a series of State Distribution Circuits (SDC). The AFOS RDC/SDC communications network is depicted in exhibit A-20-1. In 1985, the approximately 120 additional NWS offices which did not receive AFOS systems will be implemented with Remote Terminal to AFOS (RTA) systems and integrated into the AFOS network via dedicated communications lines to AFOS WSFO's or WSO's.

2.2 Operations Concept. The AFOS RDC network delivers centralized guidance products to the NWS offices, allows the exchange of locally generated products between sites, and is the primary means of delivering NWS products to other circuits servicing the public and other agency systems. Prior to AFOS, NWS sites received and distributed the majority of their data and forecast products over area circuits operated by the Federal Aviation Administration as well as several independent NWS facsimile and NOAA Weather Wire Services. AFOS is a dramatic departure from this distribution methodology in that the NWS now operates and maintains its own integrated communications network. The change is further heightened by the integration of communications, processing, storage, and display functions at the sites and by the store-and-forward communications protocol and loop configuration of the AFOS network which makes each site dependent on its neighbors, the SMCC, and NMC for the proper handling and distribution of data and products.

/wsom/manual/IMAGES/e201.gif

The interdependent nature of the AFOS system requires an operations concept that reflects two differing operational roles.

* Service Operations

* System Operations

Primary responsibilities in these operational roles are:
 

Service Operations	System Operations
*Service requirements definition and validation.	*Network operations and support requirements definition and validation.
*Service preparation and control.	*Network management and control.
*Service dissemination.	*Network operations and support.
*Service monitoring and quality control.	*Network monitoring and quality control.

These NWS operations roles at the national, regional, and site levels are depicted in exhibit A-20-2. The left column lists organizational responsibility in service operations, the right column lists responsibility in system operations, and the center column shows those areas in which organizations have responsibilities in both aspects of operations.

The NWS service operation spans all NWS program areas and is the subject of the bulk of the Operations Manual chapters. The AFOS system operations roles and responsibilities and the organizational interfaces with the service operations are addressed in detail in following sections of this chapter.

2.3 Operations Priorities. Maintaining the AFOS network integrity and effectively managing the system is vital to the NWS in fulfilling its service mission.
 

/wsom/manual/IMAGES/e202.gif

In fulfilling the real-time service mission, as stated in WSOM Chapter A-02, the acquisition of data on severe or otherwise dangerous weather conditions and the preparation and dissemination of warnings and/or observations of such conditions, as appropriate, must take precedence over all other assigned activities. Real-time maintenance of the operational integrity of the RDC communications network is second in precedence only to the above activities.

The network operations and support and service areas have organizational interfaces at various levels, (see 3.4). Conflicts that cannot be resolved via the organizational channels can be submitted to the change management process for ultimate resolution by the Assistant Administrator for Weather Services, if required. The following section provides more detail.

2.4 Change Management. The change management organization and policy is the subject of Chapter A-21 of the WSOM. An overview is presented here since change management is the vehicle for approving changes to the AFOS system and for resolving AFOS program management issues.

The AFOS Change Management Board (CMB) has been formed to organize and manage the development and operation of a change management program for AFOS.

* The members of the CMB are the Directors of NWS Headquarters Offices (W/OM, W/OH, W/NMC, W/OSD, and W/OTS), the Chief of the Management and Budget Staff (W/MB), and the Directors of the NWS regions using AFOS equipment (W/ER, W/SR, W/CR, and W/WR). The Chairman is the AFOS Program Manager (W/OSD).

The functions of the Board include:

Establishing specialized mechanisms essential to effective management of AFOS changes, including mechanisms for AFOS configuration control and product review.

Allocating the resources (staff, funds, and facilities) necessary to accomplish all tasks assigned by the Board.

Documenting and reporting all major decisions.

Recommending to the Assistant Administrator for Weather Services changes that have a major impact on service requirements, the NWS organization, NWS budget, or previously approved AFOS schedule.

Referring to the Assistant Administrator for Weather Services any major issues that cannot be resolved by the Board.

All requests for change to the AFOS system are to be submitted to the AFOS Operations Division (AOD) for processing, including review and coordination prior to scheduled CMB action. Minor requests for change do not require CMB approval but must be approved by AOD before action or implementation is initiated. The Chief, AOD will determine whether a change is of a major or minor nature.

In order to support the review and processing of requests for change to products carried on the AFOS network, the CMB has established the Data Review Group (DRG). The group, composed of at least one member designated from W/OM, W/OH, W/NMC, W/OSD, and W/OTS, is authorized to approve or reject requests for change affecting products on the AFOS network.

Requests for product changes are submitted to the Group through the Chief, AOD. Upon receipt by the AOD, requests for change are logged and distributed to the DRG members for review. The Office of Meteorology (OM) and/or Office of Hydrology (OH), as appropriate, are responsible for validating the service requirements of the product request prior to action by the DRG. Requests that involve new or changing requirements are referred to the DRG after validation of requirements by OM and/or OH. Requests upon which the Group cannot agree and requests which, upon analysis, are determined to have major impact on the system are returned to the Chief, AOD, for referral to the AFOS CMB.

3. Roles and Responsibilities. This section addresses the roles and responsibilities for management of the AFOS program at the national, regional, and site levels. Exhibit A-20-3 illustrates the AFOS program management structure.

3.1 National Headquarters. At the National Headquarters level the major AFOS program management roles are the Assistant Administrator for Weather Services, AFOS Program Manager, AFOS Operations Manager, and the Office Directors.

3.1.1 Assistant Administrator for Weather Services. The Assistant Administrator for Weather Services has delegated the authority for management of the AFOS program to the AFOS Program
 

/wsom/manual/IMAGES/e203.gif

Manager. The Assistant Administrator for Weather Services retains approval authority for major issues that cannot be resolved by the AFOS CMB.

3.1.2 AFOS Program Manager. The Director of OSD, (W/OSD), is delegated overall authority for the AFOS program. The authority for the network operations and support of the AFOS system has been redelegated to the AFOS Operations Manager (W/OTS5).

Specific responsibilities of the AFOS Program Manager are:

Serves as Director of OSD with responsibility for the planning, design, and development of major enhancements and upgrades to the AFOS system; for analyzing and evaluating requests for change in terms of potential impacts on the system design; and for defining requirements for experimentation and development testing in support of major changes.

Serves as Chairman of the CMB. Informs the Assistant Administrator for Weather Services of any major issues that could not be resolved by the Board.

Serves as the voting member of the CMB for the OSD.

Approves the plan covering the transfer of AFOS line item funds to system development and operations support.

3.1.3 AFOS Operations Manager. The AFOS Operations Manager is the Chief of the AOD (W/OTS5) who also serves as Deputy Director, Office of Technical Services (OTS). The authority for the network operations and support of the AFOS system has been delegated to the AFOS Operations Manager by the AFOS Program Manager. This is represented in exhibit A-20-3 by the dashed arrow. This delegation provides an individual and supporting organization (AOD) dedicated to providing the real-time network operations and management support for the AFOS system.

Specific responsibilities assigned to the AFOS Operations Manager are:

Serves as Chief of AOD, OTS, with responsibility for developing plans, policies, and procedures for the operation, maintenance, and support of the AFOS system in coordination with the program manager, regions, and other operational units, including those of other agencies requiring AFOS communications interfaces; provides direction to other OTS divisions, Headquarters offices, and regions in carrying out their support responsibilities for AFOS system operations; coordinates and tracks the change management process; coordinates the analysis, evaluation and functional specification of requests for changes; operates the AFOS Integrated Test Bed function; evaluates the system operations and performance; and develops and approves systems operations plans and documentation.

Operates the SMCC to provide AFOS network control; data monitoring; communications, hardware, and software consultation to the network; Service Records Retention System tape logging; AFOS software development and maintenance; and management of the Gateway data exchange interface and other system interfaces.

Approves all minor requests for change. Minor requests for change do not require CMB approval but must be approved by AOD before action or implementation is initiated. The Chief, AOD, determines whether a change is of a major or minor nature.

Controls and manages expenditures of AFOS line item and NWS reprogrammed resources; serves as focal point for preparation and changes to the AFOS budget plan; establishes and coordinates the OTS, OM, OH, and Regions' resource requirements for AFOS field operations; and issues status reports on the total AFOS program budget.

3.1.4 Office Directors. The Directors of OM, OH, NMC, OSD, OTS, and Chief of MB are the members of the AFOS CMB from National Headquarters and serve as the focal points for approving and submitting requests for change originating from their offices.

The Directors of OM and OH are responsible for defining and reviewing the service requirements for the AFOS program in the meteorological service and hydrological service areas, respectively. These service requirements take the form of definition of products (their content, format, and distribution), primary and backup dissemination requirements and system capabilities necessary to support the service role of the forecaster/hydrologist in the field.

The Director of NMC is responsible for support of the Gateway interface with the SMCC. This involves receipt of observations, summaries, forecasts, and warnings from the SMCC for distribution to other agency and international circuits and passing selected data received over these circuits to the AFOS system. In addition to the two-way Gateway data exchange support, the NMC is responsible for generating graphics products for AFOS display and for header conversion, formatting, and retention of alphanumeric products, as required, for distribution to other circuits.

The Director of OSD serves also as the AFOS Program Manager. The AFOS responsibilities of the Director, OSD, are covered under the Program Manager responsibilities (see 3.1.2).

The Director of OTS has assigned responsibility for the technical operations and support of the AFOS system to the Chief of the AOD. The Chief, AOD, who is Deputy Director, OTS, is designated AFOS Operations Manager (see 3.1.3). Overall responsibility for technical services not specifically related to the network operation and support of the AFOS system remains under the Director, OTS.

The Chief of MB has responsibility for retaining for use by the Program Manager those AFOS line item funds not allocated to specific development or operational activities. As a CMB member, the Chief, MB, is responsible for evaluating the resource impact of major requests for change.

3.2 Regional Headquarters. At the regional headquarters level, the major AFOS program management roles are performed by the Regional Director (RD) and Regional AFOS Systems Manager (RASM).

*3.2.1 Regional Director. The Directors, Eastern Region (W/ER), Southern Region (W/SR), Central Region (W/CR), and Western Region (W/WR) are members of the AFOS CMB. The RD's have overall responsibility and authority for the real-time forecast, warning, and observing services within their regions. The regional responsibilities include: quality control of regional products and services, management of allocated resources, and tracking of allocations and regional reprogrammed resources in accordance with national directives. The RD's serve as the approving officials for all requests for change submitted from their regions.

3.2.2 Regional AFOS Systems Manager. The RASM is delegated regional authority for network operations and support activities from the RD. This is represented in exhibit A-20-3 by a dashed arrow. The RASM position, as a regional counterpart to the AFOS Operations Manager at the national level, is responsible for the real-time operational support of the RDC network. It is the discretion of the RD where within the regional organizational structure the RASM position is located.

The RASM serves as a focal point for all regional requests for change to the AFOS system. The review of requests for change originated by an AFOS site or within the regional office is to be coordinated at the regional level by the RASM. After approval by the RD they are to be forwarded to the Chief, AOD. Requests for change involving RFC unique software, hardware, or products are to be approved and forwarded by the RD of the region through which the RFC's SDC is driven.

3.3 AFOS Field Site. At the WSFO, RFC, and WSO levels, the major AFOS program management roles are performed by the Meteorologist in Charge-Area Manager/Hydrologist in Charge, the AFOS Systems Manager (ASM), and the AFOS Systems Technician.

3.3.1 Meteorologist in Charge-Area Manager/Hydrologist in Charge. The meteorologist in charge-area manager (MIC-AM) serves as the AFOS site manager for his/her WSFO area of responsibility. The hydrologist in charge (HIC) serves as the site manager for the RFC. Specific authority for network operations and support is delegated by the MIC-AM/HIC to the ASM and AFOS Systems Technician (through the area electronics supervisor). Similar authority for network operations and support is delegated to the MIC/OIC at the WSO.

Responsibilities of the MIC-AM/HIC are:

Setting priorities for utilization of the system consistent with network operations, system maintenance, and service directives.

Maintaining a high level of office performance and operational readiness through measures such as quality control monitoring, use of periodic drills, identifying and seeking to fulfill training needs of the staff, maintaining equipment and expendable supplies, and performance of preventative maintenance.

Setting direction for and maintaining cognizance of on-station development work.

Resolving conflicts in operations priorities (for example, in data or maintenance requirements) between the WSFO and RFC/WSO's on the SDC's.

3.3.2 AFOS Systems Manager. The AFOS Systems Manager (ASM) who is a meteorologist or meteorological technician at a WSFO is delegated authority and assigned responsibility for network operations and support (other than hardware) of the AFOS system in the forecast area. At the RFC, under delegation from the HIC, a designated senior hydrologist performs this function for the site. This delegation is represented in exhibit A-20-3 by a dashed arrow.  Organizationally and operationally, the ASM is to function much like a program leader.

Specific responsibilities of the ASM are:

Training personnel on station and at WSO's within the forecast area in utilization of AFOS, maintaining records with regard to on-station AFOS training, and assisting the site manager in identifying additional training needs.

Maintaining the integrity of the data base of the WSFO and coordinating data base requirements with the RFC/WSO's.

Managing a "Procedures Library" and AFOS System Log.

Checking the AFOS operational proficiency of site operators on a periodic basis and maintaining records of the station's state of operational readiness (periodic drills).

Verifying and completing documentation of all software modifications and changes, including applications programs.

At each WSO, there should be an assigned AFOS Program Leader. The AFOS Program Leader at the AFOS or RTA equipped WSO is to work in close coordination with the WSFO ASM to provide the system support for the service office.

3.3.3 AFOS Systems Technician. The AFOS Systems Technician who is the senior electronics technician (SET) at the WSFO is delegated authority and assigned responsibility for the hardware support (and, additionally, at some offices certain software and network support) of the AFOS system in the forecast area. The delegation of authority by the MIC-AM/HIC through the AES is represented in exhibit A-20-3 by a dashed arrow.

Specific responsibilities of the AFOS Systems Technician are:

Repair and maintain on-station AFOS hardware in accordance with regional and national directives contained in WSOM Chapters and Engineering Handbook 13.

Provide technical and logistical support to all AFOS technicians in the maintenance area.

Verify and complete documentation of all hardware modifications and changes.

In practice, with a computer/communications system such as AFOS, it is often difficult initially to isolate problems as purely software, communications, or hardware. Therefore, the ASM and SET need to maintain a continuing technical exchange and work as a team to most effectively maintain network and site operations.

Depending on the computer/communications background of the ASM and SET and established station operating procedures, either individual (or both) may be assigned responsibility for:

Serving as on-station software expert -- assisting others in the technical operation of the system and in development work.

Maintaining working and backup operational disks, operational software, and station-specific files.

Resolving AFOS software/hardware failures.

3.4 National Headquarters/Regional AFOS Systems Interface.  The technical operations and support, meteorological/hydrological services, and development and design support aspects of the AFOS system span the entire NWS organization.

The need for an organizational path that is able to respond to the real-time network operation and management support needs of the AFOS system has evolved an interface structure depicted in the left column of exhibit A-20-3. At the national level, an AFOS Operations Manager as Chief of the AOD, heads an organization created exclusively to fulfill this function. The RASM is the regional counterpart of the AFOS Operations Manager at the national level. The RASM does not necessarily head a regional organizational unit, but still serves as focus for the management and support of AFOS real-time system operations within the region. In this capacity the RASM receives technical direction from and channels operational support needs to the AFOS Operations Manager at the national level. At the WSFO level, the ASM and AFOS Systems Technician form a team responsible for the network operation and management support needs of the forecast office and service office AFOS systems. The successful performance of this function at the site level is critical to the system operation since it is the local offices that provide the weather services to the public and have hands-on responsibility for maintenance of the integrity of the RDC/SDC network.

The same interface structure depicted in the left column of exhibit A-20-3 is used for submission of requests for change to the AFOS system. The RASM serves as the focal point for requests for change at the regional and site level. Review of these requests is to be coordinated by the RASM for approval by the RD. Requests receiving regional approval are forwarded through the RD to the AFOS Operation Manager (Chief, AOD) who is responsible for the approval process at the national level. Minor requests for change are acted upon at the AOD level, while requests for major changes are forwarded for action to the AFOS CMB.

The Program Manager position, created by the Assistant Administrator for Weather Services, resides in the formal management structure for the AFOS program depicted in the center column of exhibit A-20-3. It is through the Program Manager, serving as Chairman of the AFOS CMB, that major requests for change (those requests having major impact on service requirements, the NWS organization, NWS budget, or previously approved AFOS schedule) are submitted to the CMB. Unresolved major issues are referred to the Assistant Administrator for Weather Services for decision. It is through the AFOS CMB that conflicts in network operations and support and service requirements are addressed.

4. AFOS Directives. This section establishes the AFOS directive series.

4.1 Operations Manual. Part A -- "General" of the WSOM establishes Chapters A-20 through A-29 under the heading of AFOS Management.

All WSOM Chapters and OML's under the AFOS directive series are to be coordinated with the AOD and approved by the Chief, AOD, before submission to the Assistant Administrator for Weather Services for final approval.

4.2 Handbooks. The AFOS handbook series is hereby established. The procedures for preparation of AFOS handbooks are in WSOM Chapter A-01. In most cases, responsibility for preparation of AFOS handbooks is with the AOD. All handbooks in the AFOS series are to be coordinated with the AOD and receive final approval from the Chief, AOD. Policy and procedures for AFOS hardware maintenance are provided in Engineering Handbook No. 13 (EHB 13). Maintenance of EHB 13 is the responsibility of Engineering Division (W/OTS1).

* AFOS Handbook 1, Notices and Handbook Maintenance, outlines the responsibility and process for creating and maintaining the AFOS Handbook Series, describes its components, and provides space for filing the notices that are issued in conjunction with the handbooks.

* The AFOS handbook series consists of the following:
 

AFOS Handbook #	Title	Status
1	Notices and Handbook Maintenance	Issued 11/83
2	Operator's Handbook	Issued 4/84
3	Configuration Management	Not Issued
4	Network Operations	Update Issued 3/84
5	Reference Handbook
	Volume 1 - System Overview	Not Issued
	Volume 2 - Fault Recognition and Recovery	Issued 11/82
	Volume 3 - Station Operations	Not Issued
	Volume 4 - System Management	Not Issued
	Volume 5 - Regional Backup Plans	Not Issued
	Volume 6 - Applications Programs	Issued 8/84
	Volume 7 - SMCC Operations	Not Issued

WSOM Issuance
84-16    11-5-84