All work

Dow / Program delivery

Migrating inspection records across 15 Dow sites

Dow needed to replace the system used for equipment inspection and maintenance records. I proposed the rollout, designed the records-review process and coordinated with site teams through a migration the team completed across 15 sites.

My role
Rollout planning, records review, progress reporting and site coordination.
Working context
A funded engineering program involving plant teams with separate priorities and resources.

Replacing a system used for inspection planning

The retiring system held information used to plan equipment inspections and maintenance. Moving that information meant working with site teams to check the recorded operating conditions and close data gaps, as well as preparing it for the replacement system.

I organized the records review and coordination across sites. Each plant controlled its own resources and priorities; I had no authority over site budgets or reporting lines. The rollout depended on site support and a review process that people could fit around their operating responsibilities.

A three-site pilot before the remaining 12 sites

Leadership initially recommended five phases. I proposed two: a pilot at three sites to test the review process, followed by the remaining 12 sites together.

Each phase required another round of setup and tracking. The pilot would establish the process before the remaining sites used it. I built support with site counterparts and internal leadership, who helped present the proposal to operations leadership.

From five phases to two

Initial proposal: five phases

  1. Phase 1
  2. Phase 2
  3. Phase 3
  4. Phase 4
  5. Phase 5

Each phase required separate setup and tracking. Site allocations within the five phases are not shown.

The rollout we used: two phases

Pilot

3 sites

Test the review process

Remaining sites

12 sites

Use the process established in the pilot

Diagram of the initial proposal and the rollout used. Block widths do not represent time, effort or cost.

The initial proposal had five phases. The rollout used a three-site pilot followed by the remaining 12 sites together.

Fewer phases reduced repeated setup, but reviewing 12 sites together increased the coordination needed at one time. I paired the proposal with a pilot and common reporting so the team could track progress and problems across sites.

Site teams checked the records first

Local equipment records were limited, and the migration had less preparation time than a new inspection program. I built a template and review guide so site teams could check the existing information first. Further research could then focus on the remaining equipment-data gaps.

When written reviews stopped progressing, we worked through the information in meetings with groups within each plant. Questions about recorded fluids, temperatures, and operating conditions gave those sessions a concrete focus.

Two constraints that shaped the review

  • Limited local records

    Put site validation first, then research unresolved equipment-data gaps.

  • Written reviews stalled

    Work through the questions in meetings with the relevant plant groups.

Summary of review decisions described in this account. Internal records and review templates are not reproduced.

Reporting to site teams and operations leadership

I built trackers, presentations and dashboards covering milestones, resource needs, data quality and risks. Weekly internal and site meetings addressed problems with the work. Reviews at key stages gave operations leadership the information needed to assess progress and make decisions.

I also explained differences between the old and new systems, including changes in the records and model outputs that reviewers needed to understand.

How I checked the effect of changes to inspection-model assumptions

In later migration work, I used spreadsheet comparisons to show how proposed changes in materials or assumptions about corrosion affected model output. Reviewers could examine those implications before another platform upload. Site specialists made the technical decisions; platform administration remained with the relevant specialists.

How I checked the effect of changes to inspection-model assumptions

In later migration work, I used spreadsheet comparisons to show how proposed changes in materials or assumptions about corrosion affected model output. Reviewers could examine those implications before another platform upload. Site specialists made the technical decisions; platform administration remained with the relevant specialists.

A completed migration

The team completed the migration across 15 sites. My contribution was the rollout proposal, records-review process, progress reporting and coordination between site teams, engineering specialists and leadership.