IT wants single sign-on for good reasons: one identity source, instant deprovisioning when someone leaves, enforced MFA, no password sprawl across yet another SaaS tool. The field wants to open the app and start the route. Inspection software has to satisfy both, and the tension is real because field conditions break the assumptions office SSO was designed around.
Why the office pattern breaks in the field
The standard corporate login flow assumes a personal device, a keyboard, and a network. A unit inspector has none of these reliably:
- Gloves and screens. Typing a fourteen-character password with nitrile gloves on a rain-speckled tablet is a genuine barrier, and every barrier gets solved with a workaround, usually a shared session that never logs out.
- Connectivity gaps. Tank farms, rack tops, and vessel interiors are dead zones. If authentication requires a live round-trip to the identity provider, the app is unusable exactly where the work is.
- MFA in the plant. Push notifications assume the phone is present and has signal. Many operating areas prohibit personal phones entirely. An MFA prompt that cannot be answered at the vessel is a denial of service, self-inflicted.
- Shared and ruggedized devices. Field tablets are often pool equipment. Identity has to attach to the person, not the hardware, without a full login ceremony at every handoff.
What to require from a vendor
The requirements list for procurement and IT security review is short and testable:
- Standard federation. SAML 2.0 or OpenID Connect against your identity provider: Entra ID, Okta, or equivalent. No vendor-proprietary directory as the source of truth.
- SCIM or equivalent provisioning. Joiners, movers, and leavers flow from your directory automatically. Ask specifically how fast deprovisioning propagates, because a terminated contractor's field access is an audit question waiting to happen.
- Offline session policy, configurable. After an online authentication, the app should support a bounded offline session, re-verified with a local unlock such as a PIN or biometric. IT sets the session length; the field gets a glove-friendly unlock. Both sides get what they need.
- Device-level trust where phones are banned. Support for MFA methods that live on the managed device or a hardware token, not only on a personal phone.
- Attribution survives everything. Every reading, edit, and approval carries the authenticated identity, including work captured offline on a shared tablet and synced later. If two inspectors used the same device that day, the records must still say who did what.
The rollout details that bite
Two practical notes from deployments generally. First, contractors: inspection programs run on third-party NDE technicians, and your identity provider probably does not hold their accounts. Decide early whether contractors federate through a guest tenant, a sponsored account, or a vendor-side identity with your MFA policy applied. The wrong answer, discovered during a turnaround, is shared credentials.
Second, session length is a policy conversation, not a technical one. A twelve-hour offline session matches a field shift; a thirty-minute web timeout matches an office norm. Applying the office norm to the field app guarantees workarounds. Bring the chief inspector into the room when the session policy is set.
The test before you sign
Have one inspector, with gloves, take a provisioned tablet into a known dead zone, authenticate beforehand, complete a route, hand the tablet to a second inspector for their route, and sync both. Then check the records for correct attribution and check the console for what deprovisioning that contractor takes. That single afternoon validates more than any architecture diagram. It is the test we invite for intelliSPEC, and it should be table stakes for anything your field crews will carry.
