FP_business_requirement_v

1、HuaweiTechnologiesISC/APSProjectBusinessRelease1BusinessRequirementsFPRevision2.1/2AUG,2002?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1TABLEOFCONTENTSTHEAS-ISPROCESS5PURPOSE5OVERVIEWOFOPERATIONS5Overviewofbusinessprocess6MDS8MPS8Purchasing10Manufacturingplan10BUSINESSSCENARIOS11BUSIN

2、ESSSCENARIODETAIL:1.MATERIALASSIGNMENTACCORDINGTODEMANDPRIORITY12BUSINESSSCENARIODETAIL:2.PTOANDPOCSHOULDBEDELIVEREDANDPLANNEDTOGETHER13BUSINESSSCENARIODETAIL:3.MULTIPLEPTOWITHSAMESHIPDATE15BUSINESSSCENARIODETAIL:4.ACCOUNTFORSHIPMENTTIME(OUTSIDEFPFUNCTION)16BUSINESSSCENARIODETAIL:5.RESERVEMATERIALAN

3、DCAPACITYFORTIER1ORDERS16BUSINESSSCENARIODETAIL:11.MANUALENTERTHEBOM(NOTSUPPORTED)17BUSINESSSCENARIODETAIL:12.ALTERNATEPARTFUNCTION18BUSINESSSCENARIODETAIL:13.ECO20BUSINESSSCENARIODETAIL:14.AIPHASEINANDPHASEOUT21?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BUSINESSSCENARIODETAIL:15.DI

4、FFERENTATTRIBUTEFORPARTINBOM22BUSINESSSCENARIODETAIL:16.PLANBASEDONORDERBOM22BUSINESSSCENARIODETAIL:17.R&DMATERIALREQUIREMENT(OUTSIDEFPFUNCTION)24BUSINESSSCENARIODETAIL:18MATERIALPLANNINGFORPOCFORECAST24BUSINESSSCENARIODETAIL:21.LARGEQUANTITYSMALLVALUEITEMMANAGEMENT(OUTSIDEFPFUNCTION)25BUSINESSSCENA

5、RIODETAIL:22.SAFETYSTOCK27BUSINESSSCENARIODETAIL:23.INVENTORYDETAILS&STATUS27BUSINESSSCENARIODETAIL:24.OUTPUTFACTORYLOCATIONFORPO,POCONLYCONSUMEFROMSAMELOCATIONPOC29BUSINESSSCENARIODETAIL:31.SUGGESTPRFORNON-CRITICALPARTS31BUSINESSSCENARIODETAIL:32.VENDORALLOCATION32BUSINESSSCENARIODETAIL:33.BLANKETP

6、OANDFINITECAPACITYSUPPLIER33BUSINESSSCENARIODETAIL:34.VMIANDJITPARTS34BUSINESSSCENARIODETAIL:35.POFORIMPORTITEMSARRIVEINHK36BUSINESSSCENARIODETAIL:41.MINIMUMUTILIZATIONREQUIREDFORSUBCONTRACTORS38BUSINESSSCENARIODETAIL:42.MAINTAINEVEN(MINIMUM)UTILIZATIONOFRESOURCE39BUSINESSSCENARIODETAIL:43.SCHEDULEW

7、ORKORDERSFOR?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1PORTIONOFAIFORECAST40BUSINESSSCENARIODETAIL:44.RESOURCEGROUPINGFORPRODUCTIONPLANNING41BUSINESSSCENARIODETAIL:45.MULTIPLEPARALLELRESOURCES43BUSINESSSCENARIODETAIL:46.ATOCUSTOMIZEDROUTIING44BUSINESSSCENARIODETAIL:47.FINITECAPACITY

8、PLANNINGRULE44BUSINESSSCENARIODETAIL:48.COORDINATEWORKORDERSFORFINISHEDAIANDSEMIFINISHEDAI47BUSINESSSCENARIODETAIL:51.AIWORKORDERCONSOLIDATIONRULE48BUSINESSSCENARIODETAIL:52.RELEASEWORK-ORDERWITHMATERIALSHORTAGE49BUSINESSSCENARIODETAIL:53.RELEASETHEWORULES50BUSINESSSCENARIODETAIL:54.CHECKSOFTWAREAND

