Siemens Documentation - Modeling Components
Siemens Documentation - Modeling Components
Modeling Components
In order to model a component, for example, to add entities or modify entities within the component, you must activate Modeling mode. Select a component and choose Modeling tab
→ Scope group → Set Modeling Scope to activate Modeling mode and modify the selected component, as required.
A new icon overlay displays to indicate that an object is currently under modeling.
Note It is possible that a parent entity is open for modeling but has a child entity that cannot be modeled, for example, a super component.
If you have not completed modeling, you can save your work in Teamcenter (refer to Teamcenter Update). In this case, the default configuration causes modeling changes of the
unfinished component (known as a local component) to be ignored in Teamcenter. Additionally, the revision remains unchanged. However, when you open the component again in
Process Simulate, your latest work is available and you may resume modeling.
Note The Teamcenter Portal Viewer displays 3D data sets with the following attributes: role=Iman_rendering and type=DirectModel. If you configure Process Simulate to persist
modeling changes in a data set with these attributes, your latest modeling changes are always visible in Teamcenter. If, however, you configure Process Simulate to persist
modeling changes in a data set with the following attributes: role=Iman_references and type=TMX3DRep, the Teamcenter Portal Viewer shows the state of the object before
modeling, while Process Simulate shows the latest modeling changes.
When you are satisfied with the results of your modeling session, use the End Modeling commandfollowed by Teamcenter Update to update Teamcenter. The new data now persists in
Teamcenter and its revision is updated.
Note If you are not in Modeling mode, many of the options in the Modeling tab are disabled.
Modeling mode remains activated until you run the End Modeling command.
It is possible to model more than one instance of the same prototype concurrently. In this case, the last instance copied back to Teamcenter is the one that updates the item revision (a
race condition). This feature enables you to make temporary changes before deciding which item to accept.
The following nodes cannot be modified:
Components that use a .CO file
Compounds
Parts
Released item revisions
There are two types of geometry in JT files: XTBRep and JTBrep. Process Simulate provides full support for XTBRep, however, it only provides limited support for JTBrep. You can
open JTBrep components for modeling in Process Simulate and it is possible to perform kinematic modeling. It is not possible to perform geometric modeling on existing JTBrep
geometry, however, new geometry can be created and modeled.
Note Only JTs in the XTBRep format support projecting weld points on exact geometry. See Project Weld Points.
If you inserted a component created using a third-party program, you can use Set Modeling Scope to view frames stored in the PMI section of the JT file. Performing End
Modeling stores the frame information in the same way as a component originally created using Process Simulate.
Changing the name of a component requires modeling.
Note Process Simulate takes into account the access permissions in Teamcenter before allowing modeling of objects.
It is not necessary to end your modeling session before closing Process Simulate. In this case, objects remain open for modeling the next time you open Process Simulate.
When using End Modeling, the system updates all the instances linked to that component.
You can configure Teamcenter to block modeling changes to released items. This situation occurs when an item has been released in Teamcenter while opened for
modeling - Process Simulate displays an error message when you run Teamcenter Update.
https://docs.plm.automation.siemens.com/tdoc/tecnomatix/13.1.2/PS_TC#uid:index_xid1015772:Modeling_Menu:xid1163656:Set_Modeling_Sco… 1/1