STEERING PROCESS AND STEERING MODEL BUILDER

Abstract: An application development environment for developing end user applications for supporting management of operational environment. The environment consists of a number of subsystems. An organisation modeller for defining the operational processes and the organisational units that are involved. A connection builder for defining connections to collect data from other systems. A view builder to define the views on the data. A distributor to create the end user application. A steering process modeller for defining a steering process by the steps of identifying a steering process, identifying at least one steering step for each steering process and linking the steering steps in order to build the steering process model. A model builder for defining steering models by the steps of identifying a steering model, defining input variables, defining output variables, defining the relation between the input and output variables.

Description: Steering process and steering model builder 1. Introduction This application for patent consist of the following : • organisational background of the invention • description of state of the art technologies • context of the invention • summary of the invention • detailed description of the invention • supplements 2. Organisational background of the invention Organisations operate a large amount of steering processes. The function of steering processes is to support the management of operational processes. To perform this function steering processes produce information. The information is used to support the decision making on operational processes. The information is based on implicit or explicit steering models which are developed by the organisation in order to control the operational processes. Information systems are used in the steering processes to produce the information. 3. Description of the state of the art technologies At this point of time various technologies or combinations of technologies are used to produce information. 1. On Line Analytical Processing (OLAP) software OLAP software is often used together with database technology. OLAP software is used to select (a part of) data collection. Furthermore the software is used to perform simple operations on the data en display the results of the operations. OLAP software pre- processes and stores the processed data collection to ameliorate response time in case of data selection. 2. Relational On Line Analytical Processing (ROLAP) software ROLAP is often used in combination with database technology as well. This type of software basically has the same functionality as OLAP. It is used to select large amounts of data, perform simple operations and display the results. In case of ROLAP no preprocessing takes place. A query is formulated in Structured Query Language (SQL) or a SQL related language. The query is executed on the database. 3. Functional software packages Functional software packages are used to run various large administrations such as financial administrations or employee/salary administrations. They offer reporting tools to define reports on the data which are available in the database. 4. Specialised control systems This type of software supports specific steering processes on a specific area like logistics or inventory control. Often they can only be used by specific organisations or branches like process industry or transport. 5. Spreadsheet Spreadsheet software is used to perform medium complex calculations. Spreadsheet software does not use database technology for data storage. Spreadsheet software offer various functions to display data. 4. Context of the invention The invention is a part of an application development environment. The development environment is intended to develop software applications which support the management of operational processes (see figure 1). The development environment consists of the following subsystems : • Organisation modeller This module is used to define the operational processes and the organisational units that are involved. • Connection builder The connection builder is used to define connections to collect data from other systems. • View builder This module is used to define the views on the data. • Distributor The distributor creates the end user application. The last two modules of the development environment make up the invention : • Steering process modeller • Model builder 5. Summary of the invention The invention is intended to define steering processes by naming the steering steps and store them in the database. Furthermore the invention is intended to construct and store steering models. Steering models can be constructed by configuring standard steering models. Finally the invention is intended to connect steering steps with steering models and store the connections in the database. 6. Improvements compared to the state of the art technologies The invention is innovative because none of the described technologies offer ways : • to construct steering models in a predefined way by using configurable standard models • to define steering processes by naming the steps and link them to the steering models Because of this invention it is possible to develop applications that support steering processes much quicker and with less effort than nowadays. 7. Detailed description of the invention The detailed description of the invention describes the process of defining a steering model, a sub model and a steering process and the linkage of steering models to a steering step. New Steering Model definition Figures 2 and 3 illustrate the process of defining a new steering model. The system asks for the name of the new steering model (1) and stores an empty steering model in the project file (2). Then the user is presented with three choices, namely defining a new sub model, editing an existing sub model or deleting an existing sub model (3). When the user chooses to add a new sub model (4, 5), the system asks for the name of the new sub model (Figures 4 and 5, step 15). The system asks the user for the type, 'free model' or 'standard model', of the new sub model (16, 17). • When the user chooses for a free model, the system loads the free model dialog from the dialog database and displays it (18, 19, 20). The system asks for the number of input and output variables of the new sub model (21, 22) and to name a variable for each input and output (23). Then the user has to enter the (logical) relation between the input and output variables (24). The sub model is stored in the project file (25) and the system returns to the steering model definition. • When the user chooses for a standard model (18), the system loads the available standard models from the standard model database (26) and displays a list of standard model types (27). The user chooses a standard model type and the system loads the accompanying dialog from the dialog database (28, 29). The dialog is displayed (30). The system asks the user to enter the values for the standard model parameters (31) and the variable name for each input and output (32). The sub model is stored in the project file (33) and the system returns to the steering model definition. When the user chooses to edit an existing submodel (6), the system asks for the name of the sub model to be edited (8). The system loads the sub model definition from the project file (9). When the sub model is of type 'standard model' (10) the system loads the standard model dialog from the dialog database (11). When the type is 'free model', the system loads the free model dialog from the dialog database (12). Subsequently the flow continues at (B) and (C) for free models and standard models respectively. When the user chooses to delete an existing submodel (7), the system asks for the name of the sub model to be deleted (13). The system deletes the sub model definition from the project file (14) and returns to the steering model definition. New Steering Process definition Figure 6 illustrates the process of defining a new steering process and steering steps. The systems asks to enter a name for the new steering process (50) and creates a new steering process in the project file (51). Each steering process consists of one or more steering steps. These steering steps can be nested, so each steering step is either a root step or has a parent step. For each steering process, the system will define the steering steps that belong to the steering process. The system asks to enter a name for a steering step (52) and to enter the parent step for the steering step (53). Subsequently the system stores the steering step in the project file (54) and offers to add another steering step (55). Connecting steering models to steering steps Each steering step of a steering process that has no sub steps (lowest level steering steps) has to be connected to a steering model. The system asks the name of a steering process (Figure 7, step 60, 61). The system creates a list of lowest level steering steps (62) of this steering process and asks the user to enter a name of a steering step (63, 64). Next, the system displays a list of available steering models (65) and asks the user to choose one (66). The relation between the steering step and the steering model is stored in the project file (67). 8. Examples Example of a steering process The capacity planning process can be used to illustrate a steering process and steering steps. This process consist of the following steering steps: 1. Demand forecast The expected demand is forecasted using specific forecasting techniques. 2. Generate capacity plan A feasible capacity plan is generated using a capacity planning algorithm. 3. Adapt capacity plan The generated capacity plan can be manually adapted. 4. Generate roster Based on the capacity plan, a roster is generated to fill in the capacity need. Example of a steering model For the steering step "Generate capacity plan" the following steering model can be used (see Figure 8). This steering model has three input variables and one output variable. The steering model is defined using two sub models. The first sub model is a free model, which calculates the amount of capacity needed based on the demand forecast and de cycle time per activity (see Figure 9). For the second sub model a standard model is used, namely "Finite Capacity Scheduling" (see Figure 10). This standard model generates a suggested capacity utilisation, using a standard capacity scheduling algorithm.

