Archive for the ‘Manufacturing industry’ Category

Toyota exonerated (mostly) for unexplained acceleration

January 23, 2012

I just had a chance to review John Shook’s, of the Lean Enterprise Academy’s, e-letter regarding Toyota’s role in the SUA (sudden unexplained acceleration) charges. NASA found no evidence of electronics malfunction. And this after Toyota recalled almost 10 million cars.

However, Toyota does come out completely clean. It turns out that the dealer who provided the Lexus to the Saylor family in California, the event which sparked the crisis, placed a too large floor mat without correctly attaching it to the floor. The mat entrapped the accelerator pedal, causing the accident.

Yet, we expected more of Toyota. It turns out that their enormous growth over the prior few years caused them to become less sensitive to customers, read more of the article here.

Kenesto: What is it?

December 18, 2011

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

December 2, 2011

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.

Inforbix $ errata, Autodesk Vault to the cloud

November 19, 2011

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

November 18, 2011

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/

The Cloud Lives!

November 18, 2011

18 Nov 2011: Ralph Grabowski proposed his opinion that the cloud is dead. He couldn’t be more wrong. Consider users at the Siemens NX CAE Symposium that ended last week. Virtually all of the eight users at a panel noted that cloud computing would definitely be part of their plans. Assuming that some minor issues such as security, cost, and application software licensing could be solved, all seem to have or want it in their future plans.

Several customers represented companies that already have with HPC clusters. While this ideal “local cloud” met their expectations, the cost of such a cluster is very high and not a solution for smaller companies.

I agree that the use of cloud computing for interactive applications is a bad idea. However, the vast computing power, parallel processing, and expected low costs make it a very appealing idea for tasks that require modest bandwidth and have high computational needs. Autodesk’s CEO, Carl Bass, clearly has the right idea. Autodesk, over the past two years has introduced several applications that span the range of interactive hardware and relying on the cloud to ramp up compute speeds. At AU last year I had the chance to listen to Bass and speak with him about his ideas for best utilizing the cloud. As I wrote in that article, Autodesk’s concept is to “Don’t replicate desktop solutions on the cloud. Instead make maximum use of desktop and mobile systems, utilizing the cloud where it makes sense.” Still makes sense today. Here is a link to that article http://wp.me/pvn8U-3e.

Oddly enough, with the possible exception of DS, Autodesk’s competitors don’t seem to get the concept. For example, while I interpreted from Siemens customers that they were excited about potential use of the cloud, Siemens PLM Software, except for licensing issues, seems to have no plans to enable them. The same goes for PTC.

Let me know what you think.
—–

How Local Motors won the DARPA contest

September 6, 2011

A few weeks ago I published an article entitled “DS clarifies DARPA crowdsource win.” A few things, in my mind needed clarification. Dassault Systemes PR rep, Jessica Harrison from fama PR, arranged for me to speak with Alex Fiechter, Local Motors Engineer. I was curious, among other things, about how crowd-sourcing was used for the design and whether it was useful. I also wondered how they handled input from 12,000 community users and what was the process they used. Finally I wanted to find our more about Local Motors.

Here is how the process worked. Local Motors (LM) massaged the DARPA specs for the contest into a “brief,” a mission statement of what they desired, and posted it onto their website, asking their community members if they were interested in responding. Most of the community members are interested in industrial design and some helped LM design their Rally Fighter. Along the way, LM developed their concept for Local Forge, an open source web-based co-creation platform. Apparently, car lovers worldwide love to design shapes for cars of their dreams. Local Forge is a way for them to share their designs via images, with all other community members.

A key aspect of the mission statement was to use the existing Rally Fighter chassis as a base upon which to build the body. With the mission statement , eventually 150 to 180 proposal were submitted, from which the final design was chosen. The proposals could be in any electronic form, such as images or even CAD files. They had to show the 3 required views at a minimum. The community then voted on the submissions. Only the winning submitter gets paid. LM used SolidWorks for the mechanical design and Catia for the body design.

What next? Will it be produced? DARPA owns the design now that the contract is complete. A research arm of the DoD, the DoD may or may not choose to produce the design.

Has Local Motors discovered a new way of doing business that involves minimal plant investment, a way to solicit valuable (and mostly free) input from leading designers, and deliver an exciting new product? You be the judge. Visit some of the links from my previous article quoted above and provide some feedback via comments on this blog.

——

Creo Freestyle exposes its shape

July 5, 2011

5 July 2011: Last week I had the chance to spend some web time with Paul Sagar, Director of Product Management at PTC. Paul is in charge of PTC’s surfacing and industrial design (ID) products. Paul’s background is in industrial design (ID) and design engineering in the UK and has spent about 11 years at PTC.

