Device and method for producing a processing tool

0001Device and method for producing a processing tool

0002The invention relates to a device and a method for generating a processing tool, which processes an electronic workflow that includes work steps.

0003A procedure and a software tool called ARIS are disclosed in August-Wilhelm Scheer: "ARIS - from business process to application system", Springer-Verlag, 4th edition, 2002. It describes how to model a business process with ARIS how to create an application system that processes this business process.

0004A model of a business process is set up, cf. e.g. A.-W. Scheer, Fig. 24. Process elements of different types are used for this. It is possible to individualize reference models, e.g. for business processes in production, procurement, sales (A.-W. Scheer, Fig. 50). The business process is processed using a system for process control. Such systems are often referred to as "workflow systems" (Section D.III). In Section D.IV.2.2 ff. business objects are presented with standardized interfaces and access methods

0005The ARIS software tool ("framework") has an architecture with the following four layers (see section DV2.1):

0006- The process design layer, which includes tools to model a business process. A user can create process, function and data models, organization charts and diagrams for authorizations,

0007- The layer of process planning and control, which includes tools with which the processing of a business process is controlled and monitored, e.g. the "ARIS Process Control Interface" and tools for cost calculations that relate to work steps and activities ("ARIS Activity-Based Costing "),

0008the workflow management layer for processing workflows and with interfaces to workflow management systems,

0009- The layer of business objects ("ARIS Business Objects"). Examples of business objects are customer, order, work plan, work process, supplier.

0010Under the name "mySAP Supply Chain Management" (mySAP SCM), SAP offers a software environment for networking, planning, coordinating and executing a logistics chain for a manufacturing company. The software environment, which is available at http: // www.sap- ag.de/germany/solutions/scm/ (queried on March 13, 2002), it enables u. Adapting a logistic infrastructure to changes in the market, for example the introduction of new products or new customer segments ("supply chain design"). Every phase of the logistics process, from price calculation to delivery to the customer, is monitored and in the event of deviations from the plan notifications are sent ("supply chain event management"). Online shopping is integrated, including rule-based procurement, automated replenishment and support from multiple suppliers. Logistics chains are managed in all phases of the production process, even beyond company boundaries. The MySAP E-Procurement software environment supports both business-to-business procurement for production material and for indirect material. mySAP E-Procurement (http://www.sap-ag.de/germany/solutions/e_procurement/, queried on March 13, 2002) enables the strategic procurement of production materials such as raw and auxiliary materials, spare parts (eg speedometer) or other goods, and supports the purchase of indirect, non-manufacturing-related goods and services including operating supplies, office supplies, machine parts, janitorial supplies and repairs.

0011Both that in A.-W. Scheer, loc. Cit., The procedure and tool disclosed under the name ARIS, as well as the SAP modules described above, have fixed data models, for example for business objects, transactions, activity type changes. It is necessary that the user adapts his business processes and processing tools to these specifications, for example those of the data model. An adjustment ("customizing"), for example A SAP module often comes close to an individual solution for a specific business process.

0012US Pat. No. 5,774,661 discloses a method and a device for controlling the processing of workflows using a graphical user interface without the need for individual programming. A network central computer ("Workflow Server Computer") comprises data storage for data objects ("object repository") and a first interpreter for logical rules ("rule engine"). The interpreter evaluates complex logical expressions, for example to to decide on the forwarding of documents depending on variables. The network central computer is connected to at least one network subscriber computer (“serves computer”). This runs a graphical user interface with which one can generate electronic work processes (“workflow builder”), a rule generator (“rule builder”) ") and another rule interpreter. These workflows route data objects through a data network (“routing”), depending on user input and the actions of the rule interpreter. The description language and the mode of operation of the rule interpreter are described in detail. A script executor ("Script handler") converts the results of the rule interpreter into commands for external application programs, for example for data output or the sending of e-mails.

0013According to the method disclosed in US 5,774,661, each workflow must be graphically generated again with business rules. Even if different companies have different workflows for the same application category, e.g. the procurement of goods and services, have defined and need processing tools for these workflows, each time a workflow has to be made available to a computer again with the graphical user interface and the "workflow builder".

0014The invention has for its object to provide a device and a method by which a device for processing any electronic workflow on a data processing system is generated quickly and efficiently.

0015The object is achieved by a device according to claim 1, a method according to claim 9 and a computer program product according to claim 14 or claim 15. Advantageous refinements are specified in the subclaims.

0016The processing tool can be adapted to any electronic workflow with work steps. This means that it is not necessary to restrict the design of the workflow, for example because it has to match a specific information model with certain data object types and relations between them or because it has to be compatible with a given standard workflow. The invention also saves having to implement an individual solution “from scratch” for a workflow that is not compatible with a standard workflow or a standard processing tool, which is time-consuming and error-prone.

0017According to the invention, the information model is adapted to the workflow instead of having to adapt the workflow to the information model. Because that used. The information model is tailored to the electronic workflow by adapting a given standard information model by adding, deleting or changing data objects. This saves work compared to the procedure of creating an information model "from scratch".

