≡ Menu
CollegeGirlReadingABook
Share the knowledge

A question I get with some regularity is some variation of, “How do I get started as a Teamcenter ITK developer?”, or, “…as a Teamcenter customizer?” It’s gotten to the point where I either have to:

  1. start ignoring all of those emails.
  2. Write a post that I can point people to which answers the question once and for all.

After much deliberation, I decided to go with option b.

I have to warn you that there is no magic bullet to becoming a Teamcenter customizer, but here are three basic approaches to getting started: [click to continue…]

{ 6 comments }
Share the knowledge

Recently I was asked for my thoughts regarding using a one BOM or a two BOMs to represent parts and designs. In one approach you store a single BOM which contains all of your CAD and business data in a single BOM structure. In the other you use one BOM strictly for the CAD designs and another for the business data and associate the two. So, which approach is better? What are the pros and cons of each? What considerations should you think about?

I’m very much still figuring this stuff out myself; I have my opinions, but honestly I don’t the experience yet to back up my opinions. I’ll share what I currently think; hopefully it’ll spur your own thinking on the matter, if nothing else. [click to continue…]

{ 32 comments }
Share the knowledge

One of the trickiest things about working with the BMIDE is making sure that your template won’t introduce any unwanted or, worse, invalid, changes to the the system. You have to keep track of what changed between successive versions of your data model — for that matter, you have to keep track of which version was last deployed. It can be rather daunting.

That’s why I’m pleased to share this recipe for checking your current template against what’s actually live on the system. It comes to use courtesy of long-time FOD (Friend Of the Dojo), The Teamcenter Heretic. TCH has dug into the utilities documentation to come up with a step-by-step process for generating a report that will tell you exactly what will change if you deploy your template.Take a look, I think you’ll find it useful.

– Scott

[click to continue…]

{ 6 comments }
section-1scaledsimplicity.jpeg
Share the knowledge

Does this situation sound familiar? Your company has an in-house system for doing some portion of what is now part of Teamcenter (or Windchill or Aras or…). The Powers That Be have decreed that Teamcenter will replace the homegrown software. Everyone hates the old system. It old and complicated and ugly. When it was new it was state of the last decade’s art. Everyone, from management to users, wants to know how soon it can be replaced and decommissioned.

Well, I’ve been pondering this question myself lately. I think I have the answer you should give them. I say, tell them that you will never get rid of the old system.

Here’s why — and what I think you should do instead.
[click to continue…]

{ 8 comments }
git logo
Share the knowledge

Like any good software developer, I use a source control system daily. But I’ve fallen behind the times. The latest source control paradigm out there is something called a Distributed Version Control System (DVCS). The two main DVCS’s are Git and Mercurial. GitHub, which hosts git projects, seems be getting written up weekly in technology and business publications. I’m playing catch up, but now I understand what the big deal is. The PLM world needs to take notice. We need Distributed PLM systems.

Here’s why. [click to continue…]

{ 31 comments }
Optimization WordPress Plugins & Solutions by W3 EDGE