9、DOCUMENTSBEFOREWORKORDERRELEASE52BUSINESSSCENARIODETAIL:55.WIPTRACKING53BUSINESSSCENARIODETAIL:61.SCHEDULINGRULE54BUSINESSSCENARIODETAIL:71.SCHEDULEFROZENPERIOD55BUSINESSSCENARIODETAIL:72.ADDURGENTORDERS(OUTOFSCOPE)55BUSINESSSCENARIODETAIL:81.REPORTING56BUSINESSSCENARIODETAIL:82.PLANCHANGEKPI57BUSIN

10、ESSSCENARIODETAIL:83.TRACKFACTORYSEXECUTIONADHERENCETOTHESCHEDULE58?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1REVISIONHISTORY59MAJORCHANGESSINCELASTREVISION59REQUIREDAPPROVALS60THEAS-ISPROCESSPurposeTheBusinessRequirementdocumentcapturestheAs-IsProcess,identifiesimprovementopportuni

11、tiesanddefinestheTo-BeProcess.Italsodocumentsbusinessscenariosthatdescribetheworkflowandbusinessprocessesthatthesoftwaresolutionshouldaddress.Itelaboratesontheavailableinputs,requiredprocessing(includingtimingandfrequencyconsiderations)andtherequiredoutputs.Eachscenariointurnhelpsindefiningwhatsolut

12、ionfeatureswouldberequired.Thedocumentisasupportingtooltodecideonthefeaturesandfunctionalityneededinthesolution.Theusecasescenariosarelaterusedtovalidateandacceptresolvedissues.ThedocumentshouldbeusedatthestartoftheSolutionArchitecturephase,andcontinuallyreviewedthroughouttheimplementation,asmoreinf

13、ormationbecomesavailable.OverviewofOperations?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1OverviewofbusinessprocessAtHWtheplannersofdifferentdepartmentareinchargeofmaterialsplanning.Andtheplannersonlyplantheproductsfortheirowndepartment.Alltheplanningprocessesareseparately.Thewholepro

14、cessis:a. GatheringandprocessalldemandswithMDSb. GenerateMPSc. RunMRPandSchedulingd. ProcessWOandPRe. ExecuteWOandPRShortage?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1TheBill-of-materialsforatypicalHuaweisalesorderitemisasinthefollowingfigure:NotethatPTOatthetopoftheBOMisapackingpro

15、cess,anddoesnothaveanyrouting.ThesalesorderlineitemwillbeatATOlevel.SMTfactoryisinthe?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BTSmode,producingaccordingtoforecast.ThereisaSMTinventorywarehouseforSMTboards.ATOfactoryperformthefinalassemblyandtestingwhenHuaweireceivestheorder.Insimp

16、lewords,PlanningattheATOlevelisATO.ThePlanningattheSMTlevelisMTS.ATOsareuniquetocustomerswhereasSMTsarenot.Thus,multipleuniqueATOssharecommonSMT.MDSInMDSphase,plannersgatheralltheforecastsfirst.Thentheywillcheckandadjusttheforecasts.Afterconfirmtheforecasts,theplannersgatherallthedemandstogether,tha

17、tmainlycomingfromthefollowingfourwaysa. Demandsfrommarketingplandepartmentb. Demandsfromthebusinessdepartment(realsalesorders)c. Internaldemandsbetweendifferentdepartmentsd. IndependentrequirementsfromdifferentdepartmentsAfterthisphase,plannersknowallthedemandsthatneededtobeplanned.MPSTogenerateMPS,

18、plannersfirstgenerateaMPSplanandgettherelationreports.ThentheyadjusttheMPSresultbeforesendingtoteplanningmanagerforapproval.AftertheplanningmanagerconfirmedtheMPSresult,theplannersneedtomaintainthenewMPSplan.ThentheMRPschedulingplanisgenerated.WhenadjustingtheMPSplan,theplannersconsiderthefivefactor

19、sbelow:a.Versionchange?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1b.Thecapacityconstrainofthekeyresourcesc.Therequirementschangefromthemarketing,andchangesininternalrequirementsd.Theplanningpercentageisnotaccurate,causethedemandsarenotmappingwellwiththehistorydatae.Otherthingssuchasb

20、asicdatanotaccurate,theplanningattributenotcorrectandspecialordersetc.TMPMRelease5.1?2001i2Technologies,PROPRIETARYandCONFIDENTIALPurchasingPurchasingforecastTherearetwotypesofpurchasingforecast,oneisweeklyforecast,andtheotherismonthlyforecast.Weeklyforecastcoversthreemonthspurchasingforecasts.Thema

