Computer system for business applications with alert notification

Field of the Invention

The present invention generally relates to data processing and, more particularly, relates to business application computer systems, programs, and methods that use alert messages.

Background of the Invention

Distributed computer networks that execute business applications support business organizations. Situations that are critical and important for the organization can occur at any time inside or outside the organization. Often, the situations are unexpected. The applications generate alerts to inform one or more users about the situation, for example: A customer relation management (CRM) application reports that a key customer terminates a contract. A production planning application reports delivery problems for an important order. A business analysis application detects a decline in revenue. A computer system monitor points out insufficiency of resources and informs about an expected memory overflow.

For alert systems, the following references are useful: United States Patents 6,185,603 to Henderson et al, 6,157,941 to Verkler et al., 5,748,884 to Laundry, 5,786,755 to Cicchino et al., 5,754,111 to Garcia, 5,548,753 to Linstead et al.

Further: GEISSBÜHLER A ET AL: "Design of a general clinical notification system based on the publish-subscribe paradigm" 1997 Amia Annual Fall Symposium. A Conference Of The American Medical Informatics Association. Proceedings, Proceedings Of 1997 Amia Annual Fall Symposium The Emergence Of Internetable Health Care Systems That Really Work, Nashville, TN, USA, 25-29 O, 25 - 29 October 1997, pages 126-130, XP002179981 1997, Philadelphia, PA, USA, Hanley & Belfus, USA.

Further: J. BREED ET AL.: "The Spacecraft Emergency Response System (SERS) For Autonomous Mission Operations" 3RD INTERNATIONAL SYMPOSIUM ON REDUCING THE COST OF SPACECRAFT GROUND SYSTEMS AND OPERATIONS, [Online] March 1999 (1999-03), pages 1-8.

Geissbuhler et al. discusses a publish-subscribe paradigm as a mechanism providing a framework for the exchange of data between independent applications in an event-driven manner. The paradigm is used in the context of a clinical notification system. Escalation is incorporated.

Landry as well as Breed et al. discuss event-based notification systems arranged to support escalation procedures.

Business applications can be configured to provide electronic notifications to a single recipient or to a group of recipients (cf. Linstead et al.). There is a technical problem relating to the configuration of the business application notification system to select a specific target group that receives alert notifications from a particular business application.

Brief Description of the Drawings

<ul id="ul0001" list-style="none"><li>FIG. 1 illustrates a simplified block diagram of a computer network system according to the present invention, the system having a central computer, peripheral computers, and communication devices;</li><li>FIG. 2 illustrates a simplified block diagram of the computer network system of FIG. 1 with further details of the central computer, the peripheral computers, and the communication devices;</li><li>FIG. 3 illustrates the operation of the system of FIGS. 1-2 according to a preferred implementation of the present invention as a method in a simplified time and flow-chart diagram;</li><li>FIG. 4 illustrates a display of a communication device with a notification message issued by the central computer;</li><li>FIG. 5 illustrates a display of a further communication device with a further notification message issued by the central computer;</li><li>FIG. 6 illustrates assignment tables for providing a message distribution list according to the present invention; and</li><li>FIG. 7 illustrates the message distribution list.</li></ul>

Detailed Description

FIG. 1 illustrates a simplified block diagram of exemplary computer system 999 having a plurality of computers 900, 901, 902 (or even more).

Computer 900 can communicate with computers 901 and 902 over network 990. Computer 900 has processor 910, memory 920, bus 930, and, optionally, input device 940 and output device 950 (I/O devices, user interface 960). As illustrated, the invention is implemented by computer program product 100 (CPP), carrier 970 and signal 980.

In respect to computer 900, computer 901/902 is sometimes referred to as "remote computer", computer 901/902 is, for example, a server, a peer device or other common network node, and typically has many or all of the elements described relative to computer 900.