At PlanetPTC, Creo Freestyle was one of the many product announcements that struck me as fascinating. Just the idea of having incredible ID software as a freebie within Creo Parametric was one I wanted to explore further. After searching the PTC site for more detail with limited success, PTC’s VP and PR leader, Eric Snow, organized a web conference that “knocked my socks off!” You will see what I mean soon.

Immediate after my return from PlanetPTC I asked for a clarification as to precisely what Freestyle was and how it worked. Paul kindly responded with this piece of information -

  • “Freestyle is a new feature inside Creo Parametric that allows for rapid freeform surface creation. It is built upon the concept of subdivisional modeling.
  • The result of the Freestyle feature is a quilt of surfaces. The resulting surfaces or quilt can be added to, just like any other surfaces, with tools such as trim, merge, round, etc, or even thicken or solidify to make the model solid.
  • When working with Freestyle you always have to start with a primitive shape. A gallery of primitives is available for you to choose from such as sphere, cylinder, circle, disc, etc.
  • You are always working and manipulating the control mesh that surrounds the primitive. The control mesh can be subdivided up to add more detail or control. Adding more details allows for more control over the shape.
  • The 3D dragger allows for quick and easy manipulation of the control mesh and consequently the resulting geometry shape. The resulting geometry is high quality, curvature continuous, manufacturable surfaces.”

Here is what I wanted to find out about on the call:

  • What it does and what it cannot do,
  • Where it fits competitively,
  • How does it compare to a full ID system,
  • How the designs get started and how they are stored within Creo, and
  • What is sub divisional modeling?

Paul explained that Freestyle is a new freeform surface modeling capability added into Creo Parametric. Called a super feature within the model tree, Freestyle appears as a single feature with the tree. It’s almost like a modeling environment within a feature. It’s a simple and easy tool use, and is designed to be intuitive, interactive and quick. Targeted to industrial designers who want a tool to conceptualize but are not interested in the methodology of building surfaces, which has traditionally been done by building curves and surfaces from those curves. Modifications are made to the surfaces by going back and manipulating the curves. Instead Freestyle is designed to just deal directly with the shape. Thus users can concentrate on the form rather than what’s behind the form.

See the video of the bottle design that Paul downloaded.

The resulting surfaces generated by Freestyle are of high quality. You can take them directly to manufacturing. They can be thickened and brought directly into Creo Parametric as solids. They can be acted on as a normal solid with all solid modeling features, for instance, by adding ribs and bosses and holes. It can be brought directly into machining.

Surface manipulation. Can you control how the resultant surfaces by, for instance, controlling tangencies or other typical surface controls? His comment: “No. That is not how sub-divisional modeling works. It does not use normal surface patching techniques.”

A design starts with a primitive. Each primitive comes with a control mesh.

Creo Freestyle Primitives

Each mesh has edges, vertices, and faces. You can push or pull on them, or you can subdivide it. For instance, you can chose and edge and “split this edge,” and Freestyle will add more controls on that edge. The more controls, the more flexibility to manipulate the surface.

Each face of the control mesh corresponds to an actual patch in the resulting geom. that is created. Each patch is curvature continuous, resulting in a smooth model. Surfaces are G2 continuous, with some exceptions.

In the movie file of the bottle design, you should be able to see the design being developed. Unfortunately there is no audio file describing the workflow, but I am sure our readers can follow the concepts of Freestyle from watching the movie. Note that the design starts by building a solid model from a scanned sketch.

A sketch of the bottle

Trace Sketch allows importing the image and manipulates it, such as for fit or scaling, the objective being to use the image as an underlay for the design. A sphere is used to start designing the solid model using Freestyle. Special features during the process such as “connect” joins two faces together for completing the handle. Other operations such as a crease can generate either a hard or soft edge. Also note that Creo does not capture the history of the Freestyle design; only as a single Freestyle feature.

The 3D model of the bottle

Other sub-divisional modelers like Maya and 3D Studio Max, use sub-divisional modeling, but none of these modelers create NURBS surfaces — Creo Freestyle does. It creates regular Creo Parametric surfaces. Similar capabilities to Freestyle exist in Rhino’s T-Spline models and CATIA’s Imagine and Shape.

Conclusions:

  • You can build geometry very quickly with Freestyle.
  • It’s full integration with Creo Parametric integrates Freestyle design into the traditional design workflow.
  • It has only a few commands and should be relatively quick to learn.
  • The resulting geometry is of high quality and thus not throwaway work.
  • The resulting surface geometry can be operated on directly using Creo Parametric surface commands or converted directly to a solid and manipulated with traditional Creo Parametric commands.
  • With Freestyle free and relatively easy to learn, we recommend that users who do any industrial design begin using Freestyle right away.

