
Holding architecture: VMS + NVR
Center β Watcher VMS (private cloud). In shop floors β Watcher NVR appliances for process recording and local archive.
Two layers for a multi-site holding
Design Watcher VMS as the private-cloud center and Watcher NVR appliances for process recording in each shop floor or plant.
Center β Watcher VMS
- Unified access across plants and roles
- API and integrations (ACS, analytics, B2G)
- Security policies and federation of sites
Edge β Watcher NVR in shop floors
- Local process recording on the site
- Shop-floor archive and resilience if the WAN drops
- Ready appliance with a predictable quote per floor
Typical scheme
Holding center runs Watcher VMS. Each plant or shop floor runs one or more Watcher NVR appliances that record locally and connect to the center.
When to choose holding architecture
Holding / several sites
You need a single control plane, shared policies, API and process recording that survives locally in each shop floor β design VMS + NVR.
One shop floor only
No holding center yet β a Watcher NVR appliance for process recording is enough. You can attach VMS later when the company grows.
Go to Watcher NVRWhat the designer gets
Clear security boundary
Policies and integrations live in the VMS center; shop floors keep resilient local recording.
Scalable by shop floor
New plant or shop floor β add another NVR appliance without redesigning the whole VMS.
Spec you can put in a tender
Separate center and edge scopes so procurement and CAPEX stay predictable.
Holding architecture review
Tell us sites count, shop floors and roughly how many cameras. We will propose a VMS + NVR layout for the holding.
Request: Watcher VMS + NVR for a holding
Leave contacts and brief scope β we will prepare an architecture sketch for designers.