通用汽车GVDP全球整车开发流程原版.ppt_第1页
通用汽车GVDP全球整车开发流程原版.ppt_第2页
通用汽车GVDP全球整车开发流程原版.ppt_第3页
通用汽车GVDP全球整车开发流程原版.ppt_第4页
通用汽车GVDP全球整车开发流程原版.ppt_第5页
已阅读5页,还剩61页未读 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

,gvdp v5.0 update don smith,22may06,this document is for internal gm use only. not to be duplicated or disclosed outside gm without approval of don smith 586-986-1983,gvdp post dsi v5.0 released 06april06 (for more information go to: / gvdp/asiapacific/index.html),gvdp pre-vpi process documentation v1.0 released 06mar06 (for more information go to: /gvdp/pre_vpi.html ),gvdp pre-vpi gvdp version 5.0,outline,pre-vpi and post-vpi global gvdp 5.0 background high level framework process agreements process agreement detail 5.0 content program framework architecture & program work structure gvdp 5.0 assumptions & enablers process documentation,pre-vpi and post dsi gvdp,pre-vpi gvdp “bolts-on” to the beginning of the rest of the gvdp for individual programs and supplies needed deliverables at dsi,program development,architecture framing,architecture engineering,architecture refinement,program framing/ architecture development,portfolio plan development,program execution,current arch?,vpi,vdr,sorp,pfi,afi,to ensure quality execution.,assi,aa,dsi,ac,architecture framing initiated,architecture statement of strategic intent,program framing initiation,architecture approval,document of strategic intent,architecture confirmation,vehicle program initation,verified data release,start of regular production,what is pre-vpi gvdp?,pre-vpi gvdp is gms integration of architecture development and program development,pre-vpi gvpd is global is a documented process accommodates multi-market architectural development similar to global epsilon accommodates the newly defined global portfolio process provides timing guidance for architecture and program development (start and end points) defines required decision points and approval forums (governance),pre-vpi gvdp overview,architectural approval,document of strategic intent,architecture statement of strategic intent,vehicle program initiation,pfi,yes,no,arch. framing initiation,afi,vpi,1 mth,arch. mods?,program framing initiation,portfolio development,program framing,architecture framing,engineering & execution,architecture refinement,program development,5-6 mo.,6-7 mo.,6-7 mo.,6 mo.,6 mo.,ongoing,assi,aa,ac,dsi,architectural confirmation,pfi,vpi,1 mth,program framing,program development,5-6 mo.,6-7 mo.,dsi,lead program (e.g. vectra),derivative program(s) (e.g. gmx 353, gmx 354),no architecture modifications (outside of bandwidth) (e.g. gmx211,gmx272, gmx386),new/modified architecture (e.g. epsilon, gamma, delta),afi-ac key program deliverables,architecture framing,engineering & execution,architecture refinement,afi,global market & arch. requirements bandwidth of physical dimensions/proportions arch. boundary conditions (material cost & investment) body styles mainstream architecture configuration/packaging load path strategy key architectural bom rows selected baseline powertrain plan (engine/trans. families, drive types) proportional model(s) sourcing strategy manufacturing strategy,virtual performance assessment virtual package assessment underbody 3d math model global adv plan allowable costs sor development sourcing activities,assi,aa,ac,architecture imperatives architecture cost status virtual architecture assessment proportions / integrated packaging systems & component concept solutions proportional model early supplier involvement manufacturing concept,capability of arch. & bandwidths defined,architecture capability confirmed virtually,architecture solution defined,initial participating regions and programs initial engineering requirements regulatory performance etc.,initial arch. objectives identified,program framing,the purpose of program framing: develop common program vision and objectives with leadership translate customer and corporate requirements into technical requirements understand the engineering solutions within the existing architecture modifications as required within existing bandwidths develop the compatible boundary conditions captured in the dsi,program planning/ architecture adaptation,program framing,portfolio development,target exploration workshop,program framing kickoff,document of strategic intent,program framing complete,program definition complete,ongoing,program framing initiation,pfi,dd,dsi direction,gvdp,pfc,pdc,5-6 months,dsi,approves “kick-off” of program dsi development confirms pfi inputs: “big idea” and strategic role in portfolio architecture program scope and timeline body style and brand assumptions potential powertrain families and drive configurations initial capital and engineering workload assumptions primary region(s) of sale potential issues authorizes resources (core pet),regional avdlt or gpdc (if required),dsi prep,program framing,program framing kickoff,document of strategic intent,program framing complete,program framing,program definition complete,ongoing,program framing initiated,pfi,dsi direction,pfc,pdc,dd,target exploration workshop,gvdp,5-6 months,dsi,portfolio development,create and assess program alternatives develop organizational alignment concerning scope, vision, and key objectives (key wins, price of entry items) establish program targets and boundary conditions program positioning preliminary content (including powertain, key technologies) financial boundary conditions design enablers manufacturing footprint develop & verify high level engineering solutions that will meet existing bill of architecture (boa),dsi prep,global portfolio planning,global vdp 5.0 background,product development leadership direction to shorten time between vpi and sorp reduction based on gelt led studies of gmdat and toyota lead time advantages. study concluded: gms global vdp lead times lag toyotas by several months toyotas enablers: decoupled development, overlapping functional work and fast functional processes dsi to sorp advantage of about 4 months gmdat lean vdp faster for in-country products actual gvdp 5.0 reduction is 15 weeks (37/20 to 33/20) for new and major vehicle programs. reduction moves single theme math 15 weeks closer to the market. gvdp 5.0 was released for programs with a document of strategic intent (dsi) on or after june 1, 2006, and for select programs earlier existing 4.1 programs will not be updated to 5.0 logic or timing. additional studies are being conducted to develop shorter templates for derivative programs gvdp pre-vpi released for use on 06mar06 creates deliverables important to executing gvdp 5.0,gvdp 5.0 release announcement 07april 06,all, following an initiative sanctioned by the global product development council (gpdc), global engineering leadership team (gelt) and global joint engineering and manufacturing staff (gjems) to shorten product development lead time, we are pleased to announce the release of the global vehicle development process (gvdp) 5.0. this release improves vpi-sorp timing, for new and major programs, from 37 months to 33 months, and moves styling 15 weeks closer to market introduction. gvdp 5.0 is directed at programs with document of strategic intent (dsi) dates after june 1, 2006, and several select (slightly earlier) programs where partial implementation will occur. regards, rick spina executive director global program management,gvdp 5.0 framework 33/20,theme development,idr,vdr,-112,design arm,sourcing,sor,b,ct,procure parts,fg,cv design solution,fg,sv design solution,process/ formability,construct / verify dies,b,ct,procure parts,iv design solution,fg,dta,-163,ad,-155,design dies,mvb s,mvb ns,ppv,design body shop tools,construct/ verify body shop tools,-15,ped pro mule,mules,vpi-sorp 15 week reduction from gvdp 4.1,-148,std,dsi-sorp overall leadtime is within 6 weeks of toyota,functional processes have been adjusted, added, or refined: styling & surfacing mules sourcing dies and bodyshop tooling pedestrian protection ppap end-of-line test iterative matching etc.,dsi,-181,idr,vdr,-112,design arm,sourcing,sor,b,ct,procure parts,design anrm,sourcing,sor,b,ct,procure parts,theme development,fg,cv design solution,fg,design solution,iv design solution,fg,sv design solution,process/ formability,design dies,construction / verify dies,b,ct,procure parts,fg,sf,-116,psd,-121,gvdp 4.1 framework 37/20,mvb s,mvb ns,pvv,design body shop tools,construction / verify body shop tools,styling,mules,iv,engineering design,manufacturing / launch,to show how time was removed for 5.0, lets build the framework starting with 4.1,dsi,-166,idr,vdr,-112,theme development,fg,cv design solution,fg,sv design solution,process/ formability,design dies,construction / verify dies,b,ct,procure parts,build one,mvb s,mvb ns,ppv,construction / verify body shop tools,design body shop tools,styling,mules,iv,engineering design,manufacturing / launch,enabled by: increased sketch work done pre-dsi revised definition of idr requirements earlier sourcing of dc 12 components revised dfp schedule,std,-148,idr,vdr,fg,cv design solution,fg,sv design solution,process/ formability,design dies,construction / verify dies,b,ct,procure parts,build two,mvb s,mvb ns,ppv,construction / verify body shop tools,design body shop tools,styling,mules,iv,engineering design,manufacturing / launch,dta,-163,ad,-155,theme development,std,-148,idr,vdr,design,sourcing,sor,b,ct,procure parts,fg,cv design solution,fg,sv design solution,process/ formability,design dies,construction / verify dies,b,ct,procure parts,build three,mvb s,mvb ns,ppv,construction / verify body shop tools,design body shop tools,vpi,styling,mules,iv,engineering design,manufacturing / launch,4.1,dta,-163,ad,-155,-112,theme development,std,-148,idr,vdr,design,sourcing,sor,b,ct,procure parts,fg,cv design solution,fg,sv design solution,process/ formability,design dies,construction / verify dies,b,ct,procure parts,build four,mvb s,mvb ns,ppv,design body shop tools,construction / verify body shop tools,overlap of me activities with engineering design,styling,mules,iv,engineering design,manufacturing / launch,must adhere to idr data approximately 1mm to vdr or as restricted by the red / blue process,dta,-163,ad,-155,-112,theme development,std,-148,key gvdp 5.0 process agreements,gvdp 5.0 assumptions and enablers (link) gvdp 5.0 modification restrictions (link) lead time reduction changes lengthening of dsi-vpi process styling & surfacing process change mule stream pull-ahead relative to vpi overlapping of me activities with engineering design process additions / refinements / clarifications ppap process end of line testing ped pro iterative matching pqrr process additional changes,lengthening of dsi-vpi process,currently 22 weeks,dsi,-172,theme,alternatives,develop single theme alternatives,dsi,-181,ad,-166,dta,-172,theme,alternatives,develop single theme,+4,+2,gvdp 4.1,gvdp 5.0,4 additional weeks to develop themes 2 additional weeks for engineering assessment of clinic input (not design driven),vpi,-144,single theme,develop theme,dsi document of strategic intent std single theme direction dta design theme alternatives vpi vehicle program initiation ad alternatives development,added 6 weeks,lengthening of dsi-vpi process,gvdp 5.0,what has changed? 4 weeks added between dta and the std 2 weeks added between std and vpi why has it changed? 4 weeks, enables a more robust design “styling“ process by allowing additional time to create and optimize multiple themes to a given set of architectural criteria with increased fidelity of the design surfaces. 2 weeks, for engineering assessment of the single theme decision outcome and to allow for management reviews (engineering and program management driven) what does this mean to program teams? clinic properties will have the benefit of a more robust and comprehensive theme development process higher fidelity theme at single theme direction additional time to complete business case and charter document at vpi additional time for management reviews,dsi,-172,theme,alternatives,develop single theme alternatives,added 6 weeks,+4,+2,vpi,-144,single theme,dsi document of strategic intent std single theme direction dta design theme alternatives vpi vehicle program initiation ad alternatives development,styling & surfacing process change,idr,vdr,interior,uppers,doors,fenders & quarter panels,hood & decklid,fascias/lamps/grilles/moldings,-113,-105,-88,-121,-113,-101,-119,-117,-117,-115,-110,-106,-106,-102,-97,-98,-98,-98,gvdp 4.1,idr,vdr,gvdp 5.0,-116,-106,-90,interior,-116,-106,-96,metal,-116,-106,-94,fascias/lamps/grilles/moldings,dsi,-172,theme,alternatives,develop single theme alternatives,theme,alternatives,develop single theme,std- single theme direction dso design sign offf std-md single theme direction math data sf styling freeze dta design theme alternatives vpi vehicle program initiation psd preliminary styling data idr initial data release ad alternatives development eso engineering sign off cso contact sign off vdr verified data release,ta,-115,styling & surfacing process change,what has changed? theme development has been reduced by 16 weeks (std to sf) single theme math is now 15 weeks closer to the market idr/vdr activities consolidated (6 to 3) and moved to single idr time between dso and sf reduced by 8 weeks preliminary styling data (psd) & theme approval (ta) have been removed why has it changed? enabled by higher fidelity theme at std due to added time between dsi & vpi idr/vdr work stream consolidation now aligns more closely with interdependent surface development single idr and proximity of dso and sf eliminates need for psd theme approval not a separate milestone and essentially occurs at dso. final design reflected in sf 4 weeks later what does this mean to program teams? earlier decisions required (relative to vpi) to support earlier styling critical sourcing less time between std and sf reduces the opportunity for iterations, reducing the program teams ability to make changes post dso less potential change after idr since panels are developed simultaneously before idr release easier tracking of surface releases requires rigorous adherence to r/b process for idr/vdr surface change management (formerly r/b/g process) critical for inner metal release integrity, iv fidelity, and overlap with me workstream,idr,vdr,gvdp 5.0,-116,-106,-90,interior,-116,-106,-96,metal,-116,-106,-94,fascias/lamps/ grilles/moldings,dsi,-172,theme,alternatives,develop single theme alternatives,clinic,dsi document of strategic intent std- single theme direction dso design sign offf sf styling freeze dta design theme alternatives vpi vehicle program initiation psd preliminary styling data idr initial data release ad alternatives development eso engineering sign off cso contact sign off vdr verified data release vdrsm vdr sheet metal std md single theme direction math data,sourcing of styling critical components,gvdp 5.0,dsi,-172,clinic,dcs,-127,-147,cluster,design center has eliminated 16 weeks (std-sf) to enable 5.0. this is a 40% reduction in the amount of styling time design timing reductions based on key suppliers selected at designated times sourcing timing is driven by need for styling to work with suppliers to develop criteria before eso,sor,-104,final soln,design,-140,b,ct,procure parts,-113,final soln,-124,-105,-137,-165,gvdp 5.0,arc,-151,sourcing,-172,dsi document of strategic intent cver concept vehicle engineering release vpi vehicle program initiation sver structure vehicle engineering release arc architecture refinement complete vdr verified data release,mule stream pull-ahead relative to vpi,sor,what has changed? mule process consolidated to common biw, non-running and running workstream first mule complete (fmc) wk -121, first running mule available 2 weeks later at wk -119 biw, non-running & running mules moved earlier relative to vpi new milestone (arc architecture refinement complete) why has it changed? mules are not driving timing post vpi (design center and powertrain calibration are) pulling mules ahead relative to vpi accommodates reduced time post-vpi arc required to confirm architecture components stability confirm the refinement of the architecture prior to sourcing of architecture components allows production sources to start mule design and tooling prevents cost creep due to late changes what does this mean to program teams? architecture and powertrain decisions including initial powertrain ssts must be frozen at dsi -4 design concept sheets for long lead chassis components start dsi -7 program ladv planning starts significantly earlier (dsi) to enable planning & execution of dsi to vpi adv activities consolidated mule stream more consistent with ppo build activities,mule stream pull-ahead relative to vpi,-104,final soln,-140,-113,cver,-109,final soln,gvdp 5.0,design,b,ct,procure parts,-124,-105,-137,-165,sourcing,dsi document of strategic intent cver concept vehicle engineering release ladv learning analysis development & validation ppo pre production operations sver structure vehicle engineering release biw body in white arc architecture refinement complete vdr verified data release ssts subsystem technical specifications sor statement of requirements ct critical test b- build,sor,what has changed? most chassis sources are on-board before vpi source selection now overlaps with component design by source why has it changed? supports the mule build mrd which is now closer to vpi overlapping of sourcing & component design work allows sourcing after vpi for selected chassis components enables design competition between sup

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论