Adtec digital TBGS w/adManage - Manual (Page 20)

Chapter 3 - Using adManage 18
Alarm Management
Alarm Status:
To view the current alarms, browse to Alarm Management >
Alarm Status (Fig. 3.6)
Figure 3.6
To view all alarms that have registered in the past hour, click on
the “Current Alarms” button located at the top of the alarm grid. Alarm
Status gives you the ability to narrow the results for alarms using the
following criteria; Type, Date/Time, Headend ID, Channel ID, File
Name, and Notification Status.
There are 19 types of alarms. Refer to the following chart for
status and troubleshooting assistance.
Suggested Use for Alarm Rules
Merge
Description: Merge occurred - Status Only
Suggested use: This alarm is used to notify that the Local
schedules have been placed into the Merged Schedules folder via the
Merger Service. Use this for confirmation that new/updated schedules
have been moved to the merged schedule folder. This process must
happen in order for the Duets to see your new/updated schedules. After
you assign this alarm to a user, it will take 5 – 10 minutes after loading
the schedules from your traffic software to receive an alarm. If you
do not receive this status alarm and new schedules have been made
or updated, please move to troubleshooting procedures. This Alarm
would be useful for any traffic personnel wanting confirmation of the
movement of new/updated schedules, which is a necessity for the Duets
to retrieve them.
Merge Conflict
Description: Merge conflict occurred - Local and interconnect
spots are scheduled for the same avail time.
Suggested use: This alarm is used only in an interconnect
environment, to notify of a conflict when merging the two schedules
together. This alarm will be sent out in situations where scheduled
breaks exists n both schedules. If this alarm is received, reference the
schedule name in the alarm to troubleshoot your conflict. This Alarm
would be useful for any traffic personnel.
UnMerge
Description: UnMerge occurred - Status Only
Suggested use: This alarm will notify that verifications have been
unmerged and are ready for billing. This Alarm would be useful for any
traffic personnel ready to bill the previous day.
Not Checked-In (*Highly Recommended Alarm*)
Description: Channel has not checked-in - The ad inserter has
not reported back an RDY file in the past hour, most likely caused by a
communication problem/interuption.
Suggested use: This alarm is used to notify that a Duet has not
logged into the TBGS in the past hour. Communication to the Duet must
be investigated and re-established if need be. The Duet must be able
to login to retrieve schedules and place verifications. This alarm should
be used and monitored to ensure constant/consistent communication to
the TBGS. This alarm would be useful for anyone managing Duets at the
headend and any IT specialist.