NX Knowledge Based solutions

2003. 8. 23.이주호

EDS PLM Solutions Korea

1

Technology ProgressionTechnology Progression

Data Mgmt Process Mgmt Collaboration Knowledge

Drawing Based Feature Based Process Based Knowledge Based

User Group Department Enterprise

74 0388 95 99

Digital D

rawings

SolidsFeaturesVisualizationMaster Model

Digital M

odels

Auto threadsAero threadsConsumer ProductsMachinery

Digital P

rocesses

Process WizardsOptimizationRule based modelingWAVE

Predictive

Engineering

Pervasive knowledgeKBE languageKnowledge checkersExpert applicationsAutomation

Knowledge

Management

File-based datamanagement

VaultingApplicationEncapsulation

Product Structure ManagementConfigurationManagement

Change mgmtSecurity

CAx IntegrationsERP/MRP IntegrationsVariant Management

VisualizationMulti-SiteRDV

2

Technology ProgressionTechnology Progression

Data Mgmt Process Mgmt Collaboration Knowledge

Drawing Based Feature Based Process Based Knowledge Based

User Group Department Enterprise

74 0388 95 99

Digital D

rawings

SolidsFeaturesVisualizationMaster Model

Digital M

odels

Auto threadsAero threadsConsumer ProductsMachinery

Digital P

rocesses

Process WizardsOptimizationRule based modelingWAVE

Predictive

Engineering

Pervasive knowledgeKBE languageKnowledge checkersExpert applicationsAutomation

Knowledge

Management

File-based datamanagement

VaultingApplicationEncapsulation

Product Structure ManagementConfigurationManagement

Change mgmtSecurity

CAx IntegrationsERP/MRP IntegrationsVariant Management

VisualizationMulti-SiteRDV

Automated Processes and best practices

Technology

Technology in the 21st century is going to be less about discovering new phenomena and more about putting known things together with greater imagination and efficiency

3

What IS KBE?What IS KBE?

Knowledge Based Engineering (Design Focused)

The concept of “Knowledge Based Engineering” is a very broad one. The basic idea is to find ways of recording different kinds of knowledge about how to engineer, design, and configure a productin a way that allows it to be easily found, understood, reused, and maintained.

• A KBE language is one of many kinds of tools that can be used to help achieve this. A KBE language allows knowledge to be captured in the form of “rules”: statements written in the language.

• These knowledge bases can exist in many forms such as:

– Spread sheets

– Hand books

– Engineering formulas

– Data Bases (Knowledge Pipeline is key to accessing)

4

Why Is KBE Needed?Why Is KBE Needed?

•With customer requirements as input, manufacturing companies are engaged in the process of design, development and manufacturing of products. The customer requirements are translated to performance criteria and cost. This process of design to manufacturing is a complex process, which is time-consuming, requires high skills and is also expensive. Manufacturers continue to invest in technology, consulting and services to improve the process, but engineers continue to face the following questions:

•Sets the rationale behind this design

•How do we ensures design constraints have not been violated

•How can we Ensure parts meet performance goals

5

What Is KDA?What Is KDA?

Knowledge Driven Automation (Product & Process Focused)•Capturing knowledge, adopting best practices and providing automation of design and manufacturing processes.

Weld AssistantProgressive Die Wizard

Mold Wizard

6

Why Is KDA Needed?Why Is KDA Needed?

•This is required in order to allow manufacturers to automate their engineering and manufacturing processes capturing the design rules, experience and

expertise residing in the organizations and leveraging it during new product development.

(The Value)–Free Engineers from repetitive tasks

–Capture and enforce company best practices.

–Allow "what-if" scenario's during the sales cycle

–Achieve process standardization

–Development of custom and proprietary applications or wizards.

Frame layout

Fixtures

Components

Manufacturing

FEA

Design Design Layout Layout

Modeling Modeling ComponentsComponents

Surface Surface ModelingModeling

Fixture DesignFixture Design ManufacturingManufacturingFEAFEA

UI styler

Reduce Time

7

Knowledge Driven Automation Can Involve…

Sales AutomationSales AutomationCustom Engineered Proposal Drawings

Automated Proposals, Quotations

Pricing Logic, ERP integration

Automated emails, reports, etc….

WEB Based so direct sales, reps and customers can use!

Manufacturing AutomationManufacturing AutomationAssembly & Machining Fixtures

Routings/Work Cell Selection/OP Sheets

Inspection Documents/Scheduling

Machine, Tool & Fixture Design

Engineering AutomationEngineering Automation- Drawings, 2D & 3D Wireframe

- Solid Models & Assemblies