0018The invention makes it possible to integrate existing legacy systems logically and not only at the data technology level and to reuse the data and information stored in them. Old systems can still be used as data sources. This reuse saves having to adapt the data and information to a new processing tool with great effort and a high risk of errors. It is also not necessary to change legacy systems or even take them out of production use or to adapt the processing tool to an legacy system.

0019In the following an embodiment of the invention will be described with reference to the accompanying drawings. Show

0020Fig. 1. an example of a company-specific

0021Information model with the data object type "scope of procurement"; FIG. 2 shows a section from an electronic specification of a workflow;

00223 shows an exemplary architecture of the device.

0023The method according to the invention is explained using the example of supplier management of a manufacturing company, for example an automobile manufacturer. The processing tool 560 generated according to the invention is called supplier manager for this example. It includes a data storage system^• 570, an application layer .561 with processing logic and a user interface layer 562 with user interface. However, the method according to the invention can also be used for any other field of application in which a workflow is to be processed electronically and a processing tool is required for this.

0024Supplier management refers to a set of activities that are carried out with the aim of ensuring that a company receives goods and services from external and / or internal suppliers on time and on schedule, "has their purchasing costs under control" and controls variants and customer complaints. Every company that manufactures technical products must operate supplier management in a suitable way along its value chain in order to survive on the market.

0025Typically, the supplier management comprises a selection of at least one supplier and an implementation and monitoring of the procurement of a specified scope of procurement from the selected supplier. Supplier management preferably includes individual work processes, for example for awarding, handling changes and reducing costs. Supplier management often spans multiple companies, multiple locations, multiple functions, and multiple disciplines. The supplier management preferably also includes operative purchasing, for example with a tender, soliciting offers, deciding on at least one offer, concluding a contract and monitoring the delivery. Purchasing auctions on the Internet can be part of supplier management. The supplier management of a manufacturing company is preferably limited to the direct suppliers of the manufacturing company. The manufacturing company does not take into account in its own supplier management that these direct suppliers in turn have suppliers who are upstream suppliers from the perspective of the manufacturing company.

0026Supplier management is defined by a business process that specifies individual workflows of supplier management. Such a workflow comprises work steps, each of which has at least one input and / or at least one output. Many manufacturing companies have defined company-specific business processes, for example for supplier management. For this definition, they often have considerable effort, for example operated for coordination between participating organizational units. A company often differentiates itself from its competitors by good business processes.

0027An advantage of the invention is that the method provides a supplier manager for individual or all work processes of this company-specific business process. The supplier manager is tailored to the work processes of the business process with little effort, instead of having to tailor the business process to a specific procedure or to a specific information model, data model or software product. An efficient supplier manager standardizes the business processes, eg the purchasing processes. A binding, comprehensible and ideally optimized business process for supplier management, which is linked to the product creation process, is supported and partially automated. Non-optimized business processes can also be supported by the supplier manager. The supplier manager makes the business process transparent and allows you to intervene in a timely manner, for example if there is a risk that deadlines will not be met. This enables a company to save costs and to reliably meet cost and schedule specifications and master variants.

0028The generated supplier manager can be used - in addition to the "actual" supplier management - in particular for the following application purposes:

0029• for predicting costs or deadlines

0030• As a data analysis tool ("data warehouse") for subtasks of supplier management - thanks to the generic information model and the integration into the IT environment, the data is available that is required for meaningful statistical evaluations.

0031• for the simulation - the supplier manager tests a fictitious procurement scope, whereby the scope of procurement goes through the business process or individual work processes. Weaknesses in this business process or workflow can be identified.

0032• to compare alternatives during the specification or during the execution of a workflow. In order to compare two alternatives of the workflow, two supplier managers are created using the method according to the invention. The two two supplier managers are compared. In particular, an average number

0033- from generated screen forms,

0034- of required screen interactions - of database read access

0035- And / or compared to database write accesses.

0036• as an early warning system - which process steps can lead to delays, which steps belong to the critical path ("critical path")?

0037for the education and training of employees.

0038The supplier manager created according to the invention is a software system that can run on a first data processing system. The supplier manager includes a single workflow or a set of electronic workflows. A goal is specified, eg selection of suppliers for a specified scope of procurement. A business process specifies the work processes. After selecting some of these workflows, the selected workflow (s) are run through. Typically, a sequence of screen forms is run through here, in which buyers and employees of suppliers enter inputs, for example a delivery date for an inquiry or a price for an offer. Such a form preferably comprises at least one input field, a field for the display of data and a navigation element. An electronic document is repeatedly generated from user entries in a screen form.

0039In a larger company, several procurement scopes and thus several "instances" of work processes are processed in parallel, for example, a procurement scope for the "driver's seat car type A", one for the "headlight car type B" and one for the "body in white car type C". The instances can be in different processing status or maturity levels. The invention makes it possible to efficiently generate a supplier manager who can process a complete business process. This business process is modeled by the specifications of several workflows. Each workflow is preferably characterized by a data object, which is enriched, refined or otherwise processed, for example by processing the workflow. For example, attributes of the characterizing data object are assigned values ​​or relations between the characterizing data object and further data objects are generated. The workflow also refers to other data objects. For example, by reading in or changing these other data objects, or by linking them to one another by means of relations.

