最新形态控制-批量生产(PPT)PPT课件.ppt

《最新形态控制-批量生产(PPT)PPT课件.ppt》由会员分享，可在线阅读，更多相关《最新形态控制-批量生产(PPT)PPT课件.ppt（36页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、进入夏天，少不了一个热字当头，电扇空调陆续登场，每逢此时，总会想起进入夏天，少不了一个热字当头，电扇空调陆续登场，每逢此时，总会想起那一把蒲扇。蒲扇，是记忆中的农村，夏季经常用的一件物品。记忆中的故那一把蒲扇。蒲扇，是记忆中的农村，夏季经常用的一件物品。记忆中的故乡，每逢进入夏天，集市上最常见的便是蒲扇、凉席，不论男女老少，个个手持乡，每逢进入夏天，集市上最常见的便是蒲扇、凉席，不论男女老少，个个手持一把，忽闪忽闪个不停，嘴里叨叨着一把，忽闪忽闪个不停，嘴里叨叨着“怎么这么热怎么这么热”，于是三五成群，聚在大树，于是三五成群，聚在大树下，或站着，或随即坐在石头上，手持那把扇子，边唠嗑边乘凉。孩

2、子们却在周下，或站着，或随即坐在石头上，手持那把扇子，边唠嗑边乘凉。孩子们却在周围跑跑跳跳，热得满头大汗，不时听到围跑跑跳跳，热得满头大汗，不时听到“强子，别跑了，快来我给你扇扇强子，别跑了，快来我给你扇扇”。孩。孩子们才不听这一套，跑个没完，直到累气喘吁吁，这才一跑一踮地围过了，这时子们才不听这一套，跑个没完，直到累气喘吁吁，这才一跑一踮地围过了，这时母亲总是，好似生气的样子，边扇边训，母亲总是，好似生气的样子，边扇边训，“你看热的，跑什么？你看热的，跑什么？”此时这把蒲扇，此时这把蒲扇，是那么凉快，那么的温馨幸福，有母亲的味道！蒲扇是中国传统工艺品，在是那么凉快，那么的温馨幸福，有母亲的味

3、道！蒲扇是中国传统工艺品，在我国已有三千年多年的历史。取材于棕榈树，制作简单，方便携带，且蒲扇的表我国已有三千年多年的历史。取材于棕榈树，制作简单，方便携带，且蒲扇的表面光滑，因而，古人常会在上面作画。古有棕扇、葵扇、蒲扇、蕉扇诸名，实即面光滑，因而，古人常会在上面作画。古有棕扇、葵扇、蒲扇、蕉扇诸名，实即今日的蒲扇，江浙称之为芭蕉扇。六七十年代，人们最常用的就是这种，似圆非今日的蒲扇，江浙称之为芭蕉扇。六七十年代，人们最常用的就是这种，似圆非圆，轻巧又便宜的蒲扇。蒲扇流传至今，我的记忆中，它跨越了半个世纪，圆，轻巧又便宜的蒲扇。蒲扇流传至今，我的记忆中，它跨越了半个世纪，也走过了我们的半个人

4、生的轨迹，携带着特有的念想，一年年，一天天，流向长也走过了我们的半个人生的轨迹，携带着特有的念想，一年年，一天天，流向长长的时间隧道，袅长的时间隧道，袅形态控制-批量生产(PPT)Overview of CMvRequirement&DefinitionvIntroduction to CM mainframevCM PlanningvCI,CC,CSA&CAvBusiness opportunity2vConfiguration identification(CI):Entity within a configuration that satisfied an end use functio

5、nvProduct configuration information:Requirements for product design,realization,verification,operation and support(comprises both product definition&product operational information)9vConfiguration status accounting(CSA):Formalized recording and reporting of the established configuration documents,th

6、e status of proposed changes and the status of the implementation of approved changesvConfiguration item(CI):Aggregation of hardware,software,processed materials,services,or any its discrete portions,that is designed for configuration management and treated as a single entity in the CM process10Obje

7、ctives vTo document and provide full visibility of the products present configuration and on the status of achievement of its physical and functional requirements.Another objective is that everyone working on the project at any time in its life cycle uses correct and accurate documentation11CM Proce

8、ssvConfiguration identificationvChange controlvConfiguration status accountingvConfiguration auditing12Organization of CMvCM should be organized with defined responsibilities and sufficient independence and authority to achieve the required CM objectives13Configuration boardvIt has the correct autho

9、rity in relation to the relevant configuration baselines14CM plans and procedurevCMP:documented,approved,controlled,procedure,defined R&A,conveyed to suppliersvFocus on customer requirements for the products,CM process be detailed in a CM planvCM plan may be a stand-alone document,or a part of anoth