- BOMs, Schematics, Documentation, Reports

- Automated FEA (thermal & structural)

- Overall Systems Integration and Automation

8

Broad ApplicabilityBroad Applicability

Part Design Acceleration and

Optimization

Knowledge-Driven Process Automation

Knowledge-Driven Modular Assembly Configuration

Novel Types

of Analysis

Best Practices Capture and Enforcement

Web-Based Product Configuratorsor other Interfaces

9

Unigraphics NX Provides The Tools for Capturing Product & Process Knowledge

(A Family of Product Definition Tools)Process Wizards

Knowledge FusionCustom User Interface

WAVE – Parametric Assemblies

UDF – User Defined Features

Spreadsheet Driven Models

CAD Software

Parasolid

Direct Modeling

Machining / Process Quality CheckersTemplates

Integrated Simulation and Verification (ISV) CAM

2002 X-5309

10

What is Knowledge Fusion? What is Knowledge Fusion?

(The Technology)

•A unique capability that blends the power of rules based automation with the utility of high-end MCAD

–An object-oriented environment for Knowledge capture and re-use

–A KBE language which is now part of the NX architecture

A unique capability that blends the power of Knowledge Based Engineering with the utility of high-end mechanical CAD

1. Create geometry2. Add “rules” (constraints)3. Evaluate and modify

1. Capture knowledge (rules)2. Evaluate against new criteria3. Create Geometry

Engineering

NXNX

Process

Tools

Design

11

Strength and Weakness of Traditional CAD and Program LanguageStrength and Weakness of Traditional CAD and Program Language

• Traditional CAD

– Strength• Graphical interaction• Creation of complex parametric features• Managing feature relationships and modeling history

– Weakness• Limited representation of design intent• Design rationale not captured• Limited “what if” capabilities.

• Program language– Strength

• Rules are easily captured and expressed in the language• Declarative versus procedural

– Weakness• Difficult to express complex geometric features in textual format• Difficult to represent the design purely textually and be independent

of the evaluated model --- needs “language binding to the part file”• Problems implicit in any programming language

12

CAD And KF IntegrationCAD And KF Integration

Take full advantage of both CAD and KF strengths

Permit users to focus on what must be expressed in the KBE language rather than being concerned with completely specifying every design detail

Allow user to change the model both interactively and in the KBE language without invalidating either representation - Both views of the model are always in synch

Enable users to extend the UG data model by easily creating intelligent, custom modeling features

Unigraphics NX with its embedded KF supports the Generative approach PTC with its “Behavioral Modeling” cannot provide this approach

Process:1. Create geometry2. Add “rules” (constraints)3 . Evaluate and modify

Process:1. Capture knowledge (rules)2. Evaluate against new criteria3 . Create Geometry

Designer - Variational(Variational)

Engineer - Generative(Generative)

13

KF Key Differentiators KF Key Differentiators

Protect customer proprietary knowledge

• Capture knowledge in Rule file (ASCII format)• Capture knowledge in Part file (binary DFA format)• Capture knowledge in KF Feature• Capture knowledge in customer specific DLLs• Control knowledge files and versions via Teamcenter Engineering• Breadth of geometric coverage

UG/KF has very rich classes for geometries and has classes for adding single tier components and creating expressions -capabilities not available in other KBE systems.

• UF/KF make actual UG modeling featuresNot just simple primitives.

• UG/KF supports bi-directional editingUG/KF created objects can be edited and relevant rules re-fired

by editing appropriate expressions from the Expression Editor or via UG/Open calls.

UGNX customers have full control of their proprietary technology

14

KF Key DifferentiatorsKF Key DifferentiatorsUnigraphics features

• User Defined Features are created using Unigraphics’rich set of modeling tools to create complex models.

• The existing UG parts can also be re-used.

• RPO - It’s big benefit already for conventional UDF, also same for knowledge enabled UDF.

• UG/KF adoption exposes all important parameters as attributes for the UDF class

• Use rules to control the selection/swapping of UDF• Use rules to control the positioning of UDF• Use Nested UDF• Programmatically swap UDF and dynamically

configure topology of the UDF

User Defined Feature in UG/Knowledge Fusion

(Child) BLOCK: { Class; ug_block; Length;0.5;Width;2;Height;6;Origin;Point(0,0,0);X_Axis;Vector(1,0,0);Y_Axis;Vector(0,1,0);Operation;Unite;Target;{};Suppress?;FALSE; };

(Child) CYLINDER: { Class; ug_cylinder; Diameter;3;Height;0.5;Origin;Point(3,1.5,3);Direction;Vector(0,1,0);Operation;Unite;Target;{};

Suppress?;FALSE; };

