plm實(shí)施工具11培訓(xùn)課件庫(kù)cmii培訓(xùn)課件

CMIITraining（CourseIII)黃博宏2008年3月4日ChangeEffectivities,FormsandTraceabilityCMIITraining（CourseIII)黃博宏Ch2022/12/10hpConfidential-UsedforSPILPLMBPMonly2大綱ProductBaseline,ReuseandChangesTheEnterpriseConfigurationandChangesClosetheLoopwithWorkAuthorizationsEffectivitiesversusEffectiveDatesDependentDemandandEffectivitiesAs-BuiltandAs-ModifiedRecordsProblemReportFormandECRFormECNFormandChangeImpactMatrixDCRFormandDeviation/WaiverFormDecisionTreeforReidentificationItemSerializationandLotTraceabilityTraceabilityofChangestoEnd-ItemsCMandDevelopmentwithDataModelsSoftwareDefectPreventionandReportingHighlightsofthisCourseRevisited2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly3學(xué)習(xí)標(biāo)的學(xué)習(xí)如何增加計(jì)劃性變更的可見性和新產(chǎn)品基線的生效方式及日期.學(xué)習(xí)如何利用相似版本的計(jì)劃中/已發(fā)行的產(chǎn)品基線來管理管理系需求的結(jié)構(gòu)..學(xué)習(xí)何謂＂接納變更(對(duì)管理性文件)＂并確保使用正確的版本.學(xué)習(xí)了解文件的＂發(fā)行日期＂,“生效日期＂,與＂生效＂的差異,并知道如何應(yīng)用.學(xué)習(xí)“可互換規(guī)則＂和如何通過每一個(gè)變更達(dá)成End-Item可追蹤性.如何設(shè)計(jì)適當(dāng)?shù)谋砀駚砑訌?qiáng)并支持Close-loop流程(實(shí)現(xiàn)＂接納變更＂)學(xué)習(xí)如何,何時(shí)分派序號(hào)和批號(hào),和如何達(dá)成雙向批次追蹤.學(xué)習(xí)如何更新＂制造紀(jì)錄＂來反映發(fā)生在＂操作＂和＂維護(hù)＂階段所發(fā)生的變更.學(xué)習(xí)如何利用自動(dòng)化工具和資料模型來幫助產(chǎn)品的開發(fā),并了解為何CM一直如此的重要.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly4A.ProductBaseline,ReuseandChangesProductBaseline,從何開始?怎么重復(fù)利用現(xiàn)有的設(shè)計(jì)和零件和正在進(jìn)行中的變更來建立我們的productbaseline?談到baseline就不能談到revisionhistory,本章節(jié)也會(huì)談到相關(guān)的revisionhistory格式.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly5Baseline是具有結(jié)構(gòu)概念的,End-Item的Baseline不只包含自己相關(guān)的文件,還包含通過BOM往下延伸的所有相關(guān)文件.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly6As-PlannedandAs-ReleasedInformation高階需求被了解(as-released)后,才有可能把下階的需求設(shè)計(jì)出來(as-planned)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly7第一個(gè)Baseline出現(xiàn)后,所有的修改都需要通過ECN來授權(quán).CustomerApprovalForm也是另一種授權(quán)的方式2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly8很少會(huì)有完全嶄新的Configuration,她們大部分都來自于一個(gè)現(xiàn)有的Configuration和Process,有多少是屬于As-PlannedInfo.取決于Reuse的程度.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly9Reuse可以簡(jiǎn)單區(qū)分為六種:(已經(jīng)存在而且可以Reuse,或是需要一些修正,或是完全需要重新研究和設(shè)計(jì))我們的目標(biāo)是一旦我們?nèi)〉昧酥匾男畔?或發(fā)明),我們就要善加利用,提高它的重用率.所以一旦as-released以及as-plannedbaseline的正確性與一致性被改進(jìn)了,同時(shí)產(chǎn)品開發(fā)的效率也就同時(shí)被改進(jìn)了.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly10

