Video Transcript
System Topologies
3m 11s
00:00
There are plenty of ways to design Q-SYS systems for each installation.
00:04
Let’s look at some of the more common applications and design philosophies
00:08
so that you can feel comfortable selling the best
00:11
solution for your customer requirements and budget.
00:14
Let’s start with the centralized processing architecture;
00:17
this option is typically the most robust and cost-effective solution
00:21
when doing larger projects or several smaller rooms.
00:25
In a centralized processing architecture,
00:27
a single Q-SYS Core serves multiple spaces from a centralized location,
00:32
such as a technology closet or a data center.
00:35
This could be two or three smaller spaces run by a smaller Q-SYS Core processor
00:40
or several larger spaces run by a Q-SYS Server Core,
00:44
such as multiple meeting rooms or an entire transportation hub.
00:48
The Q-SYS Core connects to dedicated I/O at the edge or within the space;
00:53
this often results in a lower total cost as processing resources are shared,
00:58
and I/O is tailored to the needs of each space.
01:02
Centralized processing scheme can also simplify the connection between your installation
01:03
and Q-SYS Reflect Enterprise Manager for remote monitoring and management
01:03
by registering a single core instead of multiple cores.
01:03
Centralized processing makes sharing audio, video, and control between multiple spaces easier,
01:08
making it the ideal solution for flexible
01:10
installations where several spaces can be combined to create a larger space.
01:16
This next design approach, which is usually called “Edge” or “distributed topology”
01:20
is essentially the opposite of centralized.
01:24
Instead of having a single Q-SYS Core processor to drive the whole system ….,
01:28
an Edge topology relies on each space having its own Q-SYS Core processor,
01:34
either located within the space or nearby in a technology closet.
01:38
This could entail each meeting room having its own Q-SYS Core for example.
01:42
In an edge deployment typology, each space is self-sufficient.
01:47
Changes can be made to a processor’s design without impacting other spaces,
01:52
and there is less concern about overburdening a processor’s capability.
01:57
Now, on the flip side, edge deployment makes moving audio,
02:01
video, and control signals between spaces
02:04
more complex than if you were to do it in a centralized deployment model;
02:07
it’s not impossible, but it just requires a little
02:10
bit more coordination and planning between systems.
02:14
There are times when neither centralized nor edge typologies are the best option to pursue;
02:19
sometimes, the truth lies somewhere in between;
02:22
we call this a hybrid typology.
02:26
As its name suggests,
02:27
a hybrid topology combines pieces of centralized and edge processing schemes.
02:33
Centralized assets, including paging, internet radio audio streams, digital signage,
02:38
and satellite television channels,
02:38
can exist in one location and be routed to each space as needed.
02:42
Otherwise, each separate space more-or-less stands independently,
02:47
and content doesn’t need to be dynamically shared from space to space.
02:51
No matter the project type or scale,
02:54
Q-SYS can handle it –
02:55
it’s just about selecting the best design typology and pairing it with the right Core.
03:01
Check out the link in the links section to compare
03:02
all Q-SYS Cores either by feature or by application.
03:06
Until then, we’ll see you next time.