introduction to - isid-industry.jp · requirement tree function block diagram(fbd) block...

©2017 Information Services International-Dentsu, Ltd. Confidential ©2017 iTiD Consulting, Ltd. Confidential

Introduction to

2017

Information Services International - Dentsu, Ltd. (ISID)

iTiD Consulting, Ltd.


Typical Issues in Product Development

1

©2017 Information Services International-Dentsu, Ltd. Confidential ©2017 iTiD Consulting, Ltd. Confidential 2

What iQUAVIS Provides to Tackle the Issue

Why iQUAVIS is Crucial for Your Product Development?

Cannot prevent problems to occur, and

causing reworks.

Do not have enough time for developing

quality.

Failures are found in the market.

Takes time to solve inter-domain issues

since there is no “common language”

between different technical domains.

Minimize design reworks

Minimize reworks based on the analysis of the structuralized information of the product (technology break down).

Enable apprentices to design with

"experts’ knowledge"

Store and utilize explicit experts’ Knowledge on design examination and project management into the system.

Establish “common language” to

encourage communication between

experts in different domains

Provide tools to express technology of the product as a “common language”, which is easy to understand by experts in different technical domains.

Typical Issues

iQUAVIS solution enables to..

As a result, many companies suffer from issues such as..

Product development today is expected to be more speedy and sophisticated, and consequently, it became complicated.

Today’s Product Development


Concept of iQUAVIS

3


What is iQUAVIS ?

iQUAVIS is a methodology and a tool for “System Modeling”, as ”Quality & Risk Management”, and ”Project Management” of the product development.

It is a unique tool which combines all three aspects.

4

System Modeling

Project Management

Quality & Risk Management


Task Schedule

Framework of iQUAVIS

Gantt Chart / Schedule Chart etc. Component Function

Failure mode

cause RPN measures

** ○○○

** ○○○

** ○○○

** ○○○

** ○○○

** ○○○

FMEA etc.

Create Process

Generate Tables

Project Management

System Modeling


Function Block Diagram Block Diagram State flow Diagram Requirement tree Entity Block Diagram

Requirement Function Entity

Hardware

Software

Technology Breakdown Tree

5


Basic Consideration Flow Chart

④Extract Risks ⑥Development Planning & Progress Management

①Req. Analysis ②Function Design ③Consideration of

Implementation Means

Use-case Diagram

State-flow Diagram

Req. Tree

Function Flow Diagram

Block Diagram

TBD

FT Diagram

⑤Consider Countermeasure

Comp. Func. Concern Cause RPN Countermeasure Task Schedule

Development Plan (Process)

×

× ×

×

× ×

×

DSM

Organize Stake-holder Clarification of the System of Interest

Organize usecase Extract needs

Clarification of system Req.

Organize system state and behavior

Consideration of Mechanism and Function Design

Allocation of implementation means

Organize impact relationships

9

9 3

6

9

9

DMM

Grasp trade-off Relationships

Thrash outing concern & cause

Consideration of countermeasure & review Process streamlining Task extraction & planning

EBD

FMEA/DRBFM

System Modeling

Quality & Risk Management Project Management

6


iQUAVIS Methodology & Tool

7

System Modeling


“Technology Breakdown”

“Technology Breakdown” is the methodology to construct product architecture (Relations of Requirements and Functions and Entities).

Stakeholders

Needs

Product

:strong :mid :weak

Requirements & Functions to be satisfied

system structure

stakeholder needs

system requirements

function /behavior

characteristic value

component /parameter

sub- system

system

Requirement Function Entity

Hardware

Software

Technology Breakdown Tree (TBT)

Function Block Diagram(FBD) Block Diagram State flow Diagram Requirement tree Entity Block Diagram(EBD)

8

Basic methodology


Technology Breakdown Tree

Requirements Functions Entities (system structure)

9

“Technology Breakdown Tree (TBT)” visualizes the allocation relationships.

iQUAVIS will easily extracts the related items.

Fuel efficiency

Engine Requirement

Reliability

Noise & Vibration

Cost

Exhaust gas regulation

Engine power

Weight

Combustion efficiency

Cool Engine body

Circulate Cooling water

Water pump

Radiator

Thermostat

Cooling system

Engine block

Engine head

Body system Engine

Early warm-up in engine starting

Heat transfer to air

Engine control system

Cooling water control software

System Modeling [Demo] Let me show the data. ①見方の説明 Functions that were wrote out in Block diagram are reflected in the TBT. And in TBT, you breakdown Functions, and construct relations between Requirements and Functions and Components. ②正逆展開 In this way, you can extract the related items. ③気付き In this way, you can realize trade-off.


QFD (Quality Function Deployment)

10

“QFD” is the matrix to visualize the relations between Requirements/Functions and Entities from bird’s-eye view.

Req

uir

em

en

ts

or

Fu

ncti

on

s

Entities (Components or Design parameters)

iQUAVIS allows you to notice impacts of changes easily. W

ate

r Pum

p

Early Warm-up in Engine starting

Cool Engine Body

Engin

e H

ead

Direct Impact

Indirect Impact


QFD

Engin

e B

lock

