![\"WindowsLiveWriterOpen_BA10image_2\"](\"http:\/\/siemens.pmhclients.com\/images\/uploads\/WindowsLiveWriterOpen_BA10image_2.png\")
I\u2019ve seen a lot of conversation lately in regards to openness in the CAD\/PLM industry. So it seems timely to share some of the discussion and reiterate how important open standards are to us as a company and the PLM industry.
First some of the recent conversations along this thread:
- Evan Yares recently blogged in An Open Data Manifesto<\/A>:
\u201cthere are few companies (or rather, company leaders) that really recognize the importance of a commitment to open data (and, more generally, open interoperability) as a foundation to a trust relationship with their customers.\u201d
Some of you may remember Evan\u2019s humor two-and-a-half years ago in suggesting a Proprietary 3D for All<\/A> t-shirt.<\/LI>
\t- Rob Jamieson noted in his A new common CAD standard<\/A> blog post on Develop3D: \u201cI\u2019d hate to think the only way we will reach a common standard is through multiple acquisitions and the creation of one master CAD company.\u201d<\/LI>
\t- Randall Newton wrote in the latest issue of VEKTORRUM<\/A>:
\u201cJT has become quite popular in automotive as a common data format for visualization and related data sharing. This is partially because Siemens PLM\u2019s Teamcenter application for product data management is far and away the best selling PLM data application in automotive.\u201d
Randall went on to comment:
\u201cSpatial\u2019s explanation for dropping JT support rings hollow\u2026 Choosing to drop support for a popular visualization standard is contrary to the stated goal.\u201d<\/LI>
\t- Ralph Grabowski recently blogged Spatial explains why no JT in InterOp Release 21<\/A>. He passed the ball to us for comment. See his subsequent post Siemens PLM responds to Spatial\u2019s complaint on JT<\/A>, and check out his blog from today JT import\/export not a problem: Okino does it<\/A>.<\/LI>
\t- Back in March, Deelip Menezes sparked some conversation on his blog regarding Dassault\u2019s lightweight data format<\/A> where Al Dean shares his thoughts on the format and openness. Al noted: \u201cWhile each vendor claims to be opening up their formats, fact of the matter is that these initiatives are there for one reason and one reason alone \u2013 to assist them sell more software.\u201d<\/LI>
<\/UL>
We are definitely in the business of selling software. But we believe that the best way to do that is to meet our customers\u2019 needs. Open standards are demanded by our customers. So openness is not just a philosophy I\u2019ve heard Tony Affuso talk about nearly every time he speaks to our customers. We have to deliver on it \u2013 otherwise JT and Teamcenter would not be as widely used as they are today.
We commit and deliver openness in five ways<\/A>: open business model, open data model, open architecture, open applications, open communities for innovation. That\u2019s why we published the JT data format<\/A> over four years ago and we continue to publish the JT specification so it is openly available. Last year the ISO gave it Publically Available Specification<\/A> status. Next month, we will release the 9.5 revision of the specification.
Ralph notes in the Okino blog post that the company licensed our JT Open toolkit. It\u2019s available to any company \u2013 including our competitors. See the JT Open<\/A> member companies<\/A> and vendors<\/A> we\u2019re able to list on our website. They are the folks driving the ISO work. It\u2019s not our community, it\u2019s theirs. We just get to be part of it.
So let\u2019s continue the \u201copen\u201d conversation. Please leave us a comment, question or complaint and we\u2019ll address them here in the open.<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"I\u2019ve seen a lot of conversation lately in regards to openness in the CAD\/PLM industry. So it seems timely to share some of the discussion and reiterate how important open standards are to us as a com…<\/p>\n","protected":false},"author":61893,"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-796","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts\/796","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\/61893"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/comments?post=796"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts\/796\/revisions"}],"predecessor-version":[{"id":797,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/posts\/796\/revisions\/797"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/media?parent=796"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/categories?post=796"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/tags?post=796"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/industry?post=796"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/product?post=796"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/news\/wp-json\/wp\/v2\/coauthors?post=796"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Rob Jamieson noted in his A new common CAD standard<\/A> blog post on Develop3D: \u201cI\u2019d hate to think the only way we will reach a common standard is through multiple acquisitions and the creation of one master CAD company.\u201d<\/LI>
\t