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.

Direct Metal Laser Sintering (DMLS) produces high strength and finished metal parts

10 March 2012: A few weeks ago I received a press release about EOS, the laser sintering company based in Germany, that got me thinking about their process. They claimed to directly produce parts, specifically knee joints, from an additive machining process that could be used in orthopedic surgery. Nick O’Donohoe, of the PR firm, the Parker Group, stated that “A sea change in medical treatment—mass customized, patient-specific care devices—will be evident at this years’ American Academy of Orthopedic Surgeons (AAOS) meeting. There, EOS and its customers are displaying all types of innovative, high-quality orthopedic products that excel in effectiveness, fit, and comfort.”

Of course, from my years in the industry I knew quite a lot about additive manufacturing, but naively assumed it only produced low temperature and low stress capable plastic type parts.

After a little research into the background of laser sintering I was surprised to learn EOS’ laser sintering can produce parts made from chromium steel and even titanium! The difference between the melting points between plastic and these metals was several thousand degrees. I was determined to find out how this was done.

I scheduled a call with Andy Snow, Regional Director at EOS of North America. I have attached a summary of call below. But first, I had to learn a bit about powder metallurgy and high power lasers.

How it works

Basically it works similar to an SLS (stereo-lithography) additive machining process. A laser is directed to the material and it solidifies the material. In this case the material is powdered metal and the laser is high powered enough to fuse the metal in its beam area to a depth of 20 microns (typically SLS systems solidify plastics at an 120 to 200 micron depth). The elevator is lowered 20 microns, powdered metal is swept over the previous layer and the process repeats, of course with the laser beam directed to the precise locations based on an original CAD converted model.

Other similar technologies include laser sintering and electron beam welding. It is left to the reader to examine these alternatives for their particular requirements.

Conclusion

While EOS DMLS systems are pricey ($600K+) compared to plastics additive manufacturing, the choice using of high strength metals directly in this process offers the users a final product ready  for use, possibly after some clean-up such as polishing. In addition, certain geometries possible with additive manufacturing, such as internal channels, can be machined no other way. See the references below for additional links.

Disclosure:

No compensation of any sort was provided for this article.

—–

An interview with Andy Snow, Regional Director at EOS of North America

RAY: EOS has a unique approach with its direct metal laser sintering (DMLS). I am interested in the strength of the materials and finishing process and what’s required to produce a finished product? Can with start with a discussion of orthopedic knee replacements?

ANDY: Traditional knee replacement devices are made using a casting process. Our EOS produced parts are far better than cast materials, which need secondary machining and polishing.

RAY:  Does your final product also need additional machining operations?

ANDY: Yes, for orthopedic devices intended for implants, which need porous surface for orthopedic implants.

RAY: Porosity; does powdered metallurgy need binders?

ANDY:  Not in DMLS (direct metal laser sintering), as opposed to traditional sintering process.

RAY: I read that EOS systems melt Titanium. Is this true?

ANDY: Yes pure Titanium.

RAY:  What does a system cost?

ANDY:  $600k to 750K USD, depending on what materials you need to process.

RAY: Does titanium-sintering cost more?

ANDY: Not necessarily. It depends mostly on if there is a need to process multiple metals.

RAY:  Does the operator just dump a pail of powdered metal in the hopper and go?

ANDY: The input is powdered metal. It works similar to a stereolithography process – growing geometry layer by layer by heat from laser. Layers for our metal process can be 20-80 Microns depending on alloy. Plastics typically are thicker and 100 to 150 microns per layer.

RAY: EOS machines are slower?

ANDY: Yes

RAY: How slow? What are some example build times?

