Upgrade Paths
Start with a clean foundation, then upgrade in controlled steps: credentials, rules, reporting, and integration — without ripping out the system and swearing for three weekends.
What we upgrade first (in SA reality)
- Power & reliability (load-shedding breaks weak designs).
- Rules & schedules (stop “everyone can go everywhere”).
- Credential experience (throughput + less bypassing).
- Reporting (only when someone will use it).
Upgrade categories
Jump to the upgrade type that matches your real problem (not the brochure headline).
Most common upgrades
These are the upgrades that actually move the needle in Pretoria: smoother entry, fewer bypasses, cleaner admin, and better uptime.
Credentials & entry method
Change how people enter: faster throughput, better control, fewer “shared tag” problems.
- ✓RFID → biometric / face / palm where justified
- ✓Keypad for shared points (clean code rules)
- ✓Mobile credentials where supported
- ✓Credential lifecycle: issue, revoke, replace
Rules, schedules & permissions
Stop “everyone can go everywhere” and reduce after-hours risk.
- ✓Access groups (areas) + time schedules
- ✓Department-based permissions
- ✓Contractor time windows
- ✓Holiday / exception schedules
Reports, audit trails & T&A
Turn events into usable information (or compliance evidence).
- ✓Entry logs, exports, and incident review
- ✓Attendance / shift support where applicable
- ✓User activity audits (who, where, when)
- ✓Retention planning (how long you keep data)
Visitor & contractor workflows
Stop handing out permanent access because “it’s easier”.
- ✓Temporary credentials (time-boxed)
- ✓Contractor windows + restrictions
- ✓Visitor approval logic (site dependent)
- ✓Audit trail for who authorised what
Sliding gate motor integration
Gate motors belong inside the access workflow — not as a cheap standalone job.
- ✓Credential-based gate opening (not “everyone has a remote”)
- ✓Rules & schedules for vehicles / staff / contractors
- ✓Throughput planning (peak times, safety devices)
- ✓Visitor access options where needed
Power, protection & reliability
Uptime in South Africa is a power design problem. Solve it properly.
- ✓Battery-backed PSU where required
- ✓Surge protection & clean supply strategy
- ✓Load-shedding behaviour defined (what stays on)
- ✓Neat enclosure + labelled distribution
Included (standard for upgrades)
- ✓Quick assessment questions to confirm workflow and risk
- ✓Defined upgrade scope (what changes, what stays)
- ✓Install + configuration + testing
- ✓Handover update (so admins know the new rules)
Excluded (keeps upgrades sane)
- ✓Open-ended fault-finding on legacy systems
- ✓Major civil works (trenching, rebuilding door frames, patch/paint)
- ✓Electrical faults / DB work (scoped separately)
- ✓Networking remediation for unstable LAN/Wi-Fi (scoped separately)
Tell us what you want to improve
Send your area + site type + number of doors/gates + rough user count and the upgrade goal (credentials / rules / reporting / visitor workflow / gate integration / power reliability). We’ll recommend the cleanest upgrade path and scope it properly.
FAQ
Quick answers before someone asks for “a price” with zero info.
Should I upgrade credentials or rules first?
If the problem is abuse (sharing tags, bypassing doors), rules and permissions often give the biggest improvement. If the problem is throughput or friction, credential upgrades can help more. We decide based on workflow.
Is anti-passback worth it?
Only if your site has a real in/out workflow with the correct readers. Anti-passback done wrong creates admin pain. Done right, it stops credential sharing.
Why do you talk so much about power supplies?
Because most “system problems” in Gauteng are power problems. Battery-backed power and clean distribution reduce failures more than fancy readers.
Can you integrate sliding gate motors?
Yes — as part of controlled access. We prefer credential-based control, rules, and visitor workflows rather than selling commodity motor installs as the main offering.
Can upgrades be done without replacing the whole system?
Often yes, if the base architecture is clean and supportable. If the existing install is chaotic, remediation may be required first as a separate scoped job.