Module 1

Lecture 2
CAD/CAE/CAM/CAx Database
 C Ax IN PRODUCT CYCLE
CAE
Assembly Mechanism/Kinematics

CAD/E
Analysis

Modeling Geometric Drafting

Data Base

CAM
Assembly Robotics CNC Process
Stations Language Programming Planning

CAI
Inspection Products
 Product Lifecycle Management

CAE

Tooling design
CAD

Item management

Product structure
“Item” could be:
• CAD document
centralized DB Security
• Text document
[File vault]
• Design spreadsheet
Engineering Changes • Software program
• Process Plan
• SOP
Task management
• Customer complaint
• Service records
 Product Lifecycle Management

Item management

- product architecture planning

Product structure - specification (BOM tree, hierarchical model)
- Instantiation (parametric) from templates
centralized DB Security
[File vault]

Engineering Changes

Task management
 Product Lifecycle Management

Item management

Product structure
- Authority
centralized DB Security - Views
[File vault] - Access control (check-in/check-out)

Engineering Changes

Task management
 Product Lifecycle Management

Item management

Product structure
-ECR
centralized DB Security - Design modifications
[File vault] - Confirmation/approval cycle
- ECN
Engineering Changes - Info storage/retrieval

Task management
 Product Lifecycle Management

Item management

Product structure

centralized DB Security
[File vault]

Engineering Changes

Task management

-team specification (requirement based, resource based)

- task assignments
- milestones setting, management
- critical path
- deadline reminders, notifications
Organizational View

8
 Functional View
Single Source of Product Data

Teamcenter

CAD DATA MANAGEMENT

NX, AutoCAD BOM MANAGEMENT
Drawing & 3D Design Re-use
Variants / Options

ACCESS CONTROL
Information Security

INTEGRATED VISUALIZATION
Access 2D & 3D Drawing
Sectioning / Measure / Clearance Check
No CAD Tool Required
MS Office
Integration

COLLABORATION
Share Documents, RELEASE MANAGEMENT
Conference Engineering Release Process

9
CAD/CAM systems uses

Relational and Object databases

to store geometric, graphical
and other data that defines a
CAD model
Relational database is a set or collection of tables.
• A DB can have as many tables based on the needed
attributes
• Data in a table is stores as attributes in rows
• Each row in a table is called as a record or tuple

Eg. DB of a Boundary Representation, has three

relational tables faces, edges and vertices. A
cube has 6 faces. Each face has four vertices
F1 E1 E2 E3 E4 Each is a
separate table
E1 V1 V2 with
V1 X1 X2 X3 corresponding
rows(record)
Relationships between tables are of three types :

- One to one [there is only one record in the

second table for each record in the first table]
- One to many [mutiple records exist in the
second table for each record in the first table]
- Many to one [parent-child / multiple records in
the first table, only one record exists in the
second table]
How to query/update the RDBMS..

SQL : Structured Query Language is used to

Define data, manipulate, retrieve, sort and filter
specific data form the DB

Sample statements include CREATE DATABASE,

CREATE TABLE, SELECT, ALTER, INSERT, DELETE
AND UPDATE
Parametric design examples

Definition of a nut

Length of threads

Length of smooth part =

total length – threaded length
 Parametric design examples..

Exploded view:
Yamaha YFM200 Motorcycle
Automatic Clutch
Catalog-based Designs

An extended of parametric design:

Base model specifies topology and relations between geometry
The design details are all expressed as parameters
Part design is created by providing a table with parameter values

Standard sections

Al extrusions

…
Catalog-based Designs: an example

Catalog of fasteners (screws, nuts, …)

Catalog design

We shall assume a catalog of parts (though you can have product catalogs)

1. Divide the group of products into categories;

each category has the same set of descriptors

2. Each group will form a sub-set of the catalog, called family

e.g. Fastener chapter, Screw family, has attributes: designation, type, dia, length

3. Construct a parametric CAD model of one member of the family

QUESTION: What are the independent variables in this model?

4. Identify the independent variables with names matching attribute names

Catalog design…

4. Identify the independent variables with names matching attribute names

5. Create a table (e.g. a MS Excel table) with attributes and values

6. Use the GUI of the CAD system to link the table, design, family description
Catalog-based Designs

Using catalogs:

Catalogs ≈ a Database table

 search for a catalog component using a query on its design parameter(s)

Example
Filter: (l_length > 10) and (l_length < 15)

Alternate method:

Most CAD systems will allow a

thumbnail preview and select
Object Database Management systems
Extends SQL to OQL
-works on attributes, behaviour and methods

Eg. Model, year and Color …..

drive, stop and maintain…
auto clutch, gear…

Object is an entity that has attributes and behaviours.

Behaviour is the sequence of steps or the algorithm

Spur Gear Attributes : root diameter, addendum

OBDMBS works on classes (object definition),

instantiation(specific object) and membership access
Other ODBMS concept / Parametric design and objects

Inheritance promotes modularity and re use, allows one object to

inherit variables and methods from another object

The class that we inherit is known as a

superclass in Java or
base class in C++
Eg. extrude class
Class Extrude {
//define class variables (object attributes)
Private P1, P2, P3, P4, R,T;
Public void setP1 (P1input)
P1 =P1input
//repeat the above method for P2 to P4, R and T
}
Object relational mapping

-This mapping converts in memory objects to

relational data
-Eg Java class would map to an SQL table
-An instance of the class would map to a record(row)
in the table, while properties would map to
individual fields(cells) in that row.

MACROS
-Is a simple string of commands that records a
sequence of actions that a designer performs
frequently
-Interfacing CAD and CAM
 System Engineering “ Vee”

The “Vee” Model of System Development

User
System
Requirements &
Demonstration &
Concept of
Validation Systems
Operations
Engineering
Domain
System
System
Requirements &
Integration & Test
Architecture

Component Component
Design Integration & Test

Component
Engineering
Procure, Fabricate, Domain
& Assemble Parts

Ack.: T Asokan ,IIITM

Ack.: T Asokan ,IIITM
 Mission Operation &
Continuous Quality Improvement Plan
Analysis Retirement

S ystem Final
Validation Plan
Requirements System Test

Functional Verify
Verification Plan
Decomposition Subsystems

Physical Test
Test Plan
Decomposition Components

Build
Components

The design downstroke and the manufacturing upstroke

Ack.: T Asokan ,IIITM

 Summary
• Classification of systems
• System engineers and their roles
• System design processes
• Economic impact of design process
• System life cycle

Example
https://insights.sei.cmu.edu/blog/requirements-in-model-based-systems-
engineering-mbse/

Ack.: T Asokan ,IIITM