IPP&E Overview
IPP&E objects
During the integrated program planning and execution process, Teamcenter objects are created at various stages to store product and process data. These objects are associated with each other through relationships. (The source page includes a conceptual diagram of these business objects and relationships — not reproduced here as it is an image.)
| Object | Description |
|---|---|
| Project WBS | Work breakdown structure that is associated with the program, project, and subprojects. |
| Common WBS | A WBS template that you can use to create a project WBS. |
| WBS Root Element | This is the top node of the WBS hierarchy. If the Common WBS property value of WBS root element is True, the structure is the common WBS. If the value is false, the structure is the project WBS. |
| WBS Element | This is a node in the Work Breakdown Structure (WBS). A leaf node of the WBS is referred to as a work package, which represents a task in the program schedule. |
| Task Info | It contains schedule information for the WBS work package. |
| Functional Work Package (FWP) | It contains details of the work for a specific functional organization. Many work packages, each created for a distinct functional organization, can fulfill the work identified for a WBS work package. |
| FWP Estimates | It contains the estimates, including labor, material and other costs for a functional work package. |
| Functional Org | This is a specific functional organization node in the organization structure of a company. An Organizational Breakdown Structure (OBS) is a hierarchical organization of functional organization nodes. Individual nodes of the OBS are called OBS elements. |
| Deliverables | This refers to the deliverable data resulting from the execution of a functional work package. |
| Risk/Opportunity | This is used to indicate a risk or opportunity that may occur during the execution of the program. A risk may result in increasing the cost or delaying the completion of the program. An opportunity may reduce the cost and can have a positive impact on the program schedule. |
| Program | It refers to the project that is being planned and executed. |
| Integrated Product Team (IPT) | This is the hierarchical representation of the team responsible for the planning and execution of a program. |
| Integrated Master Plan (IMP) | This is an event-based, top-level plan consisting of a hierarchy of program events. Each event is decomposed into specific accomplishments, and each specific accomplishment is decomposed into specific criteria. |
| Event | It refers to a program assessment point that occurs at the culmination of significant program activities. |
| Accomplishment | This is the desired result prior to or at the completion of an event indicating the level of the program's progress. |
| Criteria | It refers to the definitive evidence that a specific accomplishment has been achieved. |
| Contract | It refers to an agreement to provide a product or service to a customer. It typically includes product and data requirements, statement of work, and terms and conditions. |
| Contract Line Item Number (CLIN) | This constitutes part of a contract that breaks down the contract based on the commodities being procured. CLINs help identify the supplies or services to be acquired as separately identified line items in a contract to provide for accounting traceability. |
| Data Requirement Item | This is an individual data requirement for a contract. A collection of these objects is called the Contract Data Requirement List (CDRL). |
| Requirement | This refers to the requirements for the product. |
| Engineering Bill of Materials (EBOM) | This is the engineering definition of a product. |
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/ippe/dyf1737238867045/xid1926928.html · retrieved 2026-07-10