Instructions for a Successful Transition to

New TAF format with AvnFPS

Beginning with the 0000 UTC 05 November issuance all TAFs created by the
National Weather Service will change to a new format. Simultaneously
with the format change, 32 TAFs at airports receiving trans-oceanic
flights will become 30 hours long instead of the usual 24.

  -------- -------- -------- -------- -------- -------- -------- --------
  KATL     KBDL     KBOS     KBWI     KCLE     KCVG     KDEN     KDFW

  KDTW     KEWR     KIAD     KIAH     KIND     KJFK     KLAX     KMKE

  KMSP     KOAK     KONT     KORD     KPHL     KPIT     KSAN     KSDF

  KSEA     KSFO     KSLC     KSTL     KSWF     PANC     PAFA     PHNL
  -------- -------- -------- -------- -------- -------- -------- --------

Table 1: Designated airports to have 30-h TAF forecasts beginning 0000
UTC 5 November

The purpose of these instructions is to assist the Aviation Focal Point
(AFP) and the aviation forecaster during the transition in TAF format
using AvnFPS. For the majority of the WFOs, no special action is
required to begin issuing and monitoring TAFs in the new format. For the
remaining offices\--to be determined in a moment\--either the forecaster
or the AFP will need to perform one, possibly two, task(s) at specific
times to complete a successful transition with AvnFPS.

For reference in the instructions to follow, here is the timeline of the
TAF format transition:

  --- ------------------------- ------------------------------------------
      When                      Event

  1   1720Z-1740Z 04 November   Last routine TAFs disseminated in current
                                format.

  2   2220Z -- 2340Z 04         New 00Z TAF preparation time
      November                  

  3   2320Z -- 2340Z 04         New TAFs, valid at 0000Z 5 November 2008,
      November                  submitted in new format

  4   2329Z 04 November         Last possible amended TAF(s) issued in
                                current format

  5   2330Z 04 November         All TAFs now issued in new format
  --- ------------------------- ------------------------------------------

The WFOs that will be required to perform additional steps in
preparation for the new TAF format have the following condition(s):

-   Have one or more 30-h TAFs shown in Table 1 either as a primary
    and/or secondary (backup) responsibility;

-   Routinely use TAF templates for initial issuances that have
    references to time in them, e.g., AFT xxZ or TIL yyZ or xxZ-yyZ.

If neither condition applies to your office, then no additional action
is required on the part of the AFP or aviation forecaster to make a
successful transition from the current TAF format to the new one using
AvnFPS. You can proceed to Page 11 for final instructions on preparing
and disseminating your 00Z 5 November TAFs in the new format.

However, if your office meets any of the above condition(s), then please
locate the situation(s) that matches your office, and proceed to the
directed page.

1)  Your office has two or more 30-h TAFs for which you have primary
    **and** secondary responsibilities\...See Page 3. OR

2)  Your office has one or more 30-h TAF(s) for which you have primary
    responsibilities\...See Page 5. OR

3)  Your office has one or more 30-h TAF(s) for which you have backup
    responsibilities\...See Page 7

4)  Your office makes use of TAF templates when composing the initial
    issuance of the product **and** makes references to time, e.g., AFT
    03Z, TIL 10Z, or 02Z-10Z\...See Page 9

Final instructions on composing and disseminating the first TAF in the
new format is given on page 11

If your office has primary **and** backup responsibilities of two more
airports listed in Table 1, the aviation forecaster or AFP will need to
change the \'Taf Duration\' attribute from 24 to 30 (hrs) for the
affected TAF(s). [This action should be done just before Event #3 in
Table 2]{.underline}.

There are two ways to do this.

The easiest way is to use a script that MDL has provided in the [OB8.3.1
release]{.underline}. It will examine your AvnFPS configuration and
update the tafduration attribute in the TAFs\' info.cfg file if needed.
Like so,

  -----------------------------------------------------------------------
  /awips/adapt/avnfps/bin/avnstart.sh cvt3 30

  -----------------------------------------------------------------------

