Aerospace Teamcenter Deployments: Two Real-World Data Points

Two independent, real (if thin) aerospace-sector data points on Teamcenter deployments touching Program Planning. Both are attributed but neither provides deep technical detail on Schedule Manager configuration specifically — included because published aerospace case studies naming Program Planning are genuinely scarce in the public web, consistent with what was found researching Capital's practitioner footprint.

1. Exotic Metals Forming Company (via Applied CAx)

Source: https://www.appliedcax.com/resources/teamcenter/plm-case-study-exotic-metals-forming-company-teamcenter-implementation/

Applied CAx (a Siemens implementation partner) describes hands-on consulting work with Exotic Metals Forming Company, an aerospace manufacturer. Per the case study:

• Before the engagement, Exotic Metals was experiencing slow response times and a PLM system prone to crashes, which was actively hurting user productivity.
• Applied CAx partnered with them to streamline and maintain the Teamcenter PLM installation, described as improving business processes and realizing more value from the existing PLM investment.
• The case study explicitly locates Program Planning within "the planning quadrant of Teamcenter," executed in combination with requirements management, document management workflows, and change management alongside program management — i.e., Program Planning is framed as one leg of an integrated planning quadrant, not a standalone module.
• Reported outcome: high confidence from Exotic Metals that Teamcenter would help them hit future targets.

No specific Schedule Manager configuration, calendar, or resource-loading detail is given in the available case study text — this should be treated as a directional/relationship case study rather than a technical deep-dive.

2. Aerospace/Defense Teamcenter Implementation — ITAR Context (via a public resume posting)

Source: https://www.hireitpeople.com/resume-database/81-project-manager-resumes/170488-teamcenter-implementation-project-manager-resume

A publicly posted resume (candidate identity not verified/not the point here — cited for the concrete configuration detail, not the person) describes serving as system architect on a global Teamcenter PLM implementation, working directly with Siemens architects, using Agile/Scrum for the implementation project itself. Specific, concrete details relevant to program-planning implementers:

• Data management model was mapped specifically for the aerospace division, with explicit attention to "requirements for security, usability, and data structure" as distinct concerns to design around — i.e., the data model isn't one-size-fits-all across an enterprise that has both aerospace and non-aerospace divisions.
• ITAR (International Traffic in Arms Regulations) compliance was an explicit review criterion for the system architecture — a real, concrete regulatory constraint that shapes how program/project structures, access control, and data partitioning must be designed in aerospace/defense Teamcenter deployments (relevant to anyone architecting Program Planning hierarchies where certain programs/projects must be access-partitioned for ITAR reasons).
• Interface/integration point selection (reporting, data flow, integration) was handled as its own explicit workstream separate from the core PLM rollout.

Implementer Takeaway

If deploying Program Planning/Schedule Manager in an aerospace or defense context, plan for ITAR-driven access partitioning as a first-class design constraint on the program/project hierarchy (who can even see a given program's existence, not just its content) — this is a concrete, real-world consideration these two sources both gesture at, even though neither provides the actual TC access-control configuration recipe. Neither of these is a substitute for actual ITAR/export-control legal guidance — treat this as "remember to ask the question early," not implementation instructions.