Sheet 01/10General schematic
PLC + OT + ITIndustrial softwareBased in Pamplona
We are commissioning engineers who also write code. We connect your PLCs, your OT systems and your IT so machine data reaches the people who make decisions.
Shop-floor experience in commissioning and international projects.
Line controller
What we do · FB 01 · FB 03We program it and publish its data without touching the logic.
Line controller
What we doWe program it and publish its data without touching the logic.
ExampleTap a component in the cabinet
ExampleDrag to rotate the cabinet · tap a component
Alarm viewer
4 active · 4 unacknowledged
Help text
Counters, temperatures, alarms: it is all in the controller. To see it, someone has to walk to the machine with a laptop.
Help text
One side talks about data blocks and cycle times; the other, about APIs and databases. In between: stalled projects and spreadsheets nobody maintains.
Help text
Planning relies on what the ERP says or what the shift supervisor remembers. What the line actually did yesterday is nowhere to be found.
Help text
The machine stops, gets reset and carries on. Nobody writes down why. Next week it happens again.
Fixing it takes someone who understands the machine and writes the right software for it. That is what we do.
See what we doEach service works on its own or as part of a complete project. We start with whatever hurts most.
We program PLCs, HMIs and drives for new and existing machines: sequences, interlocks, recipes, alarm handling and PID loop control. Clean, commented and documented code your maintenance team can follow.
Inputs
Outputs
We read your PLCs, sensors and equipment. We store every value with its line, shift, batch and recipe, and turn it into history, KPIs and alarms that help you make decisions with the right context.
Inputs
Outputs
We connect the machine level to the business level: OPC UA, MQTT, Modbus, databases, ERP and MES. Without touching what already works, and keeping the plant network safe. If the machine is old, we retrofit it so it can communicate.
Inputs
Outputs
Web apps built for the people who will use them: the operator on the line, the shift supervisor, maintenance or management. Plant dashboards, downtime logging, digital work orders and traceability.
Inputs
Outputs
Combinatorial optimisation algorithms to sequence orders, cut changeovers and assign machines and shifts. Plans that respect the real constraints of your plant.
Inputs
Outputs
We start up machines and lines on site: signal checks, loop and drive tuning, validation with production and training for operators and maintenance. Afterwards we provide on-site and remote support when something fails or needs changing.
Inputs
Outputs
Not sure where to start? We'll work it out during the plant visit.
Request a visitWe have spent many hours next to machines, starting up lines. We know a stoppage costs money and software cannot be one more problem. So this is how we work:
We come to your factory, walk the line and talk to operators, maintenance and IT. No sales presentations.
Transition ·problem understood
We review which signals exist, where they are and what is missing. You get it in writing: what we would do, in what order, what it costs and which risks we see.
Transition ·scope agreed
We build a first, limited version with real data from your plant. If it doesn't add value, you'll know early and without spending much.
Transition ·validated on site
We install it, train your team and leave it documented. Then we stay around: support, adjustments and new features.
Transition ·new need
↺ back to step 1
We have programmed PLCs, tuned PID loops, checked electrical cabinets and commissioned complete lines. Now we use that experience to build software that works on the shop floor from day one. We show up with a laptop and a multimeter, not a slide deck.
Before founding Sandbox Dynamics, the team worked on commissioning and international projects.
Motor M1 start with seal-in
The same, in code
// Motor M1 start with seal-in
"Motor_M1"FALSE := ("Start"FALSE OR "Motor_M1"FALSE)
AND NOT "Stop"FALSE
AND NOT "Fault_FC1"FALSE;Press Start and let go: the motor keeps running thanks to the seal-in contact. Just like on a real panel, the pushbuttons act while you hold them down.
Program · Why us
Each reason written as a PLC rung: when its conditions hold, the output switches on.
Data blocks and cycle times with your integrator. APIs, networks and databases with IT.
Try it: the same logic, in your PLC's ladder diagram and in code.
We test outside production, plan every change and always leave a way back.
You talk to the people who design and code your solution. No sales reps, no middlemen.
Our base is in Pamplona, but we work wherever we are needed. When required, we come to your plant.
Sandbox Dynamics
Micro-cooperative
EX-01 · Packaging · FB 02 · FB 04
ExampleContext
Packaging line with several machines and controllers from different generations.
Challenge
Stoppages were written down by hand at the end of the shift. Nobody knew which machine stopped most, or why.
Before: Stoppages written down by hand at the end of the shift
After: Every stoppage logged as it happens, with machine and time
Before: Causes that depend on each operator's memory
After: The operator confirms the cause on a line-side screen
Before: Meetings that argue about opinions, not data
After: Shift report with the causes that cost the most time
Architecture
We read states and alarms from every PLC and log each stoppage with its cause as it happens.
What we deliver
How we measure the result
Sound familiar?
These are the technologies we work with, arranged by plant level (ISA-95). Tick the ones you have and we'll tell you where we would start.
We are a micro-cooperative of engineers based in Pamplona. The person who visits your plant is the person who then codes the solution.
Co-founder
Co-founder
No commitment. An engineer, not a salesperson, will get back to you.