1 / 31

PALMA Steering Committee #20, February 21 th 2008

PALMA Steering Committee #20, February 21 th 2008. Agenda. Agenda. PALMA Roadmap D3S Organization & Workload Major Issues GISD Palma Project Palma Maintenance Palma V2.0 Build Palma V2.1 Spec/Build Palma Adoption Project DLJ DSA/SR TAS TADL Uk DLJ/TOL Uk

dirk
Download Presentation

PALMA Steering Committee #20, February 21 th 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. PALMA Steering Committee #20, February 21th 2008

  2. Agenda Agenda • PALMA • Roadmap • D3S Organization & Workload • Major Issues • GISD Palma Project • Palma Maintenance • Palma V2.0 Build • Palma V2.1 Spec/Build • Palma Adoption Project • DLJ • DSA/SR • TAS • TADL Uk • DLJ/TOL Uk • Palma Opportunities • D3S/TSS-TRSS

  3. PALMA Roadmap on visibility SRS & IRS V1 SRS & IRS V2.0 Design SRS V2.1 Build PDMLink V1.0 V1.1 V1.2 V2.0.beta .1 .2 .3 .4 V2.1..x Adopt PDMLink TSS: 1.1 DLJ (TOL) DLJ 2.x TADL: 2.0 DSA, TUS, DAE ? V1.0 V1.1 V1.2 - 1.3 V1.4 Build Teamcenter V1.x Adopt Teamcenter DSA-SR: 1.1 -------------------- 1.3 1.4 DSA, TUS, DAE ? StudyGap Analysis DSA DAE Not Confirmed / Possible Candidate or Start-date not stabilized yet Confirmed

  4. PALMA Core Organization Group Operations Director Reynald Seznec Business Rep.Lionel Sauter Chief Inf. OfficerPatrick Anglard Functional LeaderOlivier Rives Group Process Owner Rep.Claude Masia DOPS PALMA Project ManagerCyril Piltan Key users LeaderBruno Michal Program ManagerStephane el Mabrouk G I S D Program Manager E. Viero D3S PALMA Adoptions Support Leader A. Franzese Program Manager Support A. Franzese D3S Core Project C. Villeneuve PDMLink Design Leader C. Villeneuve / S. Turlet PDMLink Build Leader D. Polzin TeamCenter Build Leader C. Servoz Maintenance Leader D. Olier / C. Servoz PALMA Technical/Functional Core Team PALMA Adoptions Support Team Software Vendors: UGS - PTC PALMA Back Office, InShore, OffShore Engineering: Methodology, Process, Tools, …

  5. PALMA Adoption Organization Group Operations Director Reynald Seznec Business Rep.Lionel Sauter Chief Inf. OfficerPatrick Anglard Functional LeaderOlivier Rives Group Process Owner Rep.Claude Masia DOPS PALMA Project ManagerCyril Piltan Key users LeaderBruno Michal Program ManagerStephane el Mabrouk G I S D Program Manager Eric Viero D3S PALMA Adoptions Support Leader A. Franzese Program Manager Support Antoinette Franzese DLJ/TOL – DSA/TADL Project Manager N. Adewale DLJ Project Manager S. Turlet DSA/SR Project Manager C. Servoz DSA/SR Project Manager C. Servoz PALMA Local Team PALMA Local Team PALMA Local Team PALMA Adoptions Support Team Software Vendors: UGS - PTC PALMABack Office, InShore, OffShore Engineering: Methodology, Process, Tools, …

  6. PALMA - Workload Core/Adoption Team Reports & UI enhancements 7 new PLM resources on one month 1 new UK Adoption Project 1 new UK Adoption Project

  7. PALMA Major Issues • No visibility on the Global PALMA Adoption RoadMap • D3S Top Management Approach: • We asked to PTC a strong partnership on a global PALMA Roadmap on 3 years plan. • PTC is OK on this approach • We have been waiting the answer of THALES Group with this approach • D3S asks to have a dedicated Steering Commitee PALMA for each Adoption Projects and a Global Steering Commitee to drive to PALMA Program Organization Issues

  8. PALMA Maintenance GISD: PALMA Maintenance • Order 2008 No commitment today • Project Status: On track with a strong activity • PCR Updated since 2008/01/01 • PALMA PDMLink : 82 PCRs (32 bugs + 45 evolutions + 5 support actions) • PALMA TeamCenter : 43 PCRs (10 bugs+ 30 evolutions + 2 support actions) • Issues: • The PALMA Reports WorkPackage must begin ASAP • Actions: GISD must choose the technical solution on w9. • A solution for the Doc Mng & UI enhancement must be done • Actions: D3S analyses in progress on w8 • PALMA V1 Functionnal Perimeter always open • Actions: GISD must close the functionnal perimeter • Risks: • Impact on DLJ Planning – PALMA V2.0 perimeter always open • Actions: The PALMA V2.0 perimeter must be closed at the end of march. The maintenance activity is fully supported by a change management process and controlled with the JIRA tool

  9. Dashboard activity 2 1 1. Constant evolution of new PCRs 2 : Many PCRs “To Be Tested”. Qualification synchronized with PALMA V2.0.3 Dashboard actity

  10. PALMA V2.0 GISD: PALMA V2.0 – Build • Order 2008 OK • Project status: • PALMA V2.0.3 in progress … • Qualification planned on W13 • Issues • Maturity and complexity of PALMA V2.0 (AsPlanned, AsBuilt …) • Actions: Many workshops and PALMA Versions done by D3S • Risks • Impact on planning - Choice of Infrastructure availability for the qualification phase • Actions: D3S preconise to use the current Maintenance Platform • Delay to incorporate new PCRs on the PALMA V2.0 Functional Scope • D3S remarks: • No new evolutions PCRs after end of march for the last version of PALMA V2.0.4 planned in June. The evolutions identified between now and the end of march must be compliant with the DLJ delivery and constraint PALMA V2.0 Build: Project with major domains on track

  11. PALMA V2.0 Main Milestones and WorkPackage Progress 2 weeks of delay but PALMA V2.0.3 includes new PCRs & the CodeBar functionality on the As-Built domain New version to include the PCRs between February – April and compatible in term of charges versus D3S team PALMA V2.0.3 Qualification on W13

  12. PALMA V2.1 GISD: PALMA V2.1 – Spec/Build • Order • PALMA V2.1 – Spec: OK • PALMA V2.1 – Build: On going • Project status: • PALMA V2.1: Specification baselined except Exindus. A SSR must be planned on w10 • Estimation done by D3S on the Non-Conformance; e-Dir; AsMntLight on this last Specification baselined. • Assessment with PTC to share the content of the estimation • Issues • Full V2.1 workload not compatible with the DLJ planning and with the OOTB approach • Actions : • GISD - Simplification of many requirements at the Core Level done (except Exindus). • Assesment with PTC to share the content of the estimation – on going • GISD/DLJ/D3S - Definition of a critical functional scope necessary for the first deployment of DLJ on w10. PDMLink : D3S Assumption V2.1.0: June 2008 (BDF2): “Non Conformance” (impacted DLJ Training), “Exindus light” (specification are waiting from DLJ and validated by GISD), V2.1.1: September2008 (DBF3) : Full “Non Conformance”, Edir” (limited to the user data management) End 2008/Begin 2009 : AsMntLight, ToBeApplied, Exindus TeamCenter : “To Be Applied” • Risks • Impact on the DLJ planning

  13. PALMA Core – Major Issues PALMA Core: Major Issues • No template of a Migration Strategy and no PALMA Loaders developed and optimized on PALMA V1 et V2.0 which can be used on the Adoption Projects • Actions: D3S organize a Meeting with PTC. • GISD/D3S - A dedicated sub-project must be identified at the Core Level on w10. The objective is to share and mutualize the workload on this activity and, to secure the migration phase for each Adoption Projets. • No Architecture & Performance Study on PALMA • Actions: D3S has organize a Meeting with PTC & DLJ. • Issue on the availability of PTC expertise • GISD must decide on this topic. • PTC want/need a remote access to PALMA (TBC) Migration & Architecture Issues

  14. DLJ PALMA Adoption Project DLJ PALMA Adoption Project • Order • WP 2a: Adoption of PALMA V1 Perimeter - Build OK • WP 2b: Adoption of PALMA V2.0 Perimeter – Spec D3S offer sent – waiting • WP 2c: Adoption of PALMA V2.0 Perimeter on going • Issues: • Architecture Domain • Actions: first PTC proposal not acceptable for the planning (April) • Migration Domain: Many issues due to the development in // of the PALMA Loader & DLJ adaptation + no reference on this activity + bugs on the standard loader. • Actions: see PALMA Major Issues • Integration Domain: Activity/Responsability scope must be clarified. • Actions: D3S/DLJ meeting to define the WBS on w9 • Interactive Domain: Gap Analysis of PALMA V2.0 important in term of workload and not compatible with the DLJ planning and the Core OOTB • Actions: D3S - Presentation of the workload on w9 • DLJ/GISD must validate the content (“Gamme Mng”, ...) on w9

  15. DLJ PALMA Adoption Project DLJ PALMA Adoption Project • Risks: • Architecture Domain: Delay of Architecture study due to the constraint of availability of the PTC expertise • Actions: D3S works with PTC to reduce the delay • Migration Domain: Impact on global planning • Actions: Follow the migration planning and report daily between DLJ and D3S in a dedicated projet • D3S - see PALMA Major Issues • Integration Domain: • Actions: D3S: provide proposal including scope, perimeter and responsibility • Interactive Domain: 1. Gap between the local DLJ requiremrents and the Core OOTB approach • Actions: cf. Actions on Issues • 2. Functionnal scope always open • Actions DLJ/D3S - SSR on each domain specified during the Lot2b phase and consistante with the planning

  16. DLJ PALMA Adoption Project DLJ PALMA Adoption Project Planning V1 perimeter: On time on the Interative Module Migration : As Specified / As Designed Chang Product Review 10/03/2008 Migration : Change Management Chang Product Review 09/04/2008

  17. DLJ PALMA Adoption Project DLJ PALMA Adoption Project Planning V2 perimeter: Lot 2C Gap Analysis development workload not included inside the planning for the time Lot 2C Development workload includes only the current proposal

  18. DLJ PALMA Adoption Project DLJ PALMA Adoption Project Main Milestones Progress V1 perimeter:

  19. DLJ PALMA Adoption Project DLJ PALMA Adoption Project Main Milestones Progress V2 perimeter:

  20. DSA/SR Adoption Project DSA/SR Adoption Project (PALMA V1.3 build TeamCenter 2005) • Order • P0’ – P1’ : on going • Project Status: • Project on track • V 2.1 domain “To be applied” : Estimation in progress • Issues: • No visibility on the Global project planning ? • Actions: DSA/SR • Risks: • Impact on planning: Deployment on distributed system • PALMA has never been qualified on distributed system. Topic following by SIEMENS and SR/NL • Actions: D3S has delivered on W8 the PALMA DSA/SR current version • Good ressouce at the good time • Actions: SR/NL must communicate on the global project planning P0’ requirements qualified on W08 P1 requirements qualified on W12

  21. DSA/SR Adoption Project DSA/SR Adoption Project Main Milestones and WorkPackage Progress: Go Live planned on W12

  22. TAS PALMA Adoption Project - PEGASE TAS Adoption Project (PALMA V2 PDMLink V9 2008) • Order • Gap Analysis - Phase 1 : OK • Implementation – Phase 2: On going • Project Status: • PALMA Gap Analysis – Phase 1: As-Designed perimeter; SRS Draft - ARD Draft (Architecture Study); Migration Study • Issues: • TAS users involvement (Functional and Architecture): Workshops Planned with impact on planning – Difficulties in gathering functional inputs to support As-Designed workshops (workshop input preparation). • Actions: Red Flag bring up by C. Chauvin (TAS Chef de service IS). • Launch Phase 2 before ARD review in order to minimize planning impact • TCIS data availability: All components will not be loaded on time in TCIS • Actions: Prioritize dataset to be loaded • Risks: • Impact on planning – Operational deployment delayed • System acceptation by users • Actions: TAS decisional review planned at the end of phase 1 with business key users hierarchy Standard adoption on target – No Gap identified so far Architecture study most probably not completed before phase to start up 2 weeks delay on phase 1

  23. TAS PALMA Adoption Project - PEGASE TAS PALMA Adoption Project - PEGASE Planning: 2 weeks delay (to be confirmed at the end phase 1)

  24. TAS PALMA Adoption Project - PEGASE TAS PALMA Adoption Project - PEGASE Main Milestones and WorkPackage Progress: To be consolidated in Phase 2 offer review Phase 2 offer review planned on W14

  25. TADL PALMA Adoption Project TADL Adoption Project (PALMA V2 PDMLink V9 2008) • Order • Gap Analysis – Phase 0 OK • SPEC/BUILD – Phase 1 negociation in progress • Project Status: • Gap Analysis in progress • Review of the SSS and Architecture study must be done on w9 • Issues: • Offer negociation not closed. • Actions: TADL/ D3S Progressing project on a T&M basis until offer signed off. • D3S - Colin Ward (D3S Account Manager) is in active negotiation with TADL to resolve this commercial issue. Objective: a commitment on w9 • Risks: • Potential impact on planning caused by delay in system hardware procurement as unable to procure hardware until offer is signed off (D3S UK Finance Process) Standard adoption on target – No Gaps identified so far Delay in offer sign off could impact planning PALMA V2.0 + TOL Workflow/Reports/Loader as target

  26. TADL PALMA Adoption Project – Phases 0 & 1 TADL PALMA Adoption Project Planning:

  27. TADL PALMA Adoption Project – Phases 0 & 1 TADL PALMA Adoption Project – Phases 0 & 1 Main Milestones and WorkPackage Progress:

  28. DLJ/TOL PALMA Adoption Project DLJ/TOL Adoption Project (PALMA V1 PDMLink V8) • Organisation : Project Mng: N. Adewale/M. Pearson D3S / E. Goodwillie TOL • Project Status: • PALMA v1 adoption - As-Designed and MCAD integration perimeter • -Migration: New offer requested by TOL end of 2007 to implement changes to migration scope and then to redo extraction and production load of component library and Go-Live product data. • Custom Reports: Additional functional requirements and fixes implemented by A. Laurenco and I. Cagnieux at end of 2007. Still some outstanding issues. • New requirement from TOL for D3S to propose a solution to resolve some key MCAD integration usability issues. Storyboard documenting requirement sent to PTC for comment. • Issues: • Currently no planned date for system Go-Live. • Actions: • GISD must organise ASAP a conference call with GISD, D3S, DLJ and DLJ/TOL • Risks: • Addition of new functionality could further delay Go-Live. • Credibilty on the PALMA Program

  29. DLJ/TOL PALMA Adoption Project – Data Migration DLJ/TOL PALMA Adoption Project – Data Migration Planning:

  30. DLJ/TOL PALMA Adoption Project – Data Migration DLJ/TOL PALMA Adoption Project – Data Migration Main Milestones and WorkPackage Progress:

  31. D3S/SR Adoption Project D3S/TSS Adoption project : El@n (PALMA V1.2 - PDMLink 8) • Organisation : RUN Mng: D. Olier • Project Status: • - RUN activity on track • Issues: • Risks: • - Project without support of the Top Management • Opportunities: • To use the el@n system for a dedicated TRS Program (Ligne 13 – Contact: F. Ropars) • - Action: el@n qualification platform accessible. Internal qualification in progress with some TRS actors Opportunity to use @elan directly by TRS for a dedicated program

More Related