Rane HAL1x Design Guide - Page 106

Priority, Number, is paging into Scenario

Page 106 highlights

HAL SYSTEM DESIGN GUIDE is paging into Scenario A, Paging Station Y tries to page into Scenario B. What should happen? Should Paging Station Y's page go through to Zone 3 but not to Zone 2 (because Paging Station X is currently paging into Zone 2)? Or should the page go through to both zones, overriding the current page into Zone 2? Or should Paging Station Y be prevented from sending the page because of the conflict? Answering these questions is the purpose of the Scenario Priority. The Role of a Scenario Priority Let's revisit the above example, but this time with priorities in place. Let's say Scenario A has a priority of 10 and Scenario B has a priority of 20 (lower priority than Scenario B). When someone using Paging Station Y decides to page into Scenario B, the status indicators on the paging station indicate that the Scenario is Busy (meaning at least one of the Scenario's zones is currently receiving a page). Paging Station Y is not allowed to page into Scenario B because Scenario B has a lower priority than Scenario A. If, however, Scenario B had a higher priority than Scenario A, Paging Station Y would show a status of Caution for Scenario B, indicating a page is possible but will override the page currently being heard in one or more of the zones in Scenario B. (For more details on the status indicators associated with HAL paging stations, see the next question.) By default, Halogen assigns each new Scenario a priority value of 50. If you do nothing, all Scenarios will have the same priority, meaning no Scenario can override another Scenario. If, however, you have Scenarios that should take precedence over others, configure their priorities accordingly-the lower the number, the higher the priority. For example, you might configure a Scenario specifically for the manager of the organization and give it the highest priority. The Role of a Scenario Number Here's another possible dilemma. What if you have defined a Scenario that will be available on more than one paging station, yet you want the manager to have priority into that Scenario. This is where the Scenario Number comes into play. Each Scenario is assigned a unique number, which is configurable. You can use this number to help you identify identical Scenarios. For example, you might create Scenario A intended for the receptionist. You give this Scenario a priority of 10 and a number identifier of 104. You create an identical Scenario A intended for the manager. You give this Scenario a priority of 1 and a number identifier of 101. Although these two Scenarios have the same name and contain the same zones, you can use the number to help you distinguish one from the other. NOTE: You do not have to worry about numeric identifiers and priorities when it comes to emergency paging. The HAL System includes a special block designed specifically for emergency paging situations. See below for details. What does each paging status (Busy, Caution, Ready) mean? The Pager1 RAD paging station displays LED status indicators labeled Busy, Caution, and Ready. When the end user selects a Scenario to page into, the status indicator informs the user if the page is possible. The following table includes definitions of each state: 102

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

is paging into Scenario A, Paging Station Y tries to page into Scenario B. What should happen? Should Pag-
ing Station Y's page go through to Zone 3 but not to Zone 2 (because Paging Station X is currently paging
into Zone 2)? Orshould the page go through to both zones,overriding the current page into Zone 2? Or
should Paging Station Y be prevented from sending the page because of the conflict? Answering these ques-
tions is the purpose of the Scenario
Priority
.
The Role of a Scenario Priority
Let's revisit the above example, but this time with priorities in place. Let's say Scenario A has a priority of 10
and Scenario B has a priority of 20 (lower priority than Scenario B). When someone using Paging Station Y
decides to page into Scenario B, the status indicators on the paging station indicate that the Scenario is Busy
(meaning at least one of the Scenario's zones is currently receiving a page). Paging Station Y is not allowed
to page into Scenario B because Scenario B has a lower priority than Scenario A. If, however, Scenario B had
a higher priority than Scenario A, Paging Station Y would show a status of Caution for Scenario B, indi-
cating a page is possible but will override the page currently being heard in one or more of the zones in Sce-
nario B. (For more details on the status indicators associated with HAL paging stations, see the next
question.)
By default, Halogen assigns each new Scenario a priority value of 50. If you do nothing, all Scenarios will
have the same priority, meaning no Scenario can override another Scenario. If, however, you have Scenarios
that should take precedence over others, configure their priorities accordingly—the lower the number, the
higher the priority. For example, you might configure a Scenario specifically for the manager of the organ-
ization and give it the highest priority.
The Role of a Scenario Number
Here's another possible dilemma. What if you have defined a Scenario that will be available on more than
one paging station, yet you want the manager to have priority into that Scenario. This is where the Scenario
Number
comes into play. Each Scenario is assigned a unique number, which is configurable. You can use
this number to help you identify identical Scenarios. For example, you might create Scenario A intended for
the receptionist. You give this Scenario a priority of 10 and a number identifier of 104. You create an iden-
tical Scenario A intended for the manager. You give this Scenario a priority of 1 and a number identifier of
101. Although these two Scenarios have the same name and contain the same zones, you can use the number
to help you distinguish one from the other.
NOTE
:
You do not have to worry about numeric identifiers and priorities when it comes to emergency
paging. The HAL System includes a special block designed specifically for emergency paging sit-
uations. See below for details.
What does each paging status (Busy, Caution, Ready) mean?
The Pager1 RAD paging station displays LED status indicators labeled Busy, Caution, and Ready. When the
end user selects a Scenario to page into, the status indicator informs the user if the page is possible. The fol-
lowing table includes definitions of each state:
HAL SYSTEM DESIGN GUIDE
102