Every signal.
Every camera.
One timeline.
DVIS records your plant’s process data, video, operator screens and radio traffic against a single clock — so any event, this morning’s or three years back, replays exactly as it happened.
Be Anywhere.
Unlimited viewing clients, and an access model that decides precisely who sees which cameras and which signals. The plant is wherever you happen to open it.
I am able to check in randomly on critical assets and can monitor the process remotely. The functionality of the user interface is very easy to navigate and the performance of the system is impressive. Shift Manager
Know Everything.
Process data, video, operator screens and radio traffic, all written against one clock — so nothing is missing from the moment you’re looking at.
In my opinion, the main feature of DVIS is having data and video being simultaneously displayed. It honestly helps to troubleshoot problems more than I ever expected. Section Manager, Process Control
Fix Anything.
Replay any event exactly as it happened, this morning’s or three years back, and settle what caused it instead of arguing about it.
With DVIS, you can troubleshoot issues in the present and past with ease. This has saved me countless hours… It also saves the company from unplanned downtime, due to being able to identify and correct issues before they happen again. Electrical Engineer
A process historian tells you a value moved. A camera system shows you footage. Neither alone tells you why. DVIS is both, in one system, on one clock.
It’s built as a set of loggers — each one capturing a different kind of evidence, all writing into the same time-synchronized store. Run the ones you need.
Every tag, at full rate, kept.
Collect from your Level 1 and Level 2 systems — and keep them at full resolution rather than the averaged summaries most historians settle for.
Analog, digital or text: a million time-series per server, trended together, with every point tracing back to the tag it came from.
And if it speaks OPC, DVIS can log it — which, in practice, means almost anything on the floor.
Drivers & protocols
Native drivers: Allen-Bradley ControlLogix · Siemens S7 · GE · GE iFIX · Modbus · OSIsoft PI · MQTT · SNMP · OPC DA · OPC UA · REST · UDP
Beyond those, DVIS is a general-purpose OPC UA and OPC DA client — it connects to any compliant server. Point it at Kepware and its catalogue of 150+ device drivers becomes DVIS signals: PLCs, CNC controllers, drives, meters and building systems, without us writing a driver for any of them.
Nothing about your existing stack has to change, and you aren’t tied to any one vendor’s.
Great tool for troubleshooting PLC programs, enabling me to go back and see what happened to better understand events. BOF Maintenance Engineer, Steelmaking Electrical
Caster strand torques and roll positions, with the hovered point resolving to its source tag
Footage that lines up with the data.
Point DVIS at the IP cameras you already have — 500 or more per system — each recorded at whatever resolution and frame rate that vantage point actually deserves.
Every frame is stamped against the same clock as the signals, so scrubbing the trend scrubs the video.
And every PTZ command is logged with it — so “who panned the camera off the caster, and when?” has an answer.
Cameras & PTZ control
Per system: 500+ IP cameras · Per screen: up to 60 at once · Per camera: resolution and frame rate set independently · Live and historical
ONVIF discovery finds the cameras already on your network and resolves their stream addresses, so commissioning doesn’t begin with a spreadsheet of RTSP URLs collected from four different vendors’ manuals.
On a PTZ camera, shift-click anywhere in the frame and it points there. Shift-scroll drives the optical zoom — real glass, not a digital crop. Presets and home are a keystroke away, and you never leave the layout you were working in.
Because a plant camera pointed the wrong way is its own kind of outage, PTZ is a per-camera permission with configurable travel limits — you decide who can move which cameras, and how far. And every command runs through the DVIS server rather than straight to the camera, carrying the user, the camera and the exact movement with it — which is what makes that history there to read at all.
Being able to research backwards in time quickly, having everything synched. Process Automation Engineer, Plate
Five camera views, every one stamped 8:57:18:003 — the same instant as the cursor on the trends
See what the operator saw.
Video shows what the equipment did. HMI Capture shows what was on the operator’s screen at that moment — which alarms were up, which page they were on, what the interface was telling them.
When a decision looks wrong in hindsight, this is what shows you whether the information needed to make it was actually on screen.
And a frozen HMI looks exactly like a quiet one in a screenshot — so DVIS records the screen’s update rate as a signal, and you can alarm on it.
Capture & health signals
Nothing to install on the operator station. DVIS captures over VNC — RealVNC or TightVNC, single sign-on supported — so the HMI runs untouched. Where a station can host it, Windows Graphics Capture is the alternative.
It records the application, not the desktop. Target a window by name, capture just its client area, or crop to a sub-region — the trend pane, the alarm banner. Frame rate, resolution and bitrate are set per station, so a busy alarm screen and a slow overview don’t cost the same.
Five signals per station, not just a picture. The screen itself, whether the window is minimised, whether it’s been closed, whether the VNC session is connected, and how fast the frame buffer is updating. That last one is the one that matters at 3am: a screen that has stopped repainting is indistinguishable from a calm one until you look at the update rate — and because it’s an ordinary signal, the Automailer can tell you before anyone notices.
Playback of the operator’s screen, beside the video and trends for the same moment.
Radio traffic, on the same clock.
Record radio channels and plant audio alongside everything else. When you replay an incident you hear the crew’s calls as they were made — the part of the record that no trend or camera captures.
Thirty-two audio channels run in our largest deployment, synchronized to the frame.
And you don’t have to sit through the dead air — you can see where the talking was before you play a second of it, and skip or mute everything in between.
What that looks like in practice
Skip silence: jumps past the quiet stretches, every panel moving with it · Suppress silence: plays straight through with the quiet parts muted · Sensitivity and padding: adjustable, so a transmission is never clipped at the front · Per-channel mute
Amplitude is recorded as an ordinary DVIS signal, so it trends on the same timeline as everything else. The spikes tell you where the radio traffic was — scrub straight to them instead of scrubbing through an hour of nothing. That same signal is what finds the silence, and you can draw it as a waveform, an amplitude envelope, or a plain trend.
I would maybe say something about audio as well. Process Automation Engineer, Plate, asked what we should advertise
Waveform above, amplitude trended along the same timeline below — the spikes are where someone spoke
The system tells you. You don’t go looking.
Set a condition on any signal and DVIS emails the people who need to know the moment it’s met — and it doesn’t send a bare alarm code. It sends the trends, the digital states and the camera frames from the event itself.
Your team learns about the problem from their inbox, with the evidence already attached.
And the alerting is a recorded signal too — every trigger, clear and error trends alongside the process that caused it.
Alert rules & attachments
Rules, not thresholds. A trigger is a function — combine signals, do arithmetic, compare against other signals. It must hold for a configurable number of seconds before firing, with damping and rate limiting so a chattering input can’t flood an inbox. Choose one alert per event, reminders while it stays triggered, or silence until it clears.
Attachments are built after the fact. Attach any DVIS component — charts, video, tables — or a rendered web page, captured a set number of seconds after the trigger, so the email shows what happened next rather than only the instant it fired.
Recipients come from your directory. DVIS groups or Active Directory groups, so the on-call list is the one you already maintain. If a rule itself errors, that can raise its own alert — a broken alarm isn’t a silent one.
It watches itself. Triggered, not-triggered, error and mail-sent states are each published as DVIS signals, so “how often did this fire last month?” is a trend, not a mailbox search.
The auto-mailer based on signal values, radio traffic and HMI recordings synced up with real time video and data is a huge asset to us. Caster Electrical Manager
From condition to inbox — the trigger fires, DVIS waits, then builds the evidence and sends it to the group you already maintain
Built the way each person works.
Charts and video arranged however the job needs them, at whatever sizes make sense. Focus a single chart or camera when something needs attention, then drop back to the full view.
Layouts live in two places: a shared server collection everyone can see — the standard screens your plant agrees on, maintained centrally — and each user’s own, which is theirs alone. Standardise what should be standard without stopping anyone building the view they actually work from.
Unlimited viewing clients, and an access model that decides precisely who sees which cameras and which signals.
Custom layout design with various size charts and video. Ability to focus on one particular chart or video in a layout. Replay of charts and video. BOF Maintenance Engineer, asked for the best parts of DVIS
One layout, built for one job — two trend panels and six named cameras, all on the same timeline
Let the video answer on its own.
Point a detector at a camera, draw a polygon around the part of the frame that matters, and DVIS turns what it sees into an ordinary signal — trended on the same timeline as everything else.
Because the result is just a signal, everything already built works on it. Chart it. Alarm on it with the Automailer. Use it in a rule beside your PLC tags.
And it runs backwards. Point a new detector at video you recorded three years ago and it works through the archive to tell you every time the thing happened — not only from today onward.
What it can watch for
Brightness · Variation · Object detection with your own model · Region of interest: polygon mask · Confidence threshold and class filter · Sample rate set per detector
Brightness and variation need no model at all. They measure light and change inside the region you drew, which is often the whole question — is it running, is it glowing, has it moved, has it stopped.
Object detection loads your model and writes what it finds as labels, filtered by class and by confidence. Historical runs process in parallel and report progress as they go, so a season of footage is a job you start rather than a job you sit through.
One region, watched — and what it saw recorded below it as ordinary signals, on the same timeline as everything else
Whatever else your plant is talking to.
Not every source is a PLC. These loggers cover the connections that usually get left out of a historian — and they run on the same modular architecture, so you deploy only what you need.
UDP Logger
Decode datagrams straight off the wire — including GE Ethernet Global Data — by byte offset, filtered by producer and exchange.
SQL Table Writer
Turn DVIS tables into real SQL Server or SQLite tables, created and indexed for you, so your existing reporting just reads them.
Reflective Memory Logger
Read a reflective-memory card directly, mapping offsets to signals — and import your existing iba definitions rather than retyping them.
System Diagnostics Logger
Disk queues, network adapters, CPU and memory recorded as ordinary signals, so server health trends beside the process it’s recording.
Highly flexible modular server architecture … lots of technical data easily available to administrators, allowing us to often fix things without needing vendor support. Process Automation Engineer, asked what we should advertise
And whatever needs to read it back.
The archive isn’t locked behind one client. Everything DVIS records is reachable over HTTP, so your reporting, your data science and your own applications can work from the same record your operators do.
Signal data
Pull time-series over any range, plus current values and signal metadata — analog, digital or text.
Video
Retrieve recorded video for a camera and a moment, addressed the same way as the data beside it.
Components
Ask the server to render a chart or a whole layout, so a report embeds the real thing instead of rebuilding it.
Write back
Push images in from your own systems, and read server health while you’re there.
Our largest deployment, today.
One plant, one system — running on standalone servers or virtual machines, scaled to whatever the site needs.
You’ll be talking to the people who wrote it.
We asked four customers what we should advertise. Three of them led with support. One advantage of a small company is that a feature request reaches an engineer, not a queue.
Awesome product support!BOF Maintenance Engineer
Your customer service to our team has also been very responsive over the years.Caster Electrical Manager
Very fast response on support issues. Excellent two-way communication during feature development — feature requests taken seriously and often acted on quickly.Process Automation Engineer
Any event. Any camera. Exactly as it happened.
DVIS records your plant’s process data, video, operator screens and radio traffic against a single clock. Run the loggers you need.
Get in touch.
Innovative. Proven. Trusted.
With over 40 years of innovation, Industrial Measuring Systems, Inc. pioneers state-of-the-art refractory laser systems, from the earliest solutions to today's most advanced technologies.
