These portable demo cases exist to compress the right habits into a repeatable environment: safe bring-up, IO proving, motion basics, alarms, diagnostics and handover discipline without the time pressure and risk of a live customer site.
The value is not a lab-style demonstration. The value is teaching the sequence engineers need when something real has to be powered, proved, moved, diagnosed and handed over properly.
Students learn how to work through a system methodically: power sequence, IO checks, permissives, enable states and the decisions that should happen before first movement.
Motion fundamentals are taught with context: homing, direction, stop behaviour, permissives, interlocks and what the wider control structure has to prove before movement is safe and meaningful.
These rigs make it possible to repeat faults, isolate the cause, test alarm wording and teach a calmer troubleshooting method without risking production equipment or site time.
Students also work through the part most training ignores: logging, acceptance checks, comments, IO references and the documentation habits that make real handovers easier to support later.
The S120 demo case is built to teach commissioning, motion structure, IO and Comfort HMI logging in a way that maps cleanly to real Siemens work. It is not a toy exercise. The platform is structured around supportability, visible machine states and a repeatable bring-up workflow.
That makes it useful both as a teaching platform and as a development environment for testing ideas before they reach production equipment.
The rig can be delivered as a standard non-F CPU with external safety hardware, or as a failsafe variant where the training scope requires it. The key teaching point remains the same: permissives, enable chains, safe readiness and recovery behaviour.
It is strongest where students need a repeatable path through motion commissioning without live-site pressure, or where teams want a safer environment for developing and testing approach before touching production equipment.
Robot training is built around the same principle: teach the structure that survives on live equipment. That means readiness, hold, abort, recovery, IO and handshake behaviour, not just how to make something move.
FANUC Handling, ARC and RoboGuide workflows are covered, with related integration logic and, where required, EtherCAT-based motion concepts that connect robot work back to the wider cell.
The aim is to make robot training useful to the wider cell, not isolate it from the rest of the automation. That means teaching what the robot has to do within the full engineering context.
Training can also be delivered for Siemens PLC, HMI and IO, Siemens motion including S120, Yaskawa handling robots, and broader automation and integration. Use the training page to choose format and delivery style.
Delivery is built around practical exercises so students leave able to commission, diagnose and document work more effectively rather than simply recognising interface screens.
Best when training needs to align closely with real equipment, real constraints and live project context.
Controlled environment using demo cases. Best for focused learning without production interruption.
Structured 4–6 hour sessions focused on workflow, diagnostics and design decisions.
Groups are kept small so the practical element stays useful. Typical delivery is up to 4 students per demo case, with in-person sessions usually running as a full day and online sessions typically 4–6 hours.
See delivery formats, course coverage and how the demo cases fit into the wider training offer.
See how commissioning, motion, retrofit and integration support connect to the training scope.
Read fuller case studies with constraints, decisions, bring-up method and supportable outcomes.
Browse the same capability by discipline and see where the training hardware fits into the wider stack.
The working style behind the demo cases: practical first, structured second, polished third.
Send the stack, the skill gap and the preferred format to define the training properly.
The best first brief includes the PLC, HMI, drive or robot stack, what the team currently struggles with, whether you want demo-case training or live-machine context, and any safety or access constraints that shape delivery.