Available · SCADA & industrial automation
I also do SCADA work.
PLC data collection, AVEVA/Wonderware screens, and SQL-backed production reporting — the unglamorous side of industrial software that keeps a line running. Available now for B2B contract work, remote or hybrid.
Engineering background
Gheorghe Asachi Technical University of Iasi · Faculty of Electrical Engineering, Energy and Applied Informatics
Four-year engineering program covering power converters, electric drives (including vector and numeric control), PLCs, distributed control systems, industrial informatics, and industrial robots. That's the hardware-side context the SCADA / .NET work is built on.
What I do
7 areasPulling tags and events from PLCs on the line, landing them in a queryable store, and keeping that store aligned with what the line actually produces.
HMI screens and data views that operators and shift leads can actually read. Layout for shift handoffs, not for screenshots.
Programmable logic controllers, distributed control system configuration, and drive-control software — vector and numeric control included. I write the control side, and I read the electrical side well enough to keep the conversation honest with the panel builders.
Views, aggregations, and reports over collected production data. Designed for slow queries, missing rows, and the kind of dirty data real lines produce.
Package counts, run duration, quantities, downtime flags, shift summaries. The numbers that show up on Monday morning, not the ones that look good in a demo.
Sitting with the client or project director until vague operational needs turn into a concrete data collection or screen change. No "just build me a dashboard" black boxes.
Visual Basic scripts and helpers that bridge the SCADA stack to SQL, files, or the rest of the plant. Boring, but it’s the stuff that keeps the line running.
Past work
Worked on an industrial data collection/reporting project for a pipe production line. Collected PLC production data into SQL Server, built AVEVA/Wonderware screens and data views, and translated client requirements into reporting and data collection logic.
- AVEVA Wonderware
- Visual Basic
- MS SQL
- PLC Data
What I'm already productive in for this kind of work.
- AVEVA Wonderware InTouch / System Platform screens, data views
- MS SQL Server collected data, views, reporting layer
- Visual Basic legacy glue, scripts, integration helpers
- PLC tag data production line telemetry into the SQL layer
Typical fits — if yours is on this list, we're off to a good start.
- Greenfield or extension of an existing PLC → SQL data collection setup
- New AVEVA/Wonderware screens or rework of screens that operators stopped trusting
- Production reports that pull from SQL and need to actually match the line
- Stabilizing an existing SCADA / reporting layer that grew organically
- B2B contract work alongside an internal automation team
Honest list — saves us both a back-and-forth.
- Long-term on-site only roles that need daily plant presence — I work remote or hybrid
- OT cybersecurity audits, network segregation, or compliance-heavy work
- Pure control cabinet / panel manufacturing without an electrical workshop partner
- Pure field wiring and cable harness work on the plant floor
- Sales or pre-sales engineering for SCADA / HMI products
Send a short email with the line, the SCADA stack, and what you're trying to get out of the data. I'll reply with whether it actually fits and what the next step would look like.
Need the .NET / web side too? go to /contact or read /about.