core alm program

Core ALM Program

Didier Balmette

Jan 31st, 2013

IPage : 231/01/2013 Confidential – Valeo Property Core ALM Program

Agenda

Pourquoi ? 2011

Première étape 2012

Deuxième étape 2012

Troisième étape 2013

Quatrième étape 2013


Pourquoi ?

Valeo Entreprise mondiale Centre de développement répartie sur le globe Mondialisation des projets Coopération entre centres

Constat Chaque centre de développement a un outil différent Impossible de standardiser / collecter les sources codes Méthode de développement différentes

Solution Un outil standard pour tout les développeurs Une gestion centralisée

D’où le projet


Agenda

Pourquoi ? 2011






Valeo organization

VIS

CDA

PTS

VIAS

VWS VWM

VLS

BG PG PL

CDV

CIE

CIC

THS

PCE PEM PAM PAC

PEL

TCC

GEEDS

BG / PG / PL impacted by

Core ALM program


StatusALM Users Global Growth

SHENZEN 23

TROY 17

BIETIGHEIM 404

CERGY CRETEIL

BOBIGNY LVR

CHATELLERAULT 481

VERSZPREM 29

TUAM93

CAIRO485

JAPAN 29

Entities 2012 2015CDA 670 800

CDV 410 520CIC/CIE 260 280

PTS 340 340PEM 226 226PEL 114 114

VIS 70 90VLS 40 56

VWM 30 34

THS 10 15GEEDS

(incl VIAS/Shenzen) 470 580

Total 1560 1825

Our SW development activity is increasing, with more & more multisite projects


Workshop

Groupe de discussion Un représentant de chaque BG/PG Organisation de Workshop Un ou plusieurs animateur Un chef de projet

Année 2012 Mise en commun des outils et des procédures Faire émerger un consensus Etablir une spécification de l’outil

Présentation Publicité auprès des BG / Users Présentation auprès des Directeurs


GEEDS

GROUP• R&D M&T• ALM CC

• FTE

VLS

Cergy

VIAS

CDV

VWM

Core ALM teamImplication of relevant PGs and GEEDS experts

Châtellerault

Bietigheim

Cairo

PCE/PEL

Créteil

CIC/CIE

Bobigny


Not covered by this program

Core ALM Program scope overview

MCAD(Catia)

Simulations & Calculation tools

PLMTarget

PRM

ECAD(Cadence)

ALM

Activities Management

Product Structure Management

Internal Collaboration

Design review

SW Configuration Control & Change

Management

Knowledge Capitalization / Standardization

Reporting & Monitoring

Interfaces Tools

RequirementsManagement (tbd)Will be defined

in Core ALM 1. 2

Customers issue mngt systems (tbd)

Will be defined in Core ALM

1. 2

ALM Functional scope includes all Core functions and some interfaces to other environments

Will be defined in Core ALM

1. 2

Core ALM 1.1: projects

Core ALM 1.2: timesheets


Constant Innovation Policy

Glossary, HLP & business needs contribution

I| 7

High level business needs classification grid Change management Configuration

managementActivities management Requirements

managementRelease plan

Planning management

Resource management

Cost control

Reporting

Efficiency

Cost control

Traceability

Tech doc management

BOM vs. Content consistency

Traceability

Promotion model

Completeness

All changes captured

All decisions made

All impacts identified

All decisions achieved

Seamless processes

Changes exchanged

Visibility on Reqs coverage

History of a SwCR / SwPR

Reasons of a change of file

BOM intrinsic consistency

Easy access to documents

PLM based Classification

Content : Reqs/CR/PRs list

BOM building mechanisms

BOM of a configuration

Reqs/CRs/PRs of a BOM

Eng/Non eng activities mgt

Workload initial input

Actual workload collection

Resource planning

Resource assignment

Workload consolidation

Budget overflow detection

Project status & progress

Sw department productivity

Features related to CRs/PRs

CRs/PRs related to Features

Of change management

Classification grid

Valeo Glossary

ALM Glossary Functional specification

Business needs Use Cases

High Level Processes

UC1

UC2

UC3

12

34


Legend

Produce documents & code

Work packages

Formalize requirements

Define sw product (int. &

ext. comp. structure)

Initiate Activities

Relate them to requirements

Specify & Plan releases

Relate Activities to

tasks & components

Project preparation Project launch Changes after

delivery

Initiate ACRs, APRs

Run CCB (can be physical or

not)

Deliver SW (to internal or

external customer)

Update schedule

Group requirements into features

(optional)

Define org.: users, roles &

rights, templates

Initiate Parent & Child

Activities

Perform lowest level

activities

Close development

activities

Create Development

baselines (optional)

Early changes

(before formal testing)

Changes before

delivery

Create Release baseline

Define Project Schedule & resources

Initiate ECR in PLM

When changes applied, close ECR & update

PLM BOM

Activities Mgt

Change execution

Change Preparation

Create Delivery baseline

Refine: • needs • feasibility• Interface

with Project Mgt

Delivery

Reporting

Product Configuration management

Out of ALM workshops scope

Out of ALM workshops scopePublish

reusable components into catalog

Integrate components

& product

Integrate and test the product

Verify & Validate


Proposed ALM Project Dashboard

Anal

yzed

Number of ACRs/APRs in each status: Today the following priority is defined:

