Blog

Notes on queue management and deployment guides

Technical articles on the editions, deployment requirements, integrations and measurement approach of the NGQ Queue Management System.

6 min read

Single License or Enterprise: How to Choose the Right Edition?

Both editions run the same branch software; the difference starts at the centre. Branch count, reporting needs and central management expectations are the three deciding factors.

Read article
7 min read

Branch and Central Deployment: Which Component Goes Where?

Software installed at the branch uses the same requirements in both editions, while NGQ Manager is installed at the centre for the Enterprise edition only and has its own requirements.

Read article
4 min read

Built on .NET 10: Security and Long-Term Support

.NET 10 is more than a version number — it is an enterprise choice for security updates, performance and long-term support.

Read article
4 min read

Five Seconds From Centre to Branch: How Settings Are Delivered

Define settings centrally instead of visiting each branch; definition changes are applied to branches every 5 seconds by default.

Read article
6 min read

What Gets Measured Gets Improved: Reporting and Waiting Time

Measure waiting time with the live branch report, transaction report, staff report and chart analysis — and base staffing plans on data.

Read article
5 min read

From Call Screen to Digital Signage: TroyBlink Integration

Queue numbers and counter information flow live to call screens; screen content is managed centrally through TroyBlink.

Read article
5 min read

HTTPS, Certificates and Activity Logs: Corporate Security Settings

HTTPS with your corporate certificates, hashed passwords in the database, e-mail password reset and a comprehensive activity log.

Read article
5 min read

CRM, ERP and Time-Attendance Integration: Stop Duplicating Data

Work with corporate systems over RESTful API support — without entering user and appointment data twice.

Read article
4 min read

Beyond 10 Branches: Moving to IIS and Planning Capacity

Self-hosting is sufficient for testing; above 10 branches, moving to IIS is recommended. The central database is the main scaling factor.

Read article
5 min read

Choosing Kiosks, Indicators and Terminals: The 10-Client Rule

The default configuration is optimised for 10 web-based indicators and 1 main display; if only LED indicators are used, the memory requirement is lower.

Read article

Let's plan your scenario together

We will determine the right edition and hardware together, based on your branch count and integration needs.

Request a Demo