Altair expands its reach with easy to license third party software

24 April 2012: Intrigued by the recent spate of third party announcements by Altair Engineering, I sought out someone in the company to find the reason for their seemingly rapid expansion. Last week I spoke with Antoine Poussier, VP of Global Partner Relations, who was able to enlighten me.

First, a little about Altair, a company many of you may know very little about. At least I knew little about the company or their products. I knew they had some well-respected analysis software; it turns out that they have much more. Think about $213 million USD in revenue, 1500 employees, seven major business lines, over 40 offices across 16 countries, and over 4000 customers in a wide variety of industries.

Known primarily for its HyperWorks simulation software, other business lines include cloud computing software, product design, business intelligence software, industrial design and styling software, and a venture focused on next generation solid state lighting.

The HyperWorks Partner Alliance provides a foundation for an open CAE licensing structure, which enables customers to easily try-out new software with minimal additional cost. Their strategy offers a unique contrast to the licensing strategy of most software vendors in the CAD/CAM/PLM marketplace today. Rather than offering software with a substantial initial cost and a lower ongoing annual maintenance cost, Altair Engineering instead allows on-demand access to their software as well as those of third party vendors using an on-the-fly licensing scheme using HyperWorks units (HWU’s). HWU’s act like tokens. Customers buy a certain number of HWU tokens to use on a monthly basis. A user, running each software removes tokens from the token pool; quitting the software returns these tokens to the pool. For instance, HyperMesh, Altair’s own meshing product, uses 21 tokens. Users can download any number of products from a server that they might need to use, then merely activate them by using the correct number of HWU’s. Although I tried repeatedly to find out, Poussier refused to reveal how much the HWU’s cost or how many might be used per application. Users will need to contact Altair directly for this information.

The impact is to eliminate the cost of acquiring new or infrequently used software. Also, no additional licenses need to be procured or managed, reducing the burden on IT and purchasing. It also makes it much easier to try out different software or perhaps use very specific software for a limited time. Visit www.hyperworksalliance.com/PartnersList.aspx to find out what third party applications are available. These are in addition to the many Altair products.

In summary: Altair Engineering’s HyperWorks Partner Alliance makes it easy for potential partners to sign up and makes it easy for users to explore alternative simulation solutions.

Disclosure: None required. No compensation of any sort was provided for this article.

Additional info about the company is available at www.altair.com.

—–

Siemens PLM Software’s Active Workspace mines product data

18 April 2012: For a long time I have been less than an enthusiastic advocate of PLM based systems as a vehicle for managing development processes. Sure, the storage of data is an important way of gathering product development data. Yet, viewing and using the associated data was always difficult. I found that, coming from a CAD background, which provides glorious views of 3D products, scrolling through page after page of data tables quickly becomes mind-numbingly tedious. Often one needs to view different datasets in different ways to attain a glimmer of data needed for decision-making.

Siemens announcement recently of Active Workspace (AWS) for their HD-PLM environment is their latest, and best attempt to present data graphically to the user, making the system perform the work of visually integrating the vast amount of integrated product data.

Last Fall, while attending a Siemens analyst conference, the company rolled out some preliminary information about Active Workspace. I was excited then about the long-term possibilities of revising the ways users can extract and make use of vast amounts of data. This announcement provides a very useful beginning for this project.

Exactly what is HD PLM? It’s not a product, but an architectural framework. HD-PLM, announced two years ago, provides a technology foundation enabling Siemens product development team to produce a common set of integrated software tools that will identify, capture and collate the massive amount of information available in manufacturing enterprises, and apply meaning to that data using an intuitive visual environment.

Two weeks ago, on 3 April 2012 Siemens announced Active Workspace Version 1, the first product to achieve the beginning of that vision. Grindstaff noted that “Active Workspace creates an intuitive and personalized 3D graphic interface that significantly enhances the ability of our PLM suite of offerings to deliver knowledge instantly to the right people, at the right place and in the right context to support rapid and intelligent decision making.”

To find out more I sought out some details from Siemens and had a conference call with two product managers for AWS: Bill Lewis and John Whetstone. They described AWS as having the following capabilities:

  • Find information fast
  • Visualize and navigate
  • Compare and report
  • Collaborate
  • Configure and share control

Lewis described AWS as a tool to help the vision of semantic data understanding enabling users to make smarter decisions using HD PLM. Indeed products are getting more and more complex. HD PLM is looking to solve this. He sees this as a tool for all PLM users; not just professional users, but casual users as well.

The slide below shows the products supported by AWS.

Products supported by Active Workspace V1

An example of AWS in action

