1

System Engineering with Aras Innovator

Neptune Conference 28th May 2015

Outline

Who is Aras ?

System Engineering with Aras

Demo - OSLC interoperability between PLM and ALM

2

3

Who is Aras?

3

Aras background

500+ CustomersCommunity led by customers, partners & consultants

Global Operations | PLM Industry TeamNorth America, Europe and Asia

Markets with complex products and processes Automotive

Industrial Machinery

Aerospace & Defense

High Tech Electronics

Consumer Goods

Life Sciences

Energy

Innovations Technology: Model-based SOA

Business: SaaS subscription model

Solutions Enterprise PLM/MDM

▫ Managing the product lifecycle through critical business processes

▫ Driving collaboration across, disciplines, functions, locations and the supply chain

▫ Synchronizing disparate groups and teams

Product Data Management

▫ CAD management and visual collaboration▫ Document management▫ Workflow, lifecycle management and security

4

Aras customers

5

Aras is different

At Aras we’ve taken a different approach

▫ Technology: Model-based SOA

▫ Business: SaaS subscription model

We’ve built a better PLM solution: one that

▫ Adapts to your business, not the other way around

▫ Removes unnecessary barriers to collaboration

▫ Changes the economics of PLM in your favor

That delivers greater benefits sooner and a lower TCO

6

7

Aras System Engineering Initiatives

Aras Initiatives for System Engineering

Partnership with University of Kaiserslautern and Prof. Martin Eigner for Model-Based System Engineering with Aras Innovator

IBM – Aras Strategic Partnership to integrate PLM and Continuous Engineering

▫ Integrating IoT design practices with PLM

▫ Linking PLMs physical product structure with System Design and ALM

▫ Tracing System level requirements down to a part in a physical structure

8

9

MBSE with Aras

Product Lifecycle

Dis

cip

line

s

PLM Landscape and Vision

10© Lehrstuhl für Virtuelle Produktentwicklung | 2015

Source: VPE Research Project mecPro² (T. Gilz)

Future PLM (System Lifecycle Management = SysLM) Realized with aras I NNOVATOR

PLM Systems

11

11

© Lehrstuhl für Virtuelle Produktentwicklung | 2015

Source: VPE Research Project mecPro² (T. Gilz)12© Lehrstuhl für Virtuelle Produktentwicklung | 2015

ering

relations

to discipline-

specific

Development

Systems Engine

elements

(for System

architects)

Source: VPE Research Project mecPro² (T. Gilz)13© Lehrstuhl für Virtuelle Produktentwicklung | 2015

Source: VPE Research Project mecPro² (T. Gilz)14

15

IBM – ARAS Partnership

IBM – Aras Partnership

Define & publish a reference architecture (data models, use cases, and process models) for integrated SE, MBE, ALM, PLM, and MRO

Jointly collaborate between Airbus/IBM/Aras on the ProSTEP iViPOSLC ALM-PLM Interoperability Forum

Enhance OSLC specifications to incorporate PLM concepts

16

Data Base

Physical Product - PLM - Aras

OSLC Capabilities - Data and Processes Sync.

© 2015 Aras aras.com17

IBM Continuous Engineering & SSE

Co

nti

nu

ou

s V

erif

icat

ion

Unlocking Engineering Knowledge

Strategic R

euse

Rational Team ConcertRational DOORS Next Generation

Rational Quality ManagerRational Rhapsody Design Manager

Rational Engineering Lifecycle Manager

TraceabilitySecurity

ComplianceWorkflows

ConfigurationsRevisions

OSLC “links” in Aras are fully intelligent PLM

relationships – instead of “dumb” attributes

Change ManagementRequirements ManagementArchitecture Management

Configuration ManagementQuality ManagementTracked Resource Set

Product Structure

18

Interconnected ECO between ArasInnovator and IBM Continuous Engineering Suite

Use Case and Demo– OSLC based

Flow – Existing release in PLM

19

PLM contains a Released product configuration (a structure) which includes multiplicity of Parts from MCAD, ECAD, and ALM

