Cancel
Showing results for 
Search instead for 
Did you mean: 

Teamcenter Upgrade from 8.3 to 11.2 effort estimating

Experimenter
Experimenter

We are contemplating upgrading Teamcenter from 8.3 to 11.2 and have had a couple of effort estimates provided.  We are running a single TC instance using iPEM and store and forward (3 servers) as well as translation.  Desire is to move to new hardware as well (AIX,Oracle,Tomcat).  We do not have any customizations of our Teamcenter system - configurations only.

 

What are we looking at from both a effort and duration perspective just for a application administrator?  Has anyone tried to do this big of a jump or can help me understand how their 8.3 to 10.1 upgrade went (issues and/or timeline)?

 

Thanks.

 

 

 

1 REPLY

Re: Teamcenter Upgrade from 8.3 to 11.2 effort estimating

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

Our Tc8,3 to Tc10.1 upgrade went smoothly even though the data model changed drastically including the renaming of workflow handlers.

 

Our biggest challenge was standing up a test system that matched the infrastructure of production. This is a very important point as you will need to upgrade the remote FSC's (store and forward) before upgrading the application and web servers. You will need at least one remote FSC for your test environment to prove our this process before running it on production.

 

Next was cloning production with existing software on new hardware (and OS's). Some things needed to be changed (reverted .NET to J2EE) then changed back after the upgrade was completed (J2EE back to .NET). We also uninstalled Dispatcher before the upgrade and reinstalled after.

 

Client installations have changed a little bit and you'll need to consider how to pass the infodba (or installing user) password during the silent install. You'll need a few workstations to run through the install/uninstall/install iterations needed to have clean scripts. Java is no longer included and will give you plenty to consider (and validate) when updating clients.

 

You will face a larger challenge since the data model from Tc8.3 to Tc11.2 is vastly different and you will have many more considerations about how to handle new or changed features. Most likely you'll need a two-step upgrade, Tc8.3 to Tc10.1 to Tc11.2. Give yourself a couple of months to clone, upgrade, script silent installs, test and document before scheduling the production cutover/rollout. Tc11.2 is worth the effort.


Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2