Identity & module management
Accounts, passwords, sessions, module registration, usage entitlements and account access.
UNIFIED MANAGEMENT PLATFORM
One place for identity.
Room for specialist tools.
UMP is the application foundation above the operating system. It manages work accounts, module access and lifecycle, giving independent modules a common framework.
Platform evolution planCLEAR RESPONSIBILITIES
One foundation.
Three clear boundaries.
The platform decides who can enter a module. The module decides what they can do there. The operating system provides the resources.
Business permissions
Modules such as RTS own permissions for viewing, editing, reviewing and settling business records.
Runtime resources
Processes, files, networks and devices. A UMP work account is separate from an operating system root account.
THE PLATFORM STACK
Give each layer a clear responsibility.
Target architecture. Some platform and RTS APIs still share a service process during migration.
04
Work entry
MH · Navigation & link cards
03
Business & specialist capabilities
RTS / VRS / TTS / SKWS / VE
02
Platform foundation
UMP · Identity / Access / Lifecycle / API
01
Runtime resources
Operating system · Services · Storage · Network
IDENTITY → ACCESS → ACTION
Entering a module.
Acting within it.
Change the conditions below to explore the access model. Servers must enforce authorization; hiding a link is only a presentation choice.
UMP → RTS
Access to RTS allowed
The account may view permitted data. RTS still rejects editing.
Interactive rule illustration. No account or backend is connected.
MODULE LIFECYCLE
A defined path from
registration to retirement.
These are the target management capabilities, to be implemented in stages according to their dependencies.
- 01
Register & check
Identify the module, version, API and dependencies.
- 02
Install & upgrade
Verify the package, environment and service health.
- 03
Enable & authorize
Manage module availability and account access separately.
- 04
Disable & uninstall
Check impact, revoke access and retain data according to policy.
IN PROGRESS
Where we are. Where we go next.
Existing code includes a separate platform frontend, module registration, hub links and account sessions. The account model and some services remain in transition from RTS to UMP.
Establish independent UMP identity, complete module access control, API contracts and a controlled installation executor. MH remains mandatory and cannot be disabled or uninstalled separately.
LET’S BUILD YOUR WORKSPACE
Start with how you work.
Tell us how the team collaborates, which devices are on site and what matters first. We’ll work out the right combination of modules.