FPbusinessrequirementv2.1 [IBM—华供应链全套方案].doc

Huawei TechnologiesISC / APS ProjectBusiness Release 1 Business Requirements FPRevision 2.1/ 2 AUG, 2002TABLE OF CONTENTSTHE AS-IS PROCESS5PURPOSE5OVERVIEW OF OPERATIONS5Overview of business process5MDS8MPS8Purchasing10Manufacturing plan10BUSINESS SCENARIOS11BUSINESS SCENARIO DETAIL: 1. MATERIAL ASSIGNMENT ACCORDING TO DEMAND PRIORITY12BUSINESS SCENARIO DETAIL: 2. PTO AND POC SHOULD BE DELIVERED AND PLANNED TOGETHER13BUSINESS SCENARIO DETAIL: 3. MULTIPLE PTO WITH SAME SHIP DATE14BUSINESS SCENARIO DETAIL: 4. ACCOUNT FOR SHIPMENT TIME (OUTSIDE FP FUNCTION)15BUSINESS SCENARIO DETAIL: 5. RESERVE MATERIAL AND CAPACITY FOR TIER1 ORDERS16BUSINESS SCENARIO DETAIL: 11. MANUAL ENTER THE BOM (NOT SUPPORTED)16BUSINESS SCENARIO DETAIL: 12. ALTERNATE PART FUNCTION17BUSINESS SCENARIO DETAIL: 13. ECO19BUSINESS SCENARIO DETAIL: 14. AI PHASE IN AND PHASE OUT20BUSINESS SCENARIO DETAIL: 15. DIFFERENT ATTRIBUTE FOR PART IN BOM21BUSINESS SCENARIO DETAIL: 16. PLAN BASED ON ORDER BOM22BUSINESS SCENARIO DETAIL: 17. R&D MATERIAL REQUIREMENT (OUTSIDE FP FUNCTION)23BUSINESS SCENARIO DETAIL: 18 MATERIAL PLANNING FOR POC FORECAST24BUSINESS SCENARIO DETAIL: 21. LARGE QUANTITY SMALL VALUE ITEM MANAGEMENT (OUTSIDE FP FUNCTION)24BUSINESS SCENARIO DETAIL: 22. SAFETY STOCK26BUSINESS SCENARIO DETAIL: 23. INVENTORY DETAILS & STATUS27BUSINESS SCENARIO DETAIL: 24. OUTPUT FACTORY LOCATION FOR PO, POC ONLY CONSUME FROM SAME LOCATION POC28BUSINESS SCENARIO DETAIL: 31. SUGGEST PR FOR NON-CRITICAL PARTS30BUSINESS SCENARIO DETAIL: 32. VENDOR ALLOCATION31BUSINESS SCENARIO DETAIL: 33. BLANKET PO AND FINITE CAPACITY SUPPLIER32BUSINESS SCENARIO DETAIL: 34. VMI AND JIT PARTS33BUSINESS SCENARIO DETAIL: 35. PO FOR IMPORT ITEMS ARRIVE IN HK34BUSINESS SCENARIO DETAIL: 41. MINIMUM UTILIZATION REQUIRED FOR SUBCONTRACTORS36BUSINESS SCENARIO DETAIL: 42. MAINTAIN EVEN (MINIMUM) UTILIZATION OF RESOURCE37BUSINESS SCENARIO DETAIL: 43. SCHEDULE WORK ORDERS FOR PORTION OF AI FORECAST38BUSINESS SCENARIO DETAIL: 44. RESOURCE GROUPING FOR PRODUCTION PLANNING39BUSINESS SCENARIO DETAIL: 45. MULTIPLE PARALLEL RESOURCES40BUSINESS SCENARIO DETAIL: 46. ATO CUSTOMIZED ROUTIING41BUSINESS SCENARIO DETAIL: 47. FINITE CAPACITY PLANNING RULE42BUSINESS SCENARIO DETAIL: 48. COORDINATE WORK ORDERS FOR FINISHED AI AND SEMIFINISHED AI44BUSINESS SCENARIO DETAIL: 51. AI WORK ORDER CONSOLIDATION RULE45BUSINESS SCENARIO DETAIL: 52. RELEASE WORK-ORDER WITH MATERIAL SHORTAGE46BUSINESS SCENARIO DETAIL: 53. RELEASE THE WO RULES47BUSINESS SCENARIO DETAIL: 54. CHECK SOFTWARE AND DOCUMENTS BEFORE WORK ORDER RELEASE48BUSINESS SCENARIO DETAIL: 55. WIP TRACKING49BUSINESS SCENARIO DETAIL: 61. SCHEDULING RULE50BUSINESS SCENARIO DETAIL: 71. SCHEDULE FROZEN PERIOD51BUSINESS SCENARIO DETAIL: 72. ADD URGENT ORDERS (OUT OF SCOPE)51BUSINESS SCENARIO DETAIL: 81. REPORTING53BUSINESS SCENARIO DETAIL: 82. PLAN CHANGE KPI54BUSINESS SCENARIO DETAIL: 83. TRACK FACTORYS EXECUTION ADHERENCE TO THE SCHEDULE54REVISION HISTORY55MAJOR CHANGES SINCE LAST REVISION56REQUIRED APPROVALS56THE AS-IS PROCESSPurposeThe Business Requirements document captures the As-Is Process, identifies improvement opportunities and defines the To-Be Process. It also documents business scenarios that describe the workflow and business processes that the software solution should address. It elaborates on the available inputs, required processing (including timing and frequency considerations) and the required outputs. Each scenario in turn helps in defining what solution features would be required.The document is a supporting tool to decide on the features and functionality needed in the solution. The use case scenarios are later used to validate and accept resolved issues. The document should be used at the start of the Solution Architecture phase, and continually reviewed throughout the implementation, as more information becomes available.Overview of OperationsOverview of business processAt HW the planners of different department are in charge of materials planning. And the planners only plan the products for their own department. All the planning processes are separately. The whole process is:a. Gathering and process all demands with MDSb. Generate MPSc. Run MRP and Schedulingd. Process WO and PRe. Execute WO and PRThe Bill-of-materials for a typical Huawei sales order item is as in the following figure:Note that PTO at the top of the BOM is a packing process, and does not have any routing. The sales order line item will be at ATO level. SMT factory is in the BTS mode, producing according to forecast. There is a SMT inventory warehouse for SMT boards. ATO factory perform the final assembly and testing when Huawei receives the order. In simple words, Planning at the ATO level is ATO. The Planning at the SMT level is MTS. ATOs are unique to customers whereas SMTs are not. Thus, multiple unique ATOs share common SMT. MDSIn MDS phase, planners gather all the forecasts first. Then they will check and adjust the forecasts. After confirm the forecasts, the planners gather all the demands together, that mainly coming from the following four waysa. Demands from marketing plan departmentb. Demands from the business department (real sales orders)c. Internal demands between different departmentsd. Independent requirements from different departmentsAfter this phase, planners know all the demands that needed to be planned.MPSTo generate MPS, planners first generate a MPS plan and get the relation reports. Then they adjust the MPS result before sending to te planning manager for approval. After the planning manager confirmed the MPS result, the planners need to maintain the new MPS plan. Then the MRP scheduling plan is generated. When adjusting the MPS plan, the planners consider the five factors below:a. Version changeb. The capacity constrain of the key resourcesc. The requirements change from the marketing, and changes in internal requirementsd. The planning percentage is not accurate, cause the demands are not mapping well with the history datae. Other things such as basic data not accurate, the planning attribute not correct and special orders etc.PurchasingØ Purchasing forecastThere are two types of purchasing forecast, one is weekly forecast, and the other is monthly forecast.Weekly forecast covers three months purchasing forecasts. The materials are mainly locally supplied. And the purchase lead time are relatively short. Some examples are packaging materials, PCB etc.Monthly forecast covers nine months purchasing forecasts.Ø Special materials are only purchased when the real sales orders are received.Ø The MAX/MIN method allows MAX and MIN inventory for the materials. When the materials inventory is lower then the MIN value, they will be purchased use the following formula:Purchase quantity = MAX Inventory PO (time based) + Required quantity of sales order (time based)Manufacturing planThe planners generate the production reports using the manufacturing data of the first three weeks. Planner only releases the manufacturing orders that begin in the next two days in the manufacturing execution system.Normally planners only release work orders when the materials of work order are all ready in the inventory. But in some urgent cases, they also release the work order even when not all the materials are all ready. The shortage material may be arriving within the following two days. Business Scenarios Introduction:Based on the interview questions and discussions with BU process owners and factory schedulers, various business scenarios that represent FPs business requirements have been compiled. This document will be a live document and will get updated with more details on the existing scenarios and also new scenarios and requirements will be included as the project goes though conceptual design and solution architecture. Business Scenario Detail: 1. Material assignment according to Demand priorityUser Scenario: Order priority for sales orders and forecast orders are assigned by Sales according to Huaweis internal rule. FP must assign material and allocate capacity based on the order priority. Planners/Users Impacted: PlannersList of Causes/Triggers for Scenario: Sales, forecast and internal demands entered from MP and ERP need to be prioritized and planned.Related Scenarios: Frequency: Demand priority logic is used every time the planner produces a plan. Currently the plan is produced once a day.Decision to be Made/Action to be taken: The sequence of which the orders are being fulfilled. When a high priority demand has material shortage, low priority demand can be fulfilledCustomer/Decision Maker: PlannerTime Allowed to Make Decision: Input Data Requirements: Every demand, as well as forecast, must have a priority. Logic Requirements : Demand sort priorityInformation Requirements for Decision/Criteria to Make Decision: Since FP plans all the orders in factory for all product family, product etc, priority rule be set at a detailed granularity to provide clear tie-breaking rules for demands from different departments. Description of DeliverableBusiness Rules: The priority typically based on product family, customer, and order entry date. User Interface/Reporting Requirements:Key Functionality: Demand sort priorityUser Access to Data and Interfaces: Planner can see all the demand information in the Orders screen.Business Scenario Detail: 2. PTO AND POC should be delivered and planned togetherUser Scenario: POC items appear as line items in the sales order. POC should be delivered with PTO item.Planners/Users Impacted: PlannerList of Causes/Triggers for Scenario: When Sales order or Forecast coming from MP or ERP, the POC and PTO should be in the same order and different lines.Related Scenarios:Frequency: Decision to be Made/Action to be taken: When one line item of the order (PTO or POC) is late, the other will be also delayed. And they will deliver together.Customer/Decision Maker: PlannerTime Allowed to Make Decision: Input Data Requirements: sales order id, linenumber, duedate of the sales order from Oracle.Logic Requirements: Information Requirements for Decision/Criteria to Make Decision:Description of DeliverableBusiness Rules: different line items in one sales order should be shipped together.User Interface/Reporting Requirements: Key Functionality: Married lineUser Access to Data and Interfaces: Business Scenario Detail: 3. Multiple PTO with same ship dateUser Scenario: A contract may contain multiple PTOs of which some of them have the same ship dates. The PTOs with same contract number with same due date should be planned together to complete at the same time, and also released at the same time. Planners/Users Impacted: PlannersList of Causes/Triggers for Scenario: There are some sales orders with multiple PTO items.Related Scenarios:Frequency: Decision to be Made/Action to be taken: When one line item of the order is late, the other will be also delayed. And they will deliver together.Customer/Decision Maker: PlannerTime Allowed to Make Decision: Input Data Requirements: sales order id, linenumber, duedate of the sales order from Oracle.Logic Requirements: Information Requirements for Decision/Criteria to Make Decision:Description of DeliverableBusiness Rules: different line items in one sales order should be shipped together.User Interface/Reporting Requirements: Key Functionality: Married lineUser Access to Data and Interfaces: Business Scenario Detail: 4. Account for Shipment Time (Outside FP function)User Scenario: Include the Time to transportation from DMS in work order start time planning. Planners/Users Impacted: PlannerList of Causes/Triggers for Scenario: For some sales order the due date is the date that customer receipt date.Related Scenarios:Frequency: every time the sales orders come into ODS.Decision to be Made/Action to be taken: PlannerCustomer/Decision Maker: Time Allowed to Make Decision: Before sales order data comes into ODSInput Data Requirements: the due date of sales orders need to be the shipment time from HW.Logic Requirements: should can identify which orders time include the transportation time, which do not include. And must can provide the transportation time from HW to customer.Information Requirements for Decision/Criteria to Make Decision: transportation time from HW to customerDescription of DeliverableBusiness Rules: sales order due date = customer receipt date transportation timeUser Interface/Reporting Requirements: Key Functionality: User Access to Data and Interfaces: Business Scenario Detail: 5. Reserve material and capacity for tier1 ordersUser Scenario: Order with “Order Hold” status from Tier 1 customers should have high priority to reserve material and capacity. Tier2 “Order Holds” are not planned in FP.Planners/Users Impacted: PlannerList of Causes/Triggers for Scenario: Related Scenarios:Demand sort priorityFrequency: Used every time the planner produces a plan. Currently the plan is produced once a day.Decision to be Made/Action to be taken: Customer/Decision Maker: PlannerTime Allowed to Make Decision: Input Data Requirements: The priority field in demand data of this type order must higher then other type.Logic Requirements: Information Requirements for Decision/Criteria to Make Decision:Description of DeliverableBusiness Rules: Orders with “Order Hold” status from Tier 1 customers must be satisfied before sales order from lower tier customer. User Interface/Reporting Requirements: Key Functionality: Demand sort PriorityUser Access to Data and Interfaces: Business Scenario Detail: 11. Manual enter the BOM (Not supported)FP does not support maintain data in FP. User Scenario: Creation and Maintenance of BOM in FP.Planners/Users Impacted: PlannerList of Causes/Triggers for Scenario: Sometimes planners can release some WO even the material are not all ready in the inventory.Related Scenarios: Frequency: Decision to be Made/Action to be taken: Customer/Decision Maker: Time Allowed to Make Decision: Input Data Requirements: Logic Requirements: Information Requirements for Decision/Criteria to Make Decision:Description of DeliverableBusiness Rules: User Interface/Reporting Requirements: Key Functionality: User A