Professional Documents
Culture Documents
Guide
optiMET© v5.1
9 APPLICATION DATA.............................................................................................................................. 23
OptiMET enables Observers to add human based observations to the met database and assists in
generating messages based on WMO306 codes
This document provides information facilitating the effective operation of the software
Note Lists important information in this section, important related information from
other sections of the manual or advice on best practice in the usage of the
software or its accessories.
Caution This highlighted information cautions the reader of a potential hazard. Failure
to read, understand and employ information contained in this instruction could
result in the the loss of data.
The optiMET workstation is provided pre-loaded and preconfigured with the optiMET application
These applications are configured for integration with the MTECH AWOS system.
optiMET requires an operating SQL Database server and if messages are to be sent to the AFTN, an AFTN
Gateway must be running on the server
The computer clock must be set to display UTC, with Summertime options turned off.
By default, the workstation should automatically synchronise with an NTP server, and it is recommended
that these settings not be edited.
Note For the software to work correctly, the workstation time MUST be
synchronised to UTC.
Caution The user should maintain an image of the C: drive to enable fast recovery in
the event of hard drive problems.
3.1 Logging On
The user must log on to publish messages using OptiMET. This is the logon window.
To log on you must have an ID code and a Password. These are assigned by the Administrator.
Enter the Status, ID code and password from the drop down boxes. Select LOG In.
When Logged in your Name and Status [ Observer, Forecaster or Administrator ] will be displayed.
All messages Published are logged with the name of the User time and date.
Administrators can change passwords and register the names of users and their status.
The Logon window is shown below. [ note password is initially set to “password” ]
Select your access level from the 3 available levels; Observer, Forecaster, Administrator.
Select your User ID code from among the drop down list of ID codes.
The login information will appear in the application Title bar and the user can Publish Messages.
The main screen is shown below. optiMET always starts with the Metar/ Speci screen first.
The row of tabs allows the user to select the required message or function.
Enabled messages are shown in BOLD Black, disabled functions are in Grey.
AFTN is disabled
This screen enables the user to setup the Metar/Speci Message Generation process.
1. MODE
MANUAL
This enables the user to generate a message anytime by clicking on the Message TAB
AUTO
This automatically generates the message and Publishes it, both internally and to the AFTN.
This function applies only to METARS and HTML messages. When AutoMode is selected, only the
automatically acquired observations are sent and the METAR encodes an AUTO code.
2. AUTOMESSAGE
This allows selection of Auto Metar, Auto HTML or both
3. SCHEDULE
This enables the user to select a 30 or 60 minute interval between messages. It also allows the user to
observe the time to next message in the schedule.
4 SCHEDULE ALERT
This enables the user to select audible and or visual alerts. Alerts are generated for 5 minutes prior to the
scheduled time, until acknowledged.
4. DATABASE STATUS
This shows the status and the time and date of the last access to the database.
These messages are generated from the same window. The user selects the message type on the form
which is shown below.
4.1 Alarms
If SPECI alarm criteria are enabled, The alarm indicates an alert. The METAR alarm is time scheduled
Depending on the sensors fitted to the system, some of the data fields are automatically populated when
the READ button is clicked.
After a Message Schedule alert, the READ button appears RED. Clicking the READ button also
acknowledges the alert. In other cases they must be entered by the observer.
RECORD allows the Observers observations to be added to the database
Either a METAR or SPECI can be selected. This code word replaces the Token “TYPE” in the template.
Keyword Selection
After startup, the codes shown in this area are as per the following section of the screen
If CAVOK is selected the message will encode CAVOK in place of Visibility RVR and Cloud.
SKC and NSC affect only the Cloud entry area, but are disabled if CAVOK is selected
Memorised Observations
Some observations can be selected from a list of previous observations. This is accessed from the drop
down box where this feature is available.
This enables the most frequent observations to be quickly accessed. These Observations are loaded from
the configuration file, but are updated during operation.
When the drop down box control is clicked, the following appears.
The Present Weather selection Matrix enables legal codes and combinations of codes to be selected and
incorporated into the METAR.
1. Code Selection
Select Codes, descriptor and intensity where appropriate. Rules are encoded into the selector engine to
ensure codes which are WMO 306 compliant are selected.
Caution This selection matrix embodies some “expert system” functions to prevent
illegal combinations, this may prevent some combinations from being
selected.
The codes in the Message group window are added to the main form fill by clicking Accept Group. The
selection matrix closes at this time.
The same matrix is used wherever codes according to WMO 306 CT 4678 are required.
VISIBILITY MATRIX
Note This enables the user to enter Directional Visibility according to FM15, and16
RVR MATRIX
Where required but not automatically updated, the following enables the RVR observation to be correctly
formatted.
Where required but not automatically updated, the following enables the Cloud observation to be correctly
formatted.
The cloud Type can be entered by an observer for the first layer only
Caution Extra cloud codes can be added where permitted by national or regional
agreement, in compliance with WMO 306 Table 500 or otherwise.
TTF MATRIX
When logged on as a Forecaster, TTF can be added in place of NOSIG using the following
When all observations have been entered the METAR May be encoded.
This is performed by first selecting a METAR template.
The Metar Template is selected from those available in the drop down box.
The observations in the form are then composed into the METAR template by automatic substitution.
Missing observations are replaced by solidii according to WMO 306.
Once the user is happy with the content of METAR [ the user must carefully review it to ensure it is correct ].
The draft message can then be published
Messages are published for local distribution to the workstations in the AWOS system which are running the
MITAS Surface Weather Client software.
Caution The user should check the METAR before publishing it. Once published it
can be corrected using a COR, but cannot be “un published”.
Note that the AFTN Message template and AFTN message windows appear at this time, enabling the
published message to be sent out on the AFTN
The AFTN addresses are selected from the drop down list depending on the addresses required for the
message distribution. The message is then ENCODED and can be SENT if OK
Messages are posted to the SQL Database AFTN table as a “queued” message.
Messages queued in the database are published to the AFTN if an AFTN gateway is fitted to the system.
Otherwise messages are printed out for manual entry at an AFTN terminal
Messages in the AFTN database table can be observed using the AFTN log Tab on the OptiMET window
Caution The user should check the AFTN Messge before sending it Once sent
cannot be “un sent”.
The SPECI has the same format as a METAR. The word METAR ias replaced by the keyword SPECI.
A set of criteria is evaluated. In manual Mode an alert is raised when an alarm condition occurs
The INI* file has a section [SPECI] which controls the alert criteria.
In the example section below [ which contains the ICAO Annex 3 criteria ] some items have been changed.
These changes are highlighted.
Generally, if all the SPECI criteria are used, there will be a large number of SPECI reports generated.
SPECI reports may be reserved for changes in OPERATIONASLLY significant weather variables at the
airport concerned.
=====================================================
[SPECI]
Enabled = 1
interval = 60000
COMMENT: Message editor will not alarm on wind direction if the wind speed is below
windDirnMinSpeed.
COMMENT: Message editor will alarm when the change in wind direction since the last auto
message
COMMENT: (or last check when in manual mode) is greater than windDirnChange
COMMENT: To disable the check set windDirnMinSpeed above the highest value that the wind
sensor can read,
COMMENT: or set windDirn to 180 or above
windDirnMinSpeed = 10
windDirnChange = 60
COMMENT: Message editor will alarm when the change in wind speed since the last message
is at
COMMENT: least WindSpeedChange.
COMMENT: To disable the check set WindSpeedChange to greater than the wind sensor can
read. (eg 1000kts)
windSpeedChange = 10
COMMENT: Message editor will not alarm on wind gust when the wind speed is less than
windGustMinAve
COMMENT: Message editor will alarm when the change in the peak wind speed (gust)
between the last message
COMMENT: (or last check when in manual mode) is at least WindGustChange
windGustMinAve = 15
windGustChange = 20
COMMENT: Message editor will alarm when visibility improves and passes through any of the
visThreshold values
COMMENT: To diable any threshold change its name (eg. to xvisThreshold0)
COMMENT: There can be up to 8 visThresholds (ie. 0-7)
visThreshold0 = 800
visThreshold1 = 1500
visThreshold2 = 3000
visThreshold3 = 5000
COMMENT: Message editor will alarm when rvr is improving and passes through one of the
rvrThreshold values
COMMENT: To disable any threshold change its name
COMMENT: There can be up to 8 rvrThresholds (ie. 0-7)
rvrThreshold0 = 150
xrvrThreshold1 = 350
rvrThreshold1 = 400
rvrThreshold2 = 600
rvrThreshold3 = 800
COMMENT: Message editor will alarm when any of the at the onset, cessation or change in
intensity
COMMENT: of any of the weather phenomena described by weatherCondition[0-9]
COMMENT: To disable any condition change its name
COMMENT: There can be up to 10 weatherConditions
weatherCondition0 = RA
weatherCondition1 = SS
weatherCondition2 = FC
weatherCondition3 = SN
weatherCondition4 = TS
weatherCondition5 = FZ
COMMENT: Message editor will alarm when the lowest is below cloudConditionMaxHeight and
changes to or from
COMMENT: (but not between) any of the cloudConditions
COMMENT: To disable set the cloudConditionMaxHeight to 0 (or negative),
COMMENT: to disable any individual condition change its name
COMMENT: There can be up to 6 cloudConditions
cloudConditionMaxHeight = 1500
cloudCondition0 = BKN
cloudCondition1 = OVC
COMMENT: Message editor will alarm when the lowest cloud is any of the above
cloudConditions and rises past
COMMENT: any of the cloudThresholds.
Not all SPECI conditions may be required. In manual mode the user has the
Note option to generate a SPECI or not.
Caution In AUTO mode a SPECI will be sent on every alarm. Use only the key alarm
criteria to avoid sending too many SPECI messages.
Auto Mode is selected in the MODE box at the top left hand corner of the window.
In Auto Mode Metars will automatically be generated according to the schedule, and SPECIs will be
generated according to the enabled criteria.
In Automode many of the functions are locked out. However, to resume control, the user should select
manual mode.
Not all SPECI conditions may be required. In manual mode the user has the
Note option to generate a SPECI or not.
Caution In AUTO mode a SPECI will be sent on every alarm. Use only the key alarm
criteria to avoid sending too many SPECI messages.
The Message Log TAB allows the user to review the last 10 messages published.
The Weather TAB allows the user to review the recent observations at the time of message publication.
The template files have embedded tokens which are replaced during the encoding process.
There are 2 types of tokens, one for use with HTML files uses the caret as a wrapper:
eg: ^METAR^
The other is based on the WMO Codes for Metars from WMO 306.
Eg: QPhPhPhPh
In some instances, the automatic observations, or derived data are used in a token replacement process to
generate messages, therefore, when editing the HTML message templates, the tokens may be inserted
where desired.
AIRPORT ^CCCC^
DATE/MONTH/YEAR ^DATE^
UTC ^UTC^
RUNWAY ^RWY^
RUNWAY LIGHT SETTING ^RLS^
WIND DIRECTION MEAN (deg) ^WD2^
WIND SPEED MEAN (kt) ^WS2^
METEOROLOGICAL OPTICAL RANGE (m) ^VIS^
RUNWAY VISUAL RANGE (m) ^RVR^
BACKGROUND LUMINANCE (cd/m2) ^BL^
CLOUD BASE HEIGHT (ft) ^CL10^
SEA LEVEL PRESSURE (QFF)(hPa) ^QFF^
AERODROME PRESSURE (QFE)(hPa) ^QFE^
ALTIMETER SETTING (QNH)(hPa ) ^QNH^
AIR TEMPERATURE (degree C) ^AT10^
DEW POINT TEMPERATURE(degree C) ^DPT1^
RELATIVE HUMIDITY(%) ^RH^
PRECIPITATION (mm/h) ^RF1^
Password File