0040Preferably, several work processes of a business process are not directly linked to one another or extended beyond the intended scope. Rather, two work processes are connected to one another via the common database of the supplier manager, whose data model 531 was generated using the company-specific information model 530. In particular, two workflows automatically interact with one another in that the first workflow inserts data objects into the data storage system 570 or changes existing data objects and the second workflow reads in some of these data objects. Conversely, the second workflow can supplement or change data objects that the first reads. This decoupling means that work processes can be changed independently of one another, and the supplier manager has a modular structure.

0041A preferred embodiment of the method according to the invention for generating a company-specific supplier manager comprises the following steps:

0042• A company-specific information model 530 with types of data objects is generated by adapting a standard information model for supplier management to the workflow to be processed if necessary.

0043This company-specific information model 530 is used to generate a specific data model 531 as the physical data storage scheme of the data storage system 570. If, for example, a relational database is used for data storage, a relational database schema is created as the data model. A data storage system 570 of the processing tool 560 is generated on the basis of this data model 531.

0044At least one of these standard workflows is selected from a library 540 with electronic standard workflows. A standard processing tool is assigned to each electronic standard workflow. Such a standard processing tool is a processing module that can be processed by the data processing system and has read and / or write access to the data storage system 570.

0045• A specification 550 of a generally company-specific workflow with work steps is generated. For this specification 550, data object types of the company-specific information model 530 and relations between them are used. To create specification 550, the selected standard workflow is modified if necessary.

0046• Calculation or checking rules that relate to data objects and / or work steps and can be carried out automatically are generated.

0047• The standard processing tool of the selected standard workflow is configured using the specification 550 of the workflow to be processed. • The processing modules are integrated into the Supplier Manager 560 and inserted into a specified IT environment.

0048These steps are described in detail below.

0049Commercial software tools are preferably used in an inventive manner, in particular

0050to generate the specific information model 530 and the data model 531,

0051- establish specification 550 of the workflow,

0052- generate calculation and test rules,

0053to create the electronic workflows ,

0054Realize interfaces to old systems in the IT environment

0055- And generate a source program in a suitable programming language, such as Java.

0056The method according to the invention makes it possible to quickly and efficiently generate a supplier manager for a predetermined and generally company-specific workflow. If the workflow is later changed or expanded, the method can advantageously be carried out again in order to create a new supplier manager for the changed business process. It is not necessary to manually adjust the supplier manager. This avoids the risk that the changed supplier manager is no longer compatible with the new workflow.

0057According to the invention, a specific information model 530 is used for the specification 550 of the workflow. A Modeil is a simplified and inevitably incomplete image of a section of reality. The model contains the properties and dependencies of reality that are needed to solve a specific task. The term "information" denotes the abstract meaning (the "semantics") of a statement, description, instruction, message or message. Data is used to represent and store information, for example in a computer. An information model is a simplification of reality that structures information and facts for the processing of at least one task. A data model describes how the data structured according to an information model is physically stored, for example in a file or a database. A relational database schema and an entity-relationship diagram are two examples of such data models.

0058The supplier manager 560 generated according to the invention comprises or has read and write access to a data storage system 570, for example a database with data objects. The data objects represent physical or commercial business objects that are used for supplier management or play a role in it.

0059The. Database is preferably generated using a data model 531 in such a way that the data objects of the database and the relationships among these data objects are compatible with the data model.

0060The company-specific information model 530 is preferably generated by tailoring a generic information model to the conditions and requirements of the manufacturing company (“information model customizing”). Both information models include types of data objects and relations between these data object types. The generic information model applies, for example, to the supplier management of every manufacturing company. The generic information model is preferably tailored to a specific business process, a specific workflow and / or a specific company by deleting or modifying types of data objects of the generic information model. In particular, data objects of the generic information model that are not required for this business process and this company are deleted. If necessary, data objects are added. Data object types are modified, for example, by adding or deleting attributes or by specifying preferred or standard values. However, the generic information model is so powerful that it is sufficient for most use cases in a category. One such category is, for example, the supplier management of manufacturing companies described by a business process with work processes.

0061The generic information model includes all data object types and relations that are required to describe a workflow for the supplier management of a manufacturing company. The generic information model thus replicates the conceptual world of process experts. It supports and facilitates a complete notation and modeling of the work processes including all input and output variables and parameters of work steps. Because the conceptual world of the process experts is replicated, a complex and error-prone translation step between models and descriptions of the experts and an IT language that can be used for IT purposes is not necessary, and media breaks do not occur. This advantage is particularly noticeable in the event of subsequent changes and additions during the specification of work processes.

0062This type of generation of the company-specific information model 530 and the data model 531 derived therefrom requires considerably less time and costs than generation “from zero”. The risk decreases that essential facts in the information model that the data storage system 570 of the processing tool 560, and may therefore not be taken into account in the specification 550 of the workflow. Rather, the likelihood that a complete information model will emerge increases.

0063The generic information model is preferably tailored so that it is compatible as far as possible with information models of productively used legacy systems, for example for inventory management or production control. This allows these legacy systems to remain productive. They will not only be integrated into the supplier management and the supplier manager at the logical level, but also at the logical level. The old systems can still be used, an expensive reimplementation of, for example, proven old systems is not necessary. Double data storage is not necessary. If required, such an old system acts as a data source for the supplier manager or, conversely, “obtains” data from the supplier manager 560. This is made possible, among other things, by the company-specific information model 530.