Whetstone performed a live demo for a sample company. We start by searching for all objects in the database for the company. The search yields the following 130581 results:

Searching for all objects

Data was taken from Teamcenter and indexed to achieve the speedy result, which took only a few seconds. Note the object filter types at the top of the screen.

Selecting the type – Physical Design Model Elements – resulted in this:

Revealing Physical Design Model Objects

These are the physical mechanical model elements of the company, each designated with a different part number.

Shown below are the types of objects from which we can choose as a high level selection. This data is already in the Teamcenter data which we extract. The data extraction methods and rates are user determined.

The types of object filters offer ready access

Drilling down to the hard drive we get only 61 objects:

View of model elements in one sub-assembly

This is the tile view, showing access to other data associated with each object, such as: revision, owning user, type, and other data. Along the right side are icons that can launch applications, such as shape search and visual navigator, where used, and more info.

Visualizing the top level hard drive and using the JT object formats, here is the result:

Visual navigator display for the hard drive sub-assembly

Note the pan, zoom, and rotate options at the top of the image above. Drilling down to the drive heads shows this:

Displaying a sub-assembly within the hard drive

The “more info” icon reveals attached documents such as FEA results.

Revealing additional information associated with the drive heads

AWS requires the user to have a license of Teamcenter (TC). It is a companion product to TC.

My impression:

This is a big deal for Siemens and their users. It basically allows data mining of related, or as Siemens refers to it – the semantics of the data. Semantics, or the problem of understanding, allows one to make sense of the miasma of data relations associated to products. What is the product, what functions does it do, where does it fit, what were the specifications and were they met, what tests were performed, and so on. This data is stored within Teamcenter. Making sense of the data stored in different databases is difficult.

AWS seems aimed at the largest users. Early adopters include GM, Ford, JPL, and Rolls Royce.

While I was turned on by the AWS capability, this release seems to have an awkward and incomplete UI. Also, the reporting and rollup capabilities need to be extended. For instance, cost rollups and product status do not seem to be available yet, but are on the drawing board. Searches are limited to single attributes.

AWS V1 is available now. Maintenance releases are scheduled for July 2012 and Nov 2012. While the next major release is not due until the end of 2013, there is plenty in this release to keep users busy.

Pricing seems modest. $750 per named user. But, for large installations this could add up quickly. I expect there are volume discounts.

As far as competition, only Dassault Systemes with their V6 Enovia 3D Live offering is even in the same ballpark.

More info can be found at www.siemens.com/plm.

Kenesto: What is it?

18 Dec 2011:  Just a few weeks ago Mike Payne, one of the founders of PTC, SolidWorks, and SpaceClaim, noted on his LinkedIn page that he was un-retired. I found this exciting enough to reach out to Mike to find out about his new company. As a result Mike Payne, Kenesto CEO since March of this year, hosted me earlier this week at their offices in Waltham, MA. He and some of his staff filled me in about the product and where it’s heading.

Basically, the product is the antithesis of Payne’s formerly complex products in the CAD arena. Aimed at the category called business process automation, this cloud-based application allows asynchronous spawning of processes. Different from similar systems that try to model processes, Kenesto builds processes on the fly. Users wanting to track a process they are initiating, for instance an ECO, initiate a process, attach documents to it, and add users to the next process by adding their email addresses. Different types of “next processes” can be defined, such as “review and approve.” At each step in the process the recipient can add additional processes that add steps to the overall process. Kenesto builds the process diagram as steps are added. Note that this differs significantly from the BPM (Business Process Modeling) approach that models processes using a cumbersome programmatic approach. Kenesto calls it Business Process Automation (BPA).

We spent a fair amount of time discussing security and about control of attached documents. Jerry Meyer, Kenesto’s chief product officer, explained that most documents  (CAD images, docs, pdf’s or other related files) could be made view only, limiting the need for most security. In addition, Meyer and Payne both emphasized that ideally Kenesto would point back to the primary data vault, which provides primary security for collaborative data sharing. Users would most likely, if needed, upload to Kenesto more concise files, such as JT.

Each user of the process can examine all of the process steps, and see who did what and the entire process status. Processes can complete, but are left in the system for inspection and review. This brings up many possibilities of additional value. Different than is done in most cases today, each Kenesto process contains value in that the steps are recorded as to who did what, when it was done, and the reasons for certain decisions. Imagine, as might be the case for an FEA analysis of a product during the design cycle, if you could record the various simulation alternatives and capture the alternative finally selected and the reasoning behind it. IMHO, this might be easier than the complex simulation capture and record systems being proposed by many CAE systems such as Simulia and Siemens’ PLM Software.

