George Pickering
Controls • Motion • Robotics • Stage Engineering
Siemens IO and motion engineering hardware
Portfolio • By discipline • Scarborough, UK • Worldwide

Browse the work by discipline, not just by finished machine.

Most real projects cross several layers at once: mechanical decisions affect wiring, electrical architecture changes commissioning time, software structure changes recoverability, and diagnostics shape whether a team can support the system properly later. This page separates the capability so it is easier to see where depth sits and how the pieces fit together.

Best use Find the layer of work that matters most first, then drill into examples and scope.
What it shows Capabilities, deliverables, tooling, engineering priorities and linked project context.
How projects behave Most outcomes combine several disciplines even if the entry point looks narrow at first.
Main standard Buildable, traceable, recoverable and supportable systems rather than one-off fixes.

How the disciplines connect

This is the quickest way to understand the portfolio properly: start with the layer you recognise, then follow how it interacts with the others in a real engineering outcome.

Portfolio by discipline

Pick the track closest to the work you need. Each page goes deeper into capability, typical deliverables, tools and selected examples.

Automated packing outcome
How to read the discipline pages

Pick the closest entry point, then follow the crossover.

Most visitors arrive thinking they need one thing: electrical help, PLC software, a robot cell, a panel, a server setup or a mechanical change. In practice the best outcomes nearly always sit across several layers.

That is why the discipline pages stay specific while still linking back to projects and services. The pages are there to make the scope clearer, not pretend the layers are separate in the real world.

Specific entry point
Cross-linked context
Real deliverables
Practical scope

Featured project context

A few project pages that show how the disciplines combine into real outcomes rather than sitting as isolated capabilities.

What runs through all of it

Whether the work starts as a frame, a panel, a motion axis, a robot integration or a software utility, the priorities stay consistent.

Buildable

Design choices grounded in real workshop, access, routing and assembly constraints.

Traceable

Clear IO naming, terminal logic, documentation and project structure that people can follow quickly.

Recoverable

Systems that expose useful states and fault paths instead of trapping operators and maintenance teams.

Supportable

Handover packs, backups and design logic that remain useful after commissioning has finished.

Start point

Not sure which discipline your project belongs in?

That is normal. Most jobs cross several categories. Send a short outline of the problem, the target outcome, any platform preferences and the delivery timing, and I can point you to the most relevant examples or define the likely scope more clearly.

Automated system output