If there are no errors[^1], [restart the AvnFPS client
programs]{.underline}, aka "AvnWatch" for the changes to take effect.
The forecaster should then proceed to issue his/her 00Z TAFs as they
normally would.

The other way is to use the AvnFPS TAF Site Info Editor to change the
Taf Duration attribute from 24 to 30 (hrs). If you do not have the
OB8.3.1 maintenance release installed this is the only option available
to you.

+---+-------------------------+-----------------------------------------+
|   | Action                  | Result                                  |
+---+-------------------------+-----------------------------------------+
| 1 | Start AvnFPS            | AvnFPS Configuration GUI appears, like  |
|   | Configuration GUI from  | so:                                     |
|   | the AWIPS root menu by  |                                         |
|   | selecting AvnFPS and    | ![](media/im                            |
|   | then Configuration GUI  | age1.jpeg){width="1.6777777777777778in" |
|   | options                 | height="2.7875in"}                      |
+---+-------------------------+-----------------------------------------+
| 2 | Click on TAF Site Info  | TAF Site Info GUI appears               |
|   | Editor button           |                                         |
+---+-------------------------+-----------------------------------------+
| 3 | Enter the 4-character   | Values for the TAF site are loaded into |
|   | identifier of the 30­h   | the editor:                             |
|   | TAF into the Site Id    |                                         |
|   | field and press         | ![](media/im                            |
|   | \'Load\' button         | age2.jpeg){width="3.9458333333333333in" |
|   |                         | height="3.290277777777778in"}           |
+---+-------------------------+-----------------------------------------+
| 4 | Change TAF Duration     | Attribute is changed. *Text field       |
|   | attribute from 24 to 30 | background color will change to pink.   |
|   |                         | This is okay.*                          |
+---+-------------------------+-----------------------------------------+
| 5 | Press \'Save\' button   | TAF info.cfg is successfully saved.     |
|   | to write changes back   |                                         |
|   | to disk                 |                                         |
+---+-------------------------+-----------------------------------------+
| 6 | Repeat steps 3-\>5 for  | Additional TAF info.cfg files are       |
|   | each additional 30­-h    | saved.                                  |
|   | TAF location            |                                         |
+---+-------------------------+-----------------------------------------+
| 7 | Close Editor by         | TAF Site Editor disappears              |
|   | clicking on the 'Close' |                                         |
|   | button                  |                                         |
+---+-------------------------+-----------------------------------------+
| 8 | Close Configuration GUI | Main GUI disappears.                    |
|   | via File-\>Close option |                                         |
+---+-------------------------+-----------------------------------------+

[Restart the AvnFPS client programs]{.underline}, aka "AvnWatch" for the
changes to take effect. The forecaster should then proceed to issue
his/her 00Z TAFs as they normally would.

If your office has primary responsibilities of one or more airports
listed in Table 1, the aviation forecaster or AFP will need to change
the \'Taf Duration\' attribute from 24 to 30 (hrs) for the affected
TAF(s). [This action should be done just before Event #3 in Table
2]{.underline}.

There are two ways to do this.

The easiest way is to use a script that MDL has provided in the [OB8.3.1
release]{.underline}. It will examine your AvnFPS configuration and
update the tafduration attribute in the TAFs\' info.cfg file if needed.
Like so,

  -----------------------------------------------------------------------
  /awips/adapt/avnfps/bin/avnstart.sh cvt3 30

  -----------------------------------------------------------------------

If there are no errors[^2], [restart the AvnFPS client
programs]{.underline}, aka "AvnWatch" for the changes to take effect.
The forecaster should then proceed to issue his/her 00Z TAFs as they
normally would.

The other way is to use the AvnFPS TAF Site Info Editor to change the
tafduration attribute from 24 to 30 (hrs). If you do not have the
OB8.3.1 maintenance release installed this is the only option available
to you.

