applying systems engineering for smarter product development - … · 2017-10-06 · plm scope,...

© Copyright 2017 Tata Technologies. All rights reserved. All other trademarks are trademarks of their respective owners.

Applying Systems Engineering for Smarter Product Development Lionel Grealou, Vice President – PLM Europe, Tata Technologies

© Copyright 2017 Tata Technologies. All rights reserved. All other trademarks are trademarks of their respective owners. 2

A SYSTEM is a set of interrelated components working together toward a common purpose… an integrated composite of people, products and

processes that provide a capability to satisfy a stated need or objective

The System

External Entity

External Entity

External Entity

External Entity

External EntityActivity

Data

Materials

Activity

Energy DataSignals

Data

Data

Materials

Clear holistic purpose stated by business stakeholders

Start point of a design process Basis for the end-to-end testing of a

system’s fitness-for-purpose Clear input / output, boundaries, internal

and external interdependencies clearly articulated structure: logical,

technological, physical, etc. Can be decomposed in a “system of

systems” (e.g. system sub-system component sub-component part)


SYSTEMS ENGINEERING is an interdisciplinary approach that provides the means to enable the realisation of successful systems

SOFTWARE HARDWARE ELECTRONICS

FIRMWARE EMBEDDED

SOFTWARE

ELECTRICAL

MECHANICAL

ROBOTICS

CYBERNETICS

Design and verify an integrated and lifecycle balanced set of system people, products and process solutions

Align interdependent requirements that satisfy customer needs


Pre-acquisition Acquisition Utilisation Retirement

Make Sell ServiceCreate

Advanced

PlanningConcept Design

Development

& SimulationManufacturing

Sales &

MarketingService & Support

Systems Engineering is mainly effective in the Acquisition phase where conceptual to detailed design is created & half of Utilisation phase where product is already in use

Enterprise / Business Management

Project management

Systems Engineering

Operations

Systems Engineering spans across the entire PLM scope, hence it’s difficult to comprehend

Requirement decomposition Business Needs & Requirements (BNR) Stakeholders Needs & Requirements (SNR) System Requirement Specification (SRS) StRS StRS StRS StRS StRS

Requirement maturation and validation


System Study Approach

I/P O/P

Constraints

Characteristics

Attributes

• Means

• Resources

• Enablers

•

•

•

I/P O/P

Black BOX Approach

R

F Functional architecture, which describe what the system must do, from a capability point of view

L Logical architecture, which defines how the system is implemented

P Physical, which includes components / software, implementation parameters, a virtual definition of the real world product, including 3D representation to “visualise” the targeted system concept in the early phases

Requirements and test cases, which define the contextual needs with use cases, functional and non-functional requirements

White BOX Approach

R

F

L

P

Q

V

V

I

Envisage Maintain

Qualify

Validate

Verify

IntegrationPhysical design

Logical design

Functional design

Requirements

Align

Feed back

Align

Align

Digital twin vs

real product

Build

Applying the V-model across Disciplines


Mission

Function 1 Function 2

Function 1.1

Function 1.2

Function 2.1

Function 2.2

Logical Architecture: Requirement breakdown structure

Physical Architecture: Work breakdown structure

System

Sub-system 1

Sun-system 2

Assembly 1.1

Assembly 1.2

Assembly 2.1

Assembly2.2

Component A

Component B

Logical / Functional (keeping system as a black box)

Physical (keeping external system as a black box)

o What the system elements areo How they looko How they are to be manufactured, integrated & tested

o What the system will doo How it will be testedo Under what conditions it will performo What other systems will be involved with its operationo System Boundary

WHAT

HOW

Changes slowly

High level trade-offs & feasibility analysis

Physical Implementation

Problem Space – Ownership: System Owner

Solution Space – Ownership: Developer

Changes much faster

Logical vs Physical Architecture


Make Sell ServiceCreate

Advanced

PlanningConcept Design

Development

& SimulationManufacturing

Sales &

MarketingService & Support

Requirement maturation & validation

Requirement maintenance

Early BOM CAD BOM

EBOM / product configuration

MBOM / kitting

SBOM / sales configuration

M/ECAD

Light visualisation

Virtual reality / high-end visualisation

Software engineering

Extended enterprise collaboration

Materials & compliance

Weight & balance

Digital manufacturing

CAE / simulation lifecycle

Product development PPPM / RAID

Change management

Manufacturing execution (MES)

Enterprise resource planning / business analytics

Pro

du

ct L

ifec

ycle

Man

agem

ent

(PLM

)

MBSE workflows apply across the entire “V-model”, starting from the product conceptual design phase, continuing throughout its development and later lifecycle phases

Model Based Definition (MBD)

Design / xCAD / KBE models Simulation / CAE models Mathematical models Cost models Etc.

Model Based Systems Engineering (MBSE)

Every disciplines are likely to follow their own lifecycle and V-models and must be managed as an interdependent ecosystem

Integrated Product Development


Product A, Revision 1

CAD Product with complete PMI information:

o Dimensionso Weld Symbolso Notes / Labelso Feature Controls

Drawing A, Revision 1

Drawing for Product A which inherits complete PMI object info.

Designer creates 3D Part Designer creates Drawing object Complete 3D-2D Part Info Managed

PMI information flows into the JT File when the corresponding CAD structure is attached in Teamcenter