21、terialsaremainlylocallysupplied.Andthepurchaseleadtimearerelativelyshort.Someexamplesarepackagingmaterials,PCBetc.Monthlyforecastcoversninemonthspurchasingforecasts.Specialmaterialsareonlypurchasedwhentherealsalesordersarereceived.TheMAX/MINmethodallowsMAXandMINinventoryforthematerials.Whenthemateri

22、alsinventoryislowerthentheMINvalue,theywillbepurchasedusethefollowingformula:Purchasequantity=MAX-InventoryPO(timebased)+Requiredquantityofsalesorder(timebased)ManufacturingplanTheplannersgeneratetheproductionreportsusingthemanufacturingdataofthefirstthreeweeks.Planneronlyreleasesthemanufacturingord

23、ersthatbegininthenexttwodaysinthemanufacturingexecutionsystem.Normallyplannersonlyreleaseworkorderswhenthematerialsofworkorderareallreadyintheinventory.Butinsomeurgentcases,theyalsoreleasetheworkorderevenwhennotallthematerialsareallready.Theshortagematerialmaybearrivingwithinthefollowingtwodays.?200

24、1i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenariosIntroduction:BasedontheinterviewquestionsanddiscussionswithBUprocessownersandfactoryschedulers,variousbusinessscenariosthatrepresentFPsbusinessrequirementshavebeencompiled.Thisdocumentwillbealivedocumentandwillgetupdatedwithmor

25、edetailsontheexistingscenariosandalsonewscenariosandrequirementswillbeincludedastheprojectgoesthoughconceptualdesignandsolutionarchitecture.?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenarioDetaMaterialassignmentaccordingtoDemandpriorityUserScenario:Orderpriorityforsalesord

26、ersandforecastordersareassignedbySalesaccordingtoHuaweisinternalrule.FPmustassignmaterialandallocatecapacitybasedontheorderpriority.Planners/UsersImpactedPlannersListofCauses/TriggersforScenario:Sales,forecastandinternaldemandsenteredfromMPandERPneedtobeprioritizedandplanned.RelatedScenarios:Frequen

27、cy:Demandprioritylogicisusedeverytimetheplannerproducesaplan.Currentlytheplanisproducedonceaday.DecisiontobeMade/Actiontobetaken:Thesequenceofwhichtheordersarebeingfulf川ed.Whenahighprioritydemandhasmaterialshortage,lowprioritydemandcanbefulfilledCustomer/DecisionMaker:PlannerTimeAllowedtoMakeDecisio

28、n:InputDataRequirements:Everydemand,aswellasforecast,musthaveapriority.LogicRequirements:DemandsortpriorityInformationRequirementsforDecision/CriteriatoMakeDecision:SinceFPplansalltheordersinfactoryforallproductfamily,productetc,priorityrulebesetatadetailedgranularitytoprovidecleartie-breakingrulesf

29、orDescriptionofDeliverable?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessRules:Theprioritytypicallybasedonproductfamily,customer,andorderentrydate.UserInterface/ReportingRequirements:KeyFunctionality:DemandsortpriorityUserAccesstoDataandInterfacesPlannercanseeallthedemandinforma

30、tionintheOrdersscreen.BusinessScenarioD2taPTOANDPOCshouldbedeliveredandplannedtogetherUserScenario:POCitemsappearaslineitemsinthesalesorder.POCshouldbedeliveredwithPTOitem.Planners/UsersImpacted:PlannerListofCauses/TriggersforScenario:WhenSalesorderorForecastcomingfromMPorERP,thePOCandPTOshouldbeint

31、hesameorderanddifferentlines.RelatedScenarios:Frequency:DecisiontobeMade/Actiontobetaken:Whenonelineitemoftheorder(PTOorPOC)islate,theotherwillbealsodelayed.Andtheywilldelivertogether.Customer/DecisionMaker:PlannerTimeAllowedtoMakeDecision:InputDataRequirements:salesorderid,linenumber,duedateofthesa

32、lesorderfromOracle.LogicRequirements:InformationRequirementsforDecision/CriteriatoMakeDecision:DescriptionofDeliverableBusinessRules:differentlineitemsinonesalesordershouldbeshippedtogether.?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1KeyFunctionality:MarriedlineUserAccesstoDataandInt