所謂AccommodateChange,很重要的一點(diǎn)就是維持它的可見度(Visibility),而所謂可見度,必須交代的就是其＂來龍去脈＂下圖顯示了在一個(gè)ProductBaseline里面包含的所有文件的信息,包括了這樣的文件是何時(shí)會(huì)被Release,通過什么樣的授權(quán)(ECN)來Released,或是在何時(shí),這份文件已經(jīng)被Released.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly11ChangeExistingFornewone在導(dǎo)入了ImplementationPlan和ECNEffectivity的觀念后,在這個(gè)Baseline里面還必須要加入如下圖所示的＂PlannedChange＂2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly12所有的文件應(yīng)該都要有所謂的＂RevisionHistoryBlock(版本紀(jì)錄)＂,交代在這個(gè)版本之前是什么(Was-Is),現(xiàn)在與過去的差異是什么.右圖是一個(gè)范例.

第一個(gè)版本出現(xiàn)時(shí)就寫在第一行,后續(xù)所做的修改就接著往下寫,每一個(gè)改變出現(xiàn)就新增一行2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly13

下圖是另一種格式,將上頁(yè)的格式做了九十度的翻轉(zhuǎn),另外也加入了其變更的過程(ECNNumber,FastTract).這樣的表達(dá)方式會(huì)比上頁(yè)的好一些,加強(qiáng)的＂AccommodateChange＂的意涵2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly14以下的這個(gè)范例又把上頁(yè)的觀念在做延伸,將整個(gè)Baseline的＂結(jié)構(gòu)＂(subsets)也同時(shí)記錄下來.

慣用縮寫:EC:ECR/ECN變更紀(jì)錄

Copy(C):被取代的文件副本

MU(Mark-up):被取代文件的注記

DCR(DocumentChangeRecord):修改紀(jì)錄2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly15B.TheEnterpriseConfigurationandChanges有關(guān)于End-Item的設(shè)計(jì)基礎(chǔ)主要文件,最多有四種,但關(guān)于企業(yè)的主要文件,最多有九種.本章節(jié)主要介紹這九種文件,和它們彼此之間的關(guān)系,以及如何通過版本說明文件來界定最上層的文件.以及,如何引用Baseline和Change的觀念來管理及同步這些文件的版本及內(nèi)容.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly16

如同End-Item一樣,BusinessEnterprise也有他一套的PrimaryDocument和它的Hierarchy2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly17

這如End-Item有PhysicalItemHierarchy一樣,BusinessEnterprise里面的Facilities&InformationSystem也形成了所謂的AdministrativeHierarachy.

而Procedures,就是在說明如何使用Facilities&InformationSystem來達(dá)成企業(yè)目標(biāo)的步驟和方法(OperationStandard)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly18Primary:連接在PrimaryItem的文件Secondary:連接在PrimaryDocument上的文件如果我們把BusinessRegulations也算進(jìn)去的話,BusinessEnterprise的PrimaryDocuments應(yīng)該有九大類2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly19AdministrativeHierarchy的另一種視圖以StrategicBusinessPlan的內(nèi)容,展開所謂的＂核心流程(CoreProcesses)＂,這也是Facilities,InformationSystem&EnterpriseStandards的根本.

