Provide all of the following information that applies to your appeal. In
case of formatting problems, contact the Operations and Requirements
Division - W/OS1 at (301) 713-1373.

**Header**

The header includes blocks 1 through 2, and will be completed by the
W/OS1 change analyst upon receipt of the change request.

1\. WSH TRACKING NUMBER. For WSH use. Number automatically assigned by
Change Management Database.

1A. REV LEVEL. For WSH use to indicate revisions.

2\. DATE RECEIVED. For Weather Service Headquarters (WSH) use to
indicate the date the soft copy arrived at the ***appropriate***
mailbox.

***Blocks 3 through 13 must be the same as the RC being appealed. Blocks
14 through 16 must contain additional information to justify the
approval of the appeal/RC.***

3\. ORIGINATOR OFFICE. Office of authorized submitter, e.g., NWS, FAA,
ERH.

4\. SUBMITTING AUTHORITY. Name and routing code of authorized submitter
usually the office director or equivalent or person formally delegated
by office director or equivalent.

5\. COGNIZANT TECHNICAL INDIVIDUAL. Name, routing code, and telephone
number of person to be contacted by WSH offices familiar with the
requirement and proposed solution.

6\. ORIGINATOR TRACKING NUMBER. Originator=s tracking number using local
numbering system.

7\. DATE SUBMITTED. Date RC Appeal submitted - email soft copy to the
***appropriate*** mailbox.

8\. SYSTEMS AFFECTED BY CHANGE. Check off all boxes for systems affected
by the proposed changes. If the system affected is not listed, check
"other" and specify the system name. Data product changes constitute a
unique category; do not check off any of the other systems unless a
hardware or software change will be required for those systems. **For
best results in checking boxes double click on the cell, select
\"checked\" for the default value on the pop up window, and then select
okay.**

9\. ORD IDENTIFIER. For WSH use to indicate the Operational Requirements
Document (ORD) assigned under OSIP.

10\. TITLE OF CHANGE. Concise descriptive title of change, include
location(s), if applicable.

11\. CATEGORY OF CHANGE. Check off boxes for Request for Change (RC),
Preliminary Engineering Change Proposal (PECP), or Engineering Change
Proposal (ECP).

12\. TYPE OF CHANGE. Check off boxes for type of change; any combination
of hardware, software, or data can be selected; assume documentation
always applies and check documentation only box when there is no
physical hardware or software change.

13\. SITES AFFECTED. List of site(s) affected. Include and specify the
station or communications identifier. When referring to component
information, include part and serial numbers.

14\. NEW INFORMATION ON REQUIREMENT, PROBLEM, OR DEFICIENCY OF EXISTING
SYSTEM FOR APPROVING AUTHORITY CONSIDERATION. Submitter's additional
narrative description of problem(s) and supporting information for the
basis for change. For new requirements, submitters should identify the
applicable ORD.

15\. NEW INFORMATION ON KNOWN OR PROPOSED SOLUTION. Submitter=s
additional information for the recommended solution; describe how
solution would be accomplished and new features; include advantages over
alternate solution(s); if RC is for a data products change, describe new
products or changes to existing products.

16\. NEGATIVE CONSEQUENCES IF NOT APPROVED. Submitter's list of negative
consequences if the appeal/RC is not approved.

17\. REVIEW GROUP DECISION. For WSH use to document decision actions.