Schedule Manager's Rearchitecture for Active Workspace (Teamcenter 11.2+)

Source: Siemens Teamcenter blog, "Behind the screens of Schedule Manager in Active Workspace!" — https://blogs.sw.siemens.com/teamcenter/behind-the-screens-of-schedule-manager-in-active-workspace/

This is useful background for anyone troubleshooting why older Schedule Manager customizations or performance assumptions (rich client era) don't carry over cleanly to Active Workspace-based deployments (relevant context for TC 2606, which builds on this architecture).

What Changed at Teamcenter 11.2

• Business logic moved server-side: Scheduling business logic (the actual scheduling engine calculations) was moved from the Rich Application Client onto the Teamcenter server. Previously, more of this logic executed client-side.
• Data model simplification: Schedule and schedule-task objects were re-parented — moved off of ItemRevision-based objects onto lightweight workspace objects. This is described as a "completely rearchitected" data model, done specifically to improve performance and scalability.
• These two changes together are why Schedule Manager in Active Workspace behaves and scales differently than the legacy rich-client version — it's not just a UI reskin, the underlying object model changed.

Migration/Compatibility Notes (Relevant for Anyone Upgrading)

• Siemens states published API signatures were preserved across the rearchitecture specifically so existing customizations could migrate rather than requiring a rewrite — but new capabilities required entirely new APIs (meaning some newer Active Workspace scheduling features simply have no rich-client equivalent API).
• A dedicated "Schedule Manager asynchronous attribute consolidation utility" is called out as the tool for migrating/converting existing schedule data to the new lightweight object model.
• The migration was explicitly engineered for "minimal TEM upgrade time impact while handling huge data migration" — i.e., Siemens anticipated that large schedule datasets (many programs/projects with years of history) would otherwise make this a slow upgrade step, and built tooling to mitigate that.
• The blog explicitly says to follow Siemens' documented migration best practices for this step rather than improvising — a hint that ad hoc upgrades of large schedule datasets have been a known pain point.

Known Practitioner Complaint (from search-snippet, unattributed forum commentary found alongside this topic)

Multiple sources note that documentation for Schedule Manager in Active Workspace specifically is sparser than for the legacy Rich Client — most available third-party tutorials, screenshots, and how-tos still assume the old rich-client UI, which can be disorienting for teams standing up new Active Workspace-based (e.g., 2606) deployments.

Related Feature: Kanban Boards

Active Workspace also added Kanban-style boards to Program Planning / Schedule Manager, letting users manage task status via drag-and-drop rather than only through the Gantt/tree table view — useful for teams running a more agile task-tracking cadence layered on top of the traditional Gantt schedule.