The capability is the same. The constraints are not.

The plant does not stop for a release window. Change is scheduled around turnarounds that are planned years ahead, an outage has a physical consequence rather than a commercial one, and safety and environmental controls have to be evidenced to a regulator rather than asserted. Rollback plans here are engineering documents.

The organisation is a sequence of projects and movements with contractual dates attached. Cost and schedule control dominate every other consideration, much of the data originates in the field from people who are intermittently connected, and the system that cannot work offline is the system that gets worked around.

Where data may sit is a legal question before it is an architectural preference, and access has to be provable rather than merely configured. Procurement is formal, audit is periodic and adversarial, and a control that exists only in a policy document will be found. The evidence trail is part of the deliverable.

Demand is seasonal and campaign-driven, so capacity is a question with a date on it. The customer-facing surface changes every few weeks while the systems of record must not, and the cost of the estate sits almost entirely in the integration between those two speeds.