Camera & NVR infrastructure
Suitable existing video and recording systems are assessed—not assumed compatible.
Platform architecture
The intelligence layer between video and action.
SHIVMUDRA connects suitable camera and NVR infrastructure, site-edge processing, configured analytics, evidence, customer visibility and human response.
System flow
From camera view to authorised decision.
This is a functional architecture. It deliberately omits credentials, ports, internal addresses and other confidential implementation detail.
Site edge device
Selected workloads operate near the source according to performance, privacy and resilience needs.
Configured analytics
Zones, schedules, thresholds and conditions translate an operating question into observable rules.
Event & evidence layer
Qualifying conditions become structured events with relevant context.
Customer visibility
Approved server or command views organise incidents, sites and infrastructure health.
Investigation & response
People assess evidence, decide and follow their organisation’s process.
Configuration model
Standard platform. Site-specific operating logic.
01Suitable camera feeds
02Multiple selected analytics
03Zones & schedules
04Thresholds & conditions
05Events & evidence
06Alerts & incidents
07Multi-site visibility
Configuration follows the operating question.
Different sites may require different cameras, rules, zones, schedules, persistence conditions, evidence policies and alert workflows. Controlled updates change that configuration without presenting every site as identical.
- Multiple analytics where a feed and hardware budget are suitable
- Customer-specific event and incident lifecycle
- Device registration and supported health awareness
- Time and data synchronisation according to deployment design
Event to incident
A detection becomes useful only when context and responsibility are clear.
Observe
A configured condition is evaluated.
Qualify
Zone, schedule, threshold and duration rules are applied.
Structure
The event receives site, rule and timing context.
Evidence
Approved visual context supports human assessment.
Escalate
The event follows the agreed alert or incident workflow.
Resolve
An authorised user investigates, decides and records the response.
Parallel operating pillar
Device and system health belong beside analytics—not beneath them.
A quiet feed and an unavailable feed are not the same operating state.
SiteOperational context
NVRRecording & communication
Camera 01Selected stream
Camera 02Selected stream
HDDRecording storage
Edge intelligenceAnalytics & events
Illustrative system state
Healthy
Expected communication and supported health checks are available.
Privacy, ownership & resilience
Architecture choices respect the deployment boundary.
Client video and operational data remain client property.
Access, evidence and retention follow the approved deployment and NVR design.
Suitable processing remains near the source where practical.
This can improve responsiveness, privacy and resilience; it does not imply every operation is always offline.
Offline and communication-loss behaviour is designed explicitly.
Connectivity, local capacity, alert delivery and recovery expectations are part of site assessment.
Suitability depends on camera position, field of view, lighting, occlusion, video quality, scene complexity, connectivity, hardware capacity and responsible configuration.
Start with discovery
Discuss the infrastructure you have—and the operating outcome you need.
We will assess the environment, existing infrastructure, observable condition and intended response before recommending an approach.