IPP&E, Earned Value Management, and EIA-748 — How the Pieces Fit

What IPP&E is for, per Aviation Week Network

Aviation Week Network's "Integrated Program Planning And Execution" page (a Siemens Digital Industries Software placement/profile) frames IPP&E as a response to a specific pain point in aerospace and defense: most A&D organizations run program management on "disconnected tools (Word documents, Excel spreadsheets, various scheduling software)," which the article says makes it "nearly impossible" to get a clear, current view of program status — and calls this out as a major contributor to program failures. Source: Aviation Week Network.

IPP&E's pitch is to integrate cost, schedule, and technical requirements into one program management system with full traceability across program artifacts, rather than reconciling separate tools by hand.

WBS structure, as described by Aviation Week / Siemens

The article describes IPP&E's WBS as a hierarchical decomposition: phases → deliverables → work packages, with "work elements" as the lowest, actionable tier — the level where tasks are actually scheduled, budgeted, and dated. This maps directly onto the classic EVM work-package/control-account model (see below) even though the article doesn't use DCMA or EIA-748 terminology explicitly.

Explicit EVMS integration claim

Per the same source, IPP&E's "Business Process Integration" capability includes "detailed process mapping, configuration management, and earned value management system (EVMS) integration with third-party pricing software." This is the clearest direct statement found in this research that IPP&E is positioned to plug into an EVMS environment rather than being a full EVMS itself — it hands off to specialized pricing/EVM tools (consistent with the Cobra/Acumen ecosystem — see the companion file ippe-cost-schedule-tool-integrations.md).

Corroborating language from Siemens' Stottler Henke / Aurora partner page

Siemens' own partner page for the Aurora Intelligent Scheduling integration states IPP&E "provides a systems approach to program planning and execution by integrating cost, schedule and technical requirements in a fully planned, resourced and budgeted program management system," and explicitly says it "supports Integrated Master Plan, Integrated Master Schedule and Earned Value Management." Source: Stottler Henke — Siemens IPP&E with Aurora Intelligent Scheduling.

This confirms IPP&E is explicitly marketed around the DoD-standard IMP/IMS (Integrated Master Plan / Integrated Master Schedule) artifacts that EIA-748-compliant programs are required to produce — the IMP defines program events/accomplishments/criteria, and the IMS is the detailed, resource-loaded schedule that traces to them. IPP&E's "work element" tier is the natural landing spot for the work packages that an IMS schedules and an EVMS earns value against.

What could NOT be substantiated

Despite targeted searches, no Siemens or third-party document was found that explicitly maps IPP&E's WBS/OBS objects to the 27 EIA-748-E guidelines (or legacy 32 criteria) point-by-point, nor any document walking through a DCMA 14-point schedule assessment in the context of an IPP&E-generated IMS. General DCMA 14-point and EIA-748 background is well documented publicly (e.g., Deltek's DCMA 14-Point explainer, Humphreys & Associates on EIA-748-E), but nothing ties those frameworks to Teamcenter/IPP&E specifically in public material. Treat the WBS/OBS-to-EVMS mapping in this KB as inferred from IPP&E's stated capabilities plus general EVM industry practice, not as a Siemens-published crosswalk.

Note on a naming collision

"IPP&E" (Siemens Teamcenter, Integrated Program Planning & Execution) is easily confused with SAP iPPE (Integrated Product and Process Engineering), an unrelated SAP module for production/process structure modeling that also appears in Teamcenter Gateway for SAP (T4S) documentation (e.g., the "ippe_transfer" configuration guide section at docs.plm.automation.siemens.com). These are different products from different vendors solving different problems — see ippe-naming-collision-sap-ippe.md for detail.