Maintenance Management Platform
A facilities maintenance system its own staff can reorganize: the navigation is data, not code.
A maintenance operation with equipment spread across departments and multiple sites needed a system its own staff could reorganize. Off-the-shelf CMMS products fix the navigation to the vendor's idea of how a plant is arranged. Custom builds usually hard-code the menu instead, which means every new department is a change request, a quote, and a wait.
What we built
We made the navigation data rather than code. The system opens on a page of large department tiles; each one opens into further tiles, or into a real screen, to any depth. Administrators add levels and boxes at runtime, with no deployment and no database change. Staff can pin personal tiles of their own alongside the shared ones.
Underneath, a page registry keeps itself current from the application at startup and fails closed: a screen nobody has been granted access to simply doesn't exist for them. Permissions are enforced on the server, and tile visibility follows those permissions automatically, so the menu can never advertise a door the user can't open.
The outcome
The navigation model proved general enough to lift out as a reusable specification, and we now start new line-of-business projects from it. Clients get a proven permission-aware navigation system on day one.
Client system. Screenshots and a demo can be added here once approved for publication.