Knowledge Fusion Language

Adoption

15

Why Knowledge Fusion Not API?Why Knowledge Fusion Not API?

What is the difference between API and KF?

Overly complex systems

Systems that are hard to use (often times the system creator is the

only one who can use it.)

Complex architectures with lots of external, “dongled” applets and

applications.

Expensive and long programming efforts

The inability to fully automate many tasks

High Maintenance costs & System re-writes

16

KF versus C++ Example KF versus C++ Example UI styler

• UG/Open API

– Create Dialog Callbacks

– Creation Code

– Edit Dialog Callbacks

– Editing Code

– Toolbar Callbacks

– 6500 lines of C code

– 2 dialogs

– 1 toolbar for icons

– ~3 months

• Knowledge Fusion

– Creation Code

– (reused for edit)

– (No UI-specific code)

– (No toolbar code)

– 320 lines of KF code

– 1 create/edit dialog

– 1 toolbar for icons

– ~3 days

17

KF And Data Management Integration KF And Data Management Integration

Tightly integrated with Teamcenter Engineering

Description:• Versioning• Browsing existing classes• Where used• Add read/write controls at rule level

Benefits:• Use of Teamcenter Engineering to control the

release procedures of these KF files • Knowledge capture from the Database • Handling of Knowledge fusion files made

easy

18

Knowledge Fusion – top ten reasons

1. Integrated architecture provides major performance boost (over external KBE systems)

2. Application flexibility (vs. sequential languages)

3. Ability to create object oriented systems

4. Rule-based assembly configuration

5. Integrated Database lookup, ODBC connections during update

6. Integrated optimization during update

7. Integrated CAE during update

8. Simple GUI creation for models and/or rules

9. Integrated PDM control of rules and models

10.The value of KBE is best realized when deeply integrated intoMCAD and fully compatible with PLM

CASE Study 1 : Knowledge Driven Airframe DesignCASE Study 1 : Knowledge Driven Airframe Design

Conceptual Design

Manufacturing & Assembly

Detailed Design

OrderOrder

Approved ConceptApproved Concept

Controls &Controls &AccessoriesAccessories

Advanced DesignAdvanced Design

LoftingLofting Subsystems &Subsystems &Part DesignPart Design

AnalysisAnalysis

?1

BaseConfigBaseBaseBase

ConfigConfigConfigOptionsOptionsOptionsOptionsCommon PlatformCommon PlatformCommon PlatformCommon Platform

Evaluate Multiple ConfigurationsEvaluate Multiple Configurations?2 ?3

ConfigConfigModelingModeling

StructuralStructuralPartsParts

Save 4-5 monthsSave 4-5 months

Review & managedesign variantsReview & managedesign variants Evaluate alternatives ...Evaluate alternatives ...

Solid modelsSolid models Reduce physical mockupsReduce physical mockups

Subsystems 4 to 10x fasterSubsystems 4 to 10x fasterreduce physical mockupsreduce physical mockups

Faster Program kick-offFaster Program kick-off

Aircraft ConfiguratorConfiguration StudiesConfiguration Studies

Capture Configuration Rules

Composites/Composites/Sheet MetalSheet Metal

Quality &Quality &InspectionInspection

FabricationFabricationCable Routing/Cable Routing/TubingTubing

Mfg. Mfg. SimulationSimulation

Capture mfg. intent during designCapture mfg. intent during design Reduce die design and die try-outReduce die design and die try-out

4x to 10x more productive4x to 10x more productive

ApplyApplyCM RulesCM Rules

ToolingTooling

from weeks to daysfrom weeks to days

20

Example: Cross beam packaging wizardExample: Cross beam packaging wizardTasks for automation: stringer

Analyze existing technology

21

Cross beam packaging wizardCross beam packaging wizardTask formalizationThe rule to set up profile on surface

Cross section of stringer and surface

Stringer axis

Wall parallel to derectionWall normal to surface

22

Cross beam packaging wizardCross beam packaging wizardWizard efficiency

40

Efficiency

~33 h

20 min

Common technology

~1 hSet up 100

0.5 minSet up of 1 cross-beam

KF

Development time- 2 days

23

Inheritance in Knowledge fusionInheritance in Knowledge fusionInheritance of defined classes

Class from Rib Wizard

Wing Wizard

Class from Stringer WizardDefClass: stringer (ug_base_part);

(string parameter) type: “000.01”;

(number parameter) shema: 1;

(Child) s_type: {Class; type_234NASA;

};

DefClass: wing (ug_base_part);

(string parameter) type_of_wing: “direct”;

(number parameter) shema: 1;

