Site access

Compliance status, wired to the gate.

Approval is not a piece of paper. It is whether the card works when somebody puts it against the reader — so access reflects real compliance status, and somebody who has lapsed does not get through on a card issued months ago.

Book a Demo

A dozer working the top of a coal stockpile against open sky

Working with PIAGO

Customer stories

How it works

How an approval turns into a working card.

Step 01

Approval becomes permission

Clearing a worker for your site and granting them access are the same act, not two systems kept in step. Because they are not held in two places, they cannot drift apart.

Want to see this working against your own access control system?

Book a Demo (07) 3251 2468

The full list

Everything in site access.

WinDsx — live in production

Full two-way. Card provisioning and access rule updates flow out to the access system; swipe data flows back, which is what powers presence, fatigue and exceptions.

Gallagher — built and delivered

Card provisioning and permission updates flow outbound, keeping each worker’s card current with their compliance status. Swipe data does not return on this integration.

Who is on site now

Live presence from the gate rather than from a sign-in sheet. WinDsx installations only, since it depends on swipe data coming back.

Access events and the exception queue

Anomalies at the reader surface as a queue to be resolved rather than as a log nobody reads. WinDsx installations only.

Fatigue rules

Configure maximum hours, pre-entry limits and minimum rest gaps. Breaches notify the right people. WinDsx installations only.

Emergency response — who is on site

During an incident, see which ERT-trained workers are on site right now, rather than working it out from a roster.

The difference

What it takes for an approval to reach the gate.

How it usually goes

Compliance lives in one system and the card reader lives in another.
Somebody is approved on Friday and still cannot badge in on Monday.
“Who is on site right now” means counting cars, or ringing the gatehouse.
Fatigue limits are a policy in a document, not a check at the gate.
In an evacuation, the muster list is whoever signed the visitor book.

With GO! Site Approved

Compliance status and the access system are wired together, both ways.
Approval issues the card. Losing compliance withdraws it.
A live presence view, straight off the readers.
Maximum hours and rest gaps are checked, and a breach raises an alert.
The ERT-trained workers currently on site, listed instantly.

Questions about site access

Our access control already works. What does this add?

Your access system is very good at deciding whether a card is valid. What it does not know is whether the person holding it is still qualified to be there. Wiring the two together means a card reflects a current compliance status rather than a decision somebody made months ago — and on WinDsx, it means the gate can tell you who is on site right now.

What is the difference between the WinDsx and Gallagher integrations?

WinDsx is full two-way: cards and access rules flow out, and swipe data flows back. Gallagher is outbound only — card provisioning and permission updates flow out, but swipe data does not return. That difference matters, because live presence, fatigue rules and the exception queue all depend on swipe data, so they apply on WinDsx installations.

What happens at the gate when someone’s ticket lapses?

Their compliance status changes, and access is reviewed rather than left as it was. The card stops being a standing permission and starts reflecting whether they are currently qualified to be there.

Can we enforce fatigue rules through the gate?

On WinDsx, yes. Configure maximum hours, pre-entry limits and minimum rest gaps, and breaches notify the right people.

In an emergency, can we tell who is on site?

Yes — the emergency response view shows who is on site and which of them are ERT-trained, which is a different question from who was rostered.

The rest of the pipeline