Specifications

SPECTRUM Web Operator
Known Alarm & Event Reports Anomalies in Web Operator Suite 2.6
SPECTRUM Software Release Notes Page 123
Known Alarm & Event Reports Anomalies in
Web Operator Suite 2.6
Problem 1: All SPECTRUM defined events and alarm probable causes are
titled. Any additional events/alarms created by the user will have its
corresponding event code/alarm probable cause number as the title. The
Alarm and Event Presentation Editors can be used to give titles to any new
probable causes or event codes created by the user.
Problem 2: Groupings of probable cause and event types are not
complete. Those that are not grouped will appear in the “Ungrouped”
column. The Alarm and Event Presentation Editors can be used to create
new groupings of probable causes and event codes or to modify existing
ones.
Problem 3: Reports will timeout when clicking on totals if the
SpectroSERVER goes down while gathering data.
Problem 4: The totals listed in Alarm Reports should be considered a close
approximation rather than a precise sum of generated alarms. Often, if you
click an alarm total, the number of items in the report for generated alarms
will be exactly the number you clicked. Sometimes, the number will not be
exact due to the following causes:
• If the alarm total includes Today, more items listed as alarms could
have occurred since DBWriter was run.
• The user does not have permission to read alarm data from
SPECTRUM.
Problem 5: In SPECTRUM 5.0 there are no persistent alarms. This means
that if the SpectroSERVER is shut down and restarted, the alarms will be
re-generated with new alarm IDs. This may impact the alarm blocks
reported with differing alarm ids even though the events are for the same
alarm.
Problem 6: Pie Charts on workstations supporting only 8-bit color may
contain pie slices without proper 3D shading due to a lack of color
resources.