OperationPlan(financialplan)的內(nèi)容會(huì)指出,有那些BusinessProgramsVDD:VersionDescriptionDocument2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly20OperationPlan(ofenterprise)=BuildSchedule(ofphysicalitem)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly21VDD本來用在SoftwareProgram,不過一樣可以適用在企業(yè)上,圖的左邊就是一個(gè)范例.跟前一章節(jié)談到的一樣,也需要描述其生效日期及其Authority(ECN)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly22左圖是有關(guān)產(chǎn)品生產(chǎn)計(jì)劃,里面每一個(gè)文件的變更都會(huì)有ECN來說明其變更的授權(quán)及生效日期.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly23同樣的道理,在企業(yè)里面也有相同的需求和做法.不同的時(shí)間區(qū)間,應(yīng)該對(duì)應(yīng)到不同的管理文件.所有的管理性活動(dòng),也應(yīng)該依據(jù)當(dāng)時(shí)生效的文件來執(zhí)行.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly24C.ClosetheLoopwithWorkAuthorizations無論是PhysicalItem或者是BusinessEnterprise,都可以通過baseline來控管在何時(shí),應(yīng)該使用哪個(gè)文件的哪個(gè)版本,呈現(xiàn)其＂可見度(Visibility)＂.本章節(jié)從這點(diǎn)繼續(xù)延伸,探討如何延伸其＂可見度＂2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly25所謂的＂Effectivity＂就是要知道,“現(xiàn)在是什么,改變之后又是什么＂2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly26加入PlannedChange之后的樣貌D:表示刪除,A:表示新增2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly27PhysicalItems的概念也可以套用到BusinessEnterprise,每一個(gè)階層也可以有它各自的Baseline.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly28左圖就是上頁(yè)想法的一個(gè)實(shí)踐例子.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly29這是一個(gè)例子,在這個(gè)例子中,因?yàn)樵黾恿薖rogramC,所以O(shè)perationPlan也同時(shí)做改變版本的動(dòng)作2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly30

ECN提供對(duì)文件修改或新增的授權(quán)

WorkAuthorization提供了對(duì)實(shí)物(PhysicalItem)購(gòu)買,制造,組建,測(cè)試的授權(quán),其根據(jù)就是文件,而其結(jié)果也必須符合文件的內(nèi)容.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly31

ConformanceDocuments有的是說明＂結(jié)果應(yīng)該是什么＂,有些是說明達(dá)成這樣的結(jié)果,“需要的步驟是什么＂.

這個(gè)工作的授權(quán)是來自于負(fù)責(zé)指出應(yīng)用哪些文件,哪個(gè)版本的那個(gè)人,而不是那些實(shí)際上根據(jù)這個(gè)WA做出動(dòng)作的人2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly32

有些管理性工作是常態(tài)性的,使用的費(fèi)用來自于經(jīng)常性費(fèi)用預(yù)算.這一類沒有所謂的＂WorkAuthorization.

有些管理性工作則是來自于某些管理性的項(xiàng)目,費(fèi)用會(huì)來自于這些ProgramBudget.

所謂的AdministrativeActivity不外乎這兩類.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly33

在ECN流程上,PhysicalItem和BusinessEnterprise其實(shí)都一樣.但在WorkAuthorization上則不同.

