The winning strategy: Layered, vendor‑neutral architecture
How to combine “big ecosystem” stability with “best‑of‑breed” openness—without locking your campus into a dead end.
Short version:
Don’t choose between ecosystem and best‑of‑breed.
Use a layered architecture: ecosystem for building infrastructure, best‑of‑breed for security, and your own vendor‑neutral integration layer on top.
The layered, vendor‑neutral model
Layer 1
Building infrastructure
BMS, HVAC, Fire, Energy
- Long lifecycle, certified hardware.
- Deep integration with building physics.
- Predictable maintenance.
Strategy: Use a major ecosystem here.
Layer 2
Security & access control
Genetec, Mercury, Axis, etc.
- Modern REST APIs.
- Visitor & contractor automation.
- Identity‑driven access.
Strategy: Choose best‑of‑breed.
Layer 3
Integration & workflows
Your logic, your rules
- Visitor preregistration.
- Contractor validation.
- Cloud workflows.
Strategy: Keep this vendor‑neutral.
Layer 4
SCADA / Operator UI / BMS
Desigo CC or similar
- Unified alarms & events
- Doors, HVAC, video in one pane
- Situational awareness
Strategy: Use for visualization, not business logic.
How this balances ecosystem vs best‑of‑breed
- Ecosystem where it’s slow‑moving: BMS, HVAC, fire, energy.
- Best‑of‑breed where it must evolve fast: access control, video, visitor and contractor workflows.
- Your own logic where the business rules live: integration layer, not buried in a vendor UI.
- Unified view without monolith: operator UI that reads from multiple systems instead of owning them.
Key idea:
Don’t ask “ecosystem or best‑of‑breed?”.
Ask: “Which layer deserves stability, which layer deserves agility, and which logic must we own ourselves?”
Practical implications for design decisions
When a vendor says “we’re open”
- Check if “open” means documented REST APIs or just “we have drivers inside our own platform”.
- Ask if write‑access is available without enterprise‑only licensing.
- Verify if you can integrate from your own middleware, not only via their PSIM/BMS.
When choosing access control
- Prefer platforms that expose cardholder, visitor, and access rule management via API.
- Ensure you can drive access rights from external systems (HR, contractors, permits).
- Keep door controllers doing what they’re best at: local, real‑time enforcement.
When designing workflows
- Model workflows (visitor, contractor, maintenance) in your own integration layer.
- Use the ACS and BMS as enforcement engines, not as workflow engines.
- Expose clear APIs so you can swap vendors later without rewriting your business logic.
Conclusion
The safest, most future‑proof strategy is not to “marry” a single ecosystem, nor to bet everything on a patchwork of best‑of‑breed tools.
It’s to design a layered, vendor‑neutral architecture:
- Ecosystem for building infrastructure.
- Best‑of‑breed for security and access.
- Your own integration layer for logic and workflows.
- A unified operator UI that reads from all of the above.
That way, you can change products without changing your philosophy—and your building becomes an evolving system, not a frozen diagram from the day it was commissioned.