[go: up one dir, main page]

WO1997013210A1 - Procede et systeme de modelisation et de visualisation dynamiques de donnees - Google Patents

Procede et systeme de modelisation et de visualisation dynamiques de donnees Download PDF

Info

Publication number
WO1997013210A1
WO1997013210A1 PCT/CA1996/000666 CA9600666W WO9713210A1 WO 1997013210 A1 WO1997013210 A1 WO 1997013210A1 CA 9600666 W CA9600666 W CA 9600666W WO 9713210 A1 WO9713210 A1 WO 9713210A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
model
workstations
user
view
Prior art date
Application number
PCT/CA1996/000666
Other languages
English (en)
Inventor
Edward Sitarski
Kezheng Gan
Original Assignee
Numetrix Limited
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
Application filed by Numetrix Limited filed Critical Numetrix Limited
Priority to AU71196/96A priority Critical patent/AU7119696A/en
Publication of WO1997013210A1 publication Critical patent/WO1997013210A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION 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/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates to a data model visualization system. More specifically, the present invention relates to a method and system for dynamically modelling and visualizing data to allow a user to dynamically manipulate and visualize data models from a common data pool via a graphical user interface.
  • DRP Distributed Resources Planning
  • MRP Material Resources Planning
  • All DRP and MRP systems are software- database-computer based systems which share several common characteristics namely, they all use a data model and perform basic net requirement (inventory projections) and replenishment calculations.
  • the calculated net requirements are used to fulfil a warehouse's requirements for customer demand and safety stock which in turn becomes the demand which drives scheduling and manufacturing utilization at the manufacturing plants.
  • the data model In order to build the data model required to calculate the net requirements, the data model must be able to model factors such as manufacturing, shipments, inventory levels and customer demand ie. , the distribution chain.
  • DRP systems are not designed to consider. For example, manufacturing plants have limited production capacity, warehouses have limited floor space, shipping and receiving services have a limited hourly flow through and shipping fleets have a finite capacity. Further to this end, all of these constraints have an associated cost which must be considered when searching for the best solution to a given situation. Consequently, if the DRP system, does not take the above factors or constraints into consideration, the data model will not accurately reflect the actual environment and therefore any calculations made using the data model will be inaccurate.
  • DRP systems are batch oriented systems which do not provide for real-time analysis or manipulation of the data model.
  • Batch oriented systems update information at regular predefined time intervals. Typically, these time intervals, are in terms of hours rather than minutes or seconds. Consequently, it is often very difficult to make accurate business decisions the data supporting the decision is often not up-to-date.
  • a computer implemented system for dynamically modelling and visualizing data accessible to a plurality of users comprising: a data store; a plurality of user stations for accessing data sets in said data store, said user stations allowing accessed data sets to be manipulated and/or displayed and sending manipulated data sets back to said data store for storage therein; and an interface acting between said data store and the plurality of user stations, and registering with said user station, the interface determining when said user stations access common data sets, said interface updating said common data sets automatically when one of said user stations manipulates the common data set.
  • a computer implemented process for dynamically modelling and visualizing data accessible to a plurality of users comprising the steps of: establishing a data store; enabling a plurality of workstations for accessing data sets in said data store, said workstations allowing accessed data sets to be manipulated and/or displayed and sending manipulated data sets back to said data store for storage therein; and creating an interface acting between said data store and the plurality of workstations, said interface registering with said workstation accessing data from said data store and, determining when said two or more workstations access a common data set, said interface updating said common data set at other workstations automatically when one of said workstations manipulates the common data set.
  • Figure 1 shows a dynamic modelling and visualization system in accordance with an embodiment of the present invention
  • Figure 2 shows an architecture of an MVC network component of the system of Figure 1 ;
  • Figure 3 shows a typical MVC session of the system of Figure 1 ;
  • Figure 4 shows a main window graphical user interface of a user desktop component of Figure 1 ;
  • Figure 5 shows a list of available views associated with an open selection made with respect to Figure 5;
  • Figure 6 shows a portion of a process to create a single view associated with a create selection made with respect to Figure 5;
  • Figure 7 shows a view customization window associated with a single option selected in the window of Figure 6;
  • Figure 8 shows a units window associated with the view customization window of Figure 7;
  • Figure 9 shows a display field associated with the view customization window of Figure 7;
  • Figure 10 shows a compound view window associated with a selection made in Figure 5;
  • Figure 11 shows a typical view display of a VT and/or a template chart associated with a user defined application model
  • Figure 12 shows a typical view of a VT data editor associated with the user defined application model.
  • a method and system for dynamically modelling and visualizing data in accordance with the present invention is indicated generally at 20.
  • the system 20 is designed to allow users at a plurality of workstations to access data sets stored in a shared data pool via an interface.
  • a user accesses a data set from the datapool, the user may manipulate a view and/or share the data set depending on the configuration of the workstation. Multiple workstations may access the same data set. If one workstation manipulates the data in the data set, the changes in the data are automatically conveyed to the interface which updates the data in the data pool as well as the data in the same data sets accessed by other workstations. This allows common data accessed by multiple users to be updated in substantially real-time if one of the users modifies the data set. Specifics of the system 20 will now be more clearly described.
  • system 20 is partitioned into a multi-user level 24 and a single user level 28 representing one of the workstations.
  • a plurality of common data repositories 32 each containing a base set of data 36 which has been translated by a translator 40 from a plurality of independent data repositories 44.
  • independent data repositories 44 may include a production planning data repository at a manufacturing location, a finished goods inventory data repository at a warehouse location and a demand forecasting data repository at a head office location.
  • the plurality of data repositories 44 may further differ from each other in that the data stored therein may be in different formats including, but not particularly limited to, RDBMS (Relational Database Management Systems), ASCII files (either fixed length of token delimited), ODBC (Open Database Connectivity) or OODBMS ( Object Oriented Database Management Systems).
  • RDBMS Relational Database Management Systems
  • ASCII files either fixed length of token delimited
  • ODBC Open Database Connectivity
  • OODBMS Object Oriented Database Management Systems
  • the base set of data 36 stored in the data repositories are configured as tables. Within each table are a plurality of tuples representing the actual data.
  • the base set of data 36 stored in the data repositories 32 are placed into one or more desired formats and allow for a realistic model, representative of the business of the organization, to be created.
  • the model for example may include customer orders, forecasts, inventory plan, production plan, products etc.
  • Model objects 48 represent a data set from base set of data 36 that is defined by a triplet.
  • the triplet consists of a connection name, a table name, and a selection predicate expression.
  • Each component of the triplet respectively identifies the data repository 32 from which the name of the table from data repository 32 and the tuples from the table, all of which define model object's 48 data set.
  • Multiple model objects 48 may access the same tuple set provided that each individual model object 48 uses different parts of the table.
  • the definition model objects 48 is known each time system 20 is initialized however, the physical tuples are read on a demand basis only.
  • Model objects 48 do not have any visual attributes associated with them.
  • Model server 52 is also responsible for maintaining internal cache consistency between model objects 48. When initialized, model server 52 internally caches a physical tuple set of the data as requested by the model object 48 triplet. Consequently, model objects 48 may share this physical tuple set and it is the responsibility of model server 52 to synchronize updates of the tuple set between model servers.
  • Additional model objects 48 may be defined by a user from a Graphical User Interface (GUI) 49 connected to model server 52.
  • GUI 49 also has the capability of changing the selection predicate expression thereby changing the tuples called from the table. It is also contemplated that it is further possible to have multiple model servers 52 each with their respective model objects 48 share the same tuple set and hence the same data. In this case a synchronization mechanism would have to ensure integrity of data changes and updates.
  • multi-user level 24 acquires data from independent data repositories 44, translates the data into one or more desired formats, to form a base set of data 36.
  • the base set of data 34 represents an accurate picture of the business of the organization.
  • Model server 52 links one or more model objects 48 which directly access data stored in base data set 36, to a user workstation 28.
  • Workstation 28 generally comprises a model-view-controller (MVC) network 56 and a desktop 68.
  • MVC network 56 is defined by one or more visualization tools (VTs) 60 and/or one or more manipulation tools (MTs) 64.
  • VTs 60 and MTs 64 are predefined visualization and manipulation objects respectively, which the user selects in order to perform a specific operation on one or more underlying model objects 48.
  • a list and brief description of VTs 60 and MTs 64 currently included in system 20 can be found at Appendix A.
  • the desktop 68 allows a user to select from a plurality of templates 66.
  • Templates 66 represent a predefined set of VTs 60 and MTs 64 connections which perform commonly required operations to one or more object models 48 and when selected, establishes these connections to create an MVC network.
  • a summary of the templates presently available to system 20, and examples of data fields included in the template can be found at Appendix B.
  • Desktop 68 also allows the user to select a VT 60 to append to an MVC network 56 created through selection of a template 66.
  • MTs 64 are transparent to the user. This is due to the fact that MTs 64 are low level tools employed by the templates 66.
  • Desktop 68 provides a graphical user interface (GUI) which allows the user to build an application model 72 by selecting the desired model object 48 and linking any one of a number of predefined VTs 60 and MTs 64 by selecting template 66 and possibly one or more additional VTs 60.
  • GUI graphical user interface
  • application model 72 is constructed. In other words, passing object model data 48 through MVC network 56 results in the manipulation of data through the user defined VTs 60 and MTs 64 connections which builds application model 72 for display to the user.
  • MVC network 56 is defined by a connection of components 88 such as model objects 48, VTs 60 and MTs 64 and which is linked to one or more model objects 48.
  • Each object has assigned to it at least one role which is determined by the nature of the object. The roles that are available are models 76, views 80 and controllers 84. If the component 88 is assigned the model 76 role that object is used to store and manage data. If the component 88 is assigned a view 80 role that object is used to display data only ie., the data cannot be changed. If the component 88 is assigned a controller 84 role, that component 88 is used to add/delete and/or change data.
  • component 88 is able to assume more than one role.
  • component 88 could assume the roles of a combined view 80/controller 84 which has the ability to display data and add/delete and/or change data.
  • Component 88 could also assume the combined roles of a model 76/view 80/controller 84 which is able to manage, display and add/delete and/or change data.
  • MVC network protocol is defined as follows:
  • Model 76 can accept data add/delete/change messages from controllers 84, which it is allowed to accept or refuse, ii) Model 76 is responsible to inform all views 80 connected to it when it accepts a change.
  • View 80 is responsible to accurately reflect all update messages which are received from model 76.
  • FIG. 3 illustrates a typical MVC session.
  • VT 60 or in this case, the data editor, is connected to at least one object model 48. This connection is invoked by a user via desktop 68 which results in the formation of application model 72.
  • Application model 72 will be described in further detail below.
  • Model object 48 then responds by sending a Send Data Definition Message 96 back to VT 60 followed by a Send All Data to View 100.
  • Register message 92 is in the form of a triplet which identifies the object name, execution model name in which the component 88 is operating and the role of the component 88 ie, model 76, view 80, view 80/controller 84 etc.
  • Send Data definition message 96 informs, component 88 the data characteristics of the model object 48.
  • the MVC protocol is self-describing in that model objects and VTs 60 register with each other prior to establishing a connection.
  • the above-described MVC network protocol and messaging the MVC architecture provides for dynamic data updates. For example, if three VTs 60 are attached to a single model object 48, a change made through one of the VT 60 would be reflected automatically in remaining two VTs 60. This event can occur when several users operating different application models 72 on separate workstations link to the same model object 48. These changes are effected by the user at the application model 72 level.
  • Figure 4 illustrates a main window 100 of desktop 68.
  • the user may select from a plurality of menu items which includes a File item 104, Windows Item 108, Desktop item 112, Views item 116, Alerts item 120, Network item 124, Horizon item 128, and Help item 132.
  • File item 104 gives the user access to system 20 via login option which permits the user to register with system 20.
  • File item 104 also provides an exit from system 20 via an Exit option.
  • Window item 108 permits the user to select a view from a list of predefined views 110 configured by a user in prior sessions.
  • Desktop item 112 provides access to options such as Load, Save, Save As and Options, of which none of these are shown. From Desktop item 112 the user can load predefined desktop configurations, save the current version or change the current settings. Desktop item 112 also provides the user with the flexibility of selecting default options via the Options item. Such options could include, an Automatic start-up when the user logs in, Alert views on start-up, open with a default view on start-up, or default units of measure.
  • Selecting Views item 116 displays a drop down menu which includes such options as Open 136, Create 140, Copy 144, Customize 148 and Delete 150.
  • a drop down menu which includes such options as Open 136, Create 140, Copy 144, Customize 148 and Delete 150.
  • Open option 136 the user is presented with a window 154 which identifies a list of views which are available to the user.
  • Create option 140 as shown in Figure 4, a cascading menu presents two additional options, namely, Single 155 or Compound 156 allowing the user to select between creating a single view or a compound view.
  • window 158 appears which permits and the user to select template 66 from a list of available templates and a VT 60 from a drop down menu.
  • a view customization window 162 appears, as shown in Figure 7, permits the user to select various customization options. These option include, but are not limited to items such as Filtering Criteria 166, default Units 170, Display Fields 174. Selecting Units 170 and Display Fields 174 produces windows 178 and 182, shown in Figures 8 and 9 respectively. Display Fields 174 permits the user to edit the display fields which are generated by the view template. Selecting units 170 permits the user to select the desired measurement units with which the data will be presented. For example, if the user is working with an inventory model, the available units could include cases, pallets, six packs or twelve packs.
  • a window 186 presents the user with a list of available single previously defined views 190. Two or more of views 190 may be compounded to generate the desired results. For example, a user may wish to chart manufacturing utilization against warehouse utilization for comparison of performance.
  • Application model 72 is launched by selecting View Open option 136 where the view, whether newly created or simply selected from the existing views, is displayed.
  • the underlying MVC network 56 constituted by linked VTs 60 and MTs 64 as defined by the selected template 66 and possibly a selected VT, registers with the selected model object 48 and if permitted, establishes a connection.
  • Model object 48 reads the tuple data into the intemal cache of model server 52 as requested by the template and tools.
  • the tuple data is passed up through MVC network 56 where VTs 60, and MTs 64 constituting the MVC network 56 manipulate and filter the data as per its configuration as determined by the user.
  • Two examples of a typical application model 72 are shown in Figures 11 and 12.
  • the user has the ability to edit data in application model 72 if the visualization tool selected assumes the role of a View/Controller, as shown in Figure 12.
  • the visualization tool selected assumes the role of a View/Controller, as shown in Figure 12.
  • the user is capable of editing data as desired.
  • the change to data is passed through MVC network 56 to model object 48.
  • each model object 48 is aware of all MVC networks registered to it via the MVC protocol. Consequently any changes to data made via MVC network 56 by a user is, if accepted by model object 48, instantly updated to all views via other MVC networks 56 registered to the model object. In effect, this means that a plurality of users sharing the same object model at the same time, instantly see the effects of each user operating with that particular model object.
  • Figure 11 shows application model 72 as a view 80 in which the view is in the form of a chart.
  • Alert item 120 Another feature available to system 20, via desktop 68, is Alert item 120 shown in Figure 4.
  • Alerts are tools which monitor data passing through MVC network 56 to detect certain conditions which the user defines via Alert item 120. For example, a user operating a view which displays information regarding raw materials inventory could instruct the view to trigger an alert condition when a particular raw material quantity falls below a certain level. If and when this event occurs, the data in violation of the alarm condition is displayed to the user in tabular form with a user defined message describing the alarm condition.
  • the alert feature may be set as a default feature which activates automatically when the user logs-in to desktop 68. In this case, when desktop 68 opens, a Violation Table is displayed which informs the user of any alert conditions present in the default application model 72. Altematively, the user may also view the Violation Table at any time by selecting an "Inspect" option in a pull down menu once Alert item 120 has been selected.
  • the hyper-link feature (not shown) is a direct user control which may, for example, be activated by double-clicking on a conventional mouse button. Operation of the hyper-link feature can be illustrated by the present example.
  • the user opens the violation table and sees that a particular inventory level has fallen below the predefined alert value.
  • the user may wish to see an inventory status view to get a better idea of what the inventory situation is like for a given category of items.
  • the hyper-link feature launches the inventory status view which is becomes the current application model 72 displayed on desktop 68.
  • the user may further hyper-link on any field in the inventory status, for example, a customer order field to open a new view associated with the particular data item.
  • system 20 may include additional features.
  • a versioning feature could be included which allows users to save a copy of the data associated with a particular application model 72. This feature would be particularly useful if the user wished to perform "what-if scenarios on application model 72. In this situation, the dynamic features of system 20 would not be required as the user requires manipulating the model at will to generate various situations.
  • the version of application model 72 would be saved separately allowing to manipulate data with having the changes reflected in substantially real time to other users on the system.
  • VT Table - A dynamic data editor allows user to edit application model.
  • VT List - This tool is employed to browser a list and contains data editing features.
  • V - view VC - View controller H rlVC - Model View C Controller VT Form Manages a set of records. Permits user to edit one or more records at a time.
  • MT Selection Manages messages to MVC components 88. Attaches to an object model 48.
  • MT Aggregate Dynamically maintains the aggregation of tuple data.
  • Supports aggregation functions such as Sum, Average, Min and Max.
  • MT Cross tab Permits user to alter the key structure of object model 48 data. GUI interface to permit editing.
  • Effective Demand - This is the effective demand based on selected forecast consumption rule.
  • Ending Inventory - This is tbe projected inventory ignoring Deployment Orders and is calculated as follows: (Ending Inventory - Starting Inventory + Scheduled Production + Enroute ⁇ Untransmitted + On-order • Effective Demand).
  • Ending InventoryfDeployment • This is the projected inventory including Deployment Orders and is calculated as follows: (Ending Inventory - Starting Inventory + Scheduled Production + Enroute + Untransmitted + On-order + Deployment orders - Effective Demand).
  • Days of Coverage This is the number of days of cover that the Ending Inventory or the Ending Inventory Deployment) (depending on what is used in the view) represents based on Effective Demand.
  • Weeks of Coverage This is tbe numoer of weeks of cover that the Ending Inventory or the Ending I ⁇ ventory Deploymeru) (depending on what is used in tbe view) represents based on Effective Demand.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

