Technical continuity
Direct contact and a documented project
I handle the project directly and document technical decisions, code and procedures. Logs and documentation help explain how the software works and support the people who will maintain it.
Method
Understand the process first. Then write the software.
I start with the required functions and how the plant operates, then design the software, test it and prepare for commissioning.
Working with manufacturing companies, machine builders and integrators
I work directly with the company operating the plant or contribute to a machine builder’s or integrator’s project. On projects involving several suppliers, I handle technical discussions and the software’s integration with the other systems.
How solutions are built
Purpose-built software with reusable components
In custom applications, I separate communications, the machine model and process logic. For SCADA, I use platforms suited to the project and integrate dedicated components where needed.
Operator interfaces and integrations use application services to access system data and functions. Reusing common components focuses development on machine functions. A modular structure is also useful in a compact application.
- Separate adapters keep protocol details out of application rules.
- Explicit states and operations give interfaces, integrations and diagnostics a shared operational meaning.
- Tests cover events, errors and disconnections; commissioning checks integration with the real plant.
- Documentation and version control make changes traceable and easier to maintain.
When I use AI assistants in development, I keep component boundaries explicit and verify changes through code review, testing and documentation. These tools support engineering work without replacing the checks and commissioning required by the project.
-
PLC / devices
Machine control and safety remain within the automation.
-
Communication adapters
Defined communications and device operations.
-
Machine model
States, data, events and application operations.
-
Application services and process-specific logic
Common components and functions specific to the machine.
-
HMI / web UI / databases / business systems / AI tools
Explicit interfaces; exposed operations require authorization, checks and recorded outcomes.
How I work
From requirements to handover
From the first assessment to handover, I focus on what the machine needs to do, how to test it and how to keep the software maintainable.
-
01
Start
Context and objective
Understand the machine, process, problem and constraints.
In practice: The objective and information to gather.
-
02
Survey
Systems and data
Identify interfaces, data sources and the operational meaning of the data.
In practice: A map of data flows and sources.
-
03
Modeling
PLCs, software and operators
Define the functions of the PLC, SCADA and applications, and the operators’ tasks.
In practice: Component functions and links with other systems.
-
04
Integration
Development and integration
Develop the functions and test them during integration.
In practice: Tested software and configurations.
-
05
Validation
Validation and cutover
Test operational and edge cases, and prepare the move into production.
In practice: Test results and release instructions.
-
06
Delivery
Handover and continuity
Leave tools to understand behavior and maintain the system.
In practice: Documentation and tools for diagnostics and maintenance.
Development stages and deployment choices
Development and validation can proceed in stages. Deployment is planned around the plant: it may involve gradual side-by-side operation or a final direct cutover after validation.
A clear starting point reduces rework
Before developing, I check which signals, states, events and data sources are actually reliable. This reduces ambiguity, lost time and hard-to-maintain systems.