[Project(s) Name] – Change Management Dashboard

# of

AC

Rs/

APR

s

Priority

Low Medium High

Type of the Requests submitted over the last 6

months:

Problems [# of APRs]

Changes [# of ACRs]

# of

AC

Rs/

APR

s

Status

Subm

itted

Appr

oved

Plan

ned

Reje

cted

Clos

ed o

ver t

he

last

6 m

onth

s

Inte

grat

ed

ACRs/APRs origin

Assi

gned

Impl

emen

ted

Test

ed S

olve

d

Test

ed F

ail

On

Hold

Canc

elle

d

ImmediateUnknown

Today the following severity is defined:

# of

APR

s

SeverityMinor Moderate Major Critical

Customer[# of ACRs/APRs]

Valeo [# of ACRs/APRs]

Bench testing

Vehicle testing

ProductionAfter Sales

Unknown

Software Dev.

Software Int.

Software Test.

Hardware

System/ProductProduction

Evolution of # of opened ACR/APR:

# of

AC

Rs/

APR

s

TimeTotal number of open ACRs/APRs

Number of open customers’ APRs

Number of open internal APRs

DRAFT


Workshop

Choix de la solution technique Etude de solutions (serena, ibm etc…)

Choix de la solution Base Serena Dimension Développement client Java Valeo

Pourquoi Coût et gestion (une base) Solution déjà présente en allemagne


Agenda

Pourquoi ? 2011






Spécifications

Ecriture de la Spécification Ecriture en // des workshop de la spécification Validation par relecture des acteurs des Workshop

Validation globale de la spécification Approbation formelle par les directeurs R&D Présentation en BG/PG

Préparation pour le Groupe Préparation d’un Business plan pour le groupe Présentation et validation du plan au niveau groupe Acceptation par le groupe


Agenda

Pourquoi ? 2011






Dev center (site B)Dev center (site B)

Servers (outsourced)

Core ALM generic architecture

Oracle DBLic Mgr

Dev center (site A)

Library cache server

End user

App + Filesserver

End user

File downloads Dev center (site B)

Same architecture as site A

Direct DB read

File uploads

File replica

tion


Infrastructure

User desktop system requirements Processor : dual core, min 2 Ghz RAM : 2 GB LAN : 100 Mbits Harddisk : 2 to 3 months of data (10 GBytes as a guideline) SW environment: Windows XP or 7

Local infrastructure LAN devices: 100 Mbits

Tests Tests de perfomance


Agenda

Pourquoi ?

Première étape

Deuxième étape

Troisième étape

Quatrième étape

Next steps


Enhancements solution will be realized and deployed in 3 stages

Infra. set up +

Client upgrade

Stage 1. 0

Object model upgrade

Core functionalities Priority 1 requirements

(Project Launch, Change Mgt, Activity Mgt, Configuration Mgt, SW Delivery)

Standards components & documentation Mgt

Reporting & Monitoring part 1

Project Management interface (MSProject + PRM)

Requirements Mgt interface (Doors)

Core functionalities Priority 2 requirements

(Project Launch, Change Mgt, Activity Mgt, Configuration Mgt, SW Delivery)

Reporting & Monitoring part 2

Requirements Mgt interface (other)PLM Interface:

- part 1 (PLM-ALM BoM link + changes notifications)

- part 2 (where-used + change processes integration)

Stage 1. 2

Foundation

Functionalities

Interfaces

Stage 1. 1(All entities)


Benefits on Resources efficiency

The future Valeo Core ALM will improve teams efficiency in different ways:

Benefits for all

SW Project Leader

Ease to find data

Reduced data double entry

24/7 User support

Interfaces with PLM & Project Mgt tool

Configuration & Change Mgt processes automation

CCB live mgt in ALM

Enhanced Project Mgt & SW Delivery

Reduced rework

Improved traceability

Process driven & traced

Automatic Baseline comparison

Developer, Analyst,

Integrator &Tester

SW Quality Manager

Reduced rework (bug fixing) Reuse capabilities


S1 2013 S2 2013 S1 2014 S2 2014 S1 2015 S2 2015 S1 20160%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

CDV VIAS CIE CIC, VLSPEM VWM, THS PEL

Gains in efficiency have been calculated following a conservative ramp-up

Stage 1.1

Stage 1.2

Stage 1.0

At 100% of gains, a tester / developer profile has 3 to 4% increase of efficiency,a SW Project Leader profile 9 to 10% and a SW Quality Manager 6 to 7%.


T0T0

+ 1 year

IAR

Today

Planning

Dev

Dev

Deployment

Spec

Kick-off

CDV Pilot Go-liveEarliest Sept, 4th VWM

PELVIAS(remaining users)TCC

VLSPEM

Test

s

Test

s

Spec validated

T0 + 6 months

T0+ 18 months

CDV PilotGo-live

PilotVIAS deployment, along PGs migrations

CIE/CIC

Pilot Upgrade

Infra def+ dev

Pilot Deployment

Centralized CDV platformSecured response time

Functional improvementsSW Standards management

Further functional improvementsInterface with PLM target

Go-no GoGo-Live

Key: Stage 1.1

Stage 1.2

Stage1.0

All entities on Core ALM

Add-ons spec 1.1

core alm program

Documents