Product status: Kenesto is approaching their first Beta and will use this to refine their product and its UI. Right now the user interface appears to be very simple. Being cloud based, and storing little or no CAD data, implementation involves signing up for the product and picking some areas to begin using the system. Ideal areas would be those that require tracking of the process status.

Pricing is not yet available. Payne described that the company is searching for a pricing schema that encourages the use of the system rather than the alternative. Kenesto is building up its staff. Currently the company is small, with development in Israel.

I like the approach. Clearly the system is evolving rapidly. Not too different than Autodesk’s 360 Nexus approach, the idea of fitting in to the way organizations work rather than forcing each company into using “best practices” should simplify implementations. Most importantly, Kenesto enables tracking the flow of information across organizational boundaries and can insure that critical design and review steps are not lost in the day-to-day miasma of paperwork and deadlines.

You can find put a bit more at www.kenesto.com and download a paper describing generally describing the product.

——

Autodesk 360 and Nexus – PLM 1.0: not perfect – but a great start

3 Dec 2011: Errata. I was incorrect in stating that Buzzsaw was a local PDM vault for AEC/BIM. Several people have written me about this, one being Stephen Bodnar of Autodesk. Bodnar stated that “Vault is the on-premise DM solution for both industries, whereas Buzzsaw is cloud-based and is also built on Autodesk’s Cloud, and is intended for design file collaboration between partners/suppliers and other users and does, in fact, have bi-directional push/synchronization with Vault)”

1 Dec 2011: I am on my way back from Las Vegas, where AU 2011 was held. The highlight of the event, at least for me, was the announcement of what I am calling Autodesk PLM 1.0. The announcement was not a well-kept secret, but the content of the announcement was closely held.

Monday’s media day preceded the conference. The actual PLM announcement came late Tuesday morning. Carl Bass retracted his oft quoted remark about PLM not being something customers worried about; instead, it was revised to mean “until the technology was right.” I couldn’t agree more with his reasoning. Most of Autodesk’s competitors PLM systems offer expensive, difficult to use, and almost impossible to install PLM systems, that rarely have met expectations. Even then, it is often at the cost of massive consulting assistance, rarely meeting anticipated timeframes, AND generally involves the implementation of substantially revised business processes.

Different than my analyst peers I have always been skeptical of such large and costly projects. Not being on the implementation side, I could afford to be skeptical. Many such projects, aside from basic PDM, seldom actually get implemented. Most stall. Autodesk estimates that most deliver only PDM. To test this thesis, I tweeted my followers and asked what they had accomplished. With just a few responses, this is hardly scientific. Several stated that did not yet have even PDM fully implemented!

So what was actually announced? The system is being called Autodesk 360. It is based on having locally installed PDM. For mechanical and for AEC this is Vault. Buzzsaw, a cloud based application provides design file collaboration for AEC teams. The third, and new software piece is called Nexus. The dictionary describes the word nexus as a “connector.,” and is a good description of what the software aims to do. In the following discussion I concentrate solely on mechanical PLM. For information on Buzzsaw and how it uses Nexus readers will have to go elsewhere. Try here.

Nexus is cloud based, and comes with 140 or apps. Each app looks like a series of specialized templates, along with customizable (by the user) workflow logic. Delivery is expected by the end of March 2012. No pricing was announced, however, the implications were that it would be modest. It will be sold on a per user subscription basis. All Nexus data and apps will be run in the cloud, using an ordinary browser. The mass of data will remain locally hosted using Vault. Having and maintaining Vault locally solves the issue of loading very large cloud based data while still maintaing some degree of interactivity.

How will it interface with Vault and other PDM systems? Very well with Vault. No connectors were announced to integrate with other PDM systems. Autodesk hinted that this is a good opportunity for third party developers and VARs. Connections with Nexus could be implemented via as yet unannounced APIs.

Today, the connection between Vault and Nexus is one way. CAD data cannot be sent from Nexus to Vault. Nor is it synchronized among Vaults, as is done among Apple’s iCloud apps. However, Vault data is automatically synced up to Nexus. Expect bi-directional sync in the future.

Is it easy to install and operate?

Keep in mind that my total exposure to Autodesk 360 Nexus comes from a 30 minute, main stage presentation, followed by a 60 minute working session where about 20 people per workstation watched a very capable Autodesk developer demo and responded to questions, often by showing us how Nexus would solve the proposed question.

