≡ Menu

Enhancement Request: An External Dependencies BMIDE View

Share the knowledge

I know I should lay off the BMIDE, but I have another complaint suggestion.

As you probably know a BMIDE data model has lots of dependencies and most of those dependencies exist within the data model itself. For example, a property may have a naming rule attached, and that naming rule may depend on a List of Values (LOV). The property, naming rule, and LOV all exist within the data model.

But data models also contain external dependencies. These are dependencies on things that aren’t in the data model. They are expected to be defined in the Teamcenter instance before the data model is deployed. And those are the problem.

External Dependency Examples

Groups can be an external dependency for Type Display rules which determine which groups can create which item types. The type display rules are in the data model but they refer to groups in the organization structure which are not. And if you try to deploy a template to a Teamcenter instance which doesn’t have those groups defined you will get an error.

PLMXML Transfer Modes can also be an external dependency. I’m not even all that sure what in the data model refers to transfer modes. But I know it’s an issue because the other day we spent a lot of time dealing with a template that failed to deploy because a transfer mode was missing. The template had been extracted from an upgraded Teamcenter Engineering instance which had a lot of accumulated junk in it, the dependency on this transfer mode being one such item. We had to hand-edit the XML of the data model to make it refer to a generic out-of-the-box transfer mode that we knew existed.

External Dependency BMIDE View

My suggestion is to add a new view to the BMIDE that shows all the external dependencies in one place. I think they should be organized by type — groups, transfer modes, etc. Each external dependency should also indicate where the dependency is defined, such as “DojoDesignItem – Type Display Rules”. If that listing can also be linked to the actual definition so we can click on it and go to where it is defined, that would be great.

Armed with this information we could check that the target systems already have the necessary groups, transfer modes, etc. defined or we could make sure we’ve added commands to the install scripts to create the necessary definitions.


I could be wrong but I don’t think there’s anything particularly challenging about this idea, other than just the time it takes to implement. I believe that the list of all possible dependencies is well defined. So all the BMIDE would have to do would be to scan for the types of XML elements which may have external dependencies and then collect any references that it finds.

Enhancement Request?

Is this an enhancement we should try to get Siemens PLM to implement? Do you have a better suggestion? If you just want to show your support, click the Google +1 button.

  • Suyog

    I have created a BMIDE project having two custom template(for eg.) Now I want to to add only two Items (including IR,IMF and Item Rev Master Form) to another server.I can do it using copy paste from default.xml and importing into another server using Import->Template file as well as localization file option.Can we have any other option for this scenario?

    • http://plmdojo.com/ Scott Pigman

      If you knew ahead of time you wanted to break those two types out separately the thing to do would be to put them in their own template. Of course, you probably didn’t realize that ahead of time and now you are stuck. You could use RMB → Organize → Move to extension file… to move the definitions to their own extension file instead of hand-editing the XML — but I’d verify the results carefully.

      FWIW, I know that SPLM knows that they need to do more to make it easier to refactor the data model.

  • Brijesh Kr85

    how can we do data migration(Solid Edge ST4 to Teamcenter Express 5.1 ) with some mandatory attributes in item revision and its revision master form  , i tried it with “Add to TeamCenter ” OOTB utility ,  that comes when you install SEEC embedded client and Administrator and it created items without considering the mandatory attributes…if you do it manually it will not allow you to create items if you have not filled the mandatory fields….how to handle this?

    • http://plmdojo.com/ Scott Pigman

      I’m sorry, but I’ve never worked with solid edge or the utility you mention. I suggest you try the forums at plmworld.org. 

    • https://twitter.com/total_plm Ilya Chaykovsky

      you clarify the issue a bit? Migration from what to what (from file system to
      TCX5.1 or ?)? BTW have you tried to use OOTB data preparation utilities (link
      fixup, analyze, change links)?

Optimization WordPress Plugins & Solutions by W3 EDGE