Access Expert or Security Expert? A field guide to Schneider’s two access control products (and who should install them)
If you’re specifying access control on a Schneider-integrated building, you’ll run into two products with almost identical names. Access Expert and Security Expert. Both from Schneider. Both integrate with EcoStruxure Building Operation. Both do the core job — cards, readers, doors, credentials, events.
They are not the same product. And picking the wrong one for your building is an expensive mistake.
Here’s the plain-English version — plus the mistake we see on almost every project where a security or low-voltage contractor gets brought in without the BAS integrator in the room.
What they have in common — deep EBO integration.
Start with the reason both products exist under the Schneider name. Both integrate deeply with EcoStruxure Building Operation. Not “the two systems can email each other” integration. Real integration:
- Card events fire on the same event bus as HVAC alarms
- Doors and readers appear as native objects in the EBO operator interface
- A single sequence of operations can reference the door state and the zone temperature
- TGML graphics show live access events on your floor plans
- Alarms sync bidirectionally — acknowledge in EBO or acknowledge in the access system, either way they clear
This is what makes either product worth buying in the first place. Without EBO integration, you’re paying more for what you could get from any commodity access control vendor. With it, access control becomes part of the building’s operating system.
The short answer — side by side.
Before the detailed breakdowns — the two products at a glance.
| Factor | Access Expert | Security Expert |
|---|---|---|
| Deployment | Cloud (Schneider-hosted on AWS) | On-premise (your servers, your network) |
| Best fit | Multi-site, mobile-heavy, IT-lean orgs | Single-facility, security-sensitive, data-sovereign orgs |
| Access control server | None on-site | On-site server required |
| Updates | Automatic monthly (Schneider ships) | You or your integrator manage |
| Data location | Schneider cloud (AWS, TLS 1.2 + SSE) | Your building |
| Offline resilience | Controllers buffer, UI needs cloud | Full local operation, no cloud needed |
| Native reader line | HID Signo (Schneider-branded) | Security Expert SX-series |
| EBO integration | Smart Connector (SW-SMARI-CONNECT) | Native |
| Multi-tenant architecture | Enterprise instance + shared instances | Configurable by site |
| Answer if you want it in the cloud | Yes | — |
| Answer if access data cannot leave the building | — | Yes |
Access Expert — the cloud product.
Access Expert lives in Schneider’s cloud, hosted on AWS. The card database, credentials, schedules, and access groups all live in the cloud. Your on-site hardware is intelligent controllers (Mercury-based — the AX-SSC, AX-MP1501, MP1502, MP2500, MP4502 line) and card readers (HID Signo, Schneider-branded). Controllers talk to the cloud over TLS 1.2 encrypted channels.
What it’s built for.
- Multi-site organizations — Enterprise instance architecture supports shared instances across geographies, with root-level visibility for owners and separated data for tenants or divisions
- IT teams that don’t want an on-prem access control server to install, patch, back up, or refresh
- Mobility-heavy operations — iOS and Android app, HTML5 web client, unlimited concurrent operators from day one
- Owners who value automatic monthly updates — features and cyber patches ship in the cloud, no on-site maintenance window required
- Multi-tenant buildings — Enterprise architecture separates tenants while giving building ownership visibility across the whole system
What comes native, not as an add-on.
- Access control with unlimited concurrent operators
- Visitor management (self-check-in kiosk, host notifications, contractor tracking)
- Mass messaging (SMS + email to any group, one click)
- Two-factor authentication (text or QR code, no additional license)
- Windows client, HTML5 web client, and mobile apps in every tier
What integrates.
Access Expert connects to EBO through the Access Expert Smart Connector (SW-SMARI-CONNECT). Beyond EBO, it integrates with a long list of third-party systems out of the box — Milestone, Pelco, Salient, Exacq, Avigilon, Hanwha (video); Allegion and ASSA ABLOY Aperio (wireless locks); Bosch B-series (intrusion); KONE, OTIS, Mitsubishi, Schindler, ThyssenKrupp (elevator destination dispatch); Zenitel ICX-Alphacom (SIP intercom); Invixium and SAFR (biometrics); Active Directory over LDAP (HR sync).
Where the “cloud” matters.
No on-prem server means no server refresh cycle, no local backup rotation, no operating system patch schedule. Weekly Veracode cyber scans run in the background. Updates ship monthly from Schneider.
If the internet drops, the on-site controllers keep operating. Card holders and events buffer locally and sync when connectivity returns. The operator UI needs the cloud to function — the doors don’t.
Security Expert — the on-prem product.
Security Expert lives on your building’s own network. The database, credentials, schedules, and application all run on servers you (or your facilities team) own. No cloud dependency.
What it’s built for.
- Single-facility or campus deployments where data sovereignty matters — access data stays inside the building, full stop
- Government, healthcare, defense, high-security research — anywhere “our access control data cannot leave the building” is a hard IT policy
- Buildings with strict cloud policies against hosted physical security data
- Operations that require zero external network dependency for door operations — the door doesn’t wait on an internet connection, ever
- Millions of credentials stored in offline memory — resilient to any network disruption
Its own reader line.
Security Expert has its own multi-technology reader family — the SX-DRD, SX-RD, SX-RK, SX-DRK series — in Mullion, Wallplate, and Mini form factors. Black or white. Optional keypad, optional Bluetooth. Support for MIFARE/DESFire, 125kHz, NFC, and Bluetooth mobile credentials. OSDP Secure Channel out of the box.
What integrates.
Security Expert integrates natively with EcoStruxure Building Operation — the same TGML graphics, the same alarm sync, the same shared event bus. Beyond EBO, it uses standard industry protocols (SOAP, SIP) and has an extensive library of pre-built integrations, plus a fully documented public API for anything custom. SIP-compliant VoIP intercom systems get a deep native integration.
Where “on-prem” matters.
Zero cloud attack surface. Data lives where regulators or IT policy require it to live. No internet dependency for the operator interface, not just the doors. And in a scale-up scenario — a campus growing from 50 to 500 doors — you’re not renegotiating cloud tier pricing.
What integration actually looks like on the operator screen.
This is what “integrated” actually means when the work gets done properly.
Live door states on your floor plan. Card events sharing an alarm view with HVAC critical faults and lighting overrides. A sequence of operations that reads the door open event, checks the HVAC zone occupancy, and either logs it or triggers a response — all from one platform, one workstation, one operator training curriculum.
Facility team stops managing three separate consoles. Night shift stops asking which system an alarm came from. Reporting stops being a multi-system correlation exercise.
The one common mistake — who installs it.
Here’s the part that comes up in almost every Schneider access control conversation we have.
The security integrator or low-voltage contractor gets brought in. They install the panels. They pull the wire. They mount the readers. They program the cards. Everything works — you badge in, the door unlocks, events show up in the Access Expert or Security Expert UI.
Then the owner asks the question: “so when does this start talking to my BAS?”
And the answer is silence.
The integration was never actually done. Not because the product doesn’t support it — Schneider engineered the integration into both products deliberately. But because integration on the EBO side is a completely different skill set than pulling wire and mounting readers.
Real EBO integration means:
- Mapping access events into EBO objects, with the right hierarchies and naming conventions
- Building TGML graphics that show doors and readers on the operator’s floor plan — not the vendor’s stock screens, the actual building
- Programming sequences that reference both the door state and the HVAC or lighting side
- Configuring bidirectional alarm sync so access alarms land in the EBO operator alarm view and acknowledgements flow back
- Testing the integration under realistic scenarios — fire alarm events, after-hours access, weekend overrides, lockdown drills, network outages
None of that is a “you pulled the wire, you’re done” task. It’s EBO integration work. It requires an integrator who lives in EcoStruxure Building Operation every day — who has installed and commissioned EBO on other buildings, who understands the object model, who knows the TGML graphics engine, who has written sequences of operations that reference multiple building systems at once.
Security integrators and low-voltage contractors are excellent at what they do. But EBO is not what they do. And when the integration doesn’t happen, the owner ends up with an expensive access control system running as a standalone island — the exact opposite of what Schneider’s integration was built for.
What the BAS integrator brings.
For either product — Access Expert or Security Expert — the integration work sits on the BAS side of the fence. The BAS integrator brings:
- EBO server-side installation and licensing — same platform as the HVAC and lighting integrations
- Object modeling — mapping the access system’s data hierarchy into EBO’s object model correctly the first time
- TGML graphics work — building the floor-plan views that show doors, alarms, and access events
- Sequence-of-operations programming — the actual “if door opens after hours, log the event and check zone temperature” logic
- Alarm bus integration — routing access alarms into the EBO operator alarm view, configuring bidirectional acknowledgement
- End-to-end commissioning — testing the integration under realistic scenarios, not just “does the door open”
This isn’t philosophical. It’s practical. The person who commissions the access control panel is not the person who should be programming EBO. Different skill set. Different toolset. Different daily work.
Athena’s role.
We’re Schneider EcoXpert certified. We install and integrate both sides — the access control layer and the EBO layer.
On design-build projects, we specify the integrated stack up front — Access Expert or Security Expert, matched to the building profile — and take the integration from wire pull through EBO commissioning as one continuous scope. No handoff. No mystery about which contractor owns which piece.
On retrofits, we work with existing EBO deployments and layer new Access Expert or Security Expert onto them. If a security integrator already installed the access control side, we can come in to close the EBO integration gap — but the cleaner path is to have the BAS integrator on the project from the start, before the access control spec gets written in isolation from the BAS spec.
We’re not selling a proprietary integration. We’re the integrator that makes Schneider’s published integration actually work in your building. The wiring, the panels, the network, the credential migration, the sequence programming, the commissioning — all under one roof.
If you’re evaluating.
Two questions worth bringing to the conversation:
- Cloud or on-prem? If your IT team’s answer is “cloud is fine, we prefer it,” Access Expert is likely the fit. If the answer is “no access data leaves the building,” you’re on the Security Expert path.
- Who owns the EBO side? If your BAS is on EcoStruxure Building Operation, or you’re moving to it, have the BAS integrator in the room from the first Schneider access control conversation. Don’t let the access control specification happen in isolation from the BAS specification.
That’s the shape of it.
See both products in action.
Access Expert — Product Walkthrough
Security Expert — Product Walkthrough
