Home Page
1.0 INTRODUCTION
The fielding and commissioning of the Advanced Weather Interactive Processing System (AWIPS) have catapulted the National Weather Service (NWS) into a new era of data integration and computational capability. Local applications developed by Weather Forecast Office (WFO), River Forecast Center (RFC), and National Center (NC) personnel enable offices to satisfy unique user requirements and improve efficiency of local operations.
This document addresses the implementation of several key site and regional requirements found in the AWIPS Local Applications Policy (Attachment 1). It describes the processes for: (1) submitting Local Application Registration (LAR) information for locally-developed applications; (2) registering the use of any local application; and (3) obtaining waivers to the local application policy, standards and guidelines.
2.0 SUBMISSION AND REGISTRATION PROCESS
The submission and registration process and the policy, standards and guideline compliance schedule for a local application are dependant on its operational implementation date. Section 2.1 explains how to handle local applications operational before September 15, 2000. Section 2.2 describes how to handle local applications operational after September 15, 2000. Section 2.3 describes the actions taken if a site fails to comply with the local application policy, guidelines and standards.
2.1 Applications Operational Before September 15, 2000
The submission and registration of these local applications by the sites will be accomplished in a phased approach.
Phase one (developers): The originating site shall submit Local Application Registration (LAR) information to the Local Application Database (Section 4.0). The originating office is the office who developed the local application. This activity will be completed by November 30, 2000. Note: The developers are encouraged to submit software and documentation (Phase three) along with the LAR information if they know that the application is used by more than one site.
Phase two (users): Each site shall register all local applications being used operationally at the site. If the application is not in the Local Application Database, the site should contact its LAWG Regional representative (RR). The LAWG RR(s) shall coordinate the submission of the LAR information to the Local Application Database. The activity will be completed by January 31, 2001.
Phase three: For each application registered by multiple sites, the originating site's LAWG RR shall establish a time frame for the submission of software (source or executable) and documentation (user and installation), and compliance with the local application policy, standards and guidelines. This schedule will be published at the AWIPS Local Applications Web site (Section 4.0). The activity will be completed by January 31, 2001.
2.2 Applications Implemented after September 15, 2000
The submission and registration process of local applications by the sites is slightly different for locally developed applications (implemented by the originating site) and adopted applications (implemented by a site other than the originating office).
a. Submitting and Registering a Locally Developed Application
Step one: Notify the local application community of a "planned" or "under development" local application by submitting the following LAR information (Sections 1.1, 1.2a, 1.2b) to the AWIPS Local Application Database.
Step two: Submit all LAR information to the AWIPS Local Application Database prior to the operational implementation of the local application. This submission will automatically trigger email notification to the LAWG RR.
Step three: Upload the software (source or executable) and documentation (user and installation) to the AWIPS Local Application Database unless the application is intended for local use only.
Step four: Register the application via the Local Application Database, when the local application becomes operational at the site. This registration will automatically trigger email notifications to the Network Control Facility (NCF), System Support Team (SST) and LAWG RR.
b. Locating and adopting another site's locally developed application.
Step one: Review the Local Application Database for applications that perform the desired functionality.
Step two: Download the application and documentation from the Local Application Database.
Note: Application software will be available for downloading only if the originating region believes the application is compliant with the local application policy, guidelines, and standards. Once compliance is verified, the LAWG RR will release the software and notify the AWIPS community.
Step three: Register use of the application via the Local Application Database, when the local application becomes operational at the site. This registration will trigger an automatic email notification to the NCF, SST and LAWG RR.
2.3 Noncompliance with the policy, guidelines, standards
If a site (user) fails to comply with the submission and registration process (Section 2.0), the site will be asked to comply within 30 days. After 30 days, the issue will be turned over to the AWIPS System Engineer for disposition.
If a site fails to comply with the local application guidelines and standards, the site will be asked to obtain a waiver or make the changes necessary to meet the standards and guidelines within a regionally assigned period of days. After that period, the issue will be turned over to the AWIPS System Engineer for disposition.
3.0 WAIVERS PROCESS
A site can obtain waivers to deviate from the local application policy, guidelines and standards from the AWIPS System Engineer. Waiver requests should be submitted to the LAWG RR. The LAWG shall review the waivers and recommend a course of action to the AWIPS System Engineer. In some cases, the recommended course of action may be to amend the policy, standards and guidelines. The AWIPS System Engineer shall evaluate the LAWG's recommendation and respond with two weeks. The AWIPS System Engineer shall either approve the waiver/change or disapprove the waiver and provide a recommended course of action. The LAWG shall maintain a list of waiver requests and their status. A waiver form is provided in Appendix 1.
4.0 SUPPORTING INFORMATION
The AWIPS Local Application Database provides the infrastructure, database, and user interface to submit and register local applications, view an inventory of local applications, post and respond to user questions, report and respond to software deficiencies, and upload/download registered local application software and documentation.
The AWIPS Local Application Policy establishes a standardized approach for the development, testing, implementation, maintenance, and configuration management of AWIPS locally-developed applications.
The AWIPS Applications Integration Framework Manual (AIFM) establishes the guidelines and standards for local applications. Appendix 4 of the AIFM contains the Local Application Registration (LAR).
All this supporting information can be found at the AWIPS Local Applications web site. The web site includes the means to view the status of local application waivers. The address is http://tgsv5.nws.noaa.gov/tdl/awips/.
Waiver Number: (completed by the LAWG)
Application Name:
Requestor Name and Location:
AIFM Reference:
Reason for Waiver:
Granted/Denied: (completed by AWIPS System Engineer)
Rationale: (completed by AWIPS System Engineer)
These requirements can be found in the AWIPS Local Application Policy.
Site Requirements
- use existing applications to meet site unique requirements to the degree possible (3.3.c);
- submit Local Application Registration (LAR) information for each locally-developed application following the standards in the AIFM Section 3.8 (3.3.f);
- register the use of each local application prior to implementation on an AWIPS platform (3.3.h); and
- obtaining written waivers from the AWIPS System Engineer to deviate from local application policy, standards and guidelines (3.3.k).
Regional Requirements
- enforce site compliance with the local application policy, guidelines, standards, and resource utilization limitations (3.2.c(2)).
| Local Applications Home Page |