Definitive capability reference

Configured for the operational questions that matter.

Capabilities are not disconnected models. They are observable conditions, event rules, evidence and response workflows assembled within the SHIVMUDRA platform.

01 / Capability pillar

Retail & customer experience

Understand flow, service pressure and opening routines across suitable views.

Operational question

When does a queue persist beyond an agreed condition?

The queue must be visually distinguishable from normal movement.

People CountingHow many people cross a defined line or occupy an area?Read functional detail

ConfigurationDefine a suitable line or zone, direction and operating window.

EventCreates count or occupancy observations.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inEntrances, service areas and multi-location review.

Important dependencyAngle, density, occlusion and image quality affect counting.

Queue MonitoringWhen does a queue persist beyond an agreed condition?Read functional detail

ConfigurationDefine queue zone, minimum presence, duration and schedule.

EventCreates a service-pressure event.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inCheckout, reception, service and dispatch areas.

Important dependencyThe queue must be visually distinguishable from normal movement.

Crowd DetectionWhen does density in a zone exceed a meaningful threshold?Read functional detail

ConfigurationSet the zone, occupancy condition, persistence and schedule.

EventCreates a sustained crowd-condition event.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inEntrances, waiting areas and congestion-prone spaces.

Important dependencyPerspective and normal peak patterns must inform thresholds.

Customer Unattended DetectionIs a customer waiting without staff presence for too long?Read functional detail

ConfigurationDefine customer and staff zones, presence logic and wait duration.

EventCreates an unattended-customer event.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inCounters, help desks and service stations.

Important dependencyRoles and zones must be visually distinguishable.

Store Opening-Time DeviationDid an observable opening state occur in the agreed window?Read functional detail

ConfigurationDefine the schedule and visible opening condition per site.

EventCreates a schedule-deviation event.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inStorefronts, shutters, gates and suitable opening indicators.

Important dependencyThe state must remain clearly visible; calendars and camera health matter.

02 / Capability pillar

Workforce & operations

Surface schedule-aware presence conditions while keeping judgement with people.

Employee Not at Station

Is a defined station unattended beyond an agreed period?

Configure: Set station zone, schedule, expected presence and grace period.
Produce: Creates a station-attendance exception.
Use: Service desks, checkpoints and suitable operating stations.

Breaks, shift changes, shared areas and occlusion shape the rule.

People Presence in Configured Zones

Is someone present—or absent—where presence matters?

Configure: Configure the zone, duration, direction and active schedule.
Produce: Creates a presence or absence event.
Use: Controlled rooms, loading points and service areas.

The condition must be observable without assuming identity or intent.

Schedule-aware Conditions

Did an observable condition occur inside or outside its operating window?

Configure: Link calendars, schedules, zones and persistence thresholds.
Produce: Creates a schedule-aware exception.
Use: Opening routines, restricted access and process checkpoints.

Time synchronisation and accurate schedules are essential.

Multi-site Event Review

Which configured situations across locations need attention?

Configure: Align event categories while retaining locally appropriate rules.
Produce: Organises authorised site events for review.
Use: Distributed retail, facilities and logistics operations.

Connectivity, permissions and site health shape visibility.

03 / Capability pillar

Security & loss prevention

Bring defined intrusion, dwell and sensitive-area conditions to human attention.

Intrusion Detection

Has a person entered a configured restricted area?

Configure: Define zones, directions, schedules, persistence and exclusions.
Produce: Creates an alertable intrusion event.
Use: Perimeters, restricted rooms, stock and operational zones.

Coverage, lighting, occlusion and realistic geometry affect results.

Loitering Detection

Has someone remained in an area beyond a meaningful duration?

Configure: Define the area, dwell time, schedule and normal exceptions.
Produce: Creates a sustained dwell event.
Use: Sensitive perimeters, access points and stock-adjacent areas.

Duration must match normal behaviour and scene context.

Sensitive-area Crowd Conditions

Is density in a sensitive zone high enough to require review?

Configure: Set zone, density, persistence and schedule for the context.
Produce: Creates a crowd-condition event.
Use: Entry control, gates and restricted corridors.

