Learn when to use VideoMon, Smart Wall, Matrix or native XProtect rules to control Smart Client displays from HMIs and automation platforms.
Control rooms rarely operate through video alone.
Operators may be working with alarm systems, access control, industrial HMIs, transport-management platforms, building-management systems and other operational tools alongside Milestone XProtect.
When one of those systems detects a problem, it may already know exactly which cameras the operator needs to see.
The difficulty is getting that information onto the correct XProtect Smart Client display without asking the operator to manually find the cameras, build a view and move it to the correct monitor.
This is where externally controlled display management becomes useful.
The design question
Which system should own the display logic: Milestone XProtect or the external control system?
What Does External Smart Client Control Mean?
External Smart Client control means that a system outside XProtect can decide what appears on one or more XProtect Smart Client displays.
That external system might be:
Industrial HMI or SCADA
Process, production and operational control systems.
Building Management
Plant, environmental, fire and facilities alarms.
Alarm Management
Platforms coordinating security and incident workflows.
Transport Control
Rail, road, airport and wider transport-management systems.
Touch Panels
Hardware controllers and operator consoles.
Custom Applications
Bespoke dashboards, PSIMs and command applications.
Rather than simply telling XProtect that an event has occurred, the external system can issue a much more specific instruction.
Display cameras 12, 15 and 18 on workstation Bravo, monitor 2, using a two-by-two layout. Place camera 12 in the first tile and show it fullscreen.
That is a different requirement from creating an alarm or triggering a recording rule. The external system is not only reporting that something happened. It is controlling the operator's display environment.
Start by Deciding Who Owns the Display Logic
Before choosing a product, establish where the operational logic already lives.
If XProtect knows that an alarm has occurred and XProtect rules determine which cameras should be displayed, the native Milestone tools may be the simplest route.
If an external HMI or automation platform already manages the wider operational workflow, it may be more sensible for that system to control the XProtect displays directly.
Start With the Native XProtect Options
As with most integrations, the best starting point is the least complex option that can meet the operational requirement reliably.
Native video wall
XProtect Smart Wall
Best where Milestone should manage a collaborative video wall, presets, mixed content, rules and operator-driven workflows.
Lighter camera push
Matrix
Useful where a rule or operator needs to send selected cameras to a predefined recipient or Matrix position.
Milestone-owned automation
Rules and Events
Suitable when the external system only needs to create an event and XProtect should determine what happens next.
Bespoke in-client workflow
MIP Plug-in
Appropriate where the project needs a new Smart Client tab, panel, view item, search tool or guided operator workflow.
Use an event when XProtect should decide what happens next. Use external display control when the external system must decide exactly what the operator sees.
Where Does VideoMon Fit?
VideoMon sits between an external control system and the XProtect Smart Client displays.
The external system sends a command using TCP, UDP or serial communications. VideoMon processes that command and applies the requested action to the appropriate Smart Client workstation and monitor.
The external system does not need to reproduce the complete XProtect interface or stream the video itself. It only needs to tell VideoMon what the XProtect displays should do.
External HMI or automation platform → VideoMon → XProtect Smart Client workstations → Connected monitors
This is particularly useful where the external platform already contains the operational logic.
An industrial HMI may already know which production line has stopped, which alarm has been raised, which cameras cover the affected machinery, which workstation is responsible and which display layout the operator needs. VideoMon provides the practical link between that operational knowledge and the XProtect display.
What Can VideoMon Control?
Flexible Grid Layouts
Create square or rectangular grids that match the situation rather than relying on one permanent view.
Workstation and Monitor Addressing
Target specific Smart Client workstations, monitors, rows, columns and display tiles.
Camera Assignment
Add or remove XProtect cameras from individual display positions using configured identifiers.
Fullscreen Control
Place a selected camera or tile into fullscreen mode when an incident demands immediate attention.
PTZ Control
Control supported PTZ movement, zoom and preset-related actions from the external workflow.
Smart Client Monitoring
Identify enabled workstations and view connection state, hostname, network information and monitor count.
Configuration Export
Export camera identifiers and detected Smart Client information to simplify external-system configuration.
Remote Client Actions
Refresh or restart supported Smart Clients remotely where dedicated display workstations require maintenance.
Exporting identifiers may sound like a small feature, but it avoids a surprising amount of commissioning pain. A single mistyped camera identifier can otherwise turn a straightforward control-room workflow into a very confusing afternoon.
Practical VideoMon Use Cases
Transport
Transport Control Rooms
Display platform, entrance, concourse and PTZ cameras automatically for passenger assistance, trespass, lift faults or trackside incidents.
Industry
Manufacturing and Process Control
Present the cameras associated with a production line, machine, safety zone or loading area when an HMI detects a fault.
Facilities
Building Management
Show relevant cameras for fire alarms, plant-room faults, environmental alarms, lift failures or power and cooling incidents.
Security
Alarm and Access Workflows
Use an external workflow to select the correct views for intrusion alarms, access events, perimeter systems and other security incidents.
Example: Intrusion Alarm to Operator Display
- An intrusion alarm is received.
- The external platform identifies the affected zone.
- It selects the associated cameras and target workstation.
- VideoMon creates the display layout and places the cameras.
- A PTZ camera moves to the relevant position where required.
- The operator verifies the incident while the wider workflow continues in the external platform.
VideoMon Versus XProtect Smart Wall
VideoMon and Smart Wall overlap in one obvious area: both can change what appears on control-room displays. However, they approach the problem from different directions.
Choose Smart Wall When
- XProtect should own the wall configuration.
- Operators need a native, shared video wall.
- Maps, messages, alarms and other content must appear alongside video.
- XProtect rules and presets can drive the required behaviour.
- Operators should manually send content to the wall.
Choose VideoMon When
- An external platform should own the display logic.
- TCP, UDP or serial command control is required.
- Individual workstations and monitors must be addressed.
- Camera placement must be controlled at tile level.
- The display layout must be built dynamically.
This does not have to become a contest between the products. A customer may use Smart Wall in a central security control room and VideoMon-controlled Smart Clients in industrial, transport or operational workstations elsewhere on the same estate.
The correct choice depends on who owns the operational logic and what the displays are expected to do.
When Is VideoMon Not the Right Answer?
Saved Views
A normal saved Smart Client view already solves the problem.
Matrix
A single Matrix recipient provides the required result.
Smart Wall Presets
Native presets already provide the required automation.
Simple Events
The external system only needs to create an alarm or event.
Custom Workspace
The project needs a complete bespoke workflow inside Smart Client.
Video Ingestion
The real problem is bringing in or distributing the video source.
A bespoke MIP plug-in may be more appropriate where the customer needs a new Smart Client tab, custom side panel, specialist view item, guided operator workflow or investigation tool.
Likewise, if the difficult part is bringing an unusual video source into XProtect, the project may need Streamforce, ORB Driver or another media integration rather than VideoMon.
Display control should not be used to solve a video-ingestion problem wearing a false moustache.
How VideoMon Fits With Other ORBNET Products
VideoMon can form one part of a wider XProtect workflow, but each component should still have a clearly defined job.
Event Gateway
Receives and normalises external alarm events that may start the wider workflow.
ORB Driver
Presents supported external video sources as usable XProtect camera channels.
Streaming Engine
Acquires, converts, routes and distributes remote or non-standard video sources.
VideoMon
Controls where the resulting XProtect cameras appear on Smart Client displays.
In a remote-video workflow, Streaming Engine may move and transform the video, ORB Driver may bring the source into XProtect, and VideoMon may then control where the camera appears. The products are complementary because they solve different parts of the chain.
Security and Network Design
Externally controlling security displays should be treated as an operationally sensitive integration.
The command path should not simply be exposed to any device that can reach the network. The design should define:
Command Sources
Which systems are allowed to issue display commands.
Target Clients
Which workstations and monitors may receive them.
Network Path
Which protocols, ports and network zones are involved.
Remote Connectivity
How links across untrusted networks are protected.
PTZ Authority
How external control and operator priority are managed.
Logging and Recovery
How failures are recorded and what happens when the controller is unavailable.
TCP, UDP and serial connections have different characteristics. TCP may suit an established connection where ordered delivery is useful. UDP can provide simple, low-overhead command delivery, but does not inherently confirm delivery. Serial remains relevant in industrial environments and control rooms where established systems still use RS-232 or serial gateways.
The protocol should be selected based on the existing system and operational requirement, not because one acronym looks more futuristic on an architecture diagram.
What Should Be Defined Before Deployment?
✓ Operational Outcome
Specify the target workstation, monitor, layout, camera positions, fullscreen behaviour and what happens when the incident ends.
✓ Workstation and Monitor Naming
Create a stable naming convention for hostnames, workstations, monitors and control-room positions.
✓ Camera Identifiers
Agree how cameras will be referenced and how renamed or replacement devices will be handled.
✓ Protocol and Network Path
Confirm TCP, UDP or serial settings, source and destination, firewall rules, segmentation and recovery behaviour.
✓ PTZ Behaviour
Define presets, continuous movement, operator override, priority and return-to-home behaviour.
✓ Failure Handling
Test offline Smart Clients, disconnected monitors, unavailable cameras, repeated commands, service restart and network interruption.
✓ Acceptance Criteria
Measure workstation selection, grid creation, camera placement, response time, PTZ operation and recovery after restart.
✓ Support Ownership
Define who supports the external system, VideoMon, XProtect and later changes to identifiers or network rules.
A successful acceptance test should prove more than “the camera appeared once”. It should also prove predictable behaviour during failure, restart and recovery.
Conclusion
VideoMon is not simply another way to build a video wall.
It allows the system that already understands the operational situation to control what the operator sees inside XProtect Smart Client.
For Milestone-managed collaborative video walls, XProtect Smart Wall remains the natural starting point.
For simple event-driven camera presentation, Matrix or native XProtect rules may already be sufficient.
VideoMon becomes particularly useful when an external HMI, automation platform or control system must control specific Smart Client workstations, monitors, grids and camera positions using TCP, UDP or serial commands.
The deciding question is not “Do we need a video wall?” It is: Which system should own the display logic?
Frequently Asked Questions
What is VideoMon for Milestone XProtect?
VideoMon is an ORBNET integration that allows external HMIs, automation platforms and control systems to manage XProtect Smart Client displays using TCP, UDP or serial commands.
Does VideoMon require XProtect Smart Wall?
No. VideoMon can control supported XProtect Smart Client displays without requiring XProtect Smart Wall.
Does VideoMon replace XProtect Smart Wall?
Not necessarily. Smart Wall is Milestone's native collaborative video-wall solution. VideoMon is aimed at projects where an external system needs command-driven control of Smart Client displays.
Can an alarm automatically change an XProtect display?
Yes. Native XProtect rules can change Smart Wall content or send cameras to Matrix recipients. VideoMon becomes useful when an external workflow platform needs more precise control over workstations, monitors, grids and individual tiles.
Can VideoMon control several monitors?
Yes. VideoMon can address individual enabled Smart Client workstations and their connected monitors.
When should I use a custom MIP plug-in instead?
A custom MIP plug-in is usually more appropriate when the requirement is a bespoke Smart Client workspace, side panel, view item, search tool or operator workflow rather than external command-based display control.
ORBNET Systems
Need to Connect an External Control System to XProtect Displays?
ORBNET can help assess whether your requirement is best served by VideoMon, Smart Wall, Matrix, native XProtect automation or a custom integration.
Explore VideoMon