TW200305088A - System and method for order group planning with attribute based planning - Google Patents

System and method for order group planning with attribute based planning Download PDF

Info

Publication number
TW200305088A
TW200305088A TW091137686A TW91137686A TW200305088A TW 200305088 A TW200305088 A TW 200305088A TW 091137686 A TW091137686 A TW 091137686A TW 91137686 A TW91137686 A TW 91137686A TW 200305088 A TW200305088 A TW 200305088A
Authority
TW
Taiwan
Prior art keywords
date
order
time
item
orders
Prior art date
Application number
TW091137686A
Other languages
Chinese (zh)
Inventor
Myrick Crampton
Sunil Soman
Original Assignee
Manugistics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/287,775 external-priority patent/US7539630B2/en
Priority claimed from US10/287,805 external-priority patent/US6885902B2/en
Priority claimed from US10/287,788 external-priority patent/US6898472B2/en
Priority claimed from US10/287,773 external-priority patent/US20030149631A1/en
Application filed by Manugistics Inc filed Critical Manugistics Inc
Publication of TW200305088A publication Critical patent/TW200305088A/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A system and method for planning the use of supply chain network resources in order to meet demand as defined by one or more groups of orders. The system and method is an attribute based rather than an order or stock keeping unit based system and method allowing for greater flexibility and improved simplicity in obtaining planning solutions. The system and method defines and uses stock keeping unit attribute definition groups, which allows orders to be prioritized and organized into slices of orders such that an optimal planning solution is generated. During the planning process, the system and method may determine whether the supply chain network resources used to fulfill the orders are replenishable by purchase. The system and method recognizes time events and takes into account the exact sequence of the events in order to obtain an optimal solution.

Description

0) 0)200305088 玖、發明說明 (發明說明應敘明:發明所屬之技術領域、先前技術、内容、實施方式及圖式簡單說明) 相關中請案交叉參照 此申請案主張2001年12月27日及2002年5月3日所申請 之美國暫定專利申請案序號6 〇/3 42,404及60/3 77,243的優 先權’其所揭露的在此將全部併入做為參考。此申請案也 主張以下共同等候判定及一般讓渡的美國非暫定申請案 的優先權:2002年11月5日申請,序號10/2 87,788,代理 人文件號82001.0350之Cramp ton等人的「具以屬性為基礎 之規劃之訂購群組規劃系統及方法」;2002年1 1月5日申請 ’序號 1 0/287,775,代理人文件號 8200 1.0390 之 Crampton 等人的「藉由以屬性為基礎之規劃所製造之補充系統及方 法」;2002年11月5日申請,序號1 0./287,805,代理人文件 號82001· 0 391之Crampton等人的「藉由以屬性為基礎之規 劃所購買之補充系統及方法」;2 0 0 2年1 1月5日申請,序號 10/287,773,代理人文件號82001.0392之Cramp ton等人的 「具以屬性為基礎之規劃之訂購群組規劃系統及方法」。 發明說明 技術領域 本發明是有關於規劃製造資源的利用之系統及方法, 更特別是,本發明是有關於以屬性為基礎之規劃系統及方 法,其可運作於高度複雜及動態的環境中,並且會產生多 重資源的利用之規劃,以達成要求。 先前技術 對於具有重要製造容量及/或多重來源的任何商業而言 (2)200305088 ,規劃製造資源的使用, 縮的任務。在今日競爭的 變的更為真實,因為今日 些商業哲學,如剛好在時 源規劃。 以滿足需求的問題總是是令人畏 環境中,規劃資源的使用之問題 的商業趨勢迫使許多商業遵循某 間内的概念,此需要高紀律的資 〜农适的巨大網路、言庫、運 銷及其他的生產/運銷位曹丄 運 ή U置所組成。另外,這些位置 一個包含一些資源,如奘 母 4 .、 裝配、、泉’以及所有會交互作用及一 起工作的儲存設備,以產口 , 生成TO給客戶。單獨製造網路的 複雜度時常使其非常難於 、及將巨大數目之通常組成 製U或供應鏈網路之資源 只/原列入計畫表中。 許多其他因素會使試圖4目告 '圖規劃,以及將製造或供應鏈網路 中的資源列入計畫表Φ; 4 Μ <複雜度增加。例如,公司通常合 接收來自於各種客戶的夂絲、w 曰 各種叮早,每個訂單及每個客戶合 具有不同的優先權及其仙沾兩> ^ 曰 、 3為求。另外,公司通¥會需要 能對預測的未來訂單傲招老 早做規劃,並且用以判斷何時材料必須 訂購及保留給預期的客 > 〜田 — /、 户w丁早 < 谷里。例如,Ά車製造業 者會接收來自於車隊蚩去 .. 者、租車公司、個人居民或任何數 目之大及較小量的客戶之訂單。每個訂單會包含許多項目 對於A車製造業者而言,這些可能是具有不同選擇物之 不同樣式的汽車。這些訂單中的每個也可包括其他重要的 資訊’如客戶想要收到或能取得訂單物品之日期及日期的 範圍、物品可用的位置,如特定的業者位置、客戶所選擇 的選用包裝、以及可行的取代組態。因此,每個訂單通常 200305088 具有許多參數,其係定義訂單必須如何、什麼、何時、及 那裡完成。 今曰許多製造商堅持一種或多種商業哲學,如剛好在時 間内的原則,以降低成本。不幸的是,這些原則中的每個 可能是製造商也可能想要遵循之另一原則的障礙。另外, 這樣的哲學會增加試圖規劃訂單的完成之複雜度,以及可 使其更難於規劃供應鏈網路中的資源之使用。 為了有效及正確地規劃,較佳而言,規劃系統將能考慮 到可相關於每個網路資源之各種限制。這些限制可基於一 些因素,如時間、數量、品質、可用物品的型式、以及類 似之物。較佳而言,用來表示資源網路的任何模型也將是 強健的,以致於會考慮許多資源網路的動態特性。在使用 規劃系統的任何模型中,這些流動限制的增加會增加規劃 程序之全部的複雜度。 此外,用於規劃的模型必須考慮到時間問題。為了規劃 網路資源,真實的時序需求必須考慮。這意謂實際的時間 延遲,例如,在真正地需要零件時,需訂購用於裝配線的 元件部份之增加時間需要考慮。此外,在任何的有效規劃 系統中,項目(如成品)的時間可用性、過程中的運作及原 料需要考慮。 因為各種原因,其中的某些已敘述如上,規劃資源的使 用,以滿足需求的使用之成本會過高。為了有效率及有效 用地滿足今曰商業的規劃需求,非常強健的,並且可確認 及容納許多限制及有時商業的衝突目標之規劃系統及方 (4) (4)200305088 法是非常想要的。 因此,本發明係針對規劃商業資源的最佳使用,以達成 訂單之系統及方法。更特別是,本發明係提供用以產生及 維持位於多個位置上之多個資源的使用之限制及屬性敏 感規劃’以芫成一個或多個訂單之系統及方法。 用於將訂單列入計畫表及資源分配之傳統的規劃系統 通常由存貨保持單元(SKU)所驅使。另一種方法可使用以 屬性為基礎的方法。支配供應鏈規劃的限制及商業規則通 常由產品、市場、以及操作環境的某些基本特性(屬性) 所驅使。因此,模型的表示應該以這些屬性的觀點來達成。 根據本發明之一具體實施例,所提供的是稱為屬性基礎 規劃(ABP)系統的一種系統。此系統可包括盥 一貝针庫傳輸 勺电腦裝置。如由具有屬性的一個或多個訂鼙 a 吓疋義之需 求可輸入到系統,其會產生用於網路内的資源之利用的♦ 劃。訂單可以是内部或外部產生的訂單,或可甚至表二、 計畫過的客戶需求。在處理訂單後,ABP系統會立刻Z為 用於網路資源之利用的規劃,以完成需求。 根據本發明之另一具體實施例,存貨保持 . 千70屬性定義 D)群組會產生及定義出來。根據本發明之ΑΒρ 忧用SAD群組,來提供各種系統功能。例如, " m ^ 群組可 采將訂單按優先順序處理,並且將資源組織成如組食 /或材料清單(BOM)的部份,以及類似之物之群 〜及 * 、 叫1*、、且。為了 足進各種功能,會產生各種.表。例如,在會產生的表 200305088 (5) 皆嗤护Wifi 包括用於未規劃訂單的暫時表、BOM及組態表、SAD群組 、以及類似之物。此外,運輸矩陣也會產生,以追縱及考 慮運輸問題。0) 0) 200305088 发明 Description of the invention (the description of the invention shall state: the technical field, prior art, content, implementation and drawings of the invention are briefly explained) The relevant application cross-references this application and claims December 27, 2001 Priority of U.S. Provisional Patent Application Serial Nos. 6 0/3 42,404 and 60/3 77,243 filed on May 3, 2002 and their respective disclosures are hereby incorporated by reference in their entirety. This application also claims the priority of the following non-tentative U.S. applications, which are awaiting determination and general assignment: Application dated November 5, 2002, serial number 10/2 87,788, agent file number 82001.0350, etc. Order Group Planning System and Method Based on Attribute-Based Planning "; Application of 'No. 1 0 / 287,775, Agent Document No. 8200 1.0390, etc. by Crampton et al. Supplementary Systems and Methods Manufactured by Planning "; Application of November 5, 2002, Serial No. 10 / 287,805, Agent Document No. 82001 · 0 391 by Crampton et al." Purchased by Attribute-Based Planning "Supplementary systems and methods"; "Application Group Planning System and Method with Attribute-Based Planning," by Cramp ton, etc., applied on November 5, 2002, with serial number 10 / 287,773, agent file number 82001.0392, etc. ". DESCRIPTION OF THE INVENTION TECHNICAL FIELD The present invention relates to a system and method for planning the utilization of manufacturing resources. More particularly, the present invention relates to an attribute-based planning system and method that can operate in a highly complex and dynamic environment. And there will be plans for the utilization of multiple resources to meet the requirements. Prior Technology For any business with significant manufacturing capacity and / or multiple sources (2) 200305088, planning the use of manufacturing resources, a reduced task. Today's competition becomes more real, because today's business philosophy, such as just in time source planning. The problem of satisfying demand is always in a frightening environment. The business trend of planning the use of resources has forced many businesses to follow the concept of a certain room. This requires highly disciplined resources ~ a large network of suitable farms, a sound bank, Transportation and sales and other production / transportation positions consisted of Cao Yuyun's price and real estate. In addition, these locations one contains some resources, such as the mother 4, assembly, spring, and all storage equipment that will interact and work together to produce TO to customers. The complexity of making a separate network from time to time often makes it very difficult, and a huge number of resources that usually make up a U or supply chain network are only / originally listed in the plan. Many other factors will make attempts to plan planning, and to include resources in the manufacturing or supply chain network into the planning table Φ; 4 Μ < increased complexity. For example, companies usually receive reel from various customers together, w is a variety of bites, each order and each customer have different priorities and its two advantages are better. In addition, the company will need to be able to plan for the predicted future orders, and use it to determine when the materials must be ordered and reserved for the expected customers > ~ 田 — / 、 户 w 丁 早 < Guli. For example, car manufacturers may receive orders from fleet owners, car rental companies, individual residents, or any number of large and small customers. Each order will contain many items. For A car manufacturers, these may be different styles of cars with different options. Each of these orders can also include other important information such as the date and range of dates the customer wants to receive or be able to obtain the order item, the location where the item is available, such as the location of the specific operator, the customer's choice of packaging, And a viable alternative configuration. Therefore, each order typically has 200305088 with many parameters that define how, what, when, and where the order must be completed. Many manufacturers today adhere to one or more business philosophy, such as the principle of just in time, to reduce costs. Unfortunately, each of these principles can be an obstacle to another principle that manufacturers may also want to follow. In addition, such a philosophy would increase the complexity of trying to plan the completion of orders and make it more difficult to plan the use of resources in the supply chain network. For effective and correct planning, preferably, the planning system will be able to take into account the various constraints that can be associated with each network resource. These restrictions can be based on factors such as time, quantity, quality, type of items available, and the like. Preferably, any model used to represent a resource network will also be robust so that the dynamic characteristics of many resource networks will be considered. In any model using a planning system, these increases in flow restrictions increase the overall complexity of the planning process. In addition, the model used for planning must take time into consideration. In order to plan network resources, real timing requirements must be considered. This means a real time delay. For example, when parts are really needed, the additional time needed to order the component parts for the assembly line needs to be considered. In addition, in any effective planning system, the time availability of the project (such as a finished product), the operation of the process, and the raw materials need to be considered. For various reasons, some of which have been described above, the cost of planning the use of resources to meet demand can be prohibitive. In order to efficiently and effectively meet the planning needs of today's business, it is very robust, and can identify and accommodate many constraints and sometimes business conflicting goals. Planning systems and methods (4) (4) 200305088 method is very desirable . Therefore, the present invention is directed to a system and method for planning the optimal use of commercial resources to fulfill orders. More specifically, the present invention provides a system and method for generating and maintaining restriction and attribute-sensitive planning of the use of multiple resources located in multiple locations to form one or more orders. Traditional planning systems for placing orders on schedules and allocating resources are often driven by inventory holding units (SKUs). Another approach is to use a property-based approach. The constraints and business rules that govern supply chain planning are often driven by certain basic characteristics (attributes) of the product, market, and operating environment. Therefore, the representation of the model should be achieved from the perspective of these attributes. According to a specific embodiment of the present invention, there is provided a system called an attribute-based planning (ABP) system. This system may include a computerized storage device for the transfer of the ampoules. If one or more subscriptions with attributes a scare the need, they can be entered into the system, which will generate a plan for the use of resources within the network. The order can be an internally or externally generated order, or it can even be the customer demand as shown in Table 2. After processing the order, the ABP system will immediately plan for the utilization of network resources to complete the demand. According to another specific embodiment of the present invention, inventory holding. Thousands of 70 attribute definitions D) Groups are generated and defined. The ABD group according to the present invention uses SAD groups to provide various system functions. For example, the " m ^ group can take orders in priority order, and organize resources into parts such as food and / or bill of materials (BOM), and groups of similar things ~ and *, called 1 *, , And. In order to fully enter the various functions, various tables will be produced. For example, the table 200305088 (5) will protect Wifi including temporary tables for unplanned orders, BOM and configuration tables, SAD groups, and the like. In addition, a transportation matrix will be created to track and consider transportation issues.

根據本發明之另一具體實施例,用於規劃資源的使用, 以滿足需求之程序包括初始化程序。初始化程序會包括許 多步驟,其會包括用以產生及/或產生靜態模型之步驟。 為了模型化資源網路,較佳而言,各種項目將會定義出來 。這些包括可用資源、位置、包括容量及附屬限制之各種 型式的限制、時間桶狀區間、商業規則、使用者及客戶偏 愛、組態、傳輸矩陣及Β Ο Μ、以及類似之物。初始化步 驟會包括初始化桶狀區間之步驟。桶狀區間的初始化可藉 由將一種或多種限制與桶狀區間結合而達成。初始化程序 也會包括安置初始分配及配置材料之步驟。初始化程序也 會包括產生暫時表及未規劃訂單的表之步驟。According to another specific embodiment of the present invention, the program for planning the use of resources to meet the requirements includes an initialization program. The initialization procedure may include many steps, which may include steps to generate and / or generate a static model. To model the network of resources, various projects are better defined. These include available resources, locations, various types of restrictions including capacity and ancillary restrictions, time buckets, business rules, user and customer preferences, configuration, transmission matrix and beta, and the like. The initialization step will include a step of initializing the bucket interval. The initialization of the bucket interval can be achieved by combining one or more restrictions with the bucket interval. The initialization procedure will also include steps to place the initial distribution and configuration materials. The initialization process will also include steps to generate temporary tables and tables for unplanned orders.

根據本發明之另一具體實施例,用來處理訂單的程序會 包含於用於規劃網路資源的使用之程序中。第二程序會包 括選擇基於SAD群組的一組訂單、載入具有一組訂單及其 相關資料的視窗、將視窗中的每個訂單按優先順序處理、 以及根據其屬性來處理視窗中的每個訂單之步驟。ABP 系統會藉由處理群組中的訂單而規劃,一次一個群組。處 理過之每個群組的訂單會安置在視窗中。視窗中的訂單會 按優先順序處理,並且基於其屬性而處理規劃。相關於每 個訂單的資料也會載入到視窗。這樣的資料可例如包括以 SKU為基礎的BOM、組態、次要項目的存貨保持單元、成 -10- 200305088 ⑹ 品存貨保持單元、以及類似之物。 根據另-具體實施例,用來處理訂單的程序會包括處理 視窗中的每個未規劃訂 個—时、丰 平 ,入一個扦早 < 步驟。在規劃 未規劃的訂單之前,萃絲备 糸、,无曰產生用於資源的初始分配,以 束結用於特定訂單的資 、 貝源—旦初始分配已產生,用於未 規劃的訂單之規劃會 Αβρ系統會重新檢查BOM、組 感、相關的成品存貨傻姓留^ ” 貝保持早兀、次要項目存貨保持單元、 SAD群組、以及類似 、 ,wo 、’ ’以規劃每個訂單。相關於每個 n丁早的每種組態( 、相關的SAD群組,次要項目SKU)會 重新檢查及檢查,以判 刻斷那—個位置/資源/桶狀區間機會 會牷供最佳的機會。 根據本發明之另一且m 祛嬙合▲ # “仏實施例,判斷用於每個訂單的最 佳機會會猎由以下的步 H _ 來達成。首先,會選擇組態及將 了允繂的位置按優先順 ^ f 0 . ^ 斤處理。然後會選擇最高的優先權 位置/成品存貨保持單元。 Ϋλ Ά ^ m 将成品存貨保持單元初始化’ 以及判斷用於最高優先 ^ ^ ^ 2 仅置之可允許資源的集合。會決 疋用於每個資源之材料 ARP ί ^ 行性。在決定材料可行姓中, ΑΒΡ系統首先會檢查資 σ沾& +、 #貪’以判斷是否存貨可供應物 口口的凊求量。如果依照 堂七n如、 、7例如由使用者或客戶所定義(如 而求日期)之指定參數, q ^ 賞源存貨不能完全地供應物品的 足夠里,則系統會檢查另—# ^ ^ —種可行的方法,以滿足經由此 貝源的需求。用以滿足需 食Μ $、 而I的其他方法例如包括藉由製造 商的補无、藉由購買的補 土 Α山m 補无及/或藉由取代的補充。一旦 決疋出用於資源的材料 J仃性,則ABP系統會做出限制可 200305088According to another embodiment of the present invention, a procedure for processing an order is included in a procedure for planning the use of network resources. The second procedure will include selecting a set of orders based on the SAD group, loading a window with a set of orders and their related information, prioritizing each order in the window, and processing each order in the window according to its attributes Steps for each order. The ABP system is planned by processing orders in groups, one group at a time. Orders for each group processed are placed in the window. Orders in the window are processed in order of priority and planning is handled based on their attributes. The data related to each order is also loaded into the window. Such information may include, for example, a SKU-based BOM, a configuration, a inventory holding unit for a minor item, a -10-200305088 counterfeit inventory holding unit, and the like. According to another specific embodiment, the procedure used to process the order will include processing each unplanned order in the window—hours, hours, and hours, and into a premature < step. Before planning unplanned orders, the company prepares for the initial allocation of resources to consolidate the capital used for specific orders. Once the initial allocation has been generated, it is used for Planning meeting Αβρ system will re-check BOM, group sense, related finished product inventory silly surnames ^ "Bei keep early, secondary item inventory holding unit, SAD group, and similar ,, wo, '' to plan each order .Each configuration (, related SAD group, minor project SKU) related to each n will be re-examined and inspected to determine the location / resource / barrel interval opportunity The best opportunity. According to another embodiment of the present invention, the combination of ▲ # “仏 embodiment, judging the best opportunity for each order will be achieved by the following step H_. First, the configuration will be selected and the allowed position will be processed according to priority ^ f 0. ^ The highest priority location / finished product holding unit is then selected. Ϋλ Ά ^ m Initialize the finished product inventory holding unit ’and judge it for the highest priority ^ ^ ^ 2 Set only the set of allowable resources. The decision will be made on the material ARP used for each resource. In determining the feasible surnames of the materials, the ΑBP system first checks the assets σ && +, # # 'to determine whether the inventory is available and the quantity required. If according to the specified parameters defined by the user or customer (such as the date), q ^ reward source inventory can not completely supply the goods, the system will check another — # ^ ^ -A feasible method to meet the needs of this source. Other methods to meet the demand M $, and I include, for example, replenishment by the manufacturer, replenishment by the purchase of supplements, and / or supplementation by replacement. Once the nature of the materials used in the resource is determined, the ABP system will make restrictions on

⑺ 行性的評估,以及材料容量相容性的檢查。用於每個可接 受位置/資源/桶狀區間機會的這些步驟會重複。 然後每個位置/資源/桶狀區間機會基於各種目標及客 戶偏愛而評估出來。然後最佳的位置/資源/桶狀區間機會 選擇用於規劃網路資源的使用之目的,並且輸出會產生。 根據本發明之另一具體實施例,凍結SAD群組會產生及 用來凍結一個或多個訂單。此可用來確定訂單已做規劃, 即使訂單不是可行的。 根據本發明之另一具體實施例,ABP系統會識別多級目 標函數,以決定最佳的位置/資源/桶狀區間機會。多級目 標函數會提供用以達成希望的規劃結果之標準。較佳而言 ,ABP系統會併入多級目標函數,以決定用於規劃上的訂 單之最佳安置。如果ABP系統找出用於規劃訂單的多個機 會,則ABP系統會將每個機會分等級,並且選擇基於多個 目標之最佳機會。 根據本發明之另一具體實施例,各種表會產生,以提供 一些功能。這些表包括,例如,預定分配表、BOM表、 SAD群組表、以及類似之物。 根據本發明之另一具體實施例,一群訂單會選擇出來, 並且會藉由產生一種或多種SKU屬性來做規劃,其中SKU 屬性群組係相關於藉由屬性之一個或多個訂單、基於一個 或多個SKU屬性群組而將訂單按優先順序處理、基於載入 視窗中之訂單的優先權,而選擇一個或多個訂單、選擇來 自於視窗中的訂單、以及規劃資源的使用,以達成來自於 -12- 200305088 (8) 視窗中的選擇訂單。 根據本發明之另一具體實施例,藉由製造之資源的補充 之決定可藉由決定有關於訂單的屬性資料來達成,其中資 料包括相關於訂單的存貨保持單元、基於訂單屬性而將一 種或多種組態結合到訂單,其中組態包括一個或多個次要 項目存貨保持單元、基於每種組態來評估組態且判斷是否 每種組態是否可行、以及基於組態的評估而選擇用於規劃 資源的使用之可行的組態。 根據本發明之另一具體實施例,藉由購買之資源的補充 之決定可藉由決定時間項目來達成,其中時間項目為有關 於訂單之時間或時間週期内的特定點、基於時間項目來決 定時間事件、產生包括時間事件及時間項目之時間線、基 於時間線而從一群預定方案中選擇可用的方案、以及基於 可用的方案而產生輸出。 根據本發明之另一具體實施例,列入計畫表控制可用來 得到最佳資源使用規劃。列入計畫表控制為用來影響搜尋 桶狀區間,以找出安置訂單的可行機會之方式的方案《有 許多型式的列入計畫表控制可用,包括往前、往後、剛好 在時間内、凍結、以及不列入計畫表。 根據本發明之另一具體實施例,所提供的是用於規劃網 路資源的使用,以完成如由訂單所定義的需求之一種方法 。訂單係具有屬性資料,並且此方法包括定義訂單的參數 、基於訂單屬性資料而將一種或多種組態結合到訂單、基 於組態而決定可接受的位置-資源-桶狀區間機會,其中組 (9) (9)200305088 態包括一個或多個存貨保持單元、評估每個位置-資源_ 桶狀區間機會、以及基於每個位置·資源_桶狀區間機會的 評估,選擇位置-資源·桶狀區間機會中的—個當作最1的 位置·資源-桶狀區間機會之步驟。 根據本發明之另一具體實施例,所提供的是用於規劃網 路資源較用,以完成如㈣單所定義的需求之一種方法 此万法包括首先會識別相關於基於訂單屬性資料之訂單 的成品存貨㈣單元、將成品存貨保持單元#始化、基於 -始化的…貨保持單元,決定可允許位置的集合及用 於母個可允許位置之可允許資源的集合、評估用於每個可 允許位置及可允許的資源組合之位置資源,狀區間機 會、以及基於評估,選擇位置·資源_桶狀區間機會中的一 個當作最佳的位置-資源-桶狀區間機會之步驟。 在下列說明中將提出本發明的其它特徵與優點,其中一 邵分從該說明中就可理解,或是可藉由實作本發明而習得 本發月的目的及其它好處將可由以下文中的說明及申請 專利範圍,以及所附圖面所特別指出的結構來實現及達到。 為了達成這些及其他的優點,以及根據本發明的目的, 會具體實施及做廣泛地說明。 其必須瞭解到,先前之本發明的一般性說明及以下的詳 、’·田說明為範例性及說明性,其係要提供如所主張的本發明 之進一步解釋。 實施方式 現在將詳細參考到本發明的較佳具體實施例,其範例係 -14 - 200305088 (ίο) 說明所附圖面中。 在此所揭露的本發明將併入共同等候判定及一般讓渡 的美國非暫定申請案之内容作為參考:2002年11月4曰申 請’尚未指定序號,代理人文件號82001.0350之Crampton 等人的「具以屬性為基礎之規劃之訂購群組規劃系統及方 法」;2002年11月4日申請,尚未指定序號,代理人文件號 82001.0390之Cramp ton等人的「藉由以屬性為基礎之規劃 所製造之補充系統及方法」;2 0 0 2年1 1月4日申請,尚未指 定序號’代理人文件號82001.0391之Crampton等人的「藉 由以屬性為基礎之規劃所購買之補充系統及方法」;2002 年11月4日申請,尚未指定序號,代理人文件號82001.0392 之Cramp ton等人的「具以屬性為基礎之規劃之訂購群組規 劃系統及方法」;200 1年7月13曰申請,序號09/903,8 5 5, 代理人文件號8200 1 -0 1 48之Weber等人的「策略運輸規劃 系統及方法」;以及2001年10月1日申請,序號09/965,854 ,代理人文件號82001-0189之Z are foss等人的「包含共同 研究的供應鏈管理系統及方法具以屬性為基礎之規劃之 訂購群組規劃系統及方法」。 本發明係提供製造或供應鏈網路中的資源之最佳規劃 及計畫表之系統及方法。此系統(稱為屬性基礎規劃(ABP) 系統)可將SKU及屬性模型化。藉由此系統所實施的ABP 系統及程序會產生輸出,其用來定義使用供應鏈的資源之 規劃。輸出可以是文字、原料、圖形或對於規劃用途有用 的任何其他形式。A B P系統可與如此項技術中所熟知之各 200305088 00 種其他的商業規劃、計畫表、購買、共同研究、以及可 用型式的系統及應用裝置(包括商業上全部可由 Manugistics公司取得的網路策略、網路順序安排、以及 網路共同研究)做為介面。相關於AB P系統的各種功能可 藉由以下伴隨描述用來實施本發明的新穎性方面之各種 觀念的附圖之說明,而最佳地了解。 本發明的以下說明將參考各種項目,其中的某些明白地 定義於以下術語中。⑺ Evaluation of performance and check of material capacity compatibility. These steps are repeated for each acceptable location / resource / bucket interval opportunity. Then each location / resource / barrel interval opportunity is evaluated based on various goals and customer preferences. Then the best location / resource / barrel interval opportunity is selected for the purpose of planning the use of network resources, and the output will be generated. According to another embodiment of the present invention, freezing the SAD group is generated and used to freeze one or more orders. This can be used to confirm that the order has been planned, even if the order is not feasible. According to another specific embodiment of the present invention, the ABP system recognizes a multi-level objective function to determine the optimal location / resource / barrel interval opportunity. Multilevel objective functions provide the criteria to achieve the desired planning results. Preferably, the ABP system incorporates a multi-stage objective function to determine the optimal placement of orders for planning purposes. If the ABP system identifies multiple opportunities for planning an order, the ABP system ranks each opportunity and selects the best opportunity based on multiple goals. According to another embodiment of the present invention, various tables are generated to provide some functions. These tables include, for example, a predetermined allocation table, a BOM table, a SAD group table, and the like. According to another specific embodiment of the present invention, a group of orders will be selected and planned by generating one or more SKU attributes, where the SKU attribute group is related to one or more orders by attributes, based on one Or multiple SKU attribute groups to prioritize orders, select one or more orders, select orders from the window, and plan the use of resources based on the priority of orders loaded in the window to achieve From -12-200305088 (8) Select the order in the window. According to another specific embodiment of the present invention, the decision to supplement the manufacturing resources can be achieved by determining the attribute data about the order, where the data includes an inventory holding unit related to the order, and one or Multiple configurations are combined into the order, where the configuration includes one or more minor item inventory holding units, evaluating the configuration based on each configuration and determining whether each configuration is feasible, and selecting to use based on the evaluation of the configuration A viable configuration for planning the use of resources. According to another specific embodiment of the present invention, the decision of supplementing the purchased resources can be achieved by determining a time item, wherein the time item is a specific point in the time or period of the order and is determined based on the time item Time events, generating a timeline including time events and time items, selecting an available scheme from a group of predetermined schemes based on the timeline, and generating an output based on the available schemes. According to another embodiment of the present invention, the schedule control can be used to obtain the optimal resource usage plan. Inclusion plan control is a scheme used to influence the search of bucket-like intervals to find feasible opportunities for placing orders. "There are many types of incorporation plan controls available, including forward, backward, and just in time. Internal, frozen, and excluded from the schedule. According to another specific embodiment of the present invention, what is provided is a method for planning the use of network resources to fulfill the requirements as defined by the order. The order system has attribute data, and the method includes defining parameters of the order, combining one or more configurations to the order based on the order attribute data, and determining an acceptable location-resource-barrel interval opportunity based on the configuration, where the group ( 9) (9) 200305088 State includes one or more inventory holding units, evaluates each location-resource_ barrel interval opportunity, and selects location-resource · barrel based on the evaluation of each location · resource_ barrel interval opportunity One of the interval opportunities is regarded as the most position, resource-bucket interval opportunity step. According to another embodiment of the present invention, what is provided is a method for planning the comparison of network resources to fulfill the requirements as defined in the bill. This method includes first identifying orders that are related to order-based attribute data. The finished product inventory unit, the finished product inventory holding unit #, the initial-based ... inventory holding unit, determines the set of allowable locations and the set of allowable resources for the parent allowable locations, and evaluates for each A position resource, a permutation opportunity, and a combination of permissible position and permissible resource are selected as the best position-resource-barrel interval opportunity based on evaluation. Other features and advantages of the present invention will be presented in the following description. One of them can be understood from the description, or the purpose and other benefits of the present month can be learned by implementing the present invention. Explain and apply for the scope of the patent, as well as the structure specifically indicated in the drawings to achieve and achieve. To achieve these and other advantages, and in accordance with the purpose of the present invention, specific implementations and extensive descriptions will be made. It must be understood that the previous general description of the present invention and the following detailed descriptions are exemplary and illustrative, and are intended to provide further explanation of the invention as claimed. DETAILED DESCRIPTION Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. The invention disclosed herein takes the contents of the US non-tentative application incorporated into the common waiting judgment and general assignment as reference: November 4, 2002, the application 'No serial number has been assigned, agent file number 82001.0350 of Crampton et al. "Order group planning system and method with attribute-based planning"; applied on November 4, 2002, has not yet specified a serial number, agent document number 82001.0390, "by using attribute-based planning Supplementary systems and methods manufactured ";" Applications made on November 4, 2002, and not yet assigned a serial number 'Agent Document No. 82001.0391 "by Crampton et al.," Supplementary systems purchased through attribute-based planning and Method ";" Application system and method for ordering group planning with attribute-based planning "by Cramp ton et al., Who applied on November 4, 2002 and has not yet assigned a serial number, agent file number 82001.0392, etc .; July 13, 2001 "Application of Strategic Transportation Planning System and Method" by Weber et al., Application No. 09/903, 8 5 5 and Agent Document No. 8200 1 -0 1 48; and Application No. 09/965, October 1, 2001, 8 54, Z are foss of agent file number 82001-0189, etc. "Order group planning system and method including attribute-based planning of supply chain management systems and methods for joint research". The present invention is a system and method for providing optimal planning and planning of resources in a manufacturing or supply chain network. This system, called the Attribute Basic Planning (ABP) system, models SKUs and attributes. The ABP system and procedures implemented by this system produce outputs that are used to define the planning for the use of resources in the supply chain. The output can be text, raw materials, graphics, or any other form useful for planning purposes. The ABP system can work with 200,305,088 00 other business plans, plans, purchases, joint research, and available types of systems and applications (including all network strategies commercially available from Manugistics) , Network sequencing, and network research) as interfaces. The various functions related to the AB system can be best understood by following the accompanying drawings that describe various concepts used to implement the novel aspects of the present invention. The following description of the invention will refer to various items, some of which are clearly defined in the following terms.

術語 ABP系統:屬性基礎規劃(ABP)系統。一種規劃系統,用 以規劃資源的利用,以滿足需求。 BOM :材料清單。一種結構,其描述可製造SKU的各種方 式。每種記錄通常將母項目與子項目結合,並且拉取量會 告知多少子單元需用於每個母單元。此外,屬性限制會存 在,其會告知何時可利用此記錄。Terminology ABP system: Attribute Basic Planning (ABP) system. A planning system to plan the use of resources to meet demand. BOM: Bill of Materials. A structure that describes the various ways in which SKUs can be manufactured. Each record typically combines parent items with child items, and the pull amount tells how many child units are needed for each parent unit. In addition, attribute restrictions exist, which inform when this record is available.

桶狀區間(bucket): —種時間區間,通常用於限制及配置 物《在供應鏈最佳化系統中,規劃範圍通常區分成許多桶 狀區間。桶狀區間可具有相同長度,或者是在桶狀區間持 續時間會增加時,其可以縮短。例如,桶狀區間可定義為 天級的一個星期、星期級的三個星期、以及月級的三個月 。以下所述將給予涵蓋4個月的1 3個桶狀區間。如果桶狀 區間以天級的4個月來模型化,約1 2 0個桶狀區間將會模型 化。因為系統模型化的桶狀區間愈少,模型將會愈小且演 算法會愈快,所以桶狀區間的數目是重要的。 -16- 200305088Bucket interval: A time interval, usually used to limit and configure things. In the supply chain optimization system, the planning scope is usually divided into many bucket intervals. The barrel interval can be the same length or it can be shortened when the duration of the barrel interval increases. For example, a bucket interval can be defined as a week of the day, three weeks of the week, and three months of the month. The following will give 13 barrel-shaped intervals covering 4 months. If the bucket interval is modeled on a 4-month scale, about 120 bucket intervals will be modeled. Because the fewer bucket intervals the system models, the smaller the model and the faster the algorithm, the number of bucket intervals is important. -16- 200305088

(12) 組態(Configuration) ·· —組BOM記錄,其完全定義用於 SKU訂單之指定的可建構組態。 限制(Constraints):置於任一個入口上的任一種限制,如 資源,其會藉由ABP系統來辨識。限制可以是硬式(應該 絕不會揮發的溶液)或軟式(應該會試圖相符的溶液)。 限制桶狀區間(Constraint Bucket) ··相關於限制的桶狀區 間,其具有容量限制。通常將會有最大值。也會有放#資 訊來告知多少容量可能過度使用及做如此的費用。 限制規則(Constraint Rules): —種簡短方式,用來定義限 制桶狀區間的容量。例如,行事曆可與以星期級所區分的 限制結合,其中可用的每個單元會轉換成一數量的容量。 例如,如果有一種相關於一個人之以星期級所區分的勞工 限制,並且有一種定義可用輪班之行事麼,星期一至星期 四之為二次輪班(1個人* 4天* 2輪班/天* 8小時/輪班=6 4小 時),以及星期五可為一次輪班(1個人*丨天*丨輪班/天* 8小 時/輪班=8小時),則一個星期的容量將為64 + 8 = 72人小時。 需求(Demand):系統上的需求包含外部需求及相依需求 。外部需求包含客戶訂單及預測。相依需求為滿足獨立需 求所需的額外需求。 相依需求(Dependant demand):此為系統所產生的一組訂 單’其為配置於獨立需求之方向材料及容量的結果。 有效需求日期(Effective Need Date):此需求日期係低於 運送物品至指定位置所需的運輸時間。 FGSKU:成品存貨保持單元。SKU為成品。 -17- 200305088(12) Configuration ·· — A group of BOM records, which fully define the specified configurable configuration for SKU orders. Constraints: Any kind of restriction placed on any entrance, such as resources, will be identified by the ABP system. Limitations can be hard (a solution that should never evaporate) or soft (a solution that should attempt to match). Constraint Bucket • Restricted buckets have a capacity limit. There will usually be a maximum. There will also be # information to inform how much capacity may be overused and the cost of doing so. Constraint Rules:-A short way to define the capacity of the bucket interval. For example, calendars can be combined with restrictions that are distinguished by week level, where each unit available is converted into a quantity of capacity. For example, if there is a labor restriction related to one person that is distinguished by week, and there is a way to define the work that can be performed on a shift, the second shift is from Monday to Thursday (1 person * 4 days * 2 shifts / day * 8 Hours / shift = 64 hours), and one shift on Friday (1 person * 丨 day * 丨 shift / day * 8 hours / shift = 8 hours), then the capacity of a week will be 64 + 8 = 72 person hours . Demand: The requirements on the system include external requirements and dependent requirements. External demand includes customer orders and forecasts. Dependent needs are the additional requirements needed to meet independent needs. Dependant demand: This is a set of orders generated by the system. It is the result of arranging materials and capacity in the direction of independent demand. Effective Need Date: This need date is less than the shipping time required to deliver the item to the designated location. FGSKU: Finished Product Inventory Holding Unit. SKU is a finished product. -17- 200305088

(13) 旗標(Flag):旗標是用來表示指定條件、偏愛物、限制、 以及類似之物的存在。旗標也可用來控制規劃過程。例如 ’旗標係用來表示計畫表機會不是可行的,因此,ABP 系統需要察看其他計畫表機會。 凍結群組(Freeze Group): —種Sad群組,藉此相關於此 群、、且的每一玎單會凍結。這用於規劃週期,以確定即使不 可行,訂單將會列入計畫表中。 凍結群組表(Freeze Group Table):此表用來確認應該視之 為;東結的S A D群組。 獨立需求(Independent Demand):此為相對於相依需求之 傳运至系統的一組訂單,其相關於由ABp系統所產生的訂 單。 初始分配(Initial Assignment):傳送至系統的一種分配, 其表不先前的委託無論是否可行,應該都會兑現。每次 規劃程序執行時,在任何其他訂單規劃之前,初始分配將 會置入桶狀區間中。初始分配的配置會確認凍結訂單總是 位於規劃的相同位置。 位置(Location):位置為供應鏈中的某一處。每一個位置 會有一種名稱。 需求曰期(Need Date):訂單傳送及/或可利用之最希望的 曰期。 最早(Maximum Earliness):在請求物品將承兑的需求日期 前之時間區間。此值係由SAD群組來指定。 最晚(Maximum Lateness):在請求物品將承兑的需求曰期 •18- 200305088(13) Flag: A flag is used to indicate the existence of specified conditions, preferences, restrictions, and the like. Flags can also be used to control the planning process. For example, the ‘flag’ is used to indicate that schedule opportunities are not feasible, so the ABP system needs to look at other schedule opportunities. Freeze Group: —Sad group, by which every order related to this group will be frozen. This is used to plan the cycle to determine if the order is not feasible, the order will be included in the schedule. Freeze Group Table: This table is used to confirm that it should be considered as the SD Group of East End. Independent Demand: This is a group of orders that are shipped to the system relative to the dependent demand, which are related to the orders generated by the ABp system. Initial Assignment: An assignment transferred to the system, which indicates that the previous assignment should be fulfilled regardless of whether it is feasible or not. Each time the planning process is executed, the initial allocation will be placed in a bucket interval before any other order planning. The configuration of the initial allocation confirms that frozen orders are always in the same location as planned. Location: Location is somewhere in the supply chain. Each location will have a name. Need Date: The most desired date for order delivery and / or availability. Maximum Earliness: The time period before the date on which the requested item will be accepted. This value is specified by the SAD group. Maximum Lateness: The date when the requested item will be accepted • 18- 200305088

(14) 後之時間區間。此值係由sad群組來指定。 多、,及目“函數(Multi-level Objective Function):用來達成 希望的規劃結果之標準。較佳而言,ABP系統會合併多級 目標函數’以決定規劃上之訂單的最佳位置。如果ΑΒΡ 系統找出規劃訂單的多種機會,ΑΒ ρ會將每種機會分準位 ,並且會選擇基於多種目標之最佳機會。這些目標包括, 例如’晚(一種與訂單的有要需求日期相對之規劃訂單的 量測)、全部利用(一種如何填滿規劃訂單的容量限制之桶 狀區間的量測)、以及運輸(在製造訂單之資源的位置與訂 單上的客戶位置之間的運輸費用)。 汀單(Order):每種訂單包含預定及使用者定義屬性。預 定屬性可包括,例如,身份、SKU、數量、開始曰期(選 用)、需求日期、客戶、優先權、以及有效需求日期。要 注意的是,訂單及SKU可同時具有使用者定義屬性的值。 如果都具有值,訂單的值總是優先^例如,訂單 < 能疋名 為Joe Dealer的客戶之具有天窗及合金車輪的藍色卡車 因此’成品(亦即訂單)為具有以下屬性(蓝色、夭® 金車輪及Joe Dealer)的卡車。 %h要項 母項(Parent Item): —種B0M記錄,相關於母項及/入 0 見 B0M。 於在 規劃(Plan): —種經由時間而對資源的需求分配^, ; 某個時間期間(亦即,規劃範圍)來滿足一種或多種客戶 單。 關之物 期間最大量(Period Maximums):可用於指定桶狀區 -19- 200305088 (15) 品的取大量。 資源(Resource) ·· —種可為任何實體的資源,其為包括裝 配線、製造機器、倉庫、儲存場所、儲存櫃、供應商、以 及類似之物之物品的來源。通常每種資源可藉由名稱及位 置而獨一無二地識別出來。 SAD群組(SAD Group) : SKU屬性說明群組。SAD群組係 相關於各種模型化概念,並且告知訂單為可用的。每種 S A D群組可具有S K U的清單,以及相關於訂單之屬性的某 些或全部之屬性值的清單。例如,如果具有顏色(紅,藍) ,以及天窗(是/否)的屬性之關於模型1@1、模型1@2、以 及1型—2^.2的SKU存在,則某人可藉由寫出(sku : (M ^ 1或模型1 @2)及顏色(紅))而定義出概念上為紅色之遍 及全部模型1車輛之SAD群組。SAD群組可用來控制如何 使ABP系統將訂單列入計畫表中及規劃資源的使用。例如 ’玎單群組可用來決定在處理訂單之前,關於訂單群組之 最早及最晚時間、關於訂單群組之計畫表控制、定義關於 訂單之「最佳」配置的次序(m e t r i c s)及目標、以及類似的 事物,如何排序訂單。每種S AD群組可按優先順序處理, 以致於屬於某一 SAD群組的訂單可在屬於較低優先權的 SAD群組之訂單之前,列入計畫表中。 計晝表控制(Scheduling Controls):用來影響方式的計書 ’其中會搜尋桶狀區間,以找出訂單的可行位置。有許多 可用的計畫表控制的型式,包括提前、延後、剛好在時間 内、凍結及不列入計畫表中。 -20- 200305088(14) Later time interval. This value is specified by the sad group. Multi-level Objective Function: The standard used to achieve the desired planning result. Preferably, the ABP system will incorporate multi-level objective functions to determine the optimal position of the order on the plan. If the ΑBP system finds multiple opportunities to plan an order, Αρ will classify each opportunity and select the best opportunity based on multiple goals. These goals include, for example, 'late (a relative to the date of the demand for the order) Measurement of planned orders), full utilization (a measurement of how to fill the barrel-shaped interval of the planned order's capacity limit), and transportation (transportation costs between the location of the resources of the manufacturing order and the location of the customer on the order ). Order: Each order contains reservation and user-defined attributes. Reservation attributes can include, for example, identity, SKU, quantity, start date (optional), demand date, customer, priority, and valid demand Date. Note that both the order and the SKU can have values for user-defined attributes. If both have values, the value of the order always takes precedence ^ For example Orders < Blue truck with sunroof and alloy wheels for a customer named Joe Dealer, so the 'finished product (i.e. order) is a truck with the following attributes (blue, 夭 ® gold wheels and Joe Dealer).% H Parent Item: — a kind of B0M record, related to the parent item and / or 0 See B0M. In Plan (Plan): — a kind of demand for resource allocation over time ^,; a certain period of time (also That is, planning scope) to satisfy one or more customer orders. Period Maximums: can be used to specify the barrel area -19- 200305088 (15) to take a large number of products. Resource Can be any physical resource, which is the source of items including assembly lines, manufacturing machines, warehouses, storage locations, storage cabinets, suppliers, and the like. Usually each resource can be uniquely identified by its name and location SAD Group: SKU attribute description group. SAD group is related to various modeling concepts and informs the order is available. Each SAD group can have a list of SKUs, and A list of some or all of the attribute values for the attributes of the order. For example, if there is a color (red, blue) and skylight (yes / no) attributes about model 1 @ 1, model 1 @ 2, and type 1 —2 ^ .2's SKU exists, then someone can define (red) (sku: (M ^ 1 or model 1 @ 2) and color (red)) the concept of red throughout all Model 1 vehicles. SAD group. The SAD group can be used to control how the ABP system places orders in the schedule and plans the use of resources. For example, '玎 Order Group' can be used to determine the earliest and latest time about order group, schedule control about order group, define the order of "best" configuration about order, and Goals, and similar things, how to order. Each SAD group can be processed in order of priority, so that orders belonging to a SAD group can be listed in the plan table before orders belonging to a lower priority SAD group. Scheduling Controls: Schedule books used to influence the way ’barrel-like intervals are searched to find out the feasible position of the order. There are many types of schedule controls available, including advance, postponed, just in time, frozen, and not included in schedules. -20- 200305088

(16) 計畫表機會(Scheduling Opportunity):定義將訂單列入計 畫表中的機會之一種位置/資源/桶狀區間或資源/桶狀區 間,其滿足對於訂單及桶狀區間,資源及/或位置之所有 可用的限制。 SKU :每種SKU係相關於項目及位置。SKU具有預定屬性 及使用者定義屬性。SKU可以是原料、處理中的產品 ("WIP”)、成品、或WIP及成品。SKU可以是硬式或軟式限 制,並且如果原料將會具有一種補充模型,其會告知是否 可以補充材料,以及如果如此的話,如何做。 平滑限制(Smoothing constraint): —種限制的型式,其會 才曰引系統計算關於基於負載及範圍内之可用時間總量的 限制之每單位時間容量的平均量。每一桶狀區間的最大值 會$又足成可用時間的量乘以每單位時間平均量。 次要項目(Subordinate Item): —種相關於母項及次要項的 B0M記錄。見bom定義。 使用者疋義屬性(UDA)(User Defined Attribute,UDA): — 種實施特性的屬性。例如,汽車實施的客戶對於每種車會 有顏色屬性。電腦實施中的客戶可能不會具有顏色,但是 可能會有硬碟尺寸。 一般概念 本發明係有關於規劃訂單及資源的屬性基礎系統。為了 易於了解本發明的各種新穎性,底下會提供伴隨各種概念 的解釋之例子。以下的例子會介紹可用於了解本發明的創 新方面之概念。 -21 - (17) 200305088 根據本發明之一1 、 /、體實施例的ΑΒΡ系統為強健規劃系 ^ f可運作於南複雜度及高動態環境。參照圖1,其繪 勺疋運作於|巳例環境中的Ab p系統1 〇 〇之方塊圖。ab p 系統1 〇 〇可传闲碰科 j災隨及軟體的結合而實施。ABP系統1 〇〇 T包括資料座1〇1$ 厚 4 了與位於如個人電腦、工作站、伺服 抑X及㉘似之物之單一或多個電腦上的一個或多個資料 庫做為介面。圖1緣示的是汽車製造業者的製造網路,其 曰氣k二種基本汽車模型,、SUVs、以及Minivan 因為可選擇的數目(例如,動力驅動窗、天窗、以及類 似疋物)係由汽車製造業者提供,所以網路必須能使三種 土本模型型式做出很多變化。網路包括亞特蘭大、丹佛及 R〇CkVlUei三個製造廠所102至106。每個場所102至106 依序包括多種資源i ! 〇、1 2 〇及i 3 〇。資源i i 1 2 〇及1 3 〇 可為裝配線、倉庫、機器設備、存貨清單或任何其他實體 其為任何可由客戶所請求之成品的來源。就某種意義來 說’每種資源110、120及130可以是獨一無二的,每種可 一有不同的容量、運作時間、產品線、以及其他的限制。 限制對於資源、資源的群組、位置或資源的群組會存在特 定的。再者,汽車製造業者可執行某種規則,其會在資源 及位置上,配置更多的限制。每種資源11〇、12〇及13〇可 相關於一種或多種材料140。材料140為任意元件部分或元 件材料,或甚至是可由資源所需求的成品,以產生成品。 看待資源1 1 0、1 20及1 3 0的一種方式就是視它們為一種井 其可藉由,例如,製造、購買或取代來補充。雖然未顯 -22· (18) (18)200305088 示,但是其他的材料也可以做為材料14〇。亦即,做為資 源110到130的材料140可由其他的材料來組成。汽車製造 業者有許多客戶150,其會交付訂單16〇到汽車製造業者。 訂單會由ABP系統1〇〇來符合語法,並且會產生一種規劃 ,其用來履行多種訂單之資源的最佳利用。每種單定會包 含相關資訊,當將訂單列入計畫表中時,其可用來產生某 種參數。這些包括請求傳送日期及位置、請求產品的識別 、請求產品的數量、客戶識別、傳輸模式、以及類似之事 物。訂單中所請求的成品可視之為「成品存貨保持單元 (FG SKU)」。通常將會有多種組態及元件材料來滿足每種 FG SKU所訂定的需求。例如,假設客戶訂了轎車。進一(16) Scheduling Opportunity: Defines a position / resource / barrel interval or resource / barrel interval for the opportunity to place an order in the schedule. It satisfies the order and barrel interval, resources, and And / or all available restrictions for the location. SKU: Each SKU is related to the project and location. SKUs have predetermined attributes and user-defined attributes. SKUs can be raw materials, products in process (" WIP "), finished products, or WIP and finished products. SKUs can be hard or soft restrictions, and if the raw materials will have a supplementary model, it will tell if supplementary materials are possible, and If so, how to do it. Smoothing constraint (smoothing constraint): a type of constraint that will allow the system to calculate the average amount of capacity per unit of time regarding the limit based on the load and the total amount of time available within the range. The maximum value of a bucket interval will multiply the amount of available time by the average amount per unit time. Subordinate Item:-A B0M record related to the parent and secondary items. See the definition of bom. Use User Defined Attribute (UDA): — An attribute of an implementation characteristic. For example, customers of a car implementation have color attributes for each type of car. Customers in a computer implementation may not have color, but may There will be hard disk size. General Concept The present invention relates to a property-based system for planning orders and resources. To facilitate understanding of various aspects of the present invention The following examples will introduce concepts that can be used to understand the innovative aspects of the present invention. -21-(17) 200305088 According to one of the embodiments of the present invention, The ABP system is a robust planning system. It can operate in a highly complex and highly dynamic environment. Referring to Figure 1, it depicts a block diagram of the Ab p system 100 in an example environment. The ab p system 1 〇 〇 Can be transmitted and implemented with the combination of software and disaster. The ABP system 100T includes a data base 1010 $ thick 4 and a single unit such as a personal computer, workstation, servo X and the like One or more databases on one or more computers are used as the interface. Figure 1 shows the manufacturing network of an automobile manufacturer, which includes two basic car models, SUVs, and Minivan because of a selectable number. (For example, power drive windows, sunroofs, and similar objects) are provided by car manufacturers, so the network must be able to make many changes to the three native model types. The network includes three manufacturing plants in Atlanta, Denver, and RokkVlUei. 102 to 106. Each site 102 to 106 includes multiple resources in sequence i! 〇, 12 〇, and i 3 〇. Resources ii 1 2 0 and 1 3 〇 can be assembly lines, warehouses, machinery and equipment, inventory lists or any Other entities are the source of any finished product that can be requested by the customer. In a sense 'each resource 110, 120 and 130 can be unique and each can have a different capacity, operating time, product line, and Other restrictions. Restrictions may be specific for resources, resource groups, locations, or resource groups. Furthermore, automobile manufacturers can implement certain rules, which will place more restrictions on resources and locations. Each resource 110, 120, and 130 may be associated with one or more materials 140. Material 140 is any component part or component material, or even a finished product that may be required by resources to produce a finished product. One way to look at resources 110, 120, and 130 is to treat them as a well that can be supplemented by, for example, making, buying, or replacing. Although not shown in -22 · (18) (18) 200305088, other materials can also be used as material 14. That is, the material 140 as the resources 110 to 130 may be composed of other materials. The automaker has many customers 150 and will deliver orders 160 to the automaker. Orders will be grammatically conformed by the ABP system 100, and a plan will be generated that makes the best use of resources to fulfill multiple orders. Each order contains relevant information, which can be used to generate certain parameters when placing the order in the planning table. These include the date and location of the requested transmission, the identification of the requested product, the number of requested products, the identification of the customer, the mode of transmission, and the like. The finished product requested in the order can be considered as a "FG SKU". There will usually be multiple configurations and component materials to meet the requirements set by each FG SKU. For example, suppose a customer orders a car. Into one

步假設用來建造轎車的全部所需為三種元件,元件A 、以及C或D。在此例巾,至少有二種可能組態,所建造Steps assume that all three components required to build a car are components A, and C or D. In this example, there are at least two possible configurations.

的轎車具有元件A、…,以及所建造的轎車具有元件A m。這些不I组態及元件材料可列入材料清單(在此 為BOM)之中。 除了上述之限制及訂單參數之外’製造資源規劃系统+ 規劃網路資源的利用時,必須能適應—些其他重要因素田 例如’如果在希望曰期或接近希望曰期時要傳送成品:訂 單及/或製造元件部分及正確時間的材料是需要的。如果 在適當的時間未訂購材料’則履行訂單的材料將 在所需求部分的時間之前之元件部分的訂購為具曰有有效 及適時製造能力的關鍵之一。 規劃及列入計畫表是連續的程序。因此,任何的有效規 •23- (19) 2003050S8 劃系統必須能適應在 單之前,已列…表 丁使用可用製造資源的新訂 較佳而言,可信二Γ:已列入計畫表的分配或訂單。 Ϋλ ^ 、、見劃系統將能適應習性、商業規^ 、以及4多型式的製造 商業見則 網路。例如,M e者m括u複雜的製造 ^以者可依循剛好在時間内的 要在請求傳送日期之前, 心,因此需 製造者可能更喜歡在客 另一万面, 戶了接丈的最早日期,傳 〇 這些目標對於每個製造者是特有的,以及可能、種^ 式的訂單是特有的(經由模型、客戶、優先權等):以及; 幫助製造者了解其長期的目桴。^及了 ^因此,會滅別及適應製造 者的特疋需求之系統會非常令人滿意。 公司(如大製造者)通常會從多個客戶中,接收一些訂單 及/或對於尚未給予其訂單的客戶做預測。客卢可為第三 方、在相同公司中的部門、供應鏈伙伴或任何其他的賣I 。由公司所接收的每種訂單可由其如客戶名稱、訂單身份 、請求的SKU、需求日期、數量及類似之物的屬性所定義 。通常SKU將至少由二種屬性所定義,稱為物品及位置。 S K U可具有使用者定義屬性的值。s K U也可群組化成成口 (FG)SKU、處理中的產品(WIP)SKU、或原料SKU。原料 及WIP SKU的項目在BOM中,可能是次要的。次要項目為 需用來產生另一個項目之元件部分或材料。要注意的是關 於訂單之使用者定義屬性的值可使關於SKU之使用者定 義屬性的值無效。例如,SKU可具有天窗使用者定義屬性 之不正確的預設值(意謂無天窗)。特定訂單可使此值無效 -24- 200305088 (20) ,以及設定天窗使用者定義屬性為真。這些概念可以以 下的例子而最佳地了解。假設FG SKU可由以下的屬性來 定義[項目==轎車,位置=亞特蘭大,選擇=動力方向盤]。 進一步假設關於基本轎車模型之用來建造F G S KU組件部 分A、B、以及c及關於動力方向盤選擇的額外元件(「方 向盤組件」)是需要的。在此例中’有四種次要項目SKU ,在亞特蘭大的組件A、在亞特蘭大的組件B、在亞特蘭 大的組件C及在亞特蘭大的方向盤組件。 A B P系統1 〇 〇可將s K U ’以及使用者定義屬性值組織成 S K U屬性說明(在此為「S A D」)群組。訂單的s A D群組將 相關於具有「至少」定義SAD群組之相同屬性的任何訂單 。因此,只要其具有「至少」定義SAD群組的屬性,具有 比定義SAD群組的屬性之更多屬性的訂單會屬於sad群 組。例如,假設S A D群組係由以下的二種屬性所定義[項 目=轎車及位置==亞特蘭大],則無論訂單是否相關於其他 屬性,具有這二種屬性的所有訂單將屬於SAD群組。例如 ,具有屬性[項目=轎車、位置=亞特蘭大及電動窗=是]的 訂單將屬於SAD群組。滿足由SAD群組所定義的條件之訂 單係視為此群組的部分。ABP系統1〇〇係使用sad群組, 以提供一些功能。例如,在其他功能之中,sad群組可用 於:定義用於訂單之屬性易受影響的材料清單(b〇m);定 義屬性易受影響的存貨;定義屬性易受影響的取代品;將 限制應用於訂單;定義用於訂單的最早/晚日自;定義用 於訂單的專用資源群組;將規律用於訂單;定義用於訂單 -25- (21)200305088The sedan has elements A, ..., and the sedan built has element Am. These different configurations and component materials can be listed in the bill of materials (here BOM). In addition to the above restrictions and order parameters, 'manufacturing resource planning system + planning network resource utilization must be able to adapt — some other important factors such as' if the finished product is to be transmitted at or near the desired date: order And / or materials to make the component parts and the right time are needed. If the material is not ordered at the appropriate time, then the material fulfilling the order will be one of the keys to effective and timely manufacturing capabilities for ordering the component parts before the time of the required part. Planning and inclusion in the schedule is a continuous process. Therefore, any effective regulations • 23- (19) 2003050S8 planning system must be able to adapt to the list before the list ... Table new use of available manufacturing resources is better, believable II Γ: already listed in the plan table Assignment or order. Ϋλ ^, and planning system will be able to adapt to habits, business rules ^, and more than 4 types of manufacturing business rules network. For example, Me and M include complicated manufacturing, and the user can follow the request within the time just before the transmission date. Therefore, the manufacturer may prefer to be the earliest and the earliest. Date, pass. These goals are unique to each manufacturer, and possible, different types of orders are unique (via models, customers, priorities, etc.): and; help manufacturers understand their long-term goals. ^ And ^ Therefore, a system that will eliminate and adapt to the special needs of the manufacturer will be very satisfactory. Companies (such as large manufacturers) typically receive orders from multiple customers and / or make predictions for customers who have not yet given their orders. Kelu may be a third party, a division within the same company, a supply chain partner, or any other seller. Each order received by the company can be defined by its attributes such as customer name, order identity, requested SKU, demand date, quantity, and the like. SKUs are usually defined by at least two attributes, called items and locations. SKU can have values for user-defined attributes. s K U can also be grouped into a mouthful (FG) SKU, a product in process (WIP) SKU, or a raw material SKU. Raw materials and WIP SKU items may be secondary in the BOM. A minor item is a component part or material that needs to be used to produce another item. It should be noted that the value of the user-defined attribute on the order can invalidate the value of the user-defined attribute on the SKU. For example, SKUs can have incorrect preset values for sunroof user-defined attributes (meaning no sunroof). Certain orders can invalidate this value -24- 200305088 (20) and set the sunroof user-defined attribute to true. These concepts can be best understood with the following examples. Assume that the FG SKU can be defined by the following attributes [item == car, location = Atlanta, select = power steering wheel]. It is further assumed that parts A, B, and c for building the F G S KU assembly for the basic car model and additional components for steering wheel selection ("steering wheel assembly") are needed. In this example, there are four secondary item SKUs: component A in Atlanta, component B in Atlanta, component C in Atlanta, and steering wheel component in Atlanta. The A B P system 1 〇 〇 can organize SK U ′ and user-defined attribute values into S KU attribute description (here, “S A D”) group. The s A D group of orders will be related to any order that has the same attribute that "at least" defines the SAD group. Therefore, as long as it has attributes that at least define the SAD group, orders with more attributes than those that define the SAD group will belong to the sad group. For example, suppose the SAD group is defined by the following two attributes [item = car and location == Atlanta], regardless of whether the order is related to other attributes, all orders with these two attributes will belong to the SAD group. For example, orders with attributes [item = car, location = Atlanta, and power window = Yes] will belong to the SAD group. Orders that meet the conditions defined by the SAD group are considered part of this group. The ABP system 100 uses a sad group to provide some functions. For example, among other functions, the sad group can be used to: define a list of materials (b0m) that are vulnerable to attributes for an order; Restrictions apply to orders; define earliest / late date for orders; define dedicated resource groups for orders; apply rules to orders; define for orders-25- (21) 200305088

的列入計畫 ,將訂單排 將達反應用 時候,或不 通常會有身 示給使用者 劃程序,以 SAD群組 的例子為由 =顏色,屬, $丁單將是此 中的每種屬 例如,屬性 標、屬性存 稱係確認那 對照來自訂 名稱值對是 ^ -1的指標 」編輯。具 「或」以群: 自於訂單的 屬性值。屬七 行為。例如 色」、「藍色 表控制;定義排序標準,以在規劃程序執行前 序;將速率模型應用到關於位置的訂單;以及 於訂單。訂單達反係表示訂單達反軟式限制的 能規劃訂單的時候,因為其已達反硬式限制。 份及某些相關值可以國際化,局部的格式而顯 。在將各種項目分組成SAD群組中,可簡化規 提供最佳規劃的解決方案。 的;貝料可儲存於SAD群組表中。簡單SAD群組 單—屬性名稱及值組所定義的群組:屬性名稱 f生值=紅色。具有顏色屬性中的紅色值之所有 群組的—部份。表中的某種領域對於SAD群組 性名稱/屬性值對,會組成定義。這些包括, 型式、屬性名稱、屬性值、指標、屬性匹配旗 在旗標、以及類似的事物。屬性型式及屬性名 種訂單屬性,以比較對照。屬性值為用來比較 單的資料之值。指標可用來指定群組内的多種 如何相關的(例如,「及」或「或」連接關係) 係意謂名稱/值對係以群組的其餘來評估「或 有相同指標的名稱/值對係「及」一起編輯及 :的其餘來編輯。屬性匹配旗標係指定是否來 屬性值應該匹配或不匹配來自於名稱/值對的 存在旗標係指定是否屬性不存在於訂單上之 ’如果屬性值為顏色,可允許的值可能是「紅 」、或沒有值存纟。此旗標係表示是否目前沒 -26- 200305088Included in the plan, the order will reach the response time, or the user will not usually be shown to the planning process, taking the example of the SAD group as the color = color, genus, $ 丁 单 will be every The species, for example, the attribute index and the attribute name confirm that the index of the custom name-value pair is ^ -1 ". With "or" to group: attribute value from the order. Belong to seven behaviors. For example, "color", "blue table control; define the sorting criteria to execute the pre-order in the planning process; apply the rate model to the order about the location; and to the order. The order fulfillment means that the order reaches the anti-soft limit and can be planned At the time, because it has reached the anti-hard limit. The share and some related values can be displayed in an internationalized, partial format. Grouping various items into SAD groups can simplify the rules and provide the best planning solution. The shell material can be stored in the SAD group table. Simple SAD group list—the group defined by the attribute name and value group: attribute name f value = red. For all groups with red value in the color attribute— Part. A certain field in the table will form a definition for the SAD group name / attribute value pair. These include, type, attribute name, attribute value, indicator, attribute matching flag on flag, and similar things. Attribute Type and attribute name order attributes for comparison. The attribute value is used to compare the data of the order. The indicator can be used to specify how many of the groups in the group are related (for example, "and" Or "OR" connection relationship) means that name / value pairs are evaluated with the rest of the group "or name / value pairs with the same index are edited together with" and "and the rest are edited. The attribute matching flag specifies whether the attribute value should match or not match the existence from the name / value pair. The flag specifies whether the attribute does not exist on the order. If the attribute value is a color, the allowed value may be "red ", Or no value stored. This flag indicates whether there is currently no -26- 200305088

(22) 有值匹配。 一些屬性可用來定義SAD群組。這些屬性包括,例如, 項目識別符號、規劃位置、請求位置、啟始日期開始、啟 始日期結束、需求日期開始、需求日期結束、偏愛日期開 始、偏愛日期結束、最小數量、最大數量、最小優先權、 最大優先權、客戶名稱、客戶位置、SKU及可用於實施ABP 系統1 00之任何其他的使用者定義屬性。規劃位置屬性可 藉由其規劃的位置,而用來將訂單分組。請求位置屬性可 藉由每一訂單的請求位置,而用來將訂單分組。啟始日期 開始及啟始日期結束屬性係藉由某一範圍的起始日期,而 用來將訂單分組。啟始日期開始及啟始日期結束屬性可個 別使用,或與定義某一範圍的起始日期結合。起始日期可 識別出訂單可規劃於其中之最快(亦即,最早)的桶狀區間 。此為可選擇的領域,其可使用最新的以下日期[範圍啟 始,訂單啟始日期,訂單需求日期-最早]。啟始日期係用 來識別出訂單允許規劃於其中之最快的桶狀區間。要注意 的是容量或材料可行性可能使真正的啟始日期延後,但是 不會早於最早啟始曰期。需求日期開始及需求曰期結束屬 性係藉由某一範圍的需求日期,而用來將訂單分組。需求 日期開始及需求日期結束可個別使用,或與定義某一範圍 的需求日期結合。偏愛日期開始及偏愛日期結束屬性可藉 由某一範圍的偏愛日期,而用來將訂單共同分組。其可個 別使用,或與定義某一範圍的需求日期結合。最小及最大 數量屬性可基於每一訂單所請求的可接受·最小及/或最大 -27- (23) 200305088 數量’而用來將訂單共同分組。最小優先權及最大優先權 屬性可藉由優先權而用來將訂單分組。 A B P系統1 〇 〇支援以屬性為基礎之材料清單(在此為 BOM」)。然而,不像傳統規劃系統中的B〇M,相關於 系統100的BOM允許以選擇為基礎及以規則為基礎的材 料需求之模型化。例如,在汽車工業中,汽車楔型通常具 有一些特性及選擇。每種特性或選擇(如電動窗)會驅動將 需要提供如此的特性或選擇之的元件型式。斟 7聆具有電動 窗的汽車而言,將需要如電動窗組件及4 w馬诘,m ^ 1吳(用以驅動 電動窗)的材料(亦即,元件部分)。特性或選擇之特定組 合的存在也會影響到需用於組合的材料。例如,假設在上 例中,除了電動窗選擇之外,第二選擇(自動天窗)是需要 的。這會導致除了天窗組件之外,並且要將4%馬達需求 (當電動窗存在時,原來只需要的)改變1〇w馬達需求。 BOM基本上是用於SKU或成品的方法,並且顯示出用來滿 足SKU的屬性需求之成品的所有可能組態之所需要的元 件部分或材料。對於以上的自動工業例子中,用於SKU(例 如,汽車模型)的BOM可顯示出用來建造SKU之各種可接 受的組態之元件(例如’電動窗組件、4 w馬達、引擎、煞 車等)。因此’存在更多的元件,更多的組態是可能的, 並且會需要更多的元件部分或材料。此一特色的存在或不 存在因此驅使了材料的需求。當需要試圖使組態可行時, 可使用取代品。取代模型可產生有幫助的取代品。取代模 型係用來識別用於已知S K U的可取代s κ u、優先權、以 -28. 200305088(22) There is a value match. Some attributes can be used to define SAD groups. These attributes include, for example, item identifier, planning location, request location, start date start, start date end, demand date start, demand date end, preferred date start, preferred date end, minimum number, maximum number, minimum priority Rights, maximum priority, customer name, customer location, SKU, and any other user-defined attributes that can be used to implement the ABP system 100. The planned location attribute can be used to group orders by its planned location. The requested location attribute can be used to group orders by the requested location of each order. Start Date The start and end date attributes are used to group orders by a range of start dates. The start date start and end date end attributes can be used individually or combined with the start date that defines a range. The start date identifies the fastest (ie, earliest) barrel interval in which the order can be planned. This is an optional field, which can use the latest of the following dates [range start, order start date, order demand date-earliest]. The start date is used to identify the fastest barrel interval in which the order is allowed to be planned. Note that capacity or material feasibility may delay the actual start date, but not earlier than the earliest start date. The demand date start and demand date end attributes are used to group orders by a range of demand dates. The start of the demand date and the end of the demand date can be used individually or combined with a range of demand dates. The preferred date start and preferred date end attributes can be used to group orders together by a range of preferred dates. It can be used individually or in combination with a requirement date that defines a range. The minimum and maximum quantity attributes can be used to group orders together based on the acceptable, minimum, and / or maximum -27- (23) 200305088 quantity requested for each order. The minimum priority and maximum priority attributes can be used to group orders by priority. The A B P system 100 supports property-based bills of materials (here, BOM). However, unlike the BOM in traditional planning systems, the BOM related to the system 100 allows the modeling of selection-based and rule-based material requirements. For example, in the automotive industry, automotive wedges often have some characteristics and options. Each feature or option (such as a power window) drives the type of component that will need to provide such a feature or option. For a car with a power window, materials such as a power window assembly and a 4 w horse stable, m ^ 1 Wu (to drive the power window) will be required (ie, component parts). The presence of a particular combination of properties or choices also affects the materials to be used in the combination. For example, suppose that in the above example, in addition to the power window selection, a second selection (auto sunroof) is needed. This will result in a 4% motor requirement (when the power window is present, which was only required) in addition to the sunroof assembly, and a 10W motor requirement. The BOM is basically a method for SKUs or finished products, and shows the required component parts or materials for all possible configurations of the finished product to meet the attribute requirements of the SKU. For the auto industry example above, the BOM for a SKU (for example, a car model) can show components of various acceptable configurations for building a SKU (for example, 'power window assembly, 4 w motor, engine, brake, etc. ). So there are more components, more configurations are possible, and more component parts or materials will be needed. The presence or absence of this feature has driven the demand for materials. Use alternatives when you need to try to make the configuration feasible. Replacement models can produce helpful replacements. The substitution model is used to identify substitutable s κ u for known S K U, with a priority of -28. 200305088

及取代品拉取量。如果基本組態不可行,則會嘗試取代品 SKU。在此一個中所允許的鏈可允許以SKU2來取代SKU1 。如果SKU2不可行且具有取代品SKU3,則會嘗試SKU3 。循環取代會偵測出來且不允許的。取代品可由目前的 SAD群組來限制。 SAD群組可用來將其他的項目分組。例如,SAD群組可 用來產生專用資源群組。專用資源群組會產生及用於限制 可規劃特定資源之訂單。專用資源群組可使用SAD群組來 實施。參考專用資源群組的任何資源將只能製造屬於相關 於專用資源群組的SAD群組之訂單^ SAD群組可用來將其 他的項目分組,某些將在以下的段落中做說明。 在較佳具體實施例中,ABP系統1 〇〇為桶狀區間規劃系 統。此意謂ABP系統1〇〇試圖將訂單規劃成桶狀區間。桶 狀區間可由如時間、限制、資源、以及類似之物的許多參 數所定義。例如,繪示於圖1中之需將資源之一列入計畫 表中的訂單可指派由時間區間所定義的桶狀區間,並且特 疋於此位置的資源。例如,假設訂單已指派位於亞特蘭大 位置1 0 2的資源「A」11 然後,訂單可指派由如r 9月 U日至9月12日」、「資源A」、以及「亞特蘭大,gA」之時 間區間、資源及位置所定義的桶狀區間。 為了支持由本發明所提供的各種特性,會產生一些資料 庫表。表係由列及行所組成。列及行的值將取決於表本身 、土式表了產生包括BOM、桶狀區間、群組、SAD 群組、存貨清單表、項目(應該列入清單之所有成品及次 -29- (25) 200305088And the pull amount of the substitute. If the basic configuration is not feasible, an attempt is made to replace the SKU. The chain allowed in this one allows SKU2 to be substituted for SKU1. If SKU2 is not feasible and has a replacement SKU3, SKU3 will be tried. Cyclic substitution will be detected and not allowed. Substitutions can be restricted by the current SAD group. SAD groups can be used to group other items. For example, SAD groups can be used to generate dedicated resource groups. Dedicated resource groups are generated and used to limit the orders that can be planned for specific resources. Dedicated resource groups can be implemented using SAD groups. Any resource referring to a dedicated resource group will only be able to make orders belonging to the SAD group related to the dedicated resource group ^ The SAD group can be used to group other items, some of which will be explained in the following paragraphs. In a preferred embodiment, the ABP system 100 is a barrel-shaped interval planning system. This means that the ABP system 100 attempts to plan the order into a bucket interval. The bucket interval can be defined by many parameters such as time, limits, resources, and the like. For example, the order shown in FIG. 1 that requires one of the resources to be listed in the schedule may be assigned a barrel interval defined by a time interval, and is specific to the resource at this location. For example, suppose the order has been assigned the resource "A" 11 located in Atlanta position 102. Then, the order can be assigned time such as r September U to September 12 "," resource A ", and" Atlanta, gA " Bucket intervals defined by intervals, resources, and locations. To support the various features provided by the present invention, some database tables are generated. A table consists of columns and rows. The values of the columns and rows will depend on the table itself, and the native table produces BOM, bucket interval, group, SAD group, inventory list table, items (all finished products that should be included in the list and sub-29- (25 ) 200305088

資源群組、以及類似之物之一些 要材料)、位置、資源 實體。 全部程序 為了滿足需求,用來產生利用資源的規劃之全部程序可 區分成二個子程序。參照圖2八及2B,其為二個高準位的 流程200及220,用以產生規劃或修飾利用網路資源之存在 的規劃,以達成根據本發明一具體實施例之需求。為了說 明的目的,流程200將稱為初始流程,而流程22〇將稱為訂 單規劃流程。對於每個流程200及22〇,簡略介紹定義每個 流程200及220所定義的各種步驟之討論在底下會提供,緊 接著為在二個程序中所介紹的特定步驟及概念之更詳細 的討論。 簡I之’當靜態模型載入及/或產生時,程序2 〇 〇會開私 於步驟202。靜態模型可藉由定義或載入,例如, $關於 可用資源的資料、位置、日曆、規律、限制、商業規則 SKU SAD群組、材料清單(BOM)、專用資源群組及類似之 物,而模型化。此包括可標記為「保持於記憶體中 τ」的 SKU及藉由這些SKU所涉及的ΒΟΜ關係。在步驟2〇 *,會 初始化桶狀區間。為了初始化桶狀區間,每一桶狀區 以是相關的及/或由限制來定義。這些限制可包括,例令 ’容量限制。在步驟206,會安置初始分配及配置對鹿、 材料。在步驟2 0 8,會產生一個或多個未規劃的訂罝、 早'^暫 時表。某些這些步驟之更詳細的說明會在底下提供。 y、 在完 成初始化程序200之後,用來.處理訂單的第二程序222會門 -30- 200305088Resource groups, and some similar materials), locations, resource entities. All procedures In order to meet the needs, all procedures used to generate a plan for the utilization of resources can be divided into two sub-procedures. Referring to FIGS. 2A and 2B, there are two high-level processes 200 and 220 for generating a plan for planning or modifying the use of the existence of network resources to achieve the requirements according to a specific embodiment of the present invention. For illustrative purposes, process 200 will be referred to as the initial process and process 22o will be referred to as the order planning process. For each process 200 and 22, a brief introduction to the various steps that define each process 200 and 220 is provided below, followed by a more detailed discussion of specific steps and concepts introduced in the two procedures . Jane I 'When the static model is loaded and / or generated, the procedure 2000 will be opened in step 202. Static models can be defined or loaded by, for example, data about available resources, locations, calendars, rules, restrictions, business rules, SKU SAD groups, bills of materials (BOM), dedicated resource groups, and the like Modeling. This includes SKUs that can be labeled "keep in memory" and the BOM relationships involved by these SKUs. At step 20 *, the bucket interval is initialized. To initialize bucket intervals, each bucket is related and / or defined by a restriction. These restrictions can include, for example, 'capacity restrictions'. In step 206, the initial allocation and configuration of the deer and material will be placed. In step 208, one or more unplanned booking, early '^ temporary tables are generated. A more detailed description of some of these steps is provided below. y. After completing the initialization program 200, the second program used to process the order is 222. -30- 200305088

(26) 始進行。(26) Begin.

為了達成如例如由尚未規劃的訂單(亦即,未規劃訂單) 所定義的需求,第二全部程序2 2 0會用來規劃網路資源的 利用。間T之’當在步驟222 ’選擇—個或多個訂單的一 部分時,程序220會開始。一部分訂單為一群訂單,其每 個會與基於SAD群組的屬性值之特定8八13群組相關。在步 驟224,會載入下個視窗,其具有一個或多個訂單的選擇 部分及其相關項目。會相關於一個或多個訂單之項目包括 ,例如,組態、BOM、次要項目SKU、成品SKU(FG SKU) 及類似之物。在步驟226,會將視窗中的每個訂單按優先 順序處理。具有較高優先權的那些通常將會在具有低優先 權的那些之前,列入計畫表中。在步驟228,會選擇尚未 規劃之最高優先權的訂單,並且規劃此, U 早β如果在視窗 中,有任何更多的未規劃訂單,則下個笋古振* ^ Γ调取网優先權訂單 將會列入計畫表中,如步驟230所表示,否則在步驟Μ] 中,會寫入分配,以致於會保存需用來達成訂單之商In order to achieve a demand as defined by, for example, an unplanned order (ie, an unplanned order), the second full procedure 220 is used to plan the utilization of network resources. Between T ' When a portion of one or more orders is selected at step 222 ', the procedure 220 may begin. A part of the order is a group of orders, each of which will be related to a specific 8-8 13 group based on the attribute value of the SAD group. At step 224, the next window is loaded with one or more selected parts of the order and its related items. Items that will be relevant to one or more orders include, for example, configuration, BOM, minor item SKU, finished SKU (FG SKU), and the like. At step 226, each order in the window is processed in order of priority. Those with higher priority will usually be listed on the plan before those with lower priority. In step 228, the highest priority order that has not been planned is selected, and this is planned. If there are any more unscheduled orders in the window, the next one will be listed. * ^ Γ Call the network priority The order will be listed in the plan table, as indicated in step 230, otherwise in step M], the allocation will be written, so that the merchant needed to complete the order will be saved

源及/或材料。一旦已寫入分配,在步驟234,暫^ 動態資料會卸載。在步驟236,會判斷是否其他‘八中的 單需做處理’並且假如如此,會回到步驟222,::的玎 程序2 2 0。 再,入開始 以上關於程序200及220所介紹的特定步驟及概令、 詳細的說明會緊接於後。當在步驟2〇2 :〈更 的靜辑,八去、 見劃模型 勺靜J邵刀時,初始程序2〇〇通常會開始。例如,η — 出在資源、專用資源群組及其位置( ::定義 表4或倉庫位 -31 · (27) 200305088 置 的 通 需 之 的 序 出 例 傾 因 態 或 期 規 於 劃 後 訂 成 給 計 、、勺關係。有關於如可用於特定資源之容量及物品 ^式&lt; 4争定資訊也可以定義出來。在初始模型化期間, 常為靜態的限制可定義出來。會產生傳輸矩陣,以定義 用、;i括需用於傳送至特定客戶之供應鏈的各種路程Source and / or material. Once the allocation has been written, the temporary data will be unloaded at step 234. In step 236, it is judged whether other ‘eighth orders need to be processed’ and if so, it returns to step 222, :: program 2 2 0. Then, enter the specific steps, outlines, and detailed descriptions of the procedures 200 and 220 described above. When in step 002: <More static compilation, eight-going, see-through model, spoon static J Shao Dao, the initial procedure 200 usually starts. For example, η — out of resources, dedicated resource groups and their locations (:: Definition of table 4 or warehouse location -31 · (27) 200305088 The general order of the general needs or the schedule is set after delineation It is related to the calculation of the supply, the spoon. The information about the capacity and items available for a specific resource, etc. 4 can also be defined. During the initial modeling, often static restrictions can be defined. Transmission will occur Matrix to define the use of; i includes the various routes that need to be used to transfer to the specific customer's supply chain

專,^間。如日曆、桶狀區間、商業規則、SKU、BOM 頁目可疋義出來。熟習此項技術者將會了解到在規劃程 勺模土化階段期間,一些其他一般的靜態實體也可定義 來。 般而a ,某些資料直到最後片刻才輸入將是較佳的。 女剛好在規劃訂單之前,將會較佳地輸入有經常改變 向的巧度動態資料,或直到最後片刻,才可用之資料。 此’在已定義靜態部分之後,某個時候會輸入模型的動 部刀剛好在規劃程序開始時,一般將會輸入如新訂單 修飾訂單的資料。剛好在訂單規劃開始時,甚至必須週 性地更新一般的靜態資料(如有關於限制、資源及商業 則的資料)’以及會輸入有關於那些的資料。剛好在關 特疋規劃範圍或關於如從前客戶的特定條件之訂單規 之刖’新限制也會增加。新或修改的商業規則也會在最 片刻増加,以反映商業需求的經常改變。最後,在實施 單規劃之前,一般將會在最後片刻輸入最新訂單。 較佳而言,程序2〇〇及220會產生利用資源的規劃,以達 需求(例如,獨立及相依訂單)^特定的桶狀區間會保留 特疋〃丁單。桶狀區間為相關於,例如,資源及表示列入 畫表機會之時間區間。在步驟204,桶狀區間會藉由安 -32· 200305088Special, ^ between. Such as calendar, bucket interval, business rules, SKU, BOM pages can be defined. Those skilled in the art will understand that during the soilization phase of the planning process, some other general static entities can also be defined. Generally, it would be better to enter some data until the last moment. Females will enter dynamic data that often changes direction, or will not be available until the last moment, just before planning an order. This ’, after the static part has been defined, the moving knife of the model will be entered at some point. Just at the beginning of the planning process, it will generally be entered as new order modification order data. Just at the beginning of order planning, it is even necessary to update the general static data (such as information on restrictions, resources, and business rules) on a weekly basis and input information about those. New restrictions that are just in the scope of planning or order specifications regarding specific conditions such as previous customers will also increase. New or revised business rules are also added at the very least to reflect frequent changes in business needs. Finally, the latest order will usually be entered at the last moment before the single plan is implemented. Preferably, the procedures 2000 and 220 will generate a resource utilization plan to meet the demand (for example, independent and dependent orders). ^ Special bucket intervals will retain special orders. Bucket intervals are time intervals that are related, for example, to resources and presentation opportunities. In step 204, the bucket interval is

(28)(28)

置限制於其上而初始化。這些限制可包括量的限制及品質 的限制。在初始化步驟2 0 4期間,會產生所有限制的狀態 (桶狀區間),以及會設定在這些狀態的容量。在桶狀區間 中,限制會增加及實施。這些限制桶裝區間會與資源桶狀 區間並行。因此,例如,特定限制(如資源容量限制)會定 義用於特定桶裝區間。例如,當在不同的時間週期,其會 限制為另一準位時,在一次週期期間,用於特定資源的總 容量會限制為某一準位。限制會使用三種資料庫表(限制 表、限制規則表、以及桶狀區間表)來模型化。Set the limit to initialize it. These limits may include limits on quantity and limits on quality. During the initialization step 204, all restricted states (barrels) will be generated and the capacity will be set in these states. In barrel-like zones, restrictions are increased and enforced. These restricted bucket intervals are parallel to the resource bucket intervals. So, for example, specific limits (such as resource capacity limits) are defined for specific barrel ranges. For example, when it is limited to another level at different time periods, the total capacity for a particular resource is limited to a certain level during one period. Restrictions are modeled using three database tables (restriction tables, restriction rule tables, and bucket interval tables).

在AB P系統1 0 0做出用以達成任何尚未規劃的訂單之規 劃之前,會在步驟2 0 6的初始步驟期間,對具有預定分配 的訂單做規劃。初始分配係用來「凍結」訂單。亦即,在 執行規劃程序之前,其可用來保存位置/資源/桶狀區間, 以達成特定訂單。其可藉由通常在規劃任何其他訂單之前 會安置到桶狀區間中的初始分配來完成,以確定其總是在 規劃上的相同位置。在規劃訂單前,具有預定分配的訂單 將會較佳地列入計畫表中。這可藉由訴諸初始分配配置常 式來完成。 在某些情況中,會產生預先分配表,以定義預定分配。 這樣的表會包含分配的資訊,如:要分配的訂單身份、分 配訂單中的資源、用於訂單之列入計畫表的桶狀區間、以 及相關於分配(或許不屬於此)的訂單數量。關於初始分配 的Β Ο Μ組態資訊會儲存於Β Ο Μ表中。在達成希望後,初 始分配會立即在預先分配表中做處理。參照圖3 A,其為 -33- 200305088Before the AB P system 1 0 0 makes a plan to reach any unplanned orders, during the initial step of step 2 06, the orders with a predetermined allocation are planned. Initial allocation is used to "freeze" orders. That is, it can be used to save locations / resources / barrels to fulfill specific orders before the planning process is performed. It can be done with an initial allocation that will usually be placed in a barrel section before any other order is planned to determine that it will always be in the same position on the plan. Prior to order planning, orders with pre-assigned allocations will preferably be included in the planning table. This can be done by resorting to an initial allocation configuration routine. In some cases, a pre-allocation table is generated to define a predetermined allocation. Such a table would contain allocation information such as: the identity of the order to be allocated, the resources in the allocated order, the bucket interval used for the order to be included in the planning table, and the number of orders related to the allocation (which may not belong to this) . The BOM configuration information about the initial allocation will be stored in the BOM table. Once the hope is reached, the initial allocation is processed in the pre-allocation table. Referring to Figure 3 A, it is -33- 200305088

(29) 用於初始分配的配置之流程3 〇〇。在步驟3 02,會將初始分 配中的訂單數量BOM放置在使用設計 BOM組態之設^十 桶狀區間中的設計資源。在步驟3 04,會更新未評估訂單 的材料町行性之材料可用性。在本文中的材料可以是用來 補充資源之任何元件材料或成品。在步驟3 0 6,會判斷可 用於桶狀區間/資源的限制。限制通常是桶狀區間/咨、 Λ Μ / 位置相依的。二種因素可用來判斷限制是否可用。笙 Φ 一· &gt; 只會考慮應用於初始分配上的設計資源〜…… 、 π 話說 ,用以配置限制的資源名稱必須真正地與設計資源的 &lt; 匹配,或用以配置限制的資源群組必須包括初始分配上、 設計資源。第二,限制達反不應該防止初始分配放 、 、 A直在設 計資源上的設計桶狀區間中。在步驟3 0 8,會更舫m 曰人研用於所 有可用限制之設計中的容量。在步驟3丨〇,會記綠有關、 訂單的分配之資訊。 ’於 在程序200的步驟208中,會產生用於一個或多 、 Μ禾規劃 订單之一個或多個暫時資料庫表。這些未規劃訂 早為即將 精由程序200及220所規劃之目標訂單。此表可細 gp ^ 、&amp;田仞始分 而識別出未完全完成的所有訂單。此表可經由 蚩,丨 升餘的規 &quot;呈序20〇 ,而將載入的訂單限制為只有在此表+ ^ 出4^ , 丫所識別 果的那些訂單。在藉由訂單的部分或群組來處理訂單 ,ABP系統100的記憶體需求會降低。 早中 在圖2B的步騾226中,訂單會按優先順序處埋及排 奴而言,當多個可單存在時,訂單會一個接一 王里。 i 個做虑 。優先處理的訂單通常會優先得到材料及容 T的存取。 -34- 200305088(29) Process 3 for configuration of initial allocation. In step 3 02, the order quantity BOM in the initial allocation is placed in the design resource in the design ^ ten barrel-shaped interval configured using the design BOM. At step 04, the material availability of the unapproved material is updated. The material in this article can be any component material or finished product used to supplement resources. In step 306, a determination is made of the limits available for the bucket interval / resource. Restrictions are usually barrel-like intervals / references, ΛM / position-dependent. Two factors can be used to determine whether restrictions are available. Sheng Φ 1 &gt; Only design resources that are applied to the initial allocation will be considered ~ ..., π In other words, the resource name used to configure the restriction must really match the &lt; or the resource group used to configure the restriction The group must include initial assignments and design resources. Second, limiting the response should not prevent the initial allocation of,, and A directly in the design barrel-shaped interval on the design resources. In step 308, the capacity of the design used by the researcher in all available limits will be even greater. In step 3, the information about the allocation of the order is recorded. In step 208 of the process 200, one or more temporary database tables are generated for one or more M & M planning orders. These unplanned orders are already targeted orders that will be precisely planned by procedures 200 and 220. This table can be divided into gp ^ and & Tian Yuan to identify all orders that have not been completed. This table can be passed through the 升, 丨 surplus rules &quot; ordering 20〇, and the loaded orders are limited to only those orders identified in this table + ^ out 4 ^, ya. When processing orders by part or group of orders, the memory requirements of the ABP system 100 will decrease. Early middle In step 226 of Figure 2B, the order will be buried and eliminated in order of priority. When multiple orders are available, the order will be one after another. i worry. Priority orders usually have priority access to materials and capacity. -34- 200305088

(30) 因為某種汀單載其他之前做處理是較佳的,所以較佳而言 ’系統會使用將訂單按優先順序的機制。用來將訂單按優 先順序的機制稱為排序。(30) Because it is better for some orders to be processed before the others, it is better that the system will use the mechanism of ordering in priority. The mechanism used to prioritize orders is called sorting.

叮單排序機制允許將訂單群組模型化,以及將高優先權 訂單會得到優先處理之這種方式的標準排序。如果二種訂 單具有相同優先權,其會藉由資料庫依序做處理。參照圖 3 B ’其為用於將訂單按優先順序之流程3 2 〇。在步驟3 2 2 ’會將訂單組織成訂單群組。在步驟324,會藉由SAD群 組來定義每個群組。在步驟3 26,會藉由例如序號而將每 個SAD群組排序。序號係用來將這些訂單SAD群組的相對 優先權模型化。較低序號係相關於較高優先權。在每個訂 單群組内,可單會基於一種或多種屬性而排序(上升或下 降)。在步驟328,會藉由使用者定義標準而將每個群組内 的訂單排序。對於每種訂單,標準會不同。例如,在某一 群組的訂單可由需求日期來排序,而另一個群組的訂單可 藉由預定的優先權號碼來排序The ordering mechanism allows modelling of groups of orders and standard ordering in such a way that high priority orders are prioritized. If the two orders have the same priority, they will be processed sequentially by the database. Referring to Fig. 3B ', it is a flow 3 2 0 for prioritizing orders. At step 3 2 2 ’the orders are organized into order groups. At step 324, each group is defined by a SAD group. At step 3 26, each SAD group is sorted by, for example, a serial number. The serial number is used to model the relative priority of these order SAD groups. Lower numbers are associated with higher priorities. Within each order group, orders can be sorted (up or down) based on one or more attributes. At step 328, orders within each group are sorted by user-defined criteria. The criteria will be different for each order. For example, orders in one group can be sorted by demand date, while orders in another group can be sorted by a predetermined priority number

為了說明已敘述過的某些概念,會提供以下的例子。 設汽車製造商生產模型X汽車,並且接受車隊、零售及 貨銷售的訂單。製造商有三種區別的訂單群組:車隊訂 、零售訂單及存貨訂單。因此,這=種 k 一種群組的相對優先To illustrate some of the concepts already described, the following examples are provided. Suppose the automaker produces Model X cars and accepts orders for fleet, retail, and cargo sales. Manufacturers have three distinct order groups: fleet orders, retail orders, and inventory orders. Therefore, this = the relative preference of the k-group

可以模型化。進一步假設車隊訂單是I 早疋取重要的,緊接著 零售訂單’而最後為存貨訂單。對於每—群組而言,用 將群組内的各種訂單排序之優先權標準也可以定義出 。例如,零售群組中的訂單可藉由需 w *不曰期來排序(上^ -35- 200305088Can be modeled. It is further assumed that the fleet order is important to take early, followed by the retail order ’and finally the inventory order. For each group, the priority criteria for sorting various orders in the group can also be defined. For example, orders in a retail group can be sorted by requiring w * not date (top ^ -35- 200305088

,而車隊群組中的訂單可藉由收入(使用者定義屬性)來排 序(下降)。 訂單群組的取得及群組内的排序可使用延伸介面來達 成。ABP系統100可支援以下運作的此介面之基本實施。 SAD群組可用來定義訂單群組。序號可用來將這些訂單群 組的相對優先群模型化。較低序號係相關於較高優先權。 在每個訂單群組内,訂單會藉由單一屬性來排序(上升或 下降)。例如, 序號 訂單群組描述符號(SAD群組) 排序屬性 排序訂單 1 訂單型式=車隊 收入 下降 2 訂單型式=零售 業者 下降 3 訂單型式=存貨 需求曰期e 上升 上表顯示車隊訂單比零售訂單更重要,其依序比存貨訂 單更重要。在車隊訂單的群組内,較高收入的訂單比較低 入的訂單更重要。在每一群組内,訂單可在不同基礎上排 序。例如,對於零售訂單的群組而言,具有較高種類數目 之來自於業者的訂單會比具有較低種類數目之來自於業 者的訂單更重要。因此,製造商可定義三種準位的業者: 種類數目「3」為最高準位,「2」為中間準位及「1」為最 低準位。因此,屬於最高準位的那些業者之訂單會優先處 理。在另一例中,假設製造商所關心的是準時運送。在這 樣的事態中,在SAD群組内的訂單可藉由需求日期來排序 。在那情況中,需求日期屬性可定義於訂單中,以及用來 設定SAD群組内之每一訂單的相對優先權。 -36- (32) (32)200305088 除了排序機制外,ABP系統100會使用二種其他機制來 幫助確足最重要訂單的旁$ #人 取里晋叮早扪疋成疋令人滿意的。此二種機制為 容量配置及材料配置。容量配置機制在不希望訂單優先處 理(儘管訂單排序)的事件中,會幫助調和系統的強烈行為 。根據此機制,會產生系統限制模型,其可用來配置基於 有意義屬性的容量。例如,特定資源的容量可設計用於某 種客戶。用以確認最高優先權訂單為優先做令人滿意的處 理之第三種機制稱為材料配置。此系統允許標記存貨清單 及將使用屬性的收入列入計畫表中,以將材料強制配置到 希望的耵單。例如,假設用於項目的i 〇〇個單元的存貨已 分配屬性「客戶=Jay-Mart」。基本上,此屬性會給予ι〇〇 個單兀旗標,並且基本上會與用於Jay Mart的1〇〇個單元 相反。這確定了這100個單元只能由Jay_Mart的獨立/相依 需求得到。 在本發明的一較佳具體實施例中,AB p系統J 〇 〇係使用 可單視窗,其可顯示未列入計畫表的訂單清單。未列入計 畫表的ΤΓ單清單確定了相同訂單不會列入計畫表兩次,因 為其會與SAD群組的多種標準匹配。例如,假設具有優先 權1 (例如’咼優先權)的S A D群組全都是紅色汽車,而具 有優先權2的SAD群組全都是具有ABS煞車的汽車。具有 AB S煞車的紅色汽車將會規劃在第一群組中。雖然在第二 群組中也會遇到,但是因為其未在未列入計畫表的訂單中 ,所以其將會略適。 為了有效管理記憶體,以及藉由盡可能的使資料庫呼叫 -37- (33) (33)200305088 變少’以改善性能,當將實體載入記憶體及卸載出記憶體 時’根據本發明一較佳具體實施例之ABP系統1 〇〇會依循 某種規則。訂單視窗會提供一種方式,來察看及處理訂單 °可單視窗的大小係取決於硬體組態及模型的大小,並且 係由使用者來設定。只有未列入計畫表的訂單將會做處理 ’這些會保持在未列入計畫表的訂單表中之暫時清單上。 當將資訊載入記憶體中時,以下的規則會使用··在訂單视 窗中的訂單,用以請求特定SKU的訂單,SKU會載入記憶 體中;對於由唯一項目(不是SKU)所定義的訂單,此項目 及相關於此項目的所有SKU會載入;用於SAD群組的BOM 關係’其應用於載入的SKU及項目;用於SAD群組的取代 sku資訊,其應用於載入的SKU及項目;受到硬式限制(從材 料觀點)的唯一 SKU將會載入;以及用於與載入的及 項目相關的存貨之材料可用資訊。 對於卸載而1,訂單視窗開始時會載入記憶體的SKU、 項目、以及BOM在處理訂單視窗之後,將會從記憶體中 卸載,除了以下的例外··一旦其已載入,每個SKU將具有 一個旗標,以決定其將是否從記憶體中卸載,具有此旗標 組的SKU將不會卸載;參數可設定在演算法上,以提供視 窗記憶體。此參數將會給予一些訂單视窗,其將會記住 SKU的使用,亦即,如果在最後的^固视窗中,已修 飾或考慮’其將不會卸載;B0M組態將不會卸載,除非 目則的SKU卸載;以及從記憶體中卸載的SKU將具有會在 持續儲存中更新的可利用狀態。 200305088 (34) 為了說明這些概念,以下的例子會提供。假設訂單的排 序清單(訂單排序程序的輸出)如下: 群組 訂單身份 車隊 01 車隊 03 零售 02 零售 06 存貨 05 存貨 04 在上表中,有六個訂單,01為最高優先權訂單,而04 為最低優先權訂單。假設使用者已配置三個訂單的視窗大 小。當第一項目請求訂單視窗裝填器程序時,常式會將具 有身份0 1、03、以及02的訂單載入到記憶體。當再次請求 訂單視窗裝填器時,常式會將具有以下身份·· 06、05、以 及04的訂單載入到記憶體。只有在已處理完目前訂單視窗 中的所有訂單之後,通常才會請求訂單視窗裝填器。 處理訂單的方式會取決於訂單是否凍結。如果訂單屬於 凍結群組表中的SAD群組,會凍結此訂單。此表包含SAD 群組名稱的集合。藉由SAD群組之一描述的訂單會較佳地 以其需求曰期,而列入計畫表中。知道凍結訂單與初始分 配不同是重要的。初始分配為基本訂單,其在先前執行規 劃程序200之後,會「凍結」。在對ABP輸出做必要的調整 之後,系統使用者會凍結在後來的ABP執行期間,使用者 不想移動的訂單。初始分配會有分配日期、位置及資源。 -39- (35) (35)200305088 然而,「凍結訂單」通常是用來強制指配為特定日期及/ 或位置之「某種」訂單。例如,汽車製造商會有表示「車 隊訂單必須取得其需求日期」之商業規則。為了使此商業 規則模型化,較佳而言,會產生凍結SAD群組「訂單刑式 -車隊」。/東結叮單會以其需求桶狀區間而列入計佥表中 。需求桶狀區間為包含需求日期(在此例中,滚辞SAD群 組的需求日期)的桶狀區間。如果未指定位置,則會使用 弟一個可行位置。 參照圖3C,其繪示的是在SAD群組3 52、訂單3 54到358 及凍結群組表3 6 0之間的關係之方塊圖3 5 0。訂單3 5 4到3 5 8 中的每一個具有訂單型式,「車隊」的屬性。基於此屬性 ,訂單3 54到3 5 8係相關於SAD群組3 52。凍結群組表360 係相關於三個SAD群組3 52、3 62及3 64。因為SAD群組352 與凍結群組表3 6 0有關,所以相關於S A D群組3 5 2的每個訂 單將會凍結,因此訂單3 5 4到3 5 8將會指配為指定時間(例 如,5星期)。 訂單規劃 在圖2B的步騾2 2 8,會規劃用以達成一個或多個訂單之 資源的使用。AB P系統1 〇 〇會實施按優先順序處理的強烈 演算法。此演算法一次會處理一個訂單,評估用於訂單的 潛在分配(桶狀區間、資源及位置)。此演算法會藉由使用 者定義多級目標函數評估分配及確定相關於材料及容量 限制的分配是可行的,而選擇用於訂單的最適合分配。 圖4為資源規劃的流程4 0 0,以達成如由訂單所定義的需 -40 - 200305088, And orders in the fleet group can be sorted (decreased) by revenue (user-defined attributes). The acquisition of order groups and ordering within groups can be achieved using the extended interface. The ABP system 100 can support the basic implementation of this interface operating below. SAD groups can be used to define order groups. The serial number can be used to model the relative priority groups of these order groups. Lower numbers are associated with higher priorities. Within each order group, orders are sorted (rising or falling) by a single attribute. For example, the sequence order group description symbol (SAD group) Sorting attributes Sort orders 1 Order type = Fleet revenue decline 2 Order type = Retailer decline 3 Order type = Inventory demand date e Rise The above table shows that fleet orders are more than retail orders Important, it is more important in order than inventory orders. Within the fleet order group, higher revenue orders are more important than lower revenue orders. Within each group, orders can be sorted on a different basis. For example, for a group of retail orders, an order from a vendor with a higher number of categories is more important than an order from a vendor with a lower number of categories. Therefore, manufacturers can define three levels of operators: the number of categories "3" is the highest level, "2" is the intermediate level, and "1" is the lowest level. Therefore, the orders of those operators that belong to the highest level will be given priority. In another example, suppose the manufacturer is concerned about shipping on time. In such a situation, orders within the SAD group can be sorted by demand date. In that case, the demand date attribute can be defined in the order and used to set the relative priority of each order in the SAD group. -36- (32) (32) 200305088 In addition to the sorting mechanism, the ABP system 100 will use two other mechanisms to help ensure that the most important orders are located next to each other. # 里里丁丁 早 扪 疋 成 疋 is satisfactory. These two mechanisms are capacity allocation and material allocation. The capacity allocation mechanism helps to reconcile the strong behavior of the system in the event that you do not want the order to be processed first (although the order is ordered). Based on this mechanism, a system limit model is generated that can be used to configure capacity based on meaningful attributes. For example, the capacity of a particular resource can be designed for a certain customer. The third mechanism used to confirm the highest priority order as a priority for satisfactory processing is called material allocation. This system allows tagging inventory lists and including income from usage attributes in planning tables to force allocation of materials to desired bills. For example, suppose that the inventory of 100 units used for the project has been assigned the attribute "customer = Jay-Mart". Basically, this property will give ιι single flags, and will basically be the opposite of the 100 units used for Jay Mart. This confirms that these 100 units can only be obtained by independent / dependent requirements of Jay_Mart. In a preferred embodiment of the present invention, the AB p system J 〇 〇 uses a single window, which can display a list of orders not included in the plan table. The list of TI orders that are not included in the schedule determines that the same order will not be included in the schedule twice because it will match multiple criteria of the SAD group. For example, suppose that the SA D group with priority 1 (e.g., '咼 priority) are all red cars, and the SAD group with priority 2 are all cars with ABS brakes. Red cars with AB S brakes will be planned in the first group. Although it will also be encountered in the second group, it will be slightly suitable because it is not in the order that is not listed in the schedule. In order to effectively manage memory and reduce database calls as much as possible -37- (33) (33) 200305088 'to improve performance, when entities are loaded into and unloaded from memory' according to the present invention The ABP system 100 of a preferred embodiment will follow certain rules. The order window will provide a way to view and process the order. The size of the single window depends on the hardware configuration and the size of the model, and is set by the user. Only orders that are not on the schedule will be processed ’These will remain on the temporary list in the schedules that are not on the schedule. When information is loaded into memory, the following rules will be used ... Orders in the order window to request an order for a specific SKU, the SKU will be loaded into memory; as defined by a unique item (not a SKU) Order, this item and all SKUs related to this item will be loaded; the BOM relationship for the SAD group 'it applies to the loaded SKU and item; the replacement sku information for the SAD group, it applies to the load Incoming SKUs and projects; only SKUs subject to hard restrictions (from a material perspective) will be loaded; and information on the availability of materials for the loaded and project-related inventory. For unloading 1, the SKU, item, and BOM of memory will be loaded at the beginning of the order window. After processing the order window, it will be unloaded from the memory, with the following exceptions ... Once it has been loaded, each SKU There will be a flag to determine whether it will be unloaded from memory. SKUs with this flag group will not be unloaded; parameters can be set on the algorithm to provide window memory. This parameter will be given to some order windows, which will remember the use of SKUs, that is, if in the last window, it has been modified or considered 'it will not be uninstalled; B0M configuration will not be uninstalled unless The unloading of the SKUs as intended; and the SKUs unloaded from memory will have an available status that will be updated in continuous storage. 200305088 (34) To illustrate these concepts, the following examples are provided. Assume that the ordering list of the orders (the output of the order sorting program) is as follows: Group Order Identity Fleet 01 Fleet 03 Retail 02 Retail 06 Stock 05 Stock 04 In the table above, there are six orders, 01 is the highest priority order, and 04 is Lowest priority order. Assume that the user has configured window sizes for three orders. When the first item requests the order window loader program, the routine loads the orders with the identity 0 1, 03, and 02 into memory. When the order window loader is requested again, the routine will load orders with the following statuses: 06, 05, and 04 into memory. The order window loader is usually requested only after all orders in the current order window have been processed. The way an order is processed will depend on whether the order is frozen. If the order belongs to the SAD group in the frozen group table, the order is frozen. This table contains a collection of SAD group names. Orders described by one of the SAD groups are preferably included in the schedule based on their demand dates. It is important to know that the frozen order is different from the initial allocation. The initial allocation is a basic order, which will be "frozen" after the previous execution of the planning process 200. After making the necessary adjustments to the ABP output, the system user freezes orders that the user does not want to move during subsequent ABP executions. The initial allocation will have an allocation date, location, and resources. -39- (35) (35) 200305088 However, a "frozen order" is usually used to force a "some" order of a specific date and / or location. For example, a car manufacturer may have business rules that say "Fleet orders must get their demand dates." In order to model this business rule, it is better to generate a frozen SAD group "Order Penalty-Fleet". / Dong Jie Ding Dan will be listed in the schedule based on its demand barrel range. The demand bucket interval is a bucket interval that contains the demand date (in this example, the demand date for rolling SAD groups). If no location is specified, a feasible location is used. Referring to FIG. 3C, it is a block diagram 3 50 showing the relationship among SAD group 3 52, orders 3 54 to 358, and freeze group table 3 6 0. Each of the orders 3 5 4 to 3 5 8 has the property of an order type, "fleet". Based on this attribute, orders 3 54 to 3 5 8 are related to SAD group 3 52. The frozen group table 360 is related to the three SAD groups 3 52, 3 62, and 3 64. Because SAD group 352 is related to the frozen group table 3 60, each order related to SAD group 3 5 2 will be frozen, so orders 3 5 4 to 3 5 8 will be assigned to a specified time (for example , 5 weeks). Order Planning In steps 2 2 8 of Figure 2B, the use of resources to fulfill one or more orders is planned. AB P system 100 implements strong algorithms that are processed in order of priority. This algorithm processes one order at a time and evaluates the potential allocation (barrels, resources, and locations) for the order. This algorithm uses the user-defined multi-level objective function to evaluate allocations and determine that allocations related to material and capacity constraints are feasible, and chooses the most appropriate allocation for the order. Figure 4 shows the process of resource planning 4 0 0 to achieve the needs as defined by the order -40-200305088

(36) 求,並且通常顯示出圖2B的步驟22 8。特別而言,此為以 屬性為基礎的規劃程序。流程4 〇 0會處理按優先順序處理 的訂單,並且會藉由資源的最佳利用而產生用來達成訂單 的規劃。繪示於圖4中之每個步驟的簡短說明在底下會提 供,緊接著為步驟的更詳細說明。在步騾402中,會選擇 一個訂單來做處理。程序步騾4 0 2也可包括定義規劃訂單 的參數之步騾。在步驟404,會選擇組態及將可接受的位 置按優先順序處理。每個訂單會具有有項目及具有一個偏 愛位置。如果其兩者都有’則成品SKU已識別出來。如果 只具有項目,則系統將較隹地產生可用來識別相關於選擇 訂單的成品之SKU(具有可行位置的項目)的按優先順序 處理訂單,並且會從訂單中產生成品SKU(在此「FG SKU 」)的集合。步驟404會導致用於集合中的每個FG SKU之 可接受位置的決定,因為SKU通常會定義位置。一種或多 種組態會相關於每個SKU。因此在步驟404(先前載入的可 允許組態-見流程2 2 0、圖2 Β、步驟2 2 4)。在步驟4 0 6中, 來自FG SKU的集合中之SKU會選擇用來規劃。所選擇的 FG SKU通常將是具有尚未規劃之集合中的最高優先權之 SKU。在步驟4〇8,會初始化fg SKU,以致於FG SKU將 具有相對應於訂單及/或項目的所有屬性。基於所選擇的 SKU ’會決定那一資源為用於規劃SKu之可接受的資源, 並且根據步驟4 1 0的優先權來排序資源。要注意的是,當 伴隨相關曰期的部分訂單載入圖2Β之步驟224的視窗時 ’可能已載入及/或決定可接受資源的清單。在步驟4 1 1 • 41 - (37) (37)200305088 msmaam ,會選擇清單上之氣古山 -、有取南優先權的資源。在步 會做出材料可行性判斷,、2 ^ 杜’驟412 ’ A. ^ . 斷以決疋位置/資源是否具有足夠 的材料來滿足如訂單 有足夠 ^ ^ .. 義々而求,如果否,材料是否备 補无。在步驟4 1 4中,合嵙、欠、κ 疋么曰 +辨4 1 6 ^ 曰對貝源做出限制可行性評估。在 步驟416,會做出材料 在 ^ 令里相容性檢查。在步驟418,合鲆(36), and step 22 8 of FIG. 2B is usually displayed. In particular, this is an attribute-based planner. Process 4 will process orders processed in priority order, and will use the best use of resources to generate a plan to achieve the order. A brief description of each step shown in Figure 4 is provided below, followed by a more detailed description of the steps. In step 402, an order is selected for processing. Program steps 4 0 2 may also include steps for defining parameters of a planned order. In step 404, the configuration is selected and the acceptable locations are prioritized. Each order will have an item and a preferred position. If both of them are ’then the finished SKU has been identified. If there is only an item, the system will relatively easily generate a prioritized processing order that can be used to identify the SKU (item with feasible location) related to the finished product of the selected order, and a finished product SKU (herein "FG SKU "). Step 404 results in a decision on the acceptable location for each FG SKU in the set, as SKUs typically define locations. One or more configurations are associated with each SKU. Therefore at step 404 (permissible configuration previously loaded-see flow 2 2 0, Figure 2 B, step 2 2 4). In step 406, the SKUs from the collection of FG SKUs are selected for planning. The FG SKU selected will usually be the SKU with the highest priority in the unplanned collection. At step 408, the fg SKU is initialized so that the FG SKU will have all attributes corresponding to the order and / or item. Based on the selected SKU ', it is determined which resource is an acceptable resource for planning SKu, and the resources are ranked according to the priority of step 4 10. It should be noted that when part of the order accompanying the relevant date is loaded into the window of step 224 of FIG. 2B, a list of acceptable resources may have been loaded and / or determined. At step 4 1 1 • 41-(37) (37) 200305088 msmaam, Qiqishan-on the list will be selected, and the resource with south priority will be selected. At the step, the material feasibility judgment will be made, and 2 ^ Du 'Step 412' A. ^. It is determined whether the location / resource has sufficient materials to satisfy if the order has sufficient ^ ^ .. No, is the material available? In step 4 1 4, the combination of 嵙, 欠, and κ 疋 疋 + 1 4 1 6 ^ 做出 to make a feasibility assessment of the limitation of Beiyuan. At step 416, a material compatibility check is made in the order. In step 418,

估用於FGSKU的摘狀 B ΜΆ muKr ^ ^ r 貪源機會,以及最佳機會會選 擇為用於位置的「最伟一 ^ —、$、 佳個」。在步騾418,在評估用於姓 足位置〈桶狀區間/資源機會之後, ; 否還有要檢查的資源。如果有用於相同位驟420 ’會判斷是 資源,則會回到步驟411 、置《其他可接受 源。如果在相同位置不再有可接; 選:用來評估的另-資 會選擇及記住最佳桶狀區間/資源機* '原’則在步驟422 斷是否還有可接受的位置。如果如此…在步驟424,會判 及選擇另-位置。#果不再有可接受位則會回到步驟406 會選擇最佳位置/資源/桶狀區間。在置’則在步驟426 分配到最佳位置/資源/桶狀區間。在步驟428,會將訂單 否還有需要規劃的訂單。如果有其+驟43〇,會判斷是The pick B 摘 muKr ^ ^ r estimated for FGSKU, and the best opportunity will be selected as the "most powerful ^ —, $, best one" for the position. At step 418, after assessing the use of the surname position <barrel interval / resource opportunity, whether there are resources to check. If there is a resource 420 'for the same bit, it is judged to be a resource, and then it returns to step 411 and sets other acceptable sources. If there is no more access at the same position; Choose: The other-used for evaluation will choose and remember the best bucket interval / resource machine * 'Original', then step 422 determines if there is still an acceptable position. If so ... At step 424, another-position is determined and selected. #If there are no more acceptable bits, then go back to step 406 and choose the best location / resource / barrel interval. In-place 'is allocated in step 426 to the best location / resource / barrel section. At step 428, there will be no more orders that need planning. If it has +43, it will be judged as

程序400會從步驟402重新開始,否 7早貝J ν程序會結束。 以下伴隨圖5Α到5Η的簡化例子借 示用來規劃資源的 利用之程序400如何達成需求。在此 到貝你白0 1 子,已選擇訂輩〇 ^ 5 02來做規劃,如圖5A所顯示。訂單 千1 1 5 〇 2係選自按優先 順序處理的清單(未顯示)。基於相關Λ、 &amp;可單〇 i 5 0 2的資訊 ,可決定出F G S KU的清單(因此可捲&amp; 又的位置,Loc卜Loc2 及L 〇 c 3 )。在此例中,可接受的位置 *、決定為 Loci 504、 •42- 200305088 (38)The process 400 will restart from step 402, otherwise, the program will end. The following simplified examples accompanying Figures 5A through 5 (b) illustrate how the process 400 used to plan the use of resources can meet the demand. At this point, you have been selected as a white 0 1 son, and have been selected to order 0 ^ 5 02 for planning, as shown in Figure 5A. The order 1 1 5 2 is selected from a list (not shown) processed in order of priority. Based on the relevant Λ, &amp; can be 0 502 information, a list of F G S KU can be determined (hence the location of &amp; and Loc 2 and Loc 2 and Loc 3). In this example, the acceptable location *, decision is Loci 504, • 42- 200305088 (38)

Loc2506及Loc3508。可接受的位置也可藉由偏愛來排序 。因此,在此例中’ Loci 504係在Loc2 506之上’因為Loci 504比Loc2 506更合意,以及Loc2 506係在Loc3 508之上 ,因為Loc2 506比Loc3 508更合意。此第一步驟通常對應 於圖4的步驟404。 接著,會再檢查訂單位置對(Ο 1,L 〇 c 1)及做出關於製造 位於L 〇 c 1的訂單〇 1之可接受資源的清單之決定。一旦決 定可接受資源的清單,清單會藉由偏愛來排序’如圖5 B 所顯示。在此圖中,資源R S 11 5 1 0係在R S 12 5 1 2之上’因 為113115 10比RS12 5 12更合意。此步驟通常對應於圖4的 步驟410。在下個步驟中(其通常對應於412)’會試圖將位 於可在位置Loci 5 04上潛在地製造訂單之第一資源RS η 5 10的訂單列入計畫表中。然後會將結合(〇1-Locl-RSli) 的列入計畫表機會列入計畫表中、做評估及分準位(此步 驟通常對應於414),如圖5C中所顯示。 接著,最後二個步驟(亦即,圖4的步驟412及4 14)會重 複用於資源RS i 2 5 1 4,如圖5 D中所顯示。在此例中’關於 (Oi-Locl-RS^)的列入計畫表機會之準位會發現比關於 (Oi-Locl-RSn)所計算的更佳,因此(〇1-L〇cl-RSl2)的列 入計畫表機會為到目前為止所發現的最佳列入計畫表機 會,並且會記住為用於Loci 504是最佳的。 一旦Loci 5 04中的所有可接受資源已評估出來’會檢查 可接受位置之清單中的下個位置(位置L〇c2516)’如圖5E 所顯示。只有一種可接受資源,用於1丁單〇1 502之位於 -43 - 200305088 (39) [〇。2 506的11321518。會做出試圖將資源1^21516列入計 畫表中,如圖5 F所顯示’並且或評估結果。如果成功, 用於(Oi-Loc]-!^^)的列入計畫表機會會與用於 (Ο ! - L 〇 c 1 - R S 12)的列入計畫表機會做比較,以決定最佳的 訂單/位置/資源組合。會做比較,以將所計算的適合度與 「到目前為止為最佳的」做比較,以及假如其適合度超過 到目前為止所發現的最佳適合度,則會將目前的列入計畫 表機會儲存為「到目前為止所發現的最佳列入計畫表機會 」。在此例中,用於(〇1-!^〇(:2-11312)的列入計畫表機會係 發現為「到目前為止為最佳的」。 因為所有資源係在用於L 〇 c 2的Ο!之可接受資源的清單 中’所以會重新檢查在〇 i的位置之清單中的下個位置。 然而,如圖5G中所顯示,沒有用於l〇c3 5 18的可接受資 源。然後到目前為止所發現之用於最佳列入計晝表機會的 列入計畫表資訊,(Oi-LochRS!2),會記住,更新所有限 制上的可用性,以及提取下個訂單及以如圖5H所顯示之 相似的方式來處理它。 在圖4的流程4 0 0所介紹之特定步驟及概念的更詳細說 明將於底下提供。在步驟402中,會選擇下個或第一優先 全訂單(亦即,來自排序的訂單清單)來做處理。在此步驟 期間,限制及/或規則會定義出來,以提供用於規劃訂單 的參數。限制及/或規則將通常會基於相關於所選擇的訂 單之資訊。要注意的是此步驟及所有接下來的步赞會重複 於迴路中,直到在目前優先權群組中的所有訂單都已處理 -44- 200305088 (40) 。再者要注意的是關於所有組態及所有資源的可行性不需 要做檢查。一旦已得到良好的足夠結果,程序會停止。 為了顯示定義於處理步驟402中的參數如何會影響訂單 列入計畫表的方式,以下簡化的訂單處理例子會提供。假 設汽車製造商接受具有三種屬性的訂單:項目名稱、位置 及需求日期。項目名稱可以是由製造商所建造的汽車的樣 式名稱。位置為工廠位置,或任何遞送位置,如客戶的 位置。需求日期係表示汽車的完成曰期。現在參照圖51 ,其係顯示可能用於汽車樣式「轎車」之訂單的屬性值之 各種組合之方塊圖540。象限1 542係表示指定訂單必須完 成之需求日期及位置之訂單。象限1 542中的訂單將指定 SKU=「轎車」(亦即,項目名稱)、「亞特蘭大」(亦即, 位置)、以及「5個星期」(亦即,需求日期)。在此例中, ABP系統100可解決用於訂單之適合的桶狀區間/資源機 會,會受到某種條件的支配。例如,較佳而言,桶狀區間 將會落於用於訂單之可接受的列入計畫表區間。例如,可 接受的列入計畫表區間係介於「需求日期-最早可允許的 」與「需求日期+最晚可允許的」之間。較佳而言,資源 係位於訂單上所指定的位置(意含訂單上所指定的SKU) 。較佳而言,相關於材料及其他可用的硬式限制的分配是 可行的。較佳而言,桶狀區間/資源機會應該是所有潛在 機會中最佳的,或者是對應於目標函數中的每個目標之準 位的一個係低於指定的臨界值。多級目標函數係用來評估 最佳桶狀區間/資源機會。ABP系統100可允許一些規律, -45- 200305088Loc2506 and Loc3508. Acceptable positions can also be sorted by preference. Therefore, in this example, 'Loci 504 is above Loc2 506' because Loci 504 is more desirable than Loc2 506, and Loc2 506 is above Loc3 508, because Loc2 506 is more desirable than Loc3 508. This first step generally corresponds to step 404 of FIG. Next, the order position pair (0 1, L 0 c 1) is checked again and a decision is made as to the list of acceptable resources for manufacturing the order 0 1 located at L 0 c 1. Once the list of acceptable resources is determined, the list is sorted by preference 'as shown in Figure 5B. In this figure, the resource R S 11 5 1 0 is above R S 12 5 1 2 'because 113115 10 is more desirable than RS12 5 12. This step generally corresponds to step 410 of FIG. In the next step (which usually corresponds to 412) 'will attempt to include the order in the first resource, RS η 5 10, which is a potential manufacturing order at location Loci 5 04, in the plan sheet. The combination (〇1-Locl-RSli) will then be included in the plan table, evaluated and scored (this step usually corresponds to 414), as shown in Figure 5C. Next, the last two steps (ie, steps 412 and 4 14 of FIG. 4) are reused for the resource RS i 2 5 1 4 as shown in FIG. 5D. In this example, the level of opportunity for inclusion in the schedule for (Oi-Locl-RS ^) will be found to be better than calculated for (Oi-Locl-RSn), so (〇1-L〇cl- RS12) is the best listing opportunity found to date and will be remembered as the best for Loci 504. Once all acceptable resources in Loci 5 04 have been evaluated, 'the next position in the list of acceptable positions (position L0c2516)' is checked as shown in Figure 5E. There is only one acceptable resource for 1 Ding 〇 502 located at -43-200305088 (39) [〇. 2 215 11321518. An attempt will be made to include resource 1 ^ 21516 in the schedule, as shown in Figure 5F, and / or evaluate the results. If successful, the schedule opportunity for (Oi-Loc]-! ^^) will be compared with the schedule opportunity for (O!-L 〇c 1-RS 12) to determine Best order / location / resource combination. A comparison will be made to compare the calculated fitness with the "best by far" and if the fitness exceeds the best fitness found so far, the current inclusion will be included in the plan The table opportunity is stored as "the best opportunity to be included in the plan table found so far." In this example, the schedule opportunity for (〇1-! ^ 〇 (: 2-11312) was found to be "best by far." Because all resources are being used for LO 2 of the 0! List of acceptable resources, so the next position in the list of 0i positions will be rechecked. However, as shown in FIG. 5G, there is no acceptable resource for 10c3 5 18 . Then the listing schedule information (Oi-LochRS! 2) found so far for the best day listing opportunity, (Oi-LochRS! 2), will remember to update the availability on all limits, and pick up the next order And handle it in a similar way as shown in Figure 5H. A more detailed description of the specific steps and concepts introduced in the process 400 of Figure 4 will be provided below. In step 402, the next or A priority full order (that is, from a sorted order list) for processing. During this step, restrictions and / or rules are defined to provide parameters for planning the order. Limits and / or rules will usually be based on Information about the selected order. Note that this step and All the next steps will be repeated in the loop until all orders in the current priority group have been processed -44- 200305088 (40). Also note that the feasibility of all configurations and all resources No check is required. The program will stop as soon as good and sufficient results have been obtained. In order to show how the parameters defined in processing step 402 affect the way the order is included in the planning table, the following simplified order processing example will be provided. Assume a car Manufacturers accept orders with three attributes: item name, location, and demand date. The project name can be the style name of a car built by the manufacturer. The location is the factory location, or any delivery location, such as the customer's location. The demand date is Represents the date of completion of the car. Reference is now made to Figure 51, which is a block diagram 540 showing various combinations of attribute values that may be used for orders of the car style "sedan". Quadrant 1 542 represents the date and location of the demand that a specified order must complete Orders in quadrant 1 542 will specify SKU = "sedan" (ie, item name), "Atlant Large ”(i.e., location), and“ 5 weeks ”(i.e., demand date). In this example, the ABP system 100 can resolve a suitable bucket interval / resource opportunity for an order, subject to some sort of Domination by conditions. For example, preferably, the bucket interval will fall within the acceptable schedule interval for orders. For example, the acceptable schedule interval is between "demand date- "Earliest allowed" and "demand date + latest allowed". Preferably, the resource is located at the position specified on the order (meaning the SKU specified on the order). Preferably, the related Allocation of materials and other hard constraints is feasible. Preferably, the bucket interval / resource opportunity should be the best of all potential opportunities, or the level corresponding to each goal in the objective function One is below the specified threshold. A multi-stage objective function is used to evaluate the optimal bucket interval / resource opportunity. ABP system 100 can allow some laws, -45- 200305088

每個具有一個準位。使用者可從規律之預定的可延伸清單 中選擇,以及分配SAD群組(以識別出那一訂單是可用的) 及規律的準位。使用者也可指定容忍值,以識別出二種規 律需多靠近,才會將值視為相等。例如,如果差異為〇 · 1 ’則具有值2 · 0 1及2 · G 2的一種規律會視為具有相同值。當 - 二種機會與已知訂單做比較時,規律中的準位會從最高優 先權到最低優先權做檢查。在容忍值内之不同的第一級係 告知此機會是較佳的。 象限2 544係表示指定需求日期,但是未指定位置之訂 _ 早。例如’訂皁會指定如轎車的項目及如5個星期的需求 日期。在此例中,ABP系統1〇〇可解決用於訂單之適合的 桶狀區間/資源機會,f受到某種條件的支配。較佳而言 ,桶狀區間會落於用於訂單之可接受的列入計畫表區間。 資源可位於任何位置。相關於材料及所有可用的限制的分 配必肩疋可伃的。較佳而言,桶狀區間,資源機會應該是 所有潛在機會中最佳的,或者是對應於目標函數中的每個 目標之準位的-個係低於指定的臨界值。 · 象限3 546係表示未指定需求日期或位置之訂單。例如 訂單,、和員目,轎車。及如5個星期的需求日期。在 ' 此例中’ ABP系統1〇〇可解決用於訂單之適合的時間桶狀: ^間/資源機會,會受到某種條件的支配。例如,較隹而 言,時間桶狀區間可以在規劃範圍中的任何位置。資源玎 位於任何位置。較佳而言,相關於材料及所有可用的P艮制 的刀配將疋可仃的。較佳而言,桶狀區間/資源機會應该 -46- (42) (42)200305088 是所有潛在機會中最佳的,或者是對應於目標函數中的每 個目標之準位的一個係低於指定的臨界值。 象限4 5 4 8係表示未指定需求日期,但指定位置之訂單 。例如,訂單可指定項目,轎車,以及位置,亞特蘭大 在此例中,ABP系統1 00可解決基於某種條件之用於訂單 之適合的桶狀區間/資源機會。例如,桶狀區間可以 在規 劃範圍中的任何位置。較佳而言,資源可位於訂單上所# 定的位置。較佳而言,相關於材料及所有可用的限制的分 配是可行的。較佳而言,桶狀區間/資源機會是所有潛在 機會中最佳的,或者是對應於目標函數中的每個目標之準 位的一個係低於指定的臨界值。 在(圖4的)步驟404,用於步驟492可接受位置所選擇的 訂單之所選擇的組態會決定出來,並且基於訂單屬性而按 優先順序處理。用於訂單之成品SKU的集合會決定出來。 FG SKU會已載入至圖2B的步驟224中的訂單視窗。集合可 基於某種標準而決定出來。例如,如果SKU已指定於訂單 上,則此SKU為集合中唯一的成品SKL^為了說明,假設 訂單係關於亞特蘭大的轎車,則只有此FG SKU可包含於 集合中。另一方面,如果訂單指定項目,則關於此項目的 所有SKU無論位置如何,都是可行的成品SKU。例如,如 果訂單只有指定轎車,具有無論位置如何(亦即,亞特蘭 大或任意其他城市)之以轎車當作項目之任何SKU都是可 行的成品SKU (假設這些SKU存在)。如果在集合中,有多 種FGSKU,這些FGSKU可使用延伸介面來排序。在規劃 -47- 200305088 (43) 具有較低偏愛的SKU之前,會做出排序,以指引ABp系統 100使用最偏愛的SKU(因此,位於最偏愛的位置)來規劃 訂單。A B P系統1 0 〇會支援介面的基本實施,其合根據從 SKU位置到訂單上的目的位置之運輸費用來將SKU集合 排序。這些費用可使用位置乘以位置的運輸矩陣而模型化 。例如,會產生一種表,其允許使用者指定每單位亞特蘭 大L丹佛的費用1.0元,每單位亞特蘭大 &gt;丹佛的費用0·75 元。如果沒有入口存在’則成品不會在已知位置之間移動。 基本上’決定出FG SKU的集合將會導致決定出可接受 位置的清單。S KU是與位置相依的。因此,一旦所有可接 受的SKU識別出來,可接受位置也將識別出來。 FG SKU的集合可藉由偏愛來排序。亦即,某種FG SKU 會基於例如位置偏愛而比其他FG SKU具有更高的優先權 。此位置偏愛可源自於客戶偏愛或製造商的偏愛或某些第 二方的偏愛。 在(圖4的)步驟406中,會選擇用於規劃具有最高優先權 的可接受位置。一般而言,這將是以位置為基礎的偏愛。 因此,具有最偏愛位置的FG SKU將會優先選擇用來規劃。 在(圖4的)步驟406,會初始化單一成品SKU訂單組合之 特有的FG SKU,藉此屬性會複製到訂單,而不會複製到 SKU。相關於ABP系統100中的各種實體(例如,訂單、SKU 、項目及類似之物)之屬性會以三種準位(項目、SKU及訂 單準位)來模型化。特定於項目(以及具有與規劃關聯)之 生產、設計或銷售相關屬性會以項目準位來模型化。以項 -48 - 200305088Each has a level. The user can choose from a regular, extensible list and assign SAD groups (to identify which order is available) and regular levels. The user can also specify tolerance values to identify how close the two rules need to be before they are considered equal. For example, if the difference is 0 · 1 ', a rule having the values 2 · 0 1 and 2 · G 2 is regarded as having the same value. When-two opportunities are compared with a known order, the level in the rule is checked from the highest priority to the lowest priority. The first tier that differs within the tolerance value tells that this opportunity is better. Quadrant 2 544 indicates the date of the specified demand, but the order of the unspecified position is _ early. For example, 'order soap will specify items such as cars and demand dates such as 5 weeks. In this example, the ABP system 100 can resolve the appropriate bucket interval / resource opportunity for the order, f is subject to certain conditions. Preferably, the bucket interval will fall within the acceptable schedule interval for orders. Resources can be located anywhere. The assignments related to materials and all available constraints must be shouldering. Preferably, in the bucket interval, the resource opportunity should be the best among all potential opportunities, or the level corresponding to each target in the objective function-the system is below the specified threshold. · Quadrant 3 546 represents orders without a specified date or location. For example, orders, and staff, cars. And such as the demand date of 5 weeks. In 'this example', the ABP system 100 can resolve a suitable bucket of time for orders: time / resource opportunities, subject to certain conditions. For example, relatively speaking, the time bucket interval can be anywhere in the planning range. Resources 玎 are located anywhere. Preferably, knife materials related to the material and all available puddings will be acceptable. Preferably, the bucket interval / resource opportunity should be -46- (42) (42) 200305088, which is the best of all potential opportunities, or a low corresponding to the level of each goal in the objective function. At the specified threshold. The quadrants 4 5 4 8 represent orders without a specified date but at a specified location. For example, an order can specify an item, a car, and a location, Atlanta. In this example, the ABP system 100 can resolve a suitable bucket interval / resource opportunity for an order based on certain conditions. For example, a bucket interval can be anywhere in the planning range. Preferably, the resource can be located at the position specified on the order. Preferably, assignments related to materials and all available restrictions are feasible. Preferably, the bucket interval / resource opportunity is the best of all potential opportunities, or one of the levels corresponding to each objective in the objective function is below a specified threshold. At step 404 (of FIG. 4), the selected configuration for the order selected at the acceptable location in step 492 is determined and processed in priority order based on the order attributes. The set of finished SKUs for the order will be determined. The FG SKU will be loaded into the order window in step 224 of FIG. 2B. Sets can be determined based on some criteria. For example, if the SKU has been specified on the order, then this SKU is the only finished SKL in the set. For illustration, assuming that the order is for an Atlanta car, only this FG SKU can be included in the set. On the other hand, if an order specifies an item, all SKUs related to this item are feasible finished SKUs regardless of their location. For example, if the order has only designated cars, any SKU with a car as an item regardless of location (that is, Atlanta or any other city) is a viable finished SKU (assuming these SKUs exist). If there are multiple FGSKUs in the collection, these FGSKUs can be sorted using the extended interface. Prior to planning -47- 200305088 (43) a SKU with a lower preference is sorted to direct the ABp system 100 to use the most preferred SKU (hence the most preferred location) to plan the order. The A B P system 100 will support the basic implementation of the interface, which will sort the SKU collection according to the transportation cost from the SKU location to the destination location on the order. These costs can be modeled using the location-by-location transport matrix. For example, a table would be generated that allows the user to specify a cost of $ 1.0 per unit of Atlanta L Denver, and a cost of $ 0.75 per unit of Atlanta &gt; Denver. If no entrance exists' then the finished product will not move between known locations. Basically, deciding on the set of FG SKUs will lead to deciding on a list of acceptable locations. S KU is location dependent. Therefore, once all acceptable SKUs are identified, acceptable locations will also be identified. The collection of FG SKUs can be sorted by preference. That is, certain FG SKUs have higher priority than other FG SKUs based on, for example, location preferences. This location preference can be derived from customer preferences or manufacturer preferences or some second party preferences. In step 406 (of FIG. 4), an acceptable location is selected for planning with the highest priority. In general, this will be a location-based preference. Therefore, the FG SKU with the most preferred location will be preferred for planning. In step 406 (of FIG. 4), the unique FG SKU of the single finished SKU order combination is initialized, whereby the attributes are copied to the order and not to the SKU. The attributes related to various entities in the ABP system 100 (for example, orders, SKUs, items, and the like) are modeled at three levels (item, SKU, and order level). Project-specific (and associated with planning) production, design, or sales-related attributes are modeled at the project level. Israel -48-200305088

目準位模变化的屬性通常會應用於已知項目的所有SKU(無 論位置如何)。較佳而言,特定於已知位置的項目及應用 於此位置所規劃的所有訂單之屬性會以SKU準位來模型 化。特定於訂單(其傾向於基於客戶偏愛而使訂單變化) 的屬性會以訂單準位來模型化。如果訂單具有關於屬性的 值,則其會使用。如果訂單不具有關於屬性的值,但其相 關的SKU有,則會使用SKU值。如果訂單及SKU都不具有 關於屬性的值,而項目有,則會使用項目值。如果訂單、 SKU、以及項目都不具有關於屬性的值,則沒有值會用於 此訂單。 在初始化步驟期間,會做出所有可用的s A D群組之決定 。描述FG SKU物件的所有SAD群組會決定出來。這可藉 由將S A D群組上的屬性(名稱-值對的布林組合)對ρ g $ K U 物件上的屬性(名稱-值對)匹配來達成。在達成此之中, 會判斷出那些SAD群組為位置(以及資源)相依的。此步驟 會進行,以致於SAD群組可用性的多重檢查將不會對相同 訂單,或對相同的訂單/資源組合(關於位置相依的sad群 組)做兩次。初始化步驟也會包括計算訂單的有效需求日 期之步驟。當考慮到關於遞送物品至請求位置的運輸時間 時,有效需求日期為需求成品時的真正日 碉。如果訂單使 用已知的成品SKU來達成,則訂單的有效紮,+、 % I曰期會計算 出來。此計算可例如藉由以下的某些步驟 %來達成。例如, 如果可單上有抵達曰期,則「有效需求 、时 辟1 =抵達日期- 從可早上的客戶位置到已知成品SKU的位茧、 I&lt;運輸時間」 -49· 200305088 (45) 。如果訂單上沒有抵達日期且訂單上有需求日期,則[有 效需求日期=訂單上的需求日期]。如果訂單上都沒有抵達 曰期及需求日期,則[有效需求日期=無效]。初始化步驟 可包括計算用於FG SKU物件之正確列入計畫表區間的步 騾。如果有有效需求日期,會較佳地使用最早及最晚參數 來計算正確列入計畫表區間。如果沒有有效需求曰期,則 正確列入計畫表區間為規劃區間。早/晚表會產生,以及 藉由SAD群組而定義出相對於有效需求日期之訂單可多 晚或多早列入計畫表中。如果沒有需求日期,此表會沒有 效用。決定優先權的序號會分配給此表的SAD群組。如果 此表中的多個SAD群組係係用於FG SKU物件,則序號可 用來決定具有最高優先權的SAD群組(以及最早與最晚參 數)。 在步驟410中,ABP系統100會決定用於FG SKU的那些 資源為可接受或可允許的,以及會產生潛在資源的清單。 然後會將這些可允許資源排序,以致於具有較高優先權或 偏愛的那些資源比具有較低優先權的資源將會在較低優 先權的資源做檢查之前,優先做檢查,以決定列入計畫表 機會。可允許資源的決定通常取決於許多因素。例如,只 有位於可用位置的那些資源將通常會視為可行的資源。其 他的因素會防止特定資源被考慮。例如,概念上來說,至 少有二種因素會限制此組資源,資源位置及專用資源群組 。資源位置因素為資源為未位於成品SKU物件所定義的位 置上的時候。這樣的資源將不會考慮為潛在資源。專用資 -50- (46) (46)200305088 源群組因素為資源與專用資源群組有關的時候。專用資源 群組的去除可藉由產生專用資源SAD群組而定義出來。例 如,假彀專用資源群組包括在亞特蘭大的裝配線丨及丹佛 的裝配綠1。此專用資源群組的去除可藉由SAD群組「項The attributes of the target mode change are usually applied to all SKUs of a known project (regardless of location). Preferably, the items specific to a known location and the attributes of all orders planned for this location are modeled at the SKU level. Order-specific attributes that tend to change orders based on customer preferences are modeled at the order level. If the order has a value for an attribute, it is used. If the order does not have a value for the attribute, but its associated SKU is, then the SKU value is used. If neither the order nor the SKU has a value for the attribute, and the item does, the item value is used. If none of the order, SKU, and item have values for the attribute, no value will be used for this order. During the initialization step, a decision is made on all available SD groups. All SAD groups describing FG SKU objects are determined. This can be achieved by matching the attributes (name-value pairs of the Bollinger combination) on the S A D group to the attributes (name-value pairs) on the ρ g $ K U object. In achieving this, it will be determined which SAD groups are location (and resource) dependent. This step is performed so that multiple checks of SAD group availability will not be done twice for the same order, or for the same order / resource combination (for sad groupings that are location-dependent). The initialization step will also include the step of calculating the effective demand date for the order. When considering the transit time for delivering items to the requested location, the effective demand date is the real date when the finished product is required. If the order is made using a known finished SKU, the effective order will be calculated and the + and% I dates will be calculated. This calculation can be achieved, for example, by some of the steps% below. For example, if there is a date of arrival on the order, "effective demand, time 1 = arrival date-from the customer location in the morning to the location of the known finished SKU, I &lt; transport time" -49 · 200305088 (45) . If there is no arrival date on the order and there is a demand date on the order, [effective demand date = demand date on the order]. If neither the date nor the demand date arrives on the order, [valid demand date = invalid]. The initialization step may include the step of calculating the correct inclusion in the schedule interval for the FG SKU object. If there is a valid demand date, it is better to use the earliest and latest parameters to calculate the correct inclusion in the schedule table. If there is no effective demand date, it is correctly included in the planning interval as the planning interval. The morning / night table will be generated, and the SAD group defines how late or early the order can be listed in the plan table relative to the effective demand date. If there is no demand date, this table will be useless. The priority number is assigned to the SAD group of this table. If multiple SAD groups in this table are for FG SKU objects, the serial number can be used to determine the SAD group with the highest priority (and the earliest and latest parameters). In step 410, the ABP system 100 will decide which resources to use for the FG SKU are acceptable or allowable, and will generate a list of potential resources. These permissible resources are then sorted so that those with higher priority or preference than those with lower priority will be checked before the lower priority resources are checked to determine their inclusion. Schedule opportunities. The decision on allowable resources usually depends on many factors. For example, only those resources that are available will generally be considered viable resources. Other factors prevent specific resources from being considered. For example, conceptually, there are at least two factors that limit this set of resources, resource locations, and dedicated resource groups. The resource location factor is when the resource is not at the location defined by the finished SKU object. Such resources will not be considered as potential resources. Dedicated funds -50- (46) (46) 200305088 The source group factor is when the resource is related to a dedicated resource group. Deletion of a dedicated resource group can be defined by generating a dedicated resource SAD group. For example, the Fake Dedicated Resource Group includes assembly lines in Atlanta and Assembly Green1 in Denver. The removal of this dedicated resource group can be done by the SAD group "item

目-轎車或項目=小卡車」而定義出來。考慮過的FG SKU 物件可以是「亞特蘭大的SUV ’顏色 '红色,電動窗=是, 内邵=皮革」。在此例中,在亞特蘭大的線丨為只會製造轎 車及】、卡車之專用資源群組的部分。雖然sKU物件的 位置=亞特蘭大,但是裝配線1不是可允許的資源,因為 對應於我們的FG SKU物件的項目為SlJv❶當可允許資源 識別出來時,其會排序,以致於最偏愛的資源會在較不偏 愛的資源做檢查之前,優先檢查列入計晝表的機會。 在步驟411,如果資源已排序’會選擇具有最高優先權 的資源》如果可允許資源的集合未以優先權來排序,則系 統會隨機選擇,或藉由系統使用者所定義的任何其 方法。 合在步驟412,會評估FGSKU物件的材料可行性。此步驟 會判斷先前所選擇的資源是否將有足夠的「材料」供應, 以在可接受的時間週期内,提供FG SKu物件的需求量。「 材料」可以是元件部分或材料,或者是關於請求的成品之 成本身。基於先前所決定的Fg SKU物件,ABP系統1〇〇 曰材料凊單(BOM)中的每個準位來搜尋(偏愛的訂單中 多種組態。搜尋可允許取代品,以找出關於成品sku 的最佳材料組態。 -51- (47) (47)200305088 為了了解ABP系、统100的材料可行性能力,「桶狀區間」 的概念會敘述如下。較佳而言,ABP系統100為桶狀區間 規劃系統。此意謂系統試圖將訂單規劃成桶狀區間。會產 生用於每種限制的桶狀區間。用於限制的桶狀區間可由日 曆、樣式範圍及限制的特性之組合而定義出來。日曆會產 生,以及用來定義一些桶裝區間及可用的每個桶裝區間之 持續期間。樣式起始係用來決定每個桶狀區間的真正起始 日期及結束日期。規劃範圍+限制起始小變動(deita)係決 定第一桶狀區間起始將位於那裡。這是因為ABp系統1〇〇 需要從週期到週期做轉動。例如,假設使用者在星期一(第 1)做下個星期一(第8)的規劃^水平起始將是星期一(第8) ,並且限制通常會具有零偏移,以致於用於全部限制的第 一桶狀區間將是星期一(第8)。當下個星期到達時,使用 者將會在星期一(第8)做星期一(第15)的規劃,並且使用 者的規劃範圍將設定為星期一(第15)。因為偏移為零,所 以桶狀區間起始將是星期一(第15)。要注意的是,藉由改 變規劃範圍起始會使整個系統發生調整。顯然地,如果在 水平起始後,有一個星期起始的限制,當規劃星期一(第 8),第一桶狀區間將是星期一(第15)。當下個星期到達且 規劃下個星期一(第丨5)的開始時,第一桶狀區間將是在此 後的7天或星期一(第22)。每個桶狀區間可包括一個或多 個元件,其包括時間(桶狀區間的寬度或持續期間)、最大 容量(應該安置於桶狀區間中之訂單的希望最大數目)、放 鬆的最大容量(可安置於桶狀區間中之訂單的確實最大數 -52- 200305088Project-Car or Project = Pickup ". The FG SKU object considered could be "Atlanta's SUV 'Color' Red, Power Window = Yes, Inner Shaw = Leather". In this example, the line in Atlanta is part of a dedicated resource group that only manufactures cars and trucks. Although the position of the sKU object = Atlanta, assembly line 1 is not an allowable resource, because the item corresponding to our FG SKU object is SlJv. When the allowable resources are identified, they will be sorted so that the most preferred resource will be in Priority inspections for non-favorite resources are given priority inspection opportunities. In step 411, if the resources are sorted ', the resource with the highest priority is selected. "If the set of allowable resources is not sorted by priority, the system will choose randomly, or by any other method defined by the system user. In step 412, the material feasibility of the FGSKU object is evaluated. This step will determine whether the previously selected resources will have sufficient "material" supply to provide the required amount of FG SKu objects within an acceptable period of time. “Materials” can be component parts or materials, or the finished product itself with respect to the request. Based on the previously determined Fg SKU objects, the ABP system searches for each level in the Bill of Materials (BOM) (multiple configurations in the preferred order. The search allows replacements to find out about the finished sku -51- (47) (47) 200305088 In order to understand the material feasibility of the ABP system and system 100, the concept of "barrel section" will be described as follows. Preferably, the ABP system 100 is Bucket interval planning system. This means that the system attempts to plan an order into a bucket interval. It will generate a bucket interval for each restriction. The bucket interval for restrictions can be a combination of calendar, style range, and restricted characteristics Define it. The calendar will be generated and used to define some barrel intervals and the duration of each barrel interval available. The style start is used to determine the true start and end dates of each barrel interval. Planning scope + Limit the starting small change (deita) to determine where the beginning of the first barrel interval will be located. This is because ABp system 100 needs to rotate from cycle to cycle. For example, suppose the user is on Monday (the first) do The plan for every Monday (8th) ^ The horizontal start will be Monday (8th), and the limit will usually have a zero offset, so that the first bucket interval for all limits will be Monday (8th) ). When the next week arrives, the user will plan for Monday (15th) on Monday (8th), and the user's planning range will be set to Monday (15th). Because the offset is zero , So the beginning of the bucket interval will be Monday (15th). It should be noted that changing the starting range of the planning range will cause the entire system to adjust. Obviously, if there is a week start after the horizontal start Restrictions, when planning Monday (8th), the first bucket interval will be Monday (15th). When the next week arrives and planning the beginning of the next Monday (5th), the first bucket interval It will be the next 7 days or Monday (22nd). Each bucket section can include one or more elements, which include time (width or duration of the bucket section), maximum capacity (should be placed in the bucket section) Maximum number of orders expected in the interval), maximum capacity to relax ( Placed in the barrel range in the maximum number of orders does -52-200305088

目)、以及最小容量(應該安置於桶狀區間中之訂單的最小 數目)。 每個桶狀區間的容量會由限制來控制。限制規則基本上 會限制每個桶狀區間或一群桶狀區間的容量。根據本發明 之一具體實施例,至少三種型式的限制規則是可行的,值 、百分比及平滑部分。值限制規則會提供用以定義從一個 桶狀區間到下一個之容量的增加改變之機制。百分比限制 與值規則相似,除了定義於限制上的值會解讀為百分比, 而不會解讀為某種設定量。從一個桶狀區間到下一個的增 加改變為限制容量的百分比。平滑部份限制規則會將定義 於限制上的值解讀為對限制之總潛在負載的百分比。此負 載百分比係分佈於由桶狀區間範圍行所定義的規劃桶狀 區間中,按比例分配在基於桶狀區間中的總可用時間之桶 狀區間中。有使用限制的訂單數目係藉由桶狀區間的數目 來區分,以得到每個桶狀區間的最大容量。剩餘部份可在 根據某些圓滿結束規則(隨機地、從第一桶狀區間向前或 從最後桶狀區間向後、或藉由增加的所有桶狀區間)的桶 狀區間中展開。要注意的是,平滑規則會藉由計算每單位 可用時間的負載量及將此比與每個桶狀區間的可用時間 量相乘,而處理相疊的桶狀區間。 材料可行性 參照圖6,其為判斷材料可行性的流程6 0 0。程序6 0 0 的輸出為有關於需求材料的可行性之資訊,以及對於整個 規劃程序會是非常有用的。這樣的資訊可例如包括材料可 -53- (49) (49)200305088Project), and the minimum capacity (the minimum number of orders that should be placed in the barrel section). The capacity of each barrel section is controlled by limits. The restriction rule basically limits the capacity of each bucket interval or a group of bucket intervals. According to a specific embodiment of the present invention, at least three types of restriction rules are feasible, such as value, percentage, and smoothing part. The value limit rule will provide a mechanism to define the increase and change in capacity from one bucket interval to the next. Percent limits are similar to value rules, except that values defined on limits are interpreted as percentages and not as a set amount. The increase from one barrel interval to the next changes to a percentage of limited capacity. The smooth partial limit rule interprets the value defined on the limit as a percentage of the total potential load on the limit. This load percentage is distributed in the planned bucket interval defined by the bucket interval range line, and is proportionally distributed in the bucket interval based on the total available time in the bucket interval. The number of orders with a usage limit is distinguished by the number of bucket intervals to obtain the maximum capacity of each bucket interval. The remainder can be unrolled in bucket-like intervals according to some satisfactorily ending rules (randomly, from the first bucket-like interval forward or backward from the last bucket-like interval, or by adding all bucket-like intervals). It should be noted that the smoothing rule processes overlapping bucket intervals by calculating the load per unit of available time and multiplying this ratio by the amount of time available for each bucket interval. Material Feasibility Referring to FIG. 6, it is a process 600 for judging material feasibility. The output of Procedure 6 0 0 is information about the feasibility of the required material and can be very useful for the entire planning process. Such information may include, for example, materials -53- (49) (49) 200305088

用日期、材料可用量、可行性旗標、以及類似之物。輸出 可以是圖开,、文字或量化報告的形式。可行性旗標係表示 程序600找尋需用於選擇資源的材料供應是否是成功的。 如果可行性旗標表示程彳已成功’ Μ可用I通常會與需求 量相等,並且此數量將在可接受(需求日期+最晚)的最後 日期或在最後日期是可用的。如果一個或另外或條件沒有 同時滿足,可行性旗標將顯示程序是未成功的。較佳而言 ’會試圖找出在滿足需求量之最早日期或在滿足需求量之 最早日期之前之最早可用供應。在步驟6〇2,會擷取訂單 資料。在步驟604,會檢查選擇資源的存貨,以判斷材料 存f準位。在做出存貨足夠的判斷之後,p系統i 〇 〇會 產生有關於存貨的可用日期及將是可用的存貨數量之輸 出。存貨的可用日期將是存貨可用於使用的時候。可用存 :量可例如是藉由可用日期之存貨及列入計畫表的收入 量。在步驟606,會決定可用量是否會滿足需求量。為了 檢查存貨及做出存貨是否會滿足需求日期及數量的決定 :會使用有關於,例如,訂單屬性、有效需求曰期、需求 量、最早、最晚、以及類似之物的曰期。如果存貨判斷為 足夠的則會在步驟608產生輸出。如果另一方面,存貨 中未有足夠的量來達成需求量,則在步騾6 1 0,存貨必須 藉由製造及/或購買新的存貨來做補充。存貨的補充可藉 由製ie 構貝及/或取代存貨來達成。系統的製造、購買 及/或專代補充功能在底下會做更詳細的討論。在步驟ό 1 2 曰判斷補充步驟6 1 0是否足以滿足需求量。如果如此, -54- 200305088 (50) 則在步驟6 0 8會產生輸出。如果補充步驟6 1 0不足,則在步 騾614會試圖補足另一選擇的差距。取代步驟614在底下會 做更詳細的討論。在步驟6 1 6,會判斷取代步驟6 1 4是否能 成功地補足補充步驟6 1 0的短缺。如果補充步驟6 1 4成功, 則會產生輸出。如果補充步驟614不成功’則會在步驟618 產生輸出。要注意的是,由步驟608及618所產生的輸出會 是不同的。在步驟608所產生的輸出將較佳地包含可用量(其 應該與需求量相同)、可用日期、以及一種表示,如表示 在最後可接受曰期(需求日期+最晚)之前或在最後可接受 曰期可滿足需求量之表示「是」的可行性旗標。在步驟6 1 8 所產生的輸出將較佳地包含可用量(其將低於需求量)、可 用曰期、以及一種表示,如表示在最後可接受日期(需求 曰期+最晚)之前或在最後可接受日期不能滿足需求量之 表系「否」的可行性旗標。 檢查存貨步驟604通常需要在FG SKU物件的屬性與存 貨屬性之間,有確切的匹配。然而,在另一具體實施例中 ,莱些屬性的確切匹配不需用於稱為保存屬性的某些屬性 。例如,假設如果訂單的屬性係如下,項目=轎車、顏色 $紅色、以及電動窗=是。通常對於用來匹配此SKu的存貨 而言,這 &gt; 屬〖生中每一個必須確切地匹配。然而,假設包 栝用於客戶」的額外屬性為保存屬性。用於訂單的屬性 現在可以是項目=轎車、顏色=紅色、電動窗=是、以及客 戶二柬南業者。如果存貨具有相同的第一屬性(項目=轎車 、顏色=紅色、電動窗=是),.但不存在客戶屬性、,則存貨 •55· 200305088Use dates, material availability, feasibility flags, and the like. The output can be in the form of a graph, text or quantitative report. The feasibility flag indicates whether the process 600 was successful in finding the material supply needed to select the resource. If the feasibility flag indicates that Cheng has succeeded, the available M will usually be equal to the demand, and this amount will be available on the last date that is acceptable (date of demand + latest) or on the last date. If one or more or conditions are not met at the same time, the feasibility flag will indicate that the procedure was unsuccessful. More preferably, it will try to find the earliest available supply before the earliest date when the demand is met or before the earliest date when the demand is met. At step 602, the order data is retrieved. In step 604, the inventory of the selected resource is checked to determine the material inventory level. After making sufficient judgments on the inventory, the p system i 〇 〇 will produce an output about the availability date of the inventory and the amount of inventory that will be available. The availability date of the inventory will be when the inventory is available for use. Available stock: For example, the amount of inventory available on the available date and the amount of income included in the schedule. In step 606, it is determined whether the available amount will meet the demand amount. In order to check the inventory and make a decision as to whether the inventory will meet the demand date and quantity: related to, for example, order attributes, effective demand dates, demand quantities, earliest, latest, and the like dates. If the inventory is judged to be sufficient, an output is generated at step 608. If, on the other hand, there is not enough quantity in the inventory to meet the demand, then at step 6 10, the inventory must be replenished by manufacturing and / or purchasing new inventory. Replenishment of inventories can be achieved by manufacturing and / or replacing inventory. The system's manufacturing, purchasing, and / or dedicated supplementary functions are discussed in more detail below. In step 12, it is judged whether supplementary step 6 1 0 is sufficient to meet the demand. If so, -54- 200305088 (50) will produce output at step 608. If supplementary step 6 1 0 is insufficient, then step 614 will attempt to fill the gap of another option. The replacement step 614 is discussed in more detail below. In step 6 16, it will be determined whether replacing step 6 1 4 can successfully make up for the shortage in step 6 1 0. If supplement step 6 1 4 is successful, an output is produced. If the supplemental step 614 is unsuccessful ', an output is generated in step 618. Note that the output produced by steps 608 and 618 will be different. The output produced at step 608 will preferably include the available amount (which should be the same as the demand amount), the available date, and a representation, such as before or before the last acceptable date (demand date + latest). Accept the feasibility flag indicating "yes" if the date can meet the demand. The output produced at step 6 1 8 will preferably include the available amount (which will be lower than the demand amount), the available date, and a representation, such as before the last acceptable date (demand date + latest) or A table that fails to meet demand on the last acceptable date is a "no" feasibility flag. The checking inventory step 604 usually requires an exact match between the attributes of the FG SKU object and the inventory attributes. However, in another specific embodiment, exact matching of these attributes is not required for certain attributes called preservation attributes. For example, suppose if the attributes of the order are as follows, item = sedan, color $ red, and power window = yes. Generally, for the inventory used to match this SKu, this &gt; must be exactly matched in each case. However, it is assumed that the additional attribute of "for customers" is the preservation attribute. The attributes used for the order can now be Project = Car, Color = Red, Power Window = Yes, and Customer Two Cambodian Operator. If the inventory has the same first attribute (item = car, color = red, power window = yes), but there is no customer attribute, then the inventory • 55 · 200305088

屬性會與F G S K U物件的屬性匹配。然而,另一方面,如 果存貨具有如西北業者的客戶屬性,則將不會匹配。 存貨檢查步驟的淨邏輯(圖6的606)可參考圖7A至70而 得到最佳的了解,其為描述存貨準位及在一段時間期間的 需求量之範例的時間線。圖7 A係繪示在時間線700的早期 期間,存貨準位7 0 2會上升。需求曰期係繪示為垂直線7 〇 4 。最早可接受日期係藉由垂直線906而表示出來,其與需 求日期減去最早相等。最晚可接受日期係藉由垂直線7 〇 8 而表示出來,其與需求曰期加上最晚相等。因此,在垂直 線7 0 6與7 0 8之間的時間區間為可接受的時間期間。需求量 係藉由水平線7 1 0而表示出來。因為在此時間線7 0 0中,存 貨準位702會在時間線700的早期上升,所以存貨可用曰期 D1 710為在最早可接受日期706之前。存貨可用日期712 係存貨為最大值的日期,或存貨準位超過或相等於需求量 之第一日期。因此,在此時間線7 0 0中,從最早可接受日 期7 0 6起’所需的存貨是係可用的。在圖7 B的時間線7 2 0 中,存貨準位722的上升會慢於圖7A的存貨準位702。因 此,存貨可用日期為724為在最早可接受日期72 6之後,但 在需求日期7 2 8之前。參照圖7 C,其為另一範例的時間線 740 ^在此時間線74〇中,存貨準位742在時間線中很晚才 會上升(在需求曰期744之後),並且從不會到達需求量746 。在此例中的可用存貨日期74 8將是在最晚可接受日期752 之前,存貨為最大值(如750所表示)之最早日期。為了補 足最大存貨準位750與需求量746之間的差,存貨會補充及 -56- (52) (52) 200305088The attributes match the attributes of the F G S K U object. However, on the other hand, if the inventory has customer attributes like a Northwest operator, it will not match. The net logic of the inventory check step (606 in Figure 6) can be best understood with reference to Figures 7A to 70, which is a timeline that describes an example of inventory levels and demand over time. Figure 7A shows that during the early period of timeline 700, the inventory level 702 will rise. Demand dates are shown as vertical lines 704. The earliest acceptable date is indicated by the vertical line 906, which is equal to the required date minus the earliest. The latest acceptable date is indicated by the vertical line 708, which is equal to the demand date plus the latest. Therefore, the time interval between the vertical lines 7 06 and 70 8 is an acceptable time period. Demand is indicated by the horizontal line 7 1 0. Because the inventory level 702 rises early in the timeline 700 in this timeline 700, the inventory availability date D1 710 is before the earliest acceptable date 706. Inventory availability date 712 is the date when the inventory is at its maximum, or the first date when the inventory level exceeds or equals the demand. Therefore, in this timeline 700, the required inventory from the earliest acceptable date of 70.6 is available. In the time line 7 2 0 of FIG. 7B, the rise of the inventory level 722 will be slower than the inventory level 702 of FIG. 7A. Therefore, the inventory availability date is 724 after the earliest acceptable date of 72 6 but before the demand date of 7 2 8. Referring to FIG. 7C, it is another example timeline 740. In this timeline 74, the inventory level 742 rises very late in the timeline (after the demand date 744), and never reaches Demand 746. The available inventory date 74 8 in this example will be the earliest date that the inventory is at its maximum (as represented by 750) before the latest acceptable date 752. In order to make up the difference between the maximum inventory level 750 and the demand 746, the inventory will be replenished and -56- (52) (52) 200305088

99BHB /或部份或全部會以另一種來取抑 (如圖6之步驟610至614 所顯示)。圖7 D為在整個可桩A卩土 J搔又時間期間764 ,存貨準位 7 6 2維持為零的時候,以及直刭畀 】最後可接受日期770之後, 才會上升到需求量766,如由可用 田J用存貨日期D4 772所表示。 補充 為了更佳了解可用於補充的多 万法,以下的段落會說 明許多概念及項目’其包拾材料、、太 ,^ 材枓,目早(在此的BOM)及組態。 為了芫全了解本發明的創新觀 I先雨短地討論訂單 、BOM、SAD群組、組態與類似之 仍 &lt; 間的整個高準位關 係會是有幫助的。ABP系統1〇〇合 υυ曰規劃基於接收訂單之資 源的使用。訂單可表示客戶需电、游 而不、預測的客戶需求及/或 安全存貨(以提供未遇見需求的防借、^ y 、 ]防備)。每個訂單將會具有 屬性。用於相同SKU,可能有超過_個 ^ 個叮早。例如,假設 有具有屬性轎車@亞特之SKU。-錄—-1 1 —種玎早可相關於此 SKU,一種係用於具有選擇特性(電動窗)請求之轎車@亞 而第二訂單係用於具有未請求電動窗之轎車@亞 SAD群組係與訂單分離,並且可用來將訂單分組 。看待SAD群組的一種方是就是將其視為濾波器。SAD群 組係用於多種地方。例如,其用來定義處理順序,以及判 斷那些訂單可以那些資源來完成。組態可視為構建項目的 一種方式或指示。其通常會列出所需的材料,以完全構建 出搜尋過的項目。例如,在上例中,用於上述^車@&amp;# I大的組態將會列出需要的材料(亦即,元件),以建造轎 車。每個項目可能會有超過一種組態,因為會取代某些材 -57- 20030508899BHB / or some or all of them will be suppressed by another (as shown in steps 610 to 614 of Fig. 6). Figure 7D shows the time period 764, when the inventory level 7 62 is maintained at zero during the entire period of time, and the straight line] will rise to the demand 766 after the last acceptable date of 770, As indicated by available field J with inventory date D4 772. Supplement In order to better understand the multi-million methods that can be used to supplement, the following paragraphs will explain many concepts and projects ’which are packed with materials, materials, materials, wares (BOM here) and configuration. In order to fully understand the concept of innovation of the present invention, it would be helpful to briefly discuss the entire high-level relationship between order, BOM, SAD group, configuration, and the like. The ABP system 100-year-old plan is based on the use of resources for receiving orders. An order can represent a customer's need for electricity, travel, forecasted customer demand, and / or secure inventory (to provide protection against unmet demand, ^ y,] precautions). Each order will have attributes. For the same SKU, there may be more than ^ ^ bites. For example, suppose there is a SKU with the attribute sedan @ 亚特. -录 —-1 1 — A kind of 玎 can be related to this SKU, one is for cars with select characteristics (power windows) request @ 亚 and the second order is for cars with unrequested power windows @ 亚 SAD 群Departments are separate from orders and can be used to group orders. One way to look at SAD groups is to treat them as filters. The SAD group is used in many places. For example, it is used to define the processing order, and to determine which orders can be completed with which resources. Configuration can be viewed as a way or an indication of building a project. It usually lists the materials needed to fully build the item it was searching for. For example, in the example above, the configuration used for the above car @ &amp;# I large will list the required materials (ie, components) to build a car. Each project may have more than one configuration, as some materials will be replaced -57- 200305088

(53) 料。BOM會定義或識別出用於搜尋過的項目之所有組態 。:BOM也會定義母·子關係。SAD群組係藉由二種方式中 的B OM而使用。每種母-子關係具有母項及子項。如果一 種係取代具有SAD群組的母項,一種會有額外的控制準位 。例如,一種可能指明應用於項目轎車之所有訂單的關係 ,但是只要其具有電動窗的屬性。如果想要,一種可能指 明應用於具有電動窗屬性,而無論項目如何之所有訂單的 關係。組態使用SAD群組的另外方式就是決定可允許取代 品的時候。每種取代品具有母項及子項。使用者可取代用 於任一個項目之SAD群組,以及具有較佳的取代控制準位 。非相關於SAD群組的訂單將具有所有必要的屬性,以識 別出將需用於搜尋過的項目之材料(及組態)。 根據本發明之一具體實施例之ABP系統1 00所使用的 BOM係以屬性為基礎。不像傳統規劃系統中的BOM,根 據本發明所使用的B OM係允許以選擇及規則為基礎的材 料需求之模型化。以下提供的例子會介紹有關於B OM的 概念。在例如今日的汽車工業中,找出以下的規則是非常 平常的:所有轎車必須具有(無論所存在的其他選擇如何) 基本組之一般次組件A、B及C。具有天窗(但沒有電動窗) 的轎車樣式每部車需要一個天窗組件及10W馬達;具有電 動窗(但沒有天窗)的轎車樣式需要一個電動窗組件及 10W馬達;而同時具有電動窗及天窗的轎車樣式需要一個 電動窗組件、一個天窗組件及1 5 W馬達,因為額外的負載 ,所以較高瓦特數的馬達是需要的。要注意的是在此例中(53) expected. The BOM will define or identify all configurations for the searched items. : BOM also defines parent-child relationships. The SAD group is used by the B OM in two ways. Each parent-child relationship has a parent and child. If one line replaces a parent with a SAD group, the other will have additional control levels. For example, one might indicate a relationship that applies to all orders for a project car, but only if it has the property of a power window. If desired, one might indicate a relationship that applies to all orders that have power window attributes, regardless of the item. Another way to configure the use of SAD groups is when deciding on allowable replacements. Each substitute has a parent and child. Users can replace the SAD group used for any project, and have a better replacement control level. Orders that are not related to the SAD group will have all the necessary attributes to identify the materials (and configuration) that will be used for the searched item. The BOM used by the ABP system 100 according to a specific embodiment of the present invention is based on attributes. Unlike the BOM in traditional planning systems, the BOM used in accordance with the present invention allows the modeling of material requirements based on selection and rules. The examples provided below will introduce the concept of B OM. In today's automotive industry, for example, it is very common to find the following rule: All cars must have (regardless of other options present) the basic sub-components A, B, and C of the basic group. Car style with sunroof (but no power window) Each car requires a sunroof assembly and 10W motor; car style with power window (but no sunroof) requires a power window assembly and 10W motor; The car style requires a power window assembly, a sunroof assembly, and a 15 W motor. Because of the extra load, higher wattage motors are needed. Note that in this example

-58- (54) (54)200305088-58- (54) (54) 200305088

選擇物的存在或不存在會驅使材料的需求。再者,材料 需求會取決於存在的選擇物之組合。為了使這些需求模型 化較佳而。SAD群組會包含於Bom中。SAD群組可以 是伴隨屬性的布林組合之ι§κυ。 在決定用於規劃的每個訂單之材料組態巾,b〇m扮演 重要的角&amp;。為了使用成品的B〇M,車交佳而纟,會產生 BOM表。ABP系統1〇〇會試圖藉由察看訂單之成品的存貨 、以及使BOM擴大為必要、檢查每種定義的方法,而找 出用於每個耵單的可行配置。如下所決定之用於材料的必 要次要項目(關於說明訂單的每個Sad群組、以及關於訂 單所請求的項目、定義於B0M表中的至少一種方法)通常 需用來製造盯單。對於次要材料,同樣為真,例如,項目 及可用SAD群組可決定用於次要材料,以及關於這些的每 一種之至少一種方法必須用來製造次要項目。在此所稱的 SAD砰組為有關於材料,而不是訂單的sAD群組。 「偏移」可定義用於BOM中的任何項目。在成品SKU 的製造開始之後,此偏移會定義出此項目所需的時間量。 ABP系統1〇〇可確定用於起始成品SKU的製造之交貨時間 將至少總是與用於此成品SKU之BOM中的任何項目之最 長偏移一樣長。 組態實質上是為了製造母項所需之次要項目清單,其可 能是,例如,訂單的物件,或用來製造其他項目的中間項 目。只要至少一種組態的補充是可行的,母項的補充就可 行。當有多種組態,強烈可行性及最適合時,AB P系統1 0 0 • 59- 200305088The presence or absence of choices drives the demand for materials. Furthermore, material requirements will depend on the combination of choices that exist. To better model these requirements. The SAD group will be included in the Bom. The SAD group can be a 林 κυ of the Bollinger combination that accompanies the attribute. In determining the material configuration for each order used for planning, bmm plays an important role &amp;. In order to use the finished BOM, the car is delivered well, and a BOM table will be generated. The ABP system 100 will try to find a feasible configuration for each order by looking at the inventory of the finished product of the order and by expanding the BOM as necessary and checking each definition. The necessary minor items for the material determined as follows (for each Sad group describing the order, and for the items requested for the order, at least one of the methods defined in the BOM table) are usually used to make the mark. The same is true for the secondary materials, for example, the project and the available SAD groups may decide to use the secondary materials, and at least one method for each of these must be used to make the secondary items. The SAD ping group referred to here is the sAD group about materials, not orders. "Offset" can be defined for any item in the BOM. This offset defines the amount of time required for this item after the manufacturing of the finished SKU begins. The ABP system 100 can determine that the lead time for the manufacture of the starting finished SKU will always be at least as long as the maximum offset of any item in the BOM for this finished SKU. A configuration is essentially a list of secondary items needed to make a parent item, which could be, for example, an order item, or an intermediate item used to make other items. As long as at least one configurational supplement is feasible, the parent item can be supplemented. When there are multiple configurations, strong feasibility and most suitable, AB P system 1 0 0 • 59- 200305088

(55) 會提供搜尋及最佳化的二種機制。在強烈可行性中,一旦 系統找出可運作的組態,其會停止可接受組態的搜尋。可 接受組態可定義為在規劃區間[如果沒有最早,(需求曰期 -最早)或規劃範圍起始,如果沒有最晚,(需求日期+最晚 )或規劃範圍結束]内,可完成SAD群組的需求量之一種組 態。在最適合中,系統會搜尋用於SAD群組的所有組態, 並且會選擇有關列入計畫表的目標之最佳組態。較佳而言 ’ ABP系統1 00會使用BOM中的S AD群組,以將屬性為基 礎的材料需求模型化。參照圖8A至8C,其為BOM中之SAD 群組與SKU之間的範例關係之真實顯示。圖8A係顯示用於 丹佛的輪車之「基本」材料清單的方塊圖。因此,在此例 中,BOM包括一種關係(其可使用SAD群組),其定義基本 材料(例如,母項)及相關的次要項目SKU。在此例中,SAD 群組802係由二種SKU屬性所定義,轎車及丹佛。在丹佛 所製造的每部轎車需要某些材料,無論所存在的選擇物或 特性如何。在此例中,這些需要的材料包括次要項目sku 8 0 4至8 0 8,如在丹佛8 0 4的組件A、在丹佛8 0 6的組件B及 在丹佛8 0 8的組件C。在S A D群組8 0 2與其次要項目s K U 804至80 8之間所顯示的關係可視為用於丹佛的轎車之同 程度的一種Β Ο Μ。 圖8Β係顯示另一種ΒΟΜ的方塊圖。在此所敘述的Β〇Μ 係顯示「額外」所需的元件(圖8 A中所顯示之同程度的一 種BOM所需之上述的三種組件元件),如果天窗係配置為 選擇物,但電動窗不是。在圖8B中,SAD群組8 10係由許 -60- 200305088(55) Two mechanisms for search and optimization will be provided. In strong feasibility, once the system finds a working configuration, it stops searching for acceptable configurations. The acceptable configuration can be defined as completing the SAD within the planning interval [if there is no earliest, (demand date-earliest) or the beginning of the planning range, if there is no latest, (demand date + latest) or end of the planning range] A configuration of group demand. In the best fit, the system searches all configurations for the SAD group and selects the best configuration for the targets listed in the plan. More specifically, the ABP system 100 will use the SAD group in the BOM to model attribute-based material requirements. 8A to 8C, which are actual displays of exemplary relationships between SAD groups and SKUs in a BOM. Figure 8A is a block diagram showing a "basic" bill of materials for a Denver wheeler. Therefore, in this example, the BOM includes a relationship (which can use SAD groups) that defines basic materials (for example, parent items) and related secondary item SKUs. In this example, SAD group 802 is defined by two SKU attributes, sedan and Denver. Every car manufactured in Denver requires certain materials, regardless of the choices or characteristics that exist. In this example, these required materials include minor items sku 804 to 808, such as component A in Denver 804, component B in Denver 806, and component C in Denver 808. The relationship shown between the SAD group 8 0 2 and its secondary items KU 804 to 80 8 can be regarded as a kind of β 0 M of the same degree as used for Denver's sedan. Figure 8B shows a block diagram of another BOM. The BOM described here shows the components required for "extra" (the same three types of components required for a BOM of the same degree shown in Figure 8A). If the sunroof is configured as a selection, but the motor The window is not. In Figure 8B, the SAD group 8 10 is controlled by Xu -60- 200305088.

(56) 多屬性來定義,包括「SKU =轎車@丹佛」、「天窗=是」及 「電動窗=否」。SAD群組8 1 0係相關於用於丹佛的天窗組 件及丹佛的10W馬達之次要項目SKU 812及814。次要項目 SKU 812及814為當請求天窗選擇物時,所需要的額外材 料0(56) Multiple attributes to define, including "SKU = Sedan @ 丹佛", "Skylight = Yes" and "Power Window = No". The SAD group 8 1 0 is related to the sunroof components for Denver and the secondary items SKU 812 and 814 of Denver's 10W motor. Minor items SKU 812 and 814 are additional materials needed when sunroof selection is requested.

參照圖8C,其為另一種bom的方塊圖。BOM係顯示「 額外」所需的元件,如果天窗及電動窗皆選擇為選擇物。 SAD群組82〇係由許多屬性來定義,包括「sku =轎車@丹 佛」、天® 一疋」及「電動窗=是」。天窗及電動窗選擇物 的為求會驅使額外材料的需求。在此例中,SAD群組820 係相關於三種次要項目SKU 822至826,丹佛的電動窗組 件、丹佛的天窗組件及丹佛的丨5 W馬達。要注意的是此 BOM會比圖8B中所顯示的B〇M(只需要1〇w馬達)需要更 強力的馬達。這是因為第二方案(亦即,圖8c)有請求電動 窗及天窗選擇物,而在第一方案(㈣,圖8B)中,只有一 種電力消耗選擇物(天窗)的請求。Referring to FIG. 8C, a block diagram of another type of bomb is shown. BOM is a component required to display "extra", if both sunroof and power window are selected as options. SAD group 82 is defined by a number of attributes, including "sku = sedan @ 丹佛", "Sky®", and "power window = yes". The choice of sunroof and power window options drives the need for additional materials. In this example, SAD group 820 is related to three minor items SKU 822 to 826, Denver's power window assembly, Denver's sunroof assembly, and Denver's 5 W motor. It should be noted that this BOM will require a more powerful motor than the BOM (only 10W motor required) shown in Figure 8B. This is because the second scheme (ie, Fig. 8c) has a request for the power window and sunroof options, while in the first scheme (第一, Fig. 8B), there is only one request for the power consumption option (roof).

規劃的關鍵要素為稱為「組態」的概念。組態實質上是 必須用於訂單之次要項目SKU的清單,以製造母sku。組 態的概念可由以下的例子而了解。,於每個SKU而言,有 具有方法清單之對應的BOM ,沪盤 AI ^ ^ 示其可製造的万式。 整個方法疋非常需要的,如^^徐 供烤蛋糕時所需的。再者,當 烘烤時,如果成份短缺,則可以 J以另一種成份來取代一種成 份。BOM記錄中的SAD群組將合法A ^ . m 对曰夬义次要項目何時是可用 的。例如,假設轎車需要1〇w馬 ' ^ ^ ^ . 運,但是具有天窗的轎車 -61 · 200305088A key element of planning is a concept called "configuration." The configuration is essentially a list of secondary item SKUs that must be used for the order to make the parent sku. The concept of configuration can be understood from the following examples. For each SKU, there is a corresponding BOM with a method list, and the Shanghai Stock Exchange AI ^ ^ shows the various ways it can be manufactured. The whole method is very needed, such as ^^ 徐 for baking cakes. Furthermore, when baking, if there is a shortage of ingredients, you can substitute one ingredient with another. The SAD group in the BOM record will be legal when A ^ .m indicates when a secondary item is available. For example, suppose a car needs 10w horses' ^ ^ ^. Transport, but a car with sunroof -61 · 200305088

(57) 需要20 W馬達。母SKU轎車將具有二種BOM記錄,每一種 分別具有指定天窗或不指定天窗,以及2 0 W或1 0 W馬達的 SAD群組。組態告訴我們那些材料需用於那些數量。某人 將會採取方法+補充+取代品,以得到可建造的某事物。 如部份的工作,會達成對於材料的手邊及未來的供應的網 狀系統。例如,假設需要1 0 W馬達,以及有一個在手邊。 單一汽車的訂單可進行及使用它。進行的下個訂單也會需 要10W馬達。為了供應所需的10W馬達,馬達必須補充(購 買)、取代、或完全不規劃訂單,因為不是我們需要的所 有材料是可用的。如果其製造,其通常是次組件,並且此 次組件具有需要各種數量的一組材料。 用於轎車的訂單1可能具有以下組的材料 轎車 1 0 W馬達 用於轎車的訂單2可能具有以下組的材料 橋車 1 0 W馬達 馬達殼 所以關於相同SKU及具有相同使用者定義屬性的二種訂 單可能具有不同組之支援其製造的材料。 如果至少一種組態可在規劃區間内做補充,則訂單為可 行的材料。不同組態可具有不同的材料,因為其在它們之 中,會具有不同的材料及/或數量。當有多種組態(「強烈 可行性」及「最適合」)時,至少二種機制可用於搜尋及 -62- 200305088(57) Requires a 20 W motor. The mother SKU sedan will have two types of BOM records, each with a designated sunroof or unspecified sunroof, and a SAD group of 20 W or 10 W motors. Configuration tells us which materials are needed for those quantities. Someone will take the method + supplement + substitute to get something that can be built. As part of the work, a mesh system for materials on hand and future supply will be achieved. For example, suppose a 10 W motor is needed and one is on hand. Orders for a single car can be made and used. The next order placed will also require a 10W motor. To supply the required 10W motor, the motor must be replenished (purchased), replaced, or not planned at all, because not all the materials we need are available. If it is manufactured, it is usually a subassembly, and this subassembly has a set of materials that require various quantities. Order for cars 1 may have materials for the sedan 1 0 W motor Order for cars 2 may have materials for the sedan bridge 1 0 W motor motor housing This order may have different groups of materials to support its manufacture. If at least one configuration can be supplemented within the planning interval, the order is a viable material. Different configurations can have different materials because they will have different materials and / or quantities among them. When there are multiple configurations ("strongly feasible" and "most suitable"), at least two mechanisms can be used for searching and -62- 200305088

(58) 最佳化。在強烈可行性中,ABP系統1 00會選擇可行的第 一組態,而不會經由所有的另外組態。而搜尋最佳的組態 。反之,在「最適合」中,系統會經由所有組態,而搜尋 出對應的訂單,以及會選擇相關於列入計畫表目標之最佳 配置。在強烈可行性中,一旦可行的組態已決定(「可行 性」係定義如下:訂單的需求量可在需求日期或在需求曰 期之前達成),則ΑΒΡ系統1 00不會搜尋另一種組態。例如 ,假設二種組態(組態1及組態2)可用於訂單j。如果組態1 優先處理,並且發現可用量(訂單」·)=使用需求日期(如果存 在)的組態1之需求量,則AB P系統1 0 0通常不會再察看訂 單』·的組態。換句話說,組態2甚至不會考慮。程序會離開 迴路及處理下個訂單。在最適合中,一旦系統找出可行組 態,其不會停止搜尋。取而代之的是,其會搜尋用於訂單 j的所有組態,並且會選擇有關於列入計畫表目標之最佳 組態。所以組態1及組態2會同時處理。會選擇較佳組態。 組態、訂單與SKU之間的關係係敘述於伴隨圖9的以下 例子中。在此例中,用於訂單的組態(組態1、組態2、以 及類似組態)實質上是一組次要關係。在此例中,訂單』· 900 有二種組態,組態A 902及組態B 904。每種組態為一組次 要項目SKU 906至920。例如,組態A 902為一組次要項目 SKU 906 至9 12,而組態B 904為一組次要項目SKU 914 至920。如果藉由規劃區間的端點,而至少一種組態是可 行的,則訂單」· 9 0 0是可行的。換句話說,如果可找出至少 一種組態(訂單j的組態j),以致於可用量(組態j)=需求量, -63- 200305088 (59) 則訂單」·900是可行的,其中可用量(組態」·)為可使用在最晚 曰期(=需求曰期+最晚)或在最晚曰期前之組態「組態ij) 來補充之數量。在此的「組態j」應該讀取為訂單的「第j 個」組態。對於二種組態之訂單的可用量將是相同的。 只要組態中的所有次要項目(例如,元件材料)是可行的 ,則組態「組態j」是可行的。換句話說,組態「組態j」 係指明是可行的,只要所有的「k」(其中k為用於組態j 中的次要項目之指標)是可行的,可用量(次要項目 SKUjk)=需求量(次要項目SKUjk),Hkm,藉此「η」為中 間材料的數目。用於每種組態的可用量及日期可計算如下 。可用量(組態」·)= ΜΙΝ[可用量(次要項目SKUjk)/拉取量(次 要項目SKUjk),其中對於組態』中的所有次要項目會採用 最小值。可用日期(組態」·)= ΜΑΧ[可用日期(次要項目 SKUjk)+交貨時間(以補充次要項目)-偏移(次要項目 SKUjk)],其中對於組態ij中的所有次要項目會採用最大值 。交貨時間為需要補充項目的時間。例如,假設花五天來 構建元件材料,在此例中的出貨時間將是五天。因此,要 注意的是,在某些情況中,會沒有出貨時間(出貨時間=0) 。簡言之,對於可行的組態而言,就需要的次要項目SKU 而論,到需要次要項目的時候,每種次要項目SKU(亦即 ,元件材料)必須是可行的,並且在此日期時存貨中有足 夠的量,或如果沒有足夠的量,則供應會完全補充,以藉 由製造、購買及/或取代來滿足需求。 經由製造的補充 -64- (60) (60) 200305088 藉由製造的材料補充之後會伴隨參考圖1〇Α及1〇Β中的 流程1 000來做說明。流程1 000為藉由製造的材料補充之流 程。為了經由製造來判斷補充,較佳而言,會輸入某些資 料,如步驟1 0 0 2所顯示。這樣的資料可包括有關於s κ υ 、訂單、補充需求日期、ME(最早)、ML(最晚)參數,以 及補充需求量與最快補充起始(最快補充起始為會發生在 規劃範圍起始之前的日期)。例如,假設在星期一(第丨)完 成用於星期一(第8)的規劃。進一步假設規劃者在星期三(第 3)發表計畫表’並且在星期四(第4)開始計算補充起始, 取代星期一(第8)。在此例中,補充起始將會設定為取代 星期一(第8)的星期四(第4)。程序(如圖i〇A及10B所繪示) 會產生輸出,其顯示在最後可接受日期(需求日期+ML)或 在最後可接受日期之前,可經由製造(補充可用量)來補充 數量,此日期為補充可用量是可用的,以及旗標係表示 10 0 %的補充需求量是否在最後可接受曰期(需求曰期 + ML)或在最後可接受日期之前,可經由製造來滿足。 在步驟1 0 0 5中,會產生基於有關於規劃訂單的曰期之可 用SAD群組的清單❶因此,在決定可用的SAD群組中,ABP 系統1 0 0會再檢查應用於訂單之Β Ο Μ中的所有S A D群組, 並且只會選擇可用的那些SAD群組。為了產生可用的SAD 群組之清單,ABP系統1〇〇首先會決定用於具有屬性的 SKU之ΒΟΜ中的所有SAD群組。例如,假設規劃的訂單可 由某些屬性而定義如下:轎車@亞特蘭大、天窗=是、電 動窗=是。基於訂單,訂單之相關的BOM可識別出來。此 -65- (61) (61) 200305088(58) Optimization. In the strong feasibility, ABP system 100 will choose the feasible first configuration without going through all the other configurations. And search for the best configuration. Conversely, in the "best fit", the system searches through all configurations to find the corresponding order, and selects the best configuration related to the target included in the schedule. In the strong feasibility, once the feasible configuration has been determined ("feasibility" is defined as follows: the demand for the order can be reached on the demand date or before the demand date), the ABP system 100 will not search for another group state. For example, suppose two configurations (Configuration 1 and Configuration 2) are available for order j. If configuration 1 is prioritized and the available quantity (order) is found = the demand of configuration 1 using the demand date (if it exists), then the AB P system 1 0 0 usually does not look at the order again. . In other words, configuration 2 is not even considered. The program leaves the loop and processes the next order. In the best fit, once the system finds a feasible configuration, it does not stop searching. Instead, it searches all configurations for order j, and selects the best configuration for inclusion in the schedule target. So configuration 1 and configuration 2 will be processed at the same time. A better configuration will be selected. The relationship between configuration, order, and SKU is described in the following example accompanying Figure 9. In this example, the configuration used for the order (Configuration 1, Configuration 2, and similar) is essentially a set of secondary relationships. In this example, the order "900" has two configurations, configuration A 902 and configuration B 904. Each configuration is a set of minor items SKUs 906 to 920. For example, configuration A 902 is a set of secondary items SKUs 906 to 9 12 and configuration B 904 is a set of secondary items SKUs 914 to 920. If at least one configuration is possible by planning the endpoints of the interval, the order "900" is feasible. In other words, if at least one configuration (configuration j of order j) can be found, so that the available quantity (configuration j) = demand, -63- 200305088 (59) then the order "· 900 is feasible, The available quantity (configuration) · is the quantity that can be supplemented by using the configuration "configuration ij" at the latest date (= demand date + latest) or before the latest date. Configuration "j" should be read as the "jth" configuration of the order. The available quantities for the two configuration orders will be the same. As long as all minor items in the configuration (for example, component materials) are feasible, configuring "configuration j" is feasible. In other words, the configuration "configuration j" indicates that it is feasible, as long as all "k" (where k is an indicator for the secondary items in configuration j) are available, the available amount (secondary items SKUjk) = demand (secondary item SKUjk), Hkm, with "η" as the number of intermediate materials. The available quantity and date for each configuration can be calculated as follows. Available amount (configuration) · ΜΙΝ [Available amount (secondary item SKUjk) / Pull amount (secondary item SKUjk), where the minimum value is used for all secondary items in the configuration. Available Date (Configuration) ·) = ΜΑχ [Available Date (SKUjk for minor items) + Delivery time (to supplement minor items)-Offset (SKUjk for minor items)], where for all times in configuration ij Major items will take the maximum. Delivery time is the time when the supplementary item is needed. For example, suppose it takes five days to build the component material, and in this example the shipping time will be five days. Therefore, it is important to note that in some cases there will be no shipping time (Shipping Time = 0). In short, for a viable configuration, in terms of the required secondary project SKUs, each secondary project SKU (that is, component material) must be feasible by the time a secondary project is needed, and There is sufficient quantity in inventory at this date, or if there is not enough quantity, the supply will be fully replenished to meet demand by manufacturing, buying, and / or replacing. Supplement by manufacturing -64- (60) (60) 200305088 Supplemented by the manufactured material will be explained with reference to the flow 1000 in FIGS. 10A and 10B. Process 1000 is a process that is supplemented by manufactured materials. In order to judge the replenishment through manufacturing, it is preferable to enter certain information, as shown in step 10 02. Such information may include information about s κ υ, order, supplementary demand date, ME (earliest), ML (latest) parameters, as well as the demand for supplements and the fastest start of supplements (the fastest start of supplements will occur during planning The date before the start of the range). For example, suppose that the planning for Monday (8th) is completed on Monday (8th). It is further assumed that the planner publishes the schedule sheet on Wednesday (3rd) and starts calculating the supplementary start on Thursday (4th) instead of Monday (8th). In this example, the supplementary start will be set to replace Thursday (4th) instead of Monday (8th). The program (shown in Figures 10A and 10B) produces an output that shows the last acceptable date (demand date + ML) or before the last acceptable date, the quantity can be replenished by manufacturing (replenishing the available amount) This date is available for replenishment availability, and the flag indicates whether 100% of replenishment demand is at the last acceptable date (demand date + ML) or can be met by manufacturing before the last acceptable date. In step 1 0 05, a list of available SAD groups based on the date of the planned order is generated. Therefore, in determining the available SAD groups, the ABP system 1 0 0 will check the B applied to the order. All SAD groups in OM, and only those SAD groups that are available. In order to generate a list of available SAD groups, the ABP system 100 will first decide on all SAD groups in the BOM of the SKU with attributes. For example, suppose a planned order can be defined by certain attributes as follows: sedan @ 亚特兰大, sunroof = yes, electric window = yes. Based on the order, the relevant BOM of the order can be identified. This -65- (61) (61) 200305088

概念可參考以下的例子而最佳的顯示出來。參照圖丨〇C到 10F ’其输不四種不同的b〇m組。圖1〇(:係顯示用於轎車@ 亞特蘭大之「基本」的一種同程度的bom。此BOM組可 視為用於橋車之「基本」的一種同程度的B〇M,無論選 擇的選擇物如何(必須有組件)。因此,在此B 〇M組中的 SAD群組只是「SKU =轎車@亞特蘭大」。圖1〇Ε&gt;係顯示第 一種Β Ο Μ組。此組係顯示額外需要的元件,如果天窗係 配置為選擇物,但不是電動窗。所以,在第二組中的SAD 群組為「SKU =轎車@亞特蘭大、天窗=是及電動窗=否」 。當然,為了真正產生由圖1〇D中的SAD群組所定義的轎 車’除了繪示於第二組(亦即,圖丨〇D)中的次要項目sku 之外,繪示於第一 Β OM組(亦即,圖1 〇 c)中的所有次要項 目SKU將是需要的。圖10E為第三種bom組,其顯示額外 需要的元件,如果電動窗係配置為選擇物,但不是天窗。 關於此組中的SAD群組為「SKU =轎車@亞特蘭大及天窗= 否及電動窗=是」。最後的BOM組(如繪示於圖1〇F),係顯 示額外需要的元件,如果天窗及電動窗係選擇為選擇物。 關於第四組中的SAD群組為「SKU =轎車汾四&amp; # 卞㊇兑特蘭大及天 窗=是及電動窗=是」。要注意的是,繪示於圖i〇D到i〇f 中之第二、第三及第四SAD群組中的每一個仍然需要(圖 10C的)基本BOM的次要項目SKU。 因此,在這四組中’只有一及四組中的Sad群組會敘述 具有屬性的輸入訂單(亦即’當第一 SAD群組的屬性沒有 任何屬性與具有屬性的輸入訂單之屬性衝突時,第四sad -66- (62) (62)200305088 群、’且的屬性會真正地與具有屬性的輸入訂單之屬性匹配) 。要注意的是,訂單會使存在於SKU或項目上的屬性重疊 、致於使用者總疋必須察看訂單,而不必察看s κ u或項 目 因此’在步驟1005,合格的SAD群組之清單會產生。 在此例中,在步驟1 〇〇5所產生的清單將只包括第一及第四 SAD群組。在SAD群組清單中之SAD群組的總數為p且 。在步驟1 005中所找出的所有SAD群組會經由保持 步驟做處理,依序使用迴路,直到ABP系統1〇〇找出滿足 二種條件中的一個之「SAD群組i」: 〇)可用量(SAD群組i) = 0,這意謂在(需求曰期+ML)或 在(需求日期+ML)之前,SAD群組中的一個具有零可用 性。一旦出現可用量=0,不需要再處理清單中的SAD 群組;或 (2)i = :P,這意謂系統經由清單中的所有母SAD群組做環 繞。 在步騾1010,ABP系統100會擷取清單中的第一(或下一 個)sad群組做處理。因此,在sad群組之清單中的指標 lj會以1來增加(亦即,i — i+l)。接著,ABP系統100會 基於步騾1 〇 i 5中所規劃的訂單,而擷取用於選擇的SAD 群組之所有的BOM組態。這是因為SAD群組將不包含訂單 的所有屬性。因此,為了得到適合的BOM,ABP系統1 〇〇 會祭看原始的訂單。為了解釋的目的,「組態U」係定義 4用於「SAD群組」之組態清單中的第j個組態,並且在 /月單中的組態總數為q ,其中l£j£_Q。組態總.是特定於訂 -67- 200305088 (63) 單,因為訂單具有會不存於SKU/項目中的屬性,或訂單 屬性會使存在於SKU/項目中的屬性重疊。在步驟1 020中 ,系統會擷取用於「母SAD群組i」之組態清單中的下個 組態,做進一步的處理。同樣地,在組態清單中的指標「 j」會以1來增加(亦即,j — j + 1)。 如上所述,每種組態實質上是需要的次要項目之清單, 以製造母項。只要至少一種組態的補充是可行的,則母項 的補充是可行的。因此,在步騾1 0 2 5中,AB P系統1 0 0會 產生用於組態ij之次要項目的集合,並且在步騾1 030中, 會擷取用於「組態i j」之次要項目清單中的下個次要項目 ,做進一步的處理。在較佳具體實施例中,其代表組態清 單上的「k」。亦即,「次要項目SKUijk」係表示用於「組態…· 」之次要項目清單中的第k個次要項目。在清單中之次要 項目的總數為R且1 。以相似的方式,在步驟1 〇 3 0中 ,在組態清單上的指標「k」會以1來增加(亦即,kek+1)。 然後在步驟1 03 5中,ABP系統100會藉由複製訂單的屬 性[較佳而言,次要項目會複製到訂單。次要項目SKU(如 包含於組態中)可暫時增加屬性至訂單。當下個組態進行 時,組性必須儲存於訂單上。]及計算用於次要項目之需 求日期及需求量,而準備次要項目SKU。此步驟會要求 ABP系統100優先選用相關於「訂單」與「次要項目SKUjk 」之間的BOM關係之拉取量、偏移及複製指令。拉取量 為每單位項目搜尋(例如,母單元)所需要的元件材料(例 如,次要項目SKU)量。例如,對於汽車的訂單,頭燈的 -68- (64) (64)200305088The concepts can be best shown with reference to the following examples. Referring to Figs. 10C to 10F ', it is not possible to lose four different groups of bm. Figure 10 (: shows a kind of bom for the "basic" of the car @ Atlanta. This BOM group can be regarded as a kind of bom for the "basic" of the bridge, regardless of the choice How (must have components). Therefore, the SAD group in this B OM group is just "SKU = Sedan @ 亚特兰大". Figure 10E &gt; shows the first type of ΒOM group. This group shows additional requirements Components, if the sunroof is configured as a selection, but not a power window. Therefore, the SAD group in the second group is "SKU = sedan @ 亚特兰大, skylight = yes and power window = no". Of course, in order to really The sedan 'defined by the SAD group in FIG. 10D is shown in the first group B (in addition to the secondary item sku in the second group (ie, FIG. That is, all minor item SKUs in Fig. 10c) will be needed. Fig. 10E is the third bom group, which shows additional required components, if the power window system is configured as a selection, but not a sunroof. About this The SAD group in the group is "SKU = Sedan @Atlanta and Skylight = No and Power Window = Yes" The last BOM group (as shown in Figure 10F) shows the additional required components. If the sunroof and power window system are selected as options, the SAD group in the fourth group is "SKU = Sedan Fensi &amp";# 卞 ㊇ 威特兰 大 and skylight = yes and power window = yes ". Please note that the second, third, and fourth SAD groups shown in Figures iOD to if Each still requires a secondary item SKU of the basic BOM (of FIG. 10C). Therefore, among these four groups, 'only one and four of the Sad groups will describe input orders with attributes (ie, when the first SAD When the attributes of the group do not conflict with the attributes of the input order with attributes, the attributes of the fourth sad -66- (62) (62) 200305088 group, and the attributes will actually match the attributes of the input order with attributes) It should be noted that the order will cause the attributes existing on the SKU or item to overlap, so that the user always has to look at the order instead of looking at s κ u or the item. Therefore, at step 1005, the list of qualified SAD groups Will produce. In this example, the list produced in step 1005 will only include The first and fourth SAD groups. The total number of SAD groups in the SAD group list is p and. All SAD groups found in step 1 005 will be processed through the holding step, using the loop in sequence until The ABP system 100 finds the "SAD group i" that satisfies one of two conditions: o) the available amount (SAD group i) = 0, which means either at (demand date + ML) or at (demand Date + ML), one of the SAD groups has zero availability. Once the available quantity = 0, there is no need to process the SAD group in the list; or (2) i =: P, which means that the system loops through all the parent SAD groups in the list. In step 1010, the ABP system 100 retrieves the first (or next) sad group in the list for processing. Therefore, the index lj in the list of sad groups is increased by 1 (that is, i — i + 1). Then, the ABP system 100 will retrieve all BOM configurations for the selected SAD group based on the order planned in step 10i. This is because the SAD group will not contain all attributes of the order. Therefore, in order to get a suitable BOM, the ABP system 1000 will look at the original order. For the purpose of explanation, "Configuration U" is definition 4 for the j-th configuration in the configuration list of "SAD Group", and the total number of configurations in the / monthly bill is q, where l £ j £ _Q. The configuration total is specific to the order -67- 200305088 (63) because the order has attributes that would not exist in the SKU / project, or the order attributes would cause attributes that exist in the SKU / project to overlap. In step 1 020, the system will retrieve the next configuration from the configuration list for "parent SAD group i" for further processing. Similarly, the index "j" in the configuration list is increased by 1 (that is, j — j + 1). As mentioned above, each configuration is essentially a list of secondary items needed to make the parent item. As long as at least one configuration complement is feasible, the parent supplement is feasible. Therefore, in step 1025, the AB P system 1 0 0 will generate a set of secondary items for configuring ij, and in step 1 030, it will retrieve the The next minor item in the list of minor items for further processing. In the preferred embodiment, it represents "k" on the configuration list. That is, the "secondary item SKUijk" means the k-th secondary item in the list of secondary items used for "configuration ...". The total number of secondary items in the list is R and 1. In a similar manner, in step 1030, the index "k" on the configuration list is increased by 1 (that is, kek + 1). Then in step 1 305, the ABP system 100 will copy the attributes of the order [preferably, the secondary items will be copied to the order. Secondary item SKUs (if included in the configuration) can temporarily add attributes to the order. When the next configuration is performed, the group must be stored on the order. ] And calculate the demand date and demand for the secondary item, and prepare the secondary item SKU. This step will require the ABP system 100 to preferentially select the pull amount, offset, and copy instructions related to the BOM relationship between the "Order" and the "Minor Item SKUjk". Pull Amount The amount of component material (for example, secondary item SKU) required to search (for example, the parent unit) per unit item. For example, for a car order, -68- (64) (64) 200305088 for headlights

拉取I為一個。根據本發明之具體實施例,需求日期。欠 要項目SKUjk)可藉由以下的方程式計算出來·· 需求日期=補充需求日期·交貨時間(母SAD群 組j) +偏移(次要項目SKUijk) 需求量可計算如下: 需求量(次要項目SKUijk)=補充需求量x拉取量(次 要項目SKUijk) 較佳而P ,叮單的選擇屬性及/或具有屬性的輸入 及/或對應具有屬性的輸入SKU之項目會複製到使用BOM 士上的複製指令之次要項目SKUijk。複製指令係用來使訂 單/母SKU/母項目的相關屬性傳播到次要項目SKU。複製 々曰令會區分什麼屬性需要複製。 在步驟1 03 5的程序之後,ABp系統1〇〇會輸出具有相關 屬性的次要項目SKUijk(由具有ATtribSijk的次要項目sku 來匕表示)。爲求量及需求日期也可由以上的計算得知。 、,曰使用複製指令,以使適當屬性傳播到次要項目,如激 增的材料清單。需要將適當屬性傳播到較低準位的次要項 目,以找出存貨及補充正確的次要材料。複製指令的一例 現將參考圖10G做說明,其繪示B〇M,其中項目名稱係顯 丁於圓括號内。如顯示,此清單為以屬性為基礎之清單。 =疋所顯示之所有的母·子關係都可用於路由器A的每個 玎單。例如,只有客戶已選擇「介面型式=4埠」,由「A 」(在路由器-A與4P-IMOD之間)所代表的8(^關係才是正 確的。同樣地,只有客戶已選擇「介面型式=8埠」及「記 -69- 200305088Pull I for one. According to a specific embodiment of the invention, the demand date. The undesired item SKUjk) can be calculated by the following equations: · Demand date = Supplementary demand date · Delivery time (parent SAD group j) + offset (secondary item SKUijk) The required amount can be calculated as follows: Minor item SKUijk) = supplementary demand x pull amount (minor item SKUijk) is better and P, the selection attribute of the single list and / or input with attribute and / or the item corresponding to the input SKU with attribute will be copied to Use the secondary item SKUijk of the copy instruction on the BOM. The copy instruction is used to propagate the related attributes of the order / parent SKU / parent item to the secondary item SKU. Copying The 々command distinguishes what attributes need to be copied. After the procedure of step 105, the ABp system 100 will output a secondary item SKUijk (represented by a secondary item sku with ATtribSijk) with related attributes. The quantity and demand date can also be known from the above calculation. Use copy instructions to spread the appropriate attributes to secondary items, such as a surge in bill of materials. Appropriate attributes need to be propagated to lower-level secondary items to find inventory and replenish the correct secondary material. An example of a copy instruction will now be described with reference to FIG. 10G, which shows BOM, where the project name is shown in parentheses. If shown, this list is a property-based list. = 疋 All the parent-child relationships shown can be used for every order on Router A. For example, only if the customer has selected "Interface Type = 4 Ports", the 8 (^) relationship represented by "A" (between router-A and 4P-IMOD) is correct. Similarly, only the customer has selected " Interface Type = 8 Ports "and" Note-69- 200305088

憶體=128MB」,由「E」所代表的BOM關係才是交叉的。 如以上所提及,屬性相依係使用母SAD群組來模型化。 因此,圖1 0E中之每個BOM關係的複製指令係顯示於下表 I中。 圖中的參考號 母SAD群組 次要項目 複製指令 A 「項目=路由器A」及「介面=4埠」 4P-IMOD 從屬性=記憶體, 至屬性=記憶體, 至值=「」 B 「項目=路由器A」及「介面=8埠」 8P-IMOD 屬性,至屬性=記憶體 ,至值=「」 C 「項目=4P-IMOD」及「記憶體=128MB」 MEM-128 未複製屬性 D 「項目=4P-IMOD」及「記憶體=256MB」 MEM-256 未複製屬性 E 「項目=8P-IMOD」及「記憶體=128MB」 MEM-128 未複製屬性 F 「項目=8P-IMOD」及「記憶體=256MB」 MEM-256 未複製屬性 G 「項目=路由器A」 ASSY-主 未複製屬性 Η 「項目=ASSY·主要」 Cl 未複製屬性 I 「項目= ASS 丫主要」 C2 未複製屬性Memories = 128MB ", the BOM relationship represented by" E "is cross. As mentioned above, attribute dependence is modeled using the parent SAD group. Therefore, the copy instruction for each BOM relationship in FIG. 10E is shown in Table I below. Reference number in the figure: Primary SAD group secondary item copy instruction A "item = router A" and "interface = 4 ports" 4P-IMOD from attribute = memory, to attribute = memory, to value = "" B " Item = Router A "and" Interface = 8 Ports "8P-IMOD attribute, to attribute = memory, to value =" "C" item = 4P-IMOD "and" memory = 128MB "MEM-128 unreplicated attribute D "Item = 4P-IMOD" and "memory = 256MB" MEM-256 unreplicated attribute E "item = 8P-IMOD" and "memory = 128MB" MEM-128 unreplicated attribute F "item = 8P-IMOD" "Memory = 256MB" MEM-256 Unreplicated attribute G "Project = Router A" ASSY-Master unreplicated attribute Η "Project = ASSY · Main" Cl Unreplicated attribute I "Project = ASS ASS Primary" C2 Unreplicated attribute

表I 假設有需求在10星期期内之50單位的路由器-A之訂單 ,並且此訂單具有組態選擇物:1)介面==8 -埠;以及2)記 憶體1 2 8 MB。進一步假設系統中之各種零件的存貨位置 係如以下的表11。 -70- 200305088 (66)Table I assumes that there is an order for 50 units of Router-A within a 10-week period, and this order has configuration options: 1) interface == 8-port; and 2) memory 1 2 8 MB. It is further assumed that the inventory locations of various parts in the system are as shown in Table 11 below. -70- 200305088 (66)

項目/SAD群組 __一 存貨 項目=路由器-A及 介面=8 璋及 記憶體=128 MB __. 25 項目=路由器-A及 50 介面=4 -淳及 記憶體=128 MB 一__. ASSY·主要 50 MEM-128 10 項目=8P-IMOD及 20 記憶體=128 MB 項目=8P-IMOD及 30 記憶體=256 MB _Item / SAD group__One inventory item = router-A and interface = 8 璋 and memory = 128 MB __. 25 items = router-A and 50 interface = 4-chun and memory = 128 MB one__. ASSY · Main 50 MEM-128 10 items = 8P-IMOD and 20 memory = 128 MB items = 8P-IMOD and 30 memory = 256 MB _

表II 假設所有零件具有相同的出貨時間=1星期,並且沒有 配置用於系統中的任何部份之取代品。假設在丨0星期前, 需要具有介面=8-埠及記憶體Η 28MB之50單位的路由器 -A,以及具有8-埠介面模組及128ΜΒ&amp;憶體之25單位的路 由器-Α在手邊是可用的’這意謂只需要25單位。因此, 這需要25單位的r〇uter_a具有介面+槔及記憶體 叫2議的路由器·Α會轉移到用於所有的中間取代品之 (25單位,9星期的)相依需求。 從ΒΟΜ表中,可々 士 J知,、有二種母SAD群組Β及G會應用到 •71 - 200305088Table II assumes that all parts have the same shipping time = 1 week and that no replacement is configured for any part of the system. Assume that 0 weeks ago, you need a router-A of 50 units with interface = 8-port and memory Η 28MB, and a router of 25-unit with 8-port interface module and 128MB &memory; 'Available' means that only 25 units are needed. Therefore, this requires 25 units of Router_a with an interface + 槔 and a router called Memory 2A. It will be transferred to the intermediary demand for all intermediate replacements (25 units, 9 weeks). From the BOM table, you can see that J has two parent SAD groups B and G that will be applied to • 71-200305088

(67) 具有介面=8-埠及記憶體=1 28MB的路由器- A」,其中群 組B的次要項目sfCu為8P-IMOD,而群組g的次要項目SKU 為ASSY-主要。因此,ABP系統1〇〇會試圖找出用於這二 種次要項目之供應的來源。找出供應可藉由可用的淨存貨 或藉由製造這些零件來達成。其係藉由以下來說明·· (1) 從群組G中找出供應:群組G為標準組件,其位於配 置於路由器上之與路由器無關的選擇物中。因此,當尋找 存#或補充的A S S Y-主要時,不需要知道關於此群組之訂 單的特定屬性。從表II中,可知具有ASSY-主要的母SAD 群、、且具有5 0單位的存貨’這足以應付2 5單位的需求。因此 ’在9星期内,次要項目ASSY-主要是可行的。 (2) 從群組B中找出供應:從表π中,關於「項目 = 8P-IM0D及記憶體=128MB」及「項目=8p_IM〇D及記憶 體=256MB」,分別有20單位的存貨及3〇單位的存貨。如以 上所提及,在此群組中的存貨係藉由屬性來做區別。雖然 在手邊有全部50單位的8-埠介面模組是可用的,但是不是 全邵都可得到滿足需求。在手邊只有2〇單位是可用的,以 及有其餘5單位的需求。在B〇M表中使用複製指令可使其 餘的5單位達成。複製指令會沿著B 〇M準位複製屬性,但 是不會幫助我們解決存貨短缺。 在表I中,母SAD群組係顯示複製指令為「從屬性=記憶 體、至屬性=記憶體、至值=「」」。複製指令的解讀為: 將記憶體屬性傳送到次要項目SKU,以及將訂單之記 屬性的值複製到次要項目SKU的記憶體屬性」。“= -72· 200305088(67) Router with interface = 8-port and memory = 1 28MB-A ", where the secondary item sfCu of group B is 8P-IMOD, and the secondary item SKU of group g is ASSY-main. Therefore, ABP System 100 will try to find the source of supply for these two minor projects. Finding supply can be achieved through the available net inventory or by manufacturing these parts. It is explained by the following: (1) Find out the supply from group G: Group G is a standard component, which is located in a router-independent option placed on the router. Therefore, when looking for deposit # or supplementary A S S Y-primary, there is no need to know the specific attributes of the order for this group. From Table II, it can be seen that there is an ASSY-main female SAD group, and an inventory of 50 units' is sufficient to meet the demand for 25 units. So ’in 9 weeks, the secondary item ASSY- is mostly feasible. (2) Find out the supply from group B: From Table π, there are 20 units of inventory for "item = 8P-IM0D and memory = 128MB" and "item = 8p_IM0D and memory = 256MB". And 30 units of inventory. As mentioned above, the inventory in this group is distinguished by attributes. Although all 50-unit 8-port interface modules are available at hand, not all of them are available. Only 20 units are available at hand, and there is demand for the remaining 5 units. Using the copy instruction in the BOM table can achieve the remaining 5 units. The copy instruction will copy attributes along the BOM level, but it will not help us to solve the inventory shortage. In Table I, the parent SAD group shows that the copy command is "from attribute = memory, to attribute = memory, to value =" "". The interpretation of the copy instruction is: transfer the memory attributes to the secondary item SKU, and copy the value of the order record attribute to the memory attributes of the secondary item SKU ". "= -72 · 200305088

(68) 到訂單,而未複製到SKU。此運作的輸出為次要物件,亦 即,「具有屬性的次要項目SKU」。在此例中,次要項目SKU 為8P-IMOD,而次要項目物件為「具有記憶體128 MB之 8 0-IMOD」。接著,對次要項目物件的存貨檢查會藉由將 存貨的屬性對次要項目物件的屬性匹配而達成。因為手邊 已有2 0單位,所以ab P系統1 0 0需要補充5單位的次要項目 物件「具有記憶體128 MB之8P-IMOD」。從表I中可發現母 S AD群組e滿足需求,因為此群組具有次要項目sKU「 8P-IMOD」。此外,群組E的複製指令為「未複製屬性」, 這意謂不會複製屬性。因此,在檢查表Π之後,會發現^ 目/SAD群組「MEM· 128」在手邊有10單位,這足以應付s 單位的其餘需求。 根據以上所提及之供應方法,在步驟1 040中,ABP系統 100會得到用於次要項目SKU的供應,以及會呼叫用於具 有AttribSijk的次要項目SKU之獲得供應方法。步驟1〇4〇 的輸出為可用量(具有AttribsUk的次要項目SKU)及可用 日期(具有AttribSijk的次要項目SKU)。 然後ABP系統100會藉由以上步驟所決定的輸出,來更 新可用日期及可用量,如顯示在步驟1 045中。根據本發曰月 ,更新可由以下的方式來達成: 可用日期(組態ij)=最大(Max)[可用日期(次要項目 SKUijk)+出貨時間(母SAD群組)一偏移(次要項目 SKUijk),可用曰期(組態U)] 量(組態u)=最小(Min)[可用量(次要項目SKUijk)/ -73- 200305088 (69) 拉取量(次要項目SKUijk),可用量(組態ij)] 此外,可行旗標的決定係藉由:(68) to order without copying to SKU. The output of this operation is a secondary object, that is, a "secondary item SKU with attributes". In this example, the secondary item SKU is 8P-IMOD, and the secondary item object is "80-IMOD with 128 MB of memory". Next, the inventory check of the secondary item object is achieved by matching the attributes of the inventory to the attributes of the secondary item object. Since there are already 20 units on hand, the ab P system 1 0 0 needs to add 5 units of minor items. The object is "8P-IMOD with 128 MB of memory". From Table I, it can be found that the parent S AD group e meets the demand, because this group has the secondary item sKU "8P-IMOD". In addition, the copy instruction of group E is "unreplicated attribute", which means that the attribute is not replicated. Therefore, after checking the table Π, it will be found that the ^ head / SAD group "MEM · 128" has 10 units on hand, which is enough to meet the remaining demand of s units. According to the supply method mentioned above, in step 1 040, the ABP system 100 will obtain the supply for the secondary item SKU, and will call the supply method for the secondary item SKU with AttribSijk. The output of step 104 is the available amount (with a minor item SKU with AttribsUk) and the available date (with a minor item SKU with AttribSijk). The ABP system 100 then updates the available date and the available quantity with the output determined by the above steps, as shown in step 1 045. According to the month of this issue, the update can be achieved in the following ways: available date (configuration ij) = maximum (Max) [available date (secondary item SKUijk) + shipping time (parent SAD group)-an offset (second To the item SKUijk), the available date (configuration U)] amount (configuration u) = minimum (Min) [available amount (secondary item SKUijk) / -73- 200305088 (69) pull amount (secondary item SKUijk ), Available quantity (configuration ij)] In addition, the determination of feasible flags is made by:

3:行旗標(組態ij) =是(YES),如果以下的條件F (a) 可用曰期(組態{」)&lt;補充需求曰期及 (b) 可用量(組態ij) =補充需求量。 或,可行旗標(組態ij)==否。 在步驟1 050中,ABP系統1〇〇會檢查組態可用 零相等。如果如此,系統將不會再察看此組態中 目,並且程序會回到步驟1 〇 2 0,以得到下個組声J 果否,則在步驟1 0 5 5中,系統會在此清單中,繼 否有更多的次要項目。 如果在目前的組態清單中,有更多的次要項 k&lt;R),則程序會到步驟1 〇30,以從清單中擷取下 目(kek+Ι),否則會到步驟ι〇6〇,以決定組態搜4 根據本發明之一較佳具體實施例,當有多種 AB P系統1 〇 〇會提供用於搜尋及最佳化的二種機 機制稱為「強烈可行」,而另一種稱為「最適合 可行中,(圖10A及10B的)程序會選擇可行的第 疋義為用於母SAD群組的需求量可在需求曰期 曰期(前達成)。在最適合中,即使系統找出可 ABP系統1〇〇將不會停止搜尋。取而代之的是, 1 〇〇會經由所有組態,而搜尋母sAD群組及選擇 畫表目標的取佳組態。如果搜尋機制為強烈可^ 步驟1 065中,程序會判斷是否組態可行旗標會表 時滿足: 量是否與 的次要項 ^清單。如 續檢查是 目(亦即, 個次要項 春機制。 組態時, 制。一種 」°在強烈 一組態( 或在需求 行組態, ABP系統 相關於計 ί型式,在 -示組態是 -74- 200305088 (70) 可行的。然而,如果搜尋機制為最適合型式,程序會到步 驟1 0 7 0,其中AB P系統1 0 0會記住到目前為止已找出的最 佳組態。在步驟1 090中,會判斷是否有用於目前母SAD 群組之較多的組態。如果有較多的組態,則程序會回到步 驟1 0 2 0 ’以得到下個組態。在步驟1 〇 6 5中,會做出關於是 否可行組態已找出的判斷[如由可行旗標(組態i』·)來表示] 。如果可行旗標表示已找出可行組態,則在步騾i 〇7 5 , ABP系統1〇〇會基於強烈可行型式機制,而選擇目前的組 態當作最佳組態,然後會到步驟1 〇 8 如果沒有可行旗標 ’這意謂到目前為止還未找出可行組態(依照強烈機制) ’然後AB P系統1 〇 〇會到步驟1 〇 7 〇,並且會記住到目前為 止的最佳組態(然而,因為會選擇強烈機制,所以到目前 為止所檢查的組態沒有一個是可行的)。然後程序會移到 步驟1 090,以檢查訂單上是否有較多的組態。如果訂單上 有較多的組態,則程序會返回到步驟1 〇2〇,以評估及處理 可單上的下個組態。否則,如果訂單上沒有較多的組態, 則程序也會移到步驟1 080,其中系統會計算及更新用於目 則組態之可用日期及可用量。在此具體實施例中,目前母 SAD群組的可用日期為最佳組態的可用日期,而可用量為 最佳組態的可用量。 然後在步驟1 08 5中,ABp系統1〇〇會更新補充可用曰期 即補充可用量。根據本發明的一較佳具體實施例,補充町 用日期為在用於目前母SAD群組的可用日期與目前補充 可用日期之間之較大的一個β補充可用量為在用於目前母 -75- 200305088 (71) SAD群組的可用量與目前補充可用量之間之較小的一個 。補充旗標=是,只有同時滿足以下的二種條件:1)補充 可用日期S補充需求日期+ML ;以及2)補充可用量=補充需 求量。 在步驟1 092中,會判斷在步驟1〇85後之計算過的補充可 用量是否與零相等。如果其不為零,則不需要再處理用於 目前組態的SKU,以及程序會移到步驟1〇96,其中ABP系 統100會返回(亦即,輸出)補充可用日期、補充可用量及 補充可行性,並且會藉由步驟1 〇 9 8的製造程序而結束補充 。如果在步驟1 092,補充可用量判斷為零,則ABP系統100 會檢查BOM 1094上是否有更多的方法。如果有更多的, 則步驟1 0 1 0的系統會擷取下個母方法(亦即,S AD群組), 來做處理。否則,在步驟1 0 9 6,系統會離開此B 〇 μ方法 ,並且返回補充可用日期、補充可用量及補充可行旗標。 然後在1 0 9 8,程序1 0 0 0會結束。 經由購買的捕籴 參照圖11,其為藉由購買而做補充之一般的流程1 〇 9 4 (如 由圖6的步驟610所表示)。程序會藉由試圖將補充需求量 規劃成沿著時間線之可用的時間桶狀區間,而產生輸出。 此輸出可以是數量及/或品質報告的形式。在步驟11〇2 , 當相關資料開始輸入及/或擷取及/符合語法時,程序會開 始。相關資料可例如包括有關於訂單物件的屬性,以及如 補充需求量、補充需求曰期、最早(ME)、最晚(ml)、時 間桶裝區間的長度、週期最大值、以及類似之物之時序資 -76- 2003050883: line flag (configuration ij) = yes (YES), if the following conditions F (a) available date (configuration {") &lt; supplementary demand date and (b) available quantity (configuration ij) = Supplementary demand. Or, the feasible flag (configuration ij) == no. In step 1 050, the ABP system 100 checks that the configuration available is equal to zero. If so, the system will no longer look at this configuration, and the program will return to step 1020 to get the next group sound. If no, then in step 1 0 55, the system will There are no more secondary items in China. If there are more secondary items k &lt; R) in the current configuration list, the program will go to step 1030 to retrieve the item (kek + 1) from the list, otherwise it will go to step ι〇6 〇, to determine the configuration search 4 According to a preferred embodiment of the present invention, when there are a variety of AB P system 100 will provide two types of mechanisms for searching and optimization is called "strongly feasible", and The other is called "the most suitable and feasible, (of Figs. 10A and 10B). The procedure will choose the feasible meaning of the requirement that the demand for the parent SAD group can be reached before the demand date (before). In the system, even if the system finds that the ABP system 100 will not stop searching. Instead, 100 will go through all configurations and search the parent sAD group and select the best configuration for drawing table targets. If you search The mechanism is strongly ^ In step 1 065, the program will determine whether the configuration of the feasible flag meeting table meets: the list of minor items that are equal to the amount of the list. If you continue to check the item (ie, the minor item spring mechanism. Configuration) Time, control. A "°" in a strong configuration (or in the demand line configuration, AB The P system is related to the model, and the configuration shown here is -74- 200305088 (70) is feasible. However, if the search mechanism is the most suitable type, the program will go to step 1 0 7 0, of which the AB P system 1 0 0 Will remember the best configuration found so far. In step 1 090, it will be determined whether there are more configurations for the current parent SAD group. If there are more configurations, the program will return Go to step 1 0 2 0 'to get the next configuration. In step 1 065, a judgment will be made as to whether the feasible configuration has been found [as indicated by the feasible flag (configuration i' ·) ]. If the feasible flag indicates that a feasible configuration has been found, in step 〇 075, the ABP system 100 will select the current configuration as the best configuration based on the strongly feasible type mechanism, and then Go to step 1 〇 8 If there is no feasible flag 'this means that no feasible configuration has been found so far (according to a strong mechanism)' then the AB P system 1 〇 〇 will go to step 1 〇 〇 and will remember Best configuration so far (however, because strong mechanisms are chosen, None of the configurations is feasible.) Then the program moves to step 1 090 to check if there is more configuration on the order. If there is more configuration on the order, the program returns to step 1 〇 2〇 To evaluate and process the next configuration on the order. Otherwise, if there is no more configuration on the order, the program will also move to step 1 080, where the system will calculate and update the available configuration for the purpose. Date and available amount. In this specific embodiment, the available date of the parent SAD group is the available date of the best configuration, and the available amount is the available amount of the optimal configuration. Then in step 1 08 5, ABp The system 100 will update the replenishment availability date. According to a preferred embodiment of the present invention, the supplementary use date is a larger beta supplementary available amount between the available date for the current parent SAD group and the current supplementary available date for the current parent- 75- 200305088 (71) The smaller of the available amount of the SAD group and the current supplementary available amount. Supplementary flag = Yes, only the following two conditions are met at the same time: 1) supplementary availability date S supplementary demand date + ML; and 2) supplementary availability = supplementary demand quantity. In step 1 092, it is judged whether the calculated supplementary available amount after step 1085 is equal to zero. If it is not zero, there is no need to process the SKU for the current configuration again, and the program moves to step 1096, where the ABP system 100 returns (ie, outputs) the replenishment availability date, replenishment availability, and replenishment Feasibility, and will be supplemented by the manufacturing process of step 1098. If at step 1 092, the supplementary available amount is judged to be zero, the ABP system 100 checks if there are more methods on BOM 1094. If there are more, the system of step 10 10 will fetch the next parent method (that is, the SAD group) for processing. Otherwise, in step 1096, the system will leave this B 0 μ method and return the supplementary availability date, supplementary availability, and supplementary feasible flag. Then at 10 9 8 the program 100 0 0 will end. Purchasing via purchase Refer to FIG. 11, which is a general process 1094 (as represented by step 610 in FIG. 6) which is supplemented by purchase. The program produces an output by attempting to plan the replenishment demand into available buckets of time along the timeline. This output can be in the form of a quantity and / or quality report. In step 1102, when the relevant data starts to be entered and / or retrieved and / or conforms to the grammar, the program will start. Relevant information may include, for example, the attributes of the order item, and information such as supplementary demand, date of supplementary demand, earliest (ME), latest (ml), length of time bucket interval, maximum period, and the like Timing Resources-76- 200305088

(72) 訊的資料。進一步而言,購買出貨時間(PLT)係取決於定 義於步驟1104之購買「補充需求量」的訂單屬性。pLT為 在講買訂單(P0)已安置之後,需用於補充的延遲時間。已 給丁需用以獲得材料的時間,pLT會用來決定訂單何時需 要安置。在A B P系統1 〇 〇中,此由補充起始參數來限制。 回想有規劃範圍起始/結束,因此沒有訂單會在範圍起始 或在範圍結束之後做規劃。也要注意的是,「補充起始」 會決足任何補充的最早時間。會發生最快的任何補充為「 補充起始時間+PLT」。為了接收「補充需求日期」上的「 補充需求量」,然後PO必須交付的日期(稱為「購買訂單 士置日期」或「POPD」)會計算:(72) information. Further, the time to purchase (PLT) depends on the order attribute of the "supplementary demand" for the purchase defined in step 1104. pLT is the delay time to be used for replenishment after the buy order (P0) has been placed. The time required to obtain the materials has been given and pLT will be used to determine when the order needs to be placed. In the AB system 100, this is limited by supplementary starting parameters. Recall that there is a planning range start / end, so no order will be planned at the beginning of the range or after the end of the range. It should also be noted that the "start of supplementation" will determine the earliest time for any supplementation. Any supplement that will happen fastest is "Supplement Start Time + PLT". In order to receive the "supplementary demand" on the "supplementary demand date", then the date that the PO must deliver (called the "purchase order date" or "POPD") is calculated:

POpD =補充需求曰期-購買出貨時間(RNQ),藉此RNQ 係代表補充需求量。 在步驟1 108,會產生具有屬性的SKU之時間線。此時 間線為定義相關事件的順序的一種時間線。這些時間事件 ’如圖12A至1 2D中所繪示,包括,例如,購買訂單安置 曰期(POPD)、補充起始日期(RSD)、購買訂單安置日期加 上最晚曰期(POPD + ML)、補充需求日期減去最早 (RND-ME)、補充需求日期(RND)、補充起始日期加上 PLT(RSD + PLT)、補充需求曰期加上最早(rnd + mE)、以及 類似之物。基於步驟11 〇 8中所產生的時間線,至少四種一 般型式的方案是可行的。在步驟111〇,會決定可用的方案 。基於可用的方案,會產生輸出。所產生的輸出將取決於 相關時間事件(亦即,方案)的順序,以及以沿著時間線之 -77· 200305088POpD = Supplementary Demand Date-Purchase Shipment Time (RNQ), by which RNQ stands for Supplementary Demand. At step 1 108, a timeline of SKUs with attributes is generated. A timeline is a timeline that defines the sequence of related events. These time events are illustrated in FIGS. 12A to 12D and include, for example, purchase order placement dates (POPD), supplementary start date (RSD), purchase order placement dates plus latest date (POPD + ML) ), Supplementary demand date minus earliest (RND-ME), supplementary demand date (RND), supplementary start date plus PLT (RSD + PLT), supplementary demand date plus earliest (rnd + mE), and the like Thing. Based on the timeline generated in step 108, at least four general types of solutions are feasible. At step 111, the available options are decided. Based on the available scenarios, output is produced. The output produced will depend on the sequence of related time events (i.e., scenarios), and the time between -77 · 200305088

時間的桶狀區間,將需求補充量列入計畫表中的能力。各 種可行的方案及產生的輸出係敘述如下。圖1 2 A為時間線 1200,其繪示可幫助定義這些方案的時間事件。這些事件 包括購買訂單安置曰期(POPD) 1 202、購買訂單安置曰期 加上最晚(POPD + ML)1204、補充起始日期(RSD)1206、補 充需求曰期減去最早(RND-ME)1208、補充需求日期 (RND) 1 2 1 0、以及補充需求日期加上最晚(rnd + ML) 1 2 1 2 。要注意的是,這些時間事件不必然會根據圖丨2 A的時間 線1 2 0 0而必須有落差,而是這些事件的順序將取決於指定 的情況。例如,ML及ME的選擇通常是任意的。因此,在 1206的RSD日期可真正地領先在1204的POPD + ML日期。 當交付購買訂單時,用於補充的購買程序通常會開始。通 常’對於任何購買訂單(P〇)而言,從真正交付p〇的時間 到P〇已完成的時候之日期會有延遲時間。如先前所討論 ’此時間差稱為購買出貨時間或「PLT」1 2丨4。購買訂單 安置曰期(P〇PD) 1202為用於P〇之必須安置p〇的日期,以 真正地能在補充需求日期1 2 1 0完成。許多公司將接受早於 及/或晚於需求日期1210的補充購買。因此,在12〇8的最 早可接雙曰期(補充需求日期減去最早或RND-ME),以及 在1212的最晚可接受日期(補充需求日期加上最晚或 RND + ML)也會定義出來。在1 206的補充起始曰期或RSD 為真正或預期的購買訂單日期。時間線可區分成桶狀區間 12 16。所顯示的時間線12〇〇係區分成時間區間,其表示桶 狀區間12 16為時間相依的。除了時間相依之外,這些桶狀 -78- 200305088 (74) 區間可藉由如數量或品質因素的其他因素來定義。也要注 意的是,項目「曰期」在此會廣泛地使用,以致於其可解 讀為滿足時間的精確點,包括,例如,降到一天中的秒。 許多公司會有許多限制,以防止它們有無限的容量。為 了更精確地反應真實的限制,較佳而言,容量限制會藉由 購買模型而表示在補充中。一種方法就是藉由定義基於時 間的「容量最大值」來模型化。這些最大值稱為「週期最 大值」。這些週期最大值可用來限制材料或項目的數量, 其資源(如供應者)可在任何的已知時間區間產生或賣出。 也可包含其他規則(如「繼續存在」的概念),這允許供應 者的模型繼續存在在較早時間期間所產生的任何過量產 品,以可用於後來的時間期間。 以下為三種基本情況的簡短摘要,緊接著為各種方案的 更詳細說明。三種基本情況為完全數量的補充準時的時候 、完全數量的補充延遲的時候、以及完全數量的補充不可 行的時候。 情況1 : 補充係標記為可行的且已記錄最快的可用日期 。不需要做進一步的處理。 情況2 :補充係標記為可行的、已記錄需求日期上的可用 量且已記錄最快的可用日期。使用者可設定旗標,其允許 系統搜尋一種或多種取代品,以改善時間線。 情況3 :補充係標記為不可行的,並且已記錄需求日期上 的可用量及需求日期+最晚。在此例中,AB P系統1 0 0將試 圖取代為情況2,以試圖補足在需求日期+最晚的差異。 -79- 200305088The barrel-like interval of time, the ability to include the replenishment of demand in the schedule. The various possible solutions and the output produced are described below. Figure 12 A is a timeline 1200 that depicts time events that can help define these scenarios. These events include purchase order placement date (POPD) 1 202, purchase order placement date plus latest (POPD + ML) 1204, supplementary start date (RSD) 1206, supplementary demand date minus earliest (RND-ME ) 1208, supplementary demand date (RND) 1 2 1 0, and supplementary demand date plus latest (rnd + ML) 1 2 1 2. It should be noted that these time events do not necessarily have to fall according to the timeline 1 2 0 0 of Figure 2A, but the order of these events will depend on the specified situation. For example, the choice of ML and ME is usually arbitrary. Therefore, the RSD date at 1206 can really lead the POPD + ML date at 1204. When a purchase order is delivered, the purchase process for replenishment usually begins. Generally, for any purchase order (P0), there will be a delay from the time when p0 is actually delivered to the date when P0 has been completed. As discussed earlier, this time difference is called the time of purchase or shipment, or "PLT" 1 2 丨 4. Purchase order Placement date (POPD) 1202 is the date when PO must be placed for PO, so that it can really be completed on the date of supplementary demand 1 2 1 0. Many companies will accept replenishment purchases before and / or after 1210 on the demand date. Therefore, the earliest available double date at 1208 (supplementary demand date minus earliest or RND-ME), and the latest acceptable date at 1212 (supplementary demand date plus latest or RND + ML) will also Define it. The supplemental start date or RSD at 1 206 is the actual or expected purchase order date. The timeline can be divided into bucket intervals 12 16. The displayed timeline 1200 is divided into time intervals, which indicate that the barrel-shaped intervals 12 16 are time-dependent. In addition to being time dependent, these bucket-like intervals of -78- 200305088 (74) can be defined by other factors such as quantity or quality factors. It should also be noted that the term "date" is so widely used here that it can be read as an exact point in time, including, for example, down to the second of the day. Many companies have many restrictions to prevent them from having unlimited capacity. To more accurately reflect the true limits, the capacity limits are preferably represented in the supplement by purchasing models. One approach is to model this by defining a time-based “maximum capacity”. These maximums are called "period maximums". These cycle maximums can be used to limit the number of materials or items whose resources (such as suppliers) can be produced or sold in any known time interval. Other rules can also be included (such as the concept of “continuing existence”), which allows the supplier's model to continue to exist in any excess product produced during the earlier time period for use in later time periods. The following is a brief summary of the three basic scenarios, followed by a more detailed description of the various scenarios. The three basic situations are when the full number of supplements is on time, when the full number of supplements is delayed, and when the full number of supplements is not feasible. Case 1: The supplement is marked as feasible and the fastest available date has been recorded. No further processing is required. Case 2: Supplements are marked as feasible, the amount available on the recorded demand date, and the fastest available date recorded. Users can set flags that allow the system to search for one or more alternatives to improve the timeline. Case 3: Supplements are marked as infeasible, and the amount available on the demand date and the demand date + latest date have been recorded. In this example, the AB P system 100 replaces the trial with Case 2 in an attempt to make up for the difference between the demand date + the latest date. -79- 200305088

(75) 使用者可設定旗標,其允許A B P系統1 〇 〇搜尋一種或多種 取代品的額外數量,以改善時間線。如果取代品不能找出 使組態可行的,則組態會標記為不可行的且會忽略。 當使用者在已知時間框架内,不能得到使用者想要的所 有材料時,會使用週期最大值。這可能發生於如鐵礦的日 用品產品,或如電腦CPU之高需求中的元件。例如,使用 者可在一個星期内,獲得不超過10噸,或一個月内的50 個C P U的配置。在此例中,使用者需要決定如何使用這些 零件來得到最多的金錢。 如果分配輸出所擴展的容量缺乏,ABP系統1 00可確定 使用最小量的取代品。這可能發生在情況2或情況3。 以下為各種方案的詳細說明。第--般方案為POPD + ML&lt;RSD的時候之情況。補充起始日期(RSD)為交付真正 的補充購買訂單的時候之日期。參照圖丨2 B,其為繪示第 一方案的時間線1 220。在此方案中,在1 222的p〇PC) + mL 係領先在1 224的RSD。因此,訂單之在1 226的完成日期係 在基於PLT 1 230之在1 22 8的RND +ME日期之後。在此例中 ,所購買的材料或項目直到在最晚可接受日期之後,才是 可用的。因此’如果在步驟丨丨丨〇中,已決定情況1方案, 則會產生輸出(輸出1.1)。 輸出1.1 補充可用量=0 補充日期=最大日期 補充可行旗標==錯誤 -80- 200305088(75) The user can set a flag that allows the AB system to search for an additional quantity of one or more alternatives to improve the timeline. If the replacement cannot be found to make the configuration feasible, the configuration is marked as infeasible and ignored. The maximum period is used when the user cannot get all the material the user wants within a known time frame. This can happen in daily necessities such as iron ore, or components in high demand such as computer CPUs. For example, the user can get a configuration of no more than 10 tons in a week, or 50 CPUs in a month. In this example, the user needs to decide how to use these parts to get the most money. If the expanded output capacity of the distribution output is lacking, the ABP system 100 can determine the minimum amount of replacement to use. This can happen in case 2 or case 3. The following is a detailed description of each scheme. The first case is when POPD + ML &lt; RSD. The replenishment start date (RSD) is the date when the actual replenishment purchase order is delivered. Referring to FIG. 2B, it is a timeline 1 220 showing the first scheme. In this scenario, pPCC at 1 222 + mL is leading the RSD at 1 224. Therefore, the completion date of the order at 1 226 is after the RND + ME date of 1 22 8 based on PLT 1 230. In this example, the purchased material or item is not available until after the latest acceptable date. So 'if in step 丨 丨 丨 〇 case 1 has been decided, an output will be generated (output 1.1). Output 1.1 replenishment available amount = 0 replenishment date = maximum date supplementary feasible flag == error -80- 200305088

(76) 第二方案為POPD日期早於或相等於rsd日期的情況, RSD日期係早於或相等於POPD及ML日期的和:POPD£_ RSDSPOPD + ML。參照圖12C,其為緣示第二方案之時間 線1240。介於在1242的POPD日期與在1244的RND日期之 間的區間係定義為在1 246的PLT。不像繪示於圖12A及12B 的時間線,在1 248的RSD係領先在1 250的POPD + ML日期 。介於在1248的RSD日期與在1250的POPD + ML日期之間 的區間係用於安置PO的潛在區間。此區間稱為「潛在PO 安置區間」1 252。對應於此潛在PO安置區間1 252的可用 日期區間1 254係位於在1 256的RSD + PLT日期與在1 25 8的 RND + ML日期之間,此區間會從左到右(起始於1 256的 RSD + PLT)做檢查,以找出不會達反購買的週期最大值之 桶狀區間。如果必要,會做出跨多個桶狀區間之數量的分 割。如果判斷出此方案是可用的,則會做出判斷,以知道 第二方案下的那些次要方案是可用的。有三種在第二方案 之下的次方案會導致三種可能的輸出,輸出2.1、2.2及2.3。(76) The second scenario is the case where the POPD date is earlier than or equal to the rsd date, and the RSD date is earlier than or equal to the sum of the POPD and ML dates: POPD £ _ RSDSPOPD + ML. Referring to Fig. 12C, it is a timeline 1240 illustrating the second scheme. The interval between the POPD date at 1242 and the RND date at 1244 is defined as the PLT at 1 246. Unlike the timeline shown in Figures 12A and 12B, the RSD at 1 248 leads the POPD + ML date at 1 250. The interval between the RSD date at 1248 and the POPD + ML date at 1250 is a potential interval for placing the PO. This interval is called the "potential PO resettlement interval" 1 252. The available date interval 1 254 corresponding to this potential PO placement interval 1 252 is between the RSD + PLT date at 1 256 and the RND + ML date at 1 25 8. This interval will run from left to right (starting at 1 256 RSD + PLT) to check to find the barrel interval that will not reach the maximum value of the anti-purchase cycle. If necessary, a division is made across the number of bucket intervals. If it is judged that this scheme is available, a judgement is made to know which secondary schemes under the second scheme are available. There are three sub-schemes below the second scheme which will result in three possible outputs, outputs 2.1, 2.2 and 2.3.

關於第二方案的第一次方案係當百分之百的補充需求 量可安置於延伸至區間的端點(在1 156的RSD + PLT,在 1 25 8的1?^0 + 1^1〇之桶狀區間時,以下的輸出會產生: 輸出2.1 補充可用日期(RAD)=最後桶狀區間的結束曰期,藉 此可完全安置補充量。有二種例外:如果此桶狀區間 包含RSD + PLT,貝1J RSD + PLT將是RAD日期,或如果此 桶狀區間包含RND + ML ’則RND + ML將是RAD日期° -81 - 200305088 (77) 補充可用量=補充需求量 補充可行旗標=可行 關於第二方案的第二次方案係當數量X大於零,但低於 百分之百的補充需求量,可安置於延伸至區間的端點(補 充起始日期+PLT,補充需求日期+ML)之桶狀區間時,以 下的輸出會產生: 輸出2.2 補充可用日期(RAD) =最後桶狀區間的結束日期,藉此 可完全安置數量X。有二種例外:如果此桶狀區間包含 補充起始日期+PLT,則RAD與補充起始日期+PLT相等 ,或如果此桶狀區間包含補充需求日期+ML,則RAD 與補充需求日期+ML相等。 補充可用量=X 補充可行旗標=可行 關於第二方案的第三次方案係當由於週期的達反,沒有 東西可安置於延伸至區間的端點(補充起始日期+PLT,補 充需求日期+ML)之桶狀區間的時候。如果第三次方案使 用,則以下的輸出會產生: 輸出2.3 補充可用日期=最大日期 補充可用量=〇 補充可行旗標=不可行。 第三方案就是當POPD-ME日期早於或等於RSD曰期, 其早於或等於POPD曰期,其早於或等於POPD + ML曰期: -82 - 200305088 (78) POPD-ME£_補充啟始日期£jP〇PD£jP〇PD + ML。此方案實質 上與上述之第二方案的第三次方案相同。因此,會檢查區 間(補充起始日期+PLT,補充需求日期+PLT),以決定區 間中的桶狀區間是否會是足夠的。第三方案的輸出將與第 二方案的第三次方案相同。The first plan for the second plan is when the 100% supplementary demand can be placed at the end of the interval (RSD + PLT at 1 156, 1? ^ 0 + 1 ^ 10 in 1 25 8) The following output will be generated during the interval: Output 2.1 Supplemental Available Date (RAD) = End date of the last barrel interval, so that the supplementary amount can be completely placed. There are two exceptions: If this barrel interval contains RSD + PLT , Bay 1J RSD + PLT will be the RAD date, or if this barrel interval contains RND + ML ', then RND + ML will be the RAD date ° -81-200305088 (77) Supplementary available quantity = Supplementary demand quantity Supplementary feasible flag = The second scheme that is feasible about the second scheme is when the quantity X is greater than zero, but less than 100% of the supplementary demand, it can be placed at the end of the interval (supplementary start date + PLT, supplementary demand date + ML) For a bucket interval, the following output is produced: Output 2.2 Supplemental Available Date (RAD) = the end date of the last bucket interval, whereby the quantity X can be completely placed. There are two exceptions: if this bucket interval contains a supplementary start Date + PLT, then RAD and supplement start date + PLT is equal, or if this barrel interval contains the supplementary demand date + ML, RAD is equal to the supplementary demand date + ML. Supplementary available quantity = X Supplementary feasible flag = feasible. The third option for the second option is due to When the period is reached, nothing can be placed in the barrel-shaped interval that extends to the end of the interval (supplement start date + PLT, supplementary demand date + ML). If the third solution is used, the following output will be generated : Output 2.3 Supplement available date = Maximum date Supplement available amount = 〇Supplement feasible flag = Not feasible. The third solution is when the POPD-ME date is earlier than or equal to the RSD date, which is earlier than or equal to the POPD date, and it is earlier Date equal to or equal to POPD + ML: -82-200305088 (78) POPD-ME £ _ Supplementary start date £ jP〇PD £ jP〇PD + ML. This scheme is essentially the same as the third time of the second scheme above. The scheme is the same. Therefore, the interval (supplement start date + PLT, supplementary demand date + PLT) will be checked to determine whether the bucket interval in the interval will be sufficient. The output of the third scheme will be the same as the third of the second scheme. The sub-scheme is the same.

第四方案發生在補充起始日期低於或等於購買訂單配 置曰期減去最早,其低於或等於購買訂單配置日期,其低 於或等於購買訂單配置日期加上最晚:RSDSPOPD-ME1 POPD£_POPD + ML。參照圖12D,其會緣示第四方案之時間 線1260。時間線1 260係區分成桶狀區間1261。桶狀區間 1 2 6 1係由增加的時間及容量來限制。在此時間線1 2 6 0中, 第四方案需要在1262的RSD日期早於或相等於在1264的 POPD-ME日期,其早於或相同於在1266的POPD日期,其 早於或相等於在1 268的POPD + ML日期:RSD£jP〇PD-MES POPD£_POPD + ML。進一步而言,時間線1 260係緣示在1270 的RSD + PLT日期優先於在1 272及1274之RND-ME與RND 曰期。 參照圖1 3,其為用來產生第四方案的輸出之流程丨3 〇 〇 。當做出補充需求量是否可藉由包含在步驟1304的[RND-Μ E ]日期的桶狀區間來完全地提供之決定時,程序1 3 〇 〇會 開始。如果成功,在步驟1 3 0 6,以下的輸出會產生: 補充可用量=補充需求量 補充可用日期=補充需求日期-ME 補充可行旗標=可行 -83- (79) (79)200305088The fourth scenario occurs when the supplementary start date is less than or equal to the purchase order configuration date minus the earliest, which is less than or equal to the purchase order configuration date, which is less than or equal to the purchase order configuration date plus the latest: RSDSPOPD-ME1 POPD £ _POPD + ML. Referring to FIG. 12D, a marginal line 1260 of the fourth scenario is shown. Timeline 1 260 is divided into barrel-shaped intervals 1261. The barrel interval 1 2 6 1 is limited by the increased time and capacity. In this timeline 1 2 60, the fourth scheme requires that the RSD date at 1262 is earlier than or equal to the POPD-ME date at 1264, which is earlier than or the same as the POPD date at 1266, which is earlier than or equal to POPD + ML Date at 1 268: RSD £ jPPD-MES POPD £ _POPD + ML. Furthermore, the RSD + PLT dates shown at 1270 on the timeline of 1 260 are given priority over the RND-ME and RND dates at 1 272 and 1274. Referring to FIG. 13, it is a process for generating the output of the fourth scheme. When a decision is made as to whether the supplementary demand can be fully provided by the bucket interval contained in the [RND-M E] date of step 1304, the procedure 13 00 will begin. If successful, the following output will be produced in step 1 3 0 6: Supplementary available quantity = Supplementary demand quantity Supplementary availability date = Supplementary demand date-ME Supplementary feasible flag = feasible -83- (79) (79) 200305088

在步驟13〇8,會判斷是否至少一部份的量可安置於包含 (RND-ME)的桶狀區間1 275(見圖12D)中。如果否,則在步 驟13 10會產生顯示不可行的輸出[正確?]的輸出。如果部 份(例如,大於零,但低於補充需求量)數量可安置於包含 [RND-ME]的桶狀區間中,則會以後退方向來掃瞒多個連 續桶狀區間,一次一個桶狀區間,並且會盡可能地安置於 不違反週期取大值的每個桶狀區間中[請解釋此句?]。較 佳而了,直到三種情況中的一個滿足,才會向後移動: 情況4 · 1 .補充需求量只有部份位於包含(補充起始日期 + PLT)的桶狀區間中。 情況4.2 :補充需求量已完全安置,但是不位於包含(補充 起始日期+PLT)的桶狀區間中。 情況4 · 3 :補充需求量已完全安置在包含(補充起始曰期 + PLT)的桶狀區間中。 在步驟1311’會藉由回到包含(RND-me)的時間桶狀區 間1 274而使程序開始。在步驟1312,會向後移動一個桶狀 區間’並且盡可能地填滿桶狀區間。在步驟丨3丨4,會判斷 其是否為情況4.1的情形。如果如此,則在步驟1316會產 生基於特定因素的輸出。圖14八為產生情況4·ι(如圖13中 的步驟1 3 1 6所顯示)的輸出之流程丨4 〇 〇。在往前方向的多 個連續桶狀區間會做檢查,以在(rnd-me)發生的桶狀區 間1274之後的桶狀區間ι276(在圖12D中)為起始,並且會 盡可能地安置於在不達反週期最大值的每個桶狀區間中 。直到以下三種情況中的一種滿足,才會向後移動(例如 -84 - 200305088In step 1308, it is determined whether at least a part of the amount can be placed in a barrel-shaped interval 1 275 (RND-ME) (see FIG. 12D). If not, then at step 13 10 an output is displayed that is not feasible [correct? ]Output. If part (for example, greater than zero, but lower than the supplementary demand) quantity can be placed in the barrel section containing [RND-ME], it will back out to conceal multiple consecutive barrel sections, one barrel at a time And it will be placed in every bucket interval that does not violate the cycle as much as possible [please explain this sentence? ]. It is better, and it will not move backward until one of the three cases is met: Case 4 · 1. The supplementary demand is only partially located in the bucket-shaped interval containing (supplementation start date + PLT). Case 4.2: The replenishment demand is fully settled, but it is not located in the bucket interval containing (replenishment start date + PLT). Case 4 · 3: The replenishment demand has been completely placed in the bucket interval containing (replenishment start date + PLT). At step 1311 ', the process is started by returning to the time bucket region 1 274 containing (RND-me). At step 1312, a barrel section 'is moved backward and the barrel section is filled as much as possible. In step 丨 3 丨 4, it is judged whether it is the case of case 4.1. If so, an output based on certain factors is generated in step 1316. Fig. 14 is the output flow of the case 4 · ι (as shown in step 1 3 1 6 in Fig. 13). Multiple consecutive barrel sections in the forward direction will be checked, starting with the barrel section ι276 (in FIG. 12D) after the barrel section 1274 that occurred (rnd-me), and will be placed as much as possible In each bucket interval that does not reach the maximum value of the counter-period. It will not move backward until one of the following three conditions is met (e.g. -84-200305088

(80) ,朝著較早時間區間),一次一個桶狀區間: 情況4.1 1 :補充需求量不完全位於包含(補充需求日期 + ML)的桶狀區間中。 情況4.1 2 :補充需求量已完全安置於一個或多個桶狀 區間中,但是不位於包含(補充需求日期+ML)的桶狀 區間中。 情況4.1 3 :補充需求量已完全安置且位於包含(補充需 求日期+ML)的桶狀區間中。 程序1 400會藉由回到桶狀區間1 276(其係在(補充需求 日期-ML)發生的桶狀區間1 274之前),並且盡可能地安置 在不達反週期最大.值的每個桶狀區間中,而開始於步驟 1 402。此意謂會試圖嘗試填滿在(補充需求曰期-ML)會發 生的桶狀區間1 474之外的時間内之前的每個桶狀區間,並 且會在包含(補充需求日期+ML)日期的桶狀區間,或結束 在(補充需求日期+ML)日期的桶狀區間1 278(圖1 2D中的 桶狀區間1 3 78)之前到達此桶狀區間。在步驟1404,會向 後移動一個桶狀區間至下個較早的時間桶狀區間。在步驟 1 406,會再檢查時間線,以及判斷其是否為4.11的情況方 案。如果如此,則在步驟1 4 0 8會產生以下的輸出: 補充可用日期=會安置非零的數量之最後桶狀區間的 結束日期 補充可用量=可安置的總量 補充可行旗標=不可行 如果不是4 · 1 1的情況,則在步驟1 4 1 0,會判斷其是否為 -85 - 200305088(80), towards the earlier time interval), one barrel interval at a time: Case 4.11: The supplementary demand is not completely located in the barrel interval containing (supplementary demand date + ML). Case 4.12: The replenishment demand has been completely placed in one or more bucket sections, but not in the bucket section containing (supplementary demand date + ML). Case 4.13: The replenishment demand is fully settled and is located in a barrel section containing (replenishment demand date + ML). Program 1 400 will return to barrel interval 1 276 (before barrel interval 1 274 (Supplementary Demand Date-ML) occurred) and place it as close as possible to each In a bucket interval, and it starts at step 1 402. This means that an attempt will be made to fill each bucket interval before the time when (supplementary demand date-ML) bucket interval 1 474 occurs, and will include (supplementary demand date + ML) date The barrel interval reaches the barrel interval before the end of the barrel interval 1 278 (the barrel interval 1 3 78 in FIG. 12D) on the (supplementary demand date + ML) date. At step 1404, one barrel interval is moved backward to the next earlier time barrel interval. At step 1406, the timeline is checked again, and it is judged whether it is the case of 4.11. If so, the following output will be produced at step 1 0 0 8: Supplemental availability date = end date of the last barrel interval where non-zero quantities will be placed Supplementary availability = total amount that can be placed Supplementary feasible flag = not feasible If it is not 4 · 1 1, in step 1 4 1 0, it will be determined whether it is -85-200305088.

(81) 4.1 2的情況。如果其為4 · 1 2的情況,則在步驟1 4 1 2會產生 輸出如下: 補充可用日期=會安置非零的數量之最後桶狀區間的 結束曰期 補充可用量=補充需求量 補充可行旗標=可行 如果不是4 · 1 2的情況,則在步驟1 4 1 4,會判斷其是否為(81) Case of 4.1 2. If it is the case of 4 · 1 2, then the output will be produced in step 1 4 1 2 as follows: supplementary availability date = the end of the last barrel interval where non-zero quantities will be placed. Supplementary availability = supplementary demand. Flag = feasible If it is not the case of 4 · 1 2, then in step 1 4 1 4 it will be judged whether it is

4.1 3的情況。如果其為4.1 3的情況,則會產生輸出如下: 補充可用日期=補充需求日期+ML 補充可用量=補充需求量 補充可行旗標=可行 如果不是4 · 1 3的情況,則會返回到步騾1 4 0 4,並且會再 次往後移動到一個桶狀區間,以開始程序。參照圖1 3,如 果其不是4.1情況的情形,則在步驟1 3 1 6會判斷是否為4.2 的情況。如果其為4 · 2的情況,則在步驟1 3 1 8會產生以下 的輸出: 補充可用日期=會安置非零的數量之最後桶狀區間的 結束日期 補充可用量=補充需求量 補充可行旗標=可行 如果不是4.2情況的情形,則在步驟1 320,會判斷其是 否為4 · 3情況的情形。如果其為4 · 3情況的情形,則在步驟 1 3 22,會產生輸出如下:4.1 Case 3. If it is the case of 4.13, the output will be as follows: supplementary availability date = supplementary demand date + ML supplementary available amount = supplementary demand supplementary feasible flag = feasible If it is not 4 · 1 3, it will return to step骡 1 4 0 4 and will move back to a bucket interval again to start the program. Referring to FIG. 13, if it is not the case of the 4.1 case, it is determined whether the case is the 4.2 case at step 1 3 1 6. If it is the case of 4.2, then the following output will be produced in step 1 3 1 8: supplementary availability date = end date of the last barrel interval where non-zero quantities will be placed supplementary availability = supplementary demand supplementary feasible flag Mark = feasible If it is not the case of the 4.2 case, then in step 1 320, it will be determined whether it is the case of the 4 · 3 case. If it is the case of the case of 4 · 3, then in step 1 3 22, the output will be as follows:

補充可用日期=補充起始日期+PLT -86- 200305088Supplement Available Date = Supplement Start Date + PLT -86- 200305088

(82) 補充可用量=補充需求量 補充可行旗標=可行 如果不是4 · 3情況的情形,則會返回步驟1 3 1 2,並且直 到已產生輸出,才會向後移動一個桶狀區間,再次重新開 始程序° _由取代的補充 如果藉由製造及/或購買所做的補充企圖不能完全滿足 材料可行性程序6 〇〇的補充步驟6 1 0 (圖6)時,ABP系統1 00 會試圖補足藉由製造及/或購買及藉由取代之需求補充量 與總可用數量之間的差異。取代可用於任何型式的SKU ,包括具有屬性的FG SKU,SKU、次要項目SKU、以及 類似之物。取代模型會產生,以幫助具有屬性的SKU之取 代。每當取代品需用於具有屬性的SKU時,在ABP系統100 試圖使用定義的B OM組態中的一個來製造之後,其會試 圖取代漏失的SKU。取代品會以優先順序做處理,並且所 有的取代品在嘗試任何製造組態在取代品上之前,會測試 存在的存貨’否則高優先權取代品的製造組態會優先嘗試 。取代品可藉由產生取代表來模型化。取代品可定義所有 的子項[子項為母項的次要項目’例如’汽車為母項’而 汽車座椅為子項],但是通常不會用於成品。多級取代品 也可以允許,如用於取代品的取代品。 在步驟614及616(圖6),會做出試圖嘗試滿足尚未藉由 使用取代品之6 1 0的補充步驟達成之任何補充需求量。參 照圖1 4 B,其會用於以取代品做補充之流程1 4 5 0。當某些 -87- 200305088 (83) 資料/參數已擷取及定義時,程序會開始。所擷取的資料 可包括相關於具有屬性的母SKU(具有屬性的母SKU,此 會是選用的)、次要項目SKU、原始需求量(次要項目需求 量)、次要J頁目需求量及日期、最早(ME)、最晚(ML)、以 及類似的東西之資訊。abp系統1〇〇會使用伴隨任何取代 偏愛的此資訊,以達成稱為「取代品需求量」或「SNQ 」&lt; 所需數量的取代品。SNQ為用於具有屬性的取代品 SKU ’其可用在最後可接受日期(取代品需求日期+ML)或 在最後可接受日期之前是可用的。取代功能的輸出(如圖6 的步驟6 1 4中所繪式)包括取代品可用量、取代品可用日期 、以及取代品可行性旗標。基於所提供的資訊,可接受取 代品可在步驟1 4 5 4決定出來。如果超過一種可接受取代品 存在’則會在步驟丨4 5 6判斷每種取代品的優先權。通常, 某二取代w會比其他取代品更偏愛。因此,較佳而言,會 將可接受產品按優先順序處理。在步驟丨4 5 8,會選擇可接 受產品的一種來判斷可行性。為了判斷所選擇的取代品是 否可用於補充,在步驟1460會先做存貨的檢查。在步驟 1462,會判斷是否存貨可在需求曰期前,完全滿足需求量 。如果否,則在步驟1464會試圖藉由製造或購買,來達成 任何存貨短缺。藉由製造及/或購買取代品之補充的程序 可使用上述用於藉由製造或購買的補充之程序來完成。如 果再有可接受取代品,則會返回步驟1 45 8,以在步驟1466 ’判斷下個可接受取代品的可行性。在步驟1 468中,選擇 取代優先權。這可藉由旗標的使用來完成,其說明如下。 -88- 200305088 (84) 在步騾1 470,會基於取代品優先權、可行性及取代品偏愛 來選擇一個或多個取代品。 藉由取代的補充可藉由產生取代表而模型化。此表具有 一或多行,其會管理ABP系統1〇〇可實施取代品的方式。 此表可用來定義一些項目。 如果指定母SAD群組,當訂單與此SAD群組匹配,將只 會允許相關的取代。如果此未指定給予列,用於具有屬性 的所有取代品S KU之由列所定義的取代規則是正確的’這 係藉由取代品SAD群組來說明。換句話說,取代可總體地 應用於SKU,無論母項如何(在母項行為空的時候)’或其 只可應用於某些母子關係。在做如此中,當取代品允許時 ,使用者可使用SAD群組來進一步限制。 取代表中的行可定義出次要項目SAD群組。次要項目 SAD群組係說明將被取代的次要項目SKU。另一仃可定義 次要項目SKU。此行(可實施為二種分隔的行·取代品項 目及取代品SKU)係說明SKU係用於具有屬性的’入要項目 SKU之可接受的取代品。 複製指令可定義出來。此行包含用來指定必須複製到次 要項目SKU的屬性之複製指令的參考號。例如’取代表中 的記錄可以是如下:(82) Supplementary available quantity = supplementary demand supplementary feasible flag = feasible. If it is not the case of 4 · 3, it will return to step 1 3 1 2 and will not move back a barrel interval until the output has been generated, again Restart the procedure ° _ Supplemental replacement by replacement If the supplementary attempt made by manufacturing and / or purchasing does not fully meet the material feasibility procedure 6 supplementary step 6 1 0 (Figure 6), the ABP system 1 00 will attempt Make up the difference between the quantity replenished by manufacturing and / or purchasing and by replacement and the total available quantity. Replaces any type of SKU that can be used, including FG SKUs with attributes, SKUs, minor item SKUs, and the like. Replacement models are generated to help replace SKUs with attributes. Whenever a replacement needs to be used for an SKU with attributes, after the ABP system 100 attempts to manufacture using one of the defined BOM configurations, it attempts to replace the missing SKU. The substitutes will be processed in priority order, and all the substitutes will test the existing inventory before trying any manufacturing configuration on the substitutes; otherwise the manufacturing configuration of the high priority substitutes will be tried first. Substitutions can be modeled by generating substitution tables. Substitutes can define all children [secondary items whose children are parent's, such as 'cars are parents' and car seats are children's], but are usually not used for finished products. Multi-stage substitutes are also permissible, such as substitutes for substitutes. At steps 614 and 616 (Fig. 6), an attempt is made to attempt to meet any supplementary demand that has not been achieved by using a supplementary step of 6 1 0. Referring to Figure 14B, it will be used in the process of supplementing with the substitute product 1450. The process will start when some -87- 200305088 (83) data / parameters have been retrieved and defined. The retrieved data can include the parent SKU with attributes (the parent SKU with attributes, which will be optional), the minor item SKU, the original demand (the minor item demand), and the minor J page demand Volume and date, earliest (ME), latest (ML), and similar information. The abp system 100 will use this information along with any substitution preferences to achieve what is called the "replacement demand" or "SNQ" &lt; required number of substitutes. SNQ is for substitutes with attributes SKU 'which is available on or before the last acceptable date (replacement demand date + ML). The output of the replacement function (as shown in step 6 1 4 of Fig. 6) includes the amount of the substitute available, the date when the substitute is available, and the flag of the substitute feasibility. Based on the information provided, acceptable alternatives can be determined in steps 1 4 5 4. If more than one acceptable substitute exists', the priority of each substitute is judged at step 4 5 6. In general, some substitutions of w will be preferred over other substitutions. Therefore, it is better to prioritize acceptable products. At step 4 5 8 one of the acceptable products will be selected to judge the feasibility. In order to determine whether the selected substitute is available for replenishment, an inventory check is performed first in step 1460. In step 1462, it is determined whether the inventory can fully meet the demand before the demand date. If not, then in step 1464 an attempt is made to achieve any inventory shortage by manufacturing or purchasing. Procedures for supplements by manufacturing and / or purchasing replacements can be accomplished using the procedures described above for supplements by manufacturing or purchasing. If there are more acceptable substitutes, then return to step 1 45 8 to determine the feasibility of the next acceptable substitute at step 1466 '. In step 1 468, select Override Priority. This can be accomplished through the use of flags, which are explained below. -88- 200305088 (84) At step 1 470, one or more substitutes will be selected based on the priority, feasibility, and preference of the substitutes. Supplements by substitution can be modeled by generating substitution tables. This table has one or more rows that govern how the ABP system 100 can implement the replacement. This table can be used to define some items. If a parent SAD group is specified, when the order matches this SAD group, only relevant substitutions will be allowed. If this is not specified, the substitution rule defined by the column for all substitutes S KU with attributes is correct 'is explained by the substitute SAD group. In other words, substitution can be applied to SKUs in general, regardless of the parent (when the parent's behavior is empty) 'or it can only be applied to certain parent-child relationships. In doing so, users can use SAD groups to further restrict when substitutes are allowed. Substituting rows in the table defines a secondary item SAD group. The secondary item SAD group indicates the secondary item SKU that will be replaced. The other can define secondary item SKUs. This line (which can be implemented as two separate lines • Substitute Item and Substitute SKU) indicates that the SKU is an acceptable substitute for the 'entry item SKU' with attributes. Copy instructions can be defined. This line contains the reference number of the copy instruction specifying the attributes that must be copied to the secondary item SKU. For example, the record in the substitution table can be as follows:

豐SAD群組:項目=路由器A &amp;要項目SAD群組:項目二介面模組及介面型式=4痒 I代品SKU :項目=介面模組及位置二亞特蘭大 jl製指今:從屬性=「介面型式」,到屬性一「介面型 -89- 200305088 (85) 式」,(或使用者可遺留此空格),至值==「8 -埠」。 以上模型化的取代關係可轉換到以下範例的商業規則: 對於母路由器A而言,4 -埠介面模組總是可以8 -埠介面 模組來取代。雖然未顯示於於此例中,使用者可指定額外 屬性,而使用複製指令,複製到次要項目SKU。 優先權可由行中的一個來定義。具有屬性之已知的次要 項目SKU(假設此只是SKU)可能具有許多屬性。此行會將 這些取代品之每一個的相對優先權模型化。例如,次要項 目SKU「Y」可具有三種不同屬性(每種屬性為表中的不同 記錄),SKU「A」、SKU「B」及SKU「C」。使用優先權行 ,使用者可在這些不同的取代品中,將相對的偏愛模型化 。例如,使用者可指定SKU A是最偏愛的(優先權=1),SKU B是第二最偏愛的(優先權=2),而SKU C是最少偏愛的(優 先權=3) ° 其他行會產生,以及設計用於其他目的。例如,行可設 計用於有效日期。有效日期為在取代關係為正確的時間内 之最早點。行可設計用於停止日期。停止日期為在取代關 係為正確的時間内之最晚點。可產生用於拉取量的行。當 使用取代品時,取代特性可允許使用者將不同Β Ο Μ的拉 取量模犁化。藉由在此行中指定拉取量,當使用取代品時 ,使用者可使母項與次要項目(其會被取代)之間的Β Ο Μ拉 取量重疊。例如,母項可能是SKU「X」,次要項目可能是 S K U「Υ」,而Β Ο Μ關係上的拉取量可能是4。如果次要項 目SKU Υ係以次要項目SKU ζ來取代,則使用者可指定不 -90- 200305088Feng SAD Group: Item = Router A &amp; Required Item SAD Group: Item 2 Interface Module and Interface Type = 4 itch I Substitute SKU: Item = Interface Module and Location II Atlanta Jl System Instructions: Attribute = "Interface type", go to property one "Interface type-89- 200305088 (85) style", (or the user can leave this space), and the value == "8 -port". The above modeled substitution relationship can be transformed into the following business rules: For the parent router A, the 4-port interface module can always be replaced by the 8-port interface module. Although not shown in this example, users can specify additional attributes and use the copy command to copy to the secondary item SKU. Priority can be defined by one of the lines. A known minor item SKU with attributes (assuming this is just a SKU) may have many attributes. This trip models the relative priority of each of these substitutes. For example, the secondary item SKU "Y" can have three different attributes (each attribute is a different record in the table), SKU "A", SKU "B", and SKU "C". Using priority lines, users can model relative preferences among these different alternatives. For example, the user can specify that SKU A is the most preferred (priority = 1), SKU B is the second most preferred (priority = 2), and SKU C is the least preferred (priority = 3) ° Other rows Will be produced as well as designed for other purposes. For example, rows can be designed for valid dates. The effective date is the earliest point in time when the substitution relationship is correct. Rows can be designed to stop dates. The stop date is the latest point in time when the replacement relationship is correct. Lines can be generated for pulling amounts. When using substitutes, the substitution feature allows the user to plow different draw volumes. By specifying the pull amount in this row, when using a substitute, the user can overlap the B 0 Μ pull amount between the parent item and the secondary item (which will be replaced). For example, the parent item may be SKU "X", the secondary item may be S K U "Υ", and the pull amount on the B 0 M relationship may be 4. If the secondary item SKU is not replaced by the secondary item SKU ζ, the user can specify not -90- 200305088

(86) 同的拉取量(指明5)來使用。在化學工業應用中,此特性 實質上是有用的。 行會產生及設計用於序號。在取代表中的多個母SAD群 組·次要項目SAD群組組合(模型化不同的取代選擇物/規 則)可應用於記憶體中之具有屬性的母SKU_具有屬性組 合的次要項目SKU。在此例中,較佳而言,會使用具有最 低序號的取代選擇物/規則。 也有特定於母S A D群組-次要項目s A D群組組合(相對於 母S A D群組·次要項目s A D群組-次要項目s K U組合)之因 素可模型化於取代表中(要注意的是在取代表中的列會特 定於母S A D群組-次要項目s A D群組-次要項目s K U組合, 通常不同於取代表中的樣式之因素。BOM表會是用於將 這些因素模型化之較佳的表)。例如,AB P系統1 00允許許 多型式的「旗標」,這允許使用者能輕易地實施預定的商 業規則。這些旗標包括,例如,「部份完成」旗標、「完成 模式」旗標、「直到用完才使用」旗標及「多級取代」旗 標。如果部份完成旗標表示只有已達成部份完成,此表示 只有原始需求量(在淨輸出/製造/購買原始取代品之前)可 單獨從此取代品的存貨/補充中完全地滿足,取代品才可 以使用。如果原始需求量不完全滿足使用取代品的淨/補 充,此取代品將不會使用。如果用於次要項目SKU的取代 品未發現,其甚至在嘗試多級取代之後,可完全滿足需求 量(次要項目需求量),則取代不是可行的。 完成模式旗標會提供完成功能及將淨/補充行為管理 -91- 200305088(86) Use the same amount of draw (specify 5). This property is essentially useful in chemical industry applications. Guilds are generated and designed for serial numbers. Multiple parent SAD groups in the substitution table · Secondary items SAD group combinations (modeling different replacement choices / rules) can be applied to the female SKUs with attributes in the memory_secondary items with attribute combinations SKU. In this example, preferably, the replacement selector / rule with the lowest number is used. There are also factors specific to the parent SAD group-secondary item s AD group combination (relative to the parent SAD group · secondary item s AD group-secondary item s KU combination) can be modeled in the substitution table (require Note that the columns in the replacement table will be specific to the parent SAD group-secondary item s AD group-secondary item s KU combination, which is usually different from the style factor in the replacement table. The BOM table is used to combine These factors are modeled better). For example, the AB P system 100 allows for many types of "flags", which allows users to easily enforce predetermined business rules. These flags include, for example, the "Partially Complete" flag, the "Complete Mode" flag, the "Not Used Until Used" flag, and the "Multi-Level Replacement" flag. If the partial completion flag indicates that only partial completion has been reached, this means that only the original demand (before net output / manufacturing / purchase of the original replacement product) can be fully satisfied from the stock / replenishment of the replacement product separately. can use. If the original demand does not fully meet the net / supplement of using a substitute, the substitute will not be used. If a replacement for a minor project SKU is not found, and it can fully meet the demand (secondary project demand) even after trying multi-level substitution, the substitution is not feasible. The completion mode flag will provide completion functions and manage net / supplementary behavior -91- 200305088

(87) 為跨過多個取代品的取代功能搜尋。對於此旗標,有二種 可允許的設定:「在補充任何之前之跨過所有取代品的淨 值」,以及「根據取代品的優先權之淨值及補充」。會影響 規劃程序的行為之完成模式旗標的方式可藉由以下的例 子來解釋。 假設 SKU A、B及C係配置為用於次要項目SKU「Y」 的取代品。A比B偏愛,以及B比C偏愛。進一步假設取代 品需求量為5 0及原始需求量為8 0 (表示3 0單位係使用次要 項目SKU「X」的存貨/補充來完成)。假設用於SKU A、B 及C之手邊的存貨位置係如下: SKU A : 20 單位 SKU B ·· 10 單位 SKU C : 10 單位 另外,在S K U A、B及C之範圍中的任何地方,不再有列 入計畫表的收據,以及部份完成旗標會設定成是。基於以 上的例子,如果完成模式旗標設定成「在補充任何之前之 跨過所有取代品的淨值」,則完成取代品需求量之取代函 數的方式可以是如下: 1. 20單位A的淨存貨(在此點後,將需要5 0-2 0 = 3 0更多 的單位)。 2. 10單位B的淨存貨(在此點後,將需要3 0- 1 0 = 20更多 的單位)。 3. 10單位C的淨存貨(在此點後,將需要20-10=10更多 的單位)。 -92- (88) 200305088 4·現在返回A及嘗試補充ι〇單位 的A。假和。‘ 的A可適度的補充。在此點,我兩 叹有5單位 5 ·接著,可知5單位的B是否可用 多的單位。 果補充。因1、上 行的,所以取代法則會使用以下 為廷是可 需求量: 、&quot;應來達成取代品 • 2 0單位的存貨a • 1 〇單位的存貨b • 1〇單位的存貨c •用於5單位的A之規劃訂單 •用於5單位的B之規劃訂單 如禾芫成模 •工刑又如之跨過所有 取代品的非淨值」,則完成取代品需求量之取代函數的方 式可以是如下·· I 2〇單位A的淨存貨(在此點後,我們需要50_20 = 30更 多的單位) 2·嘗試補充30單位的A。我們假設我們只可以適度地 補无5單位的A。在此點後,我們需要25更多的單位。 單位B的淨存貨(在此點後,我們需要2 5 -1 0 = 1 5更 多的單位) 4·補充1 5單位的B。我們假設這是可行的。在此點時 ,我們不需要任何進一步地察看。所以取代品C甚至不 會碰到。 「直到耗盡才使用」旗標可用來決定補充可源自那個來 源 果此旗標設定成「是」,在耗盡所有取代選擇物之 -93- 200305088 (89) 前,用於主要(次要項目)的新規劃訂單將不會產生。如果 希望使用於次要項目的任何新補充最小化,此旗標會設定 成是。換句話說,如果此旗標會設定成是,則法則的動作 係如下: 1 ·任何淨存貨/次要項目之列入計畫表的收據。 2 ·會試圖藉由訴諸取代程序而經由取代,來達成其餘 量(如果有任何其餘量)。取代程序將會試圖藉由耗盡 關於次要項目(包括多級取代品,如果配置的話)的所 有可能取代品,以達成此需要。 3·如果取代程序不能完全達成其餘需要量,會試圖藉 由產生關於在取代後,仍遺留數量的次要項目之規劃 訂單’以補充次要項目。 「多級取代」旗標會將取代程序指引到使用遞回技術。 如果多級取代旗標設定成「是」,則ABP系統會嘗試藉由呼 叫遞回形式中的取代程序來達成取代需要。如過配置(亦即 ,設定)此旗標,則取代程序會尋找取代品中的取代品, 或取代品中的取代品,其為其他取代品中的取代品等等。 AB P系統1 〇 〇對於產生於圖4的步騾4 1 〇中之可允許資源 的清單上之每個資源會找出潛在的列入計畫表機會。如以 上所討論,系統100會重複經由已知訂單的位置清單。在 每個位置’系統1 〇〇會重複經由可允許資源的清單,以及 當重複清單時,會評估潛在的列入計畫表機會。訂單最後 會使用系統1 〇 〇已重複之跨過所有資源-位置組合的最佳 列入計畫表機會,而列入計畫表中。 -94· 200305088(87) Search for a replacement function that spans multiple replacements. For this flag, there are two permissible settings: “net value across all substitutes before any replacement” and “net value and supplementation based on the priority of the substitute”. The manner in which the completion mode flag affects the behavior of the planning process can be explained by the following example. Assume that SKUs A, B, and C are configured as replacements for the secondary item SKU "Y". A prefers B, and B prefers C. It is further assumed that the replacement demand is 50 and the original demand is 80 (indicating that 30 units are completed using the inventory / replenishment of the secondary item SKU "X"). Assume that the inventory locations for SKU A, B, and C are as follows: SKU A: 20 units SKU B ·· 10 units SKU C: 10 units In addition, anywhere in the range of SKUA, B, and C, no longer Receipts included in the schedule and some completion flags will be set to Yes. Based on the above example, if the completion mode flag is set to "net value across all substitutes before any replacement", the method of completing the substitution function of the demand for substitutes can be as follows: 1. 20 units of A net inventory (After this point, 5 0-2 0 = 30 more units will be required). 2. 10 units of B net inventory (after this point, 3 0-1 0 = 20 more units will be required). 3. Net inventory of 10 units C (after this point, 20-10 = 10 more units will be required). -92- (88) 200305088 4. Now return to A and try to replenish A unit. Fake and. ‘A can be moderately supplemented. At this point, I sighed that there are 5 units 5 · Then, we can know whether 5 units of B are available for more units. Fruit supplement. Due to the upward trend, the replacement rule will use the following as the required quantities: 、 &quot; Should be reached to achieve the replacement • 20 units of inventory a • 10 units of inventory b • 10 units of inventory c • used Planning order for A of 5 units • Planning order for B of 5 units such as Wo sculpting • Work penalties cross the non-net value of all substitutes ”, then the method of completing the substitution function of the demand for substitutes is completed. It can be as follows: · I 2 0 units of A net inventory (after this point we need 50_20 = 30 more units) 2. Try to replenish 30 units of A. We assume that we can only moderately fill A without 5 units. After this point, we need 25 more units. Net inventory of unit B (after this point, we need 2 5 -1 0 = 15 more units) 4. Replenish 15 units of B. We assume this is feasible. At this point, we do not need any further inspection. So the replacement C will not even come across. The "Use Only Until Depleted" flag can be used to determine the source from which the replenishment can be derived. If this flag is set to "Yes", it will be used for the primary (secondary) period until -93- 200305088 (89) is exhausted of all alternatives. To the project) new planning orders will not be generated. This flag is set to Yes if you want to minimize any new supplements used for minor items. In other words, if this flag would be set to yes, then the rule would behave as follows: 1 • Receipt of any net inventory / minor items included in the schedule. 2. Attempts will be made to achieve the remaining amount (if there is any remaining amount) through substitution by resorting to the substitution procedure. The replacement process will attempt to fulfill this need by exhausting all possible alternatives for minor items (including multi-level replacements, if configured). 3. If the replacement process does not fully meet the remaining requirements, an attempt will be made to supplement the secondary items by generating a planning order for the number of secondary items remaining after replacement. The "multi-level replacement" flag will direct the replacement process to the use of recursive technology. If the multi-level substitution flag is set to "Yes", the ABP system will attempt to achieve the substitution requirement through the substitution procedure in the call recursive form. If this flag is configured (that is, set), the replacement program will look for substitutes in the substitute, or substitutes in the substitute, which are substitutes in other substitutes, and so on. The AB P system 1 00 will identify potential listing opportunities for each resource on the list of allowable resources generated in step 4 1 0 in FIG. 4. As discussed above, the system 100 repeats the list of locations via known orders. At each location, the system 100 will iterate through the list of allowable resources, and when it repeats, it will evaluate potential listing opportunities. At the end of the order, the system 100 repeats the best listing opportunity across all resource-location combinations and is included in the planning table. -94200305088

為了評估已知資源上之潛在的列入計畫表機會,較佳而 言,系統1 00首先會識別資源上之潛在的列入計畫表機會 。潛在的列入計畫表機會可定義為在滿足訂單的所有可用 限制之時間内的桶狀區間。換句話說,訂單可在不達反任 何限制的桶狀區間内,列入計畫表中。任何資源上之潛在 的列入計畫表機會為三種不同實體(材料可用性、資源容 量限制及附屬限制)的函數。· 實質上有二種資源,主要及附屬。主要資源會決定是否 有足夠容量來滿足或不能滿足需求量。這可以最細微粒狀 (例如以天級)來模型化。從屬資源也是需要的。低於主要 資源的等級之粒狀,不能模型化。相關於訂單的所有資源 及材料必須同時可行的。 資源容量限制通常是相關於資源之最基本的限制。通常 ,每種資源將明確地具有相關於其的容量限制。資源上之 列入計畫表的訂單會對資源容量限制做檢查。再者,會假 設在容量限制上的時間桶狀區間具有最細微粒狀。為了模 型化資源的容量限制,容量日曆會產生,並且與經由例如 資源群組的一個資源及許多個資源相關。 不像資源容量限制,附屬限制為可或不可用於已知訂單 的「抽象」限制。附屬限制可以布林觸發器來實施,其定 義對訂單之限制的可用性。除了資源容量限制之外,訂單 會對有關其他限制的可行性做檢查。這些附屬限制會藉由 屬性的存在或不存在(或屬性的組合)來觸發。附屬限制的 一例為: -95- 200305088 (91) 具有車窗的紅色汽車之數目&lt; 1 ο ο 這是用於同時具有以下屬性的訂單之附屬限制:顏色= 紅色及天窗=是。 為了產生附屬限制,指定的實體可以「結合」在一起。 三種實體為SAD群組、資源或資源群組及日曆的最大值。 為了顯示此概念,會提供以下的例子。假設一天不會製造 出超過5 0部車,並且每個星期係藉由亞特蘭大工廠的七個 工作天來定義。如果我們決定以天級來模型化主要容量限 制,則每天會有5 0部車的最大值。如果我們決定以星期級 來模型化主要容量限制,則每星期會有5 Ο X 7 = 3 5 0部車的 最大值。假設在亞特蘭大製造之具有天窗的紅色汽車之數 目每星期不超過5 0部車。接著,使用者會產生附屬限制, 指定(顏色=紅色及天窗=是)的SAD群組、以及指定限制的 最大值為每星期5 0部車。附屬限制可特定於資源,特定於 資源群組或總體。如果限制係特定於資源,限制只能使用 於會試圖將資源上的訂單列入計畫表中的時候。如果限制 為總體的,限制會使用,無論訂單列入計畫表中的是那個 資源。在以上的例子中,限制係特定於基於亞特蘭大的所 有資源。在實施附屬限制中,相關於限制的日曆會產生。 每種限制會具有用以指定其狀態(桶狀區間)之一的容量 多少將由訂單所使用之機制,如果此訂單以此狀態(桶狀 區間)列入計畫表中的話。訂單可減少限制的容量有許多 方式: 情況1 :(數量)藉由訂單上的需求量來降低桶狀區間的容 -96- (92) (92)200305088In order to evaluate potential listing opportunities on known resources, it is better that the system 100 first identifies potential listing opportunities on resources. A potential listing opportunity can be defined as a bucket interval within the time when all available limits of the order are met. In other words, orders can be included in the schedule within barrel-shaped intervals that do not reach any limit. The potential listing opportunity on any resource is a function of three different entities (material availability, resource capacity limits, and dependency limits). · There are essentially two types of resources, primary and secondary. The main resource determines whether there is sufficient capacity to meet or fail to meet the demand. This can be modeled in the finest particles (e.g. in the order of days). Subordinate resources are also needed. Granularity below the level of the main resource cannot be modeled. All resources and materials related to the order must be available at the same time. Resource capacity limits are usually the most basic limits related to resources. In general, each resource will explicitly have a capacity limit associated with it. Orders placed on a resource will be checked for resource capacity constraints. In addition, it is assumed that the bucket-like time interval on the capacity limit has the finest particle shape. To model the capacity limit of a resource, a capacity calendar is generated and related to one resource and many resources via, for example, a resource group. Unlike resource capacity limits, ancillary limits are "abstract" limits that may or may not be available for known orders. Ancillary restrictions can be implemented by Bollinger triggers, which define the availability of restrictions on orders. In addition to resource capacity restrictions, the order will check the feasibility of other restrictions. These subsidiary restrictions are triggered by the presence or absence of a property (or a combination of properties). An example of an ancillary restriction is: -95- 200305088 (91) Number of red cars with windows &lt; 1 ο ο This is an ancillary restriction for orders that have both of the following attributes: color = red and sunroof = yes. To create affiliation restrictions, designated entities can be "bonded" together. The three entities are SAD groups, resources or resource groups and calendar maximums. To illustrate this concept, the following examples are provided. Assume that no more than 50 cars are made in a day, and that each week is defined by the seven working days at the Atlanta plant. If we decide to model the main capacity limit in days, there will be a maximum of 50 cars per day. If we decide to model the main capacity limit in terms of weeks, there will be a maximum of 5 0 X 7 = 350 cars per week. It is assumed that the number of red cars with a sunroof manufactured in Atlanta does not exceed 50 cars per week. Next, the user will generate an affiliated restriction, the designated SAD group (color = red and sunroof = yes), and the maximum value of the designated restriction is 50 cars per week. Ancillary restrictions can be specific to a resource, specific to a resource group, or overall. If a restriction is specific to a resource, the restriction can only be used when an attempt is made to include an order on the resource in the schedule. If the limit is overall, the limit will be used regardless of which resource the order is listed in the plan. In the example above, restrictions are specific to all Atlanta-based resources. In implementing subsidiary restrictions, calendars related to restrictions are generated. Each limit will have a mechanism to specify how much of its status (barrel interval) will be used by the order if this order is listed in the plan table with this status (barrel interval). There are many ways in which the order can reduce the limited capacity: Case 1: (Quantity) Reduce the capacity of the bucket interval by the amount of demand on the order

量在此例中,總是會降低訂單的數量。例如,如果需要 五部汽車’則會以相差五來降低。用於有關可允許單位的 數目之限制。 Μ /兄2 ·( 1)藉由每個訂單的一個單位來降低桶狀區間的容 τ ^在此例中,對於訂單,總是會降低1。用於限制,其 會限制相對於所產生的數量之可允許的訂單之總數。 情況3 : (UDA)查詢訂單/項目/SKU的屬性之已配置的數值 重要屬性,以及藉由訂單/項目/SKU的值來降低桶狀區間 的容量。在此例中,會使用使用者定義屬性(User Defined Attribute; UDA)中的值來決定需降低多少。當使用者想要 限制總玎單量,以及同時會外在地模型化之另一種屬性時 ,通常會使用。例如,假設運送公司會限制汽車可運送多 少單位,同時希望限制運送的總重。在此例中,一個人可 將訂單的總重放到UD A中。 情況4 : (UDA*數量)查詢訂單/項目/SKlj屬性值,以及如 果此值與先前在此狀態中列入計畫表的訂單之屬性的值 不同,則會對容量降低零,以及否則會降低1。在此例中 ,會使用UD A中的值,並且會將它與訂單量相乘,以判斷 要降低多少。假設工廠係限制一天内可製造多少汽車,並 且會限制製造汽車所花費的小時數。在此例中,一個人可 將製造一部汽車所花費的小時數放到UD A中,並且與訂單 中的汽車數相乘’所需的組件小時之總數。 情況5 :(設定)查詢訂單屬性值,以及會判斷此值是否存 在於先則(或下個)狀態的訂單中;如果屬性值不存在於先 -97· 200305088 (93) 前(或下個)狀態中,則會降低一個單位,否則會降低零。 如果SKU/屬性值不在已有的桶狀區間中,則會降低i,否 則會降低0。通常會用於可在桶狀區間中達成之事物的型 式之數目。 情況6 :(開啟)如果SKU/屬性值不在先前的桶狀區間中, 而在目前的桶狀區間中,則會降低1,否則會降低0。當從 桶狀區間到桶狀區間移動時,通常會用來限制可達成多少 種新型式的事物。 情況7 :(關閉)如果S K U /屬性值在先前的桶狀區間中,而 不在目前的桶狀區間中,則會降低1,否則會降低〇。當從 桶狀區間到桶狀區間移動時,通常會用來限制可移除多少 種型式的事物。 參照圖1 5 A ’其為用來判斷限制可行性之流程1 5 〇 〇 (通常 由圖4的步驟414來表示)。限制可行性流程15〇〇會試圖找 出谷量限制上的桶狀區間,其中訂單為應用到它的所有限 制(容量及附屬)都是可行的。限制可行性程序丨5 〇 〇會涉及 許多步驟。程序1 500係基於在實施程序之前所熟知的許多 參數。例如,從先前的步驟中,要製造的訂單需求量及用 於訂單的材料可用日期係假設為可用的。再者,由於先前 的步驟,用於訂單的列入計畫表區間是已知的。也基於先 刖的步驟,目標資源(例如,可允許資源)是已知的。底下 曰k供流私丨5 〇 〇的簡短說明,緊接著為圖1 5 a中的某些步 驟4更詳細的說明。當用於規劃的訂單之一組限制已決定 出來時’程序1 500會開始於步驟1 502。用於訂單的此組限 -98- (94) --- (94) ---200305088 制包括用於資源的容量及附屬限 项吸制。在步驟1 504,會判斷 有效列入計畫表區間。換句話誇 ^ 窄化使用組態的最早 材料可用性之正確的列入計畫表 —衣£間。在步驟1 5 0 6,會判 斷是否凍結SAD群組會描述訂單 平。如果凍結SAD群組描述 此訂單,則此訂單會安置在容 ^ 限制的桶狀區間内,其中 在步驟1 5 0 8,有效需求曰期會 H下降。項目「安置」會使用 ’因為訂單尚未列入計畫表中。 曰則會試圖安置訂單的資 源只是在此組的可允許資源之資 ^ σ ’原中的一個。也要注意的 疋,底下會敘述的訂單安置評估 %序,會用來評估目前資 源上的列入計畫表機會(安置)。〇 /、有在找出最佳列入計書 表機會之後,訂單才會列入計書 〜 Τ忽表中。在步驟1510,程序 會跳到限制可行性程序15叫的其”驟,並且會直⑭ 到步驟421的訂單安置評估步驟。如果沒有描述訂單的柬 結SAD群組,則在步驟1512,會決定用於訂單的列入計畫 表控制。在步驟15 14,會搜尋可行的桶狀區間。在圖15八 的步驟1 504,會做出判斷,以決定有效的列入計畫表區間 。列入计畫表區間可由一個或多個時間區間的交叉點來定 義。時間區間將取決於相關於訂單的各種因素。至少四種 型式的有效列入計畫表區間是可行的。參照圖1 5 B,其為 用來決定基於某些參數之有效列入計畫表區間的程序。在 步驟1 522,會判斷是否有有效需求曰期。例如,(圖4的) 步驟4 0 2會產生非無效的有效需求曰期嗎?如果如此,則 有效需求日期會存在,並且程序會移到步驟1 524。在步驟 1 5 24,會判斷最早(ME)及最晚(ML)是否無效。如果都無 -99- 200305088 (95)In this example, the order quantity is always reduced. For example, if five cars are needed, it will be reduced by a difference of five. Used to limit the number of allowable units. Μ / brother 2 · (1) Reduce the capacity of the bucket interval by one unit per order τ ^ In this example, for orders, always decrease by 1. Used to limit, which limits the total number of allowable orders relative to the quantity produced. Case 3: (UDA) Query the configured values of the attributes of the order / item / SKU. Important attributes, and reduce the capacity of the bucket interval by the value of the order / item / SKU. In this example, the value in the User Defined Attribute (UDA) is used to determine how much to reduce. It is usually used when the user wants to limit the total amount of the order and another attribute that is externally modeled at the same time. For example, suppose that a shipping company would limit how many units a car can transport, and would like to limit the total weight of the shipment. In this example, one person can replay the total of the order into UD A. Case 4: (UDA * Quantity) Query the value of the order / item / SKlj attribute, and if this value is different from the value of the attribute of the order that was previously listed in this state, the capacity will be reduced to zero, and otherwise it will Decrease by 1. In this example, the value in UD A is used and multiplied by the order quantity to determine how much to reduce. Assume that the factory limits how many cars can be made in a day, and limits the number of hours it takes to make a car. In this example, one can put the number of hours it takes to make a car into UD A and multiply it by the number of cars in the order ', the total number of component hours. Case 5: (setting) query the attribute value of the order and determine whether this value exists in the order of the prior (or next) status; if the attribute value does not exist before -97 · 200305088 (93) (or the next ), It will decrease by one unit, otherwise it will decrease by zero. If the SKU / attribute value is not in the existing bucket interval, it will decrease i, otherwise it will decrease 0. The number of types that are usually used for things that can be achieved in buckets. Case 6: (On) If the SKU / attribute value is not in the previous bucket interval, but in the current bucket interval, it will decrease by 1, otherwise it will decrease by 0. When moving from barrel to barrel, it is often used to limit how many new things can be achieved. Case 7: (Off) If S K U / attribute value is in the previous bucket interval, but not in the current bucket interval, it will decrease by 1, otherwise it will decrease by 0. When moving from bucket to bucket, it is usually used to limit how many types of things can be removed. Referring to FIG. 15A ′, it is a flow 150 (usually represented by step 414 in FIG. 4) for judging the feasibility of the restriction. The restriction feasibility process 1500 will try to find the barrel-like interval on the grain limit, in which the order is feasible for all the restrictions (capacity and subsidiary) applied to it. Limiting the feasibility procedure 丨 5 00 will involve many steps. Procedure 1 500 is based on many parameters that were well known before the procedure was implemented. For example, from the previous steps, the order demand to be manufactured and the material availability date for the order are assumed to be available. Furthermore, due to the previous steps, the schedule interval used for the order is known. Also based on the previous steps, the target resource (for example, allowable resource) is known. Below is a brief description of the k supply stream private 5 00, followed by a more detailed description of some steps 4 in Figure 15a. When a set of restrictions for an order for planning has been determined, the procedure 1 500 will begin at step 1 502. This set of limits used for orders -98- (94) --- (94) --- 200305088 system includes capacity and subsidiary limits for resources. In step 1 504, it is judged that it is effectively included in the schedule interval. In other words exaggerate ^ Narrow down the correct listing of the earliest materials available using the configuration plan — clothing. At step 506, it will be judged whether the SAD group is frozen or not. The order level will be described. If the frozen SAD group describes this order, then this order will be placed in a barrel-shaped range with a capacity limit, where the effective demand date will decrease by H at step 1508. The item "Relocation" will use ‘because the order has not yet been listed in the plan. The resource that will try to place the order is just one of the resources in this group of allowable resources ^ σ ′. It should also be noted that, the order resettlement assessment% sequence described below will be used to evaluate the current resource listing opportunity (relocation). 〇 / 、 Orders will not be listed in the schedule until the best opportunity for inclusion in the schedule is found. At step 1510, the program jumps to the step called Limit Feasibility Program 15 and proceeds to the order placement evaluation step of step 421. If there is no SAD group describing the order, then at step 1512, it will decide It is used for order schedule control. At steps 15 and 14, feasible bucket intervals will be searched. At step 1 504 of FIG. 15, a judgment will be made to determine the effective schedule interval. Column The schedule interval can be defined by the intersection of one or more time intervals. The time interval will depend on various factors related to the order. At least four types of effective inclusion in the schedule interval are feasible. Refer to Figure 1 5 B, which is a procedure used to determine the effective inclusion in the schedule interval based on certain parameters. In step 1 522, it is determined whether there is a valid demand date. For example, (Figure 4) step 4 0 2 will produce Is invalid valid demand date? If so, the valid demand date will exist and the program will move to step 1 524. At step 1 5 24, it will be determined whether the earliest (ME) and latest (ML) are invalid. None-99- 200305088 (95 )

效,則有效列入計畫表區間為交叉點A。交叉點A係定義 為以下區間的交叉點: • 在材料可用日期與規劃結束日期之間的區間。 • 在規劃起始日期與規劃結束日期之間的區間。 • 在(有效需求日期-最早)與(有效需求日期+最晚)之 間的區間。 • 在容量限制上之第一桶狀區間的起始日期與容i 限制上之最後桶狀區間的結束日期之間的區間。 如果ME及ML都無效,則在步驟1 5 2 8,有效列入計畫表區 間為交叉點B。交叉點B係定義為以下區間的交叉點: • 在材料可用日期與規劃結束日期之間的區間。 • 在規劃起始日期與規劃結束日期之間的區間。 • 在容量限制上之第一桶狀區間的起始日期與容量 限制上之最後桶狀區間的結束日期之間的區間。 如果訂單沒有有效日期,則在步驟1 5 3 0,會判斷ME及ML 是否無效。如果都無效,則在步驟1 5 3 2,有效列入計畫表 區間將是交叉點C。交叉點C係定義為以下區間的交叉點: • 在材料可用日期與規劃結束日期之間的區間。 • 在規劃起始日期與規劃結束日期之間的區間。 • 在容量限制上之第一桶狀區間的起始日期與容量 限制上之最後桶狀區間的結束日期之間的區間。 如果訂箪沒有有效需求日期,並且ME及ML不是無效,則 在步驟1 5 3 4,有效列入計畫表區間將是交叉點D。交叉點 D係定義為以下區間的交叉點:Effect, the effective inclusion in the schedule interval is intersection A. Intersection A is defined as the intersection of the following intervals: • The interval between the material availability date and the planned end date. • The interval between the planned start date and the planned end date. • The interval between (effective demand date-earliest) and (effective demand date + latest). • The interval between the start date of the first bucket interval on the capacity limit and the end date of the last bucket interval on the capacity limit. If neither ME nor ML is valid, then in step 15 28, the effective inclusion in the plan table area is intersection B. Intersection B is defined as the intersection of the following intervals: • The interval between the material availability date and the planned end date. • The interval between the planned start date and the planned end date. • The interval between the start date of the first bucket interval on the capacity limit and the end date of the last bucket interval on the capacity limit. If the order has no expiration date, at step 1530, it will be judged whether the ME and ML are invalid. If none of them are valid, then in step 1 5 3 2 the valid schedule will be the intersection C. Intersection C is defined as the intersection of the following intervals: • The interval between the material availability date and the planned end date. • The interval between the planned start date and the planned end date. • The interval between the start date of the first bucket interval on the capacity limit and the end date of the last bucket interval on the capacity limit. If the booking does not have a valid demand date, and the ME and ML are not invalid, then in step 1 5 3 4 the valid listing schedule interval will be intersection D. Intersection D is defined as the intersection of the following intervals:

-100- 200305088-100- 200305088

(96) • 在材料可用日期與規劃結束日期之間的區間。 • 在規劃起始日期與規劃結束日期之間的區間。 • 在容量限制上之第一桶狀區間的起始日期與容量 限制上之最後桶狀區間的結束日期之間的區間。 在步驟1 5 1 2中,用於訂單的列入計畫表控制會決定出 來。列入計畫表控制會影響用於可行桶狀區間的搜尋由程 序來做處理之方式。四種型式的列入計晝表控制或目標可 由程序來支援,往前、往後、剛好在時間内(JIT)、以及 「不列入計畫表中」。參照圖1 5 C,其係繪示往前列入計 畫表控制概念的時間線1 5 5 0。在此時間線1 5 5 0中,時間的 相關點為有效列入計畫表區間的起始日期(SDESI) 1552 、有效需求曰期1 5 5 4及有效列入計畫表區間的結束曰期 (EDESI)。時間線會從左側(較早的時間期間)移動到右側(較晚 的時間期間)^如果用於訂單的列入計畫表控制為「往前」 ,則用於可行桶狀區間(其滿足容量限制及所有可用的附 屬限制)的搜尋會開始於容量限制上的桶狀區間,其中有 效列入計畫表區間1 5 0 2的起始日期會降低,並且從那裡往 前移動。安置在第一桶狀區間中的訂單係滿足所有的限制 。如果我們不能在SDEDI 1 5 52與ED EDI 1 5 5 6區間之間的 區間中找出單一可行的桶狀區間,則訂單不能列入計畫表 中。圖1 5 D為繪示往後控制概念的時間線1 5 6 0。如果用於 訂單的列入計畫表控制為「往後」,則用於可行桶狀區間(其 滿足容量限制及所有可用的附屬限制)的搜尋會開始於容 量限制上的桶狀區間,其中有效列入計畫表區間的結束 200305088 (97) 日期會降低,並且以後退方向移動(例如,朝著時間線1 5 6 0 的左側)。安置在第一桶狀區間中的訂單係滿足所有的限 制。如果在SDESI 1562與EDESI 1566區間中的可行區間 不能找出,則訂單不能列入計晝表中。圖1 5 Ε及1 5 F係繪 示JIT列入計畫表控制概念之二種不同的情況之時間線 1570及1580。在第一種情況(圖15Ε)中,訂單具有有效需 求日期1 5 74。如果訂單有有效需求曰期1 5 74,則系統首先 會嘗試將訂單安置在容量限制上的桶狀區間中,其中有有 效需求日期會降低。如果此桶狀區間不可行,則系統會以 往後方向(列入計畫表早)進行,直到抵達SDESI 1 572日期 。如果判斷出在SDESI 1 5 72與有效需求日期1 574之間的 區間中,沒有桶狀區間是可行的,則系統會以往前方向進 行,從有效需求日期1 5 74開始。如果判斷出在有效需求曰 期1 574與EDESI 1 5 76之間的區間中,沒有桶狀區間是可 行的,則訂單不能列入計畫表中。圖1 5F係繪示第二種JIT 情況的時間線1 5 8 0,其中訂單沒有有效需求曰期。如果訂 單沒有有效需求日期且如果列入計畫表控制型式為ΠΤ, 則動作非常類似於「往前列入計畫表」。在此例中,系統 會藉由優先察看容量限制上的桶狀區間,而開始尋找可行 桶狀區間,其中SDESI 1 5 82會降低,並且會以往前方向 進行搜尋可行桶狀區間(其滿足容量限制及所有可用的附 屬限制)。安置在第一桶狀區間中的訂單係滿足所有的限 制。如果在SDESI 1 5 82與EDESI 1 5 84之間的區間不能找 出可行區間,則訂單不能列入計畫表中。 200305088(96) • The interval between the material availability date and the planned end date. • The interval between the planned start date and the planned end date. • The interval between the start date of the first bucket interval on the capacity limit and the end date of the last bucket interval on the capacity limit. In step 1 5 1 2 the schedule control for the order is determined. The inclusion of a schedule control affects the way the search for feasible bucket intervals is handled by the program. The four types of daily schedule control or goals can be supported by procedures, forward, backward, just in time (JIT), and "not included in the schedule". Referring to FIG. 15C, it shows a timeline 1550 that was previously included in the control concept of the schedule. In this timeline 1 550, the relevant points of time are the start date (SDESI) 1552, the effective demand date 1 5 5 4 and the end of the effective schedule interval. Period (EDESI). The timeline will move from the left (earlier time period) to the right (later time period) ^ If the listing schedule used for the order is controlled to "forward", it will be used for the feasible bucket interval (which meet The capacity limit and all available ancillary limits) are searched starting from bucket intervals on the capacity limit, where the effective date for inclusion in the schedule interval 1 50 2 will decrease and move forward from there. Orders placed in the first bucket interval satisfy all restrictions. If we can't find a single feasible barrel interval in the interval between SDEDI 1 52 and ED EDI 1 56, the order cannot be included in the plan. Fig. 15D is a timeline 1560 showing the concept of future control. If the inclusion schedule for an order is controlled to be "backward", the search for a feasible bucket interval (which satisfies the capacity limit and all available ancillary restrictions) will begin at the bucket interval above the capacity limit, where The end of the effective schedule period 200305088 (97) date will decrease and move backward (for example, to the left of the timeline 1 5 6 0). Orders placed in the first bucket area meet all restrictions. If the feasible interval between SDESI 1562 and EDESI 1566 cannot be found, the order cannot be included in the day meter. Figures 15E and 15F show timelines 1570 and 1580 for two different cases where JIT is included in the control concept of the schedule. In the first case (Figure 15E), the order has a valid demand date of 1 5 74. If the order has an effective demand date of 1 5 74, the system will first try to place the order in a bucket interval on the capacity limit, where the effective demand date will decrease. If this bucket interval is not feasible, the system will proceed in the backward direction (early in the schedule) until it reaches the SDESI 1 572 date. If it is determined that in the interval between SDESI 1 5 72 and the effective demand date 1 574, no barrel-shaped interval is feasible, the system will proceed in the previous direction, starting from the effective demand date 1 5 74. If it is determined that in the interval between effective demand date 1 574 and EDESI 1 5 76, no barrel interval is feasible, the order cannot be included in the plan. Figure 15F shows the timeline of the second JIT situation 1580, where the order has no effective demand date. If the order does not have a valid demand date and if it is included in the schedule control type as ΠT, the action is very similar to "list in the schedule forward". In this example, the system will look for feasible bucket intervals by first looking at the bucket intervals on the capacity limit, where SDESI 1 5 82 will be reduced and will search for feasible bucket intervals in the previous direction (which meets the capacity Restrictions and all available ancillary restrictions). Orders placed in the first bucket area meet all restrictions. If a feasible interval cannot be found between SDESI 1 5 82 and EDESI 1 5 84, the order cannot be included in the schedule. 200305088

(98) 用於訂單之列入計畫表控制的決定通常會基於使用者 偏愛。例如,為了降低儲存成本,很多製造商喜愛ΠΤ方 法。另一種是,某些使用者會使用取決於情況之超過一種 型式的控制。 在(圖1 5 A)的步驟1 5 1 6,會做出可行桶狀區間的搜尋。 一旦用於訂單的列入計畫表控制已決定出來,可安置訂單 的可行桶狀區間會基於列入計畫表控制及如資源限制之 上述的其他因素來決定。只有在確定所有限制(容量及可 用的附屬)的可行性之後,ABP系統1 00才會將訂單安置於 桶狀區間中。搜尋動作可藉由用於訂單的列入計畫表控制 來引導。當有許多種機制可用於搜尋列入計畫表區間中的 所有桶狀區間時,所採用的機制主要應該強調速度。在此 方法背後的基本原則係如下。 資源容量限制係用來當作搜尋機制中的「固定限制」。 可假設容量限制在所有限制中,具有最微小的粒狀。程序 係藉由檢查容量限制上之想要的桶狀區間中的容量而開 始。許多規則可決定那些桶狀區間將是想要的桶狀區間。 如果在想要的桶狀區間中,足夠的容量是可用的,則第 一附屬限制會再檢查可行性(如跨過限制的移動可稱為「 垂直移動」)。如果足夠的容量可用於第一附屬限制,則 「垂直移動」可用於第二附屬限制。同樣地,如果足夠的 容量可用於第二附屬限制,則垂直移動可用於第三附屬限 制。然後,這些垂直移動步驟當然會繼續重複其他的附屬 限制。如果,在時間内的任何點,所找出的限制在我們優 -103- 200305088(98) Decisions for inclusion in the schedule control of orders are usually based on user preference. For example, to reduce storage costs, many manufacturers prefer the UIT method. Another is that some users will use more than one type of control depending on the situation. At step 1 5 1 6 (Figure 1 5 A), a search for a feasible bucket interval is made. Once the schedule control for the order has been determined, the feasible barrel interval for placing orders can be determined based on the schedule control and other factors such as resource constraints mentioned above. Only after determining the feasibility of all restrictions (capacity and available ancillary), the ABP system 100 will place the order in the barrel section. The search action can be guided by a schedule control for the order. When there are many mechanisms that can be used to search for all barrel-like intervals included in the schedule interval, the mechanism used should mainly emphasize speed. The basic principles behind this method are as follows. Resource capacity limits are used as "fixed limits" in the search mechanism. It can be assumed that the capacity is limited to all limits with the smallest graininess. The procedure starts by checking the capacity in the desired bucket interval on the capacity limit. Many rules can determine which bucket intervals will be the desired bucket intervals. If sufficient capacity is available in the desired bucket interval, the first ancillary limit is checked again for feasibility (eg, movement across the limit may be referred to as "vertical movement"). If sufficient capacity is available for the first auxiliary limit, "vertical movement" can be used for the second auxiliary limit. Similarly, if sufficient capacity is available for the second subsidiary restriction, vertical movement can be used for the third subsidiary restriction. These vertical movement steps will then of course continue to repeat other ancillary restrictions. If, at any point in time, the limit found is our best -103- 200305088

先察看的桶狀區間中,沒有足夠容量’則會做出跨過限制 上的桶狀區間之往後或往前(取決於列入計畫表控制及已 察看的桶狀區間)的搜尋。直到滿足訂單上的需求量之限 制上的桶狀區間找出,這才會完成。跨過單一限制上的多 個桶狀區間之如此的移動稱為「椒向移動」。有可用於橫 / 向及垂直移動之各種規則。 二、 每當在附屬限制上,有橫向移動時’為了找出可行桶狀 · 區間,容量限制必須再次重新檢查。例如,每當在附屬限 制上,有「橫向移動」時,為了找出可行桶狀區間,較佳 _ 而言,容量限制會再次重新檢查。因此,系統會「垂直移 動」到容量限制、在容量限制1「橫向移動」(如果必要) 、垂直移動到第一「附屬限制」、在第一附屬限制上橫向 移動}(如果必要)、再次「棄直移動」到谷里限制,如果 在第-附屬上有「橫向移動」等等。鈔,假設有三種限 制,A、B及C , 1〇個桶狀區間,A總是可用的,B可用桶 狀區間3、4、7、8、9、1〇,以及C可用桶狀區間丨、2、5 、6、7、8、9、10 ,並且材料可以桶狀區間U故為起始。鲁 進一步假設想要往前列入計畫表中,以及沒有玎單起始日 . 期❶然後較佳而言,系統將會開始檢查在桶狀區間1的限 ' 制。在此例中,首先會檢查A1,如果良好,則會做垂直,· 移動,並且檢查B 1及找出問題。接著,會選擇檢查限制 A2或B2。ΛΒΡ系統1〇〇在返同及檢查A之前,會找出下個 可用的桶狀區間。在此例中,會找出桶狀區間3係可用於 B,然後會重新開始檢查A3。一般而言,如果B比C更為 -104- 200305088In the bucket section viewed first, if there is not enough capacity ’, a search will be made to go backward or forward across the bucket section on the limit (depending on the schedule table control and the bucket section viewed). This will not be completed until the barrel interval on the limit of the demand on the order is met. Such a movement across multiple barrel-shaped intervals on a single limit is called a "pepper direction movement". There are various rules that can be used for horizontal / vertical and vertical movement. 2. Whenever there is a lateral movement on the subsidiary limit, in order to find a feasible barrel-shaped interval, the capacity limit must be checked again. For example, whenever there is a "lateral movement" on the auxiliary limit, in order to find a feasible bucket interval, it is better that _, the capacity limit will be checked again. Therefore, the system will "vertically move" to the capacity limit, "transversely move" at capacity limit 1 (if necessary), move vertically to the first "affiliate limit", move laterally at the first subsidiary limit} (if necessary), "Abandon straight movement" to the valley limit, if there is "horizontal movement" on the first subsidiary and so on. Banknotes, assuming three restrictions, A, B, and C, 10 bucket intervals, A is always available, B can use bucket intervals 3, 4, 7, 8, 9, 10, and C can use bucket intervals丨, 2, 5, 6, 7, 8, 9, 10, and the material can start with a barrel-shaped interval U. Lu further assumes that he wants to be included in the plan table forward, and that there is no start date of the order. Period. Then, preferably, the system will start checking the limit in the bucket interval 1. In this example, A1 will be checked first, if it is good, it will be vertical, move, and check B 1 and find the problem. Next, check the limits A2 or B2. The ΛBP system 100 will find the next available bucket interval before returning to A and checking A. In this example, it will find that the barrel interval 3 series is available for B, and then it will restart checking A3. In general, if B is more than C -104- 200305088

(100) 限制的,使用者的最佳愛好可將限制B安置在C之前。這 可降低檢查的數量。 實質上,搜尋通常包括跨過限制的「垂直移動」,以及 跨過限制上的桶狀區間之「橫向移動」。搜尋會持續,直 到滿足二種情況中的一個: 1 ·滿足所有附屬限制之容量限制上的可行桶狀區間 會找出來。在此例中,訂單可安置於所找出的可行 桶狀區間,並且繼續進行訂單安置評估步驟。 2.在經由整個列入計畫表區間的搜尋中,沒有找出單 一可行的桶狀區間。在此例中,訂單不可安置於目 前的資源上。所以系統會試圖將訂單安置於可允許 資源的清單中的下個資源上。此會涉及下個資源上 之限制可行性評估的重複。如果目前資源為可允許 資源之清單中的最後資源,則系統會離開資源迴路 ,從可允許SKU的清單中提取下個SKU,以及重複 使用下個SKU之從步驟408(FG SKU初始)往前的程 以下所提供的例子係顯示以上的概念。在此例中,會試 圖將訂單列入資源R 1上的計畫表中。此訂單具有以下的 特徵: • 有效需求日期:6星期中的3天 • 有效列入計畫表區間:(4星期的起始日期,8星期的結 束曰期) •訂單數量=1 -105- 200305088 (101)(100) Restricted, the user's best interest may place restriction B before C. This reduces the number of checks. In essence, search usually includes "vertical movement" across the limit and "horizontal movement" across the barrel-like interval on the limit. The search will continue until one of the two cases is met: 1 · A feasible bucket interval on the capacity limit that satisfies all subsidiary limits will be found. In this example, the order can be placed in the identified feasible bucket interval, and the order placement evaluation step continues. 2. In the search through the entire schedule interval, no single feasible bucket interval was found. In this example, orders cannot be placed on current resources. So the system will try to place the order on the next resource in the list of allowed resources. This would involve the duplication of the feasibility assessment on the next resource. If the current resource is the last resource in the list of allowable resources, the system will leave the resource loop, extract the next SKU from the list of allowable SKUs, and reuse the next SKU from step 408 (FG SKU initial) forward The examples provided below show the above concepts. In this example, an attempt is made to include the order in the plan table on resource R1. This order has the following characteristics: • Effective demand date: 3 days in 6 weeks 200305088 (101)

列入計畫表控制=使用的JIT限制係如下: • 用於資源R 1之資源容量限制 • 二種附屬限制(限制Α及Β) 參照圖1 6,其為用以找出基於以上所列出之特徵及限制 的滿意時間桶裝區間之範例的搜尋程序中的真實表示之 方塊圖1600。圖1600包含由分隔線所表示之區分成星期時Included in the schedule control = JIT restrictions used are as follows: • Resource capacity restrictions for resource R 1 • Two subsidiary restrictions (restrictions A and B) Refer to Figure 16 for the purpose of finding out based on the above list A block diagram 1600 of the true representation in the search procedure for an example of the bucketing interval of the satisfactory time and the characteristics and limitations. Figure 1600 contains the day of the week divided by the dividing line

間期間之三列(1 6 0 2到1 6 0 6)的 一 ------〜二喱P良制肩 容量限制1 602,以及附屬限制,限制a 16〇4及限制β 16〇 。在此,星期時間期間1 6 0 7係表示桶狀區、 八u间。頂邵列1 6 0 係表示依照每個星期的容量限制(如由在 U由每個分隔線内的奏 目所表示)之可用的數量(亦即,容量 一 y、 。中間列1 604係I 不依照每個星期的限制A之可用的|田,、取I ( 3F即,容Θ 虑 部列1 606係表示依照每個星期的限制Β、 夏) 即,容量)。為了滿意地將訂單安置於可用的數量(功 間中(在此例中,桶狀區間為星期的 疋的時間桶狀1 J W Ιηε間),必須 知桶狀區間的每個限制之足夠的容量。♦、:,、啕用於C: 6星期的中間,如由i 6 0 8所表示。有长曰期會落於舅 β致列入朴全主 會在第4星期開始,而在第8星期钻 w !表區間1 6 1 、J、、々束。因為列人斗+主ρ 制係設定成JIT,所以系統會試圖將 ,匕表拍 日期的訂單中。因此,搜尋會開 取接近需,I # , _ ,, . 〇於時間桶狀區間162 ,其中需求日期1608會落於其中,』 匕间 A S *5- ^ r 1 \ ^ 口由^一所表示。!^ 為玎早數里(=1)與依照容量限制 ^ 、从&gt;r m批田上 (如顯不於分隔線1 620 Φ )的可用數篁相同,所以用於第6星 中 生期 &lt; 谷量限制的容吾 令人滿意的。接著,會做出厂垂 夏移動J到分隔線162One of the three columns (1 6 2 to 1 6 0 6) between periods ------ ~ Erli P. Good shoulder capacity limit 1 602, and ancillary limit, limit a 16〇4 and limit β 16〇 . Here, the week time period 16 0 7 indicates a barrel-shaped area and eight rooms. The top column 1 60 represents the available quantity (ie, the capacity y,.) In the middle of the weekly capacity limit (as represented by the repertoire within each division line in U). The middle column 1 604 is I does not comply with the limits of each week. A, available, take I (3F, that is, the capacity Θ consideration column 1 606 means that according to the limits of each week B, summer) (that is, capacity). In order to satisfactorily place the order in the available quantity (in this case, the bucket interval is the time of the week, the bucket interval is 1 JW Ιηε), it is necessary to know the sufficient capacity of each limit of the bucket interval . ♦,: ,, 啕 are used in the middle of C: 6 weeks, as indicated by i 6 0 8. There is a long date that falls on 舅 β. 8 weeks to drill w! Watch interval 1 6 1, J,, 々 bundle. Because the column fighting + main ρ system is set to JIT, the system will try to order the date of the dagger watch. Therefore, the search will open To be close, I #, _ ,,. 〇 is in the time bucket interval 162, in which the demand date 1608 will fall among them. "Dagger AS * 5- ^ r 1 \ ^ The mouth is represented by ^ one. ^ Is 玎Earlier miles (= 1) are the same as the available numbers from the field of >> rm (if it is less than 1 620 Φ) according to the capacity limit ^, so it is used for the 6th star during the growing period &lt; grain limit Rongwu is satisfactory. Next, the factory will be made to move J to divider 162

-106 - 200305088 (102)-106-200305088 (102)

。分隔線1 6 2 2係表示在第6星期中之限制A的容量。垂直 移動會實施,以判斷限制A的容量是否足夠。在此例中, 分隔線1 6 2 2的容量為零。因此,限制A的容量不是令人滿 意的,並且系統會「水平地移動」到較早的桶狀區間,以 定位具有足夠容量的桶狀區間。用於第5星期的時間桶狀 區間也不是令人滿意的,因為在第5星期中之限制A的容 量(如顯示於分隔線1 623中)為零。在此例中,系統會找出 分隔線1624中的容量,其表示在第4星期中之限制A的容 量是足夠的。然而,因為系統必須離開先前的桶狀區間(亦. The dividing line 1 6 2 2 indicates the capacity of the limit A in the 6th week. Vertical movement is implemented to determine whether the capacity of limit A is sufficient. In this example, the capacity of the dividing line 1 6 2 2 is zero. Therefore, limiting the capacity of A is not satisfactory, and the system “moves horizontally” to an earlier barrel section to locate a barrel section with sufficient capacity. The time bucket interval used for week 5 is also not satisfactory because the capacity of limit A in week 5 (as shown in divider 1 623) is zero. In this example, the system will find the capacity in the divider line 1624, which means that the capacity of limit A in the 4th week is sufficient. However, because the system must leave the previous bucket interval (also

即,第6星期),所以系 限制),並且重新檢查用於容量限制的第4星期的容量。g 此,從分隔線1 624,系統會垂直地移動到分隔線1 626,y: 判斷在第4星期中之容量限制的容量是否足夠。在此例今 ,有足夠的容量位於分隔線1 626中(如由分隔線1 626中知 數量「1」所表示)。因此,系統會經過分隔線1624,以j 新檢查及判別在第4星期中之限制A的容量是否足夠 較早產生的)。另一種是,重新檢查分隔線1624的容量$ 步驟會忽略,因為分隔線1624的容量已判斷為令人滿意合 然後,系統會垂直地移動到分隔線1 62 8,以判斷在第 星期中之限制B的容量是否足夠。因為用#限制B之第4』 期中的容量是零’所以系統必須移動到底部列中的另一 4 ::區間。然而,因為有效列入計晝表區間i6i〇會在第 :結束,所以系統不會移動到較早的桶狀區間。因此 ’、項移動到右邊或較晚的時間桶狀區間'然後系統會心That is, week 6), so it is a limit), and recheck the capacity of week 4 for capacity limitation. g. From divide line 1 624, the system will move vertically to divide line 1 626, y: Determine whether the capacity limit capacity in the 4th week is sufficient. In this case, there is enough capacity in divider line 1 626 (as indicated by divider line 1 626 the number "1"). Therefore, the system will pass the dividing line 1624 to newly check and judge whether the capacity of the limit A in the 4th week is enough to be generated earlier). The other is that the step of rechecking the capacity of the divider 1624 will be ignored because the capacity of the divider 1624 has been judged to be satisfactory. Then, the system will move vertically to the divider 1 62 8 to determine the Restrict whether the capacity of B is sufficient. Because the capacity in period # 4 of #Limit B is zero ', the system must move to another 4 :: interval in the bottom column. However, the system will not move to the earlier bucket interval because the effective inclusion in the daily meter interval i6i〇 will end at:. So ‘, the item moves to the right or a later time bucket’ and then the system knows

-107- 200305088 (103)-107- 200305088 (103)

第5及6星期(分隔線1630及1632),因為已發現在那些星期 中,用於限制A的容量是不足的(如分隔線1 622及1 62 3所 顯示)。然而,用於限制B之第7星期的容量是足夠的,如 分隔線1 6 3 4所表示。然後系統移回到容量限制,以判斷在 第7星期中之用於容量限制的容量是否足夠。分隔線1 636(其 為在第7星期中之用於容量限制的容量)係表示用於此桶 狀區間的容量限制有零容量。因此,系統會移動到下個(較 晚)的桶狀區間。在分隔線1 63 0,系統會決定在第8星期中 之容量限制的容量是滿意的。因此,系統會移動到分隔線 1640,其表示第8星期中之容量限制A的容量,並且會決 定也已滿足的容量。然後系統會移動到分隔線1 6 5 0,其表 示第8星期中之容量限制B的容量,並且會找出也令人滿 意的容量。因此,在第8星期中,所有的三種限制(1 602 到1 6 0 6)是令人滿意的,並且搜尋會結束。 用來找出「想要的」桶狀區間之規則也會實施。想要 的桶狀區間為最想要的桶狀區間。因此,在大部分的情況 中,第一桶狀區間會檢查可行性(在上例中,其為第6星期 的桶狀區間)^想要的桶狀區間之識別將取決於如列入計 畫表控制的許多因素。例如,如果列入計畫表控制為ΠΤ ,並且如果訂單具有如上所顯示之非無效的有效需求日期 ,則想要的桶狀區間將包含訂單的有效需求日期之桶狀區 間。如果列入計畫表控制設定為「往前」或列入計畫表控 制為ΠΤ,並且訂單沒有有效需求日期,則想要的桶狀區 間將包含有效列入計畫表日期的起始日期之桶狀區間。最Weeks 5 and 6 (divided lines 1630 and 1632), as it has been found that the capacity to limit A is insufficient in those weeks (as shown by the divided lines 1 622 and 1 62 3). However, it is sufficient to limit the capacity of Week 7 of B, as indicated by the dividing line 1 6 3 4. The system then moves back to the capacity limit to determine if the capacity for capacity limit during the seventh week is sufficient. Divider line 1 636 (which is the capacity used for capacity limitation during Week 7) indicates that the capacity limitation used for this barrel section has zero capacity. As a result, the system moves to the next (later) bucket interval. At divide line 1 63 0, the system will decide that the capacity limit in the eighth week is satisfactory. Therefore, the system moves to the divider line 1640, which indicates the capacity of the capacity limit A in the eighth week, and determines the capacity that has also been satisfied. The system will then move to the divider line 1650, which indicates the capacity limit B in the 8th week and will also find a satisfactory capacity. Therefore, in week 8, all three limits (1 602 to 16 0 6) are satisfactory and the search will end. The rules used to find "want" bucket intervals will also be implemented. The desired barrel interval is the most desired barrel interval. Therefore, in most cases, the first bucket interval will be checked for feasibility (in the above example, it is the bucket interval of the 6th week) ^ The identification of the desired bucket interval will depend on the Many factors of drawing table control. For example, if the inclusion schedule control is ΠT, and if the order has a non-invalid valid demand date as shown above, the desired bucket interval will contain the bucket interval of the effective demand date of the order. If the inclusion schedule control is set to "forward" or the inclusion schedule control is ΠΤ, and the order has no valid demand date, the desired bucket interval will contain the start date of the effective schedule date Bucket interval. most

-108- 200305088-108- 200305088

(104) 後,如果列入計畫表控制為往後,則想要的桶狀區間將包 含有效列入計畫表區間的結束日期之桶狀區間。 在圖4的步驟416中,ABP系統ι〇〇會檢查材料容量相容 性。這意謂系統1 〇〇會藉由遞回地產生用於成品sκυ及其 次要項目之任何必要的列入計畫表收據,而重新檢查組態 /資源桶狀區間機會的可行性。收據係用來訂購用於規劃 程序的補充步驟之材料。較佳而言,用於成品SKU的收據 應忒在已找出製造谷量之桶狀區間的開始時產生。對於次 要項目SKU而T ’列入計畫表的收據應該基於母SKU的出 貨時間而往後推。對於任何的SKU而言,如果在桶狀區間 中’要叮講的數需求多於用於S K U的週期最大值,則列 入計畫表的收據會產生用於先前的桶狀區間。這些應該是 可汀購材料之至少一段或一組期間,因為週期最大值檢查 曰在材料可行性步驟期間完成。如果最小/增加/最大規則 使材料在此變為不可行的,則組態/資源/桶狀區間組合將 也是不可行的。在這樣的情況中,系統1 〇〇將會繼續到下 個組態◊對於任何次要項目而言,如果用於SKU的BOM 關係’以及在製造或補充sKU的期間,次要項目是不正確 的’則组態是不可行的。程序會繼續下個組態。 在步驟41 8中,ABP系統100會評估用於FG SKU之每個 桶狀區間/資源機會,並且會選擇最佳的桶狀區間/資源組 合(顯示於步驟422中)。這通常可藉由將每個機會分級, 並且選擇具有最佳等級的機會來達成。 較佳而言,在開始桶狀區間/資源機會的真實評估之前 -109- 200305088(104) Later, if the listing schedule is controlled backwards, the desired bucket interval will contain a bucket interval that is effectively included in the end date of the schedule interval. In step 416 of FIG. 4, the ABP system ιOO checks the material volume compatibility. This means that the system 100 will recheck the feasibility of configuration / resource bucket opportunities by recursively generating any necessary schedule receipts for the finished product sκυ and its minor items. Receipts are used to order materials for additional steps in the planning process. Preferably, the receipt for the finished SKU should be generated at the beginning of the barrel section where the amount of manufacturing grain has been found. For minor item SKUs, the receipt of T ′ in the schedule should be pushed back based on the delivery time of the parent SKU. For any SKU, if the number of requests in the bucket interval is greater than the maximum period value used for SKU, the receipt listed in the schedule table will be generated for the previous bucket interval. These should be at least one period or a set of periods for the available materials, because the cycle maximum check is done during the material feasibility step. If the min / increase / max rule makes the material infeasible here, then the configuration / resource / barrel interval combination will also be infeasible. In such a case, the system 100 will continue to the next configuration. For any secondary item, if the BOM relationship for the SKU is used, and the secondary item is incorrect during the manufacturing or supplementary sKU 'The configuration is not feasible. The program continues with the next configuration. In step 418, the ABP system 100 will evaluate each bucket interval / resource opportunity for the FG SKU and will select the best bucket interval / resource combination (shown in step 422). This is usually achieved by grading each opportunity and choosing the opportunity with the best rating. Better yet, before starting a true assessment of the bucket interval / resource opportunity -109- 200305088

(105) 多、’及目標函數將會定義出來。目標函數會計算向量(或 等級)’其入口為用於每級的目標之等級。在每級,等級 為藉由規律所給予的等級之權重和。規律表會產生及用來 定義規律中的每個。此表可進一步定義用於每級的目標之 t 1值及容忍度,以判斷在已知級的二個不同等級是否應 茨視之為相等。一旦此表已建立,資源/桶狀區間機會可 使用多級目標函數來分級。(105) Multi, ′, and objective functions will be defined. The objective function calculates a vector (or rank) 'whose entry is the rank for the goal of each rank. At each level, the level is the sum of the weights of the levels given by law. A rule table is generated and used to define each of the rules. This table can further define the t 1 value and tolerance for the goals of each level to determine whether two different levels at a given level should be considered equal. Once this table has been established, the resource / bucket interval opportunities can be ranked using a multilevel objective function.

較佳而言,ABP系統1〇〇會併入多級目標函數,以決另 &quot;丁單的最佳安置。如果ABP系統1〇〇找出用於規劃訂單 多個機會,則目標函數會用來量測每個機會及選擇最佳令 個。每個機會會基於多級目標函數的每個物件來分級 目祆函數係由一組規律所組成。至少三種規律是可用的 晚(規劃訂單對用於訂單的有效需求日期之量測)、總使月 (在規劃訂單之容量限制上的桶狀區間多滿之量測)、以方 運輸(在製造訂單之資源的位置與訂單上的客戶位置之探 的運輸成本)。組成目標的規律可將階層,或等級分組。 在一等級内的每個規律可以是加權的。目標可使用一種^ 多種規律。例如,為了使延遲訂單的數目最小化之商業 施模型化,由剛好晚的規律所組成之目標 規律將是具有1的權重之一等級的—個規律 件可使延遲訂單的數目最小化,以及如果訂單可以g的丰 種資源來组成,並且用於每種資源的晚規律都θ 7超過-則會選擇使運輸成本最小的資源送到客戶位置=相同的 化此商業實施,具有二種規律及二種等級 1了模3 ㈡知會產生 -110- (106) 200305088 晚規律為-等級的-個規徐。、 律。這意謂當有使- 運輸規律為一等級的二個規 改善訂單(由客戶所指定,置的機會時,如果一種位置可 成本為何,將會使用它。$各忍度)的時間線,無論運輸 訂單需求,會使用具有最另—万面,如果二種位置可滿足 義用於每個等級的目標。二運輪成本的位置。容忍度可定 度會使用。如果所比較之:比較目標時,用於等級的容忍 目會视為相等。例如,目:個數目的差低於容忍度,則數 如果在一位置之製造訂單?主要規律為運輸成本’但是 會使用晚規律來選擇最佳位成本對另-個係在ι〇元内’則 標來計算◊向量中的每個元置。等級(其為向量)係藉由目 之等級的權重和。二種向=為由單-階層的規律所計算 較。第-對以素會做比較級會以元素接著元素來做比 層所定義的容忍度内),下—如果它們是相等的(在此階 類。如果它們不相等,較低:對的元素會做比較。諸如此 會檢查其後的階層。.^素會視為較佳的,並且不Preferably, the ABP system 100 will incorporate a multi-stage objective function to determine the best placement of Ding Dan. If the ABP system 100 finds multiple opportunities for planning orders, the objective function will be used to measure each opportunity and select the best order. Each opportunity is classified based on each object of the multi-level objective function. The objective function is composed of a set of laws. At least three rules are available late (measurement of planned order to the effective demand date for the order), total month (measurement of how full the barrel-shaped interval on the planned order capacity limit), and shipping by side (in The location of the manufacturing order's resources and the customer's location on the order's shipping costs). The laws that make up a goal can be grouped into levels, or levels. Each law within a level can be weighted. The goal can use one ^ multiple rules. For example, in order to model the commercial implementation of the number of delayed orders, the target rule composed of the rules that are just too late will be one level with a weight of 1-a rule that minimizes the number of delayed orders, and If the order can be composed of a variety of resources, and the late rule for each resource exceeds θ 7-the resource that minimizes the transportation cost will be selected and sent to the customer's location = the same implementation of this commercial implementation has two rules And two grades of 1 and 3 are known to produce -110- (106) 200305088. The regularity is-grade-a rule. Li. This means that when there is a two-tier improvement order that makes the transportation law a level (as specified by the customer, the opportunity is set, if a location can cost what, it will be used. $ Each tolerance) timeline, Regardless of the transportation order requirements, the one with the most other-ten thousand faces will be used, if the two positions can meet the goals defined for each level. The location of the second shipping cost. Tolerance can be used with certainty. If compared: Tolerances for levels are considered equal when comparing goals. For example, the difference between the number of items is lower than the tolerance. If the number is a manufacturing order at one location? The main rule is the transportation cost ', but the late rule will be used to select the best bit cost for the other one. 'The standard is used to calculate each element in the unitary vector. The rank (which is a vector) is the sum of the weights by the rank. The two kinds of direction = are calculated by the uni-level rule. The first-pair of primes will be compared with the element and then the elements will be compared within the tolerance defined by the layer), and next-if they are equal (in this order class. If they are not equal, lower: pair of elements Will compare. Such as this will check the subsequent hierarchy .. ^ prime will be considered better, and not

一旦在可接受位置的所 ^ p^ _ 貪/原評估出來,並且用最佳資 源已選擇用於此位置,如 .Λ . 在步驟424有任何的話’程序 4 〇 〇曰重複在其他可接香 、 、 、置的每一個之評估每個桶狀區 間/資源機會的步驟。如 郛 果不再有可接受位置,則在步驟 426會選擇最佳位置/資源/桶狀區間機會,並且在步驟u名 ,會將訂單分配到此機會。然後在步驟43〇,程序4〇〇會判 斷疋否再有未列入計畫表的訂單。如果有較多的未列入計 畫表訂單,則會選擇下個最高優先權的未列入計畫表訂單 • 111 (107) 200305088Once all ^ p ^ _ greedy / original in the acceptable position has been evaluated, and the best resources have been selected for this position, such as .Λ. If there is any in step 424 'Procedure 4 〇〇〇 repeated in other accessible Steps to evaluate each bucket interval / resource opportunity for each of the incense,,, and set. If there is no longer an acceptable position, then the best position / resource / barrel interval opportunity will be selected in step 426, and the order will be assigned to this opportunity in step u. Then at step 43, the program 400 judges whether there are no more orders not listed in the schedule. If there are more unscheduled orders, the next highest unscheduled order will be selected • 111 (107) 200305088

#且會重複評估及選擇用於此訂單之最佳位置/資源/ 桶狀區間機會Μ # + ^ 勺“序。然而,如果不再有要規劃的訂單, 則程序400會結束。 現在參照圖1 7,其係繪示根據本發明之一具體實施例之 ΑΒ Ρ系統的方塊圖。系統} 7 〇 〇可包括電腦裝置,如個人電 細工作站、词服器或任何其他具有微處理器的裝置。系 統17〇〇可包括資料庫1701,其可包括包含用於未規劃訂單 、:B OM、組態、訂單、以及類似之物的暫時表之一些表 以及可包括運輸矩陣。系統丨7 〇 〇會接收來自使用者1 7 〇 2 的輸入,並且會產生規劃輸出。系統丨7 〇 〇可包括一些模組 ( 1 704到1 722) ’以提供一些功能。例如,系統17〇〇可包括 用來^理〃丁單视窗之視窗管理模組i 7 〇 4。模組1 7 〇 4可用來 組織及管理訂單視窗。例如,視窗管理模組17〇4會選擇即 將要安置的訂單到視窗,並且會將視窗中的那些訂單按優 先順序處理。然後,為了規劃的目的,其可用來選擇最高 優先權的訂單。SKU模組1 706會用來組織、保持、處理、 以及管理sku。同樣地,B0M、組態及SAD群組模組〇7〇8 到17 12)係用來產生、處理及管理BOM、組態及sAD群組 。樣式模組1714係用來產生及管理樣式,其可藉由網路資 源、限制與商業規則、時間桶裝區間、以及類似之物而定 義出來時序/順序模組1716可用來產生時間線及決定程序 ’以及管理時岸事件及時間項目。評估模組1718係用來評 估及選擇各種選擇物’其在根據本發明的程序期間會上升 以評估另一種組態# , It will repeatedly evaluate and select the best location / resource / barrel interval opportunity for this order Μ # + ^ spoon "order. However, if there are no more orders to plan, the process 400 will end. Now refer to the figure 17 is a block diagram showing an AB system according to a specific embodiment of the present invention. The system} 7 00 may include a computer device, such as a personal electronic workstation, a word server, or any other microprocessor with a microprocessor. Device. The system 1700 may include a database 1701, which may include tables containing temporary tables for unplanned orders: BOM, configuration, orders, and the like, and may include a transportation matrix. System 丨 7 〇〇 will receive input from the user 17 〇2, and will produce planning output. The system 丨 〇〇〇 can include some modules (1 704 to 1 722) 'to provide some functions. For example, the system 1700 can Includes a window management module i 7 〇4 to manage the single window. Module 1 704 can be used to organize and manage the order window. For example, the window management module 1704 will select the order to be placed to Window, and will Those orders in the window are processed in priority order. Then, for planning purposes, they can be used to select the highest priority order. SKU module 1 706 will be used to organize, maintain, process, and manage skus. Similarly, B0M, Configuration and SAD Group Modules 0708 to 17 12) is used to generate, process, and manage BOM, configuration, and sAD groups. Style module 1714 is used to generate and manage styles, which can be accessed through the web Sequence resources, restrictions and business rules, time bucket intervals, and the like. The timing / sequence module 1716 can be used to generate timelines and decision procedures' and to manage shore-time events and time items. The evaluation module 1718 is used To evaluate and select various options' which will rise during the procedure according to the invention to evaluate another configuration

。例如,模組1 7 1 8會評估另一種機會, -112- 200305088. For example, module 1 7 1 8 evaluates another opportunity, -112- 200305088

(108) ,以及類似之物。訂單模組 1 7 2 0係用來重新檢查及使訂 單中的資料符合語法。基於以上的說明,熟習此項技術者 將會了解到一些其他模組1 7 2 2也會包含於系統1 7 0 0中。例 如,這些可包括用來管理及實施商業規則、搜尋目標、多 級目標函數、以及類似之物之模組。因此,根據本發明之 一具體實施例之程序及系統可使用軟體及硬體的組合來 實施。(108), and the like. The order module 1720 is used to recheck and make the data in the order comply with the syntax. Based on the above description, those skilled in the art will understand that some other modules 17 2 2 will also be included in the system 1 700. For example, these may include modules for managing and enforcing business rules, search objectives, multi-level objective functions, and the like. Therefore, the program and system according to a specific embodiment of the present invention can be implemented using a combination of software and hardware.

對於熟習此項技術者而言,將會顯然可知的是,在不達 反本發明的精神或範圍,用來規劃本發明之網路資源的利 用之程序及系統可做各種修飾及變化。因此,其是要使本 發明涵蓋在所附申請專利範圍及其同等者之範圍内所提 供的此發明之修正及變化。 圖式簡單說明 所附的圖面係用來提供對於本發明之進一步暸解,並被 加入及構成本申請案的一部份,其說明了本發明的具體實 施例,其結合本說明來解釋本發明的原理。圖式簡單說明 圖1係根據本發明的一具體實施例之系統可運作之範例 的環境之方塊圖; 圖2 A係根據本發明的一具體實施例之初始化程序的流 程圖; 圖2B係根據本發明的一具體實施例之用於規劃資源的 使用,以滿足需求之程序的流程圖; 圖3 A係關於安置初始分配之程序的流程圖; -113- 200305088It will be apparent to those skilled in the art that the procedures and systems used to plan the utilization of the network resources of the present invention can make various modifications and changes within the spirit or scope of the present invention. Therefore, it is intended that the present invention cover the modifications and variations of this invention provided within the scope of the appended patent applications and their equivalents. The attached drawings are used to provide a further understanding of the present invention, and are added to and constitute a part of this application. They illustrate specific embodiments of the present invention, and explain the present invention in conjunction with the description. The principle of the invention. The drawing briefly illustrates that FIG. 1 is a block diagram of an example environment in which a system according to a specific embodiment of the present invention can operate; FIG. 2 A is a flowchart of an initialization procedure according to a specific embodiment of the present invention; FIG. 2B is based on A flowchart of a procedure for planning the use of resources to meet demand in a specific embodiment of the present invention; Figure 3 A is a flowchart of the procedure for initial allocation of resettlement; -113- 200305088

(109) 圖3 B係關於將訂單按優先順序處理之程序的流程圖; 圖3 C係繪示SAD群組、訂單與凍結群組表之間的關係之 方塊圖, 圖4係關於資源規劃,以達成如訂單所定義之需求的程 •序之流程圖。 圖5 A至5 Η係繪示關於資源規劃,以完成訂單之範例的 程序之方塊圖,(109) Figure 3B is a flowchart of the procedure for processing orders in priority order; Figure 3C is a block diagram showing the relationship between the SAD group, the order and the frozen group table, Figure 4 is about resource planning In order to achieve the requirements as defined in the order flow chart. Figures 5 A to 5 are block diagrams showing an example of a procedure for resource planning to complete an order.

圖51係繪示用於範例訂單之訂單屬性值的各種組合之 方塊圖, 圖6係關於決定材料可行性的流程圖; 圖7 Α至7D係繪示在一段時間期間,範例的存貨準位及 需求量之時間線; 圖8A至8C係繪示在BOM中之SAD群組與SKU之間的範 例關係之真實的表示之方塊圖; 圖9係繪示在組態與次要項目SKU之間的範例關係之方 塊圖,Fig. 51 is a block diagram showing various combinations of order attribute values used for the example order, Fig. 6 is a flowchart for determining the feasibility of the materials; And the time line of demand; Figures 8A to 8C are block diagrams showing a true representation of an exemplary relationship between SAD groups and SKUs in the BOM; Block diagram of example relationships between

圖10A及10B係關於藉由製造來補充之程序的流程圖; 圖10C到10F係繪示BOM組的方塊圖; 圖10G係繪示範例的BOM之方塊圖; 圖1 1係關於藉由購買來補充之流程的流程圖; 圖1 2 A到1 2 D係繪示範例的時間事件之時間線; 圖1 3係繪示關於基於特定方案而產生輸出之程序的流 程圖; 圖1 4 A係繪示關於基於特定方案而產生輸出之程序的 -114- 200305088 (110) 流程圖; 圖1 4Β係關於藉由取代來補充之程序的流程圖; 圖1 5 Α係繪示關於決定限制可行性之程序的流程圖; 圖1 5 B係繪示關於決定有效列入計畫表區間之程序的 流程圖; 圖1 5C到1 5F係繪示各種列入計畫表控制概念之時間線; 圖1 6係繪示關於找出令人滿意的時間區間之範例的搜 尋程序之真實的表示之方塊圖;以及Figures 10A and 10B are flowcharts of procedures supplemented by manufacturing; Figures 10C to 10F are block diagrams of BOM groups; Figure 10G is a block diagram of exemplary BOMs; Figure 11 is about purchase by purchase The flow chart of the supplementary process; Figures 1 A to 12 D are timelines of time events of the example; Figure 13 is a flowchart showing the procedure for generating output based on a specific scheme; Figure 1 4 A -114- 200305088 (110) flowchart showing the procedure for generating output based on a specific scheme; Figure 14B is a flowchart about the procedure supplemented by substitution; Figure 1 5A shows that it is feasible to determine restrictions Figure 15B is a flowchart showing the procedure for determining effective inclusion in the schedule table; Figures 15C to 15F are timelines showing various control concepts included in the schedule; Figure 16 is a block diagram showing a true representation of a search procedure for an example of finding a satisfactory time interval; and

圖1 7 係繪示根據本發明的一具體實施例之屬性基礎FIG. 17 shows the attribute basis of a specific embodiment of the present invention.

規劃系統之方塊圖。 圖式代表符號說明 100 ABP系統 101 資料庫 102 製造廠 104 製造廠 106 製造廠 110 資源 120 資源 130 資源 140 材料 350 方塊圖 352 SAD群組 354 訂單 356 訂單 -115- (111) 訂單 凍結群組表 SAD群組 SAD群組 訂單 L o c 1 Loc 2 Loc 3 資源RSh RS 1 2 象限1 象限2 象限3 象限4 時間線 存貨準位 需求曰期 垂直線 垂直線 存貨可用日期D 1 存貨可用曰期 時間線 存貨準位 存貨可用曰期 -116- (112) 最早可接受日期 需求曰期 時間線 存貨準位 需求日期 需求量 可用存貨可用曰期 存貨為最大值 最晚可接受日期 時間線 存貨準位 可接受時間期間 需求量Block diagram of the planning system. Schematic representation of symbols 100 ABP system 101 Database 102 Manufacturer 104 Manufacturer 106 Manufacturer 110 Resource 120 Resource 130 Resource 140 Material 350 Block Diagram 352 SAD Group 354 Order 356 Order -115- (111) Order Block Group Table SAD Group SAD Group Order Loc 1 Loc 2 Loc 3 Resources RSh RS 1 2 Quadrant 1 Quadrant 2 Quadrant 3 Quadrant 4 Timeline Inventory Level Demand Date Vertical Line Vertical Line Stock Availability Date D 1 Stock Availability Date Timeline Inventory Level Inventory Availability Date-116- (112) Earliest Acceptable Date Demand Date Timeline Inventory Level Demand Date Demand Quantity Available Inventory Available Date Inventory is Maximum Maximum Latest Acceptable Date Timeline Inventory Level Acceptable Demand over time

最晚可接受曰期 用存貨日期D4 SAD群組 次要項目SKU 次要項目SKU 次要項目SKU SAD群組 次要項目SKU 次要項目SKU SAD群組 次要項目SKU -117- (113) (113)Latest acceptable inventory date D4 SAD group secondary item SKU secondary item SKU secondary item SKU SAD group secondary item SKU secondary item SKU SAD group secondary item SKU -117- (113) ( 113)

次要項目SKU 次要項目SKU 訂單j 組態A 組態B 次要項目SKU 次要項目SKU 次要項目SKU 次要項目SKU 次要項目SKU 次要項目SKU 次要項目SKU 次要項目SKU 時間線 購買訂單安置日期(POPD) 購買訂單安置日期加上最晚(POPD + ML) 補充起始日期(RSD) 補充需求日期減去最早(RND-ME) 補充需求曰期(RND) 補充需求日期加上最晚(RND + ML) 購買出貨時間或「PLT」 桶狀區間 時間線 購買訂單安置日期(POPD) -118- (114) (114)Minor Item SKU Minor Item SKU Order j Configuration A Configuration B Minor Item SKU Minor Item SKU Minor Item SKU Minor Item SKU Minor Item SKU Minor Item SKU Minor Item SKU Minor Item SKU Timeline Purchase Order Placement Date (POPD) Purchase Order Placement Date plus Latest (POPD + ML) Supplementary Start Date (RSD) Supplementary Demand Date minus Earliest (RND-ME) Supplementary Demand Date (RND) Supplementary Demand Date plus Latest (RND + ML) purchase shipping time or "PLT" barrel interval timeline purchase order placement date (POPD) -118- (114) (114)

購買訂單安置日期加上最晚(POPD + ML) 完成日期 補充需求日期加上最晚(RND + ML) 購買出貨時間或「PLT」 時間線 時間線 補充起始日期(RSD) 補充需求日期減去最早(RND-ME) 購買訂單安置曰期(POPD) 購買訂單安置日期加上最晚(POPD + ML) RSD + PLT 日期 RND-ME日期 RND日期 桶狀區間 桶狀區間 桶狀區間 時間線 有效列入計畫表區間的起始日期(SDESI) 有效需求曰期Purchase order placement date plus latest (POPD + ML) completion date supplementary demand date plus latest (RND + ML) purchase shipping time or "PLT" timeline timeline replenishment start date (RSD) supplementary demand date minus Go to earliest (RND-ME) purchase order placement date (POPD) purchase order placement date plus latest (POPD + ML) RSD + PLT date RND-ME date RND date bucket interval bucket interval bucket interval timeline is valid Start date (SDESI) for effective schedule date

EDESI 時間線EDESI timeline

SDESISDESI

EDESI 時間線 -119- (115)EDESI Timeline -119- (115)

SDESISDESI

EDESI 時間線EDESI timeline

SDESISDESI

EDESI 圖 列 列 列 星期時間期間 需求曰期會落於第6星期的中間 有效列入計畫表區間 時間桶狀區間 分隔線 分隔線 分隔線 分隔線 分隔線 分隔線 分隔線 分隔線 系統 資料庫 使用者 -120- (116) 視窗管理模組 SKU模組 BOM模組 組態模組 SAD群組模組 樣式模組 時序/順序模組模組 評估模組 訂單模組 其他模組 • 121 -The EDESI chart lists the time period during the week. The date will fall in the middle of the 6th week. It is effectively included in the schedule. Barrel interval divider divider divider divider divider divider divider divider divider system database. -120- (116) Window Management Module SKU Module BOM Module Configuration Module SAD Group Module Style Module Timing / Sequence Module Module Evaluation Module Order Module Other Modules • 121-

Claims (1)

200305088 拾、申請專利範圍 1. 一種規劃供應鏈資源的使用之方法,以滿足如由訂單 所定義之需求,包括下列步驟: 產生SAD群組,該等SAD群組係由屬性所定義,並 且相關於基於該等屬性之該等訂單; 基於該等SAD群組,將該等訂單按優先順序處理; 基於載入一視窗中之該等訂單的該優先權,而選擇 一個或多個該等訂單; 從該視窗中選擇一訂單; 決定用於該選擇訂單的一組態;以及 基於該等組態,選擇用以完成選自該視窗中之該選 擇訂單的一資源。 2. 如申請專利範圍第1項之方法,其中選擇一資源之該步 驟包括判斷該資源是否可由購買所補充之步驟。 3 .如申請專利範圍第2項之方法,其中判斷該資源是否可 由購買所補充之該步驟,包括下列步驟: 決定時間項目,該等時間項目係相關於該訂單,並 且其中至少一個該等時間項目係基於具有屬性之該存 貨保持單元的一購買出貨時間; 基於該等時間項目之時間事件; 產生一時間線,其包括該等時間事件及該等時間項 目; 基於來自於一群預定方案之該時間線,而選擇一可 用方案;以及 200305088200305088 Patent application scope 1. A method of planning the use of supply chain resources to meet the needs as defined by the order, including the following steps: Generate SAD groups, which are defined by attributes and related Based on the orders based on the attributes; Based on the SAD groups, the orders are processed in priority order; Based on the priority of the orders loaded in a window, one or more of the orders are selected Selecting an order from the window; determining a configuration for the selected order; and selecting a resource to complete the selected order selected from the window based on the configurations. 2. The method of claim 1 in the scope of patent application, wherein the step of selecting a resource includes a step of determining whether the resource can be supplemented by purchase. 3. The method according to item 2 of the patent application scope, wherein the step of judging whether the resource can be supplemented by the purchase includes the following steps: determining time items which are related to the order and at least one of which The item is based on a purchase and shipment time of the inventory holding unit with attributes; based on the time events of the time items; generating a timeline that includes the time events and the time items; based on a group of predetermined plans The timeline while choosing an available plan; and 200305088 基於該可用方案,而產生一輸出。 4.如申請專利範圍第3項之方法,其中該等時間項目更包 括一購買訂單安置日期、一補充起始日期、一補充需 求曰期、一最晚、以及一最早,並且其中該講買出貨 時間係定義為獲得可用請求補充材料所需之一數量的 時間,其中該購買訂單安置曰期係定義為該補充需求 日期與該購買出貨時間之間的一差值。 5 .如申請專利範圍第4項之方法,其中該等時間事件更包 括如由該購買訂單安置日期與該最晚之和所定義之一 曰期。 6. 如申請專利範圍第4項之方法,其中該等時間事件更包 括如由該補充需求日期減去該最早之間的一差值所定 義之一日期。 7. 如申請專利範圍第4項之方法,其中該等時間事件更包 括如由該補充需求日期與該最晚之和所定義之一日期。 8. 如申請專利範圍第4項之方法,其中該等時間事件更包 括如由該補充起始日期與購買延遲時間之和所定義之 一曰期。 9. 如申請專利範圍第4項之方法,其中該等時間事件更包 括如由該購買訂單安置日期減去該最早之間的一差值 所定義之一日期。 10. 如申請專利範圍第4項之方法,其中該等時間事件更包 括如由該購買訂單安置日期與該最晚之和、該補充需 求日期減去該最早之間的一差值、該補充需求日期與 200305088Based on this available scheme, an output is generated. 4. The method of item 3 of the scope of patent application, wherein the time items further include a purchase order resettlement date, a supplementary start date, a supplementary demand date, one latest, and one earliest, and among which The shipping time is defined as the time required to obtain one of the requested supplementary materials, where the purchase order placement date is defined as the difference between the supplementary demand date and the purchase shipping time. 5. The method of claim 4 in the scope of patent application, wherein the time events further include a date as defined by the purchase order resettlement date and the latest sum. 6. The method of claim 4 in the scope of patent application, wherein the time events further include a date as defined by the date of the supplementary demand minus the difference between the earliest. 7. The method according to item 4 of the patent application, wherein the time events further include a date as defined by the supplementary demand date and the latest sum. 8. The method of claim 4 in the scope of patent application, wherein the time events further include a date as defined by the sum of the supplementary start date and the purchase delay time. 9. The method of claim 4 in the scope of patent application, wherein the time events further include a date as defined by the purchase order placement date minus the difference between the earliest. 10. If the method of claim 4 is applied, the time events further include, for example, the sum of the resettlement date of the purchase order and the latest, the date of the supplementary demand minus the difference between the earliest, the supplement Demand date and 200305088 該最晚之和、該補充起始日期與購買延遲時間之和、 以及該購買訂單安置日期減去該最早之間的一差值所 定義之曰期,其中該等方案係基於該等時間項目及該 等時間事件之順序,並且每一該等方案係相關於特定 輸出。 1 1 .如申請專利範圍第3項之方法,其中所產生的該等輸出 係填滿補充是可行且準時的,填滿補充不能準時,以 及補充是不可行中的至少一種。 12.如申請專利範圍第3項之方法,更包括產生購買模型之 步驟,其中該購買模型係由定義週期最大值而模型化 ,以限制在一時間週期期間,資源可產生之材料的數 量。 1 3 .如申請專利範圍第1項之方法,更包括產生未規劃訂單 之一暫時表之步驟,以儲存在該視窗中的該等未規劃 訂單。 1 4.如申請專利範圍第1項之方法,更包括產生該等資源的 一靜態模型,以及使用用於規劃的該靜態模型之步驟。 1 5 .如申請專利範圍第1項之方法,更包括初始化桶狀區間 之步驟。 1 6 ·如申請專利範圍第1 5項之方法,其中該桶狀區間係相 關於一特定資源及時間區間。 1 7 ·如申請專利範圍第1 5項之方法,其中初始化桶狀區間 200305088The date defined by the sum of the latest, the sum of the supplementary start date and the purchase delay time, and the difference between the date of the purchase order placement minus the earliest, where the schemes are based on the time items And the sequence of these time events, and each such scenario is related to a particular output. 1 1. The method according to item 3 of the scope of patent application, in which the output generated is at least one of filling and supplementing is feasible and on time, filling and supplementing is not on time, and supplementation is not feasible. 12. The method according to item 3 of the scope of patent application, further comprising the step of generating a purchase model, wherein the purchase model is modeled by defining a cycle maximum to limit the amount of material that can be generated by a resource during a time period. 1 3. The method according to item 1 of the patent application scope further includes the step of generating a temporary list of unplanned orders to store the unplanned orders in the window. 14. The method of item 1 of the scope of patent application further includes the steps of generating a static model of the resources and using the static model for planning. 1 5. The method according to item 1 of the scope of patent application, further comprising the step of initializing a barrel section. 16 · The method according to item 15 of the scope of patent application, wherein the barrel interval is related to a specific resource and time interval. 1 7 · The method according to item 15 of the scope of patent application, in which the barrel interval is initialized 200305088 1 8 ·如申請專利範圍第1 5項之方法,其中初始化桶狀區間 之該步驟更包括安置附屬限制之步驟。 1 9.如申請專利範圍第1項之方法,更包括產生一預定配置 表之步驟。 2 0.如申請專利範圍第19項之方法,更包括儲存有關於需 預先分配的訂單之資料之步驟。 2 1.如申請專利範圍第20項之方法,更包括將預先分配安 置到該等桶狀區間之步驟。 22.如申請專利範圍第21項之方法,更包括基於該等預先 分配,而配置材料之步驟。 2 3 .如申請專利範圍第1項之方法,更包括將組態及有關於 安置於該視窗中的該等訂單之BOM資料載入到該視窗 中 0 24.如申請專利範圍第1項之方法,其中用以完成來自於該 視窗中的該選擇訂單之資源的規劃使用係基於來自於 該視窗中的該選擇訂單之屬性。 2 5 . —種規劃供應鏈製造資源的使用之系統,以完成如由 訂單所定義之需求,包括: 一電腦裝置; 一資料庫,與該電腦裝置做傳輸; 用以藉由屬性來定義訂單之一模組; 用以產生由屬性所定義且相關於藉由該等屬性的 一個或多個訂單之存貨保持單元,屬性定義群組(SAD 群組)之一模組; 20030508818 · The method according to item 15 of the scope of patent application, wherein the step of initializing the barrel section further includes the step of placing subsidiary restrictions. 19. The method according to item 1 of the patent application scope further comprises the step of generating a predetermined configuration table. 2 0. The method of claim 19 in the scope of patent application further includes the step of storing information about the order to be allocated in advance. 2 1. The method according to item 20 of the scope of patent application, further comprising the step of placing a pre-allocation into these bucket-shaped intervals. 22. The method according to item 21 of the scope of patent application, further comprising the step of allocating materials based on the pre-allocation. 2 3. If the method of the first scope of patent application, it also includes loading the configuration and BOM information about the orders placed in the window into the window. 0 24. If the first scope of patent application A method in which the planning and use of resources to complete the selection order from the window is based on the attributes of the selection order from the window. 2 5. A system for planning the use of manufacturing resources in the supply chain to fulfill the requirements as defined by the order, including: a computer device; a database that communicates with the computer device; used to define the order by attributes One module; a module for generating inventory holding units defined by attributes and related to one or more orders through the attributes, a module of attribute definition groups (SAD groups); 200305088 用以將基於一個或多個該等SAD群組的該等訂單按 優先順序處理之一模組; 用以選擇基於載入於一視窗中之該等訂單的該優 先權之一個或多個該等訂單之模組; 用以選擇該視窗中的一訂單之一模組; 用以決定用於該選擇訂單的一組態之一模組;以及 用以基於該等組態,選擇用以完成來自於該視窗中 之該選擇訂單的一資源之一模組。 2 6 ·如申請專利範圍第2 5項之系統,其中用以選擇一資源 的該模組更包括: 用以決定時間項目,該等時間項目係相關於該訂單 ,並且其中至少一個該等時間項目係基於具有屬性之 該存貨保持單元(SKU)的一購買出貨時間之一模組; 用以基於該等時間項目之時間事件之一模組; 用以.產生一時間線,其包括該等時間事件及該等時 間項目之一模組; 用以基於來自於一群預定方案之該時間線,而選擇 一可用方案之一模組;以及 用以基於該可用方案,而產生一輸出之一模組。 27.如申請專利範圍第26項之系統,其中該等時間項目更 包括一購買訂單安置日期、一補充起始日期、一補充 需求日期、一最晚、以及一最早,其中該購買出貨時 間係定義為獲得可用請求補充材料所需之一數量的時 間0 200305088A module for processing the orders based on one or more of the SAD groups in priority order; for selecting one or more of the orders based on the priority of the orders loaded in a window Modules for waiting for orders; a module for selecting an order in the window; a module for determining a configuration for the selected order; and a module for selecting and completing based on the configurations A module from a resource of the selected order in the window. 2 6 · If the system of claim 25 of the patent scope, the module for selecting a resource further includes: used to determine time items, the time items are related to the order, and at least one of these time An item is a module based on a purchase and shipping time of the inventory holding unit (SKU) with attributes; a module used to time events based on the time items; used to generate a timeline that includes the A module for waiting for time events and one of these time items; for selecting a module for an available solution based on the timeline from a group of predetermined scenarios; and for generating one of an output based on the available scenario Module. 27. If the system of claim 26 is applied for, the time items further include a purchase order resettlement date, a supplementary start date, a supplementary demand date, a latest date, and an earliest time, among which the purchase shipment time Is defined as the time required to obtain one of the requested supplementary materials 0 200305088 2 8 .如申請專利範圍第2 7項之系統,其中該購買訂單安置 曰期係定義為該補充需求日期與該購買出貨時間之間 的一差值。 2 9.如申請專利範圍第27項之系統,其中該等時間事件包 括如由該購買訂單安置日期與該最晚之和所定義之一 曰期。 3 0.如申請專利範圍第27項之系統,其中該等時間事件包 括如由該補充需求日期減去該最早之間的一差值所定 義之一曰期。 3 K如申請專利範圍第2 7項之系統,其中該等時間事件包 括如由該補充需求日期與該最晚之和所定義之一日期。 3 2.如申請專利範圍第27項之系統,其中該等時間事件包 括如由該補充起始日期與購買延遲時間之和所定義之 一曰期。 3 3.如申請專利範圍第27項之系統,其中該等時間事件包 括如由該購買訂單安置日期減去該最早之間的一差值 所定義之一曰期。 3 4.如申請專利範圍第27項之系統,其中該等時間事件更 包括如由該講買訂單安置日期與該最晚之和、該補充 需求日期減去該最早之間的一差值、該補充需求曰期 與該最晚之和、該補充起始日期與購買延遲時間之和 、以及該購買訂單安置日期減去該最早之間的一差值 所定義之日期。 3 5.如申請專利範圍第34項之系統,其中該等方案係基於 20030508828. The system according to item 27 of the scope of patent application, wherein the purchase order placement date is defined as the difference between the date of the supplementary demand and the time of purchase and shipment. 29. The system of claim 27, wherein the time events include a date as defined by the purchase order placement date and the latest sum. 30. The system of claim 27, wherein the time events include a date as defined by the date of the supplementary demand minus the difference between the earliest. 3K The system as claimed in item 27 of the patent application, wherein the time events include a date as defined by the supplementary demand date and the latest sum. 3 2. The system of claim 27, wherein the time events include a date as defined by the sum of the supplementary start date and the purchase delay time. 3 3. The system of claim 27, wherein the time events include a date as defined by the purchase order placement date minus the difference between the earliest. 3 4. The system according to item 27 of the scope of patent application, wherein the time events further include, for example, the sum of the resettlement date of the buy order and the latest, the date of the supplementary demand minus the difference between the earliest The date defined by the sum of the supplementary demand date and the latest, the sum of the supplementary start date and the purchase delay time, and the purchase order placement date minus the earliest. 3 5. If the system of the scope of patent application No. 34, where these schemes are based on 200305088 該等時間項目及該等時間事件之順序。 3 6 .如申請專利範圍第3 5項之系統,其中每一該等方案係 相關於特定輸出。 3 7 ·如申請專利範圍第2 6項之系統,其中所產生的該等輸 出係填滿補充是可行且準時的,填滿補充不能準時, 以及補充是不可行中的至少一種。 3 8 ·如申請專利範圍第2 6項之系統,更包括用以產生購買 模型之一模組,其中該購買模型係由定義週期最大值 而模型化,以限制在一時間週期期間,資源可產生之 材料的數量。 39.如申請專利範圍第25項之系統,其中該資料庫包括未 規劃訂單之一表,以儲存在該視窗中的該等訂單。 4 0.如申請專利範圍第25項之系統,更包括用以產生該等 資源的一靜態模型之一模組。 4 1.如申請專利範圍第2 5項之系統,更包括用以初始化桶 狀區間之一模組,其包括用以括將容量限制安置於該 等桶狀區間上之一裝置,該等桶狀區間係相關於一特 定資源及時間區間。 4 2.如申請專利範圍第25項之系統,其中該資料庫更包括 產生一預定配置表。 43. 如申碲專利範圍第25項之系統,更包括用以將組態及 有關於安置於該視窗中的該等訂單之BOM資料載入到 該視窗中之一模組。 44. 一種可由機器讀取之程式儲存裝置,可明確地藉由一 200305088The time items and the order of the time events. 36. The system of claim 35, each of which is related to a specific output. 37. If the system of claim 26 is applied for, the output generated by the system is at least one of filling and supplementing is feasible and punctual, filling cannot be punctual, and supplementation is not feasible. 38. If the system of item 26 of the patent application scope further includes a module for generating a purchase model, wherein the purchase model is modeled by defining a maximum value of a cycle to limit resources available during a time period The amount of material produced. 39. The system of claim 25, wherein the database includes a table of unplanned orders to store the orders in the window. 40. The system of item 25 of the scope of patent application, further comprising a module for generating a static model of these resources. 4 1. The system according to item 25 of the scope of patent application, further comprising a module for initializing bucket-shaped sections, which includes a device for placing a capacity limit on these bucket-shaped sections, and The condition interval is related to a specific resource and time interval. 4 2. The system of claim 25, wherein the database further comprises generating a predetermined configuration table. 43. The system for claim 25 of the Tellurium patent scope further includes a module for loading configuration and BOM data about the orders placed in the window into the window. 44. A machine-readable program storage device that can be explicitly identified by a 200305088 機器所執行的指令程式而具體實施,用以執行規劃供 應鏈網路資源的使用的方法步驟,以藉由根據分配的 優先權而將訂單按優先順序處理及規劃,而完成如藉 由一個或多個訂單所定義之需求,該等方法步驟包括: 將該等訂單組織成群組,該等訂單具有至少二種屬 性; 將每一群組按優先順序處理; 基於每一該等訂單的屬性,而將每一該等群組内的 每一訂單按優先順序處理; 將每一該等訂單與一組態結合;以及 藉由在規劃具有較低優先權的訂單之前,優先規劃 具有較高優先權的該等訂單,每一訂單的該優先權係 基於在每一該等訂單之自己的該群組内之每一該等訂 單的優先權及在其他該等群組中之該群組自己的優先 權,每一該等訂單的該規劃係基於每一該等訂單的該 等組態,而規劃該等資源的使用。 4 5.如申請專利範圍第44項之程式儲存裝置,其中規劃該 等資源的使用之該步驟更包括下列步驟: 選擇該等資源中的一個; 判斷是否該選擇資源的補充是可行的,以完全地完 成該訂單,該補充判斷步驟更包括下列步驟: 決定有關於該訂單時間項目,並且其中至少一個該 等時間項目係基於具有屬性之該存貨保持單元的一購 買出貨時間; 200305088The instruction program executed by the machine is specifically implemented to perform the method steps of planning the use of network resources in the supply chain in order to process and plan the orders in accordance with the priority according to the assigned priority, and to complete it by one or The requirements defined by multiple orders, the method steps include: organizing the orders into groups, the orders have at least two attributes; processing each group in priority order; based on the attributes of each such order , And each order in each such group is processed in priority order; combining each such order with a configuration; and by prioritizing orders with lower priority, planning with higher priority Priority of these orders, each order's priority is based on the priority of each such order within the group itself of each such order and the group among other such groups Its own priority, the planning of each such order is based on the configuration of each such order, and the use of these resources is planned. 4 5. If the program storage device of the 44th scope of the patent application, the step of planning the use of these resources further includes the following steps: selecting one of these resources; judging whether the selection of the supplement of the resource is feasible, and To complete the order completely, the supplementary judgment step further includes the following steps: It is determined that there are time items related to the order, and at least one of these time items is based on a purchase shipment time of the inventory holding unit with attributes; 200305088 基於該等時間項目之時間事件; 產生一時間線,其包括該等時間事件及該等時間項 目; 基於來自於一群預定方案之該時間線,而選擇一可 用方案;以及 基於該可用方案,而產生一輸出。 46.如申請專利範圍第45項之程式儲存裝置,其中該等時 間項目更包括一購買訂單安置日期、一補充起始日期 、一補充需求日期、一最晚、以及一最早,其中該購 買出貨時間係定義為獲得可用請求補充材料所需之一 數量的時間。 4 7.如申請專利範圍第46項之程式儲存裝置,其中該購買 訂單安置日期係定義為該補充需求日期與該購買出貨 時間之間的一差值。 4 8.如申請專利範圍第46項之程式儲存裝置,其中該等時 間事件更包括如由該購買訂單安置日期與該最晚之和 所定義之一日期。 49.如申請專利範圍第46項之程式儲存裝置,其中該等時 間事件更包括如由該補充需求日期減去該最早之間的 一差值所定義之一日期。 5 0.如申請專利範圍第46項之程式儲存裝置,其中該等時 間事件更包括如由該補充需求日期與該最晚之和所定 義之一曰期。 5 1.如申請專利範圍第46項之程式儲存裝置,其中該等時 200305088Generating a timeline based on the time events of the time items; generating a timeline including the time events and the time items; selecting an available scheme based on the timeline from a group of predetermined schemes; and based on the available scheme, and Produces an output. 46. The program storage device according to item 45 of the patent application, wherein the time items further include a purchase order placement date, a supplementary start date, a supplementary demand date, a latest date, and an earliest date, in which the purchased Delivery time is defined as the time required to obtain one of the requested supplementary materials. 4 7. The program storage device according to item 46 of the patent application scope, wherein the purchase order placement date is defined as a difference between the supplementary demand date and the purchase shipment time. 4 8. The program storage device according to item 46 of the patent application, wherein the time events further include a date as defined by the purchase order resettlement date and the latest sum. 49. The program storage device of claim 46, wherein the time events further include a date as defined by the supplementary demand date minus the difference between the earliest. 50. The program storage device according to item 46 of the patent application, wherein the time events further include a date as defined by the supplementary demand date and the latest sum. 5 1. If the program storage device of the scope of patent application No. 46, in which time 200305088 間事件更包括如由該補充起始日期與購買延遲時間之 和所定義之一日期。 5 2 ·如申請專利範圍第4 6項之程式儲存裝置,其中該等時 間事件更包括如由該購買訂單安置日期減去該最早之 .間的一差值所定義之一日期。 5 3.如申請專利範圍第46項之程式儲存裝置,其中該等時 間事件更包括如由該購買訂單安置日期與該最晚之和 、該補充需求日期減去該最早之間的一差值、該補充 需求日期與該最晚之和、該補充起始日期與購買延遲 時間之和、以及該購買訂單安置日期減去該最早之間 的一差值所定義之日期。 54.如申請專利範圍第53項之程式儲存裝置,其中該等方 案係基於該等時間項目及該等時間事件之順序。 5 5.如申請專利範圍第54項之程式儲存裝置,其中每一該 等方案係相關於特定輸出。 5 6.如申請專利範圍第45項之程式儲存裝置,其中所產生 的該等輸出係填滿補充是可行且準時的,填滿補充不 能準時,以及補充是不可行中的至少一種。 5 7 .如申請專利範圍第4 5項之程式儲存裝置,更包括用以 產生購買模型之一模組,其中該購買模型係由定義週 期最大值而模型化,以限制在一時間週期期間,資源 可產生之材料的數量。 5 8.如申請專利範圍第44項之程式儲存裝置,其中該等訂 單係具有關於客戶型式的一屬性,並且該客戶型式屬 200305088The inter-event further includes a date as defined by the sum of the supplementary start date and the purchase delay time. 5 2 · The program storage device according to item 46 of the patent application scope, wherein the time events further include a date as defined by the purchase order placement date minus a difference between the earliest. 5 3. The program storage device according to item 46 of the patent application scope, wherein the time events further include a difference between the date of the purchase order and the latest sum, the date of the supplementary demand minus the earliest , The date defined by the sum of the supplementary demand date and the latest, the sum of the supplementary start date and the purchase delay time, and the purchase order placement date minus the earliest value. 54. The program storage device of claim 53, wherein the schemes are based on the time items and the sequence of the time events. 5 5. The program storage device of claim 54, each of which is related to a specific output. 5 6. The program storage device according to item 45 of the patent application, in which the output generated is at least one of filling and supplementing is feasible and on time, filling and supplementing is not timely, and supplementation is not feasible. 57. The program storage device according to item 45 of the scope of patent application, further comprising a module for generating a purchase model, wherein the purchase model is modeled by a defined period maximum to limit a period of time, The amount of material that a resource can produce. 5 8. The program storage device according to item 44 of the scope of patent application, wherein the orders have an attribute regarding the customer type, and the customer type belongs to 200305088 性係用來將屬於該等群組中的一個之每個訂單按優先 順序處理。 5 9.如申請專利範圍第44項之程式儲存裝置,其中該等訂 單係具有關於需求日期的一屬性,並且該需求曰期係 用來將屬於該等群組中的一個之每個訂單按優先順序 處理。 6 0.如申請專利範圍第44項之程式儲存裝置,其中屬於該 等群組中的一個之每個訂單的該優先權係基於容量配 置,其中該容量配置係基於該等訂單屬性中的一個, 而將資源容量保留給該等訂單中的一個。 6 1.如申請專利範圍第60項之程式儲存裝置,其中該等訂 單屬性中的該一係一客戶身份屬性。 62. 如申請專利範圍第44項之程式儲存裝置,其中屬於該 等群組中的一個之每個訂單的該優先權係基於材料配 置,其中該材料配置係基於該等訂單屬性中的一個, 而將存貨保留給該等訂單中的一個。 63. 如申請專利範圍第62項之程式儲存裝置,其中該等訂 單屬性中的該一係一客戶身份屬性Sex is used to prioritize each order that belongs to one of these groups. 5 9. The program storage device according to item 44 of the scope of patent application, wherein the orders have an attribute regarding the date of demand, and the date of demand is used to place each order belonging to one of the groups according to Priority processing. 60. The program storage device according to item 44 of the scope of patent application, wherein the priority of each order belonging to one of the groups is based on capacity allocation, wherein the capacity allocation is based on one of the order attributes And reserve the resource capacity to one of these orders. 6 1. The program storage device according to item 60 of the patent application, wherein one of the order attributes is a customer identity attribute. 62. For example, the program storage device of the scope of application for patent 44, wherein the priority of each order belonging to one of the groups is based on the material configuration, wherein the material configuration is based on one of the order attributes, The inventory is reserved for one of these orders. 63. For example, the program storage device of the scope of patent application No. 62, wherein one of the order attributes is a customer identity attribute
TW091137686A 2001-12-27 2002-12-27 System and method for order group planning with attribute based planning TW200305088A (en)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US34240401P 2001-12-27 2001-12-27
US37724302P 2002-05-03 2002-05-03
US10/287,775 US7539630B2 (en) 2001-12-27 2002-11-05 System, method, and computer program for replenishment by manufacture with attribute based planning
US10/287,805 US6885902B2 (en) 2001-12-27 2002-11-05 System and method for replenishment by purchase with attribute based planning
US10/287,788 US6898472B2 (en) 2001-12-27 2002-11-05 System and method for order group planning with attribute based planning
US10/287,773 US20030149631A1 (en) 2001-12-27 2002-11-05 System and method for order planning with attribute based planning

Publications (1)

Publication Number Publication Date
TW200305088A true TW200305088A (en) 2003-10-16

Family

ID=27559592

Family Applications (1)

Application Number Title Priority Date Filing Date
TW091137686A TW200305088A (en) 2001-12-27 2002-12-27 System and method for order group planning with attribute based planning

Country Status (4)

Country Link
EP (2) EP1468391A4 (en)
AU (2) AU2002357385A1 (en)
TW (1) TW200305088A (en)
WO (2) WO2003058541A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI776711B (en) * 2021-10-18 2022-09-01 樂樂國際資訊有限公司 System, method, and computer program product for managing group-purchase orders

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7539630B2 (en) 2001-12-27 2009-05-26 Jda Software Group System, method, and computer program for replenishment by manufacture with attribute based planning
US7516095B1 (en) 2007-10-12 2009-04-07 Advisor Software, Inc. Stochastic control system and method for multi-period consumption
US10318703B2 (en) 2016-01-19 2019-06-11 Ford Motor Company Maximally standard automatic completion using a multi-valued decision diagram
CN111582781B (en) * 2020-04-24 2023-04-28 清华大学深圳国际研究生院 Method for distributing goods shelves according to replenishment orders and computer readable storage medium
CN115187180B (en) * 2022-09-09 2023-01-20 荣耀终端有限公司 Material data processing method and electronic equipment

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4827423A (en) * 1987-01-20 1989-05-02 R. J. Reynolds Tobacco Company Computer integrated manufacturing system
US5233533A (en) * 1989-12-19 1993-08-03 Symmetrix, Inc. Scheduling method and apparatus
US5369570A (en) * 1991-11-14 1994-11-29 Parad; Harvey A. Method and system for continuous integrated resource management
US5787000A (en) * 1994-05-27 1998-07-28 Lilly Software Associates, Inc. Method and apparatus for scheduling work orders in a manufacturing process
EP0770967A3 (en) * 1995-10-26 1998-12-30 Koninklijke Philips Electronics N.V. Decision support system for the management of an agile supply chain
US5819232A (en) * 1996-03-22 1998-10-06 E. I. Du Pont De Nemours And Company Method and apparatus for inventory control of a manufacturing or distribution process
US6064982A (en) * 1997-11-12 2000-05-16 Netscape Communication Corporation Smart configurator
US7668743B2 (en) * 1999-12-06 2010-02-23 Toyota Jidosha Kabushiki Kaisha Demand-production scheme planning apparatus, and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI776711B (en) * 2021-10-18 2022-09-01 樂樂國際資訊有限公司 System, method, and computer program product for managing group-purchase orders

Also Published As

Publication number Publication date
WO2003058542A1 (en) 2003-07-17
AU2002357385A1 (en) 2003-07-24
EP1468390A4 (en) 2005-10-26
EP1468391A1 (en) 2004-10-20
EP1468391A4 (en) 2005-10-26
WO2003058541A1 (en) 2003-07-17
AU2002367254A1 (en) 2003-07-24
EP1468390A1 (en) 2004-10-20

Similar Documents

Publication Publication Date Title
US6898472B2 (en) System and method for order group planning with attribute based planning
US6885902B2 (en) System and method for replenishment by purchase with attribute based planning
US7539630B2 (en) System, method, and computer program for replenishment by manufacture with attribute based planning
US20030149631A1 (en) System and method for order planning with attribute based planning
US8489446B2 (en) System and method for defining a sales promotion
US7747543B1 (en) Dynamically determining actual delivery information for orders based on actual order fulfillment plans
US7835952B2 (en) System, method, and computer program product for creating a production plan
US8429019B1 (en) System and method for scheduled delivery of shipments with multiple shipment carriers
US6119102A (en) MRP system with viewable master production schedule
US6934594B2 (en) System for determining carrier service using logistics considerations
US20030208392A1 (en) Optimizing resource plans
US20050197886A1 (en) System and method for defining a sales promotion
US20020188499A1 (en) System and method for ensuring order fulfillment
US20050197900A1 (en) System and method for defining a sales promotion
US20050197899A1 (en) System and method for defining a sales promotion
JP5039278B2 (en) Supply chain reservation
US20030233264A1 (en) Manufacturing order scheduling and materials replenishment system
US20200111033A1 (en) Lead time determinations in supply chain architecture
WO2019161394A1 (en) Lead time determinations in supply chain architecture
US20040054570A1 (en) System and method for providing logistics planning
US20050015288A1 (en) Dynamic logistics routing system
TW200305088A (en) System and method for order group planning with attribute based planning
US20050015167A1 (en) Synchronized production with dynamic logistics routing
JPH1087036A (en) Stock allocating method, and deciding method of distribution mode and stocking position, in physical distribution system
JP4303449B2 (en) production management system