Solutions Material transport
Shingo
Automated material transport between storage and the line.
- Status
- In use
- Shape
- Core server and edge clients
- Built with
- Go · Kafka · Postgres
Material That Moves Itself
Material handling is one of the purest forms of waste on a floor. Somebody walks to storage, finds a bin, drives it out, and none of that adds anything to the part.
Shingo takes the request instead. An operator asks for material by type; the system picks the bin, routes a robot, and tracks it through delivery and confirmation. FIFO is enforced by the system rather than by discipline, and every bin carries a QR code scanned at pickup to hold the chain of custody.
Capabilities
Request by typeOperators ask for what they need. The system picks the bin, routes a robot, and tracks delivery.
FIFO by defaultThe oldest eligible material always goes first, enforced by the system.
Chain of custodyEvery bin carries a QR code scanned at pickup to confirm identity.
Survives the networkEdge stations keep tracking local state and queue messages when the link to core drops.
Vendor independentThe robot fleet sits behind an interface, so changing vendor does not touch dispatch.
Related
AndonIn use
Live line status on wall-mounted displays.
- Screen designer — Cells, presses, buffers, arrows, and headers laid out on a full HD canvas.
- Live machine state — Decoded from PLC bitfields and streamed from WarLink.
- Shift aware — Planned minutes per hour, so breaks and planned downtime do not read as faults.
- Runs standalone — Each station runs on its own, with backup and restore from S3 or a central server.
WarLink7 factories
Reads the PLCs and republishes the data everywhere else it is needed.
- Talks to the controls — Allen-Bradley Logix, Siemens S7, Beckhoff ADS, and Omron FINS.
- Publishes upstream — REST, MQTT, Kafka, and Redis.
- Soft UDTs — Raw tags grouped into meaningful structures, so downstream systems are not reading addresses.
- Rules engine — Publishes, webhooks, and writebacks fired on PLC conditions.