Next diagram is QFD. QFD represents the relations between Functions and Components. And these numbers represent strength of relation. On QFD, you can find easily trade-off and rebound. [Demo] In design WP, you can recognize trade-off between “Early warm-up” and “Cool Engine Body”. And if priority of “Early warm-up” is higher than “Cool Engine Body”, you may need to countermeasure in Block or Head. This is rebound. In this way, you can find easily trade-off and rebound.

9

6

3

Strength of relation

: Strong

: Mid

: Weak

System Modeling


Block Diagram

11

“Block diagram” represents the mechanism of system.

e.g. flow of energy, material, information

Able to design a basic skeleton with other engineers by using Block Diagram as a common language.

We recommend to draw several diagrams depending on its usage. - Function Block Diagram - Entity Block Diagram - Function Flow Diagram - Internal Block Diagram - Parametric Diagram etc.

[Demo] Let me show the data. ①見方の説明 Blocks are components. Arrows represent flows of energy or material. (For example, heat, force, electric, water etc.) You can check related items. ②機能検討の説明 On the Block Diagram, you consider with other engineers “what functions are necessary ?” And write out the functions explicitly.

System Modeling


Synchronization in iQUAVIS

12

“Tree”, “Block Diagram” and “QFD” are connected and synchronized within the tool.

Easy to switch to different tool views accordingly, while you are considering the design.

Block Diagram


QFD

synchronized

As the last of system modeling, I would like to talk about Synchronization in IQUAVIS. TBT and BD and QFD are connected & synchronized in this tool. Here, Let me show demo. If you modify the tree, it is reflected in QFD and BD. And vice versa.

System Modeling



13



Concept Design

Logic Design Function Design Requirement Analysis

Detail Design Evaluation

Reliability Design

Trial Production

Design review Reviewers

FMEA (Failure Mode and Effect Analysis)

<Function> <Requirement> <Entity>

iQUAVIS automatically generates FMEA sheet from the system model

Failure mode

cause Failure

in Function


*What is DRBFM ? It is systematic FMEA method established by TOYOTA. Point of DRBFM is to focus on design changes. So, it is possible to prevent problems effectively compared with the FMEA. It has been introduced in many companies in Japan.

Component

(change)

Function Risk RPN

Countermeasure

Result of DR

Function disorder

Failure mode

cause Design Evaluati

on Manufac

ture

FMEA sheet

Failure

Engineer

＊ ○○○

＊ ○○○

＊ ○○○

＊ ○○○

＊ ○○○

＊ ○○○

Generate worksheet automatically


iQUAVIS integrates System Model and Quality & Risk Management.

14


Specifying Possible Impacts by Changes

Damage of contact surfaces

Large thermal expansion

Frictional heat by high

rotational speed

***

Coefficient of thermal expansion

Requirement Function Design

parameter Component

Failure mode

Stability of performance

Outer diameter

Stationary part

shaft

lubricant viscosity

Thickness Pad

Material

Inner diameter

Rotating part

material skirt

***

Support static load

Keep water film pressure constantly

Support dynamic load

***

Keep appropriate

stiffness

***

Keep clearance of contact surfaces

to a certain

***

***

***

Control software

Rotational speed control

***

Max rotational speed

Power generation capacity

*** ***

***

***

***

***

Damage of contact surfaces

Large thermal expansion

Frictional heat by high

rotational speed

Stability of performance

Support static load

Keep water film pressure constantly

Keep clearance of contact surfaces

to a certain

Risk

Max rotational speed

change

Effect

Coefficient of thermal expansion

Material

material

Countermeasures (candidate)

15

By noticing risk in early stage, engineers can consider countermeasures against the risk that could have been overlooked.




16

Project Management


Schedule Chart

Task Object Schedule

Schedule Chart

** integrated test

** endurance test

** integrated test

decide ** spec

decide **spec

design ** component

design ** component

production ** system

iQUAVIS automatically pick-up the tasks that relates to the changes.

Project Management

<Function> <Requirement> <Entity>

** unit test

** integrated test

decide ** spec

design ** component

Impact

Impact

Impact

Impact

change

Based on TBT, you can define all the tasks you need to consider


iQUAVIS integrates System Model and Project Management.

17


Summary

18


Summary: Basic Consideration Flow Chart using iQUAVIS

④Extract Risks ⑥Development Planning & Progress Management

①Req. Analysis ②Function Design ③Consideration of

Implementation Means

Use-case Diagram

State-flow Diagram

Req. Tree

Function Flow Diagram

Block Diagram

TBD

FT Diagram

⑤Consider Countermeasure

Comp. Func. Concern Cause RPN Countermeasure Task Schedule

Development Plan (Process)

×

× ×

×

× ×

×

DSM

Organize Stake-holder Clarification of the System of Interest

Organize usecase Extract needs

Clarification of system Req.

Organize system state and behavior

Consideration of Mechanism and Function Design

Allocation of implementation means

Organize impact relationships

9

9 3

6

9

9

DMM

Grasp trade-off Relationships

Thrash outing concern & cause

Consideration of countermeasure & review Process streamlining Task extraction & planning

EBD

FMEA/DRBFM

System Modeling

Quality & Risk Management Project Management

19

introduction to - isid-industry.jp · requirement tree function block diagram(fbd) block...

Documents