所以如何確保正確的AdministrativeDocument被使用,需要找到另一個(gè)方式來管理它2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly34WorkshopIII-1Background:ChapterAdescribedaphysicalitem-orientedas-planned/as-releasedbaselineformanaginglike-familiesofend-items.ChapterBidentifiedasimilarbaseline,orasetofbaselines,formanagingtheenterpriseadministrativerequirements.WithinCM,theconceptofanas-planned/as-releasedbaselineisnew.ApplyingtheCMIIprinciplestoadministrativerequirementsisnew.Usingsuchabaselinetomanageadministrativerequirementsisevennewer.Althoughwearestilllearninghowtodoit,weareconvincedthatitistherightthingtodo.Weneedtounderstandhowtheadministrativehierarchyinterfaceswiththephysicalitemhierarchies.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly35WorkshopIII-1YourAssignment:Identifythewaysinwhichthetwohierarchiesinterfacewitheachotherbyansweringeachofthefollowingquestions:Describetheinterfaceintermsofsecondaryitems.Theyarelinkedtoprimarydocumentsinthephysicalitemhierarchy.Howaretheylinkedtotheadministrativehierarchy?Howwouldachangeimpactthetwohierarchies?Describetheinterfaceintermsofsecondarydocumentssuchassoftwareusedtoproducesoftware.Wheredoestheresponsibilityresideforthequalityofthesoftwarethatisproducedversusthesoftwareusedtoproducesoftware?Howwouldachangeimpactthetwotypesofsoftware?Describetheinterfaceintermsofcoreprocessesversusbusinessprograms.Howdoestheownerofabusinessprogram,suchasaprogrammanager,interfacewiththeownersofthevariouscoreprocesses.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly36D.Effectivitiesvs.EffectiveDates變更管理(ChangeManagement)是整個(gè)企業(yè)管理中最復(fù)雜的一個(gè)功能,而Effectivities又是變更管理中最復(fù)雜的.所謂的Effectivities代表了變更的切換點(diǎn),它有不同的表達(dá)方式,因此也有了不同的解譯方式.ECN和Documents都有Effectivites,Document也有ReleaseDate,也有EffectiveDate,本章節(jié)將說明三者的關(guān)系,以及如何使用.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly37對(duì)這個(gè)變更的生效,有很多說法,可以說是時(shí)段13(以End-Item的生效來看),有人說是8(以Asy看),也有說是生效在A-1這個(gè)End-Item,也有說是C-1的某一個(gè)批號(hào)生效.基本上這幾種都是可能的生效表達(dá)方式.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly38BusinessEnterprise的生效多半都是與版本來區(qū)分,比較上比較沒有PhysicalItem那樣的復(fù)雜.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly39以下圖為例,Effectivity發(fā)生在哪一層,要看在那一層發(fā)生Reidentification,同時(shí)也要連結(jié)到其控制的文件.至于Reidentification的準(zhǔn)則,在ChapterJ會(huì)提到.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly40Effectivity是聯(lián)結(jié)在ControlItem所聯(lián)結(jié)的取代與被取代的ControllingDocuments,222之所以是ControllingItem,因?yàn)樗麤]有被Reidentified.而一份ECN通常只有一個(gè)Effecitivity,不論有多少份文件被影響.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly41歸納起來,每個(gè)文件都會(huì)需要三種日期

ReleaseDateEffectivity:僅限于ControllingDocument.EffectiveDate:被取代文件停止使用而新文件開始被使用的日期2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly42

ReleaseDate通常就等于是EffectiveDate,但是可以早于EffectiveDate.

對(duì)于一份ControllingDocument而言,EffectivityDate會(huì)永遠(yuǎn)等于EffectiveDate,通?？梢宰詣?dòng)填入.

在CourseIV,會(huì)進(jìn)一步說明如何取出這些日期.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly43E.DependentDemandandEffetivities傳統(tǒng)上航太業(yè)都用End-Item的SerialNumber來表達(dá)其Effecitivies.自從1970＇s/1980＇s企業(yè)開始使用ERP系統(tǒng)以后,通常都用Date來表達(dá)Effecitivites.這一章節(jié)將會(huì)引導(dǎo)了解兩者的優(yōu)缺點(diǎn),藉此更了解Effectivities的真正用意.同時(shí)也會(huì)更了解ERP如何通過相依的需求,Forecast來計(jì)算需求.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly44ERP用到所謂＂planningbill＂的觀念來計(jì)算未來的需求.從111展開的所有子件的需求都相依于111的planningbill.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly45下圖是一個(gè)PlanningBill電子化的格式2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly46

所謂＂dependentdemand＂item是說該item的需求依賴于其父件的需求.

反之,“independentdemand＂item就是其需求與其父件無關(guān).所以也就是最上一階的item.

從planningbill往下展開的同時(shí),也要考慮changeeffectivity才能計(jì)算出正確的結(jié)果.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly47EffectivitybySerialNumberEffectivitybyDateDifferentWaytoStateEffectivity2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly48下面我們用一個(gè)例子來比較End-ItemSerialNumber與Date的Effectivity表達(dá)方式2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly49第一個(gè)情境如下:Item777在一段時(shí)間后,出現(xiàn)瑕疵,如果忽略這個(gè)問題,會(huì)導(dǎo)致更嚴(yán)重的問題,為解決這個(gè)問題,我們用778來取代它,這個(gè)改變希望在end-itemserialnumber422以后生效.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly50

777被778取代后,原先的Parent555必須要re-identified(因?yàn)閚otinterchangeable),333也必須變成334,但111不動(dòng).

