Manufacturing IAM Discovery

Manufacturing is the sector where identity governance meets physics. An access decision that is merely inconvenient in a bank can stop a production line, spoil a batch, or trip a safety system. That changes what the requirements phase has to establish, and it is why manufacturing discovery cannot be run from the same template as a financial services engagement.

The core difficulty is that a plant runs two estates that were never designed to share an identity model. Corporate IT has ERP, PLM and email, with named users and conventional joiner-mover-leaver processes. The plant floor has SCADA, HMI consoles, MES, historians and PLCs — often shared logins by design, because an operator cannot badge in mid-process, and some of that equipment predates modern authentication entirely. A twenty-year-old controller will not speak SAML no matter how good your IGA platform is.

Layer onto that a workforce that does not look like an office. Three shifts with handoffs. Seasonal and temporary labor. Contractors and OEM engineers who need remote access to specific machinery, sometimes urgently, sometimes from another continent. Multi-plant groups where every site grew its own naming conventions, and acquisitions that arrived with an identity estate nobody has fully mapped. Vendor remote access into operational technology is now one of the most scrutinized paths in the sector, and it is exactly the path least likely to be documented before discovery starts.

When that discovery takes 12 weeks, the cost is not only the consulting spend. It is a plant running on shared credentials for another quarter, an audit finding that was foreseeable, and an implementation scoped against an incomplete picture of who actually needs access to what. ICA structures the discovery in under 10 days, capturing IT and OT access requirements in one process rather than two disconnected workstreams — so the requirements document your integrator receives reflects the plant as it actually runs.