33、erfaces:?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenarioDeta3.MultiplePTOwithsameshipdateUserScenario:AcontractmaycontainmultiplePTOsofwhichsomeofthemhavethesameshipdates.ThePTOswithsamecontractnumberwithsameduedateshouldbeplannedtogethertocompleteatthesametime,andalsorel

34、easedatthesametime.Planners/UsersImpactedPlannersListofCauses/TriggersforScenario:TherearesomesalesorderswithmultiplePTOitems.RelatedScenarios:Frequency:DecisiontobeMade/Actiontobetaken:Whenonelineitemoftheorderislate,theotherwillbealsodelayed.Andtheywilldelivertogether.Customer/DecisionMaker:Planne

35、rTimeAllowedtoMakeDecision:InputDataRequirements:salesorderid,linenumber,duedateofthesalesorderfromOracle.LogicRequirements:InformationRequirementsforDecision/CriteriatoMakeDecision:DescriptionofDeliverableBusinessRules:differentlineitemsinonesalesordershouldbeshippedtogether.UserInterface/Reporting

36、Requirements:KeyFunctionality:MarriedlineUserAccesstoDataandInterfaces:?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenarioDetaAccountforShipmentTime(OutsideFPfunction)UserScenario:IncludetheTimetotransportationfromDMSinworkorderstarttimeplanning.Planners/UsersImpactedPlanner

37、ListofCauses/TriggersforScenario:Forsomesalesordertheduedateisthedatethatcustomerreceiptdate.RelatedScenarios:Frequency:everytimethesalesorderscomeintoODS.DecisiontobeMade/Actiontobetaken:PlannerCustomer/DecisionMaker:TimeAllowedtoMakeDecision:BeforesalesorderdatacomesintoODSInputDataRequirements:th

38、eduedateofsalesordersneedtobetheshipmenttimefroHW.LogicRequirements:shouldcanidentifywhichorderstimeincludethetransportationtime,whichdonotinclude.AndmustcanprovidethetransportationtimefromHWtocustomer.InformationRequirementsforDecision/CriteriatoMakeDecision:transportationtimefromHWtocustomerDescri

39、ptionofDeliverableBusinessRules:salesorderduedate=customerreceiptdatetransportationtimeUserInterface/ReportingRequirements:KeyFunctionality:UserAccesstoDataandInterfaces:BusinessScenarioDetaReservematerialandcapacityfortier1orders?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1UserScenar

40、io:Orderwith“OrderHold“statusfromcustomersshouldhavehighprioritytoreservematerialandcapacity.Tier2OrderHoldsarenotplannedinFP.Planners/UsersImpactedPlannerTier1ListofCauses/TriggersforScenario:RelatedScenarios:DemandsortpriorityFrequency:Usedeverytimetheplannerproducesaplan.Currentlytheplanisproduce

41、onceaday.DecisiontobeMade/Actiontobetaken:Customer/DecisionMaker:PlannerTimeAllowedtoMakeDecision:InputDataRequirements:Thepriorityfieldindemanddataofthistypeordermusthigherthenothertype.LogicRequirements:InformationRequirementsforDecision/CriteriatoMakeDecision:DescriptionofDeliverableBusinessRules

42、:OrderswithOrderHold“statusfromTier1customersmustbesatisfiedbeforesalesorderfromlowertiercustomer.UserInterface/ReportingRequirements:KeyFunctionality:DemandsortPriorityUserAccesstoDataandInterfaces:BusinessScenarioDeiaiManualentertheBOM(Notsupported)FPdoesnotsupportmaintaindatainFP.UserScenario:Cre

43、ationandMaintenanceofBOMinFP.Planners/UsersImpacted:Planner?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1ListofCauses/TriggersforScenario:SometimesplannerscanreleasesomeWOeventhematerialarenotallreadyintheinventory.RelatedScenarios:)Frequency:DecisiontobeMade/Actiontobetaken:Customer/D

44、ecisionMaker:TimeAllowedtoMakeDecision:InputDataRequirements:LogicRequirements:InformationRequirementsforDecision/CriteriatoMakeDecision:DescriptionofDeliverableBusinessRules:UserInterface/ReportingRequirements:KeyFunctionality:UserAccesstoDataandInterfaces:BusinessScenarioDe2aiAIternatepartFunction

45、UserScenario:Usealternatepartwhenprimarypartisunavailable.Planners/UsersImpacted:PlannerListofCauses/TriggersforScenario:Whentheprimarymaterialislate,plannerwillminimizeorderslatenessbyusealternatepart.RelatedScenarios:Frequency:?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1Customer/De

