Teamcenter persistent object manager (POM) layer defines the data model architecture, or schema, using classes and business objects.
The persistent representations of the schema. Each class is mapped to a primary business object whose name is the same as the class name.
Teamcenter Data Model Schema is hierarchy based, it means there is base level object through which all the object in the system are derived. The base object in Teamcenter is called POM_object. All Business classes in Teamcenter either directly or indirectly (through hierarchy) is derived from workspace object. Due to hierarchical schema, the parent class attributes are derived to children classes. For example, creation_date from POM_application_object are derived to all of its children classes. Parent and children classes in Teamcenter are linked usually through PUID but this could vary based on classes.
The logical representations of the classes. Business objects are building block of Teamcenter. It resides above POM Objects or DB Classes. Business Object can be seen as actual representation of real life entity which are encapsulated as Business object. The underlining objects are still persistence schema classes.
Major characteristics of business object:
Business object have persistence or non-persistence (compound, runtime, typed reference, etc) properties.
Business objects are related to each other using relation object.
Business objects are controlled through rules like naming rules, condition, extensions, GRM rules, display rules, deep copy rules, etc.
Business objects can be configured with standard icons or property overlay icons.