Posts Tagged ‘CAE’
Thursday, April 17th, 2014
Earlier this week, MSC Software Corp. announced that a jury in the United States District Court for the Eastern District of Michigan found that Altair Engineering willfully and maliciously took MSC Software trade secrets (from Adams simulation software) to use in its MotionSolve product. In other words, the ruling spells out that Altair Engineering knowingly took MSC Software trade secrets with malicious intent.
Keep in mind, though, that this award was no slam-dunk, as the suit was first filed in July 2007 as MSC Software Corp. versus Altair Engineering Inc. The six-week trial ended with two days of jury deliberation.
The jury awarded MSC Software $26.1 million for misappropriation of trade secrets and breach of confidentiality agreements by Altair and two former MSC employees who are currently executives at Altair.
Jurors found that Altair had misappropriated some source code as well as concepts or processes that are used to write the code from MSC, and that the employees had also violated one or more non-solicitation, confidentiality, or severance agreements with MSC.
According to the lawsuit, after Altair hired some former MSC Software employees, Altair began developing a software product called MotionSolve that competed directly with MSC’s Adams/Solver.
MSC had previously alleged that at least eight employees had left MSC between 2005 and 2007 and took jobs at Altair. Five of those employee claims were dismissed prior to trial.
Monday, January 20th, 2014
There are a number of simulation/analysis software products available for conducting motion and FEA studies. However, the ability to conduct them both, as well as optimizing assemblies is a tall order, especially for mere mortals and non-CAE specialists. With a relatively short learning curve, for this evaluation SimWise 4D proved its mettle for handling motion, FEA, and optimization in one comprehensive package.
What is known today as SimWise 4D began when Design Simulation Technologies (DST) acquired a license from MSC Software Corp. to the MSC.visualNastran 4D (vn4D) product. That software traces its roots to the Working Model 3D product developed by Knowledge Revolution, which was acquired by MSC in 1999, extended to include FEA capabilities, and renamed Working Model 4D.
Wednesday, January 15th, 2014
Although still a few months away, there are a couple of important conferences that will be co-located this year — Collaboration & Interoperability Congress (CIC) and NAFEMS Americas Congress.
NAFEMS and Longview Advisors just announced plans to co-locate the NAFEMS 2014 Americas Conference and the Collaboration & Interoperability Congress (CIC) in Colorado Springs, CO, running May 28-30, 2014..
The central theme of the co-located events is, “Driving Product Development with Collaboration, Simulation, and Integration.” (more…)
Thursday, March 15th, 2012
National Instruments (NI) is an interesting company that develops NI LabVIEW software as its flagship product. The company is fortunate to sell its products to a diverse customer base of more than 30,000 different companies worldwide, with no one customer representing more than 3 percent of revenue and no one industry representing more than 15 percent of revenue. Customer base diversity is an especially good thing in the technical software market.
I have followed NI for a number of years and really got interested in the company a few years ago with LabVIEW 8.5 being used alongside SolidWorks. LabVIEW has followed a natural progression in the evolution of the NI product line for designing and prototyping complex systems, including robots, that are becoming increasingly pervasive in the world around us, and not just manufacturing environments anymore.
National Instruments supports the increasing need for simultaneous simulation of mechanical and electrical systems, also known as mechatronics. As I have been saying for several years, there was a time when mechanical systems and products were strictly mechanical, however, the majority of today’s products continue to become more capable, and more complex, involving the integration of mechanical, electrical, and software subsystems.
A more comprehensive way to view mechatronics is the systematic integration of mechanical, electrical, electronics, and embedded firmware (software) components. When all of the various components are combined the result is an electromechanical system. Maybe a better term is functional ecosystem. In this context, mechatronics is characterized by software and electronics controlling electromechanical systems. This description is widely seen in automotive engines and other automotive systems, as well as production machinery and medical equipment.
A continuing trend is that as mechatronics systems get more complex and as functionality demands increase, in many instances software and firmware are replacing or at least supplementing hardware. A benefit of this transition from hardware to the burgeoning emphasis on software is called “postponement,” that is, the ability to include or change major functionality features during the final stages of production via embedded software. (more…)
Friday, January 27th, 2012
There are several types of CAE-related manufacturing applications for optimizing the use of materials, tools, shape and time, and machine layout by simulating and analyzing specific manufacturing processes. However, probably the most common method for getting CAE into a manufacturing environment, finite element analysis (FEA) for parts and tooling.
FEA is a numerical technique for calculating the strength and behavior of structures. It can be used to calculate deflection, stress, vibration, buckling, and other behaviors. Typical applications for FEA would include minimizing weight and/or maximizing the strength of a part or assembly.
In FEA, structures are divided into small, simple units, called elements. While the behavior of individual elements can be described with a relatively simple set of equations, a large set of simultaneous equations are required to describe the behavior of a complex structure. When the equations are solved, the computer and FEA tool displays the physical behavior of the structure based on the individual elements.
FEA tools can be used for innovating or optimizing mechanical designs. Optimization is a process for improving a design that results in the best physical properties for minimum cost. However, optimization using FEA tools can prove difficult, because each design variation takes time to evaluate, making iterative optimization time consuming. On the other hand, FEA tools can really shine when seeking new and unique ways of designing things – the most crucial aspect of innovation.
Before committing to any CAE tool, however, be sure it is compatible with your existing CAD and CAM tools, the types of parts and assemblies you design, and your general workflow.
Keep in mind that there is no one tool that serves everyone’s needs. Some will be interested fluid flow, others in structural mechanical properties, and still others in thermal issues. Get input from as many groups within your organization as are likely to benefit from CAE tools. When evaluating CAE tools, make sure you evaluate them with your models; not just models supplied by a vendor. That way, you’ll be able to objectively evaluate different CAE tools that best suit your needs in your environment, and not be overly swayed by what a vendor wants you to see. Obviously, it’s in your best interest for objectivity to use the same parts or assemblies with different CAE tool vendors.
Finally, a word of caution. Don’t expect CAE tools to solve all your problems with all of your parts. Like CAD and CAM tools, they should be used in conjunction with experience and common sense to arrive at optimized and innovative designs. Calculating return on investment when using CAE tools can be as complicated as performing analyses on complex assemblies. However, you can probably count on estimating ROI from time saved during the design process, lower material costs, reduced numbers of physical prototypes and ECOs, and possibly greatly reducing the number of product liability lawsuits. CAE tools cannot perform miracles by themselves because they still require a significant human element, but employed wisely, will likely improve your workflow and provide tangible benefits.
Wednesday, January 25th, 2012
By now you’ve almost certainly got MCAD and CAM tools as a vital component of your business. With them you’ve hopefully seen how they have positively impacted the way you work, as well as the way you interact with your customers and vendors. Looking for a way to further increase your productivity, while continuing to optimize your processes?
If you haven’t already, it’s time you considered integrating tools into your workflow for simulation and analysis of virtually any aspect of the product development lifecycle. Although known in some circles as computer-aided engineering (CAE) tools, that acronym has largely been replaced by simulation and analysis, although they all mean roughly the same thing.
It wasn’t all that long ago that CAE was relegated to the latter stages of the design and manufacturing (product development) process — too many times as an afterthought. This is changing, though, on two fronts. First, realizing the potential payback in terms of reduced production time and getting it right the first time, many design and manufacturing organizations have moved CAE tools further forward in the development process. Some are even using them in the earliest stages of design, the conceptual phase. Second, software vendors are getting better at integrating CAE with their CAD and CAM tools.
A major roadblock to CAE’s wider acceptance has been the perception that only high-priced analysis specialists (math PhDs?) could understand and work with CAE tools. While specialists are required for some of the high-end tools for performing complex analyses, there are many CAE tools now on the market that require just some basic training and practice to become proficient in a relatively time.
Admittedly, all CAE tools require a technical mindset, but you don’t necessarily have to have a doctorate in math anymore to run many types of analysis and simulation. It really just requires familiarity with the interface of a CAE tool for creating and loading digital models, and then reviewing and interpreting the results. A really nice thing is that many CAE tools now work from within the familiar UI of your CAD or CAM tool. Finally, computer prices that continue to drop have helped popularize CAE tools, because some of them require a lot computing horsepower when working with large assemblies or very precise engineering constraints.
If this all sounds easy, it is to a point, but there are some caveats. That’s what we’ll discuss next time, as well as the most commonly used CAE tool — FEA.
Friday, January 13th, 2012
Last time, based largely on vendors’ marketing language, PLM was defined as a comprehensive system and process that integrates, interfaces, and interacts with every other IT system within an organization, including CAD, ERP, CRM, etc. While this occurs at a peer level, the PLM oversees and, to a certain extent, controls all data exchanges.
I think, however, there is a better definition and model of what PLM actually should be. Unlike many vendors’ definitions, PLM is not a peer system to other systems, such as ERP, SCM, and CRM. Rather, PLM is the intellectual property backbone of an enterprise. While the other subsystems deliver indirect cost-reducing improvements, none of them have any measurable impact on delivering top-line, revenue enhancing results and only a minor impact on lowering direct costs. The only way to positively impact top-line revenues is to develop and build innovative, higher-quality products, and PLM is the only system of the four that addresses these issues.
In this context, PLM transforms ideas to profits, capturing customer experiences, and generating ideas for new products. Along the way, the intellectual property undergoes several transformations (such as ideas to concepts, concepts-to-prototypes, prototypes-to-products, and so on) and interacts with the other systems. Ideally, a well-implemented PLM system provides a comprehensive framework that lets all the other systems and disparate groups of users to easily interact with an enterprises’ intellectual property so anyone can add value to it.
I think the revised definition and vision finally get to the heart of what a PLM was always envisioned to be, but thus far, executed and implemented by only a few PLM vendors – an intellectual property asset manager that can be used universally within an organization.
Ultimately, the success of PLM is dependent on two things. First, it is imperative that vendors communicate comprehensively and truthfully what their PLM offerings can do and integrate with, as well as what their customers can reasonably expect in terms of gains and ROI. Second, customers must educate themselves to the true needs of their organizations and how they expect PLM to fit in with the rest of their existing and future IT infrastructures. Only then will customer expectations and vendor promises meet for improving processes and resulting products through intellectual property asset management.
Can vendors pull off what PLM was truly meant to fulfill? I think so, and more and more vendors will do so, increasingly with cloud-based services that are just beginning, but should decrease implementation costs and increase productivity through being available to anyone anywhere.
Wednesday, January 11th, 2012
Like many of the ingredients in a manufacturing organization’s computer technology alphabet soup, such as ERP, SCM, CRM, not to mention CAD, CAM, and CAE, product lifecycle management (PLM) for years has been touted as being the “next big thing” and the the final frontier for integrating all manufacturing IT functions. Honestly, though, can it truly provide all that the various vendors are promising? I have asked myself that question for several years now — is PLM a great hope or just another great hype?
It seems that every vendor defines PLM in a manner that best suits their respective existing product lines and business practices, and not always necessarily the processes of the customers they are trying to serve. Therein lies a big part of the PLM problem. PLM should address processes and not just products – neither the vendors’ nor their customers’ – and too few vendors to this point have stressed the processes they are claiming to improve over the products and services they are trying to sell.
It also seems like everybody (yes, now including just about every CAD vendor big and small) is at least trying to get into the PLM act, regardless of whether they should or should not based on their development and integration capabilities or the needs of their customers. Even database giant, Oracle, says it wants to be a major PLM player, although the company has eluded that it doesn’t want to dirty its hands with traditional CAD/CAM stuff — it wants to look at the bigger picture, although it doesn’t elaborate what that picture is.
Although they are quite different in requirements, approach, implementation, and task load, I continue to see PLM and PDM (product data management) regarded practically as equals in vendors’ conference presentations and promotional advertising. Using these acronyms interchangeably only adds to the confusion that already exists in the PLM marketplace. However, it does give more vendors more opportunities to say that they “do PLM.” By definition, PDM handles only data and is a subset of PLM; whereas PLM, to many peoples’ thinking, should interface and interact with every other IT system within an organization, including ERP, CRM, etc. at a similar level as a peer system.
So, is PLM fulfilling the prophesy that the vendors have promised? That’s the question we’ll tackle in the next MCADCafe Blog.
Thursday, April 29th, 2010
I attend a number of technical and engineering conferences over the course of a year, primarily CAD or CAM related, with some CAE thrown in. Some of the events are good, some are not so good, and some are just a waste of time.
Right now I’m at a very interesting CAE event for the first time– Altair Engineering’s Hyperworks Technology Conference (HTC) 2010. From what I’ve experienced so far, I classify this event in the “good” category.
The event showcases its unique product and service offerings, as well as its diverse user base that represents the automotive, aerospace, defense, consumer electronics, and, medical device industries.
If you are not familiar with Altair Engineering, know that is one of the most significant players in design simulation and analysis with its Hyperworks technology whose product and service capabilities are available on a “pay as you go” basis. The plan is based on tokens purchased and used
As far as the industries represented goes, today’s presentations were slanted a bit toward the automotive industry with talks from Ford, Porsche, Michigan Solar Car customers, and GM, but that’s OK – we are in the Detroit area, after all.
I also spent some time with a couple folks involved with Altair’s industrial design tool, solidThinking. It’s a unique and very capable conceptual design tool that I will be spending hands-on time with over the next few weeks as the new version, 8.1, is due to ship in the near future.
This blog post provides just a brief overview of the conference, but I’ll be going into more detail on specifics of what I experienced and who I talked to in the next MCAD Weekly that publishes May 10, 2010.