The Lumora Control Tower is being designed as a planner decision workspace. It combines role-specific KPIs, configurable alerts, contextual drilldowns, task management, and plan actions.
This article describes the intended product direction. Individual capabilities may evolve as the platform is developed and validated with users.
Persona-based KPI views
Executives may begin with service, inventory, backlog, utilization, and major risk. Demand planners may focus on forecast accuracy, bias, overrides, and demand exceptions. Supply planners may focus on shortages, late supply, capacity gaps, and unpegged demand.
Configurable alert definitions
Alerts can be defined by business domain, condition, scope, severity, evaluation frequency, assignment, and escalation. Examples include frozen horizon violations, high backlog, late supply, low service level, demand shortage, and unpegged demand.
Contextual drilldown
Users should be able to move from an enterprise KPI to the products, locations, orders, resources, suppliers, and components driving the exception. The goal is to reduce the time spent recreating the root-cause trail outside the system.
Exception workbench
The workbench provides a shared queue for open, in-progress, and resolved exceptions. Planners can filter, assign, investigate, document, and close work while retaining the planning-run context.
Action from the same workspace
Depending on the exception, the user can trigger a scenario, create or review a proposal, assign a task, approve a response, or promote a plan. The action remains linked to the alert and its business rationale.
Visibility matters when it leads to a prioritized response.
What we are validating
- Which KPIs genuinely change planner behaviour
- How much alert configurability is useful without becoming difficult to govern
- Which drilldown path reaches root cause fastest
- How tasks and approvals should connect to planning scenarios
- How to measure exception response time and outcome quality