Perspective and normal peak patterns must be understood.

Evidence-supported Alerts

Can an alert arrive with responsible investigation context?

Configure: Agree event types, recipient rules, evidence and escalation workflow.
Produce: Packages a condition for alert or incident handling.
Use: Security, compliance and operating response workflows.

Delivery depends on connectivity and approved notification design.

04 / Capability pillar

Safety & compliance

Support visual checks with site-specific rules, evidence and human-led review.

VALIDATED VIEW

Visual item must be large enough in frame

Uniform ComplianceDoes visible attire meet the agreed condition in the zone?Read functional detail

ConfigurationDefine garment condition, zone, schedule and review threshold.

EventCreates a potential visual-compliance exception.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inKitchens, industrial and controlled operating environments.

Important dependencyGarment visibility, distance, lighting and variation require validation.

Head-Cover ComplianceIs the agreed head-cover condition visually satisfied?Read functional detail

ConfigurationEstablish a suitable view, zone, schedule and permitted condition.

EventCreates a potential head-cover exception.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inCommercial kitchens and suitable production areas.

Important dependencyHead size, angle, lighting and occlusion determine feasibility.

Glove ComplianceCan the camera show whether the agreed glove condition is met?Read functional detail

ConfigurationValidate close-enough views, task zones and expected appearance.

EventCreates a potential glove exception.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inSpecific handling, kitchen or production tasks.

Important dependencyHands are small and often occluded; many views will not be suitable.

Site-specific Visual ComplianceCan another compliance condition be observed responsibly?Read functional detail

ConfigurationDefine condition, evidence standard, exclusions and response during validation.

EventCreates an agreed review event.

EvidenceA timestamped event and relevant visual context can support authorised review.

Useful inCarefully scoped checks outside the standard catalogue.

Important dependencyNot every policy is visually observable; feasibility must be proven.

05 / Capability pillar

Infrastructure health

Watch the cameras, recording and storage foundation that analytics depend on.

NVR Health Monitoring

Is the recording system available and communicating?

Configure: Register supported checks, site identity and communication expectations.
Produce: Creates unavailable, degraded or communication events.
Use: Sites where recording supports security or analytics.

Signals vary by NVR, integration method, network and design.

Camera Health Monitoring

Is a configured camera available with a usable stream?

Configure: Define registration, availability and supported health checks.
Produce: Creates camera-unavailable or supported degraded events.
Use: Single and multi-site surveillance operations.

Detectable conditions depend on stream access and integration.

HDD Health Monitoring

Is recording storage reporting an abnormal condition?

Configure: Map supported storage signals and expected recording design.
Produce: Creates a supported storage-abnormality event.
Use: Sites where recording capacity protects evidence availability.

This is health awareness, not a universal hardware diagnostic.

Site Communication Visibility

Is a site quiet—or disconnected?

Configure: Define heartbeat, last-contact and degraded-operation rules.
Produce: Creates communication-loss and recovery events.
Use: Distributed deployments and remote operations.

Network outages can delay status; offline behaviour is designed per deployment.

SHIVMUDRA watches the operation. SHIVMUDRA also watches the surveillance system supporting it.

Platform-level capabilities

The operating fabric around every selected analytic.

Multiple analytics

Run selected analytics on suitable feeds within the available hardware budget.

Configurable logic

Define zones, schedules, thresholds, durations, conditions and exclusions.

Structured events

Create traceable events with site, rule and timing context.

Evidence snapshots

Preserve relevant visual context according to permissions and design.

Alerts & incidents

Route qualifying situations through an approved human response workflow.

Multi-site visibility

Organise authorised events across sites without pretending local rules are identical.

Health awareness

Bring supported device, recording, storage and communication states into view.

Controlled updates

Refine analytics and configuration through governed change.

Custom workflows

Assess client-specific problems after technical validation.

Suitability depends on camera position, field of view, lighting, occlusion, video quality, scene complexity, connectivity, hardware capacity and responsible configuration.

Start with discovery

Define the operational question before selecting the capability.

We will assess the environment, existing infrastructure, observable condition and intended response before recommending an approach.

Discuss your use case Plan a proof of concept