LIVE FLOOR PLAN
Every robot on your own plant map, moving in real time, with its state and its current mission on its card.
MRF, THE MULTIROBOTFLEET // BY KOVA TECH INDUSTRIES
Your whole fleet. One screen.
Mixed fleets are the reality: an Omron here, two MiRs there, an Otto on the dock, and every vendor ships its own island of software. MRF puts them on one live floor plan, one job queue and one fault list, then connects the result straight into the automation stack you already run.
THE WALKTHROUGH
What you see in two minutes.
- A live floor plan, with every robot moving in real time and its battery, state and mission on its card.
- Dispatch a job and watch it walk pending, sent, executing, completed. Mark a job urgent and it jumps the queue.
- Import the map you already have: Omron MobilePlanner, SEER .smap, ROS map_server files, MiR maps and positions over the MiR REST API, or any floor plan image. Whatever the map declares renders on the floor plan: walls, goals, docks and forbidden areas from a MobilePlanner or SEER file, the floor image and its walls from a ROS or MiR map, and your goal names and MiR positions become dispatch destinations.
- Open the PLC tab for live tag values off the line, then write a setpoint from the dashboard and watch it take effect.
- Point your SCADA at MRF and the whole fleet arrives as a clean OPC UA node tree. That feed is on the Plant tier.
- Open Trends for throughput, job duration, utilization, faults and battery over the last hour, shift or day, exported as CSV.
WHAT IT REPLACES
The floor you have, and the floor with MRF.
| Today | With MRF |
|---|---|
| TodayOne vendor app per robot brand. | With MRFOne dashboard for Omron, MiR and Otto. |
| TodayRadio calls asking whether it is moving. | With MRFEvery robot's live position on one floor plan. |
| TodayA fault noticed when somebody walks past. | With MRFA fault raised, badged and logged the second it happens. |
| TodayPLC data locked in the panel. | With MRFLive tags in the browser, and in your SCADA on the Plant tier. |
| TodayCustom middleware for every new system. | With MRFA REST API and MQTT in the product, and an OPC UA server on the Plant tier. |
CAPABILITIES
What ships in both site tiers.
MRF is licensed per named site in two tiers, Floor and Plant. Everything on this list is in both of them.
ONE JOB QUEUE
One queue for the whole fleet, with priorities. Mark a job urgent and it jumps ahead of the normal work.
FAULTS AS THEY HAPPEN
A fault is raised, badged and logged the second the robot reports it, not when somebody walks past it.
BATTERY, SIGNAL, SPEED
Battery, signal and speed per robot, on the same screen as the map and the queue.
LIVE PLC TAGS
Tag values off the line in the browser, and setpoints you can write back. Every tag carries its own writable flag and the server validates the write, so a safety tag cannot be written from the dashboard.
TRENDS AND CSV EXPORT
Throughput, job duration, utilization, faults and battery over the last hour, shift or day, exported as CSV. The seven day window is on the Plant tier.
MAP IMPORT
Import the map you already have: Omron MobilePlanner, SEER .smap, ROS map_server files, MiR maps and positions pulled over the MiR REST API, or any floor plan image with a two point scale. Whatever the map declares renders on the floor plan: walls, goals, docks and forbidden areas from a MobilePlanner or SEER file, the floor image and its walls from a ROS or MiR map. Goal names and MiR positions become dispatch destinations; on an image or a ROS map you place your own. OTTO sites use the floor plan image.
COMMAND TEMPLATES
Your real robots are dispatched through command templates you configure for them, so each brand is spoken to the way that brand expects.
REST API
A REST API for the systems around the fleet, so MES and ERP hooks read the same data the dashboard shows.
OPERATOR CONSOLE
A tablet friendly surface for calling and cancelling jobs and acknowledging faults, next to a live floor map it can watch but not change.
MRF PLANT
What the Plant tier adds.
The Plant tier adds the automation stack surface: a hosted OPC UA server your SCADA connects to, the seven day trend window, and extended history retention so job history and faults are kept longer. Everything else ships in both site tiers.
Both tiers are licensed per named site, and priced per site on quote.
ADD-ONS
Add what your floor asks for.
The Flight Recorder and the Mission Engine are sold as add-ons on either site tier.
Flight Recorder
The Flight Recorder keeps what your fleet actually did: every robot's position and state, every job and every fault, held on the same PC MRF runs on and replayed on your own floor plan at any point inside the retention window. Traffic maps show you which corridors carry the work.
Replay of a simulated fleet.
Mission Engine
The Mission Engine turns single jobs into missions: an ordered list of steps with conditions, loops, waits, counters, timers, PLC handshakes, operator prompts and error handling. A mission starts by hand, on a schedule, or on a PLC tag, and it drives robots through the same job queue the dashboard already shows.
A sample mission open in the editor, with one run live on a simulated fleet.
IN DEVELOPMENT
MRF 3D
The same map, the same robots and the same jobs, tilted into a navigable 3D view of your floor for control room walkthroughs. It is in development.
BUILT FOR THE PLANT FLOOR
It behaves like plant equipment.
One PC on your network
MRF runs on one industrial PC on your own network. The dashboard is a browser tab on any machine that can reach it, with nothing to install on that machine.
Licensed offline
Signed licence files, no phone-home and no licence server. Nothing outside your building can reach a running floor.
Fail-closed security
The API fails closed rather than open, and the credentials MRF holds for your devices are stored encrypted.
A failed dispatch says failed
When a send does not land, the job is marked failed with the reason. Nothing is reported as sent that was not sent.
Tag quality is tracked
Every PLC tag carries its quality, good, bad or uncertain, so a stale value never gets read as a live one.
An empty window says so
A reporting window with no data in it says it has no data, instead of drawing a zero line across the chart.
Simulated is badged simulated
Simulated data is badged as simulated. The fleet in the screenshots and in the tour on this page is a simulated one.
No invented numbers
MRF computes no cost or ROI figure, because nothing in it measures cost. It exports the measured inputs a costing model needs, and leaves the costing to you.
What it does not do
MRF does not author maps or zones; MobilePlanner, RoboShop and the vendor tools do that. It does not arbitrate traffic between robots; blocking zones and right of way stay in the vendor fleet managers.
Not a safety system
MRF is not a safety instrumented system and must never be part of one. Safety functions stay in your safety rated hardware.
INTEGRATION SURFACE
What it connects to.
Robots
Omron, MiR and Otto, over REST and MQTT.
PLCs
Allen-Bradley over EtherNet/IP, Siemens S7, Omron FINS, and any OPC UA device.
SCADA
A hosted OPC UA server on the Plant tier, tested in shape against Ignition, Kepware and UaExpert.
MES and ERP
A REST API for the systems around the fleet.
THE TOUR
One minute, tab by tab.
REQUEST A DEMO
See it on your own floor plan.
Tell us what you run. We reply the same day with a time and what we need from you.
Ready to see your fleet on one screen?
Book a demo and we will show it on your own floor plan.