Nexus appears to be an out of the box system. Nexus comes with predefined templates and workflows. Yet they can easily be added to and/or modified. Fields within templates (apps) can be defined on the fly and their characteristics (such as numeric, values, dates, etc.) as well. A Visio like graphic interface defines workflows. Many are offered in the starter system. A typical administration system allows assigning users to tasks and roles. Somehow, data fields can be interconnected, allowing visibility to see what drives or is driven by what.

So. There you have it. I imagine Autodesk will soon, if not already, have many seminars and pre-recorded AVI’s showing the software. Try here: http://usa.autodesk.com/360-lifecycle-management-software/

My conclusions

I think the product is outstanding. Being cloud based resolves many operating issues. Some users might question the security aspects of hosting much of the data remotely, and would do well to satisfy themselves that either this is not an issue, or otherwise. I think, that perhaps except for very special circumstances, the cloud-based security might even be vastly superior to what they could do locally. I think this is a non-issue.

Cost wise, I think this will prove to be much less expensive, long term, than most of today’s solutions. Again, this is a non-issue. Just take a look at the slide Stephen Bodnar of Autodesk, VP of Data Management, presented below that compares some costs for a 200 user deployment.

For collaboration, data can be uploaded, either in summary format, or detailed CAD files. Nexus has controls over what user sees what data.

Included are project management capabilities that allow rolling up from completed sub-tasks automatically. Defining projects involves defining sub-projects with easily configurable tasks and reporting procedures. If you have already implemented workflow as part of Vault, then is should be redone using Nexus. It allows more flexibility and better visibility.

If you want visibility by projects, by project managers and contributors, with flexibility to change workflows and processes to meet how you do business, it’s all there. My only question is how soon can I get it?

Ray with his skeptical face during AU2011 —-

—-

Here are a few slides from the presentation to give you an idea of what Autodesk presented. Sorry for the quality – I used my phone.

The overall concept of Autodesk 360.

Stephen Bodnar discussing their view of PLM:

Why is it called 360? Showing how the Vault and Buzzsaw make up local PDM systems:

Brenda Discher discussing why users don’t like competitive PDM systems.

What Autodesk is doing about it with Nexus.

Siemens NX CAE Symposium: Users show their love

27 Nov 2011: The week before last I attended an invitation only event in Charlotte, NC, as a guest of Siemens at their first NX CAE Symposium. Designed as a way for users to get together to exchange ideas about how they use NX CAE software, some 80 customers attended the symposium, held at the Joe Gibbs Racing Facility just outside Charlotte.

The overall consensus of the presenters and the attendees I spoke with was satisfaction with the NX CAE suite. Many complimented the breadth of the CAE software, some of which I summarize below. Overall users were most satisfied because of the inherent associativity of CAE models with design models.

Several users told stories about how, in the past, they were asked by the design team to evaluate designs and get back to them. Even with an integrated system, the CAE analysts often spend substantial amounts of time simplifying models, insuring that the mesh is adequate for an accurate design, performing a series of analyses, and making recommendations to the design team, only to find that the design team has moved way beyond the design they were working on. Thus their work had to be scrapped. NX’s CAE and design integrations allow analysts to work on the design model, thus having a better ability to stay synchronized with the design team.

Also, NX seems to play well with external solvers, often integrating them tightly into the design stream workflow. Among these were Ansys solvers as well as specialized fluids solvers, such as those from MAYA.

My reactions:
Siemens PLM Software has a well-focused and wide breadth of solutions for heavy-duty CAE experts. Jon Heidorn, Siemens PLM Software (SPLMS) Vice President welcomed the attendees, stressing that simulation is one of their fastest growing markets, encompassing integrated modeling and solutions, system level modeling, multi-discipline simulation and optimization, and the intensely complex simulation data and process management. Beyond 2010 Heidorn predicted software would be available that would perform topology optimization. SPLMS also announced that their partnership with Joe Gibbs Racing was extended to 2016.

Mark Bringle and Nelson Cosgrove of Joe Gibbs Racing discussed their facility and their focus on engineering. Building their cars from scratch, and their engines almost from scratch, but carefully following NASCAR rules for each car, provides an impetus to carefully hone each major subsystem for optimal performance. Fascinatingly, their design cycle during racing season is one week! The three main groups include chassis and vehicle dynamics, aerodynamics, and powertrain. The latest version of NX allows for full chassis FEA modeling. With NASCAR demanding similar car frames and engine performance, their engineers carefully analyze every part to improve weight and aero performance so they can achieve even small advantages over their competition.

Jim Rusk of Siemens PLM Software discussed the latest trends in product development with NX CAE Simulation. He highlighted a few concepts they are working on sand delivering to make it easier than ever. Among these are Synchronous Technology for the CA analyst which makes for easier simplification, workflows for the advanced analyst, continuing improvements in multi-discipline analysis, motion analysis for flexible bodies like springs, multi-solver support, topology optimizations, and HD3D requirements management and validation.