00641 shows an example of a generic information model for supplier management. In this example, data object types are represented by rectangles and relations between these data object types are represented by lines. The relationships between data object types determine which relationships between data objects of these types are permitted. A special relation between two data object types A and B is the contained relation, which is identified by a diamond. For example, the data object type 100.1 (“scope of procurement”) explained below is connected to the data object type 100.2 (“scope of procurement”) by such a relation. A procurement scope can contain several sub-procurement scopes, therefore a data object for a procurement scope can be connected with several data objects for a sub-procurement scope in each case by an included relation. The diamonds in Fig. 1 are close to the types of those data objects that can contain other data objects. The relations between data object types are further provided with membership intervals 110, which indicate upper and lower bounds as to how many data objects of these types can be connected to one another by a relation. Such a membership interval has the form "a: b", where a is a natural number or the 0 and b are a natural number or "n" as a symbol for the absence of an upper bound. Specialization relations are also shown by an edge with an arrow at one end. The notation of FIG. 1 is based on the "Unified Modeling Language" (UML) as a known object-oriented description medium.

0065A preferred component of the information model in FIG. 1 is the data object type 100.1 (“scope of procurement”). This type summarizes all data objects that represent the scope of procurement. A scope of procurement describes one or more subsystems or functional groups or assemblies "Shell", "headlights" and "driver's seat".

0066A data object for a scope of procurement preferably goes through a complete workflow or even several workflows for supplier management. At the beginning of this workflow, the scope of procurement is only roughly described functionally. Certain component types or material groups or even part numbers are usually not assigned to the scope of procurement at the start of the workflow. Above all, this means that the scope of procurement differs from a material group that only summarizes certain previously defined component types.

0067The processing of a business process with several workflows for supplier management is preferably started at an early stage of product development, at which specifications and decisions for certain component types have not yet been made. In the course of product development, the internal structure of a subsystem or a functional group or assembly is defined, computer-aided designs are created, and in the business process for supplier management, the corresponding objects, such as component types or material groups, are assigned to the scope of procurement. If necessary, the necessary manufacturing tools, software programs or services are also defined, specified in detail and assigned to the scope of procurement as corresponding data objects or attributes. At the end of the business process, the scope of procurement virtually forms a shell, a "cocoon", which has attributes and is linked by relations with several other data objects that specify the scope of procurement in detail. These further data objects are, for example, material groups, component types, delivery dates, prices, quality requirements, quantity, suppliers, production sites, required tools and software programs.

0068The data object type for the scope of procurement is therefore included in the information model so that one and the same procurement scope goes through the entire electronic workflow or even the entire business process and is enriched with relationships with other data objects and with attributes. The supplier manager preferably creates a data object for a procurement scope at an early point in time and thus enables efficient IT support for the early integration of suppliers. It is not necessary that the supplier manager creates specifications at an early stage that cannot be made yet. It is also not necessary to create a data object with few specifications for early phases of the business process and another data object with many specifications for late phases. This would lead to duplicate data storage and possibly to inconsistent and contradictory data, especially if changes are made later, but are not extended to all data objects.

0069A data object of the data object type for procurement scopes makes it possible to run a workflow relevant to the purchasing of the manufacturing company without, for example, constructive refinements and determinations in the course of the product creation process leading to translation steps, media breaks or the like and without asking for or even information that are not yet available at the current time.

0070The data objects of the type for procurement scopes enable a size relevant to purchasing to run through the workflow without, for example, constructive refinements and specifications leading to translation steps, media breaks or the like in the course of the product creation process and without information being requested or even forced, that are not yet available at the current time. Instead, a procurement scope is enriched with information such as component types during its run through the workflow.

0071The generic information model also includes, for example, the following types of data objects and relationships between these types:

0072- A data object for a procurement scope can be directly related to the data objects that define and describe the procurement scope in detail, or it can include several sub-procurement scopes, which in turn are linked to the data objects for detailed specifications. A partial procurement scope is the smallest data object for purchasing. A partial procurement scope is preferably related to exactly one supplier. The partial procurement scope is linked to all data objects that describe the procurement scope in detail and are used to obtain the part of the procurement scope that comes from this one supplier. If the objects of a procurement scope are obtained from several suppliers, at least one partial procurement scope is generated for each supplier. It is possible to generate several procurement scopes for a supplier, for example if the supplier delivers to several manufacturing sites of the manufacturing company. The information model in FIG. 1 comprises a data object type -100.2 (“partial scope of procurement”), which is linked to data object type 100.1 (“scope of procurement”) by an included relationship. A procurement scope does not contain any, one or any number of partial procurement scopes, which is determined by the membership interval 110.1 with the value "0: n". Conversely, a partial procurement scope belongs to exactly one procurement scope, which is determined by the membership interval 110.2 with the value "1: 1".

