Integrations
A machine knows its own state. A transport system knows where a container is. Neither of them knows what is inside it, where it should go next, or why. That gap is what AIMMASS Floor fills — and it is open to anything the mill authorises.
What is available
Field-level specifications — topics, payloads, endpoints and authorisation — go out under an integration agreement. Not because they are secret from your engineers, but because a published schema becomes a contract we cannot change, and this one is still improving.
This is the layer everything else depends on. A handling system that knows only where a container is can route it; one that knows what is inside it can decide.
Transport systems already move bobbins efficiently. What they cannot do is tell you which one caused a problem three days later.
An average tells you the frame is at 97%. This tells you which forty positions are not.
How you get it
Live events as they happen: state changes, alerts, arrivals, breaks. The broker runs on the mill's own network.
For anything that has to react: transport systems, fleet controllers, andon boards, machine interfaces.
Query current state and historical records over HTTP, with the same role-based authorisation the platform uses internally.
For anything that has to reconcile: ERP, MES, quality systems, maintenance planning.
Audit-grade records in standard formats, produced by the same report suite mills are audited against.
For anything that has to be filed: buyer audits, certification bodies, internal quality records.
Who this is for
You move containers reliably, but cannot tell which should go where next, because the container carries no information.
Destination, priority and timing per object, live — so routing becomes a decision rather than a schedule.
A handler needs four things before it can move anything: what is this, what is inside it, where should it go, and when. None of it exists on a spinning floor today.
Exactly those four, on an open bus, with a task model any handler class can consume.
Your machine knows its own state perfectly and knows nothing about the material arriving at it.
Advance notice of what is coming, what is in it, and when the current feed will run out.
Your production record starts at a machine counter and your quality record starts at a lab test. The material in between is a gap you fill with paper.
The gap filled — material movement and state, reconcilable against what you already hold.
How we behave
robot-ready — integration-ready; we work with fleet vendors.
The broker, the platform and the records are all on-premise. Your integration does not depend on our cloud or the mill's internet connection.
You integrate against the same interface the mill's own dashboards use. No partner tier, no gated API, nothing we can change for third parties without breaking ourselves first.
Role-based, granted by the mill on their own deployment. We do not sit between a customer and a vendor they chose.
We are the identity and task layer. We do not manufacture transport systems, carts or robots, and have no plans to.
Tell us what you are integrating and we will send the specification. These conversations are usually short, because the interface is not the hard part — the physics was.