46、cisionMaker:PlannerTimeAllowedtoMakeDecision:InputDataRequirementsBOMwiththeinformationaboutcompatibilityofeveryalternatecomponentinOracle,inventory.LogicRequirements:primarypartassignmentsfirst:TRUEInformationRequirementsforDecision/CriteriatoMakeDescriptionofDeliverableDecision:BusinessRuleswhethe

47、rusetheontimePRofprimarypartoruseontimeinventoryofalternatepart.UserInterface/ReportingRequirements:KeyFunctionality:AlternateParts-primarypartsassignmentUserAccesstoDataandInterfaces:?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenarioDe3aiECOUserScenario:Use-upeffectivityis

48、requiredforbothAIandrawmaterialECO.Theuse-updateisrequiredfromFPtoupdateinOracleautomatically.Use-upECOshouldalsosupport.Planners/UsersImpactedPlannersListofCauses/TriggersforScenario:ChangestoBOM,changestoexistingparts,sourcingofnewpartsornewvendors.RelatedScenarios:BOMeffectivityFrequency:atECOtim

49、eDecisiontobeMade/Actiontobetaken:Customer/DecisionMaker:PlannerTimeAllowedtoMakeDecision:InputDataRequirements:IntheBOMmusthavethedetailinformationofallthecomponentswhenitcomesfromOracle.LogicRequirements:Oracleshouldhavetheflagtoidentifyused-uportimebasedeffectivity.InformationRequirementsforDecis

50、ion/CriteriatoMakeDecision:DescriptionofDeliverableBusinessRules:UserInterface/ReportingRequirements:KeyFunctionality:BOMeffectivityUserAccesstoDataandInterfaces:?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenarioDe40iiAIphaseinandphaseoutUserScenario:DuringAIitemsversioncha

51、nge,theoverlappingperiodisnormally3monthwhentheolderversionofAIisgraduallyphasedout.OlderversionshouldbeconsumedbeforethenewversionAI.DifferentversionsofAIshouldhavedifferentpartIDs.Planners/UsersImpactedPlannersListofCauses/TriggersforScenario:Toavoidlargeinventoryforphase-outAIpart.RelatedScenario

52、s:BOMeffectivityFrequency:atphasein/phaseouttimeDecisiontobeMade/Actiontobetaken:Customer/DecisionMaker:PlannerTimeAllowedtoMakeDecision:InputDataRequirementscorrespondencerelationlistbetweenphase-outAIpartandphase-inAIpart,BOMLogicRequirements:InformationRequirementsforDecision/CriteriatoMakeDecisi

53、on:DescriptionofDeliverableBusinessRules:UserInterface/ReportingRequirements:KeyFunctionality:BOMeffectivityUserAccesstoDataandInterfaces:?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1BusinessScenarioDe5iaiDifferentattributeforpartinBOMUserScenario:ItemsrepresentedbythesamepartIDmayhav

54、edifferentattributes.Andtheseitemswithdifferentattributescannotbeusedinterchangeably.Forexamplecablewiremightbe3mor10mlength,andcannotbeusedassubstituteforeachother.Someoftheseitemsareorderedasspecialitems.Planners/UsersImpacted:PlannerListofCauses/TriggersforScenario:RelatedScenarios:Inventoryassig

55、nmentFrequency:DecisiontobeMade/Actiontobetaken:Customer/DecisionMaker:PlannerTimeAllowedtoMakeDecision:InputDataRequirements:OracledoesnotdifferentinventoryforitemswithsamepartIDwithdifferentattributes.LogicRequirements:Theinventorydatashouldbeseparatedbydifferentattributes.Anneedtogetacleardefinit

56、ionoftheattributions.InformationRequirementsforDecision/CriteriatoMakeDecision:DescriptionofDeliverableBusinessRules:UserInterface/ReportingRequirements:KeyFunctionality:attributebasedplanningUserAccesstoDataandInterfaces:BusinessScenarioDe6aiPlanbasedonorderbom?2001i2Technologies,PROPRIETARYandCONFIDENTIALTMPMRelease5.1UserScenario:AftertheATOorderhasbeenconfigured,orderBOMcanbeextractedbasedonthesalesorder.ThematerialrequirementshouldbeplannedbasedontheorderBOM.Planners/UsersImpacted:PlannerListofCauses/Trigger