Feature Deep-Dive
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
BOBR Hierarchy Management
Build and maintain your Bill of Business Resources (BOBR) organizational hierarchy from the admin UI. Every level of the hierarchy is named and structured to match your plant... not forced into a generic structure. Call routing, OEE rollup, user assignment, and access control all derive from this hierarchy.
Role Management and RBAC (Role-Based Access Control)
Define roles and assign granular permissions across every module and action in the system. Operator, Maintenance Technician, Supervisor, Quality, Production Manager, Maintenance Manager, and Executive roles all carry different permission sets. Custom roles can be defined to match your specific organizational access policies.
Call Type Configuration
Define the available call types for each asset: which roles receive notifications, what escalation rules apply, and what response time targets are expected. A press might have Maintenance, Quality, and Supervisor call types. A conveyor might only have Maintenance. Available types are configured per asset to prevent irrelevant alerts.
Module Licensing
Maintenance management (CMMS) is bundled with ProAlert Core, Quality ships with it, and module entitlement is enforced on the server rather than only hidden in the menu. Materials, Aviation, OEE, Video, EdgeSense and ISO 55001 are licensed separately, with seat management and expiry dates, and ISO 55001 depends on maintenance. Entitlement is enforced in the navigation itself, and the EdgeSense device page shows seats used against seats bought with a progress bar that blocks when they run out.
Onboarding by Invitation Only
Self-registration has been removed. A fresh installation establishes its first administrator from an emailed activation link rather than a shipped default password, and after that an administrator invites each person, who accepts and sets their own. The API register call cannot take a role from the caller, so nothing can elevate itself on the way in. The demo dataset does not ship enabled.
Runs on an Isolated Network
Every front-end library is served from the ProAlert server itself, with no content delivery network to reach, so boards, kiosks and dashboards render correctly on a plant network with no route to the internet. Per-install secrets load from outside the deployment folder, so an update cannot overwrite an installation's connection string or keys, and the data protection key ring is persisted so a deploy or an app-pool recycle does not sign everybody out.
CMMS Access Configuration
Granular CMMS (Computerized Maintenance Management System) permission configuration: who can create work orders, who can approve them, who can close them, and who can only view them. Purchase order approval levels and template approval chain membership are also configured here.
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.
Complete Audit Trail
Every system action recorded with user, timestamp, entity modified, and before/after values. The audit trail covers configuration changes, user actions, and data modifications across all modules. Audit records are write-once and available for compliance export. One identity is used however the person signed in... PIN, kiosk or password... so the same human is not three different names in the record.
Login Audit
A security administrator sees sign-ins, failed attempts and sign-outs, including the end of a session rather than only its start, which is the half most login logs leave out.
Startup Migration Check
If the database is behind the code, the application says so plainly at startup instead of failing somewhere obscure during the first shift that touches the new table.
AppError Persistence
Application errors are logged to the database rather than only to server log files. Errors are visible in the admin interface and surfaced in the Executive Dashboard's system health section. The ProAlert support team can diagnose production issues remotely from the error records without requiring server access.
HubTest Diagnostic Page
Built-in SignalR hub test page for confirming real-time connectivity during initial setup, after network changes, or when troubleshooting notification delivery issues. IT teams can verify that WebSocket connections from the application server to client devices are functioning correctly without third-party tooling.
DI Smoke Test on Startup
Dependency injection (DI) smoke test runs automatically at application startup to verify that all required services are properly configured. Misconfigured services fail fast at startup rather than failing silently during first use... catching deployment configuration errors before the first shift reaches them.
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.