PMI Export to JT

Request for Change: New Revision creation

Data flow to Stakeholders

Inherit PMI

Convert to PMI

Design Draft Manage Share

Vehicle Root

Node 1

Sub Node 1.1

Product A

Product A Revision A

Drawing A Revision A

Product A : JT File

Supplier

Manufacturing

Visualisation

Quality

Design dimensions, labels, notes

Design dimensions, weld symb, datum

Annotations, sect. dimensions,comment

Notes, Labels, Proprietary info

Model Based Design (MBD) – an Element of Systems EngineeringApplication of Product Manufacturing Information (PMI) within the Enterprise


System Architecture Dev

System Requirement Spec• Functional & Logical conversion of StRS• Complete functional System description• Established Requirements Structure

Pre-acquisition Acquisition

UtilisationRetirement

Business Operations

Stakeholders Requirement Spec• Refinement of BRS: Feasibility Analysis• Targeted inputs from experts• Key owners are respective BUs

Business Management

Business Requirement Spec• Highlights business’ needs• Elaborates Missions and goals• Key owner is the Enterprise Mgmt

Enterprise Managers

StRSStRS

Designer Supplier

Domain Experts

Forward Traceability

Backward Traceability

Requirements Engineering

Business needs structuring

Mission

Func. 1 Func. 2

Func. 1.1 Func. 1.2 Func. 2.1 Func. 2.2

Forward Traceability

Backward Traceability

Requirements Engineering

StRS Enterprise Managers

Design Iterations

SyRS

AB

C

Sub-System Elements

Product Spec

Part

Material

Processes

Detailed Sub-Systems

Mature Bill of Material

ProductionTransition to Utilisation Delivered

SystemMaintain facilities, training,

personnel, suppliers and sparesLive Production

System

1

New Requirements

New Sub-Systems

Bugs, modificationsidentified

2

Enhancements / modifications

3

Modified System

4

System disposed as it becomes: • No longer serves business needs• Too expensive to maintain• Obsolete with respect to the current

market business/technical scenario

Operational testing through Utilisation Phase

Co

ntin

uo

us testin

g

Acceptance Test & Evaluation

InformationReq.

Ag

reed R

eq.

Draft Req. Doc.

Va

lida

ted

Req

.Do

c. Req.analysis

Req.allocation

Req.elicitation

Req.validation

SRR

System

Sub-System 1

Sub-System 2

Assembly 1.1

Assembly 1.2

Assembly 2.1

Assembly 2.2

Component BComponent A

Systems Requirement Review

Req

uirem

ents V

erificatio

n

Sub System Design & Testing

System IntegrationSystem Integration Testing

System Lifecycle – a Systems Engineering Perspective


Reorganisation of people and responsibility to achieve desired maturity

Capture and manage product requirements, decomposed and assigned to design disciplines (mechanical, electrical, electronic and software)

Fully managed and traceable system requirements

Basic system design to support Product Development to verify design integrity

Cross discipline collaborative environment to manage, organize, reuse system architecture models and capture system behavior

Fully matured system development accelerating physical product design (mechanical, electrical, electronic and software), knowledge driven and

Model Based Product Design

Virtual simulation of physical models to manage and enable traceability of simulation results to requirements

Searchable, reusable, scalable knowledge artifacts to support data compliance for verifying and validating requirements in both virtual and

physical models

Requirements Management

Functional and Logical Design

Physical Product Design

Toolset Integration

Verification & Validation

Organisation

MBDModel Based Design

MBSEModel Based System Engineering

Design individual disciplines based on decomposed and traceable requirements, and enriched Product Manufacturing Information (PMI) to

support concurrent engineering and Digital Manufacturing functions

Towards SMARTER Product Development: Implementing the Systems Engineering Roadmap

Progressive integration of tools to support functional evolution


Towards SMARTER Product Development: Critical Success Factors

Take a holistic approach Focus on integration maturity Prioritise alignment

improvement Both vertical (cross-domain)

and horizontal (cross-phase) integration

Take a model based perspective across engineering

Focus on requirement traceability across the system lifecycle

Design and adopt an integrated modular BOM system

Introduce flexibility & reusability of data

Start with change management workflows

Focus on user adoption of change


SMART PLANTS

SMART PRODUCTS

SMART DESIGN

SMART ENGINEERING

SMART MANUFACTURING

SMART DATA

SMART CITIES

SMART PROCESS

SMART PEOPLE?SMART TECHNOLOGIES

PRODUCT DEVELOPMENT 3.x

PRODUCT LIFECYCLE MANAGEMENT 2.0

INDUSTRY 4.0

ANALYTICS 2.x

INTERNET OF THINGS

INDUSTRIAL INTERNET OF THINGS

BIG DATA

SYSTEMS ENGINEERING

MODEL-BASED X

MOBILITY

HYPERCONNECTED

ARTIFICIAL INTELLIGENCE

SMART EVERYTHING

© Copyright 2017 Tata Technologies. All rights reserved. All other trademarks are trademarks of their respective owners.

For further information about Tata Technologies and what we can do to help you create better products

for your customers, visit www.tatatechnologies.com today.

Making product development

dreams a reality since 1989.

applying systems engineering for smarter product development - … · 2017-10-06 · plm scope,...

Documents