0073A product type identifies the type of product to which the scope of procurement relates. A product type includes one or more procurement scopes. In the case of a car manufacturer, this product type is often characterized by a series (e.g. A-Class), a body type (e.g. sedan or coupe) and a functional group. The information model of Fig. 1 includes a data object type 100.4 ("function groups"), 100.5 ("series"), 100.6 ("body types") and 100.9 ("material groups").

0074A quantity structure indicates the expected number of pieces of the product type. Using a distribution rule assigned to the quantity structure, this number of pieces can be distributed to different production sites. In this division rule, the case is preferably taken into account that different subsystems or assemblies of a product are manufactured in different production sites.

0075- The product to which the supplier management relates is preferably described by a hierarchical product structure. This product structure preferably applies not only to a specific product type, eg a series, but to a category of products, eg for each car in a specific segment. The product structure is, for example, a description of a hierarchical breakdown of the product in the form of a tree structure. The nodes of this tree structure stand for individual viewing units of the product, eg for function groups, subsystems, assemblies, components. The root of the tree structure stands for the product as a whole, the leaves for components treated as elementary. A separate data object type 100.1 (“product types”) is introduced for these observation units.

0076- A component type is described by its own data object. The information model of FIG. 1 comprises a data object type 100.10 (“component types”).

0077- A material group is also described by its own data object and identified by a unique material group identifier ("commodity code"). The material groups preferably form a tree-like relationship hierarchy (taxonomy), the leaves of which are available component types. The material group identifier is hierarchical. For example, the material group identifier consists of six digits, of which the first two digits designate the function group and the next two digits the assembly in which the component type is used. The last two digits distinguish the component types of an assembly from each other. A data object for a material group can be created using relations, for example be connected with a scope of procurement or a partial scope of procurement, with component types, with consideration units and at least one supplier quantity. A procurement scope or a partial procurement scope can be linked by relations with one or more material groups. 1 includes a data object type 100.9 ("material groups").

0078- The generic information model takes into account different variants of a component type or assembly, which is particularly important in the automotive industry with its high number of variants and complexity. Therefore, data objects for position variants are made possible and a data object type is provided for them in the information model.

0079A supplier is represented by its own data object. For example, the supplier can be assigned information about official certifications and approval decisions of the manufacturing company. The information model of FIG. 1 a data object type 100.3 ("suppliers") for the suppliers available at all and a further data object type 100.13 ("selected suppliers") for the suppliers selected for a scope of procurement or partial scope of procurement.

0080- During the processing of a workflow for supplier management, one or more suppliers are often selected for a given scope of procurement. This scope of procurement relates to certain observation units and is linked to material groups and / or component types. Often, a set of suppliers is already specified for a material group, a consideration unit or a component type, and only one or more of these suppliers are selected. A separate class for supplier quantities is therefore provided in the information model. In a training course, two types of supplier quantities are distinguished and therefore two classes of supplier quantities are included in the information model. A specified strategic supplier quantity is a quantity of suppliers, for example for a material group, which are defined in advance on the basis of fundamental specifications of the company, the specification being valid for many procurement scopes. A provisionally selected set of suppliers consists of suppliers that have been preselected for a certain scope of procurement in an early phase of the business process. The information model therefore includes a data object type 100.11 ("strategic supplier quantities") and a further data object type 100.12 ("provisional supplier quantities")

0081A manufacturing facility is represented by its own data object. This data object is linked by relations, for example, with data objects for procurement scopes or^' Partial procurement scopes as well as for consideration units. The information model comprises a data object type 100.8 ("manufacturing facilities").

0082- In order to be able to assign the responsibilities to the work steps in the specification 550 of the workflow, a data object type 100.16 ("responsible persons") is added for the responsibilities. A data object for a responsibility can be created by relations, for example, with a data object for a procurement scope for a consideration unit or a material group.

0083- All documents for inquiries and tenders that are dispatched for a specific procurement scope or partial procurement scope are managed in separate data objects that have references to these documents and to administrative information on the documents. A separate data object type 100.17 for "requests" in the information model is provided for these data objects. The data objects of this data object type are linked by relationships with procurement scopes or with partial procurement scopes as well as with the respectively selected suppliers.

0084- Similarly, all offers for a specific scope of procurement or partial scope of procurement are managed in a separate data object. A separate data object type for "offers" is also provided for these data objects in the information model. The data objects of this data object type 100.15 are linked by relationships with procurement scopes or to partial procurement scopes and with the respectively selected suppliers.

0085Both the generic information model and the company-specific information model 530 are independent of a specific physical data storage scheme, for example a certain database scheme. For this reason in particular, the information models are independent of a specific IT environment in which the supplier manager is used. Different data models and thus different data storage schemes can be derived from the same information model, e.g. Database schemas for relational or object-oriented databases. For example, a relational database can be replaced by another relational or object-oriented database without having to change company-specific information model 530 or workflow specification 550 or business rules.

0086The generic information model includes all data objects and relations that are required to specify the workflow or processes for the supplier management of a manufacturing company. The generic information model thus replicates the conceptual world of process experts. It supports and facilitates a complete notation and specification of a workflow including all input and output variables and parameters of work steps. Because the conceptual world of process experts is replicated, a time-consuming and error-prone translation step between the specifications and descriptions of the experts and an IT language that can be used for IT purposes is not necessary, and media breaks do not occur. This advantage is particularly noticeable in the event of subsequent changes and additions during the specification of work processes. The most suitable data model with the most suitable information technology description language can be used, for example "Entity-Relationship Diagrams" (ER diagrams) or the "Unified Modeling Language" (UML).