左側(cè)這個(gè)例子是用日期來做生效的表示.對(duì)上頁(yè)所描述的情境來說,比較不是那么貼切,但使用上看起來似乎沒什么問題.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly51

把上頁(yè)的日期生效,改為左圖的序號(hào)生效,看起來更符合所要求的情境.

序號(hào)生效通常都會(huì)標(biāo)明起訖2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly52第二個(gè)情境:Item778幾經(jīng)測(cè)試后制作上非常困難,目前計(jì)劃用779來取代778,但之前已經(jīng)有八個(gè)778的成品產(chǎn)出.由于778和779對(duì)父件556來說是可互換的,所以556不需要換號(hào).預(yù)計(jì)從S/N422以后,還是使用778,直到八個(gè)778被用完后,才用779取代.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly53以下是用日期來做生效標(biāo)示,在這樣的情境下,用日期生效是很令人困惑的,當(dāng)生產(chǎn)計(jì)劃有任何變動(dòng)的時(shí)候,這些生效日期要跟著變更.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly54左圖改成了以End-itemserialnumber的方式表示,看起來就更能表達(dá)現(xiàn)實(shí)的情況.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly55左邊這個(gè)例子剛好相反,444是一個(gè)標(biāo)準(zhǔn)件,應(yīng)用在很多結(jié)構(gòu)中,在這種情況下,用日期表達(dá)生效會(huì)比批號(hào)來的容易而且清楚多了原則上在planningbill的應(yīng)用上,以end-itemserialnumber的生效表達(dá)比較恰當(dāng),但變更發(fā)生在較底層結(jié)構(gòu)的時(shí)候,用日期生效比較恰當(dāng)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly56

即使簡(jiǎn)單的變更,也會(huì)有很多不同的相依任務(wù)要執(zhí)行,更不用說是復(fù)雜的變更.

這些有任務(wù)需要有計(jì)劃的被執(zhí)行,來支持effecitivity.所以當(dāng)effectivity改變,這些任務(wù)的排程也需要改變.但不管哪種effecitivity表達(dá)方式,這些排程都是需要的

生效的表達(dá)根據(jù)不同的情境,變動(dòng)性是很大的.但不管如何,生效的維護(hù)都是一大挑戰(zhàn).2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly57F.As-BuildandAs-ModifiedRecords每一個(gè)As-buildrecord所關(guān)連的文件,表達(dá)了在當(dāng)時(shí)那個(gè)end-item的as-planned/as-releasedbaseline.Modificationrecords和ECN不同的地方在于,Modification沒有很嚴(yán)格的順序.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly58WorkAuthorization/As-builtrecords來自于As-released/As-plannedbaseline.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly59每一筆As-builtRecord都反映當(dāng)時(shí)對(duì)這個(gè)Item的as-released/as-plannedbaseline.(對(duì)照到上頁(yè)).2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly60對(duì)于高采購(gòu)成本和材料替換前置期長(zhǎng)的End-Items而言,通常會(huì)比較頻繁的做調(diào)整以便延長(zhǎng)它的服務(wù)年限(servicelife)In-Servicemodifications,執(zhí)行的方式,會(huì)跟在buildcycle中的ECN有一些差異.訂定優(yōu)先序的條件會(huì)有所不同合并變更的條件也會(huì)有所不同很多ECN是為了補(bǔ)足或修正文件的錯(cuò)誤,而這些也許不適用于In-servicedocument.有些ECN是為了改善制造難度,這通常對(duì)in-serviceitem來說并沒有意義,除非這個(gè)ECN可以同時(shí)改善維護(hù)難易度.通常在In-serviceitem中,除非明顯利益大于成本很多的改變才可能會(huì)被approved.對(duì)buildcycle中的item有利的ECN,不見得會(huì)對(duì)in-serviceitem有利.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly61多個(gè)ECR會(huì)合并成一個(gè)ECN實(shí)施,多個(gè)ECN也會(huì)被合并成一個(gè)in-servicemodification執(zhí)行.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly62

