LinkedIn
GitHub (Onurb29)Start with the physical process
Map the real workflow, operating constraint and decisions before touching the application.
Industrial systems · Terrace, British Columbia
Turning complexity into systems people trust.
I connect operations, production data and software—finding the failure between SCADA, historian, database and application before it becomes “just an IT issue.”
The intersection
Operations knowledge with systems depth.
My path started in electrical and process operations, then moved through production optimization into manufacturing systems. That combination matters: reliable software begins with understanding what the plant is actually trying to do.
Trace the complete signal path
Follow context from SCADA and OPC through the historian, database, business logic and user interface.
Build for the person on shift
Turn complex dependencies into clear tools, evidence and recovery paths that operations can use.
Selected work
Engineering beneath the interface.
The useful work is rarely a prettier dashboard. It is defining the right event, preserving context, and proving where a production record stopped matching reality.
MESROOT-CAUSE ANALYSIS
Production workflow reliability
Investigated missing and out-of-sequence production events across user actions, application records and physical equipment states.
- Separated application defects from incomplete operating workflows
- Mapped prerequisite records and system dependencies
- Produced evidence that support and operations could act on
HISTORIANSQL
Data acquisition & validation
Compared measurements and events across source systems to find timing, mapping and calculation failures hidden by final reports.
- Traced data from control layer to business reporting
- Validated counts, states and contextual records
- Improved confidence in production KPIs
TOCPRODUCTION OPTIMIZATION
Constraint-focused analysis
Structured production measures around flow and lost throughput rather than local efficiency alone.
- Defined events in physical and economic terms
- Separated constraint time from supporting activity
- Converted historical records into decision support
BLAZORSSRS
Practical reporting delivery
Built a usable reporting path when the preferred visualization platforms were unavailable or unnecessarily complex.
- Mapped live industrial tags into an equipment model
- Delivered reporting through established infrastructure
- Designed toward a maintainable web interface
Capabilities
From field signal to business decision.
I work best in the uncomfortable middle: old systems, incomplete documentation, operational pressure and several databases all claiming to be correct.
HistorianMES supportOracle & PL/SQLSQL ServerOPC DA / UASCADA integrationSSRS.NET & BlazorPythonDocker & LinuxRoot-cause analysisTheory of ConstraintsProduction optimizationLegacy modernization
Connect