(Child) beam1: {Class; stringer;}

(Child) beam2: {Class; stringer;}

DefClass: new_wing (ug_base_part);

(number parameter) schema: 5;

(string parameter) surface: str10.01;

(Child) wing_01: {Class; wing;

type_of_wing;”wing_angle”;

}

24

CASE Study 2 :Build-To-Order CASE Study 2 :Build-To-Order

DELL has replaced it’s traditional “vertical integration with virtual integration” by developing a high-velocity direct “Configure-To-Order” technology to achieve new levels of automation. This is a “Build-To-Order” example.

•Price for Performance

•Customization

•Service and Support

•Latest Technology

•Superior Shareholder Value

Dell gained enough market share last year (from 12 to 15 percent) to become the number-one company in the business. At a time when every one of its major competitors is losing money in PCs, Dell is making it, keeping margins flat while waging a price war that's destroying its rivals.

This is a Vision of business value “DELL is not a customer”

25

Knowledge Based SolutionsKnowledge Based Solutions

NX with its embedded Knowledge tools in combination with Teamcenter offers companies the opportunity to automate processes and manage digitized information.

Unigraphics NX•More than two-thirds of the typical engineering process involves routine tasks. •70% of a product's definition is often non-geometric

Teamcenter

26

Technology Map – Web based demoTechnology Map – Web based demo

Teamcenter Engineering Database

Knowledge ToolsUnigraphics NX

Application Server

Login

LoginConfirmed

JSPClient Profile

Database

27

Technology Map – Web based demoTechnology Map – Web based demo

Teamcenter Engineering Database

Knowledge ToolsUnigraphics NX

Application Server

Connect toTeamcenter

Initial Request

DisplayExistingDesigns

Pre-existing

Configurations

28

Technology Map – Web based demoTechnology Map – Web based demo

We are differentiated here!

Teamcenter Engineering Database

Knowledge ToolsUnigraphics NX

Application Server

Java Beans

JSP

Pipeline request

JT File o/p Parts Or

Sub-Assy

Requestdesigns

JT File displayed in VisViewer

Custom Design

Interface

29

Knowledge fusion deploymentKnowledge fusion deploymentEx

pert

ise

Knowledge EngineersDesign and create knowledge features and wizardsKnowledge EngineersDesign and create knowledge features and wizards

wizardscheckersadvisors

wizardscheckersadvisors

knowledge featuresutilitiesetc…

knowledge featuresutilitiesetc…

Senior DesignersView and modify knowledge contentSenior DesignersView and modify knowledge content

All UsersUse and share knowledge contentAll UsersUse and share knowledge content

CompanyUsers

30

Core 관련 정보 입력(Core Spec. sheet 선택)

국내 개발 사례 :1. 변압기 Core 설계국내 개발 사례 :1. 변압기 Core 설계

CCA Program 구동

기본 & 전기 설계Program 구동

3D Model 완성

Coil 관련 정보 입력(Core Spec. sheet 선택) 받침목 관련 정보 입력

(Core Spec. sheet 선택)

31

2. Turbo Fan Wizard 2. Turbo Fan Wizard

User InterfaceUser Interface기본설계 System기본설계 System

Turbo Fan 기본설계

Turbo Fan 편집 설계

Detail Parameters InputDetail Parameters Input

3D model create3D model createTurbo Fan 자동 생성

Turbo Fan 자동 설계

KF VDE를 통한Engineering Rule 조회

배포

권한에 따라 설계변경 가능

협력 부서 또는 제작 업체

DFA File 배포

Model File 배포

LWK-Chassis LWL-Chassis LWP-Chassis KAC LWC-Chassis 제습기 용 PAC

상위 Ass’y 생성 User’s

32

3. Hot Runner 자동 설계 시스템3. Hot Runner 자동 설계 시스템

마스터모델모델제어

수주모델로변경(Update)

상세설계

모델완성

도면 생성

Part List

DetailDrawing

ERP DB

수주정보

Library

ID Card

Utility마스터모델 제어프로그램

33

Hot Runner Manifold 설계 KnowledgeHot Runner Manifold 설계 Knowledge

XY 최소근접으로 Hot Coil 형태 변경

XY 근접으로 Manifold와Bolt 형태 변경

Y 최소 근접으로 Hot Coil 형태 변경

Y 근접으로 Manifold와Bolt 형태 변경

X 최소 근접으로 Hot Coil 형태 변경

X 근접이 심해져Manifold와 bolt 형태

변경

X근접으로 Manifold 형태변경

일반적인 형태

Y최소

X > X > X X최소

Y>Y

> X X최소

Y최소