Computer 900 is, for example, a conventional personal computer (PC), a desktop device or a hand-held device, a multiprocessor computer, a pen computer, a microprocessor-based or programmable consumer electronics device, a minicomputer, a mainframe computer, a personal mobile computing device, a mobile phone, a portable or stationary personal computer, a palmtop computer or the like.

Processor 910 is, for example, a central processing unit (CPU), a micro-controller unit (MCU), digital signal processor (DSP), or the like.

Memory 920 is elements that temporarily or permanently store data and instructions. Although memory 920 is illustrated as part of computer 900, memory can also be implemented in network 990, in computers 901/902 and in processor 910 itself (e.g., cache, register), or elsewhere. Memory 920 can be a read only memory (ROM), a random access memory (RAM), or a memory with other access options. Memory 920 is physically implemented by computer-readable media, for example: (a) magnetic media, like a hard disk, a floppy disk, or other magnetic disk, a tape, a cassette tape; (b) optical media, like optical disk (CD-ROM, digital versatile disk - DVD); (c) semiconductor media, like DRAM, SRAM, EPROM, EEPROM, memory stick.

Optionally, memory 920 is distributed. Portions of memory 920 can be removable or non-removable. For reading from media and for writing in media, computer 900 uses well-known devices, for example, disk drives, or tape drives.

Memory 920 stores modules such as, for example, a basic input output system (BIOS), an operating system (OS), a program library, a compiler, an interpreter, and a text- processing tool. Modules are commercially available and can be installed on computer 900. For simplicity, these modules are not illustrated.

CPP 100 has program instructions and - optionally-data that cause processor 910 to execute method steps of the present invention. In other words, CPP 100 can control the operation of computer 900 and its interaction in network system 999 so that is operates to perform in accordance with the invention. For example and without the intention to be limiting, CPP 100 can be available as source code in any programming language, and as object code ("binary code") in a compiled form.

Although CPP 100 is illustrated as being stored in memory 920, CPP 100 can be located elsewhere. CPP 100 can also be embodied in carrier 970.

Carrier 970 is illustrated outside computer 900. For communicating CPP 100 to computer 900, carrier 970 is conveniently inserted into input device 940. Carrier 970 is implemented as any computer readable medium, such as a medium largely explained above (cf. memory 920). Generally, carrier 970 is an article of manufacture having a computer readable medium with computer readable program code to cause the computer to perform methods of the present invention. Further, signal 980 can also embody computer program product 100.

Having described CPP 100, carrier 970, and signal 980 in connection with computer 900 is convenient. Optionally, further carriers and further signals embody computer program products (CPP) to be executed by further processors in computers 901 and 902.

Input device 940 provides data and instructions for processing by computer 900. Device 940 can be a keyboard, a pointing device (e.g., mouse, trackball, cursor direction keys), microphone, joystick, game pad, scanner, or disc drive. Although the examples are devices with human interaction, device 940 can also be a device without human interaction, for example, a wireless receiver (e.g., with satellite dish or terrestrial antenna), a sensor (e.g., a thermometer), a counter (e.g., a goods counter in a factory). Input device 940 can serve to read carrier 970.

Output device 950 presents instructions and data that have been processed. For example, this can be a monitor or a display, (cathode ray tube (CRT), flat panel display, liquid crystal display (LCD), speaker, printer, plotter, vibration alert device. Output device 950 can communicate with the user, but it can also communicate with further computers.

Input device 940 and output device 950 can be combined to a single device. Any device 940 and 950 can be provided optional.

Bus 930 and network 990 provide logical and physical connections by conveying instruction and data signals. While connections inside computer 900 are conveniently referred to as "bus 930", connections between computers 900-902 are referred to as "network 990". Optionally, network 990 includes gateways which are computers that specialize in data transmission and protocol conversion.

Devices 940 and 950 are coupled to computer 900 by bus 930 (as illustrated) or by network 990 (optional). While the signals inside computer 900 are mostly electrical signals, the signals in network are electrical, electromagnetic, optical or wireless (radio) signals.

Networks are commonplace in offices, enterprise-wide computer networks, intranets and the Internet (e.g., world wide web). Network 990 can be a wired or a wireless network. To name a few network implementations, network 990 can be, for example, a local area network (LAN), a wide area network (WAN), a public switched telephone network (PSTN); a Integrated Services Digital Network (ISDN), an infra-red (IR) link, a radio link, like Universal Mobile Telecommunications System (UMTS), Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), or satellite link.

