RONIQ for companies operating robots from multiple manufacturers
Robots from many manufacturers. One operating flow.
Bring status together, collaborate on incidents and connect maintenance history. Help site teams, operations support and manufacturers review evidence and the next action together.
A platform for managing operations. Support scope and hours are agreed separately during consultation.
Console: REST, MQTT and SIMULATOR registration, field mapping and tests. Additional manufacturer interfaces can be integrated through adapter extensions. OEM/FMS safety and driving control remain unchanged. This is an example operating data flow.
REST, MQTT, SIMULATOR and field mapping are currently supported. Real manufacturer integrations and AI observations are validated separately with customer-environment data.
OPERATIONS IN PRACTICE
From an observed issue to a recorded resolution
Follow one issue at a fictional logistics site to see how observations and people's actions stay connected.
Issue detail · historical record
EX-101 / Charging contact inspection
Resolved · RESOLVED
Asset
AMR-017 · Logistics site A
Owner
Support owner A
Current example time
10:45 · OEM NORMAL
Action timeline
The states below show the historical sequence. EX-101 is now resolved and is excluded from the open-issue count.
01
Observe an unusual state
Review started
Input
AMR-017 · OEM charging-check state · 09:10
Owner
Site operator
Next action
Check site access conditions, then review the source state and observation time
02
Review the evidence
Evidence reviewed
Input
Synthetic REST data · OEM state · quality VALID · sample-1
Owner
Site operator · support team
Next action
Attach observations to the issue. No automated control or safety decision by RONIQ
03
Record the issue and assign an owner
Acknowledged · ACK
Input
EX-101 · Charging contact inspection
Owner
Support owner A
Next action
Request a site check and review the example response target of 09:40
04
Consult the manufacturer when needed
Inspection procedure confirmed
Input
State record · site inspection record · fictional consultation note
Owner
Support team · manufacturer contact
Next action
Relay the manufacturer's inspection procedure to the site. This is a sample consultation record, not a live integration
05
Record the outcome
Resolved · RESOLVED
Input
Contact inspection record M-101 · OEM NORMAL rechecked
Owner
Recorded by site operator · reviewed by support owner A
Next action
A person records the resolution and links the maintenance history
Synthetic data and illustrative screen layout. This does not represent a customer case, measured results or completed manufacturer integration. Times and response targets are fictional, not a response-time guarantee.See what each role needs to review ↗
Service scope001
Clear responsibilities. Connected response.
RONIQ is a platform for managing operational work. If you need operations support, its scope and support hours are agreed during the adoption consultation.
01
Work managed in the platform
Review robot status and source data, track issues and assignees, record responses and manufacturer discussions, and connect maintenance plans with work history.
02
Operations support team
Review issues and follow up on assignees, response targets and manufacturer escalation within agreed customer and site assignments. Support methods and hours are agreed separately.
03
Customer and manufacturer
Customers check the site and record actions; manufacturers handle technical diagnosis and repairs. Safety decisions, driving and control remain with the existing robot and FMS.
The product is currently being implemented and validated. Commercial availability and conditions for your environment are confirmed during consultation.
ImplementedCore operational work
Assets, issues, assignees, response history, maintenance plans and work history. Connection and operational validation in your environment are carried out separately.
Under validationManufacturer connections and AI observations
Validate manufacturer-specific HTTPS GET and MQTT v5 connections and data quality. Synthetic trials and example screens do not establish real manufacturer integration or analytical performance.
PlannedFault prediction and RUL maintenance advice
Later scope requiring separate real-world validation. These are not offered as current features or guaranteed results.
Why RONIQ002
More robots bring more operational complexity.
Scattered portals, fault codes and maintenance history make it harder to find the information and next response you need.
01
Vendor Silo
Different portals and data structures for each vendor
02
Reactive Support
Response beginning only after a problem occurs
03
Fragmented History
Scattered incident, maintenance and part replacement history
04
Operator Gap
Different operating teams and procedures at each site
How it works003
OEM control. RONIQ operations.
Existing OEM/FMS retains safety, driving and route control. RONIQ connects operating data, observations and response processes.
01
Connect
HTTPS GET and MQTT v5 collection, Site Agent and field mapping
02
Observe
Review source, timestamp, quality and normalized status
03
Respond
Respond through incidents, SLA, vendor escalation and maintenance
Clarify the boundaries of control, integration, analysis and inquiries.
Who is RONIQ for?
RONIQ is an operations platform for companies operating robots from multiple manufacturers. It helps connect status review, incident response collaboration and maintenance history in one workflow.
How do the platform and operations support differ?
The platform manages status, evidence, issues, assignees and maintenance history. The support team's scope, methods and hours are agreed separately during consultation. Customers perform site checks; manufacturers perform technical diagnosis and repair. No round-the-clock response or SLA guarantee is promised.
What is implemented and what still needs validation?
The product is in implementation and validation. Basic operational workflows are implemented; real manufacturer connections and AI observations need validation in each customer environment. Fault prediction and RUL maintenance recommendations are future plans. Commercial availability and applicability are confirmed during consultation. Screens use synthetic data.
Does RONIQ replace the FMS or robot control?
No. Existing OEM/FMS retains safety, driving and route control. RONIQ connects status, events, operating incidents and response history.
Which interfaces are supported, and how are integrations extended?
Currently supports HTTPS GET (JSON/NDJSON, optional Bearer), MQTT v5 (QoS 1, TLS), and Site Agent encrypted buffering and retry. The console manages REST, MQTT and SIMULATOR registration, field mapping and tests; URLs, authentication and topics are set in Agent configuration files. Additional manufacturer interfaces can be integrated through adapter extensions and connection tests. Completed manufacturer integration is validated per customer environment.
Does AI guarantee fault predictions or maintenance timing?
Initial observations are trials reviewed with quality, coverage, evidence and reasons for insufficient data. Unvalidated SOH, RUL and fault predictions are not confirmed results; cross-customer comparison is later scope.
What information helps start a review?
Email ayden@bnbcompany.io with site and robot counts, manufacturers, models and FMS, your first operating priority and the support scope you need. Unknown items can remain blank. Scope, connection conditions and support hours are agreed separately.
GET STARTED
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.