In-servicemodification必須搭配WorkAuthorization,就如同DocumentUpdate需要有ECN作為Authority一樣.

這個(gè)WorkAuthoriztion里面必須標(biāo)明的是根據(jù)哪些文件.每一份文件也需要有ECN作為Authority或是其他種類的授權(quán).

同一個(gè)WorkAuthorization可以對(duì)應(yīng)到多個(gè)Item(如下圖).每一個(gè)modification會(huì)有一個(gè)號(hào)碼,和對(duì)應(yīng)的日期.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly63

in-service設(shè)備的變更往往在文件變更前就會(huì)做了,尤其是當(dāng)變更后的結(jié)果沒辦法事前加以計(jì)劃.

所以當(dāng)變更完成后,一定要再回過頭更新文件,同時(shí)as-buildrecord也要跟著一起修改.

所以一個(gè)WA有時(shí)候會(huì)標(biāo)示使用的文件,但同時(shí)也知道這份文件最終還是要經(jīng)過一些修正.這些文件預(yù)計(jì)有的修正,要含在modificationplan里面.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly64紀(jì)錄Modification有兩種方式:對(duì)日常使用的文件,像是操作指示,文件應(yīng)該改版.對(duì)于少量使用的文件,可以用修訂的方式(supplement)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly65基于ContinuousImprovement,physicalitems還是會(huì)持續(xù)的被替換,這些替換也許不是一對(duì)一的,可能是各種的組合.以下的圖是一個(gè)范例.Supersedingitem,表示已經(jīng)經(jīng)過調(diào)查可以替代的,Inquiry表示這個(gè)Item還需要經(jīng)過一些調(diào)查,判斷和被取代的item中間有多大的差異.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly66以下是另一個(gè)范例,這個(gè)范例比較清楚,連他對(duì)應(yīng)到的ECN也標(biāo)示出來,包括其ReleaseDate和生效,還有變更的種類(Major),specialinstruction.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly67如果被取代件與取代件,并非一對(duì)一,則用ECNnumber來代表要取代的items2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly68WorkshopIII-2Background:Eachofthreefacilitiesoperateonan18monthcyclewhichincludesa3monthshutdownformodificationsandmaintenance.Notwofacilitiesaretobedownatthesametime.Thethreefacilitiesweretobeidenticalandallthreeweretobedefinedononesetofdocuments.Differences,ifany,couldsomehowbenoted.AfterUnit1wasbuilt,Unit2wasbuiltfromitsas-builtdrawingsandUnit3wasbuiltfromas-builtdrawingsforUnit2.ProblemsbecameapparentbeforeUnit2wasfinished.Bothplannedandunplannedmodificationsaretobeaccomplishedduringthe3monthshutdownperiod.Somemodificationsareplannedbut,afterreviewingthestatusofthedisassembledconfiguration,arenotimplemented.Conversely,disassemblyoftenrevealsaneedformodificationsthathadnotbeenplanned.Astimewentby,thethreefacilitiesbecameincreasinglydifferentaccordingly.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly692022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly70WorkshopIII-2Background(Continue..)Itwasdecidedthatonlyonesetofdocumentationwouldbeusedtosupportallthreefacilitiesasawaytoavoidthecostofcreatingandmaintainingadditionalsets.Abilitytoaccomplishtheplannedandunplannedmod'swithinnomorethana3monthwindowisdependentuponhavingthedocumentationandmaterialsneededtosupportscheduledactivitiesbeginningwithDay1oftheshutdown.Thenetlossforeachdaythatonefacilitysetsidleis$1M.Itisstandardpracticetobringinseveralhundredspecialiststohelpperformsuchmodifications.TheyarereadytoworkonDay1andremainon-sitethroughtheshutdownperiod.Yourworkshopgrouphasanassignmenttodefineabetterwaytorunthebusiness.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly71WorkshopIII-2YourAssignment-Answerthefollowingquestions:Describehowyouwouldgoaboutdevelopingyourrecommendationsandhowyouwouldjustifythoserecommendations.Listthetypesofinformationthatyouwillneedwithwhichtomakeyourcasetouppermanagement.Baseduponyourintuitionaboutwhatyouarelikelytolearn,describewhatyoubelievethatyoureventualrecommendationswillbeintermsofthefollowing:Howmanysetsofdocumentationshouldtherebe?Willthemod'sbeinitiatedwithupgradeddocumentationorwillthedocumentupgradesbeaccomplishedafterthemod'sarecompleted?Towhatdegreedoyouanticipatethatdocumentswillbeupgradedbyusingsupplementsratherthanrevisingthedocuments.Howdoyouproposetominimizethedelayinrestartcausedbyunplannedmod'sforwhichtheneedisdiscoveredaftershutdownanddisassembly?2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly72G.ProblemReportFormandECRForm六種變更表格的用途ProblemReport與ECR的關(guān)系ECRs跟ECN的關(guān)系組成ECR的23種信息.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly73六種ChangeForms的功用ECR:EnterpriseChangeRequests2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly74六種Forms的另一種表達(dá)方式:

