A project career built from investment decision to field execution to digital operating model

“How is an industrial system actually specified and built?”

The technical foundation: electrical engineering support inside an engineering organization serving operating industrial plants.

• Support to electrical engineering documentation — equipment and material specifications, single-line diagrams, cable and load information, panel and installation drawings produced in AutoCAD.
• Engineering was not abstract: documents described equipment that would be purchased, installed and energized in an operating plant, so accuracy had a physical consequence.
• Working next to senior engineers built the habit of reading a technical package as a whole — what is specified, what is assumed, what is missing and what the field will have to resolve.
• This period is the reason later project-controls, procurement and construction decisions were made with technical understanding of the scope underneath them, rather than only its cost and duration.

Every project decision eventually resolves into a technical requirement that someone has to install and operate.

“Should we invest — and is this the best use of limited capital?”

Working inside the capital-investment process for operating steel plants, functionally as a front-end loading facilitator.

• Collected operating, safety, reliability and growth needs from operators and managers, then translated them into project scope, WBS, cost, schedule, risk and expected-result documentation mature enough for management decisions.
• Supported the investment-governance cadence itself: preparing the definition packages, comparability and return information that a capital-approval process depends on.
• The portfolio spanned sustaining and reliability work such as electrical modernization of substations, production-improvement projects on the line, and growth cases including evaluation of a rebar cut-and-bend operation with European equipment manufacturers and a regional location strategy.
• Monthly portfolio reviews created a recurring decision cadence: technically valid projects still competed for a finite capital pool, so both return and level of definition determined what moved forward.
• The constant search for Value Improving Practices built a habit of challenging the expected solution before commitment hardens — better return, lower capital, lower operating cost, stronger reliability or better constructability.

A good idea does not become a good investment until its scope, value and uncertainty can be understood.

“What can go wrong, what will it cost, and can this actually be built as drawn?”

The investment and contractual scope already existed. The work was understanding what had been committed, quantifying its uncertainty and producing the evidence the client required.

• Day-to-day work returned repeatedly to the contract: review the requirement, translate it into an execution plan, coordinate the internal teams producing the work and align the result with client milestones.
• Coordinated risk-management workshops across disciplines to identify threats and opportunities, agree responses and quantify exposure. Monte Carlo simulation in Primavera Pertmaster / Primavera Risk Analysis turned the risk register into information management could use for contingency decisions.
• Constructability reviews connected engineering, procurement, planning and construction around access, sequence, temporary facilities, heavy lifts, logistics, installation methods and site readiness — early enough for plans to change.
• Results were presented in formal reports and presentations to the client organization. The Risk Management and Constructability plans were contractual milestones, and were approved on first submission without comments.

A contractual requirement creates value only when it is translated into an executable process and demonstrable evidence of compliance.

“How do we connect the project from approval through startup?”

Where the separate project disciplines became one operating system — first across Brazilian and South American industrial-gas projects, then at global scale from the United States.

1. 2011 – 2017

   Project Controls Engineer — Brazil

   Full-lifecycle industrial-gas projects, project-controls tool development, and cost and schedule feasibility support for FEL-2 proposals.

2. 2017 – 2020

   Project Controls Engineer — Tonawanda, New York

   International move into a global project organization: larger capital projects, distributed engineering, and controls integrated with procurement and logistics.

• Entered with a foundation in electrical engineering, FEL, constructability and risk; left having worked engineering, cost and schedule, contingency, procurement, logistics, construction, mechanical completion, commissioning and startup.
• Developed project-controls tools and reporting structures rather than only operating them — standardizing how progress, commitments and forecast were produced and compared across projects.
• Supported FEL-2 proposal work with cost and schedule feasibility analysis, connecting the promise made to a customer with the execution reality that would have to deliver it.
• The move to Tonawanda in 2017 changed the scale rather than the discipline: global engineering centers, international supply chains, larger capital values and controls that had to integrate procurement status and logistics, not just report cost and time.
• PMP certification in 2015 provided a common integration language across a global project environment — scope, schedule, cost, risk, procurement, communications, stakeholders and governance.
• Projects using identical procedures and systems still produced different results, because execution depended on people. The real challenge was making intent, priority, responsibility and expected outcome survive communication across time zones, functions and languages.
• Field presence became deliberate: proximity to contractors resolved questions faster and made planning directly useful in installation, mechanical completion and handover.

Controls must reach the field and the final business outcome.