Embedded software is accounted for as a binary build file on a Part and has its own part #

Software file points to a RTC build process that generated it

Nothing in the Product can be changed since it is Released (including RTC link)

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSE

OSLC

Rational Team

Concert

Flow – New ECO in PLM

20

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSE

OSLC

ECO

Rational Team

Concert

Create Express ECO against the Product, state is New per Work Flow

Entire product structure is exposed on ECO

ECO state is controlled by the associated workflow

Nothing in the Product can be changed (including software) since ECO did not specify what parts of the Product are affected

Flow – ECO promoted to In Planning

21

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO

Work Item

ECO is promoted to In Planning state under Work Flow control

Promotion triggers PLM request for RTC Work Item due to software content

New Work Item is created in RTC from PLM and auto/manually populated

ECO and Work Item are linked bi-directionally via OSLC

Work Item context in this PoC is a single IR software issue

This is when Systems Engineers and Software Engineers to start discussion

Flow – Alternate ECO approach proposed

22

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO

Work Item

Work Item

RTC user responds with additional Work Item from RTC that is linked to the same ECO but addressing different software element

PLM and RTC items are linked bi-directionally via OSLC

Flow – ECO strategy collaborated on

23

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO

Work Item

Work Item

Open discussion panel in ECO

Demo OSLC back/forth navigation between Aras and RTC

Systems Engineers have to touch data in both environments in order to determine the right action, physical structure in PLM, MBE system in Rational

Flow – ECO strategy decided

24

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO

Work Item

Work Item

One of the Work Items gets “Closed” from ECO (but retained) as not relevant in this case

“Closed” Work Item and its OSLC links can’t be edited in RTC or Aras

Work Item context here is for a single IR software change

Flow – ECO affected Parts marked for work

25

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO Work Item

Work Item

Related Parts are marked as Affected in PLM ECO: Product, Electronic, and Software

Flow – ECO promoted to In Work

26

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO Work Item

Work Item

ECO is promoted to In Work state according to Work Flow

Parts marked as Affected in ECO get new revs without eliminating the previous revs (other Parts in configuration are left as is)

Work is assigned in PLM via In Box messages according to Work Flow

Work is assigned in RTC via OSLC link according to Work Flow

OSLC links can no longer be deleted or added on that ECO

Flow – ECO engineering status updates

27

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO Work Item

Work Item

Electronic and software engineers implement changes as stipulated by ECO and Work Item

Work may be done in the authoring tools with the results uploaded via CAD connectors

Engineers contribute to ECO In Work vote after respective changes are implemented and results uploaded to PLM

Software release engineer may submit software build later in the process, only vote is required to indicate completion of the software task

Software build may have dependencies on other software issues that need to be closed before the build is made

Flow – ECO promoted to In Review

28

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO Work Item

Work Item

ECO is automatically promoted to In Review once all votes are satisfied as defined by Work Flow

ECO In Review state prevents additional changes by engineering within PLM product structure, except for a subsequent software file upload

ECO In Review state trigger equivalent state in the linked Work Items via OSLC

Result of In Review may trigger Work Flow to reset ECO back into In Planning if a problem is found with the work submitted by engineering

Flow – Software build uploaded

29

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO Work Item

Work Item

Can’t release without new software upload at some point

Software build typically has dependencies on other software issues (and therefore related to different ECOs and Work Items) that need to be closed before the build is delivered for this ECO

ECO is in a waiting mode until the build is delivered

Flow – New Product rev. Released

30

ArasPLM Product

Mechanical

Electronic

Binary File

Software

IBMContinuousEngineering

& SSERational

Team Concert

OSLC

ECO Work Item

Work Item

Completed votes plus software upload promotes ECO state to Released under Work Flow control

ECO In Review state triggers equivalent state in the linked Work Items via OSLC

New configuration of the Product becomes released in PLM under the new rec and using new revs for the modified Parts

The new Product configuration can not be modified (this time including software) in PLM without a new ECO

31

32