1GVDP v5_Upd_trg.ppt/Don Smith/5/22/2006/version 6.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEXGVDP v5.0 Update Don Smith22MAY06This document is for internal GM use only. Not to be duplicated or disclosed outside GM without approval of Don Smith 586-986-19832GVDP v5_Upd_trg.ppt/Don Smith/5/22/2006/version 6.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEXGVDP Post DSI v5.0 Released 06April06 (for more information go to: http:/vdp.gm.com/ gvdp/asiapacific/index.html)GVDP Pre-VPI Process Documentation v1.0 Released 06MAR06 (for more information go to: http:/vdp.gm.com/gvdp/pre_vpi.html )GVDP Pre-VPI GVDP version 5.03GVDP v5_Upd_trg.ppt/Don Smith/5/22/2006/version 6.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEXOutline Pre-VPI and Post-VPI Global GVDP 5.0 Background High level framework Process Agreements Process Agreement detail 5.0 content Program Framework Architecture ADTs in one Global ADTs are led by Global VLEs and ADTs are lead by regional VLEs (G)ADTs are responsible and accountable for architecture and common components regardless of the program or region of application (G)ADTs are also responsible for the profitability of all programs regardless of region The Global Segment Director (GSD) from Planning leads the development of the ASSI and DSI document in support of the (G)ADT50GVDP v5_Upd_trg.ppt/Don Smith/*/version 5.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEX(Global) Architecture Development Team Member Responsibilities Lead cross-functional (G)ADTs Responsible for all programs on an architecture regardless of region The (G)VLE is responsible for program profitability in its entirety prior to SORP Interface between (G)ADT and Corporate leadership forums (e.g., APB, VPR) Responsible for the confirmation and achievement of imperatives for all programs through Charter/Contract and Scorecard Lead Engineering integration through Vehicle and Process Integration Review (VAPIR) for all programs on an architecture Ensure translation of program requirements into technical specifications Manage engineering budget for programs Ensure compliance to government regulations Execute program to meet imperatives Chief of Staff for VLE Drive decision making and issue resolution Supervisor of the Program Managers Manages across programs Manages program timing Manages program content Communicates status of Program Imperatives/Targets/MetricsGlobal PMGlobal QualityGlobal Mfg. CEGlobal VLEGlobal FinanceGlobal VCEGlobal DesignetcGlobal HRGlobal PurchasingNote: VLD is a member of the (G)ADT; see PET slide for VLD responsibilities51GVDP v5_Upd_trg.ppt/Don Smith/*/version 5.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEXRegional Program Execution Team (PET) attributes Regional programs (chaired by a VLD) will be executed by regional PETs that are initiated by and report to the (G)ADT With (G)ADTs, PETs will be expected to execute multiple programs A Regional PET is required when a lead or derivative product is either engineered or assembled (greater than CKD) in the region Lead program PET will normally be in the same region as the (G)ADT Regional PETs should be staffed as early as PFI if possible, and must be fully staffed by DSI at the latest (previously VPI); where necessary, Portfolio resources (formerly DSI Core Teams) may be used until PFI Functional members of Regional PETs have reporting relationships to functional (G)ADT leaders Regional PETs develop and execute the program Charter and Contract and make recommendations to the (G)ADT on key program decisions52GVDP v5_Upd_trg.ppt/Don Smith/*/version 5.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEXArchitecture PET attributes An Architecture PET is a working level body, enabling the GADT to focus on decision making, and will reside in the same region as the GADT. An Architecture PET should only be required for architectures with many body styles across many regions Members of the Architecture PET may include: Program Management Director (Chair) GADT Managers from appropriate functions Regional Vehicle Line Directors Program Engineering Managers / Assistant Chiefs Program Managers The Architecture PET may support the GADT by managing common activities and issues and/or defining programs prior to the creation of the PETs The Architecture PET may evolve into the PET for the lead program Some flexibility is needed in the application of these attributes as we continue to improve our understanding of the need for this team53GVDP v5_Upd_trg.ppt/Don Smith/*/version 5.0Once printed this document is UNCONTROLLED, please refer to http:/vdp.gm.com/gvdpINDEXDecision Rights Summary Architecture &