有時(shí)候ECR&ECN可以合并,如果變更簡(jiǎn)單的話

Waiver算是一種例外描述文件.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly75左邊是ProblemReportForm的范例:ProblemReport不見得一定會(huì)產(chǎn)生ECR,要看最后的解決方式.PR的重點(diǎn)在于描述問題的內(nèi)容和環(huán)境,重現(xiàn)的方法,和真正原因的調(diào)查與驗(yàn)證.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly76PR為ECR的附件,ECR除了用來解決PR里面的問題,同時(shí)也為了產(chǎn)品的改善.ECR里面包含了對(duì)解決方式的建議,成本的估算,和BusinessDecision(CRB)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly77ECR是變更請(qǐng)求,里面包含這個(gè)變更的BusinessDecision,ECN是一份高階的實(shí)施計(jì)劃,記錄所影響的文件.有時(shí)候這兩份也可以合并為一個(gè).2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly78ECN的重點(diǎn),PhysicalItem和文件的ImpactMatrix.藉此也才能更精確估算其變更成本.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly79相對(duì)于ECR,在ECN中的ImpactMatrix,應(yīng)該要更精確一些,而且是經(jīng)過重新修正的.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly802022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly812022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly82ECRnumberfromECRlogDaterequestisreceived(andlogged)byChangeAdministrationIRequestor'sname()ApprovalsignatureRequestor'slocationand/orphonenumberStatementofproblemorneededimprovementProposedsolutionorimprovementifknownbyrequestorECRcategorizationasfasttrack,yesornoPriorityfortechnicalreviewandrecommendationAssignedcreatortoprovidetechnicalreviewandrecommendationDateofassignmenttocreatorbyChangeAdmin.ITechnicalrecommendationbycreatorDatethatcreatorsubmitstechnicalrecommendationEstimateofnonrecurringcostEstimateofrecurringcostKeyimplementationtimingfactorsCRBgrouptoprovidebusinessdecisionCRBgroup'sactualdecisionPriorityassignedtochangerequestifapprovedReasonsifdisapprovedorspecificinformationneededSignatureofCRBchairpersonDateofdispositionECNnumberandeffectivityiffasttrackPagenumbers2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly83H.ECNFormandChangeImpactMatrixItemandDocumentImpactMatrixMultiplebaselineimpactedbyoneECNWas-IsrepresentationforbaselinesECNForm的22個(gè)欄位2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly84ECN被建立用來執(zhí)行一個(gè)以上的ECR,并且指出要替換與被替換的零件與文件2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly85以下是一個(gè)范例:其中要包含End-Item畫圈的部份表明沒有進(jìn)行reidenfication的階層.ItemDisposition,對(duì)原先被替換件的處置2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly86下面這個(gè)例子是上頁(yè)的延伸,加入了Impact的文件部份.文件會(huì)跟著ItemReidentification而做進(jìn)版.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly87一個(gè)ECN可能會(huì)影響到一個(gè)或一個(gè)以上的baseline,以下是administrativehierarachy,至少就包含四個(gè)baseline,同一個(gè)ECN有可能影響到一個(gè)以上的baseline.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly88所以設(shè)計(jì)的ImpactMatrix應(yīng)該要有能力可以呈現(xiàn)多個(gè)以上baseline的impact這樣可能就會(huì)有數(shù)頁(yè)以上的ImpactMatrix2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly89ECN對(duì)baseline也可以發(fā)揮同樣的功能.DocumentChangeRecord是用來記錄Document的was-is.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly90ECCImpactMatrix可以拿來跟VDD比較一下.VDD用來記錄Item必須遵從的文件歷史.