+---+-------------------------+-----------------------------------------+
|   | Action                  | Result                                  |
+---+-------------------------+-----------------------------------------+
| 1 | Start AvnFPS            | AvnFPS Configuration GUI appears, like  |
|   | Configuration GUI from  | so:                                     |
|   | the AWIPS root menu by  |                                         |
|   | selecting AvnFPS and    | ![](media/im                            |
|   | then Configuration GUI  | age1.jpeg){width="1.6736111111111112in" |
|   | options                 | height="2.7805555555555554in"}          |
+---+-------------------------+-----------------------------------------+
| 2 | Click on TAF Site Info  | TAF Site Info GUI appears               |
|   | Editor button           |                                         |
+---+-------------------------+-----------------------------------------+
| 3 | Enter the 4-character   | Values for the TAF site are loaded into |
|   | identifier of the 30­h   | the editor:                             |
|   | TAF into the Site Id    |                                         |
|   | field and press         | ![](media/im                            |
|   | \'Load\' button         | age2.jpeg){width="3.9458333333333333in" |
|   |                         | height="3.290277777777778in"}           |
+---+-------------------------+-----------------------------------------+
| 4 | Change TAF Duration     | Attribute is changed. *Text field       |
|   | attribute from 24 to 30 | background color will change to pink.   |
|   |                         | This is okay.*                          |
+---+-------------------------+-----------------------------------------+
| 5 | Press \'Save\' button   | TAF info.cfg is successfully saved.     |
|   | to write changes back   |                                         |
|   | to disk                 |                                         |
+---+-------------------------+-----------------------------------------+
| 6 | Repeat steps 3-\>5 for  | Additional TAF info.cfg files are       |
|   | each additional 30­-h    | saved.                                  |
|   | TAF location            |                                         |
+---+-------------------------+-----------------------------------------+
| 7 | Close Editor by         | TAF Site Editor disappears              |
|   | clicking on the 'Close' |                                         |
|   | button                  |                                         |
+---+-------------------------+-----------------------------------------+
| 8 | Close Configuration GUI | Main GUI disappears.                    |
|   | via File-\>Close option |                                         |
+---+-------------------------+-----------------------------------------+

[Restart the AvnFPS client programs]{.underline}, aka "AvnWatch" for the
changes to take effect. The forecaster should then proceed to issue
his/her 00Z TAFs as they normally would.

If your office has backup responsibilities of one or more airports
listed in Table 1, the aviation forecaster or AFP will need to change
the \'tafduration\' attribute from 24 to 30 (hrs) for the affected
TAF(s). So long as you are reasonably confident that you will not assume
backup responsibilities of that office between Event #1 and Event #3,
you can perform the following actions anytime after Event #1.

There are two ways to do this.

The easiest way is to use a script that MDL has provided in the [OB8.3.1
release]{.underline}. It will examine your AvnFPS configuration and
update the tafduration attribute in the TAFs\' info.cfg file if needed.
Like so,

  -----------------------------------------------------------------------
  /awips/adapt/avnfps/bin/avnstart.sh cvt3 30

  -----------------------------------------------------------------------

If there are no errors[^3], [restart the AvnFPS client
programs]{.underline}, aka "AvnWatch" for the changes to take effect.
The forecaster should then proceed to issue his/her 00Z TAFs as they
normally would.

The other way is to use the AvnFPS TAF Site Info Editor to change the
tafduration attribute from 24 to 30 (hrs). If you do not have the
OB8.3.1 maintenance release installed this is the only option available
to you.

