Cancel
Showing results for 
Search instead for 
Did you mean: 

The Teamcenter BOM Line Specification

Community Manager Community Manager
Community Manager

Introduction


Also known as the “Hybrid BOM” concept, non-geometric parts may be added to a purely non-geometric product structure, or one that was generated by managed mode NX.


In the past, the way to add a non-geometric part to another non-geometric part was to use the Product Structure tab. On the Teamcenter Item spec, the product structure at a parent level would be defined to own the part defined through its connection, as seen at right. The child part could have its own Teamcenter Item spec (which means that Rulestream would create that Teamcenter item, later to be revised or overwritten), or it could simply have a property that defined an existing item/revision in Teamcenter. Rulestream could then drive the BOM Line attributes mapped in the Product Structure tab.

 

v1.jpg

 

 

Warning: Though still functional in this release (8.14.0), the product structure tab of a Teamcenter Item Spec is deprecated and, as of Rulestream 8.16 the structure tab of the Teamcenter Item Spec will no longer be included in Rulestream Architect.  The 8.16.3 platform upgrade will remove those obsolete rules outright.  We recommend that you use, or migrate to, the Teamcenter BOM Line Specification to create product structures.  

 

However, we have identified one scenario with a pure non-geometric structure where you should continue to use the Product Structure tab. If you have a PCM where a level is skipped between Teamcenter item specs, the BOM line spec will not work. This will be fixed in the next version.

 

V2.jpg

 

  

In 8.14.0, we introduce the Teamcenter BOM Line Specification. Instead of a top-down approach where the product structure is defined in the parent, we use a bottom-up approach where the child determines whether it belongs in the product structure of the parent’s Teamcenter Item specification.

 

The BOM Line Spec may be placed in a part family anywhere in the product control model where a BOM Line needs to be added to a structure and/or where its BOM line attributes driven. It will always look up to its parent (or the next closest parent which contains an enabled Teamcenter Item Spec) so it cannot, by definition, be positioned on the top-level part. Mappings for the BOM Line attribute reside in that child part.

 

The Teamcenter BOM Line Spec can co-exist with the Teamcenter Item Spec as these are now independent of each other. In this case, the Item Spec causes its item to be created/revised/overwritten; the BOM Line Spec causes that item to be added to its parent’s structure and/or the corresponding BOM Line attributes to be updated.

 

As seen below, the Teamcenter BOM Line Spec can be Enabled or Disabled. As a rule author, you may specify the quantity of the BOM Line. You may also define the Item ID of the Teamcenter item (which can be an existing item, or one that is created by Rulestream). The Revision ID is optional as Rulestream only supports an imprecise structure at this time.

 

v3.jpg

 

 

In the case of managed mode NX, the existence of a geometric BOM Line is controlled solely by the NX model, as is the Item ID and the Revision ID. As such, they should remain blank on a geometric part. BOM line attributes (like Find Number) on an enabled BOM Line spec will be driven on the geometric BOM Line.

 

When is the product structure created or modified? As with the Teamcenter Item Spec’s product structure tab, the g_rsEngineer.ReleaseOutput function must be called with the “Structure” argument in custom.vb, typically in the RsUserRelease event. Please refer to the Teamcenter Manager for Rulestream 8.14 document for more details.

 

Prerequisites

In order for Rulestream to keep track of the product structure that it creates, a new Note Type for the BOM line must exist in the Teamcenter Business Modeler IDE (BMIDE). A Teamcenter administrator should make the following changes, as some of these operations will require administrative rights.

 

A Note Type is an object associated with a product structure occurrence in a Structure Manager Bill of Material

  

You will need to access the Note Type editor in the BMIDE by navigating to the ExtensionsOptionsList of Note Types folder. Right-click on that folder and select New Note Type.

 

  • The Project box defaults to the already-selected project.
  • In the Name box, type the name you want to assign to the new note object in the database. When you name a new data model object, a prefix from the template is automatically affixed to the name to designate the object as belonging to your organization, for example, A4_RSNote or V2_RSNote.

v4.jpg

 

When you type the name of a new note type, do not use a period (.) in the name. The note type does not function property if a period is placed in the name.

 

  • In the Display Name box, type the name as you want it to appear in the user interface, or accept the default.
  • In the Description box, type a description of the new note object.
  • Uncheck the Attach Value List check box.
  • Click Finish.

The new note object appears under the List of Note Types folder. To save the changes to the data model, choose BMIDE→Save Data Model, or click the Save Data Model button on the main toolbar.

 

Deploy your changes to the test server. Choose BMIDE→Deploy Template on the menu bar, or select the project click the Deploy Template button on the main toolbar.

 

