LOCKOUT ID: The Next-Generation Smart LOTO Tag System
Transform your lockout/tagout procedures with intelligent NFC-enabled tags, real-time tracking, SMS paging, over-shift alerts, Isolation Maps, and a secure read-only API for your systems.
Get up and running quickly with our comprehensive training videos
Modernize your safety procedures with cutting-edge technology designed for industrial environments
Tap-to-scan NFC tags for instant lockout/tagout status updates and real-time tracking
Comprehensive audit trails, compliance reporting, and automated safety protocols
Live dashboard with instant updates, shift management, and team coordination tools
New capabilities
Optional supervisor tools help you send operational SMS pages and get notified when NFC shift cycles exceed your limits.
Send critical safety and operations messages from the portal
Page tag owners or entire workscopes by SMS when you need a fast response on the job site. Choose a predefined template or write a custom message, then deliver to one worker or everyone on a workscope.
Automatic notifications when shifts exceed your limit
Supervisors set a maximum allowable shift duration. When a Gen2 or Gen3 NFC tag stays on shift past that limit, LOCKOUT ID creates alerts and notifies your configured recipients by email or SMS.
Over-Shift Alerting is optional and not enabled by default. Turn it on in Over-Shift Settings once compatible NFC tags and recipients are configured.
Plant visibility & integrations
Map labeled equipment on site diagrams and pull live lockout data into tools like CRM, SAP, and Maximo.
Upload diagrams and watch lockout status on the map
Upload isolation or plant diagrams, click to label components, and turn those labels into selectable workscopes. Markers start green and turn red when a matching tag goes on shift—so crews can see what’s actively locked out at a glance.
Secure, read-only access for CRM, SAP, Maximo, and more
Create user-scoped API tokens from the dashboard and pull live lockout data into your existing systems. The API is read-only—tokens never grant write access.
Base path: /api/v1 — authenticate with Authorization: Bearer or X-Api-Key.