i2生產(chǎn)計(jì)劃與排程(1)-文庫(kù)吧資料
2025-01-29 04:59本頁(yè)面
【正文】 processes can run on Windows NT machines ? May run server and client on separate machines ? Use existing data (from Triton and SFCS) ? Memory Resident ? MultiUser capability Rhythm FP Architecture (cont.) Rhythm FP Client Rhythm FP Client Rhythm FP Client Data Files Rhythm FP Server Rhythm FP Server Production Planner Material Planner Report Reader Production Server Whatif Server Rhythm FP Framework (Input Output) Demand Product Structure: ?Part number ?BOM ?Routings Factory Model: ?Resources ?Resource Calendar Material Availability: ?Unassigned Inventory ?./ Vendor Info. ?WIP Other Information: ?Tools ?... Production Plan: ?Capacity ?Material Rhythm FP Framework (cont.) ? FP requires ACCURATE and SUFFICIENT data input (garbage in garbage out) ? Open loop planning process in the first phase ? Planners execute the production plan based on FP’s suggestion Basic FP Data Objects ? BOM data ? Demand order data ? Part number data ? Unassigned inventory data ? Supplier part data ? Resource data ? Routing data More FP Data Objects ? Wip data ? Operation resource data ? Resource calendar data ? Vendor calendar data ? Variable capacity bucket size data FP Output Files ? Critical delivery data ? Purchase order EDC remendations ? Manufacturing order data ? Planned start times ? Procurement data ? Procurement by part data ? etc. FP Data Objects Relationship Demand Orders Forecast Orders BOM Unassigned inventory Routing data Vendor Info Resource data Resource calendar data WIP data Finished Goods Part Numbers Mfg Orders Rhythm FP Planning Concept FP Planning Concept ? BTO (Buildtoorder) engine: use Demands as the driver to create plan ? Consider both material and capacity constraints at the same time ? Consider both Sales Orders and Forecasts as the demand input with different priorities ? Start as an Infinite Capacity Plan and progress to a Finite Capacity
教學(xué)課件相關(guān)推薦
鄂ICP備17016276號(hào)-1