The operating flow, brought together.
From connections and assets to incidents, SLA, maintenance and evidence. Explore the work RONIQ supports.
A common framework for robot data
Retain original REST, MQTT and Site Agent data and normalize status and events. Review mapping versions and quality without filling missing data with normal values.
Actual supported interfaces are checked separately for each robot/FMS.
Connection approachSites and robots in context
Connect assets, manufacturer, model and installation information with current status. Separate OEM status from derived RONIQ observations and show observation time and source.
Operating views are limited to current customer and site assignments.
Product structure| Robot | Site | OEM status | RONIQ observation |
|---|---|---|---|
| AMR-017 | Site A | OEM NORMAL | Review observation |
| AMR-023 | Site A | OEM NORMAL | Insufficient data |
| Cleaning-04 | Site B | OEM PAUSED | Review incident |
From an incident to the next response
Connect acknowledgment, diagnosis, explicit escalation and resolution in one operating history. Review four timers using the SLA targets and support hours fixed at occurrence.
SLA does not pause automatically while waiting for a vendor.
Operating process| Event | Status | Next review |
|---|---|---|
| Review communication status | ACK | Explicit diagnosis completion |
| Review charging warning | INVESTIGATING | Review vendor escalation |
Connect maintenance schedules and work history
Connect scheduled, in-progress and completed work with assignees, due dates and part replacements. Review upcoming and overdue items and record work actually performed and its outcome.
Automatic purchasing and unvalidated RUL advice are not initial features.
Operating featuresPreserve the context of vendor collaboration
Link contract and warranty summaries and contact channels to operating events. Assigned operators review explicit escalations and response history.
Assess actual vendor response performance only after checking linked evidence and validation criteria.
Vendor collaborationObservations and evidence you can assess
Show observation quality, coverage, analysis version and reasons for insufficient data. Do not invent results when data is inadequate; show 'Insufficient data'.
SOH, RUL, fault prediction performance and cross-customer comparison require separate validation and remain later scope.
AI observation boundariesSeparate OEM status from RONIQ observations
SOH, RUL and fault prediction are not provided as confirmed results before validation.
Start with the robots you have.
A new way to operate.
Tell us about your robots, FMS and operating needs. Together, we check the environments that can connect.
Contact us