+---+-------------------------+-----------------------------------------+
|   | Action                  | Result                                  |
+---+-------------------------+-----------------------------------------+
| 1 | Start AvnFPS            | AvnFPS Configuration GUI appears, like  |
|   | Configuration GUI from  | so:                                     |
|   | the AWIPS root menu by  |                                         |
|   | selecting AvnFPS and    | ![](media/i                             |
|   | then Configuration GUI  | mage1.jpeg){width="1.582638888888889in" |
|   | options                 | height="2.6305555555555555in"}          |
+---+-------------------------+-----------------------------------------+
| 2 | Click on TAF Site Info  | TAF Site Info GUI appears               |
|   | Editor button           |                                         |
+---+-------------------------+-----------------------------------------+
| 3 | Enter the 4-character   | Values for the TAF site are loaded into |
|   | identifier of the 30­h   | the editor:                             |
|   | TAF into the Site Id    |                                         |
|   | field and press         | ![](media/im                            |
|   | \'Load\' button         | age2.jpeg){width="3.9458333333333333in" |
|   |                         | height="3.290277777777778in"}           |
+---+-------------------------+-----------------------------------------+
| 4 | Change TAF Duration     | Attribute is changed. *Text field       |
|   | attribute from 24 to 30 | background color will change to pink.   |
|   |                         | This is okay.*                          |
+---+-------------------------+-----------------------------------------+
| 5 | Press \'Save\' button   | TAF info.cfg is successfully saved.     |
|   | to write changes back   |                                         |
|   | to disk                 |                                         |
+---+-------------------------+-----------------------------------------+
| 6 | Repeat steps 3-\>5 for  | Additional TAF info.cfg files are       |
|   | each additional 30­-h    | saved.                                  |
|   | TAF location            |                                         |
+---+-------------------------+-----------------------------------------+
| 7 | Close Editor by         | TAF Site Editor disappears              |
|   | clicking on the 'Close' |                                         |
|   | button                  |                                         |
+---+-------------------------+-----------------------------------------+
| 8 | Close Configuration GUI | Main GUI disappears.                    |
|   | via File-\>Close option |                                         |
+---+-------------------------+-----------------------------------------+

[Restart the AvnFPS client programs]{.underline}, aka "AvnWatch" for the
changes to take effect. The forecaster should then proceed to issue
his/her 00Z TAFs as they normally would.

If your office routinely uses TAF templates to compose the initial
issuance **and** have references to time in them, e.g., AFT xxZ or TIL
yyZ or xxZ-yyZ, then they will need to be updated as well to be
consistent with date/time notation in the main body of the TAF.

+--------+------------------------+-----------+-----------------------+
| C      | Example of Current     | New       | Example of New Format |
| urrent | Format                 |           |                       |
| Format |                        | Format    |                       |
+--------+------------------------+-----------+-----------------------+
| AFT    | AMD NOT SKED AFT 01Z   | AFT       | AMD NOT SKED AFT      |
| HHZ    |                        | D1HHmm    | D10100                |
+--------+------------------------+-----------+-----------------------+
| TIL    | AMD LTD TO VIS CLD AND | TIL       | AMD LTD TO VIS CLD    |
| HHZ    | WIND TIL 05Z           | D1HHmm    | AND WIND TIL D10500   |
+--------+------------------------+-----------+-----------------------+
| H      | AMD NOT SKED 23Z-07Z   | D1HH/D2hh | AMD NOT SKED          |
| HZ-hhZ |                        |           | D123/D207             |
+--------+------------------------+-----------+-----------------------+