A variety of transmission protocols, data formats and conventions is known, for example, as transmission control protocol/internet protocol (TCP/IP), hypertext transfer protocol (HTTP), secure HTTP, wireless application protocol (WAP), unique resource locator (URL), a unique resource identifier (URI), hypertext markup language (HTML), extensible markup language (XML), extensible hypertext markup language (XHTML), wireless markup language (WML), Standard Generalized Markup Language (SGML).

Interfaces coupled between the elements are also well known in the art. For simplicity, interfaces are not illustrated. An interface can be, for example, a serial port interface, a parallel port interface, a game port, a universal serial bus (USB) interface, an internal or external modem, a video adapter, or a sound card.

Computer and program are closely related. As used hereinafter, phrases, such as "the computer provides" and "the program provides", are convenient abbreviation to express actions by a computer that is controlled by a program.

FIG. 2 illustrates a simplified block diagram of the computer network system of FIG. 1 with details of the central computer, the peripheral computers, and the communication devices.

Computer system 999 of the present invention has central computer 900 and at least one peripheral computer 901/902. Communication devices 903-906 are also computers. As explained in FIG. 1, computers 90n are coupled via network 990. In FIG 2, messages and their preferred way in network 990 are illustrates by boxes and arrows. The use of singular language and of the forward slash "/" to describe elements like "computer" stands for "at least one" but indicates that in a preferred embodiment multiple elements are used.

Peripheral computer 901/902 executes at least one business application (BA) 201/202. As used herein, the term "application" stands for an application computer program. Peripheral computer 901/902 further issues alert message 211/212 ("ALERT") when a current value of a predetermined variable in business application 201/202 is in a predetermined relation to a reference value. Central computer 900 receives alert message 211/212 and, according to a predefined type of alert message 211/212 (e.g., business type), forwards notification message 301 to communication devices 903, 904 and 905 that present a representation (cf. FIG. 4, 301-1) of notification message 301 to a predefined group of multiple original users (e.g., users 1, 2, 3, "GROUP").

Preferably, computer system 999 with central computer 900, after having forwarded notification message 301, issues further notification message 321 (cf. FIG. 5) to a further user (e.g., user 4) outside the group in the event that during a predetermined time period (cf. FIG. 3, T) no user of the group has confirmed reception of notification message 301 (case (2)).

Original and further users are listed in message distribution list 140 (illustrated in computer 900). The inclusion of users to list 140 (or exclusion) according to the present invention is discussed below in connection with tables 110, 120, and 130 and FIG. 6.

Central computer 900 is conveniently implemented as workplace application server 900' by that the users of the group interact with applications 201/202 (running on peripheral computer 901/902). I/O devices of computers 901 and 902 are shown in FIG. 1 but are omitted in FIG. 2 for simplicity.

In computer 901/902, the predefined relation between current and reference values is detected, preferably, by comparing absolute values, so that the relation is a "larger than" or "smaller than" relation. It is also possible to monitor the current values over a time period to detect either an increase or a decrease that is larger (or smaller) than a reference increase or a reference decrease, respectively.

In the example of FIG. 3, computer 901/902 monitors the "revenue" as the predetermined variable in business application 201/202. Computer 901/902 issues alert message 211/212 when the "actual revenue" (i.e., current value) is smaller than or equal to critical revenue (i.e., reference value). Hence, the notification message has "low revenue" or similar content, (cf. FIG. 4, 301-1).