“Are we optimizing purchase price, project outcome or lifecycle value?”

A deliberate transition out of project controls into ownership of the sourcing strategy itself: how technical requirements, commercial terms, logistics, supplier capability and project priorities combine into a purchase decision.

• The move was chosen, not incidental. Controls had shown repeatedly that procurement decisions set the boundary conditions of a project long before the field feels them.
• Work ran through global procurement centers across the United States, Europe, Asia-Pacific, the Middle East and Latin America — a virtual, multi-time-zone organization where sourcing strategy had to be agreed remotely and then executed locally.
• Global bid tabulations required far more than comparing quotation totals — price, delivery, logistics, project need, commercial conditions and supplier strategy were consolidated with Engineering, Operations and Project Management.
• Technical and commercial alignment was the core discipline: engineering intent, deviations, exceptions and clarifications resolved into a comparable commercial position before award.
• Technical logistics — heavy and oversized transport, packaging, customs, routing and delivery sequencing against required-on-site dates — was treated as part of the sourcing decision, not a downstream activity.
• The approved vendor base created a recurring judgment: operations valued standardization, reliability, spare-parts compatibility and long-term support, while projects could find stronger technology, lower price or better lead time. The answer required a lifecycle view of the asset.
• COVID-era volatility made those tradeoffs unusually visible. Quotation validity collapsed from thirty days to a week and at times forty-eight hours, requiring multi-source strategies, framework leverage, faster technical and commercial alignment, and continuous coordination of vendor capacity against required-on-site dates.
• The role was strongly matrixed: responsibility for results produced by people who reported elsewhere, delivered through clarity, prioritization, follow-through and accountability.

Collective performance and lifecycle value matter more than isolated optimization.

“How do we create an organization that consistently produces executable work?”

Bringing investment, contract, controls, procurement and field experience together while hiring, training and leading a delivery organization.

1. 2023

   AWP Champion

   Piloting Workface Planning in a live mechanical phase and proving it against internal execution standards.

2. 2023 – 2024

   AWP Program leadership

   Implementation planning, rollout, indicators and coaching across a major hydrogen program.

3. 2024 – Present

   Lead Construction / AWP Program Manager

   Construction organization, subcontract governance, readiness and field performance.

• A smaller hydrogen project in McIntosh, Alabama piloted Workface Planning in a realistic rather than ideal environment — WFP was introduced during the mechanical phase, on a project never structured around AWP from inception, and still materially strengthened execution.
• Scaling to a major hydrogen program in Nederland, Texas required organization design more than methodology: external AWP practitioners accelerated onboarding while the delivery model was adapted to internal standards, engineering deliverables and project-specific execution needs.
• AWP program management meant implementation planning, phased rollout, readiness and performance indicators, and continuous coaching — not the publication of a procedure. The package lifecycle from engineering work packages through procurement and vendor work packages, construction work packages, workface planning and turnover work packages had to be owned by engineering, fabrication, contractors and the field together.
• An AWP Champion was mobilized upstream to coordinate with engineering and fabrication yards before moving to site, reflecting the principle that field readiness is created long before construction mobilization.
• An Information Manager was hired for system integrations, database exchanges, information flow, communication plans and training — AWP fails with strong planners if information cannot move reliably between systems and stakeholders.
• Discipline Workface Planners were pre-mobilized ahead of mechanical construction — equipment and structural steel, piping, and electrical and instrumentation — coordinating contractor planners, readiness criteria, constraints and discipline execution expectations.
• Material management became part of the same readiness system: warehouse and laydown organization, receipt and preservation, material flow to the work front and material status as a constraint on package release.

Scale requires people, governance, data and accountability — not just methodology.

“How can execution knowledge become a repeatable digital operating model?”

Leading the functional architecture and digitalization of construction-management processes into one connected execution environment.

• The initiative started in November 2023, with first production deployment in February 2024 — a deliberately short path from functional concept to a system construction teams could actually use.
• Construction, subcontracting, project-controls, commercial, AWP and field-execution requirements were converted into a structured digital environment: functional and domain architecture, workflow design, data and integration requirements, and implementation leadership with an external developer.
• The design objective was adoption: a technically sophisticated system should not transfer unnecessary complexity to the user.
• Transactional construction information becomes structured data, which then supports project and portfolio analytics.

Digital transformation succeeds when complexity is handled by the system rather than transferred to the user.