ANDY: It is geometry dependent. For example, a quantity of 16 54 mm acetabular knee cups take about 16hrs to build. The same builds in plastics might be six times faster. Of course plastic cannot directly be used for knee cups. However, patient specific drilling guides are often built in plastics. VisionAire is one trade name. [You can find out more at http://global.smith-nephew.com/us/patients/ABOUT_VISIONAIRE.htm]

RAY: How is this better than selecting from a suite of fixed knee cup sizes, as is most often done today?

ANDY: A custom product matches the bone geometry exactly. Thus there is a better fit.

RAY: What are the cost aspects as compared to mass-produced parts?

ANDY: The patient match is better because operating room expense is less because easier to install.

RAY: Are there any special environmental requirements?

ANDY: Nothing special is required, except within the EOS machine for specific metals. The EOS machines are typically in a machine shop at the OEM.

RAY: Does the metal sintering use a co2 laser?

ANDY: Plastics additive manufacturing uses CO2. DMLS uses Diode pumped fiber optic laser, 200W or 400W

RAY: what about finishing?

ANDY: Detail finish out of metal is better due to laser spot size; layer difference, and material particle size. Plastic 60 microns, metal 20 microns. Metal can use even smaller particle size because it’s heavier. Company is exploring micro laser sintering of 1-5 microns.

RAY: what other industries use this DMLS technology?

ANDY: Aerospace, especially in turbine designs.

RAY: Who is the competition in MLS (Metal laser sintering)?

ANDY: The competition is mostly German companies. These include SLM Solutions, Phenix Systems, and ARCAM with electronic beam technology. The DMLS acronym is only used by EOS.

RAY: What makes you better than the competition?

ANDY: Our finished part quality. We are the industry leader with 60-65% of the market share. We have a strong technical base. EOS has about 400 employees with 1/3 dedicated to R&D.

Here are some images supplied by EOS:

A laser-sintered drill guide designed to conform to the patient’s bone geometry. (Courtesy Materialise)

A DMLS-made gas turbine prototype swirler in cobalt chrome. (Courtesy Morris Technologies)

An EOSINT DMLS system laser-sintering cobalt-chrome dental copings and bridges in a batch. Each bridge can be a different custom design, based on dental data from an individual patient (Courtesy EOS)

An EOSINT M 280 direct metal laser-sintering (DMLS) system. (Courtesy EOS)

References:

———————-
 Below is the press release that I quoted earlier:

EOS DEMOS LATEST ADVANCES IN LASERAY: SINTERED ORTHOPEDIC PRODUCTS AT AAOS 

Customization of implants and drill guides provides significant advantages to surgical teams

Novi, MI, February 2, 2012—For proof positive that laseRay: sintering is changing the face of medical design and manufacturing, attendees of this year’s American Academy of Orthopedic Surgeons (AAOS) meeting can stop by the EOS booth (#259). The world leader in laseRay: sintering systems is showcasing a working EOSINT M 280 direct metal laseRay: sintering (DMLS) system to demonstrate the extraordinary benefits the technology offers for orthopedic applications. The evidence includes a wide range of innovative medical products and prototypes used for instrumentation as well as spinal, joint, and cranial surgeries. The show is being held February 8-10 at the Moscone Center in San Francisco (California).

“An entire new world of orthopedic treatment and procedures has opened up,” says Martin Bullemer, EOS manager for medical business development. “Because our laseRay: sintering systems can cost-effectively manufacture any imaginable geometry, and any variation on it, they are changing the way we think about medical products.”

Laser sintering is an additive manufacturing process involving next-to-no tooling, molding or machining costs. As a result, devices can be economically mass-customized to conform to the requirements of individual doctors or patients. Orthopedic suppliers use DMLS and plastics laser sintering to create a diverse array of drill guides, clamps, implants, and surgical instruments.

EOS-related activities at the AAOS meeting include:

  • EOS customers C&A Tool (booth 4017), Morris Technologies (booth 359), and Oxford Performance Materials (booth 2821) are exhibiting laseRay: sintered products and prototypes. C&A and Morris both focus on DMLS, while Oxford Performance Materials uses the EOSINT P 800 with high-performance polymers to manufacture customized medical implants.
  • Highlights from WITHIN Technologies Ltd include their FEA/CAD optimization software that works with EOS’ plastic and metal laseRay: sintering systems to create strong, lightweight parts including innovative lattice structures.
  • FHC is exhibiting its new line of patient-customized stereotactic fixtures for cranial targeting. The new fixtures are more accurate and comfortable for the patient than standard stereotactic frames and are suitable for a broad range of head types, and for targets not easily reached with a traditional frame. They also reduce operating room times for the procedure by as much as two hours.

“Many surgeons and medical designers are only just now becoming aware of the breadth of applications made possible by this manufacturing technology,” says Fred Haer, CEO of FHC. “The laseRay: sintered products on display at this meeting are at the forefront of a revolution in personalized patient care.”

About EOS

EOS was founded in 1989 and is today the world-leading manufacturer of laseRay: sintering systems. Laser sintering is the key technology for e-Manufacturing, the fast, flexible and cost-effective production of products, patterns and tools. The technology manufactures parts for every phase of the product life cycle, directly from electronic data. Laser sintering accelerates product development and optimizes production processes. For more information visit www.eos.info

Toyota exonerated (mostly) for unexplained acceleration

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?

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.

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/

The Cloud Lives!

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

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

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.
Follow

Get every new post delivered to your Inbox.

Join 433 other followers