而ECN是針對(duì)一個(gè)Item發(fā)生變化所影響的文件.(同樣的紀(jì)錄內(nèi)容,只是動(dòng)機(jī)不同,方向不同.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly91ECN提供一個(gè)載體供多個(gè)ECR執(zhí)行之用,并且產(chǎn)出一個(gè)或多個(gè)執(zhí)行變更的藍(lán)圖.2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly922022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly932022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly94ECNnumberPagenumbersApprovedECRstobeimplementedbythisECNNameofcreatorcoordinatingthischangeLocation/phonenumberofthecoordinatorofthisECNDescription/purposeofthisECNPriorityforimplementationCustomerapproval,ifrequired,andstatusHierarchyofphysicalitemsordocumentsassociatedwiththisECNPhysicalitemnamesbygenericnounSupersededitemnumbersSupersedingitemnumbersDocumentsaffectedbytypeSupersededdocumentsbynumberandrevisionlevelSupersedingdocumentsbynumberandrevisionlevelDispositionsforsupersededitemsorpracticesSpecialimplementationinstructionsDatethattheECNisreleasedtotheCIBforimplementationplanningPagenumbersofdetailedimplementationplanEffectivityforthisECNSignatureofCIBchairperson(ChangeAdmin.II)RevisionstotheECNafterinitialreleasetotheCIB2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly95I.DCRFormandDeviation/WaiverFormAlternativesForUpgradingDocumentsChangeRecordsVersusChangeNoticesDCRFormComprisedOfNineDataFieldsWorkAuthorizationsandtheWaiverForm2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly96Step1描述ECR的目的并送交CRB核準(zhǔn)Step2如果核準(zhǔn),分派ECN號(hào)碼并且對(duì)CIB發(fā)行Step3備份將要改變的部份(theWAS)Step4將主文件改版Step5備份改變后的部份(theIS)Step6用步驟三和五的部份來建立DCR第一種方式2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly97Thefirstway2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly98第二種方式Step1-備份將要改變的部份(theWAS)Step2建立一個(gè)視觀表(view)描述改變之后的樣貌Step3用上述兩者建立DCN并連同ECR送交CCBStep4若ECR核準(zhǔn)通過,用DCN來做為文件的補(bǔ)注Step5最后連同DCN補(bǔ)注到文件中Step6把DCN當(dāng)作DCR保存在版本歷史紀(jì)錄中historybyusingtheDCNasaDCR2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly99Thesecondway(常用于國(guó)防合同)2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly100第三種方式Step1標(biāo)明文件將要變更的部份Step2準(zhǔn)備ECR并附上將要變更的部份(markup)Step3送出markup連同ECR到CCB做審核Step4如果通過了,就根據(jù)markups進(jìn)行文件修改Step5在版本紀(jì)錄中保存ECR和markups2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly101Thethirdway(常用于醫(yī)療器材業(yè))2022/12/10hpConfidential-Us2022/12/10hpConfidential-UsedforSPILPLMBPMonly102ChangeRecordvs.ChangeNotice特定的文件如何更新的方式主要依賴于文件本身和變更流程.一段時(shí)間內(nèi)三個(gè)ECN會(huì)讓文件變更三次或是額外的三次補(bǔ)注.適當(dāng)結(jié)構(gòu)化的是簡(jiǎn)化變更流程和建立合適的