Administration
A system you can't configure to your plant isn't a system. It's a product you adapt your plant to fit. ProAlert's administration module gives your IT team and operations managers the control to map the platform exactly to your organizational structure, naming conventions, access policies, and module licensing... without custom code. The BOBR (Bill of Business Resources) hierarchy, role assignments, user management, and diagnostic tools are all managed from a single admin interface that doesn't require a support ticket to update.
The bottom line: Most manufacturing platforms require a vendor professional services engagement every time you need to add a building, rename a department, or change who gets notified when a specific press goes down. ProAlert's admin tools are designed for plant IT teams and operations managers to self-administer... because your organizational structure changes faster than any vendor's implementation calendar.
System Configuration
User Management
User management in ProAlert is designed for the reality of a manufacturing plant: operators who rotate shifts, technicians who move between facilities, and supervisors who cover multiple lines. Every user configuration option required for accurate attribution and cost analysis is available from the admin interface.
| Configuration | Purpose |
|---|---|
| Account Management | Create and manage user accounts with role, language preference, site association, and LLC (Limited Liability Company) entity assignment. Language preference drives interface language and notification language for all ProAlert modules. |
| PIN Setup | Configure each user's PIN (Personal Identification Number) for call closure authentication, work order sign-off, and scrap threshold approval. PINs are stored hashed and are not recoverable. PIN verification creates a signed record tied to the user's identity for compliance audit purposes. |
| Hourly Rate Configuration | Set hourly rates per user for accurate labor cost attribution in CMMS work orders and workforce operations dashboards. Labor cost per work order, per shift, and per asset draws from these configured rates... no ERP (Enterprise Resource Planning) integration required for maintenance cost analysis. |
| Approval Level Assignment | Assign users to approval tiers for the multiple approval workflows in ProAlert: Purchase Order approval, Standard Work Template approval, and Scrap Threshold approval. Multi-level approval chains are defined here by assigning the appropriate users to each level. |
| Multi-Site Association | Users can be associated with multiple LLC or site combinations for cross-facility access. A maintenance manager who covers two plants has appropriate access to both... without requiring two separate accounts or two logins. |
Diagnostics and System Health
ProAlert includes built-in diagnostic tools designed to catch configuration problems and connectivity issues before they affect production... and to surface errors to the support team without requiring server log access.
For IT Teams: What Administration Controls
| Area | Admin-Configurable | Notes |
|---|---|---|
| Organizational Structure | BOBR hierarchy creation, renaming, and restructuring | All changes take effect immediately. Alert routing, group membership, and OEE rollup update automatically when hierarchy is modified. No application restart required. |
| Access Control | Role definitions, permission assignments, user-role mapping | RBAC (Role-Based Access Control) changes take effect on next user login. Permission model covers create/read/update/delete at the action level for each module. All role changes are audit-trailed. |
| Module Licensing | Core/Premium tier activation, license expiration dates | Module licensing is managed in the admin UI without code deployment. Expired licenses gracefully degrade to Core tier features rather than throwing errors. License status visible on the admin dashboard. |
| Authentication Policy | Password complexity, expiration interval, history depth | Managed via ASP.NET Core Identity PasswordOptions from the admin interface. All policy changes are audit-trailed. JWT (JSON Web Token) token expiration and refresh interval are deployment-level configuration in appsettings.json. |
| Error Visibility | AppError log accessible from admin UI | Application errors visible to admin users in the error log section. Errors include stack trace, timestamp, user context, and URL. Remote support does not require server SSH (Secure Shell) access to diagnose production issues. |
See how ProAlert maps to your organizational structure.
Book a 30-minute demo... we'll walk through BOBR hierarchy setup, role configuration, and the HubTest diagnostic tool with your IT team.