Claims: Claims 1. Method for developing end user applications in an application development environment for supporting management of operational processes in an organisation, in which the application development environment comprises • an organisation modeller to define the operational processes and the organisational units involved; • a connection modeller to define connections with the operational processes and/or other systems for collection of data; • a view builder to define views of the data; • a distributor for creating an end user application, characterised in that the application development environment further comprises • a model builder for defining steering models by the steps of: identifying a steering model, defining input variables, defining output variables, defining the relation between the input and output variables; and • a steering process modeller for defining a steering process by the steps of: identifying a steering process; identifying at least one steering step for each steering process; linking the steering steps in order to build the steering process model; and the method further comprises for each steering process the steps of: • displaying a list of lowest level steering steps associated with the steering process; • after selection of one steering step, displaying a list of available steering models for selection; • storing the relation between the selected steering step and the selected steering model; and • linking the input/output variables associated with the selected steering model to the data. 2. Method according to claim 1 , characterised in that the model builder performs the steps of storing the models in a standard model database, reading a model from the database, and/or modifying the identification, input/output variables and/or the relation between input/output variables. 3. Method according to claims 1 or 2, characterised in that the model builder further comprises the step of defining the number of and identifying the input and output variables. 4. Method according to claim 1, 2 or 3 characterised in that the steering steps comprise lower level steering steps, and the steering process builder comprises the further steps of linking the lower level steering steps. 5. Apparatus arranged for carrying out the method according to one of the claims 1 through 4. 6. Data carrier loaded with software which, after being loaded into a computer, provides the computer with the ability to carry out one of the methods according to claims 1 through 4. 7. Data signal comprising data which, after being loaded into a computer, provides the computer with the ability to carry out one of the methods according to claims 1 through 4.

Inventors: DE NOOIJ THOMAS, KOENDERS PHILIP JAN, DE NOOIJ, THOMAS, KOENDERS, PHILIP, JAN
Applicants: KOENDERS PHILIP JAN, NOOIJ THOMAS DE, DE NOOIJ, THOMAS, KOENDERS, PHILIP, JAN
Application year: 1999
Main classification: G06F17
IPC codes: G06F9