The Prior Naming Convention
Major releases: 10.1, 11.2. (Note that 10.0, 11.0 and 11.1 were not publicly released.)
Of course, there have been Service Packs for these as well.
Service Packs: 11.2.1, 11.2.2, 11.2.3.
Then for each of those there were patches.
Patches: 184.108.40.206, 220.127.116.11, 18.104.22.168
Service Packs Become Minor Releases
Minor releases: 11.3, 11.4, 11.5
However, patches continue to be the fourth digit. So, now we have a version naming convention that appears to be X.Y.0.Z. Yes, that's a zero in the third position. (I hope they resolve this with the release of Teamcenter 12, next year.)
Upgrades and Patches
Where this all comes into play (and potentially confusing) is when a site intends to go from Tc 11.2.x.x to Tc 11.3.x.x. 11.2 is a major release, so do we "upgrade" to 11.3? Well, no, because 11.3 is not a major release, it's a minor release. For me the key is to think of Minor Releases like Service Packs, which are installed as a patch.
For example, to go from Tc 22.214.171.124 to Tc 126.96.36.199, take a look at the Tc11.3.0_patch_1_README.pdf:
Hopefully this article has helped clear up any confusion caused by Siemens' change in the Teamcenter version naming convention. However, for a more thorough explanation (and another perspective on this subject), see Teamcenter 11.3 introduces new version convention and Installing, upgrading, and patching Teamcenter in the Siemens online Teamcenter documentation (a webkey is required).
Thanks for reading.
Patrick (aka Pat) Kennedy has a passion for systems that help engineers get stuff done, and has been implementing CAD, PDM and PLM systems since 1995. He loves his wife, kids and church, and enjoys clear skies in the Pacific Northwest (maybe because they’re so rare).