System Topologies

There are plenty of ways to design Q-SYS systems for each installation.

Let’s look at some of the more common applications and design philosophies

so that you can feel comfortable selling the best  

solution for your customer requirements and budget.

Let’s start with the centralized processing architecture;

this option is typically the most robust and cost-effective solution  

when doing larger projects or several smaller rooms.

In a centralized processing architecture,

a single Q-SYS Core serves multiple spaces from a centralized location,

such as a technology closet or a data center.

This could be two or three smaller spaces run by a smaller Q-SYS Core processor

or several larger spaces run by a Q-SYS Server Core,

such as multiple meeting rooms or an entire transportation hub.

The Q-SYS Core connects to dedicated I/O at the edge or within the space;

this often results in a lower total cost as processing resources are shared,

and I/O is tailored to the needs of each space.

Centralized processing scheme can also simplify the connection between your installation

and Q-SYS Reflect Enterprise Manager for remote monitoring and management

by registering a single core instead of multiple cores.

Centralized processing makes sharing audio, video, and control between multiple spaces easier,

making it the ideal solution for flexible  

installations where several spaces can be combined to create a larger space.

This next design approach, which is usually called “Edge” or “distributed topology”

is essentially the opposite of centralized.

Instead of having a single Q-SYS Core processor to drive the whole system ….,

an Edge topology relies on each space having its own Q-SYS Core processor,

either located within the space or nearby in a technology closet.

This could entail each meeting room having its own Q-SYS Core for example.

In an edge deployment typology, each space is self-sufficient.

Changes can be made to a processor’s design without impacting other spaces,

and there is less concern about overburdening a processor’s capability.

Now, on the flip side, edge deployment makes moving audio,  

video, and control signals between spaces

more complex than if you were to do it in a centralized deployment model;

it’s not impossible, but it just requires a little  

bit more coordination and planning between systems.

There are times when neither centralized nor edge typologies are the best option to pursue;

sometimes, the truth lies somewhere in between;

we call this a hybrid typology.

As its name suggests,

a hybrid topology combines pieces of centralized and edge processing schemes.

Centralized assets, including paging, internet radio audio streams, digital signage,

and satellite television channels,

can exist in one location and be routed to each space as needed.

Otherwise, each separate space more-or-less stands independently,

and content doesn’t need to be dynamically shared from space to space.

No matter the project type or scale,

Q-SYS can handle it –

it’s just about selecting the best design typology and pairing it with the right Core.

Check out the link in the links section to compare  

all Q-SYS Cores either by feature or by application.

Until then, we’ll see you next time.