Mostrando entradas con la etiqueta cad. Mostrar todas las entradas
Mostrando entradas con la etiqueta cad. Mostrar todas las entradas

lunes, 5 de diciembre de 2011

Getting Designs off to a Better Start: Conceptual Design


During the conceptual stage, engineers and designers rapidly explore and refine ideas. Design participants will engage in free-flowing collaborative brainstorming, exploring a range of design options—in the form of sketches, 2D drawings and layouts, and 3D models—until a final concept design is chosen. Concepts can be start out as designers sketching on paper, though eventually more realistic models need to be created to mimic the function, movement, and look of the real product.

The concept phase, however, isn’t simply a group of people ogling over highly stylized rendered images of concept designs. In many industries, like industrial equipment, aerospace and defense, etc., functional requirements outweigh the importance of aesthetics and styling. In these cases, the design team must take into account the functional requirements of the design (design intent), along with customer needs, manufacturability, environmental issues, and BOM cost issues. In some industries, such as high tech or consumer goods, the functional requirements may be secondary to styling issues, such as curved, sweeping surfaces.

Design intent is the intelligence that defines the fit and function requirements of the product. The ultimate success of the final product hinges upon design intent being captured early; encapsulated in the concept model and maintained throughout the design cycle—all without stifling creativity. Pie-in-the-sky concepts won’t hold up well during the mechanical design process when limiters like physics, mathematics, manufacturability, industry standards, and customer requirements come to bear.

One common mistake is focusing in on one concept too early in the process, often due to outside pressures (marketing demos needed for trade shows, consumer retail cycles, R&D budgets, and competitors).  The result is often bad design decisions, forcing designers, now committed to a concept, to work around complications as they rear their ugly heads throughout the rest of the development process.

In order to prevent such disasters, manufacturers need to really take their time during this crucial phase. Don’t narrow in on one concept too soon and assign multiple designers to flesh out multiple concepts concurrently. Then have several concepts detailed to the point at which the design team can determine with the highest level of confidence, which designs will work. After all, if a design isn’t going to fulfill its design requirements, this is the time to find out.

Tools of the Trade

To facilitate this iterative process, engineers must have the design tools that are very flexible as design concepts at this stage are fluid, changing often. Once created, proposed design concepts—whether in the form of sketches, 2D drawings or 3D models—must be reviewed by the extended design team and perhaps customers, and refined quickly based on their input.  Iterations should be constant at this stage so the design tools must be easy and intuitive enough to be used by non-CAD specialists as well. Often these tools may be different from the MCAD tools used during the detailed design phase.

When conceptual models are handed off to the engineering team and recreated in a MCAD system, not only does this lead to inefficiency in recreating what already exists, but often designs often change dramatically.  This misinterpretation of concept models is often caused by a communication gap between conceptual or industrial designers and the mechanical engineers tasked with creating the 3D CAD model on which the final product will be built. This disconnect between the design/styling team and the rest of the product development team often leads to loss of design intent as designs progress through the design cycle.

One way to mitigate this risk is to choose a suite of design tools that span both concept and detailed design stages. By offering bi-directional interoperability, these tools can reduce the risk of this communication gap and eliminate the need for engineers to reinterpret or re-create designers’ conceptual models, safeguarding design intent and facilitating the re-use of design data so mechanical engineers are not starting from scratch once concept models are approved.

When conceptual design tools and MCAD tools have interoperability with each other, mechanical engineers can simply bring approved sketches, drawings, even 3D concept models into their CAD software and then get to work further refining the model into a true 3D digital model or virtual prototype that can be ultimately designed, tested, and built.

lunes, 26 de septiembre de 2011

Creo 1.0 in the Multi-CAD, Multi-tool Workplace

The traditional multi-CAD experience

According to Aberdeen group, about 82% of you use multiple CAD tools in order to accommodate customers, suppliers, and other supply chain partners.  In fact, Aberdeen found many companies using up to 5 different CAD tools. Software vendors have worked hard to make a more interoperable environment for manufacturers. But the truth is, you can’t find one tool that will allow you to import, modify, and then incorporate your changes back to the original design. That’s because in a traditional parametric environment, you lose design intelligence when you export a model out of its native format.  The result is frustration, lost time as teams recreate models from scratch, and, well, a bunch of redundant CAD systems all under one roof.

