Go to content

Projects - Toms Automation

Skip menu
Skip menu
To see updaed list of projects and our work experience please use LinkedIn shortcut bellow.

Successful automation and OT projects depend as much on collaboration as on technology. I start by clarifying your goals, constraints, and success criteria so that we solve the right problem and stay aligned on priorities.

During the project I keep communication clear and transparent with regular check-ins, concise status updates, and early visibility on risks or trade-offs. Design decisions are documented and changes are tracked, so that you always understand why the system behaves the way it does.

Before going live I focus on thorough testing and performing (if needed) structured FAT/SAT plans. I also provide documentation and handover support, so that your team can operate and maintain the solution confidently.

The table on the right summaries key technologies and protocols that appear repeatedly in my projects. It is not an exhaustive list, but it gives you a sense of the typical toolset I work with.

If you are unsure whether your specific platform is covered you can still get in touch – many skills transfer between vendors and I am used to learning new environments quickly.

AreaExamplesTypical use in projects
PLC platformsSiemens, GE, Emerson, Codesys-based systemsMachine control, safety logic, sequence control, line integration
HMI & SCADAPanel HMIs, WinCC, Ignition, other SCADA packagesOperator interfaces, alarm management, trending, centralised supervision
OT protocolsOPC UA, Modbus/TCP, Profinet, Ethernet/IPStandardised communication between PLCs, gateways, SCADA and IT systems
IIoT & dataMQTT, REST APIs, databases, historiansData collection, dashboards, analytics, integration with MES/ERP and cloud
Network & securityLayered networks, VLANs, firewalls, VPNsSegmentation of OT and IT, secure remote access, protected data flows

If these project examples resonate with your situation, the next step is to talk about your specific goals, constraints and timelines. You do not need a fully defined specification – an initial conversation is often enough to outline options.

Send a short description of your production environment and what you would like to improve (for example, better visibility, less downtime or integration with IT systems). I will come back with clarifying questions and a proposed way forward.

Back to content