ATK Aerospace, MDA of Canada, and JPL, Proctor and Gamble, and Solar Technologies spoke about their analyses ranging from rocket design to cryo engineering of spacecraft to making 1 million paper diapers to designing complex solar collectors.

Hendrick Motorsports’, Charles Macdonald, discussed detailed part analysis and the tradeoffs they make for lighter, yet strong and most of all highly serviceable parts of a suspension.

Kendra Short, of JPL and the mechanical manager of the Mars Science Laboratory (MSL), successfully launched just two days ago, spoke eloquently about how having a sophisticated analysis system working directly on the design model enable them to perform many more complex analyses than would have been possible without simulation done directly on the design models. Without the ability to service the MSL (it’s a long trip to Mars), Ms. Short chatted about the enormous planning that goes into having multiple alternatives in the event of a failure. I found fascinating during a break discussion about how the MSL is to be deployed to the surface using a tether. No backup here, just reliable explosive bolts.

One of the symposiums objectives was to have users exchange ideas about how they use simulation. This seemed to be more than fulfilled. If you have a chance to attend the next symposium, don’t miss it.

Disclosure: Siemens paid for my travel expenses to attend the event.

Inforbix $ errata, Autodesk Vault to the cloud

In my previous blog, I made an error on the pricing of Inforbix, which I have since corrected. I wanted to make sure you all have seen that correction. In the pricing example that was given, for a company of 100 persons, with 30 engineers, Vic Sanchez estimated that they might have 100K to 200K files to be indexed. The annual price for Inforbix for that size customer would be $10K to $15K. A great price range for the service provided. In fact one that is very compelling.

In the meantime it looks like Autodesk is planning to announce that their Vault will now be cloud hosted. I have no other details than some early teasers that were provided by Autodesk. It will be interesting to compare these offerings. I am planning on attending Autodesk University and will be there Monday through Wednesday, Nov 28-30. Say hello if you see me. I will report on this upon my return.

Inforbix – a new approach to cloud based PDM

18 Nov 2011: Oleg Shilovitsky, one of the more prolific bloggers in the PLM industry recently announced his new venture – Inforbix LLC.

Last week I had the chance to speak with Oleg, the CEO, and his partner, Vic Sanchez, about what their new offering was all about. Of course, I suspected that the new company, with Oleg’s background as a development manager of PLM systems, might be about PDM or PLM. Of course I was right. But, I wanted to find out what the product was all about, who founded the new company, what its objective was, a little bit about the technology, and who might use it and what it might cost.

Oleg and Vic were most accommodating in helping me understand and ferret out answers to the above questions.

Background

Inforbix began development on its product in early 2010. The product was officially launched in last October, 2011, and has been in Beta since last April. Shilovitsky teamed with a Russian development team to bring the product to fruition.

About the product

In a nutshell, here is what I learned. Inforbix, today, consists of a product data crawler app that is installed onto the target system or local network containing the product data to be indexed. After user customization of the crawler app, which basically tells it where to find the data to be indexed, the app goes to work finding relevant product data, exploring the metadata stored within the data files, and indexing the data. No actual data files are uploaded to the cloud, only metadata and where the files are located. What makes this exciting is that the crawler can crawl through many data types and vaults, and decode the inherent metadata and product structure.

Targeted at small and medium sized CAD companies, the object of Inforbix is to “help people find, reuse, and share product data.”

Both the crawler app and the cloud based search environment are optimized for manufacturing and design companies. I like that non–vaulted data such as Word docs and pdfs can be “related” back the products.

The system today supports crawling CAD and PLM data from Autodesk, PTC, SolidWorks, and Siemens. More will be coming in the future. Also supported are pdf, Word, and Excel files.

A few niceties

It is secure since no files are changed, moved or uploaded. Being cloud based, little maintenance or local support is needed. It is affordable and seems to be priced right – the first 20K files are free. Each 20K files after that cost $600 per year. Sanchez estimated that a typical medium sized company with 100 people and 30 engineers might spend $10K to $15K per year, a seemingly small cost considering that no hardware and no support staff is needed for the service. Also, it immediately allows accessing the data worldwide using a browser. Asked about what happens if indexed data moves, Shilovitsky said that the crawler monitors and tracks the new location, and updates the cloud.

Inforbix offers many ways to present the data to make sense of the product connections. These include Excel like tables and filters.

I see a few drawbacks and improvements needed

