Folks,

This is a day to day problem which will be there for most of the 2T client users, where there is a chance of users missing the latest update not pushed from the server to their TC_ROOT.

Why it wont affect 4T ?

The main purpose of 4T is easy maintanence, i.e whenever there is any change in the server, OTW and other related services will take care of matching the client machine files with its server version and all missing/moified files are re-pushed to client machines.

In case of 2T?

Consider if there is a change in jar files/xml /properties which need to pushed to all client machines, how do we ensure it is pushed to client machines ?

1. Create a temp version file in server and in all user machine on the first time installation.

2. On each point release modify this particular version file with the latest release number in server.

3. Push it to all client machines ( By default adopted technique ) , replacing the existing version file.

4. Now, compare the version file from server and client machine on each startup of Teamcenter ( Eg : Code In tc_profilevars.bat ) .

5. If both the version files are same, then the Teamcenter will start or it will ask give a message to contact the admin for re-pushing the files to the system.

This will ensure all the files are up to date and the users will not miss any latest updates.

I hope this is one technique , if anybody has another good technique… Its open to share :)

Folks,

Normally when you are doing the upgrade of Teamcenter product from old Teamcenter engineering version to Teamcenter unfied, it will run many utilities to fix the errors with existing datamodel to make it ready for upgrade.

There is a utility called autofix_datamodel which will try to fix all the missing/modified attribute

autofix_datamodel -u=infodba -p=%TC_USER_PASSWD% -g=dba -mode=update -schema_add

So based on the error you will know which particular attribute needs to be added to the data_model.

If you are in mid of upgrade the following commands are used to add the attribute.

1. Set the environment

2. clearlocks -assert_all_dead infodba <password> dba

3. install -add_attr -u=infodba -p=<password> -g=dba <Class_name> <missing_attribute> <values>

4. install –regen_schema_file infodba <password> dba

Folks,

There has been confusion for many users of Teamcenter that there are 2 different options available in Multisite related environment for export

1. Export –> Remote

2. Export –> Object

Case :1

Technical : An explanation for export remote is for exporting any Teamcenter item or object to the remote site. It will be packed in the form of zip files moved to transfer area and send to the remote site using IDSM and RPC protocol.

Simple : If you have done transfer of ownership with export remote , it will change the local site and the data will be updated in the remote site with the ownership actually transfered to the remote site itself.

Case 2:

An explanation for export object is just export the object into local machine or the location provided, it will not actually affect the remote site. So the data will be extracted and placed in the local directory. ( It will modify only the data of the local site and it wont affect the remote site )

Where i can use : In multisite environment if both site is saying as owner, then you can use this technique to make one of the site as replica , and synchronize after it

Folks,

This is an issue which many users will come across in Teamcenter, — ( Seems silly for experts, But it will help new comers and users )

1.Users will initiate the workflow.

2.He wants to cancel/delete the workflow inbetween since its not getting completed properly or not allowed for modification since it is struck.

3. Users will look for Admin for deleting the workflow

4. Instead……….

5. Select the item revision where you have initiated the workflow and check for the where referenced

6. It will give the workflow name which is initiated, select the workflow and select delete.

7. This will delete the workflow which is in between status, Then refresh the item revision so that the “under process” symbol will go and the item will be clear for further modification and create new workflow if needed.

Folks,

Just explore little bit about Precise and Imprecise BOM structure and what will be best for today’s Indian industry ?

BOM :

BOM is the name given for Bill Of Materials, which will be very common name across any Mechanical/Aerospace/Automobile /Construction  industries,

Its defines list of items and their quantity used for manufacturing/Building any product.

Sample BOM screenshot : There are different types of BOM like , EBOM ( Engineering Bill of Materials ) , MBOM ( Manufacture Bill of Materials ), SBOM ( Service Bill of Materials ) and so on.

BOM Teamcenter point of view :

BOM in Teamcenter refers most of the time to EBOM which is Engineering Bill of materials, where the designer will create list of items required for assembly and defines the quantity of it. Most of the companies has enabled automatic BOM option, which means whenever an assembly saved in UG/related CAD application, the BOM is created according to the assembly and attached to the item revision.

BOM is viewed with a Teamcenter module called PSE or also called as Structure Manager in Teamcenter 8 onwards.

There are 2 main difference in BOM structure,

1. Precise BOM

2. Imprecise BOM

What is precise BOM ?

Precise BOM is a type of BOM where item revision are linked together which forms a static structure, which will not get updated based on any criteria or also called revision rules….. ( Here i have to tell about revision rule )

(Revision Rules : Those are rules defined for loading the BOM in desired format based on the rule guidelines set by yourself.

Eg : If i want to see only latest released item revision in the BOM structure u need to set a revision rule and load based on it., )

What is Imprecise BOM ?

Imprecise BOM is a type of BOM where item are linked together which form a dynamic structure and can be loaded based on the revision rule.

How do i know am i using Precise/Imprecise BOM ?

Just add a column called precise , if the assembly is precise you will get ‘y’ in the column

Which BOM is most useful and why ?

It all depends on client and situation:

For eg : ( Just guess which BOM structure can be used )

1. In case of released item where do you want to freeze the changes in BOM structure.

2. While the assembly undergoes modification continuously and not yet released.

3. The Assembly is need to be reviewed for latest working and released

4. Need to know only released item in the BOM structure.

So it all depends on situations, You can also easily toggle between Precise/Imprecise BOM from Edit menu in Teamcenter.

Thanks for your patience in reading.

Folks,

Am back from holidays, sorry for the delayed post for thirsty hearts……

Today i will explain some basic concept about Metadata and physical data

Metadata :

This normally represents a record which can be from basic Excel sheet or from a big database .

In case of Teamcenter, When we check a named reference of any dataset you can see the metadata associated with it. Which normally represents the location of the physical file pointing to volume.

Where metadata is stored for a dataset?

Metadata is in the form of record which will be stored in Teamcenter database associated with any dataset.

Physical data :

The physical data represents the data which is having a valid size, this can be any .prt,.xls,.doc,.txt etc….. Which is physical form of file having valid size associated with it.

In Teamcenter point of view, if you try to import/export any data through named reference it represents the physical data.

Where physical data is stored in Teamcenter ?

It is normally stored in volumes, based on the assigned volume for the user it will take the corresponding volume … But main thing is you will not be able to recognize the data inside the volume,  since the name is encrypted. which can be understandable only to Teamcenter.

Folks,

Sorry am in holidays where i dont have enough access to internet. so the blog will be more effective starting from Jan 17th … see you soon.

Active workspace

High Rated Topics

Count on me :)

Explore My Past postings

RSS Siemens Newsletter