Revision D • 8/05
H
A
R
R
I
S
C
O
R
P
O
R
A T
I
O
N
A-4
Appendix A VMCC
digital
where all of the community members are associ-
ated with a single station or a common purpose.
For example: a single station facility where three
consoles (one air studio, an image studio and a
production/backup air studio) are networked with
one rack; or a network origination facility where
two racks are networked with six studio consoles.
When a single community has devices associ-
ated with multiple stations—where each station
group has dedicated Air, Production and Image
studios, then Tier Convention 2 or 3 can be used
to identify where each source is from by including
a Call Group name or Discipline Prefix along with
the signal’s Community name.
Here’s a summary of how the three levels of
naming are used to create local and device pub-
lish files:
When Tier 1 naming is used, local names are
displayed on all devices. This is fine for small fa-
cilities, but when multiple consoles have output
signals being routed which have identical names
(like PGM 1, for instance), it will be difficult to
know where those signals are from if each signal
is not given a unique name. To get around this
limitation, Tier 2 naming can be used.
Tier 2 names use the In Room Prefix followed
by the first nine characters of the In Room name
to identify signals on the local device. The other
members of the community will not see the In
Room name, but will see the Tier 2 name in the
example above (e.g., Call Group Name, Name Ra-
dix, Community Name).
When multiple stations are in one facility, then
Tier 3 naming can be used. This differentiates be-
tween fellow group members (those with the same
Call Group name) and everyone else in the com-
munity by showing names on the other group de-
vices using the Call Group (XYZ in the example),
the Discipline Sort Character and the Discipline
Prefix.
On devices with different Call Group names, the
System Name is used. It consists of the Call Group
name plus the first character of the Discipline Pre-
fix. The Call Group name then identifies the sta-
tion—narrowing the possible source locations to
a few rooms. The Discipline Prefix name is typi-
cally the room function, e.g. Air, Production, Im-
age, Rack, thus by combining the call letters with
the first letter of the room function one can easily
identify where the signal originates.
Setting Signal Include Lists
The Source Include list, set in the console edit
pane, is the master list of sources that will be avail-
able for selection on router modules and source
selector panels. The
routers.ini
file is where
this list gets used to create the [SrcInclude] sec-
tion list.
The Destination Include list set sets those des-
tinations (Netcard outputs) that are available to
be controlled by destination panels. The
[DstInclude] list in
routers.ini
is equal to the
Destination Include list entries.
Edge Device Parent Reassignment
Each edge device has an assigned “parent” which
is that community member with that edge device’s
setup information in its
edgedevice.ini
file.
If an existing edge device is assigned a new par-
ent in VMCC, new
edgedevice.ini
files will
have to be provisioned and distributed to all of
the affected consoles and racks to effect the par-
ent change on the edge device.
TIER NAMING DISPLAYED SOURCE NAMES BY DEVICE:
CONVENTION LOCAL GROUP SYSTEM
TIER 1 (LOCAL)
MINIDISK1
MINIDISK1 MINIDISK1
TIER 2 (GROUP) MINIDISK1
XYZ.MD1
XYZ.MD1
TIER 3 (SYSTEM) MINIDISK1
-PROD.MD1 XYZP.MD1
VMCC SETTINGS THAT GENERATED THE ABOVE NAMES:
In Room Name
1
= MINIDISK1
Community Name
1
= MD1
Call Group
2
= XYZ
Discipline Prefix
2
= PROD
Name Radix
3
= . (PERIOD)
Discipline Sort Character
3
= - (DASH)
In Room Prefix
3
= (BLANK)
1 - Entry set in the Signal Summary edit pane
2 - Entry set in the Device edit pane
3 - Entry set in the Community edit pane
Tier Naming Convention Summary
