La présentation est en train de télécharger. S'il vous plaît, attendez

La présentation est en train de télécharger. S'il vous plaît, attendez

Core ALM Program Didier Balmette Jan 31st, 2013.

Présentations similaires


Présentation au sujet: "Core ALM Program Didier Balmette Jan 31st, 2013."— Transcription de la présentation:

1 Core ALM Program Didier Balmette Jan 31st, 2013

2 Agenda Pourquoi ? 2011 Première étape 2012 Deuxième étape 2012
Troisième étape 2013 Quatrième étape 2013

3 Pourquoi ? Valeo Entreprise mondiale Constat Solution D’où le projet 
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 A software package (included in the client ?) will periodically check the system requirements D’où le projet 

4 Agenda Pourquoi ? 2011 Première étape 2012 Deuxième étape 2012
Troisième étape 2013 Quatrième étape 2013

5 Valeo organization BG PG PL VWS VIS VLS CDV CDA CIE CIC THS TCC PTS
BG / PG / PL impacted by Core ALM program BG PG PL VWS VWM VIS VLS CDV CDA CIE CIC THS TCC PTS PCE PEM PAM PAC PEL GEEDS VIAS

6 Status ALM Users Global Growth
SHENZEN 23 TROY 17 BIETIGHEIM 404 CERGY CRETEIL BOBIGNY LVR CHATELLERAULT 481 VERSZPREM 29 TUAM 93 CAIRO 485 JAPAN Entities 2012 2015 CDA 670 800 CDV 410 520 CIC/CIE 260 280 PTS 340 PEM 226 PEL 114 VIS 70 90 VLS 40 56 VWM 30 34 THS 10 15 GEEDS (incl VIAS/Shenzen) 470 580 Total 1560 1825 Our SW development activity is increasing, with more & more multisite projects

7 Workshop Groupe de discussion Année 2012 Présentation
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 A software package (included in the client ?) will periodically check the system requirements

8 Core ALM team Implication of relevant PGs and GEEDS experts
VWM VLS Châtellerault Bobigny GEEDS GROUP R&D M&T ALM CC FTE Créteil CDV CIC/ CIE Bietigheim Cairo Cergy VIAS PCE/PEL

9 Core ALM Program scope overview
ALM Functional scope includes all Core functions and some interfaces to other environments Not covered by this program PRM Core ALM 1.1: projects Core ALM 1.2: timesheets PLM Target Simulations & Calculation tools ALM Activities Management Product Structure Management Internal Collaboration Design review SW Configuration Control & Change Management Knowledge Capitalization / Standardization Reporting & Monitoring MCAD (Catia) Will be defined in Core ALM 1. 2 ECAD (Cadence) Will be defined in Core ALM 1. 2 Customers issue mngt systems (tbd) Requirements Management (tbd) Will be defined in Core ALM 1. 2 Interfaces Tools

10 Glossary, HLP & business needs contribution
ALM Glossary Functional specification High Level Processes 1 Valeo Glossary 2 Classification grid 4 3 UC1 UC2 Update on The ALM V1 deployment UC3 Business needs Use Cases Constant Innovation Policy

11 Work packages Produce documents & code Project preparation
Project launch Early changes (before formal testing) Changes before delivery Integrate components & product Deliver SW (to internal or external customer) Changes after delivery Formalize requirements Define org.: users, roles & rights, templates Perform lowest level activities Initiate ACRs, APRs Integrate and test the product Create Release baseline Initiate ECR in PLM Group requirements into features (optional) Define sw product (int. & ext. comp. structure) Close development activities Run CCB (can be physical or not) Verify & Validate Create Delivery baseline When changes applied, close ECR & update PLM BOM Out of ALM workshops scope Out of ALM workshops scope Initiate Activities Relate them to requirements Create Development baselines (optional) Initiate Parent & Child Activities Publish reusable components into catalog Relate Activities to tasks & components Specify & Plan releases Update schedule Refine: needs feasibility Interface with Project Mgt Legend Define Project Schedule & resources Change execution Change Preparation Delivery Product Configuration management Activities Mgt Reporting 11

12 Proposed ALM Project Dashboard
DRAFT [Project(s) Name] – Change Management Dashboard Number of ACRs/APRs in each status: Today the following priority is defined: # of ACRs/APRs Priority # of ACRs/APRs Unknown Low Medium High Immediate Today the following severity is defined: Status Submitted Assigned Analyzed Approved Planned On Hold Rejected Cancelled # of APRs Implemented Integrated Tested Fail Tested Solved Closed over the last 6 months Severity Minor Moderate Major Critical Type of the Requests submitted over the last 6 months: ACRs/APRs origin Evolution of # of opened ACR/APR: Valeo [# of ACRs/APRs] Customer [# of ACRs/APRs] Software Dev. Bench testing Problems [# of APRs] Changes [# of ACRs] Vehicle testing # of ACRs/APRs Software Int. Production Software Test. After Sales Hardware Unknown Time System/Product Total number of open ACRs/APRs Number of open customers’ APRs Number of open internal APRs Production

13 Workshop Choix de la solution technique Choix de la solution Pourquoi
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 A software package (included in the client ?) will periodically check the system requirements

14 Agenda Pourquoi ? 2011 Première étape 2012 Deuxième étape 2012
Troisième étape 2013 Quatrième étape 2013

15 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 A software package (included in the client ?) will periodically check the system requirements

16 Agenda Pourquoi ? 2011 Première étape 2012 Deuxième étape 2012
Troisième étape 2013 Quatrième étape 2013

17 Core ALM generic architecture
Servers (outsourced) App + Files server Lic Mgr Oracle DB Dev center (site A) File replication Library cache server Direct DB read Dev center (site B) Dev center (site B) Dev center (site B) File uploads File downloads End user Same architecture as site A End user

18 Infrastructure User desktop system requirements Local infrastructure
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 A software package (included in the client ?) will periodically check the system requirements

19 Agenda Pourquoi ? Première étape Deuxième étape Troisième étape
Quatrième étape Next steps

20 Enhancements solution will be realized and deployed in 3 stages
Infra. set up + Client upgrade 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) Stage 1. 1 (All entities) 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

21 Benefits on Resources efficiency
The future Valeo Core ALM will improve teams efficiency in different ways: Developer, Analyst, Integrator &Tester SW Project Leader Interfaces with PLM & Project Mgt tool Configuration & Change Mgt processes automation CCB live mgt in ALM Enhanced Project Mgt & SW Delivery Reduced rework (bug fixing) Reuse capabilities Benefits for all Ease to find data Reduced data double entry 24/7 User support SW Quality Manager Reduced rework Improved traceability Process driven & traced Automatic Baseline comparison

22 Gains in efficiency have been calculated following a conservative ramp-up
Stage 1.2 Stage 1.1 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%.

23 Planning Kick-off T0 + 6 months T0 + 1 year T0 + 18 months T0 Today
IAR Stage1.0 Go-no Go Centralized CDV platform Secured response time Key: Stage 1.1 Go-Live CDV Pilot Go-live Stage 1.2 Infra def + dev Pilot Deployment Functional improvements SW Standards management CDV Pilot Go-live Earliest Sept, 4th PEL VIAS (remaining users) VLS PEM CIE/CIC VWM Add-ons spec 1.1 TCC Spec validated Dev Tests Pilot Deployment VIAS deployment, along PGs migrations All entities on Core ALM Spec Dev Tests Pilot Upgrade Further functional improvements Interface with PLM target 23

24 24


Télécharger ppt "Core ALM Program Didier Balmette Jan 31st, 2013."

Présentations similaires


Annonces Google