Knowledge, Graphs & 3D CAD Systems - David Bigelow @ GraphConnect Chicago 2013
Download as PPT, PDF3 likes2,343 views
The document discusses the challenges and complexities of managing data in the context of knowledge graphs and 3D CAD systems, emphasizing the importance of actionable data for decision-making. It highlights the pain points faced by users in navigating relationships within CAD systems and the need for better data management solutions. Additionally, it encourages the development of tailored decision frameworks that address varying roles and needs within organizations.
Knowledge, Graphs & 3D CAD Systems - David Bigelow @ GraphConnect Chicago 2013
- 1. Innovate. Share. Connect. Chicago June 12-13 Knowledge, Graphs & 3D CAD SystemsKnowledge, Graphs & 3D CAD Systems David Bigelow - Simplified Logic, Inc.David Bigelow - Simplified Logic, Inc.
- 2. Graphs
- 3. Image Source: neosigma.herokuapp.com Example: neo4j & sigma.js Relationships are Cool... (But, are hard to get your head around)
- 4. Image Source: Max DeMarzi Visualization HAS gotten better... (for simple cases)
- 5. But still has a LOOOOOONG way to go... (Huh?! Is this useful to the average person who is not a social or criminal scientist!?) Image Source: gephi.org
- 6. Most Visualization looks exclusively in the PAST! (The future starts by staring into the rear-view mirror?!) Closeness of Data Points? Clustering? Connection Counts? Overall Ranking? Correlation? Causation? Trending? Where used? Degree of Centrality?
- 7. Historical Data drives future decisions, policies, and agendas! BUT, it is typically not actionable in a timely manner. (The “Big Data” Problem!?) History is important! (ok... duh!)
- 8. character credit: SouthPark.com - “underwear gnomes” There has been an extreme focus on collecting and controlling data... (ummm.... “Phase 2” is like really important!)
- 9. You want to do amazing things?! Figure out that “Phase 2” part out! (quickly) graphic credit: SouthPark.com - “underwear gnomes”
- 10. 3D CAD Systems
- 11. CAD Systems and Types (user-centric approach to execution) Wireframe Surfaces Solids Parametric Modelers 10mm 17mm Variational Modelers Direct Modelers (pull)
- 12. Parametric Systems (hierarchical relationships) Product Data ManagerDrawings A X C D Parts A Q R S T U V W Assemblies A B C A Z D E F A C B D E F X Files Pointers & Relationships
- 13. Feature Relationships A Q R S T U V W BuildOrder Parent Child Part Features & Operations
- 14. A Q R S T U V W BuildOrder Part Features & Operations Structural and / or Geometric Dependent Relationships Relationships NOTE: This is Painful for Users! Multiple Paths / Frustrations to the SAME Geometric Results!
- 15. Part Design Automation (graphs can help navigate data, but not great for automating) Feature Instructions are typically defined to a small reference. The Resulting Geometry often is more complicated than the instructions used to create it.
- 16. S4 S5 S2S1 S3 S6 Sub-Geometry Relationships (Solid / Volume = Closed Loop Relationships) (Surfaces & Edges) e3 e1 e2 e4 e5 e5 e6 e6 e7 e8 e9 e9 e10 e10 e11 e12 e7 e8 e12 = 3D Cube
- 17. Graph-Based Extraction (Define Boundary Conditions and Seed Reference) Boundary Boundary Seed Extracted Geometry
- 18. A B C A Z D E F Assemblies Parts Feature User-Specific Approach Item Choices... Mated To, Aligned To, Selected References, etc... Assembly Relationships (business logic IN the CAD system!) NOTE: This is Painful for Users! ALSO - Painful for Corporation (data management!)
- 19. A B C A Z D E F Component “C” w/ Assembly References to Assembly “E” and Sub-Component “B” Sub-Assembly “F” Assembled to Component “C” Assembly Relationships NOTE: ALL relationships must be understood by the product data management system!
- 20. THIS is a BIG PROBLEM! EXPENSIVE, COMPLEX & PROPRIETARY Data Management Systems Multiple Use-Cases for the SAME DATA (Manufacturing, Vendors, Customer, Publishing, ERP, etc.) Sharing & Using Information with others is PAINFUL! Embedded CAD Relationships A C A Z D E F B
- 21. Breaking those Internal Relationships NOT this easy... A C AZ D E F B Result: YEARS of bad decisions persist!
- 22. Autonomy is CRUCIAL! A Q R S T U V W BuildOrder Un-Avoidable (user / user pain) Part Design A B C A Z D E F Typical (user / user / corp pain) Assembly Design A B C A Z D E F Well-Planned (flexible / enforceable) Assembly Design
- 23. Design Alternatives?! Product Design A1 A2 A3 A4 B1 B2 C1 C2 C3 C4 C5 E1 E2 E3 F1 F2 F3 F4 F5 F6 A1 A2 A3 A4 Z1 Z2 Design Alternatives A B C A Z D E F
- 24. “Choices” are a Problem... (Should you just let anyone put anything together?!) Image Source: The Matrix Reloaded
- 25. Just because you can... Doesn’t mean you SHOULD!
- 28. 0˚ 30˚ 45˚ 60˚ -30˚0˚ 30˚ 45˚ 60˚ 0˚ 30˚ 60˚ 90˚ 115˚ 0˚ 30˚ 60˚90˚115˚
- 29. Product Data Managers “manage” the Data... But this is NOT how it should be used.
- 32. This is a “Decision Framework” 3-Ring Binders!Excel Worksheets! + BUT... NOT VERY USEFUL!
- 33. Human “mobility” is a BIG problem... Typically, the “data” stays... (PDM, PLM, Excel Worksheets, Paper Notebooks, etc.) I am out’a here!Promo! The “new people” in a job are a huge variable... Newbie! (aggressiveness, competence, courage, communication skills, real-world experience vs. book smarts, etc...)
- 34. Internal Memos Warranty Info Test Data source: ibm.com source: spacesaver.com Design Standards Customer Feedback Competitive Analysis Product Design & Configuration Knowledge Comes from MANY Sources
- 35. Different Sources, Different Databases, Different Users, Different Applications, Different Use Cases, Different Customers, Different Needs, Different Life Cycles, Different Security, Different Sources, Different Databases, Different Users, Different Applications, Different Use Cases, Different Customers, Different Needs, Different Life Cycles, Different Security, This is where most I.T. Departments seriously struggle!
- 36. Let Purpose-Built Solutions Work! You can build an amazing Decision Framework from this... But, information arrives and changes at different times... Your NEW “Decision Structure”
- 37. Your NEW “Decision Structure” Services Services Services Services Services The Graph does NOT need “everything”... Connect them via “services” to... “Translate”, “Relate” and “Guide” the Business Process!
- 38. Different Roles - Engineering - Manufacturing - Purchasing - Customer - Partners -Vendor - etc. Different Targets - Region - Market - Cost - Market - Application - etc.
- 39. Interfaces! Role-Specific Decision Structures - Engineering - Manufacturing - Purchasing - Customer - Partners - Vendor - etc.
- 40. 0˚ 30˚ 45˚ 60˚ -30˚0˚ 30˚ 45˚ 60˚ 0˚ 30˚ 60˚ 90˚ 115˚ 0˚ 30˚ 60˚90˚115˚
- 43. DEMO
- 45. A lot of companies are sold a “vision” “Heeeey.... Just put everything in a single bucket!”
- 46. The Core Problem... Customers Expect... Vendors Supply... A small piece of advice... ALWAYS ASK: “Who” is the cutter and “who” is the dough?!
- 47. CRAP!CRAP!
- 48. Welcome to the NEW Variable...
- 49. THANKYOU! simplifiedlogic.com : Engineering & Consulting nitrolm.com : Cloud Licensing businessmodeling.com : A New Project :) David Bigelow, President Simplified Logic, Inc. MileTrackGPS.com : Investor