10、er document,or composed of several documents15Configuration IdentificationvA family tree of product structure and selection of configuration itemsvDocumentation of configuration itemsvProduct configuration information vEstablishment of configuration baselines16Selection of CivRegulatory&statutory re

11、quirementsvNew or modified technology,design or developmentvCriticality in terms of high risks,safetyvInterfaces with other configuration itemsvSupport and service17Selection of CivProcurement conditionsvLogistics and maintenance aspectsvCIs should be initiated as early as possible in the product li

12、fe cycle 18Documentation of CivAll physical and functional characteristics necessary to define a CI throughout its life cycle should be documentedvInclude specs,design documents,list,software data,manualvCI depends on the level of control needs 19Configuration baselines vConsists of all approved doc

13、uments that present the definition of the product at a specific pointvBe established whenever it is necessary to define a reference configuration during the product life cycle which serves as a starting point for further activities20Change controlvDocument and justify the changesvEvaluate consequenc

14、es of the changevApprove or disapprove the changevImplement and verify the changevProcess deviations and waivers 21Change control procedurevAll change proposals should be documented:*Config.items&related documents to be changed,name(s)&revision status *Name of the individual preparing the proposal,t

15、he organization and date prepared *Reason&description for the change *Urgency22Evaluation of changevThe technical merits of the proposed changevThe impact on interchangeability,interfaces,and the necessity for re-identificationvThe impact on regulatory,risk,contract,schedule,cost,manufacturing,test,

16、inspection method,purchases,stocks,maintenance,user handbooks,spare parts,spare-part manuals,delivery and customer support requirements.23Dispositioning AuthorityPriortoapprovalofachange,shouldverify:vThe change is necessaryvThe consequences are acceptablevThe change has been properly documented and

17、 classifiedvThe plan for the implementation of the change into documents,HW/SW is satisfactoryvAlso be called a CCB24Approval of changevThe R&A should be definedvThe authority for approval/disapproval may vary depending on the significant of the change.vA decision concerning approval/disapproval sho

18、uld be documented and notified the relevant areas.25vThe implementation and verification of an approved change normally includes following steps:vChanges to the CI should be formally approvedvAppropriate consequential actions by the affected departments should be initiatedvCompliance should be verif

19、ied26Configuration status accountingvCSA should perform throughout the life cycle of the productvCSA should provide information of all CIs and all departures from the specified configuration baselines,it thus enables changes to configuration baselines to be traceablevCSA records and reports should b

20、e a by-product of the identification and control activities27CSA RecordsvWhen:During configuration identification and change controlvWhat:1.Products configuration information(ID,title,effective date,version,change history,part number or build status)2.Status of release of new product3.Products confi

21、guration(P/N,product design or build status)4.The processing of change28CSA RecordsvHow:8 steps1.Provide protection from corruptions or unauthorized change2.Provide means for disaster recovery3.Permit retrieval4.29ReportingvA list of configuration baselines documentsvA list of Configuration items an

22、d their configuration baselinesvCurrent configuration statusvStatus reports on changes,deviations,waiversvStatus reports on the implementation and verification of changes30Configuration audit(CA)vCA should be performed in accordance with documented procedure to assure the product complies with its c

23、ontracted or specified requirements and to assure the product is accurately reflected by its configuration documents31Configuration audit(CA)vFunctional CA:a formal examination to verify that a configuration item has achieved the performance and functional characteristics specified in its configurat

24、ion documentsvPhysical CA:a formal examination if the“as-built/produced”configuration of a CI to verify that it conforms to its product configuration documents32Configuration audit(CA)vCA may be required before the formal CA may be required before the formal acceptance of a configuration itemaccepta

25、nce of a configuration itemvNot intended to replace other forms of Not intended to replace other forms of verification,review,test or inspection,but verification,review,test or inspection,but will be affected by the results of these will be affected by the results of these activitiesactivities33Proj

26、ect phasesConfiguration management activitiesFeasibility Project definition Development Production/Operation Project phase:Review:Staff requirementsSRRSDRDDRPrototypeFirst off productionConfiguration audit:CM plan:Configuration baseline:CM activitiesCM planDefinition phaseFBL establishedDBL establis

27、hedPBL tentativelyestablishedPBL establishedCM planDevelopment phaseCM planProduction phaseFCAPCACI identificationCI selectionKeyFBL=Functional baselineDDR=Detail design reviewDBL=Development baselineFCA=Functional configuration auditPBL=Production baselinePCA=Physical configuration auditSRR=System requirement reviewCI=Configuration itemSDR=System design reviewCM=Configuration management34Q&A35结束语结束语谢谢大家聆听！谢谢大家聆听！36