1 / 105

Evaluating SolidWorks Automation Options

Evaluating SolidWorks Automation Options. Albert J. Pristera Albert J. Pristera & Assoc. Intro.

camden-hart
Download Presentation

Evaluating SolidWorks Automation Options

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Evaluating SolidWorks Automation Options Albert J. Pristera Albert J. Pristera & Assoc.

  2. Intro Engineering departments continually aim to reduce the design cycle. SolidWorks automation software significantly speeds the process, but its implementation can be complex, costly or even inadequate. This presentation will discuss the pros and cons of SolidWorks automation in general and those of specific tools (Knowledge Based Engineering and Configurator software).

  3. Presentation Abstract • Presentation will examine what types of projects make good automation candidates, how to define the automation goals, and how design philosophy must change to fit automation. These concepts will be supported through a case study showing development of a SolidWorks weldment model. DriveWorks, KBMax, Macros, and Rulestream will be analyzed as automation methods for this model. Presentation will evaluate positive and negative features of each solution based on experience.

  4. Bio • Over four decades in machining and mechanical engineering at companies like US Steel, Snap-tite Solenoid Valves, and Moyno Industrial pumps. • Developed and maintained “home grown” automation system utilizing Microsoft Access and Pro/Program before working with outside software like DriveWorks, KBMax, and Rulestream • Rather be fishing with grandsons

  5. Bio Condensed version • Been around a while • Done a lot of different things • Rather be fishing with the Grandsons www.alpristera.com http://dagrump.blogspot.com/

  6. Flavors of Automation • 2 Basic Flavors of Design Automation • Individual automation • Short cuts, tricks, hot keys, start parts, what you as an individual do to make your job easier • Project Automation • Collaboration of different disciplines to improve entire business model. • Some of the topics we will cover apply to both catagories

  7. As individuals we find ways to help ourselves work easier faster better. • When we have to collaborate is when to process gets complicated. • This is where KBE software comes into play

  8. Definitions • Create-KBMax term for the rule writer • Architect – Rulestream term for the rule writer • Configure -KBMax term for the output generator • Engineer - Rulestream term for the output generator • Data- dimensions, spreadsheets, Db tables etc • Rules- anything that manipulates data • Program statements, excel formulae, Solidworks equations etc AKA “Code” • VB -Visual Basic

  9. What should I automate? • What makes sense? • Pain Points • Frequency • Tedious • Tribal Knowledge • Consistency • Pass the Buck

  10. What Can I Automate • Can you flow chart the process? • What does the flowchart look like?

  11. Like this? Automate!

  12. Or Like this?

  13. RECONSIDER YOUR OPTIONS • Planning and designing for automation is an opportunity to evaluate your processes. • Note the connection to Area 51 • Identifying these areas early in the process decreases implementation pain significantly. • Get your processes in order • The law of unintended consequences

  14. Which is cheaper? Purchase Channel Purchase Pre Fab

  15. DESIGN

  16. Design for Automation • Set Standards • Where is the front, side, top? • Create start templates • Properties • Primitive geometry (planes, axies) • Evaluate existing model geometry • Re-orient • Connect to primitives • Leverage relations & equations • KISS

  17. PLAN

  18. Plan for automation • Start with a project champion • Has the authority to assign tasks & priorities • Can finalize decisions • Define the goal and document it • Set bench marks • Small bites and test/demo • What is agreed upon in a meeting isn’t what is desired. • Pay special attention to purchased items. • Consider effects of changes to vendors products

  19. Rules Capturing data from the knowledge source

  20. Remember this?

  21. Gear up, we’re going in • Rule writers tool kit • Notepad ++ www.notepad-plus-plus.org • VB References • Database & Excel references • The Little Book of Rules by Ian Yates (Driveworks)

  22. Rule & Data Extraction Tools

  23. Collect the Stuff • Some Advice about rule & data collection. • Take ownership of data only when you are the owner • Take ownership of rules only when you are the owner • Use your champion • Document everything • Beta test • Input • Output • You WILL become the excuse • Eschew obfuscation • Focus on critical not pretty(that comes later)

  24. The Premise • We are in the business of building a frame and the component that fits in it. • We also have other products that may or may not be marketed in conjunction with this frame • All four possible solutions yield acceptable Cad output

  25. This is the sample project

  26. Weldment Drawing

  27. Why? • Design choices are linear • Long manual design cycle • Only one designer has experience • AREA 51 • Design has significant cost implications

  28. The task

  29. The prospective solutions * • Write a macro to capture the design • Use DriveWorks Express to capture the design • Use a KBE tool • Rulestream • KBMax • * These are what I have used on projects.

  30. And in this corner • Macro www.solidworks.com • Driveworks Xpress www.driveworks.co.uk • Rulestreamwww.plm.automation.siemens.com • KBMax www.citiuscorporation.com

  31. MACRO • Uses VB like language • Embedded in SWx • Works well in a “Master Model” * • Assembling components into an empty template is challenging • “Reads” SWx by recording *Where the model is in an open Solidworks session

  32. DriveWorks Express • Uses excel language • Embedded in SWx • Works well in a “Master Model” • Captures and links directly to SWx dimensions & properties • Uses GUI for capture & programming

  33. Rulestream • Uses Visual Basic like language • Captures Swx dimensions & properties • Databased system • Anchored to data server • Uses GUI for capture (kinda) & programming

  34. KBMax • Uses Visual Basic language • Captures and links directly to Swx dimensions & properties • File based system (transportable) • Light weight • Can directly access external data in multiple formats • Uses GUI for capture & programming

  35. Interfaces

  36. Macro Push a Button

  37. DriveWorks Express

  38. Rulestream

  39. KBMax

  40. Capture Capturing data from the model

  41. Macro Push a Button Do Something Push a Button

  42. DriveWorks Express

  43. Rulestream

  44. Rulestream

  45. Rulestream

  46. Rulestream

  47. KBMax Capture

More Related