The enterprise extends past the company
Design partners, contract manufacturers, maintenance crews, logistics providers. A meaningful share of the people using your systems are employed by somebody else, under a contract with an end date.
Automotive & Manufacturing
Identity on the shop floor does not behave like identity in the office
Both industries run an extended enterprise — tiers of suppliers, dealers, contractors — and a workforce that mostly does not sit at a desk. Identity programmes designed for the office reach the factory gate and stop.
What the two have in common
Enough that the same platform serves both, and enough differences that the same configuration never does.
Most of the workforce is not at a desk
Line operators, technicians, drivers, field service. They authenticate in gloves, in noise, in a hurry, often on a device that is not theirs and sometimes on one bolted to a wall.
Machines outnumber people
Controllers, robots, test rigs, telematics units, integration accounts. Each needs credentials, almost none has a lifecycle, and the ones installed a decade ago were configured by somebody who has since retired.
Automotive
Access travels down the chain
The relationship is not between two parties. Your engineering data, your parts catalogue and your warranty systems descend through tiers you contract with, and tiers you do not.
Dealers turn over faster than you are told
A service network of hundreds of independent businesses hires and loses staff constantly. Nobody notifies the manufacturer, so accounts survive the people who held them unless the partner administers their own.
Engineering data is the asset
Design files shared with a tier-one partner for a programme that ended two years ago are the most valuable thing on the network, and the least likely to have had its access reviewed.
The vehicle is an identity too
Connected cars, telematics units and service tools all authenticate to back-end services. They have long lifecycles, no user, and a credential rotation story that has to work over the air.
Manufacturing
Six assumptions that are false in the plant
Every one of these is true in the office, which is why office-designed identity reaches the factory gate and stops. Read the right column: that is the actual requirement.
What office IAM assumesWhat the plant floor is
Each person has their own deviceOne terminal, three shifts, twelve people
A phone is always in a pocketPhones are banned on the line, or unusable in gloves
The network reaches the internetThe cell is segmented, sometimes air-gapped, by design
A login takes fifteen secondsFifteen seconds per shift change, times four hundred people
If access fails, you raise a ticketIf access fails, the line stops and somebody counts the cost per minute
Systems get patched on a scheduleThe controller has run since 2011 and its vendor no longer exists
None of this argues for weaker authentication in production. It argues for authentication designed against the constraints that actually exist there.
How Monokee approaches it
One platform, two very different configurations
The journey adapts to the context
The same identity, reaching the same system, can face a badge tap at a shared terminal and a passkey from a laptop. What is asked is a branch on the canvas, not a global policy.
Suppliers and dealers administer themselves
Each organisation gets its own domain and its own administrator, inside limits you define — because you cannot maintain a list of who works at four hundred independent businesses.
Machine identities get a lifecycle
Service accounts, controllers and integration credentials are collected, owned and reviewed like everything else, rather than living outside governance because they always have.
Bring us the terminal on the line
The shared one, with the badge reader that half works. It is usually the most honest test of an identity design.
Talk to an expert