Système mis en application sur ordinateur destiné à la modélisation et à la visualisation dynamiques de données accessibles à une pluralité d'utilisateurs, comprenant une mémoire de données ainsi qu'une pluralité de postes de travail permettant l'accès à des ensembles de données se trouvant dans ladite mémoire de données. Les postes de travail permettent la manipulation et/ou l'affichage des ensembles de données auxquelles on a accédé, et le renvoi des ensembles de données manipulées dans la mémoire de données dans laquelle ils sont stockés. Une interface intervient entre ladite mémoire de données et la pluralité de postes de travail. L'interface cadre avec le poste de travail, accédant aux données provenant de la mémoire de données et déterminant à quel moment au moins deux postes de travail accèdent à un ensemble de données commun. L'interface met automatiquement à jour l'ensemble de données commun au niveau d'autres postes de travail lorsqu'un des postes de travail manipule l'ensemble de données commun.
PCT/CA1996/000666 1995-10-04 1996-10-04 Procede et systeme de modelisation et de visualisation dynamiques de donnees WO1997013210A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU71196/96A AU7119696A (en) 1995-10-04 1996-10-04 Method and system for dynamically modelling and visualizing data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US53923695A 1995-10-04 1995-10-04
US08/539,236 1995-10-04

Publications (1)

