Browse Prior Art Database

System and Method to generalise optimised unit balancing Disclosure Number: IPCOM000016363D
Original Publication Date: 2002-Nov-14
Included in the Prior Art Database: 2003-Jun-21
Document File: 4 page(s) / 70K

Publishing Venue



Subject of Publication

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 4

System and Method to generalise optimised unit balancing

Subject of Publication

    Disclosed is a solution describing a generalized system, which is able to do an optimized balancing of "units" reported from different systems in different environments. It is located in between those e-business application systems and works as a controlling connection which allows the user to monitor, analyze and modify the relevant data records.

    In today's systems, levelling is only possible within homogenous enterprise systems (e.g. ERP warehouse), not in B2B environments, where business integration is provided by e.g. message hubs using a hub and spoke architecture.

Summary of the Solution

    The proposed solution is able to control and monitor any kind of data streams from different e-business applications who's in- and outputs have to be managed.

    The method supports balancing of defined value-fields, which were extracted from the XML messages provided by the e-business applications.

    A XML language must be defined, that identifies unit data in messages and provides this information to the balancing component of the system. A dynamically extendable list of supported messages must be kept in some persistent storage media. Balancing rules that define the business logic, must be configured according to the supported messages types and systems. These rules also have to be accessable and storable in a persistent way.

    The monitoring of such calculations provides important leveling information for business process management. The complete process of transforming the message and balancing is shown in the next figure:


Page 2 of 4

Message Transformation Process

Original Message

Type identification

List of supported types of messages

Relevant Data for this type

Balancing rules

Selection of relevant data for this type

create Meta Data Message

add Message to Message Pool

Recalculation of balance in pool

 e.g. Siebel Orderline must match SCM Warehouse

1. From the incoming message the type is identified and checked, if this type is supported. The system uses a list of supported types for this check.
2. In the next step the relevant data for the balancing is retrieved from the message. The information which information is relevant for this type is also stored persistent.
3. Then the enriched message is created.
4. Then the message is added to the messages that are already in the system's pool.
5. This triggers a recalculation of the balance of messages in the pool. The corresponding rules (which message has to be related to which message and what...