Automotive Supplier Process (ASP): An Industry Template for Program Planning

Sources:

• https://blogs.sw.siemens.com/teamcenter/program-management-in-plm-has-arrived/
• https://www.lmtecdigitalsolutions.com/en/plm-solution-packages (partner/consultant description)

Origin

According to Siemens' own account of Program Management's history in Teamcenter, a group of automotive customers worked directly with Siemens to build an industry-specific template called the Automotive Supplier Process (ASP), aimed at solving the specific challenge of planning and executing supplier-facing programs/projects from a single location (rather than juggling separate supplier PM tools per program). This was cited as a real driver behind eventually making full Program Planning a native Teamcenter capability — the ASP template's usefulness reportedly attracted interest from customers outside the automotive domain, which pushed Siemens to generalize the pattern.

What It Addresses

ASP-style templates are positioned around Tier 1/Tier 2 automotive supplier integration: giving an OEM or Tier 1 program office standardized, repeatable program/project structures specifically shaped for supplier program management — i.e., pre-built program hierarchies, milestone sets, and gate structures matching automotive supplier development cycles (APQP-adjacent cadences), rather than a generic blank program template.

Consultant Framing (LMtec)

A partner consultancy (LMtec Digital Solutions) offers what it calls a "process and functional-based Automotive Supplier Package (ASP)" specifically to help define a customer's overall PLM strategy while integrating Tier 1/Tier 2 suppliers into the program structure — framed as leading toward "an integrated process-oriented solution" rather than a bespoke one-off configuration per customer.

Implementer Takeaway

If your organization operates in automotive (OEM or supplier), check with your Siemens rep/implementation partner whether an ASP-derived industry template is available or has been built by another customer with a similar supplier-program structure, rather than designing the program/project/subproject hierarchy from a blank slate — this is a real, named prior-art pattern rather than a generic "best practice" suggestion. Note this is one specific example of a broader pattern: several industries have built (or are building) their own named vertical templates on top of the same core Program Planning object model (programs/projects/subprojects/tasks/milestones described in the hierarchy file in this knowledge base).