MS Project / MPX Exchange with Teamcenter Schedule Manager: Format Notes and Gotchas

Teamcenter's classic MS Project interoperability path is the MPX (Microsoft Project Exchange) file format: Teamcenter's MPX Template import function brings existing MS Project plans into Teamcenter, and the export function pushes Teamcenter project plans out to MS Project or any other MPX-compatible tool.

Known Practical Gotchas

• MPX format support ended in MS Project 2010. Microsoft dropped MPX support in later MS Project versions (2013+). Any organization relying on the legacy MPX exchange path with Teamcenter needs to confirm which MS Project version is actually in use on the scheduling side — newer MS Project installs may not open/save MPX at all without a conversion step. (Source: aggregated from Microsoft Q&A discussions on MPX support, https://learn.microsoft.com/en-us/answers/questions/4840051/mpx-is-not-read-correctly-by-microsoft-project-sta and https://docs.fileformat.com/project-management/mpx/)
• Resource field name matching is required. For an MPX import to correctly populate resources, the resource field names in the MPX file must match the field names expected by the receiving tool (Microsoft Project or Teamcenter) — a mismatch silently drops or mis-maps resource assignment data rather than throwing an obvious error.
• Calendar conflict handling during import: when importing MPX/calendar data, if a calendar record has already been added to the system by another user, the importing tool surfaces the message "Calendar record was already added by another user. The other user's data will be used." This means calendar definitions are effectively first-write-wins across concurrent imports — a real risk if multiple schedulers are importing overlapping calendar definitions into the same Teamcenter environment without coordinating who "owns" the calendar master copy.

Modern Path: Teamcenter Microsoft Project Integration

Beyond the legacy MPX format, Siemens/partners also offer a dedicated Teamcenter Microsoft Project Integration connector that synchronizes work breakdown structures, tasks, dependencies, milestones, and status updates bi-directionally between the two systems, aiming to reduce duplicate data entry and manual handoffs, and improve traceability from requirements/product structure through to project tasks. (Source: aggregated vendor description via search, no single canonical URL confirmed — treat as directional context rather than a hard technical spec.)

Implementer Takeaway

Before standing up any MS Project ⇄ Teamcenter exchange:

1. Confirm which exchange mechanism is actually licensed/available for the Teamcenter version in use (legacy MPX vs. a dedicated integration connector) — they are not interchangeable and have different version support windows.
2. Establish a single owner for calendar master data before multiple people start importing schedules, given the first-write-wins conflict behavior noted above.
3. Validate resource field-name mapping explicitly as part of any pilot import rather than assuming a clean pass-through — this is a documented, recurring failure mode.