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 Pre Fab Purchase Channel

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 HHas the authority to assign tasks & priorities CCan finalize decisions Define the goal and document it SSet bench marks Small bites and test/demo WWhat is agreed upon in a meeting isn’t what is desired. Pay special attention to purchased items. CConsider effects of changes to vendors products

21. Rules Capturing data from the knowledge source

22. Remember this?

23. 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)

25. Rule & Data Extraction Tools

26. 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)

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

28. This is the sample project

29. Weldment Drawing

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

31. The task

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

33. And in this corner Macro www.solidworks.comwww.solidworks.com Driveworks Xpress www.driveworks.co.ukwww.driveworks.co.uk Rulestream www.plm.automation.siemens.comwww.plm.automation.siemens.com KBMax www.citiuscorporation.comwww.citiuscorporation.com

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

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

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

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

38. Interfaces

39. Macro Push a Button

40. DriveWorks Express

41. Rulestream

42. KBMax

43. Capture Capturing data from the model

44. Macro Push a Button Do Something Push a Button

45. DriveWorks Express

46. Rulestream

50. KBMax Capture

51. Input Interface Capturing data from the human

52. Run time display Macro  What was created in code Driveworks Express  Auto generated form Rulestream  Auto generated form  Can be customized KBMax  Auto generated form  Can be customized

53. Macro Write Code

54. DriveWorks Express

56. Rulestream

58. 3 screens later

59. Rulestream

60. KBMax

61. Rule Manipulation How do I write code?

62. Macro Write More Code

63. DriveWork Express

64. Rulestream

65. KBMax

66. Non Cad Output Quotes, BOM, Work Instructions, etc.

67. Working with Non Cad Documents Macros  Probably not a good idea…….going to get VERY complicated Driveworks Express  Not a good idea. Not even sure it can be done. If you need non-cad documents as part of your automation, you will need to go to the KBE tools. So How do KBE tools handle non cad documents?  This is the biggest difference between the two KBE tools we are analyzing.  This can be a deal breaker.  Worse, it can wreck an implementation

68. Rulestream Report Generator Rulestream uses an add on it calls the report generator. It functions like a VB Form.

69. Rulestream Report Generator

75. KBMax Output Documents KBMax captures & links directly Microsoft Word & Excel fields.

76. KBMax Output Documents You can create and format the look you want in Word or Excel, use one of the furnished templates, or download a template from the internet.

77. KBMax Output Documents

80. Putting it Together

81. Driveworks Express Capture

82. ` Driveworks Express Results

83. KBMax Capture & Results

84. What does all of this mean to me How do I decide?

85. Software Cost 0 $$ $$$$ $$$$$$$$ Macro Drv Wks Express Rulestream KBMax

86. Infrastructure Cost 0 $$ $$$$ $$$$$$$$ Macro Drv Wks Express Rulestream KBMax

87. Programming Experience Novice Some More Code Guru Macro Drv Wks Express Rulestream KBMax

88. Time to First Beta Days Weeks Months Years Macro Drv Wks Express Rulestream KBMax

89. Extensibility Code & Rule Reuse Connect to other models/products Extend Beyond One product Connect to non cad data Portability

90. Extensability Not Some More Very Macro Drv Wks Express Rulestream KBMax

91. Extensiability Macro requires extensive programming to go ouside of itself Express can only call one model at a time Rulestream is tied to a “product control model” KBMax has the ability to call configurators from within a configurator aka “Nesting”

92. Cross CAD platforms This is Solidworks World 2011 HEY !!!!

93. OK, Legacy Cad 0 2 3 More Macro Drv Wks Express Rulestream KBMax

94. Non Cad Documents Don’t Maybe Smooth Rough Macro Drv Wks Express Rulestream KBMax

95. Why KBE Why Bother

96. Why? KBE tools have two components  Creator & User This puts the engineering “rules” in the hands of non engineers Captures true cost Allows cost to be part of the decision process

97. Which is cheaper? Purchase Pre Fab Purchase Channel

98. Conventional Wisdom Said

99. So We Want 6 8 10 12 15 18 Channel Bases

100. Wait a minute 15 & 18 are not common so they are actually $$$$$$ OK Don’t use them

101. Wait a minute Holes cost $$$$$$

102. When the Dust settled Purchase Pre Fab Purchase Channel

103. Other Benefits Generate Non Cad documents  Quotes, letters, BOM’s Access to external data sources  Databases, spreadsheets Feeds external systems  PDM, ERP, MRP

104. KBMax

105. Questions www.alpristera.com http://dagrump.blogspot.com/