Event-Triggered Video Integration
When a downtime call fires in ProAlert, any RTSP (Real Time Streaming Protocol) IP camera assigned to that asset automatically captures a pre- and post-event video clip and links it directly to the call log. When a technician opens a work order days or weeks later, the video of the failure is right there... no hunting through NVR footage, no trying to reconstruct the timeline from memory.
The bottom line: Without video, you have a work order. With video, you have evidence. ProAlert's event-triggered capture means every failure is documented automatically the moment it happens... giving your reliability engineers the footage they need for Root Cause Analysis (RCA) months after the event, without requiring anyone to remember to start a recording.
Why Video Evidence Is Missing from Most Failure Analysis
-
NVR footage is overwritten before anyone looks.Network Video Recorder (NVR) systems retain footage on a rolling 7- to 30-day buffer. By the time a recurring failure pattern is identified, the video evidence from the first event is long gone.
-
Manually retrieving video clips is a project.Finding the right camera, the right timestamp, and exporting a clip from an NVR typically requires IT involvement and takes hours. By the time the clip is reviewed, the context of the failure has faded.
-
Video and event data live in separate systems.Even when video is available, connecting a specific clip to a specific downtime event, work order, or scrap entry requires manual cross-referencing of timestamps across two separate systems.
-
No other OEE or CMMS system does this natively.Standalone VMS (Video Management System) products like Milestone XProtect or Genetec have no integration with maintenance systems. ProAlert is the only platform that combines OEE, CMMS, and event-triggered VMS in one product.
How Event-Triggered Capture Works
When a Downtime (DT) call is initiated, ProAlert triggers the recording sequence automatically. No operator action required.
| Step | What Happens |
|---|---|
| 1. Call Initiated | Operator or EdgeSense IoT (Internet of Things) device places a DT call. The call creation event triggers the recording service immediately. |
| 2. Pre-Event Buffer Retrieved | The recording service retrieves the pre-event buffer from the rolling 24-hour footage store. Default: 30 seconds before the call time. Configurable per camera. |
| 3. Post-Event Capture | Recording continues for a configurable post-event window (default: 15 seconds) after the call initiation timestamp to capture the machine's immediate response to the failure event. |
| 4. Clip Processed and Linked | The clip is processed by the background VideoClipProcessingService, a thumbnail is generated, and the clip is linked to the specific DT call record in the database. The push notification "Video Ready" is delivered via SignalR. |
| 5. Accessible from Work Order | Technicians reviewing the resulting Work Order see a "Video Evidence" section with the linked clip. One click plays the footage. No NVR access required. |
Any RTSP Camera Works
ProAlert does not require proprietary hardware. Any IP camera that outputs a standard RTSP stream integrates without additional licensing or hardware.
Storage requirements (typical): H.264 at 2 Mbps for 1080p resolution. Average DT call clip (5 minutes): approximately 75 MB. Annual storage for a typical facility with 1,200 downtime calls: approximately 90 GB. Standard NAS or server storage is sufficient for most deployments.
Playback and Review Tools
ProAlert's video player is purpose-built for failure analysis, not general surveillance viewing.
ProAlert vs. Standalone VMS
Standalone VMS (Milestone, Genetec, Generic NVR)
- Video only — no connection to maintenance or production systems
- $50–$500 per camera licensing (Milestone XProtect)
- Clip retrieval requires IT access to the NVR server
- No link to DT calls, work orders, or OEE data
- Manual review of hours of footage to find relevant events
- Integration with CMMS costs $50,000+ in custom development
ProAlert Video Integration
- Video evidence linked automatically to every DT call
- Any RTSP camera — no per-camera license fees for basic recording
- Clips accessible from the Work Order with one click
- Pre-event buffer captured before the alert even fires
- Mobile playback with zoom, frame-step, and speed control
- Integration cost: $0 — same database as OEE and CMMS
For IT and Physical Security Teams
| Component | Technology | Notes |
|---|---|---|
| Camera Protocol | RTSP (Real Time Streaming Protocol) direct recording via FFmpeg | Direct RTSP connection to cameras without a VMS intermediary. Compatible with any camera that exposes an RTSP endpoint. Milestone XProtect SDK integration also available for existing VMS deployments. |
| Rolling Buffer | Database-backed frame storage (SQL Server) | Configurable buffer duration per camera. Automatic cleanup job removes frames older than the retention window. No separate video server required for standard deployments. |
| Clip Processing | VideoClipProcessingService (background worker) | Polls for pending clip requests every 10 seconds. Exports clip, generates thumbnail, updates clip status, and broadcasts SignalR "Video Ready" notification. Runs on the same server as the web application. |
| Storage | Local filesystem or NAS (recommended) | Storage abstraction layer supports local disk and network-attached storage on your plant network. Cloud object storage is supported on request for facilities with specific requirements. |
| Network Requirements | RTSP access from the recording server to cameras | The ProAlert server (or a dedicated recording server) needs RTSP access to cameras. Standard IP camera network segment access. No inbound camera firewall rules required. |
See a failure event captured on video automatically.
Book a 30-minute demo... we'll walk through a live DT call, show the auto-captured clip, and demonstrate frame-by-frame playback for root cause analysis.