0087The business process is described by an electronically available specification 550. This specification is generated and stored with a device 580 for specifying a workflow. This facility is called the specification facility in the following. The specification device 580 preferably comprises a second data processing system.

0088The specification 550 generated with the specification device 580 describes, for example, all work processes that occur in supplier management. The specification 550 is tailored to the requirements and conditions of a manufacturing company, for example to the supplier management of an automobile manufacturer. Specification 550 preferably uses those data objects and relations between data objects that correspond to data object types or Relationships between data object types of the company-specific information model 530 belong.

0089A workflow is preferably specified using a directed graph with nodes and edges. The "inputs" of a node K are then the edges from the predecessors of the node K to the node K, the "outputs" the edges of K to its successors. 2 shows an exemplary section from an electronic specification 550 of a workflow. This graph has at least the following types of nodes:

0090- Event nodes 200.1, 200.2, ..., eg "Scope of procurement defined" or "Strategy for allocation process defined" or "Supplier quantity for allocation process defined". The event nodes also include the start event nodes, which have no predecessor and at least one Have successors and act as entry points to a workflow, and target event nodes that have no successors and at least one predecessor.

0091- Function nodes 210.1, 210.2, ..., eg "Check order" or "Change dates", which have at least one predecessor and at least one successor, define work steps of a workflow and are preferably described by activities,

0092- Data object nodes 220.1, 220.2, ..., for example data objects for "partial procurement scope" or "supplier", which stand for a flow of information into or out of the workflow, for example read or write access to a database, the at least one Have predecessors or at least one successor and are of a data object type of company-specific information model 530,

0093- Organizational unit nodes 240.1, 240.2, ..., for example "project manager product" or "specialist buyer", who determine who is responsible for the execution of a work step. As a rule, an organizational unit node is assigned to a function node, for example by an edge for an organizational flow. The supplier manager can also be responsible instead of a natural person,

0094- Process variable nodes 240.1, 240.2, ..., eg "Status allocation process". A process variable node is connected to the event nodes, the event of which is that the relevant process variable takes on a certain value. For example, a process variable node "Status procurement process" connected to the event node "Supplier quantity defined for procurement process". The same or further process variable nodes "Status award process" are connected to other event nodes, the event of which relates to the status of the work process, for example the award process,

0095- AND connection node 410.1 with several predecessors and one successor, which influences the processing of a workflow. If all predecessors, which are event nodes, are fulfilled and all predecessors, which are function nodes, are executed, then the successor of the AND connection node is adopted. For example, an AND connection node 410.1 has the predecessors "change scheduling assignment" and "noted change of appointment" and the successor "release new appointment".

0096- OR connection node 400.1 with several predecessors and a successor, which also influences the processing. If at least one predecessor is fulfilled or executed, the successor is transferred. For example, an OR connection node has the predecessors "add potential suppliers", "delete potential suppliers" and "potential suppliers confirmed" and the successor "defined potential suppliers".

0097- X-OR branch node 420.1 ("exclusive or") with several predecessors and one successor. If exactly one predecessor is fulfilled or executed, a transition is made to a successor. A branching condition determines under which condition the transition is made to which successor. For example, an X-OR branch node 420.1 has the predecessors “written award documentation” (an event node) and “revision award documentation” (a function node) and the successor “approve award”.

0098- AND branch node with a predecessor and several successors. If the predecessor is fulfilled or executed, all successors are transferred.

0099OR branch node 430.1 with one predecessor and several successors. If the predecessor is fulfilled or executed, the system switches to at least one successor.

0100- X-OR branch node ("exclusive or") with a predecessor and several successors. If the predecessor is fulfilled or executed, then exactly one successor is passed. A branch condition determines under which condition the successor is passed. For example, an X-OR branch node "match potential suppliers" and the successors "obtain all approvals" and "clarify potential suppliers".

0101A solid arrow in FIG. 2 stands for a function flow 310.1, 310.2, ... for example from a data object node, a dashed arrow for an information service flow 300.1, 300.2, ..., a solid line for an organizational flow 320.1 , 320.2, ....

0102The electronic specification 550 of the workflow is preferably structured hierarchically in the sense that a single complex work step of a coarse granularity is written by a sub-business process of a finer granularity. For each step of the business process, inputs, outputs, responsibilities (which roles? Who?) And statements regarding dates and execution times are defined as described above. Master data management is often part of the workflow.

0103A preferred embodiment of the device 600 according to the invention is shown in FIG. 3. Solid arrows in FIG. 3 represent information flows during the creation of the processing tool. Dashed arrows represent information flows during the work of the processing tool.

0104Standard information models are stored in an electronic library 510.

0105The device 520 for generating a company-specific information model 530 comprises

0106Means for selecting a standard information model of library 510,

0107- Means for adding, deleting or changing data object types of the selected standard information model

0108- And means for adding, deleting or changing relations between these data object types.

0109The company-specific information model 530 is generated with the aid of the generation device 520.