The original data still needs to be maintained along with support and local data backups. A local PDM system might still be needed to support applications that depend upon understanding the product data structure. Further discussions are needed as to how the system allows role-based access to the data. For instance, how can suppliers access the data? Data being relocated might have a delay before the indexes are updated on the cloud.

Conclusions

I really like the concept and the possibilities for extending the concept to other areas of a company. It seems that it would be relatively straightforward to have different crawlers looking for different data types. Think of it as a private Google for the data in your entire company or how to get organized without the fuss. If you are a company without a PDM system (and some 75% of companies are), then this is a perfect way to get started.

Try it out

With a free entry price, it makes sense to give this a try.

A few ways to learn more

The company: www.inforbix.com

The latest press release: http://www.inforbix.com/inforbix-launch-press-release/

Oleg shows how to start using Inforbix in 20 min: http://www.inforbix.com/how-to-start-using-inforbix-in-20-min/

Industry Siemens PLM Software Analyst meeting 2011 Notes

Acting more like the tortoise than the hare in the fable; Siemens PLM Software (SPLMS) has plodded and plotted its way to the leadership position in the PLM software industry. Sticking with its “never let a customer fail” strategy as well as other newly elucidated goals has enabled the company to maintain a steady pace in gaining customers and revenue over the years.

At the Industry SPLMS Analyst meeting held on the 7th and 8th of September in Boston, Tony Affuso, CEO and Chairman, revealed substantial growth for the company. SPLMS experienced strong double-digit license revenue growth, following five previous quarters of steady growth and exceeded profitability and cash flow targets. SPLMS does not reveal its precise numerical performance. Acknowledging that most of the growth was organic (not from acquisitions) and since their growth considerably exceeded that of the market, the difference had to come from gaining market share growing their business within existing customers, from new markets, and by winning business from their competitors. Affuso discussed recent competitive wins against Dassault Systemes (DS) and PTC. His conclusion and that of the speakers that followed credited their strategies of openness and never outmoding customer data, quite different than PTC and DS. DS, in particular forced customers to endure substantial conversions in going from V4 to V5 and now to V6. At PTC, Creo appears to require a massive data migration as well. Instead, SPLMS has deployed SOA and XML to maintain a pipeline between new and existing applications. Using such “data pipelines” allows connections between disparate applications, the drawback being a modest degradation in performance for the additional work required by each application. This has been made relatively unimportant by the tremendous growth in hardware that has continued unabated all these years.

In speaking with one SPLMS executive, being a part of Siemens has allowed a stability and financial base that allows continued heavy investment in R&D, even in difficult economic times. Both Affuso and President Chuck Grindstaff cited Siemens devotion to innovation and not retreating on R&D expenditures during difficult times.

Announced last year, HD PLM seems to be making real headway. Designed as a graphic way to present Teamcenter data visually, we may at last be beginning to see the demise of the numbingly tedious display of tables of data – instead to be replaced with graphic views of the product. For instance, why look at a table of components that are over cost targets? Instead show the out-of-whack components using a color scheme on the assembly view of the product. Grindstaff described this as a way of showing the “semantics” of the product data, or relating data relationships. While I am sworn to secrecy, I can tell you that Siemens is exploring methods for the average user to generate his own views of data he might be interested in. More on this later this year.

More to come in Part 2.

—–

DS clarifies DARPA crowdsource win

A few days ago Dassault Systemes (DS) released a press release announcing that the first online, co-created military vehicle was delivered through the collaboration of Local Motors, DS, and 12,000 community members.

I was really interested in this announcement because of the concept of crowdsourcing, I had never heard of Local Motors, and what in the heck was a co-created military vehicle? After delving into more details about Local Motors, and trying to find out if this military vehicle could withstand IED’s (improvised explosive devices, as often used in Iraq and Afghanistan) I was a bit confused. The DS PR people were kind enough to put me in touch with Al Bunshaft, Managing Director of DS North America.

Al and I spoke recently, and you might be interested in what I found out.

First of all, this is a DARPA initiative (Defense Advanced Research Projects Agency). By the way, DARPA is the agency that provided the early funding for what later became the Internet. So, when I hear that DARPA is involved my ears always perk up. This project appears to be one of a series of projects DARPA is initiating to see if there are better ways to provide defense sourcing differently than in the past; namely, cheaper, more rapid development, faster deliveries, and the delivery of specialized vehicles without a massive dollar commitment.