After deployment, test your note in the Teamcenter rich client by viewing BOM Line properties in Structure Manager:

 

  • In the My Teamcenter application, right-click any item or item revision and choose Send To→Structure Manager.
  • In the Structure Manager application, right-click the item and choose Properties.
  • Scroll to the bottom of the Properties dialog box and click Show empty properties.

All the BOM Line properties appear. Your new note appears near the bottom of the dialog box.

 

As an administrator in the My Teamcenter application, select EditOptions from the menu and click the Search link at the bottom of the dialog box, as seen at left. Add a new preference named “RS_BL_NOTE” and assign the value to the Note Name.

 

v5.jpg

 

In order for occurrence notes to sync up with the attributes in NX, set the PS_Structure_change_condition to the Note Type, as seen below.

 

v6.jpg

 

To make sure that the Note has been created and assigned correctly, manually open NX from Teamcenter and create a sample assembly. The Note should show in the NX attributes when you check the child instance attributes.

v7.jpg

 

Interaction Between Non-Geometric and/or Geometric Parts

 

Case 1: An existing item is placed under a non-geometric ETO item. The BOM Line Spec will cause the child part (defined as an existing item ID) to be placed into the product structure of its parent (containing an enabled Item Spec). Mapped attributes in the BOM Line Spec are driven by Rulestream.

 

v8.jpg

 

The parent is the nearest parent that contains an enabled Item Spec. The BOM Line Spec will continue up the tree until if finds an enabled Item Spec.

 

Case 2: An item managed by Rulestream is placed under a non-geometric ETO item. The Item Spec on the child will cause an Item to be created, revised or overwritten. The BOM Line Spec, whose Item ID and Revision ID are set to blank, will cause the child part to be placed into the product structure of its parent (containing an enabled Item Spec). Mapped attributes in the BOM Line Spec are driven by Rulestream.

 

v9.jpg

 

Case 3: An existing item is placed under a geometric ETO item. The NX Spec and Item Spec on the geometric part causes the NX template to be cloned upon load. The BOM Line Spec will cause the child part (defined as an existing item ID) to be placed into the product structure of its parent (containing an enabled Item Spec and an NX spec). Mapped attributes in the BOM Line Spec are driven by Rulestream.

 

v3.jpg

 

Case 4: An item managed by Rulestream is placed under a geometric ETO item. The NX Spec and Item Spec on the geometric part causes the NX template to be cloned upon load. The Item Spec on the child will cause an Item to be created, revised or overwritten. The BOM Line Spec, whose Item ID and Revision ID are set to blank, will cause the child part to be placed into the product structure of its parent (containing an enabled Item Spec). Mapped attributes in the BOM Line Spec are driven by Rulestream.

 

v4.jpg

 

Case 5: A geometric ETO part is placed under a geometric ETO item. The NX Spec and Item Spec on the geometric part causes the NX template to be cloned upon load and creates the geometric product structure. The BOM Line Spec, whose Item ID and Revision ID are set to blank, will cause the mapped BOM Line attributes to be driven for the geometric child.

 

v5.jpg

 

Case 6: A geometric standard part is placed under a geometric ETO item. The NX Spec and Item Spec on the parent geometric part causes the NX template to be cloned upon load and creates the geometric product structure. The child part (set as a standard part) is added to the product structure upon load. The BOM Line Spec, whose Item ID and Revision ID are set to blank, will cause the mapped BOM Line attributes to be driven for the geometric child.

 

v6.jpg

 

Caveats

  

  • Keep in mind that the BOM Line Spec is dependent on its position within the product control model, as it will always traverse up the tree to find the nearest enabled Teamcenter Item Specification.
  • For the BOM line attributes, Rulestream does not yet support different locales when mapping dates and double numbers. Only the U.S. locale is supported.
  • If you disable a Teamcenter Item Spec on a part family that also contains a Teamcenter BOM Line Spec, it will disable both
  • For pure non-geometric structures, we have identified a problem with the BOM Line spec if you have a product control model in which a level is skipped between Teamcenter Item Specs, as shown at right. In this case, you should continue to use the Product Structure tab. This will be fixed in an upcoming release.

v1.jpg

 

  • For pure non-geometric structures, the BOM Line Spec may reside at multiple levels within the product control model.

For TCIN, note that as of this release, non-geometric parts are limited to a top-level geometric part, as seen below.V2.jpg

 

  • For TCIN, we currently support the NX Spec only. NX Assembly and NX Child specs will be supported in a future version.
  • For TCIN, do not place a geometric part under a non-geometric part, as that case is not supported.
  • For TCIN, a known issue is that Teamcenter operation on the top-level ETO geometric part must be set to “Create” or “Revise” for non-geometric parts to be added to a product structure that has other geometric parts in it. The “Overwrite” operation will be supported in a future release.
  • For TCIN, if you have only a top-level ETO geometric part (and no other geometric parts underneath it), you are not limited to “Create” or “Revise” – you may also use “Overwrite”.