Publication Number Publication Date
WO1997013210A1 true WO1997013210A1 (fr) 1997-04-10

Family

ID=24150379

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA1996/000666 WO1997013210A1 (fr) 1995-10-04 1996-10-04 Procede et systeme de modelisation et de visualisation dynamiques de donnees

Country Status (2)

Country Link
AU (1) AU7119696A (fr)
WO (1) WO1997013210A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7577622B1 (en) * 2004-06-01 2009-08-18 Wooten Van C Method, apparatus and medium for data management collaboration in the transport of goods
US8160893B2 (en) 1999-06-14 2012-04-17 Bally Technologies, Inc. Data visualization system and method
CN110347383A (zh) * 2019-06-28 2019-10-18 深圳市中农易讯信息技术有限公司 跨平台桌面应用的前端开发方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0550370A2 (fr) * 1991-12-31 1993-07-07 International Business Machines Corporation Système d'ordinateur collaborant
EP0553560A2 (fr) * 1992-01-31 1993-08-04 Gpt Limited Système de communication
JPH06250907A (ja) * 1993-02-26 1994-09-09 Nec Corp 分散協調作業支援装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0550370A2 (fr) * 1991-12-31 1993-07-07 International Business Machines Corporation Système d'ordinateur collaborant
EP0553560A2 (fr) * 1992-01-31 1993-08-04 Gpt Limited Système de communication
JPH06250907A (ja) * 1993-02-26 1994-09-09 Nec Corp 分散協調作業支援装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PATENT ABSTRACTS OF JAPAN vol. 018, no. 645 (P - 1839) 7 December 1994 (1994-12-07) *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8160893B2 (en) 1999-06-14 2012-04-17 Bally Technologies, Inc. Data visualization system and method
US8340980B2 (en) 1999-06-14 2012-12-25 Bally Technologies, Inc. Data visualisation system and method
US7577622B1 (en) * 2004-06-01 2009-08-18 Wooten Van C Method, apparatus and medium for data management collaboration in the transport of goods
CN110347383A (zh) * 2019-06-28 2019-10-18 深圳市中农易讯信息技术有限公司 跨平台桌面应用的前端开发方法及装置
CN110347383B (zh) * 2019-06-28 2023-11-14 深圳市中农易讯信息技术有限公司 跨平台桌面应用的前端开发方法及装置

