The model based enterprise’s effect on your innovation
Industry has done a good job of solving problems in the past, and they’re doing a good job of solving problems today. But few companies in industry are thinking about how to solve what might be called “the next big problem.” The methods companies use to discover innovative ideas required to arrive at a solution for the next big problem will make or break how that idea performs in the market.
Thomas Edison created the first successful incandescent light bulb. For this to happen, it took numerous people seven decades of continuous work to get to the point of having a useful innovation. Historians claim up to 22 people worked on the design and function of the light bulb, and they didn’t have the benefit of shared engineering data or testing results.
We know that Edison delivered on the light bulb, but the light bulb was not initially a broadly adopted product. Without the infrastructure and shared knowledge that allowed for the distribution of electricity, the light bulb itself couldn’t compete with candles and lanterns. Edison had to make his invention one that anyone could access so it could become something that would transform the market. Players in that market needed access to the knowledge that would bring electricity to the light bulb and an unimaginable range of other new products.
Innovations that solve the next big problem take seed in existing knowledge, but then often cross over to other domains. Being able to understand the design and intent of existing technology allows it to be used in a broad range of applications. There must be easily accessible information available for engineers and scientists to learn from.
Accessing the knowledge that defines complex technology is the key to creating innovations that will solve the next big problem. Consider the knowledge companies have regarding their products today. There are huge data stores that describe how to solve problems. Before JT existed, that data was typically in a form that was difficult to access or view. Now, 3D JT data has solved that problem by democratizing engineering data.
Today, we’re on the cusp of another Industrial Revolution. Model based designs using JT data and a model based enterprise will fuel it the way light and electricity did in Edison’s day.
The model based enterprise’s role in innovation
The ability to visualize 3D JT data freely in an enterprise was the “light bulb” moment for model based engineering. With the adoption by industry of model based engineering, and the broad use of JT, a new range of solutions for common use cases became available. Industry has been using JT data to change their business processes for more than two decades.
JT is referred to as a “process format” by many adopters as its impact now goes well beyond visualization. Companies have used JT to completely change the ways they use data for design work. Design reviews with JT eliminated costly rework time and improved time-to-market. But that was just the beginning.
Today, JT data supports supplier collaboration, CAE results sharing, logistics and planning, digital manufacturing, packaging, shop floor mobility, paperless drawings and virtual reality, to name a few.
These are great innovations, but these innovations are no longer enough to guarantee success in the market or give companies a competitive edge. The model based enterprise is changing the way companies answer their own “What’s next?” question.
A model based enterprise realized through JT data will enable ideas that transform the market. Industry must decide what’s next with JT. This will be the basis of what we discuss throughout this series.
This concludes part one in our series on model based enterprises and how the model based definition is the basis for how companies can answer their own “What’s next?” question. In part two, we examine how model based enterprises are the next step in the JT effort and how Siemens PLM’s proposals on the JT effort from a decade ago are now in place.
About the author
Mike Zink is a Senior Product Manager and Openness Evangelist working in the Corporate Technology Office of Siemens PLM Software. He has more than 36 years of experience with software product development, project management and manufacturing support. Mike currently has product management responsibility for the Siemens PLM JT Toolkit, PLM XML Software Development Kit and JT2Go, the 3D data viewing tool for JT. He is also the Siemens PLM Software openness evangelist and encourages openness in industry through programs such as the Code of PLM Openness and ISO standardization of JT. Mike has a Master’s degree in software development and management and a Bachelor of Science degree in computer science from the Rochester Institute of Technology.