Allow Scheduler to operate independently as a standalone MAS application, decoupled from Manage.

Thanks Pedro for the detailed response and for outlining the potential directions – really helpful to see this broken down so clearly.

I fully appreciate that decoupling Scheduler entirely from Manage is a longer-term ambition, especially given the dependencies on legacy Maximo Framework components. That said, my main driver here is not necessarily to remove Manage altogether, but rather to enable a single, unified view and control of the workforce across multiple MAS instances.

In our setup, we operate several MAS workspaces (and in some cases, completely separate instances) to support different business lines. However, our workforce is shared across these environments. The current architecture doesn’t allow us to centrally manage scheduling without workarounds or duplicate deployments.

I'm absolutely open to alternatives—whether it's the mid-term dashboard-style model or integration via MIF—as long as the end result allows us to schedule work centrally, allocate resources intelligently across environments, and avoid data fragmentation or excessive complexity.

Looking forward to continuing this conversation and seeing how we can move towards a scalable, enterprise-ready scheduling model that supports these kinds of deployments

Hi All,

This sounds like a very interesting direction, but I'd like to clarify a few key points before moving forward. It's important to confirm some foundational aspects related to architecture and integration:

• A Manage instance will still be required to support the core scheduling functions, similar to how Mobile consumes resources today.

• The potential for new dashboard applications based on the Maximo Application Framework is promising. However, it's important to note that the existing graphical applications are built on the legacy Maximo Framework.

• Decoupling modules such as Work Orders, Resources, Calendars, and Shifts from Manage—while still maintaining their relationship within the Scheduler application—is conceptually sound but would likely be a longer-term goal.

With that in mind, here’s a summary of the potential options and associated timelines:

1. Schedule Dashboards similar to Mobile, enabling multiple Scheduler instances connected to a single Manage instance – Mid-term (approx. 1 year)

2. Standalone Scheduler Manage Module, decoupled from core Manage and integrated via Maximo Integration Framework (MIF) – Long-term (2–3 years)

3. Completely new Scheduler Application, not dependent on Manage, consuming resource and work order data via APIs – To Be Determined (TBD)

Please feel free to share your thoughts, additional needs, or ideas related to this discussion.

For this type of organisation I can see huge benefits of having a decoupled Schedling tool that could pull from various instances of manage.