Notes from Siemens PLM Connection 2011

May 24, 2011

A few weeks ago I attended the Siemens PLM Connection 2011 conference in Las Vegas. Since returning I have been busy with all kinds of matters, but I wanted to get some of my thoughts on the conference to you, my readers. Siemens promised me copies of the slide presentations, which I have recently received. As any of you who have attended similar conferences, the slides go by so fast that there is little time to write the key points down.

Arriving at the hotel on Sunday, May 1st, the event started with a small cocktail party of the media with some Siemens executives. I had a chance to meet with a briefly speak with some executives before going to my room exhausted from traveling and standing on my feet for three hours. Among the execs I had a chance to speak with were Eric Sterling, Dave Shook, Kris Kasprzak, Tony Affuso, and Dan Staples. The mood was decidedly upbeat and all were excited about their performance the previous year and so far in 2011. I was unable to get specific details, as is Siemens’ custom.

At the kickoff keynote the next morning Dave Shook, Sr. VP Americas, opened the session and introduced keynote speakers from Microsoft and IBM. These were the usual pitches from cooperating vendors. Instead both companies discussed interesting technology challenges; Microsoft discussing how unstructured data can be managed, and IBM discussing the challenge of hyper digitization and the need to close an innovation gap with the velocity of change accelerating.

Tony Affuso, Chairman of Siemens PLM followed with highlights of the company’s year. Basically Siemens PLM is on track after five quarters of growth, now with 68,500 customers, 7.2 million seats, and double-digit license revenue growth. This compares to Dassault Systemes (DS) real growth last year of 7%, less the temporary revenue bump from the IBM PLM acquisition. The company has a good backlog and is executing across the board and winning substantial accounts. Following Tony was Claus Oesterschulze, describing Siemens extensive effort to internalize the use of their own software (NX, Teamcenter, and associated apps). No easy task, as in most customers, organizational changes are required along with process changes. Convinced that “IT is a big lever for business” Siemens is aggressively moving ahead and focusing on how to manage complexity. Below are a few slide from the Oesterschulze presentation.

 

Later in the morning Chuck Grindstaff, President and CTO of Siemens PLM Software presented his “technology vision.” He viewed where they are today in fully integrating Teamcenter across an enterprise to fulfill its PLM needs: view models fully and anywhere, check a model against its requirements and be able to trace these on the products; review and initiate simulations against specs directly in the CAD environment and to ask highly complex questions; ability to optimize the design for performance including cost and sustainability; using Tecnomatix to insure that manufacturing has correct models, processes and allowable variations thus enabling what-if manufacturing studies. Thus his focus on a fully integrated system, much of which is already in place today, with more coming shortly, as evidenced by the NX, Teamcenter, and Tecnomatix presentation we saw later in the week. Grindstaff feels they are far ahead of their competitors and that customers can now see that. A strong point in his direction is the ability to implement continuous changes in the product rather that the discontinuous changes that the competition [Dassault Systemes] makes. An interesting point about his thinking was his comment that “If we [Siemens PLM] can formulate the value proposition correctly then customers will listen.” His key investment areas are in intelligently integrated information, continuing their future proof architecture using SOA and XML that isolates and allows ready integration of new software, expanding their TC HD experience, systems engineering expansion, integration of domains such as MCAD, ECAD, software, plants, etc. and continued openness.

Joan Hirsch, VP of NX Products, and Paul brown, et al reviewed their thinking about the future of NX. Some of their goals include: building an effortless UI, improving complex product visibility by allowing viewing of multiple data sources and using HD3D visual reporting, integrating multiple design disciplines together, allowing front loading of best practices and knowledge, and requirements management and validation. The chart below summaries much of what they discussed.

What I found most impressive was their emphasis on non-disruptive improvements and Siemens focus on using making HD3D easy to use to “bring to life” the enormous reserves of data stored within TC. This is their 4th release of synchronous technology (ST) within NX and strides continue to be made in its use, some of which I hope to explore in more detail in an upcoming report.

Later Steve Bashada, VP of Teamcenter Products and Bill Boswell, Director, gave a Teamcenter update. New versions are due next February, with a “more visionary” version due next September 2012. Bashada viewed their key investment areas as the following: systems engineering, corporate social networks, cacheless search, massive model viewing, HD-PLM extensions, and thin client access. A Teamcenter mobility app for the iPad was announced. I downloaded it, but have yet to try it out, because I need to sign into their TC central demo app and database. I may report on this later. Think it’s complicated? Take a look at their portfolio list below.