Here is what DARPA had to say about the requirements for this vehicle. “It is important to note that even though this is a militarily relevant vehicle, this is not an offensive fighting vehicle. The goal of this vehicle will be to transport items and/or people around quickly and efficiently in a potentially hostile but mobile environment.” I found it interesting that the design requires no body armor to protect against IED’s. Apparently the military feels that a fast off-road vehicle for emergency transportation can be effective, especially if it can avoid heavily traveled roads. This winning design appears to do just that.

DS was heavily involved with Local Motors, supplying much of the core CAD, CAE, and PLM technology, namely Catia, Simulia, Enovia, and visualization tools. The winning design was based on Local Motors’ Rally Fighter chassis, a street legal rally vehicle. Contributors were invited to submit their design concepts using any design tool, even paper based drawings and ideas. Both Local Motors and DS personnel were heavily involved in converting and assembling the submitted designs into a workable CAD model. To vote on the final designs a panel of military and commercial experts was assembled.

Then Local Motors sourced the components and assembled it at their micro factory in Arizona. Here is what it look like.

XC2V winning entry

—–

Click here for the DS press release.

Related websites for more information:

About the DARPA design challenge:

http://www.darpa.mil/NewsEvents/News/DARPA_issues_Experimental_Crowd-derived_Combat-support_Vehicle_(XC2V)_Design_Challenge.aspx

About Local Motors and their participation:

http://www.local-motors.com/XC2V Click on the description for an excellent description of the vehicle mission.

Check out the video on this page of the XC2V being assembled:

http://www.darpa.mil/NewsEvents/Releases/2011/2011/06/24_DARPA%E2%80%99s_Defense_Manufacturing_Efforts_Support_White_House_Vision.aspx

PlanetPTC 2011: Its all about Creo and MKS

Earlier this week I attended PlanetPTC. I attended some of the keynote speeches in the main event and PTC held special events for the media and press. We had the opportunity to rub elbows and hold private meetings with some of the executives from PTC. I found them to be open and earnest in their plans for the future.

It all starts with Jim Heppelmann, CEO and President. Jim described a strategy meeting he held with his executives to plot the resurgence of the CAD offering. He honestly said, several times, that development lagged for the product during the last decade and they found themselves adding more and more complex features to the already existing, difficult to use Pro/ENGINEER. [A situation many of their competitors are in also] The architecture was antiquated and all agreed a new approach was needed — one that might serve PTC well for the next decade or two. Thus was born Creo!

One might ask the question, as one did at a media Q&A event with PTC executives: “Why rebrand the product line? Why not use the famous Pro/E brand and go on from there?” Replied Rob Gremley, EVP of Marketing, “because it is not Pro/E, because customers said that it was far different, and to call it Pro/E would be a mistake. Thus, we needed a new brand, even though it might confuse people at first.” My reaction, they are right, even though I sometimes struggle to properly name the new software products. For example, changing the name of CoCreate to Creo Elements Direct is enough to confuse anyone.

The rebranding and new product rollout was not without risk. In fact it was very risky for PTC. Oftentimes companies are reluctant to change their cash cows. This is clearly spelled out in the book “The Innovators Dilemma.” Such a strategy often leads to a company’s demise, with their refusal to take risks. Heppelmann should be applauded for taking this very large step. Further, Heppelmann was emphatic that existing customers would not be hurt; they would not have to buy new software to support their installations; any upgrades would be painless. Apparently, the customers bought into this and the promises for Creo futures. In the last few quarters, PTC experienced its highest revenue growth (12%) in more than 10 years, with Creo Elements Pro up 40% in license revenue. CoCreate and View also saw substantial revenue gains.

As an aside, the sessions, both main and media sessions, focused on Creo and the MKS acquisition, with little attention being paid to Windchill – the best kind of focus for a modeling dude like me.

While PTC spent a great deal of time on Creo, there was very little depth — at most a few 5 minute AVI’s. So I am using these short videos and some conversations to form my opinion. PTC promised me a more in-depth look later at the products, and of course most of the new apps are shipping now. The primary apps, Creo Elements Pro and Creo Elements Direct, aside from UI improvements are pretty much the same as they were with Pro/E and CoCreate, the exception being the new apps that extend Elements Pro. These new apps show the promise of where Creo is heading. And it’s exciting.

Architecture

Here are 2 slides from Mike Campbell’s (DVP, Creo Product Development) presentation:

  • Evolve existing, monolithic products into
    • –A scalable suite, of
    • –right-sized, interoperable, integrated design apps,
    • –spanning the entire spectrum of product envelopment
  • Built upon a common data model, managed by a common PLM backbone, and delivered with a common user experience
  • Protect existing customer investments
    • –Commercial software licenses, and packages
    • –Existing Product Development (CAD) data
    • –Capabilities, best practices, working methods
  • Extended by a broad range of complimentary 3rd party apps
    • –Strategically selected partners,
    • –Reflected in our Product Strategy