Issuing further notification message 321 to a further user is, preferably, provided by forwarding further notification message 321 to further communication device 906. Device 906 presents a further representation (cf. FIG. 5) of notification message 321 to the further user. Although the present invention is conveniently explained with dedicated communication devices for each user, the present invention can also be implemented with a single communication device, such as a large signboard visible for all users.

When instructed by the user, any communication device returns a receipt message to central computer 900 (case (1)). As illustrated in FIG. 2, device 905 is the confirming device that returns receipt message 315, devices 903 and 904 are non-confirming devices.

Communication device 903-906 is, for example, a fax machine ("facsimile"), a voice mail system, a selective call receiver ("pager"), a mobile phone with short message service (SMS) receiver, an audio device (e.g., a text-to-voice converter with speaker) or any other technical apparatus, such as a conventional personal computer (PC, e.g., with electronic mail, or pop-up function, or unified message function), that communicates to a user.

Preferably, communication device 903-906 presents the representations of notification 301/321 visually, for example, by displays 953, 954, 955, 956. For visualizing, devices 903-906 are conveniently implemented to run browser programs, such as HTML-browser in a PC or WAP-browser on a mobile phone. Optionally, device 903-906 can present also audible.

Conveniently, central computer 900 assigns a unique message identification (MID) number to notification message 301, and confirming communication device 905 returns this identification number as part of receipt message 315. In FIG. 2, the MID number is "241220011616" and is derived from data and time of alert (e.g., 24 December 2001, 16.16 hours). Preferably, confirming communication device 315 also returns user identification (e.g., the name of user 3: "K ...") . Convenient for tracing purposes, central computer 900 optionally stores the user identification.

Messages are, preferably, coded in extensible markup language (XML).

FIG. 3 illustrates the operation of system 999 in a preferred implementation of the present invention as method 400 in a simplified time and flow-chart diagram. Method steps 410-460 are explained in boxes. Dashed lines to the time axis indicate a preferred sequence of events; plain arrows indicate a preferred method flow. At the top of the figure, box 499 indicates that computer 901/902 optionally execute application 201/202 continuously. It is an advantage that feeding back alert information to peripheral computer 901/902 is not required.

Method 400 comprises issuing alert message 410, receiving alert message 420, forwarding notification message 430, presenting 440, as well as either returning receipt 450 in case (1) or issuing further notification message 460.

In step 410, peripheral computer 901/902 issues alert message 211/212 going to central computer 900. In step 420, central computer 900 receives alert message 211/212. In step 430, central computer 430 forwards notification message 301 to communication devices 903-905 (e.g., at 16.16 hours). In step 440, communication device 903-905 presents the representation of message 301 to the users 1, 2, 3 (details in FIG. 4). In step 450, communication device 905 returns receipt 450 (case (1)). In step 460 - in the absence of any receipt after T (e.g., one hour later at 17.16), central computer 900 issues further notification message 321, this time to user 4 (details in FIG. 5).

In other words, alert notification method 400 comprising that central computer 900 performs the following steps: <ul id="ul0002" list-style="none"><li>receiving 420 an alert message issued (cf. step 410) by peripheral computer 901/902 that executes business application 201/202 and that detects that a current value of a predetermined variable in the business application is in a predetermined relation to a reference value;</li><li>forwarding 430 notification message 301 to a plurality of communication devices 903, 904, 905 that present (cf. step 440) a representation of the notification to a group of users (e.g., users 1, 2, 3); and</li><li>issuing 460 a further notification message to a further user outside the group (e.g., user 4) in the event that during a predetermined time period no user of the group has confirmed reception of notification message 301 by receipt message 315.</li></ul>

In method 400, further steps 401, 402 and 403 allow the management of the message distribution list (cf. 140 in FIG. 7) by computer 900. Preferably, steps 401, 402 and 403 are executed prior to steps 410-460. This is convenient, but not essential, updating the list is possible. In deriving user group step 401, the group of users is derived from a role-to-user assignment and from an application-to-role assignment (details in FIG. 6), wherein the assignments define the business application that each user is allowed to access. In storing representations step 402, representations of the group of users are stored in the message distribution list (cf. 140 in FIG. 7). In receive subscription requests step 403, the list is modified.