0110The specification device 580 has read access to this company-specific information model 530 and to an electronic library 540 with preconfigured specifications of standard workflows. A standard processing tool from a further electronic library 590 is assigned to each specification of a standard workflow. The specification device 580 comprises means for selecting one of these standard workflows. It creates the specification 550 of the workflow. A configuration device 500 has read access to the further electronic library 590 with standard processing tools and to the specification 550. The configuration device 500 configures the standard processing tool of the library 590 that is assigned to the selected standard workflow is. The configuration device 500 uses the specification 550 for this. The configured standard processing tool can process the workflow specified by specification 550.

0111Calculation and checking rules link data objects of certain types described by the information model 530. Other rules relate to work steps or events in the business process or link data objects to work steps or events. Such rules are sometimes called business rules. An exam rule checks, for example Work steps or data objects generated during processing for integrity and consistency (consistency) and completeness. For example, such a checking rule ensures that each data object for a partial procurement scope is in exactly one of three possible statuses, or the work step "Select supplier for a partial procurement scope" is in exactly one of five possible statuses during the entire processing. Other rules carry out calculations, for example by calculating an invoice amount with VAT and the like. Determine the sum of the individual items, calculate gross / net effects or determine the actual expected value from cost items. Business rules and their application for work processes are known for example from WO 01/13303 AI.

0112The calculation and checking rules for a supplier manager are preferably generated by selecting rules from a predefined library with standard rules and adapting the selected rules if necessary. The adaptation is necessary, for example, to adapt the rules to the company-specific information model 530, the specification 550 of the workflow or to other company-specific circumstances. Other circumstances may include a company-specific product data structure, such as a specific structure for parts lists or product documentation.

0113In order to generate the company-specific information model 530 and the specification 550 of the workflow to be processed for the manufacturing company, the following procedure is used, for example:

0114• IBZED matrices are set up. These define information, participation, consent, decision, implementation

0115(= IBZED).

0116• The company-specific information model 530 is set up as described above. A data model 531 is derived from this. An object-oriented description language, for example the Unified Modeling Language (UML), is preferably used for the data model 531. The UML model includes use cases, class diagrams and activity diagrams. Among other things, it contributes to the specification of the user interface. The data model defines a data retention scheme.

0117With a software tool 580, a specification 550 of the workflow or workflows is generated. Such software tools are known in principle, for example from A.- W. Scheer, loc. Cit. And WO 02/19224 AI. According to the invention, the company-specific information model 530 is used for this.

0118• For example, calculation and / or checking rules are used to supplement objects and relationships that cannot be expressed by the software tool 550 used for modeling. • If required, specification 550 of the workflow is supplemented by textual descriptions. These descriptions are especially assigned to individual work steps or complete work processes. At least one form template is used for this, for example filled out with a word processing system. If necessary, descriptions are added in free text.

0119For these steps, additional IT support for the collaboration of people ("groupware") is used, for example group interaction software, discussion databases, a conference system and e-mail.

0120An IBZED matrix comprises a sequence of work steps to be carried out successively and / or in parallel in supplier management. Each work step is preferably characterized by an activity, for example "initiate the award process". Furthermore, the following information is defined for each work step:

0121the individual activities that make up the work step, for example, "define the scope of partial procurement", "preselect supplier quantity" and "release preselected supplier quantity",

0122the prerequisites for the work step, in particular the complete execution of certain other work steps, the results of which are required, for example "award strategy released",

0123- The results that the work step delivers after complete execution, eg "Assignment process arrived as task in the electronic inbox of specialist buyers and function group spokesman", - Responsibilities, eg which organizational units and owners of which roles are involved and how, and comments.

0124The way in which an organizational unit or a role holder is involved is identified by one of the five stipulations information, participation, approval, decision, implementation.

0125It is possible to create the workflow specification 550 "from scratch." However, labor and time are saved and the risk of errors is reduced if preconfigured specifications of standard workflows from a library 540 are used instead ("Workflow customizing "). These selected workflows are then parameterized and adjusted. This procedure requires much less effort than, for example "Customizing" a workflow management system that does not have standard workflows for supplier management, or even an individual implementation or specification "from scratch".

0126The specifications of the standard workflows are preferably described with the aid of the data object types, attributes and relations of the generic information model and the node types described above for workflow specifications. The company-specific workflows are specified using the data object types, attributes and relations of the company-specific information model 530. In addition, the workflows include data-technical data objects that control, for example, the execution of the workflow including resetting or, with the help of the data storage system 570, ensure persistent data storage and multi-user operation without access and data conflicts. Library 540 preferably includes the following standard workflows for supplier management:

0127Definition of strategies or specifications for award decisions for a specified scope of procurement to at least one supplier,

0128- awarding a specified scope of procurement to at least one supplier (award process),

0129- handling changes to at least one specified procurement scope,

0130Registration and / or evaluation of at least one supplier

0131- Monitoring the procurement process for a given scope of procurement and

0132Cost reduction for a given scope of procurement

0133- Formation of a cost target for at least a given scope of procurement

0134- Formation, a cost target for at least one cost element that is related to at least one predefined scope of procurement.