The traditional multi-tool experience

Many engineers struggle with inflexible specialized tools too. You need your models to work with tools for electromechanical design, digital human modeling, associative tooling, etc.  As with incompatible CAD systems, when the specialized tools don’t work together you get lost time, redundant work, redundant tools, and frustration.

The Creo 1.0 experience

With Creo 1.0, you can move designs from one vendor’s system to PTC without having to start over again. You can launch the model in the Creo Direct App and make whatever changes you like without worrying about interdependencies. Behind the scenes, Creo 1.0 is applying your changes using a common data model that works in a parametric or direct environment. That means you can feely move imported models between Creo Direct and Creo Parametric, without ever losing design intelligence.

In fact, you don’t even have to use the direct app if you’re an expert parametric user. Creo 1.0 offers an extension, Creo Flexible Modeling Extension (FMX), that can give you direct-like capabilities in Creo Parametric.  So, load any model in Creo Parametric and modify it using FMX, as easily as if you were working with a direct modeler. In addition, Creo offers the broadest range of interoperable design, visualization, and illustration capabilities on the market. Plus, the Creo suite includes a huge range of tools in apps that all work together.  You won’t need to use redundant, incompatible tools to get your job done. And, since all the tools and apps are based on the same interface, you won’t have to learn a new tool for every job you perform. Working in a multi-CAD, multi-tool environment is just one process that gets easier when you can switch between parametric and direct modeling. I’ll tell you about several more in the weeks ahead.

miércoles, 14 de septiembre de 2011

Creo 1.0: Just the app’s mam: Creo View ECAD


Be it for communication, collaboration, inspection, or approval, providing visualization tools to all those involved in product development maximizes productivity, increases the opportunity to fix problems early, and leads to better products. And with Creo 1.0, we’re providing a broad range of viewing apps, including Creo View MCAD and Creo View ECAD, together with range of extensions to meet the broadest set of needs.

Now as a Mechanical Engineer (or spanner as we’d be called by the sparks), I’d normally focus on the MCAD viewing apps first, but Mark Caradonna, Product Manager at PTC,  insisted we discuss Creo View ECAD. [Ed-We’ll describe Creo View MCAD in a later article.]




GH: What is Creo View ECAD?

Caradonna: Creo View ECAD is a standalone viewing app for those who want to view, interrogate, and mark up ECAD data. It works out-of-the-box with the other Creo apps, but can also complement non-Creo environments as it can handle all common ECAD formats. For example, users can directly load Cadence .brd files or Mentor DxDesigner project files directly.

GH: Who would typically use Creo View ECAD?

Caradonna: As most products now include electronics, manufacturers see ECAD design just as critical as the mechanical design. But more than 50% of today’s electronic designs must be changed after prototype testing due to problems that were not identified and communicated, adding costly design spins. Companies want to ensure effective design reviews and achieve fewer design spins. Creo View ECAD allows users within engineering, design, fabrication, test and assembly to quickly verify electronic design content that was developed in the ECAD tools.

GH: Does each user have different needs?

Caradonna: Yes, but they’re served by one app. For example, for Electrical Engineers, Creo View ECAD can support design reviews for placement and routing, for Mechanical Engineers, it can provide a more accurate view of the ECAD design, for Manufacturing Engineers it provides a way to check designs earlier to make sure they can be manufactured.  For those in testing, it can be used to view and identify faults much quicker without needing to use paper plots.

GH: What are the highlights of Creo View ECAD?

Caradonna: Here’s what I’d say are the five highlights of Creo View ECAD:
  1. Consistent improved UI and user experience across all the Creo apps (easier to learn and use). Browse locally or via Windchill for schematic or physical PCB CAD databases, without using ECAD design tools, for library, schematic, PCB and BOM data
  2. Query one or many intelligent design data objects including component, pin and net attributes
  3. Follow net connectivity across the schematic to PCB by pin fx., (identify bad signal sources)
  4. Communicate changes, comments, or red-line data in multiple languages to the EDA tool user
  5. Cross-select components, keep in/out regions, and holes to and from the PCB Layout and the 3D mechanical view of the product (this requires Creo View MCAD or Creo Parametric)– so that you can view the areas of interest in both representations simultaneously.