Gensuite Refresh

The situation

Every Hexion site around the world logs its safety data inside Gensuite (Benchmark ESG), the company's enterprise EHS application. By the time I took on the platform, the interface had aged past what sites actually needed day to day, and each location had settled into its own workaround for the gaps. There was no single, modern way to capture the data consistently across the company, which meant the data itself carried that inconsistency downstream into every report built on top of it.

From September 2023 to November 2025, I was the sole global administrator of Gensuite, owning the platform and the vendor relationship end to end. That put me in the position to see every site's pain point directly, not through a layer of tickets. I also owned OSHA, MSHA, and ACC regulatory compliance reporting during this period, so I felt the cost of inconsistent capture on both sides: the sites entering the data and the government submissions built from it.

Constraints

• The application runs global sites in different regulatory environments, so a change to a form or workflow could not break compliance capture anywhere it was deployed.
• Gensuite is a vendor platform, not something I could rebuild from scratch. The refresh had to work inside Benchmark ESG's configuration model and release cycle.
• Rollout had to reach every site without a parallel system running underneath it, so the cutover itself was part of the design problem, not an afterthought.
• I was running this alongside the day-to-day admin duties of the platform: owning OSHA, MSHA, and ACC reporting did not pause while the refresh was in flight, so the two phases had to be sequenced around live regulatory deadlines.

What I built

I led the refresh across two phases, from requirements gathering through global rollout. Phase 1 and Phase 2 together shipped more than 80 feature enhancements to how the application captures safety data, touching the forms, workflows, and reporting paths that every site uses. Because I was also the platform's sole global administrator, I could move a requirement from a site's complaint to a configured change without routing it through a separate owner first, which is part of why the two phases were able to cover as much ground as they did.

Decisions I made and why

• I split the work into two phases rather than one large release, so the highest-friction capture points could ship and stabilize before the rest of the requirements list was tackled.
• I ran requirements through global rollout myself as the platform's sole administrator, which meant no handoff gap between what a site asked for and what shipped.
• I kept the vendor relationship in my own hands rather than routing configuration changes through a third party, since Gensuite is Benchmark ESG's platform and every enhancement still had to land inside their release process.

What changed

The application now reflects more than 80 shipped feature enhancements, and every global site captures its safety data through the refreshed version rather than the one it replaced. The refresh reshaped how sites do that capture day to day, not just how the platform looks, and it is the version of Gensuite still in use across the company today.

What I would do differently

I would have pushed harder, earlier, to get a small group of sites testing Phase 1 changes before the broader rollout. Running two phases end to end while also being the sole administrator meant most of the early feedback came after a change was already live, and I had to fix in place what a short pilot with a handful of sites would have caught first.

Related