Power & access control
PACsys™
A property-wide power and access control system for hotels. PACsys manages guest-room electrical state, the housekeeping workflow and the check-in cycle — then puts every property you operate on one live dashboard.
- ~300 properties in production
- 50+ HMS / PMS vendors
- Independent AC & load control
- On-premises, cloud or hybrid
The portal
Every room, on one screen
Occupancy, device health, today's events and the open task list — the moment they change. Reception, housekeeping and maintenance all work from the same live picture.
Dashboard
Occupancy · now
64%
21 / 33
- HMS 16
- Management 3
- PACsys 2
- Checkout Rooms 5
Health · now
100%
3/3 online
v1.2.22+5c375876
Events · today
47
since 00:00
Tasks
- Available 3
- Awaiting Clean 4
- Active Housekeeping 3
- Active Bypass 1
- Approvals 0
Checkins · 30 days
Total
188
checkins
Peak
14
7/19
Active
28 /30
days
Cleanings · 30 days
Total
412
cleanings
Peak
26
7/21
Active
30 /30
days
Visiting · 30 days
Total
96
visits
Peak
9
7/26
Active
27 /30
days
Maintenance · 30 days
Total
34
jobs
Peak
5
7/31
Active
19 /30
days
Checkin & checkout · today
Checkins
12
Checkouts
9
Peak hour
11:00
Active hours
9/24
Rooms · 33 total
2nd Floor
11 rooms
201
HMS · Occupied
AC · Enabled
202
HMS · Occupied
AC · Enabled
203
Checkout
AC · Disabled
204
MGMT · Occupied
AC · Enabled
205
HMS · Occupied
AC · Enabled
206
Housekeeping
AC · Disabled
207
HMS · Occupied
AC · Enabled
208
Available
AC · Disabled
209
HMS · Occupied
AC · Enabled
210
PACsys · Occupied
AC · Enabled
211
Checkout
AC · Disabled
3rd Floor
11 rooms
301
HMS · Occupied
AC · Enabled
302
HMS · Occupied
AC · Enabled
303
Housekeeping
AC · Disabled
304
HMS · Occupied
AC · Enabled
305
MGMT · Occupied
AC · Enabled
306
HMS · Occupied
AC · Enabled
307
Bypass
AC · Enabled
308
HMS · Occupied
AC · Enabled
309
Checkout
AC · Disabled
310
HMS · Occupied
AC · Enabled
311
HMS · Occupied
AC · Enabled
4th Floor
11 rooms
401
HMS · Occupied
AC · Enabled
402
Available
AC · Disabled
403
MGMT · Occupied
AC · Enabled
404
HMS · Occupied
AC · Enabled
405
Housekeeping
AC · Disabled
406
HMS · Occupied
AC · Enabled
407
Checkout
AC · Disabled
408
PACsys · Occupied
AC · Enabled
409
HMS · Occupied
AC · Enabled
410
Available
AC · Disabled
411
Checkout
AC · Disabled
Floor health
100%
3 floors · 3 healthy · 3/3 devices
Scheduled maintenance
No scheduled maintenance.
Expiring
Nothing expiring.
Interface preview — property names and figures are illustrative.
How it fits together
One controller per floor, in the distribution board
PACsys does not put a box in every guest room. The controller lives in the floor distribution board and switches the lighting, the air conditioning, the sockets and anything else wired into it — which is why it goes into a hotel that is already trading as readily as into a new build. Keycard control is a separate component, the PACsys AT series, added only where you want it.
- New build, renovation or a hotel that never closes
- Because the equipment sits in the floor distribution board, the work happens in the riser rather than in occupied rooms. A property is wired floor by floor while the rest of it keeps trading — which is what makes a retrofit viable rather than a shutdown.
- Lighting, AC, sockets and whatever else is wired in
- Every load is switched on its own rather than through one master relay. You decide what the system controls and what it leaves alone, circuit by circuit.
- Keycard control is a separate component — the AT series
- PACsys AT adds keycard-based control of the other loads, so the room follows the guest. It is ordered when you want it and left out when you do not: without it the same controller runs on occupancy, schedule or the front desk, and nothing about the installation changes.
- The floor keeps running on its own
- Each controller holds the state for its own rooms and carries on enforcing it if the server goes quiet. Losing the server does not unpower a floor or lock anyone out.
Hardware
Built to outlast the refurbishment
Guest-room hardware is judged on how long it stays fitted, not on what it costs to fit. The TES5001 series has been developed continuously since the first installation rather than discontinued and reinvented — which is why a property wired two decades ago is still a property we support.
-
2005
First installation
TES5001 boards fitted in guest rooms.
-
Since
Four generations
Developed in place, not discontinued and reinvented.
-
2026
Gen 4 in production
The earliest boards are still switching circuits.
TES5001 Floor control module
24 · 20 · 16 · 12 · 8 ports
Gen 4AT series Secondary circuits
8 · 7 · 6 · 5 channels
To orderTES5002 Starter controller
4 channel
CurrentPort counts exist so a property buys the capacity it has, rather than a catalogue size. The AT series is built against the order — which circuits a hotel wants under keycard control is rarely the same twice.
Capabilities
What PACsys gives your operation
50+ HMS and PMS integrations
Over fifty hotel and property management systems already send us check-in, check-out and room-move events. Whatever your properties run — or inherit through an acquisition — the odds are we have integrated with it before.
Independent control of every load
The air conditioner, the lighting circuits, the geyser, the balcony sockets — each is a separately addressable load, not one master relay. Switch any of them individually from the dashboard or bind them to the guest lifecycle.
Keycard-driven power
The keycard governs the AC and any secondary load you choose to put behind it. Pull the card and the room reverts to your policy; put it back and it returns to the guest’s setting — with the front desk able to override either way.
Real-time multi-property dashboard
Live room state across every property in a single view, pushed rather than polled. What happens on the floor reaches the screen in well under a second.
Guest lifecycle automation
Check-in, check-out, room moves and stay amendments arrive from the property management system and actuate the room automatically — with guards that refuse an unsafe or stale command.
Housekeeping workflow
Room status, cleaning state and maintenance flags tracked as a live queue. Supervisors see overdue rooms without walking the corridor.
Mobile-first remote diagnostics
An engineer in front of the rack can enumerate serial ports, restart the service under a watchdog, sweep every controller with live per-device results, and read serial numbers and firmware versions straight off the bus.
Managed rollouts
Choose a version and a set of properties; endpoints update themselves at the next check-in. Staggered, version-gated and reversible, with development releases fenced off from production.
Resilient to bad networks
Properties on unreliable connectivity keep operating. Events queue locally and ship in order once the link is back — nothing is dropped in the gap.
Role-based access control
Built-in roles for administrators, managers and viewers, plus custom roles you define. Permissions are granular and enforced at the API, not just hidden in the interface.
Data isolation per property
Each property keeps its own database and the central layer rolls up. No shared-tenant surprises, no noisy-neighbour performance issues.
Complete audit trail
Every meaningful action — check-in, command, administrative override — recorded with actor, target and timestamp.
Who uses it
Four very different people, one system
A receptionist and a field engineer need almost nothing in common from the same product. PACsys gives each of them their own surface.
Front desk
Check-in and check-out, room shifts, and the current state of every room on the floor.
Housekeeping supervisor
The live cleaning queue, overdue rooms, and direct control of room fixtures.
Support engineer
Property health across the estate, version rollouts, and diagnostics per client.
Field engineer
Serial-level bus debugging from a phone while standing at the rack.
For your IT team
Boring infrastructure, on purpose
Nothing here needs a platform team to operate. If your IT department can run a Windows or Linux server and a SQL database, they can run PACsys.
Standard server stack
Modern .NET on the server side with SQL Server for storage. No container orchestration required.
Outbound-only connectivity
Properties reach out to the central service. No inbound firewall rules or site-to-site VPNs to negotiate.
Encrypted end to end
TLS in transit and transparent database encryption at rest, with token-based authentication throughout.
Live updates that degrade well
Real-time push falls back gracefully on restrictive corporate networks rather than failing outright.
Licensed per machine
On-premises installations are hardware-bound, so a licence cannot quietly walk to another site.
Fast, reversible deploys
Updates apply in seconds with a single-command rollback if a release misbehaves.
PACsys Network
Operating more than one property? The multi-property layer of PACsys puts every installation you run on a single live dashboard, with fleet rollouts and remote diagnostics.
Read moreIntegrations
How check-in, check-out and room moves arrive from your property management system — event catalogue, authentication and compatibility guarantees.
Read morePlatform
The architecture behind it: what runs where, what happens when a part of it fails, and the security posture in full.
Read moreSee PACsys on your own floor plan
We will walk through a live system with real room data, then scope what a rollout looks like for your estate — property count, integration points and timeline.