FIG. 4 illustrates display 953/954/955 of communication device 903/904/905 with notification message 301 issued by central computer 900. The representation of message 301 is conveniently hyperlink 301-1 (e.g., "LOW REVENUE") to a full version of notification message 301. The text of hyperlink 301-1 can be composed by text portions (details below). Not illustrated in the figures, because hyper-linking is well known in the art, the full text is stored, for example, in memory 920 of computer 900 (cf. FIGS. 1-2) and could read, for example, as: "The actual revenue went below the critical revenue". Optionally, computer 900 (i.e. workplace application server 900') adds follow-up suggestion 301-2, such as, for example: "ORGANIZE A MEETING", taken, for example, from a look-up table.

Preferably, notification message 301 comprises predefined text portions 301-3 and 301-4. In the example, 301-4 "REVENUE" is fixed and points to the type of application 201/202 where the alert originates (e.g., application that evaluates revenue); and 301-3 "LOW" is alert specific and could also be "HIGH". The predefined message texts are assigned to the particular business application; in other words, for each type of business application, particular text portions are defined.

Optionally, the message text (short of full versions) has placeholder for business variables that are updated when computer 900 generates message 301. For example,

The natural language of the predefined message can automatically be selected according to user attributes, stored in computer 900 or communication devices 903-905. In the event that the description is translated into German, the text could read as "NIEDRIGES EINKOMMEN - MEETING ORGANISIEREN".

Using hyperlinks is convenient, for example, to shield unauthorized persons from the full information about the alert. Optionally, computer 900 forwards the full version of message to device 905 only after having confirmed the identity of user 3 as being authorized. Displaying the full version on the same device as the short version (the hyperlink) is convenient, but not necessary. The user reacting on the hyperlink can cause computer 900 to re-direct the full version to a different communication device.

Optionally, computer 900 forwards notification messages with short text and with full text to different communication devices. For example, computer 900 forwards short texts as SMS to a mobile phone and-simultaneously or on request by the user - computer 900 forwards full texts as electronic mail.

FIG. 5 illustrates display 956 of communication device 906 with further notification message 321 issued by central computer 900. Preferably, message 321 cites message 301 (with link 301-1 and suggestion 301-2 in FIG. 4). Message 321 has descriptive portion 321-1 to indicate that message 321 is a further notification. For example, portion 321-1 could read as: "Original recipients did not confirm".

The above explanation assumed that the group of users to be notified (e.g., original users 1, 2, 3, further user 4) is predetermined. It is possible that all users of system 999 (computers 901, 902, 903) are notified. But it is desired to keep the overall number of users in the message distribution list small. In other words, the list should comprise only these users for that alert information is relevant.

The distribution list can optionally distinguish between original and further users; but for convenience, the following explanation does not distinguish original and further users.

Computer 900 creates the distribution list after receiving alert message 211/212 (dynamic creation in real-time), or before (static creation). Details are explained in connection with FIG. 3, steps 401-403, and FIGS. 6-7. The present invention thereby takes advantage of existing user-to-role and role-to-application assignments. Computer 900 combines the existing assignments with the alert scheme described above.

Optionally, users are invited to subscribe or to unsubscribe to alert notifications. In combination with approach (2), the users can modify the distribution list (set as default list). An example is explained in connection with FIG. 7.

FIG. 6 illustrates assignment tables 110, 120, 130 for providing the message distribution list (140, cf. FIG. 3) of the present invention. FIG. 7 illustrates message distribution list 140 with more detail.

Workplace 900' stores assignment tables, preferably, in memory 920. For convenience of explanation, the tables are illustrated here as matrices, wherein a matrix element with a plus symbol stands for an existing assignment.

First assignment table 110 provides a role-to-user assignment. R roles (r=1...R) are selectively assigned to U users (u=1...U) . For example, USER 1 belongs to ROLES 1, 2, 3 and R; USER 2 belongs to ROLE 1, 2 and R, and so on.

Second assignment table 120 provides a business-application-to-role assignment. Business applications (BA) 20p (p=1...P, BA 201 and 201 cf. FIG. 2) are selectively assigned to R roles. For example, ROLE 1 belongs to application 201 and 202, 203 and 20P; ROLE 2 belongs to application 201, 203 and 20P, etc. Roles are, for example, Chief Financial Officer, Employee, Sales Representative, and Accountant.

Combining tables 110 and 120 creates distribution list 140 (cf. steps 401 and 402 in FIG. 3). For example, distribution list 140 for application 201 is obtained as comprising users in roles 1, 2 and R (table 120), these users are USER 1, 2, 3 and U. Likewise, distribution list 140 for application 202 is obtained as comprising users in roles 1, 3 and R (table 120); these users are USER 1 and USER 3.

It is further convenient to further limit the number of users in distribution list 140. Third assignment table 130 provides alert-type-to-role assignment. Inside a single application, alert types TYPE a (a=1...A) are selectively assigned to R roles. For example, application 201 might create an alert of technical nature, such as an expected memory overflow, that alert is notified to technicians; application 201 might also create an alert of a business nature, such as the revenue alert (cf. FIGS. 2, 4-5), that alert is notified to business persons. Alert types are sometimes referred to as "alert categories".

For convenience, the figures show alert types of BA 201 only. In the alternative, a similar list can be provided for an alert type-to-user assignment.

In other words, the predefined group of users is determined in distribution list 140 that is derived from a role-to-user assignment and from an application-to-role assignment, wherein the assignments (110, 120, 130) define the business application that each user is allowed to access.

As mentioned, users can be invited to subscribe or unsubscribe to alert notifications, cf. step 403 in FIG. 3. FIG. 7 further illustrates modified distribution list 140', in the example, user 3 has un-subscribed from being notified about alerts in application 201, und user 1 has un-subscribed from being notified about alerts in application 202. Lists 140 and 140' store representations of the group of users and receive (step 403) subscription requests to alert notification messages from the users of the group. Subscription requests can be a request to cancel an existing notification (as illustrated) or, can be a request to establish a new notification. In other words, subscription requests selectively add and remove representations of users from distribution list 140. Persons of skill in the art are able to use assignment tables 110 and 120 to let computer 900 selectively allow or reject such requests. In other words, the possibility of a user to request is related to the role.

References

<dl id="dl0001" compact="compact"><dt>1, 2, 3</dt><dd>users</dd><dt>140</dt><dd>distribution list / message distribution list</dd><dt>201/202</dt><dd>business application</dd><dt>211/212</dt><dd>alert message</dd><dt>301</dt><dd>notification message</dd><dt>301-1</dt><dd>hyperlink</dd><dt>301-2</dt><dd>follow-up suggestion</dd><dt>301-3, 301-4</dt><dd>predefined text portions</dd><dt>315</dt><dd>receipt message</dd><dt>321</dt><dd>further notification message</dd><dt>321-1</dt><dd>descriptive portion</dd><dt>4</dt><dd>further user</dd><dt>400</dt><dd>alert notification method</dd><dt>401</dt><dd>deriving</dd><dt>402</dt><dd>storing</dd><dt>403</dt><dd>receive</dd><dt>410</dt><dd>issued</dd><dt>420</dt><dd>receiving</dd><dt>430</dt><dd>forwarding</dd><dt>440</dt><dd>present</dd><dt>460</dt><dd>issue</dd><dt>900</dt><dd>central computer</dd><dt>900'</dt><dd>workplace application server</dd><dt>901</dt><dd>peripheral computer</dd><dt>903, 904, 905</dt><dd>communication devices</dd><dt>999</dt><dd>computer system</dd><dt>T</dt><dd>predetermined time period</dd></dl>