Team Centre Automotive Edition (TcAE)!

As the month is nearing an end, the song by the band Greenday, ‘Wake Me Up When September Ends’ sounds so true. The economic uncertainty all around indeed signals that its time to wake up. However, amidst fears of recession and subsequent job cuts, this is a time when the importance as well as effectiveness of PLM as a revenue generator comes into the picture. At a time when manufacturing organizations will try to optimize processes, PLM as a tool will gain more prominence as the motive would be to at least maintain the same level of output but with lesser input.

Coming to the point, I was wondering what this post would be all about. The problem was not that I had very few things to write but the problem was that I had acquired a great deal of knowledge about E-Matrix and TeamCentre. I initially thought of penning down E-Matrix related points but postponed it to some later point of time.

Hence, we will discuss some basic features and functionalities about TcAE (Team Centre Automotive Edition).

To begin with, Team Centre is a PDM (Product Data Management) tool and is a propriety product of Siemens. Although it is a PDM tool, unlike some of the other PDM tools, it, in fact, is not crude and ugly. Rather, it is smart and very user-friendly. The basic advantage of TcAE is the global connectivity across all sites (different locations). This promoted reuse as well reduces time to produce and market. The connectivity is facilitated by ODS (Object Directory Service).

The basic premise of TcAE data storage is an Item. An item is a repository of all possible data related to a part or assembly. These include the 3D model, the drawings and other parameters. However, as is the case, these data contained in an item is not the physical data but the metadata, that is, the data about the data. A dataset is nothing but the link (metadata) about the 3D CAD model. Along with the dataset, comes the drawing which is another product of the CAD system. Likewise, there are the integration parameters between TcAE and the CAD tool and other systems, so that the associated data of the part/ assembly can be viewed in that system. The item code for each code is a vast data source in itself. It can depict the company, the location where the part is made/ created, etc.

The processes which a part number (Item ID in TcAE) undergoes, are called workflows. Workflows help to take the part/ item through different stages of product lifecycle by different release processes. These stages are nothing but the milestones which define the degree of usability of the part. While certain workflows are reversible, many of the crucial workflows are irreversible.

An item contains many revisions. Revisions are nothing but the different modifications carried out on a part/ assembly at different stages of use. Each revision has got its unique datasets. A majority of the workflows are carried out on these revisions of a part/ assembly as in a product structure, the revisions are used and not the part. To avoid ambiguity, a part goes through different stages (iterative changes) of change depending on the use. One assembly may use the first revision of a part while another assembly may use the second revision of the same part.

Another important and efficient utility is the PSE (Product Structure Environment) mode which displays the BoM (Bill of Material) structure of a part/ assembly. Various BoM utilities and rules can be set up in this mode. The PSE utility in this way proves to be an added advantage for TcAE as apart from the PDM characteristics, it imparts PPM characteristics of PLM to TcAE.

To wrap up, the most significant feature in the entire kit is the DMU (Digital mock Up) utility. As is obvious, DMU is the visualization of the BoM structure or for that matter the part/ assembly. Whatever is the CAD model, DMU presents the exact replica of that but only at the surface level. The parts which appear at the inter-face, are empty and hence, howsoever complex an assembly may be, it will load and will be visible in no time. The greatest utility of this functionality is that, it acts as a virtual testing tool eliminating the need for prototyping or at least limiting it. The fitment issues and tolerances can be checked visually without any cost.

Hence, TcAE is not only useful for the purpose which it has been designed but all the more user friendly. I hope to dig deep in the coming posts of both TcAE and E-Matrix and also regarding their integrations. Till then, syonara and yes, I will next wake up when September ends!

The Basics (EBoM Structure)!

Well, before getting into the future possibilities of PLM and all that, or rather, without getting into all that, which is all the more common with other existing blogs, let me explain what I have understood of the basic EBoM (Engineering Bill of Materials) structure. The structure may vary from organization to organization but the basic concept remains the same.

At the top stands the basic model, beneath which lie many options belonging to various families under which we have branches of groups and finally, under each group, we have assemblies and parts. So, it is more or like the hierarchy as depicted below:

The ‘Basic Model’ is nothing but the complete vehicle or product which the organization is producing. This may be an electrical appliance or an electronic device or for that matter an automobile. This ‘Basic Model’ may be present in the form of various variants. However, importantly, each variant is a complete product in itself, which in fact, is the final finished good rolling out of the line. Let us take the example of tractor industry. A complete tractor is a ‘Basic Model’.

A ‘Basic Model’ is constituted by various families. Each family is more or less a primary feature without which a ‘Basic Model’ is incomplete. Some examples of families are Engine family, front tyre family, Battery family, etc.

Families contain ‘Options’. Options are completed features from a family. In a family, there may be present multiple options which may go into a ‘Basic Model’ whose applicability is off course governed by certain features like fitment or engine H.P. For example, from the family Engine, there may be two options, 55 HP and 65 HP. It is to be noted at this juncture that only one ‘Option’ goes from each ‘Family’ into one ‘Basic Model’.

‘Groups’ constitute ‘Options’. Groups are sub-features which are assembled to form a feature (option). Practically speaking, groups are nothing but the physically separable parts, which when assembled, forms the feature. A mirror may be a group with parts or assemblies like the frame, the holder bracket, etc.

Each ‘Group’ has assemblies or parts. These are lowermost entities in an EBoM. These are the basic constituents, both from the engineering as well as the manufacturing points of view. When a designer starts from scratch, he or she starts from here.

Hope, this was more than informative as the significance of this structure will be realized as you get into the applicability mode of PLM products.

Till we meet next time, signing off!!

The Beginning...

Sometimes it feels amazing to observe some brand becoming synonymous to the very competency it represents. We do not say we will search online, we GOOGLE! We want Ariel (detergent powder) but ask for 'Surf' to the shopkeeper. And when it comes to passenger cars, people want a 'Santro' which is a 'Maruti'.
The continual evolution of SAP is no different and has completely replaced the word 'ERP' from the lexicon. Likewise, another aspect which is emerging, although in a more dormant manner, is PLM (Product Lifecycle Management). Now some pundits will even argue that ERP is an aspect of PLM or the other way around and everyone have certain bases to support their arguments.
The point however, is not categorizing the two domains, but to focus on the opportunity which PLM is bound to bring in the coming future, which surely, is not far ahead.
The very reason I have started this web-blog is to not only try to seize this opportunity but also make the readers aware of how magnanimous its consequences can be.
To introduce, I am neither some 'Platonic Pundit' in PLM nor a marketing/ sales lead of some PLM vendor. I am like majority, a user. I started my career after graduating from college in the Product Development department barely some 8 months ago. I chose the Engineering Services functionality putting aside the 'designer's hat' just for the sake of PLM.
After about 6 months of what I have experienced, PDM (Product Data Management) and PPM (Product and Portfolio Management). Off course, I try to brief myself with ERP proceedings. However, I would love to begin with what I have learnt and will continue to post my understandings, in my own way. The sole reason for not copying some wiki PLM paragraphs and incorporating them into my posts is that I can foresee the applicability of PLM beyond manufacturing industry.
I am currently engaged with some prolific PLM systems like E-Matrix and Teamcentre. The associated CAD system is Pro-E and my competency is a PPM software, ICP (Iveco Configuration Platform) which an inbuilt software of the organization I am working.
I will also post about the glitches I encounter and would welcome comments, suggestions and criticisms, anytime and every time.
Till we meet next time and talk something which is more PLM related, Ciao!