{"id":1704,"date":"2009-06-15T08:55:26","date_gmt":"2009-06-15T15:55:26","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Siemens-PLM-Corporate-Blog\/Enter-The-Scorpion\/ba-p\/333983"},"modified":"2026-03-26T11:11:25","modified_gmt":"2026-03-26T15:11:25","slug":"enter-the-scorpion","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/news\/enter-the-scorpion\/","title":{"rendered":"Enter The Scorpion"},"content":{"rendered":"<p><P>&nbsp;<BR \/><BR \/><A href=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/wordpress\/images\/2009\/06\/ScorpionFEA_thumb.jpg\" rel=\"nofollow noopener noreferrer\"><IMG class=\"alignnone size-full wp-image-2087\" src=\"http:\/\/community.plm.automation.siemens.com\/legacyfs\/online\/wordpress\/images\/2009\/06\/ScorpionFEA_thumb.jpg\" alt=\"ScorpionFEA_thumb\" width=\"229\" height=\"191\" \/><\/A><BR \/><BR \/>A lot of companies use code words for projects or upcoming products. Even if it\u2019s not a secret you have to have something to call it and picking a name that is related to product may cause problems later. For example, I\u2019ve seen more than one project where development has one name, marketing comes up with something later and the comments in the code get all messed up.<BR \/><BR \/>So, what you want to do is pick a name that is unrelated to the product. Scorpion was the code name for the upcoming <A title=\"Solid Edge Simulation \" href=\"http:\/\/www.plm.automation.siemens.com\/en_us\/products\/velocity\/solidedge\/overview\/add_on_apps\/simulation.shtml\" rel=\"nofollow noopener noreferrer\">Solid Edge Simulation <\/A>product that\u2019s going to be delivered with ST2. It brings FEA analysis to the Solid Edge designer and creates a framework for more to come.<BR \/><BR \/>Sometimes these product names can be fun. I had no shortage of cool scorpion images for power point slides. In one of our buildings in <A title=\"Pune, India,\" href=\"http:\/\/maps.google.com\/maps?rlz=1C1GGLS_enUS291US303&amp;\" rel=\"nofollow noopener noreferrer\">Pune, India,<\/A> the offices are named after zodiac signs. I\u2019d usually grab the Scorpio one for any meetings (we should have made it a War Room). One developer caught me at the coffee pot one day and asked, \u201cSo, are you going to sting the competition?\u201d We had a lot of bad jokes like that too.<BR \/><BR \/>Now I don\u2019t think the high end analysis products are particularly worried about Solid Edge Simulation. All we are doing in offering some mid range FEA tools for static analysis, modal and buckling with parts, sheet metal and assemblies. It is much more than \u201cFemap Express\u201d but if you are doing high end analysis you are better off with Femap and NX Nastran.<BR \/><BR \/>Where our sting will be is with ease of use and the level of integration. UI in CAD and FEA is a very hard thing to do (just check out all the blogs on it!) It\u2019s made harder for engineers and CAD designers who may only do a little CAE each day or week or month. If you are a user of mid-range FEA or want to start using it in your Solid Edge environment, you really should take a look at what we have done.<BR \/><BR \/>Oh, and one last point\u2026 this bug has legs (yes, I know, another bad joke). We are already thinking about what to add next.<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp;          A lot of companies use code words for projects or upcoming products. Even if it\u2019s not a secret you have to have something to call it and picking a name that is related to product may &#8230;<\/p>\n","protected":false},"author":54987,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-1704","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts\/1704","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/users\/54987"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/comments?post=1704"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts\/1704\/revisions"}],"predecessor-version":[{"id":1705,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts\/1704\/revisions\/1705"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/media?parent=1704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/categories?post=1704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/tags?post=1704"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/industry?post=1704"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/product?post=1704"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/coauthors?post=1704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}