Review evidence, then inspect
From status to the next action.
Read equipment, parts and RONIQ analysis. Record checks and actions.
What needs attention today
See the equipment, issue and next action together.
- Sites
- 1
- Equipment
- 1
- Online
- 1
- Open issues
- 1
- SLA at risk / breached
- 0
The remaining task. The next component to inspect.
Build on manufacturer readings with operating conditions and history, developing analysis that supports the next decision.
Can we finish the remaining task?
A design for reviewing the task and next charging time from a reported charge of 48%.
Explore the assumptions and example →Which component should we inspect first?
A direction that compares the current component's conditions and changes, rather than equipment age alone.
Explore component analysis →From today's priority to the recorded outcome.
AMR-031's battery observation and manually registered motor inspection are separate records. Explore each view of the same asset.
What needs attention today
See the equipment, issue and next action together.
Review evidence, then inspect
- Sites
- 1
- Equipment
- 1
- Online
- 1
- Open issues
- 1
- SLA at risk / breached
- 0
See which equipment needs your attention today
Review the owner and deadline of a manually registered motor inspection, then follow the same asset.
A single age figure does not tell the whole story.
The equipment's service period differs from the current component's. Read observations with their source, replacement history, confirmed causes and maintenance records together.
Explore the product structure →- Operating conditionsObservation time · source · data quality
- Asset and component historyCurrent installation · previous component · replacement
- Human action recordsOwner · confirmed cause · completed maintenance
- Evidence for the next analysisA product direction built on comparison and evaluation
OEM control. RONIQ connects analysis to outcomes.
Bring observations and action history together. Linking predictions to outcomes and evaluating models are the next development stage.
Direct manufacturer delivery
Manufacturer system → RONIQ ingestion API
HTTPS · REST / JSONCollect from existing systems
OEM / FMS → Site Agent · connector
HTTPS GET · MQTT v5 · field mappingBoth paths → normalized operational data
- 01 / Normalize
State · sensors · operation · component history
Preserve source, units, time and quality
- 02 / RONIQ analysis
Pattern changes · runtime · failure risk
Current pattern comparison · prediction design
- 03 / Human decision
Review evidence · assign owner · choose action
Review analysis and follow site procedures
- 04 / Action and outcome
Incident · inspection · maintenance · vendor coordination
Record confirmed cause, action and remeasurement
History supports evaluation. Retraining and deployment require separate authorization and validation.
Product direction diagram · analytical examples are synthetic demos. OEM/FMS retains driving, routing, collision avoidance and safety control.
Keep manufacturer systems. Connect operational evidence.
Connect through direct ingestion APIs or an HTTPS GET / MQTT v5 Site Agent. Extend adapters for additional manufacturer interfaces.
Supported interfaces and integration resources →- RONIQ
- Status, history, analytical evidence and assigned operational work
- Site and support teams
- Review evidence, decide on inspection and maintenance, and record actions. Support scope and hours are agreed separately.
- OEM / FMS
- Driving, routing, safety control and manufacturer diagnosis
Who is RONIQ for?
RONIQ is for companies operating robots and equipment from multiple manufacturers. Its direction connects status, operating conditions and failure and maintenance history to analyze unusual patterns, expected runtime and equipment and component failure risk, supporting human inspection and maintenance decisions.
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.
Is customer data automatically used for shared learning?
No. Customer access boundaries and permitted data purposes remain in place. Learning that connects predictions with action outcomes is a development direction. Cross-customer learning requires separate data-use rights and safeguards.
How do implemented features differ from analytical demos?
Current features cover status, component history, incidents, SLA and maintenance records, plus statistical trial analysis of 14-day observations. Product screens use demo data. Runtime, failure risk, remaining life and outcome learning are distinguished as AI designs.
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.
What is analyzed, and how can the results be used?
Current trial analysis compares the same asset's usual and recent battery discharge rate, network latency and mission duration. People review that evidence to prioritize checks. Runtime and failure-risk analysis using operating conditions and component history is the next development direction. Driving and safety control remain with OEM/FMS.
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.
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.
Start an adoption consultation