【正文】 vise capacity plan FP27 Generate schedule Scheduling Rule FP28 Adjust schedule Adjust Schedule FP29 Procurement remendation Consolidate PR Based On Time And Lot Sizing Rule FP30 Procurement Suggestion With Blanket Po Number FP31 Vendor Allocation FP32 Forecast For VMI Vendors FP33 Delivery Schedule For JIT vendors FP34 Each Factory Building At Shenzhen Should Consume Inventory From Its Own Building First, Output Factory Location For PO For Vendor Delivery Information FP35 Output schedule Output Production Schedule FP36 Reporting Reporting OUT OF SCOPE BUSINESS REQUIREMENTS Serial Number Categories of Scenarios Target User Scenarios within Category/Comments FPO1 BOM Manually Entering of BOM FPO2 Different Attribute For Part in BOM FPO3 Large quantity small value item Management FPO4 AI phase in and phase out FPO5 Add demand Adding Urgent Orders in FP Directly FPO6 Inventory Inventory Tracking Status FPO7 Routing Customize ATO routing FPO8 Release schedule Check software and documents before work order release FPO9 Schedule work orders FOR PORTION OF AI forecast FPO10 KPI Plan Change KPI FPO11 Track factory’s execution adherence to the schedule 169。OP process. Input Data Requirements: Every demand, as well as forecast, must have a priority. Logic Requirements: Demand sort priority Information 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 tiebreaking rules for demands. Description of Deliverable Business Rules: HW’s prioritizing rule must be clearly defined. Besides, when a high priority demand has material shortage, the other ponents can be used by a lower priority demand with earlier due dates. User Interface/Reporting Requirements: None. Key Functionality: Demand sort priority User Access to Data and Interfaces: Planner can see all the demand information in the Orders screen. Key Assumption for this Business Scenario to be represented in Phase I – HW establishes clear demand priority rule. Integration assigns priority points to each demand. 169。 Tier3 “Order Hold” are not planned in FP. Planners/Users Impacted: Planner List of Causes/Triggers for Scenario: When important orders are put on “Order Hold” status. Related Scenarios: Demand priority Frequency: Daily Decision to be Made/Action to be taken: None. Customer/Decision Maker: Planner Time Allowed to Make Decision: During the review of ICP and inventory assignment result. Input Data Requirements: Demands as well as the BOM and routing to support this PTO can be extracted from Oracle. Logic Requirements: The priority field in demand data of this type order must higher than other customer tiers. Information Requirements for Decision/Criteria to Make Decision: None. Description of Deliverable Business Rules: Orders with “Order Hold” status from Tier 1 customers must be satisfied before sales order from lower tier customer. User Interface/Reporting Requirements: Order Editor Key Functionality: Demand sort Priority, and inventory assignment User Access to Data and Interfaces: Order editor Key Assumption for this Business Scenario to be represented in Phase I – Tier I Booekd Hold orders are extracted by ROI from Oracle. 169。 2020 i2 Technologies, PROPRIETARY and CONFIDENTIAL BUSINESS SCENARIO DETAIL: FP4 MATERIAL PLANNING FOR POC FORECAST User Scenario: Material requirement for all noncritical material under PTO forecast BOM should be planned. These include POC, material under ATO (., P, PH, AOC, RM), and material under AI, etc. Planners/Users Impacted: Planner List of Causes/Triggers for Scenario: MRP for ponents inside forecast PTO is required. Related Scenarios: Demand priority Frequency: Daily Decision to be Made/Action to be taken: None. Customer/Decision Maker: None. Time Allowed to Make Decision: Input Data Requirements: AI forecast, POC and other raw material forecast demand Logic Requirements: Forecast demands for AI and raw materials must be planned and fulfilled according to the demand priority. Information Requirements for Decision/Criteria to Make Decision: None. Description of Deliverable None. Business Rules: AI and raw material for forecasted PTO must be planned. User Interface/Reporting Requirements: AI and raw material requirement as demands are shown in FP’s Order Editor. Key Functionality: Inventory Assignment. User Access to Data and Interfaces: FP Order Editor Key Assumption for this Business Scenario to be represented in Phase I: AI and raw material forecast can be sent to FP as forecast demands. 169。D MATERIAL REQUIREMENT User Scenario: Before the engineering start pilot production, Ramp。D BOM in Oracle is deemed reliable. FP should plan for material for engineering lots, similar to other normal demands. Planners/Users Impacted: Ramp。D material requirement planning must be in the same planning system as other demands. Related Scenarios: Forecast demands for POC and AI Demand priority Frequency: Daily. Decision to be Made/Action to be taken: None Customer/Decision Maker: None. Time Allowed to Make Decision: None. Input Data Requirements: .Before pilot, demands should e in to FP as demands at AI and raw material level. After pilot, engineering demand for ATO/AI, engineering part ID, engineering work orders, their BOM and routing, resource must all be extracted from Oracle. Logic Requirements: None. Information Requirements for Decision/Criteria to Make Decision: None. Description of Deliverable None. Business Rules: Ramp。D orders, bom and routing are entered in Oracle.