Ten capabilities, each shown through signature instances from the flagship projects. Select a capability to open it; the evidence map below shows where each one was proven.
01 · Capabilities
01 · Capability
I wrote the procedures that govern how the skids portfolio runs, from RFQ through closure and from engineering design philosophy through document control, to close the gap between execution practice and documented procedure.
Signature Instances
02 · Capability
Engineering-led proposal delivery over 10 years: scope definition, hydraulic schematics, 3D modelling, and zone-compliance documentation prepared at bid stage, before execution costs are fixed.
Awarded Projects
Pre-award Engineering design instances
Clients Served








03 · Capability
Each of these projects was the first of its kind at INTECH: the first RTTM pipeline system, the first HIPPS programme, the first CI skids at scale, and the first US project. I built the technical capability, delivered the project, and documented the knowledge for the projects that followed.
Signature Instances
04 · Capability
Some projects show a gap between the standard product and the actual requirement. On LDS, the gap was OEM sensitivity; on HIPPS, vendor analysis credibility; on Zeon, the on-site engineering model. Each gap was closed by extending the solution, without re-scoping the requirement.
Signature Instances
05 · Capability
Delivery chains rarely have every capability in place. HIPPS needed vendor QA support, CI needed engineering support at the fabricator’s site, and Zeon needed remote engineering in place of on-site support. Each gap was closed by working inside the delivery chain, with support targeted to specific deliverables and outcomes.
Signature Instances
06 · Capability
Standard OEM cycles suit standard project conditions. When delivery urgency or supply-chain length puts the schedule at risk, engagement is streamlined through direct engineer-to-engineer contact, upstream qualification, and in-flight methodology revision to keep the project on schedule.
Signature Instances
07 · Capability
Some projects require more than one discipline. LDS needed scripting alongside mechanical commissioning, HIPPS needed structural and stress analysis alongside mechanical design, and CI needed commercial judgment and remote engineering alongside design leadership. Each additional discipline was learned and applied because the outcome depended on it.
Signature Instances
08 · Capability
Delivery requires different views at different intervals; execution teams, project managers, and clients follow different information. CI needed info radiators tracking QA compliance for the client, LDS needed engineering and operational HMIs for two user groups, and Zeon needed remote radiators showing fabrication status. Each layer kept delivery aligned across stakeholders.
Operator-facing displays built for each system: RTTM dashboards, pipeline geometry, alarm consoles, and live tracking screens for each operating context.
Handover programmes built for each audience: operator walkthroughs, engineer-to-engineer sessions, and internal resource development.
Live radiators surfacing fabrication status, integration milestones, and risk flags to distributed project teams.
Portfolio-level artifacts giving management continuous visibility across engineering, procurement, QA, and MDR.
Signature Instances
09 · Capability
Problems that reach fabrication before they are identified are the most expensive in delivery. Structure set up before execution prevents this: scope boundaries fixed at contracting, change control in place before scope changes, and risks identified in pre-award rather than at delivery.
Signature Instances
10 · Capability
Engineering judgment applied at the right point in the project lifecycle produces commercial results that procurement alone cannot. I focus on the design phase, remediation alternatives, and proposal scope, where the cost of a wrong decision grows fastest.
Signature Instances
02 · Evidence map
Rows are capabilities, columns are projects. Select a cell for the evidence, or a capability name to open it.
03 · Testimonials