Held every two years at McCormick Place in Chicago, the International Manufacturing Technology Show (IMTS) is the one of the largest (over 110,000 attendees), most comprehensive (~2,400 exhibitors), and longest (six days) manufacturing shows conferences in the world, certainly North America. This year’s event marked IMTS’s 31st edition. First timers and long timers are overwhelmed by the sheer size of this event. At over 1.3 million square feet, you better dress comfortably and prepare for an overload of manufacturing technology sights and sounds.
Because IMTS is so comprehensive and massive, planning is everything, and as you walk around the various pavilions, you start to get a sense of trends and likely future impact of just about all of the technological aspects of design, engineering, and manufacturing.
Below are the major manufacturing trends that I experienced this week. Starting next week I’ll detail what I considered to be the most significant technologies and products showcased at IMTS this time around. Next week, I’ll also go over the major software developments that were introduced — mostly CAM, but some significant stuff.
Interoperability, collaboration, inspection, quality, standards, proprietary data, neutrality, competition, and innovation – these are words and realities that all manufacturers deal with daily. Over the years there have been myriad attempts to bring this stuff together, all while protecting IP. However, as we know, while the attempts to make this happen have often been valiant, too often they have fallen well short, or worse, failed altogether.
That failure may be on its way to being a thing of the past with the advent of the Quality Information Framework (QIF), an ANSI standard that supports digital thread concepts in engineering applications ranging from product design through manufacturing. Based on the XML standard, it contains a Library of XML Schema ensuring both data integrity and data interoperability in Model Based Enterprise (MBE) implementations. (more…)
For only the fourth time since its inception, earlier this week ANSYS announced a leadership succession plan with a new CEO. James E. Cashman, who has served as ANSYS’ CEO since 2000, will step down as CEO and become Chairman of the Board of Directors effective January 1, 2017. Dr. Ajei S. Gopal, a technology industry veteran who has served as a member of the ANSYS Board since 2011, has been appointed President and CEO effective immediately and will continue to serve on the Board. Dr. Gopal will become CEO on January 1, 2017. Ronald W. Hovsepian, who currently serves as Chairman of the ANSYS Board, will assume the role of Lead Independent Director as part of this transition.
As part of its ongoing acquisition quest, less than a year ago PTC acquired Vuforia from Qualcomm Connected Experiences for $65 million. What a difference a year has made!
Vuforia is an augmented reality (AR) technology platform, that PTC is betting will enrich its technology portfolio and further foster its strategy to provide technologies that blend the digital and physical worlds. In other words, the next phase of the Internet of Things (IoT).
When it was first reported that Qualcomm was soliciting bids for Vuforia as part of its effort to cut costs and focus on its key mobile business, PTC surprisingly was the ultimate suitor for the company and its technology.
Vuforia is a software platform that democratizes AR development. According to PTC, Vuforia is the most widely used AR platform in the world, powering more than 80% of AR apps in the Apple App Store and Google Play. In fact, more than 30,000 Vuforia-powered applications have been published on the App Store and Google Play – and have led to more than 275 million app installs. Vuforia also supports an active developer ecosystem with more than 250,000 registered developers, and more than 30,000 projects in development.
For the past several years we all have heard the non-stop hype from a number of different sources that the Internet of Things (IoT) is the thing that will change everything and improve our lives in ways that are still unimaginable to us. That may be true, but relatively little attention is paid to the converse – what are some of the not so great things that could result from IoT? This darker side of IoT, of course, includes security, but how about data handling, infrastructure, privacy, and the inevitable question of who actually owns the data generated from and for IoT. All of these issues are problems now and will only continue to grow unless and until they are adequately addressed.
This week I’ll cover IoT data handling and data infrastructure, both critical if the IoT is to proliferate as many vendors hope and hype. (more…)
For the past few years we all have heard a non-stop proclamation from a number of different sources that the Internet of Things (IoT) is the thing that will change everything and improve our lives in ways that are still unimaginable to us. That may be true, but relatively little attention is paid to the other side of the coin – what are some of the not so great things that could result from IoT? This darker side of IoT, of course, includes security, but how about data handling, infrastructure, privacy, and the inevitability of IoT companies going out of business. All of these issues are problems now and will only continue to escalate unless and until adequately addressed.
Believe me, I’m not alone with these concerns.
This time around I’ll cover IoT privacy and company survival. Next week I’ll cover IoT data handling and infrastructure. (more…)
Almost all of today’s CAD products are pretty capable right out of the box, but I’ve often wanted them to do more to suit my particular needs and workflow. Over the years I’ve created macros and used Visual Basic and AutoLISP for defining, customizing, and automating functions and processes not found in CAD products out of the box. My results varied widely – some were good, some were OK, and some were downright unpredictable and bad.
Several years passed and I didn’t really do too much with CAD programming, so my interest waned. That all changed, though, when cloud-based Onshape’s FeatureScript came along earlier this summer.
FeatureScript is a programming language designed by Onshape for building and working with 3D parametric models. The language is built into Onshape and provides the foundation of Part Studio modeling, including geometric references, parametric tools, and a type system with types built for math in three dimensions.
The standard feature types in Onshape, such as Extrude, Fillet, and Helix are already written as FeatureScript functions. Using FeatureScript, custom feature types extend this same function mechanism to Onshape.
Is FeatureScript the first specific programming language to be released for a CAD product? No, not exactly, but it is unique in many ways and adds to Onshape’s positive differentiation in the crowded CAD marketplace.
All 3D printers need host software to function. That’s a given. Host software sends the commands to a 3D printer that tells the printer how to build an object. Most host software communicates with the printer via a wired USB connection. For almost all 3D printers, a computer running the host software must stay tethered to the 3D printer at all times while it is running. Obviously, this is not always a great situation, hence the advantage of being wireless.
There are basically two ways to perform wireless 3D printing. First, a G-code file can be saved onto an SD card using a computer, then the SD card can be transferred to the 3D printer where the print job is initiated via a controller into a 3D printer.
This arrangement allows wireless 3D printing, but it lacks most the advantages of a truly wireless setup. The 3D printer can still be placed away from a work area, but beyond that, using the SD card transfer method is really no different than transferring data over a cable. The second way to do (truly) wireless 3D printing is by running the host software on a small embedded device, like the Raspberry Pi, that is connected to the 3D printer.
Which Is Better, OctoPrint or AstroPrint?
This is analogous to using a dedicated computer for 3D printing that stays connected to the printer at all times. But, instead of using a computer for this purpose, the host software can be run on something, such as a Raspberry Pi, which is just powerful enough to run the software.
The two most popular host software packages developed for wireless 3D printing are OctoPrint and AstroPrint. AstroPrint is, in fact, based on OctoPrint, and claims to have an optimized codebase for running on embedded computers. The AstroPrint team has made changes and additions to the software, making the two host software offerings quite a bit different in many ways.
While OctoPrint and AstroPrint do share some similarities, they are also different, primarily with regard to their intended users.
A couple of days ago, the internet of things (IoT) world was rocked with the announcement that the UK’s semiconductor and software design giant, ARM, was being purchased by Japan’s SoftBank in a cash deal for some $32 billion.
In the official acquisition statement, SoftBank says it intends to:
With all the fanfare that took place a couple years ago with the launch of cloud-based Onshape, we thought we’d weigh in with partner Geometric’s announcement of its STL Workshop.
Onshape is by no means the first cloud-based/mobile CAD application. It was and still is, however, a unique true cloud-based technology and not a desktop/cloud hybrid.
Onshape began with what was one of the best and worst kept secrets in the engineering software arena. Worst, because even early on, it was evident that the technology would be cloud based, even if virtually no details were disclosed. Best, because virtually no details were disclosed, and that just added to the anticipation for the official launch of Onshape.
One of the inherent advantages that Onshape has always had is the fact that it was created from scratch by a team used to creating things from scratch with no legacy baggage to overcome and work around. Of course, the development team has not done everything themselves, because Onshape includes software components from Siemens PLM (Parasolid; ironically the same modeling kernel used by SolidWorks) and D-Cubed. This component licensing has let the Onshape team focus its efforts on what it does best.