Also Published As

Publication number Publication date
AU7119696A (en) 1997-04-28

Similar Documents

Publication Publication Date Title
US5361199A (en) Automated procurement system with multi-system data access
Deep et al. Investigating factors affecting ERP selection in made‐to‐order SME sector
US7729924B2 (en) Virtual knowledge management system
US7131071B2 (en) Defining an approval process for requests for approval
CA2039189C (fr) Methode de planification et de gestion de procedes d'ecoulement et systeme connexe
US5099431A (en) Automated re-work shop order scheduling system
Boyson et al. The e-supply chain portal: a core business model
US7644088B2 (en) Systems and methods for retrieving data
US5949413A (en) Database graphical user interface with tabbed user view
US20040017400A1 (en) Method for project planning
EP0840239A2 (fr) Extensions du HTML pour obtenir des rapports graphiques sur le réseau Internet
JP2002525251A (ja) 供給チェーンに関連した物流情報を表示するためのシステムおよび方法
US20080162164A1 (en) Method and system for centralized management of sources of supply
CN102467701A (zh) 分布式订单编排系统中的基于事件的编排
US6970825B1 (en) Planning engine for a parcel shipping system
CN115718596A (zh) 一种业务方法模型的构建系统及方法
US20030187676A1 (en) Tool for developing a map of relevant business processes and flows
GB2380571A (en) System using graphic interface to perform stock management
Dreyer et al. Global supply chain control systems: a conceptual framework for the global control centre
WO1997013210A1 (fr) Procede et systeme de modelisation et de visualisation dynamiques de donnees
US20040117227A1 (en) Production capability simulating system and method
Vallespir et al. Enterprise modelling for interoperability
JP2001338120A (ja) 顧客関係管理サービスシステム
CN115857902A (zh) 一种基于数据中台和业务中台的低代码系统及其工作方法
JP2005004307A (ja) スケジュール管理支援システム及びアポイントメント調整支援システム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG US UZ VN AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA