Alignment between automation and business systems
I build software layers that keep orders, machine states, materials, progress and historical data consistent, making machine data usable by technical, quality and production departments.
Industrial software close to the machine
Industrial software to
connect machines,
production and
business data
I build intermediate software between automation, operators and business data: operational dashboards, traceability systems and integrations with databases, HMI/SCADA and business processes.
Automation and supervision
Databases and data exchange
Production dashboards
Logs and traceability
Operational contexts
When machines, production and data must stay aligned
In many industrial contexts information already exists, but it is spread across PLCs, HMIs, SCADA, databases, Excel files and operating procedures. My work is to make it consistent, accessible and useful.
Data collected where it originates
I acquire information from machines, supervision and existing systems, making it accessible to production, maintenance and technical teams.
Understand what happened on the line
Application logs, events and audit trails make the behavior of software, automation, operators and process readable.
Controlled evolution of existing systems
I work incrementally on tools already in use, reconstructing logic and data flows where documentation is partial, without rewriting everything from scratch.
Concrete outputs
Examples of intervention
Some anonymous examples of the kind of industrial problems I work on: machine/software integration, misaligned data, operational dashboards, traceability, logs and diagnostic tools.
Machine data available, but not yet usable
In many plants data is already present in the PLC, SCADA or local systems, but it is not immediately reliable for analysis, reports or integration with other departments.
Intervention
Analysis of available signals, verification of the operational meaning of data, normalization of machine states and construction of an intermediate software layer between automation and database.
Output
Internal APIs, historical data, diagnostic dashboards, event logs and a documented data structure: a reusable data foundation for Industry 4.0 data flows, advanced analytics and, where useful, subsequent integration with AI systems.
Dashboards that support decisions, not just observation
An industrial dashboard should not simply display numbers. It should quickly explain whether the plant can work, which enables are missing, which data is current and why a command cannot be executed.
Intervention
Interface design starting from real machine states: PLC connection, enables, alarms, available commands, valid data and blocking conditions.
Output
Operational dashboards, diagnostic pages, protected commands, clear status messages, event logs and interfaces usable by technicians, maintenance and production managers.
Reconstruct what happened, not just see the current state
When a plant produces anomalies, downtime or inconsistent data, the current state is not enough. An ordered event trace is needed to understand what happened, when, with which order or material involved and which system generated the change.
Intervention
Modeling of states, events and transitions; data collection from machine and software; management of timestamps, production references, application logs and operational causes.
Output
Event timelines, production history, material traceability, audit trails, lookup by order or batch, exports and diagnostic tools to reduce ambiguity between machine, software and process.
Incremental revamping on existing plants
Many interventions do not start from a new machine, but from plants already in production, with existing PLCs, historical HMIs, local databases and partial documentation.
Intervention
Reading the existing system, progressive side-by-side work, verification tools, non-invasive integration and data validation before release.
Output
Intermediate software modules, diagnostics, technical documentation, test procedures and integrations that make data, logs and interfaces verifiable without requiring a full rewrite.
What I do
Software tools for production, maintenance and technical teams
Local services, dashboards and software components designed to make industrial data readable for production, maintenance and technical teams.
Operational dashboards and information displays
Local or intranet screens for orders, machine states, downtime, anomalies, progress, production indicators and shop-floor information displays.
Industrial traceability
Events, materials, coils, packs, batches, buffers and progress reconstructed over time with consistent and verifiable data.
Automation-data integration
Services and applications to acquire data from PLCs, HMI/SCADA and existing systems, storing it in a structured way.
Diagnostics and technical support
Logs, audit trails, technical views and analysis tools to quickly understand errors, anomalies and unexpected behavior.
Intermediate systems
Intermediate software between automation and business data
In many industrial contexts this layer is called Level 2. It does not replace PLCs, HMI/SCADA or MES: it is the controlled software bridge that keeps machine states, orders, materials, events and production data consistent. It can also support Industry 4.0 projects when machine data must be made available in a structured and verifiable way.
It can be a service that collects data from PLCs and SCADA, a production dashboard, a traceability system, an event archive or a technical application used by maintenance and technical teams.
- Process audit and diagnostics
- Real-time production dashboards
- Material traceability and progress
- Integration with databases, ERP/MES and business departments
- Tools for maintenance and technical teams
Is machine data spread across PLCs, HMI/SCADA, databases or files?
Describe the machine, the available data and the operational problem: I can assess how to connect automation, logs and data systems without disrupting the plant.