Using "D1" (that's a one, not an ell,"l") and "D2" results in
substituting the starting and ending day, respectively, in the amendment
clause when composing the initial TAF from the template. The following
instructions can be done anytime after Event #1 is completed and for all
initial times, i.e., 00Z, 06Z, 12Z, 18Z, as needed. The procedure for
editing the templates is as follows:

+---+-------------------------+-----------------------------------------+
|   | Action                  | Result                                  |
+---+-------------------------+-----------------------------------------+
| 1 | Start AvnFPS            | AvnFPS Configuration GUI appears, like  |
|   | Configuration GUI from  | so:                                     |
|   | the AWIPS root menu by  |                                         |
|   | selecting AvnFPS and    | ![](media/i                             |
|   | then Configuration GUI  | mage1.jpeg){width="1.707638888888889in" |
|   | options                 | height="2.8361111111111112in"}          |
+---+-------------------------+-----------------------------------------+
| 2 | Click on TAF Site Info  | TAF Site Info GUI appears               |
|   | Editor button           |                                         |
+---+-------------------------+-----------------------------------------+
| 3 | Enter the 4-character   | Values for the TAF site are loaded into |
|   | identifier of the 30­-h  | the editor:                             |
|   | TAF into the Site Id    |                                         |
|   | field and press         | ![](media/im                            |
|   | \'Load\' button         | age2.jpeg){width="3.9458333333333333in" |
|   |                         | height="3.290277777777778in"}           |
+---+-------------------------+-----------------------------------------+
| 4 | In the Templates        | AvnFPS Text editor appears with the     |
|   | section, select the     | template contents. Update any           |
|   | initial issuance hour,  | references to time as indicated in      |
|   | and then the Edit       | Table 3.                                |
|   | button                  |                                         |
+---+-------------------------+-----------------------------------------+
| 5 | Press \'Save\' button   | TAF template is successfully saved for  |
|   | to write changes back   | that hour.                              |
|   | to disk                 |                                         |
+---+-------------------------+-----------------------------------------+
| 6 | Repeat steps 4-\>5 for  | Additional TAF templates are saved.     |
|   | each issuance hour      |                                         |
|   | needed                  |                                         |
+---+-------------------------+-----------------------------------------+
| 7 | Repeat steps 3-\>6 for  |                                         |
|   | each TAF.               |                                         |
+---+-------------------------+-----------------------------------------+
| 8 | Close Editor by         | TAF Site Editor disappears              |
|   | clicking on the 'Close' |                                         |
|   | button                  |                                         |
+---+-------------------------+-----------------------------------------+
| 9 | Close Configuration GUI | Main GUI disappears.                    |
|   | via File-\>Close option |                                         |
+---+-------------------------+-----------------------------------------+

When it's time to compose the 00Z 5 November 2008 TAF, the OB8.3.1
AvnFPS Monitoring GUI and TAF Editor[^4] will recognize the significance
of the date and will begin to display and process the TAF in the new
format. Guidance TAFs will change at the appropriate time to the new
format. The TAF edit tools (procedures), "AdjustTimes" and
"UseMetarforPrevailing" will reconstitute the last 'old format' TAFs
into the new ones for the 00Z issuance. TAF Syntax check will flag time
groups in the 'old' format as incorrect.

[^1]: It is recommended that the person working the designated shift
    when the TAF format changes is to issue the following command well
    in advance of 05 November date to make sure there are no problems
    with non-writable file permissions:

    /awips/adapt/avnfps/bin/avnstart.sh cvt3 24

    With this command, since the taf duration is already set at 24,
    there are no real changes performed but it does verify if the user
    running the script can make the required changes on the actual day
    and time. If \'cvtInfoCfg failed on\' messages appear, you should
    rectify the problem well before the 00Z 5 November date and then
    rerun the command to ensure no other problems appear.

[^2]: It is recommended that the person working the designated shift
    when the TAF format changes is to issue the following command well
    in advance of 05 November date to make sure there are no problems
    with non-writable file permissions:

    /awips/adapt/avnfps/bin/avnstart.sh cvt3 24

    With this command, since the taf duration is already set at 24,
    there are no real changes performed but it does verify if the user
    running the script can make the required changes on the actual day
    and time. If \'cvtInfoCfg failed on\' messages appear, you should
    rectify the problem well before the 00Z 5 November date and then
    rerun the command to ensure no other problems appear.

[^3]: It is recommended that the person working the designated shift
    when the TAF format changes is to issue the following command well
    in advance of 05 November date to make sure there are no problems
    with non-writable file permissions:

    /awips/adapt/avnfps/bin/avnstart.sh cvt3 24

    With this command, since the taf duration is already set at 24,
    there are no real changes performed but it does verify if the user
    running the script can make the required changes on the actual day
    and time. If \'cvtInfoCfg failed on\' messages appear, you should
    rectify the problem well before the 00Z 5 November date and then
    rerun the command to ensure no other problems appear.

[^4]: In prior versions of AvnFPS, the 'switch-over' or 'turnkey' time
    to the new TAF format is incorrect.