Knowledge, Graphs & 3D CAD Systems - David Bigelow @ GraphConnect Chicago 2013

Post on 26-Jun-2015

772 views 1 download

Tags:

description

Global Design and Manufacturing Companies spend a lot of time looking in the rear-view mirror relative to their product design and configuration requirements in order to determine what NOT to do in the future. A lot of time and money is spent tracking information related to design validation, testing and warranty data. Understanding history is important, it often repeats and the bad decisions of the past needs to be avoided. But, what about the GOOD decisions that have been made, those are just as, if not more important to a design and configuration process! Where do those get stored?! How are they measured?! Most importantly, HOW ARE THEY ENFORCED?! Specifically, how do you help someone in a company make the RIGHT decisions, not just be fearful of repeating a BAD one?! This is a complex problem for any Design, Engineering or IT Department. That problem gets even more complex when you are required to incorporate a 3D CAD (Computer Aided Design) systems into the mix. If 3D parts and assemblies do not physically connect together properly, or are never supposed to work logically together based on the customer application, you will lose business. The solution is to rethink the approach to how a company not only captures knowledge about failures, but also start to capture successes. The ultimate goal is to help design and engineering staff make the right decisions first, to guide them through valid relations and requirements with ease so they are never distracted by bad decisions - or forced to address a potentially bad decision before it is made. This is where graph databases are poised to address a very complex problem in a simple and easy to understand way. There are two problems that come up from this: 1) how to document the relationships, rules, dependencies and logic in the graph structure, and 2) how to guide/navigate different role-specific-users through that process safely/accurately. This presentation will cover the real-world complexities of defining, validating, documenting and enforcing mechanical 3D CAD product configuration rules and structures. Demonstrations of how different roles within the company (e.g. configuration manager, engineer, sales, etc.) can interface with the same graph database using multiple interfaces (e.g. thick client, thin and web) to be interactively guided to a proper solution the first time.

Transcript of Knowledge, Graphs & 3D CAD Systems - David Bigelow @ GraphConnect Chicago 2013

Innovate. Share. Connect.Chicago June 12-13

Knowledge, Graphs & 3D CAD SystemsKnowledge, Graphs & 3D CAD SystemsDavid Bigelow - Simplified Logic, Inc.David Bigelow - Simplified Logic, Inc.

Graphs

Image Source: neosigma.herokuapp.com Example: neo4j & sigma.js

Relationships are Cool...(But, are hard to get your head around)

Image Source: Max DeMarzi

Visualization HAS gotten better...(for simple cases)

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

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?

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!)

character credit: SouthPark.com - “underwear gnomes”

There has been an extreme focus oncollecting and controlling data...

(ummm.... “Phase 2” is like really important!)

You want to do amazing things?!

Figure out that “Phase 2” part out! (quickly)

graphic credit: SouthPark.com - “underwear gnomes”

3D CAD Systems

CAD Systems and Types(user-centric approach to execution)

Wireframe Surfaces Solids

Parametric

Modelers

10mm17mm

Variational

Modelers

DirectModeler

s

(pull)

Parametric Systems (hierarchical relationships)

ProductData 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

FilesPointers & Relationships

Feature Relationships

A

Q

R

S

T

U

V

W

Bu

ild O

rder

Parent

Child

Part Features & Operations

A

Q

R

S

T

U

V

W

Bu

ild O

rder

Part Features & Operations

Structuraland / or

GeometricDependent

Relationships

Relationships

NOTE: This is Painful for Users!

Multiple Paths / Frustrationsto the SAME Geometric

Results!

Part Design Automation(graphs can help navigate data, but not great for automating)

Feature Instructions are typically defined to a

smallreference.

The Resulting Geometry often is more complicated

than the instructions used to create it.

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

e11e12

e7

e8

e12=3D Cube

Graph-Based Extraction(Define Boundary Conditions and Seed Reference)

Boundary

Boundary

Seed

ExtractedGeometry

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!)

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!

THIS is a BIG PROBLEM!

EXPENSIVE, COMPLEX & PROPRIETARYData Management Systems

Multiple Use-Cases for theSAME DATA

(Manufacturing, Vendors, Customer, Publishing, ERP, etc.)

Sharing & Using Informationwith others is PAINFUL!

Embedded CAD Relationships

A

C

A

Z

D

E

F

B

Breaking those Internal

Relationships NOT

this easy...

A

C

AZ

D

E

F

B

Result:YEARS of bad

decisions persist!

Autonomy is CRUCIAL!

A

Q

R

S

T

U

V

W

Bu

ild O

rder

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

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

“Choices” are a Problem...(Should you just let anyone put anything together?!)

Image Source: The Matrix Reloaded

Just because you can...

Doesn’t mean you SHOULD!

Graphs &Business Logic

Imagine youproduce this...

0˚ 30˚45˚

60˚

-30˚0˚30˚

45˚60˚

0˚30˚

60˚ 90˚ 115˚

0˚30˚

60˚90˚115˚

Product Data Managers“manage” the Data...

But this is NOT how it should be used.

A Decision Framework!

What is missing?

This is a “Decision Framework”

3-Ring Binders!Excel Worksheets!

+

BUT... NOT VERY USEFUL!

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

Internal Memos

Warranty Info

Test Data

source: ibm.com

source: spacesaver.com

Design Standards

Customer Feedback

Competitive Analysis

Product Design & Configuration KnowledgeComes from MANY Sources

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, Different Sources, Different

This is where most I.T. Departmentsseriously struggle!

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”

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!

Different Roles- Engineering

- Manufacturing- Purchasing- Customer- Partners-Vendor

- etc.

Different Targets- Region- Market- Cost

- Market- Application

- etc.

Interfaces! Role-SpecificDecision

Structures- Engineering

- Manufacturing- Purchasing- Customer- Partners- Vendor

- etc.

0˚ 30˚45˚

60˚

-30˚0˚30˚

45˚60˚

0˚30˚

60˚ 90˚ 115˚

0˚30˚

60˚90˚115˚

Engineering Customers

Partners

VendorsApp Support

Manufacturing

DEMO

IndustryOpportunities...

A lot of companies are sold a “vision”

“Heeeey....Just put

everything in a single bucket!”

The Core Problem...

Customers Expect... Vendors Supply...

A small piece of advice... ALWAYS ASK:“Who” is the cutter and “who” is the dough?!

CRAP!CRAP!

Welcome to the NEW Variable...

THANK YOU!

simplifiedlogic.com : Engineering & Consulting

nitrolm.com : Cloud Licensingbusinessmodeling.com : A New

Project :)

David Bigelow, PresidentSimplified Logic, Inc.

MileTrackGPS.com : Investor