Here is a summary of the Creo Products delivered in Creo 1.

1. Creo Parametric, the successor to Pro/E. A full-featured parametric modeling application.


2. Creo Direct, a new application.  Delivering a direct modeling experience. This app provides an intuitive way to easily modify parametric models.


3. Creo Sketch, a new app for sketching. This allows artists in the organization to capture their early thoughts about the way product should look, oriented towards industrial design of products.

Creo Sketch enables simple “freehand” drawing of ideas and design concepts in 2D

4. Creo Illustrate. a new app for use by the service organization to capture the service procedures such as assembly and disassembly in an intuitive way using Creo 3-D models.

With Creo Illustrate, users can easily create 3D technical illustrations by importing design data from all of the major CAD systems

5. Creo schematics, an app for schematics capture.

Creo Schematics users can create 2D routed systems diagrams for piping and cabling designs

6. Creo Simulate. An app for the analyst. Allows the professional analyst to analyze structural and thermal characteristics of models, created within Creo or external models.

7. Creo View MCAD

8. Creo View ECAD. Continuing the theme of openness are two more applications–Creo view MCAD and Creo view ECAD. These apps are used for viewing, markup and measuring data from either Creo or other CAD applications.

Visualization of both the 3D model and the ECAD PCB Layout inside of Creo View

9. Creo Layout, an application designed for the early conceptualization of the product.

What about deliveries? Creo 1 is shipping now. An update will add some apps later this year. Creo 2 will ship in March 2012, Creo 3 in March 2013.

Other thoughts

So, overall, what do I think about Creo? It’s innovative, I like how Creo Direct works to add features that change the model directly; the UI looks much easier and mimics that of Microsoft Office apps.

Some additional thoughts:

  • While PTC is working hard on importing any CAD system’s data into Creo, interoperability is a one-way street. Data is brought into Creo, but plans are murky to allow exporting data.
  • A user from Systems Spa, described how they planned to switch from parametric modeling to direct modeling now that they had a real choice and still stay within the same software architecture. After testing they concluded that direct modeling offered a greater that 30% productivity gain. I found this very interesting and wonder how many other users bought into parametric modeling because it was essentially, the only game in town. Now that’s changed.
  • Eventually Creo Elements Direct will merge completely into Creo Direct. On the subject of Creo direct, I cornered Mike Campbell in a hall and asked how Creo Flexible Modeling, a Creo Parametric extension can add direct modeling to a parametric model. For instance, what if a parametric feature disappeared after direct changes? His concise answer was that they never change the parametric model; direct modeling just adds features that change the model. Huh? Removing a pocket fills in the pocket with a new feature. Changing a face angle adds a feature that does that. He indicated there were special commands added that perform functions like this.
  • Future plans call for Creo 1.1 due Nov 2011, Creo 2.0 due March 2012, and Creo 3.0 due Mar 2013.
  • Creo Freestyle, discussed only briefly, and included with Creo Parametric and Creo Direct, allows morphing the surfaces of a solid into quite a complex shape. Instead of operating on curves, as does Alias Design, Freestyle operates directly on the solid model. Very impressive, but I am have little information about what it can really do.
  • Relex will be rebranded into Windchill Quality Solutions
  • PTC briefly discussed the ability to perform selective data reading from other CAD systems, With the advancements in AnyData it appears to be capable of isolating specialized modeling functions (such as body-in-white?) from other CAD systems. Could this be an opening for PTC to capture large OEM’s?
  • MKS’ Integrity software, now specialized for software, especially embedded software, offers leading edge capabilities for testing and the application of requirements, thus opening the door to advanced systems engineering. Stay tuned here. The PTC executives were very excited about the possibilities.

Pricing and packaging

Getting this information from PTC was like pulling teeth. It hurt, but they eventually relented. The packaging is divided into Creo Applications (such as Creo Direct and Creo Simulate), Creo Extensions (to an App, such as Creo Advanced Simulation Extension), and packages which combine Apps and Extensions (such as Creo Engineer). Shown below are some examples. There are many more.

Creo Parametric is similar to Pro/E, where Pro/E Foundation starts at $4995, US pricing for quantity of one. Creo Direct is $3500. Creo Simulate is $7995 without the non-linear extension. Other prices are available for PTC. Prices may be different outside the US. Creo Parametric with Flexible Modeling, really desirable offering is $5995.

—-

Follow

Get every new post delivered to your Inbox.

Join 433 other followers