Getting tired from furiously scribbling notes, I then attended a Velocity business update starring Karsten Newbury, SVP and GM of the unit. Newbury discussed their business momentum, noting that in 2010, their growth in licenses was 30%, with Solid Edge (SE) accounting for 50% of that. He is investing in an expanded presence by adding resources [people], channel enablement [his words], and a focus on community for a bigger academic presence and mode direct feedback events. ST3 was well received due to its ability to support both ordered and synchronous approaches.

Mario Joyal, of Matritech, a small company in Quebec, described his results using SE with ST3. A recent design took 50% less time and other users found it easy to use. Kris Kasprzak, product manager for SE, described ST4 which is due to release on June 15. We are allowed to discuss some info about the upcoming release of ST4. New tools and functions coming include those for: advanced machine design, expanded collaboration, simulation for sheet metal, and improvements to their already impressive drafting.

After a delightful dinner and cocktails for the press and analysts Monday evening on the top floor of the Rio hotel, we finally ended the day.

On Tuesday we heard a digital manufacturing (DM) strategy update from Ziyon Amran, VP of digital manufacturing software, followed by an amazing presentation by Gene Coffman of how Ford performs virtual manufacturing. Siemens still leads the industry in revenue by a wide margin, as shown in this chart.

Key manufacturing technology domains include assembly planning and validation, robotics and automation planning, part manufacturing, and plant design and optimization. Amran discussed many of the new capabilities in each of these areas. Amran summarized what Tecnomatix offers their customers

  1. Breadth and depth of offering addressing all DM functional Areas
  2. Focused industry and domain Solutions
  3. Integrated Knowledge Management through single source of Product & Manufacturing data as part of the Teamcenter PLM platform
  4. Advanced technologies for Machining, Robotics and Human Simulation and for Enterprise Process Authoring

Coffman’s presentation focused on how Ford makes virtual manufacturing work at Ford (it isn’t easy) and how it contributes to Ford’s profitability and design to manufacturing cycle reduction. Here is one example of the continuing benefits shown by Coffman.

And finally, to wrap things up I met with Al Hufstetler, VP Quality Planning and Validation, who took me to task on a comment I made in my blog about the DS acquisition of Intercim. I stated that “In shop floor analytics DS now has the edge.” Hufstetler pointed out that Intercim’s solution uses analytics to isolate issues, whereas, Siemens solution uses a better solution, a feedback system that not only can detect quality issues, but can actively correct them. For more details on this, contact Siemens PLM Software.

www.siemens.com/PLM

Disclosure: Siemens paid for my hotel and conference admission. TechniCom paid my other travel expenses.

Highlights from the Versata think3 conference call on 19May2011

May 22, 2011

I listened in to the conference call held by Austin Scee of Versata think3. He was there to discuss Versata and the future of think3 on the conference call. Much of this was covered in his letter posted in my previous blog. Here are some of newest highlights:

  • Scee and his predecessor have spoken to more than 300 customers since last October. Their mission is for customer success.
  • He urged customers, if they are in a quandary as to who to pay for maintenance, to withhold payments until it is clear. Customers can still call Versata for service whether they have paid or not.
  • He further urged customers not to pay for any licenses other than those generated from Versata; otherwise “you are stealing from us.”
  • The company strategy is: Reset, Revitalize, Relaunch.
  • Versata has acquired 20 companies over the last 6 years, most of which were in distress. The first 100 days are the most difficult. [Ed. In this case we are way past the first 100 days!]
  • His strategy for the first 18 months is to focus on existing customers.
  • Scee unequivocally stated that Versata owns the IP and is asserting its rights in Italy and elsewhere. They bought the rights from think3, Inc., the US based company. Versata believes that the Italian court is using improper legal concepts; that an exclusive license (which they evidently purchased) is the same as an IP purchase.
  • An independent auditor was employed by Versata to evaluate the value of think3 before the acquisition. Versata spent millions of Euros on the IP. Versata paid twice what the auditor valued the company.
  • There are 15 global “success managers” to support customers [Ed. What we would call account managers.]
  • They are looking to improve the usability and speed of think3.
  • The company seeks CAD development expertise to “plug into the devFactory.”

Check out devFactory for yourself at www.devfactory.com. It’s pretty obscure what they do and there is nothing that indicates they are part of Versata.

You can check out the website at www.think3.versata.com. Oddly, the support site referenced contains nothing on think3. So far — much talk, but little action!


Follow

Get every new post delivered to your Inbox.

Join 400 other followers