0135The electronic workflow for the award process is described as an example. At least one scope of procurement or partial scope of procurement is specified. For each specified scope of procurement and partial scope of procurement, an assignment type has been defined. Possible types of award are direct award to a supplier, classic tender and concept competition.

0136After the award process has been completed, the following target results are achieved: • The potential suppliers for each procurement scope or partial procurement scope are preselected. For this purpose, a preselection is made from the suppliers generally approved for the scope of procurement or partial scope of procurement. The final selection will be made later from these suppliers.

0137• Dates for component specifications specifying the component types to be delivered are set.

0138• Inquiries were sent to the potential suppliers.

0139• The offers that have arrived have been compiled and can be managed using a "Offers" data object.

0140• The standard documents for contract design are available.

0141• The procurement documentation has been created.

0142At least one standard workflow from library 540 is selected. If required, the selected standard workflow is adapted to the company-specific information model 530.

0143When the specification 550 is generated, the selected standard workflow is adapted to the workflow to be processed. If necessary, steps in the standard workflow are added, deleted or changed.

0144A standard processing tool is assigned to each electronic standard workflow from library 540. It is possible that the same standard processing tool is assigned to different standard workflows. The standard processing tools are stored in a library 590. Each of these standard processing tools is linked to a data storage system, such as a relational database. Different standard processing tools can be linked to the same data storage system. It is also possible that all standard workflows are assigned the same standard processing tool or that all standard processing tools are connected to the same data storage system.

0145The standard processing tool of the selected standard workflow is configured using the specification 550 of the workflow to be processed. The data storage system 570 of the processing tool 560 is configured with the company-specific information model 530 and the data model 531 derived therefrom.

0146The software architecture of the supplier manager 560 preferably comprises three logically separate layers:

0147the user interface layer 562 of the user interface with screen forms,

0148- The application layer 561 with a control of the processing based on the application logic and control of the user interface and the application of rules

0149and the data storage layer 563 with the data storage system 570.

0150The three levels are separated from each other in such a way that they only interact via defined interfaces. This means that a software tool, such as data storage or a component of the user interface, can be exchanged without the other components of the supplier manager having to be adjusted. Because the layer 562 of the user interface is separated from the application layer 561, it can easily be adapted to a predetermined standard for the screen design and the user guidance ("style guide"). Changes to the application or even data storage layer 563 are not necessary.

0151Internet technologies are preferably used. The users of the supplier manager have access to the supplier manager via a company intranet or the Internet. For read and write access, an Internet access program (“Web browser”) on a network subscriber computer (“client”) is preferably sufficient, so that no or only a few components of the supplier manager or data objects for this on the network subscriber computer Supplier management need to be saved. Rather, data is stored in a data storage system 570, e.g. a relational database, stored on at least one network central computer (server) and kept available. The data management system 570 ensures that only one user can have write access to a data object at a time, so that data integrity is guaranteed.

0152The device 600 according to the invention is also preferably implemented using a multilayer architecture. Such architectures are, for example, from A.-W. Scheer, loc. Cit., Known. The ARIS software tool disclosed there has an architecture with the following four layers:

0153- The process design layer, which includes tools to model a business process. A user can create process, function and data models, organization charts and diagrams for authorizations,

0154the layer of process planning and control, which includes tools with which the execution of a business process is controlled and monitored, e.g. the "ARIS Process Control Interface" and tools for cost calculations related to work steps and activities ("ARIS Activity-Based Costing "),

0155- the layer of workflow management for processing workflows and with interfaces to workflow management systems,

0156- The layer of business objects ("ARIS Business Objects"). Examples of business objects are customer, order, work plan, work process, supplier.

0157The device 600 according to the invention can be implemented, for example, on the basis of a development environment called Versata. This is, for example, at http: //www.versata. com or http://www.versata-deutschland.de/, queried on February 20, 2002. Versata generates the business logic and the associated change and management processes on the basis of the company-specific business rules with the help of "Business Logic Automation".

0158The supplier manager 560 generated according to the invention preferably has interfaces to legacy systems that belong to the IT environment in which the supplier manager is used and that continue to be used. These old systems include, for example an inventory management system, a production planning and control system ("enterprise resource management system"), a system for customer care and for customer orders ("customer relationship management system"), a product data management system ("engineering data management system") and a document management system (" document management system ").

0159In summary, the invention relates to a device 600, a method and a computer program product for generating a processing tool, which processes an electronic workflow that includes work steps and includes an application layer 561 and a data storage system 570. A company-specific information model 530 with types of data objects is generated by adapting a standard information model, for example for supplier management. This company-specific information model 530 is used to generate a specific data model 531 as a physical data storage scheme. The data storage system 570 is generated on the basis of this data model 531. A specification 550 of the workflow to be processed is generated by selecting a standard workflow from a library '540 and adapting it to the workflow and, if necessary, to the company-specific information model 530. A standard processing tool from a further library 590 is linked to the selected standard workflow and is configured using the specification 550. The invention makes it possible to generate processing tools quickly and efficiently and to integrate legacy systems on the logical and not just the data technology level.

0160Reference symbol list

0161<img file="WO2004046832A2_D0001.tif" /><img file="WO2004046832A2_D0002.tif" />