Sunshine State Automation makes conveyor, sortation, scanners, print and apply, scales, dimensioners, robotics cells and your WCS or WMS behave as one system instead of six vendors pointing at each other. New builds, expansions and brownfield tie-ins into buildings that cannot stop running.
Every vendor's demo works on the happy path. Integrations fail on the other days: the host returns a destination that no longer exists, a scanner no-reads three cartons in a row, a network segment drops for four seconds, an operator hits an E-stop mid-transaction. Deciding what the system does in each of those cases is the actual engineering.
WCS and WMS messaging: formats, handshakes, sequencing, retries and reconciliation. Including what the floor does when the host goes quiet and how the two agree again afterward.
Barcode scanners and scan tunnels, print and apply, scales and dimensioners, weight and volume capture, light stacks, andons and operator terminals.
Transport, induction and buffering between conveyor and the systems it feeds: sorters, palletizers, robotics cells, goods-to-person stations and pack lines.
Product tracking that survives the whole path, exception queues someone can actually work, and a record of what happened that holds up when operations asks the next morning.
Sequencing the tie-in so production keeps running. Which weekend, which lanes, what falls back if the new path misbehaves, and who makes the call at 3am.
Drawings that match the enclosure, interface specs your IT group can read, and training for the maintenance team who owns it after we leave.
Most integration work is not a greenfield building. It is an expansion into an aisle that is currently running, on controls conventions somebody else chose years ago, with a maintenance team who will inherit whatever we leave behind.
Integration work keeps arriving at the same place: a building running a WMS, a control system, an execution layer and a quantity of custom glue code that nobody is willing to own, with a throughput problem that belongs to whichever vendor is not in the room. The category labels do not help: where a control system ends and an execution system begins turns out to depend entirely on which vendor you ask and what they already sell.
OIP is our answer to that. A modular control and execution layer for conveyor and sortation, written by the team that designs, fabricates, programs and commissions the equipment underneath it, so the seam that usually causes the damage is not a seam at all. It is taken module by module: a sortation supervisor and an operator interface is a complete scope, and your system of record stays exactly where it is. OIP is in active development, which we would rather state plainly than imply otherwise.
It means making equipment from different vendors, and the software above it, behave as one system. Conveyor, sorters, scanners, print and apply, scales and dimensioners, robotics cells and the WCS or WMS all have their own idea of what is happening. Integration is deciding who is authoritative, what happens when they disagree, and what the system does when one of them stops answering.
Yes. We build and support the interface between the floor and the host: message formats, handshakes, retries, reconciliation, exception handling and the behavior when the host is slow or silent mid-shift. The exception paths are where integrations fail, so that is where we spend the design time.
Yes, and we often do. Some of our work is controls scope inside somebody else's larger project. We are comfortable being the controls partner on a job where the mechanical scope belongs to another vendor.
Yes. Expansions and retrofits into a live building are a large part of the work: sequencing cutover so production keeps running, tying new controls into existing panels and networks, and matching the conventions already in the plant so your maintenance team is not learning two systems.
We integrate conveyor and controls with those systems rather than supplying the robots themselves: the transport, induction, buffering and handshakes that connect them to the rest of the building. Our team's field experience includes working alongside robotics and goods-to-person deployments in live distribution centers.
Tell us what has to talk to what. We will tell you where it is likely to break and what it takes to make it one system.