Why Architecture Must Precede Analytics
BioProcess International 2026 — Boston, MA
Why analytics and AI programs stall when manufacturing intent is never captured as a durable, machine-readable construct.
Why digital transformation stalls on the plant floor — and what it takes, structurally, to make it stick.
I'm a principal manufacturing systems engineer and independent researcher working at the intersection of pharmaceutical operations, digital architecture, and AI governance. My work centers on a stubborn problem: organizations build good systems they can't absorb. I write, develop frameworks, and contribute to industry bodies including BioPhorum, ISPE, IAAE, and the Pistoia Alliance.
The real barrier to AI value in regulated manufacturing isn't the tools or the rules — it's whether the workforce has the skill to turn capable tools into defensible work.
Operational Readiness · Part 2If failed adoption is a readiness problem, here's what you actually build: an owner with authority, and a gate that can say "not now."
Operational Readiness · Part 1A deployment designed right, built right, signed off by everyone — and stalled at the wall when the site decided it wasn't ready.
BioProcess International 2026 — Boston, MA
Why analytics and AI programs stall when manufacturing intent is never captured as a durable, machine-readable construct.
Boston, MA — panelist, two sessions
Two panels: bringing products to patients faster through project delivery, and smart manufacturing & facility modernization.
ISPE Boston Area Chapter — chapter announcement
Joined the Board of Directors of the ISPE Boston Area Chapter, after serving as Vice-Chair of its Emerging Leaders Committee.
Longer-form work on digital architecture for pharmaceutical manufacturing, AI governance, and the structures that let intent, data, and systems transfer without losing meaning. Downloadable papers and abstracts.
Plus industry-body collaborations — co-authored BioPhorum frameworks on batch disposition and AI-ready data. See collaborations →
Most of my work comes back to one observation: the gap between what organizations deploy and what they can sustain is rarely a technology problem. It's an architecture problem — of data, of intent, and of the organization itself. I research and write about how to close it, and I build the frameworks and tooling that make it tractable in regulated environments.