US20080091665A1 - Configurable Business Controls Task Notification - Google Patents
Configurable Business Controls Task Notification Download PDFInfo
- Publication number
- US20080091665A1 US20080091665A1 US11/948,586 US94858607A US2008091665A1 US 20080091665 A1 US20080091665 A1 US 20080091665A1 US 94858607 A US94858607 A US 94858607A US 2008091665 A1 US2008091665 A1 US 2008091665A1
- Authority
- US
- United States
- Prior art keywords
- event
- schedule
- database
- query
- databases
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06314—Calendaring for a resource
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
Definitions
- the present invention relates in general to data processing and in particular to improving efficiency of data access, distribution and modification within distributed databases containing diverse event notifications. Still more particularly, the present invention relates to a system, method and computer program product for generating, accessing, distributing and/or modifying events in multiple business control databases that contain event reminders.
- DCE Distributed Computing Environment
- LDAP Lightweight Directory Access Protocol
- NIS+ Network Information System
- a method for performing business control task notification comprises processing a combination of one or more databases and one or more user profiles to generate a schedule template and receive a request for a schedule.
- a computer program product compares attributes of the request for the schedule to a user profile and a schedule template to identify one or more events of the schedule template to be accessed from one or more of a plurality of distributed databases and forms a query to be sent to the one or more distributed databases.
- the query is sent to a particular database among the plurality of distributed databases.
- the computer program product receives a positive response to the query, indicating that the particular database contains a first event for the schedule, and the event.
- the schedule is created.
- the schedule is stored.
- One or more current events in the schedule requiring a notification are identified, and the notification is sent to a destination.
- FIG. 1 illustrates a distributed database in a network environment, in which preferred embodiments of the method, system and computer program product for performing business control task notification is implemented;
- FIG. 2 is a high-level logical flowchart of a process for checking a schedule and sending notices in performing business control task notification in accordance with a preferred embodiment of the present invention
- FIG. 3 is a high-level logical flowchart of a process for preparing a schedule in performing business control task notification in accordance with a preferred embodiment of the present invention
- FIG. 4 is a high-level logical flowchart of a process for querying schedule databases in performing business control task notification in accordance with a preferred embodiment of the present invention.
- FIG. 5 is a high-level logical flowchart of a process for preparing template data in performing business control task notification in accordance with a preferred embodiment of the present invention.
- the illustrated network environment includes a local or wide area network 100 , such as the Internet or another packetized digital network.
- An integrated control manager data processing system 102 an information technology schedule database 104 , an ISO schedule database 106 , a health and environment schedule database 108 , a first client 128 and a second client 130 are attached to network 100 , and communication is enabled through contact and routing information contained in database configuration 110 .
- Each of information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 contains business control schedule events stored in electronic records, representing processes wherein distributed employees and organizations must complete activities. Any employee or organization may be involved in the completion of activities reflected in business control schedules on one or more of information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 .
- Employees interact with the schedules created by integrated control manager data processing system 102 through first client 128 and second client 130 .
- Integrated control manager data processing system 102 performs functions related to access and distribution and of events stored in electronic records, located on information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 .
- Integrated control manager data processing system 102 uses data stored in database configuration 110 to communicate with information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 over network 100 .
- integrated control manager data processing system 102 For the purpose of simplifying discussion of the invention itself, many details of integrated control manager data processing system 102 , which details are well within that which is known to one of skill in the relevant data processing arts, have been omitted from the discussion of the present invention.
- the operations of integrated control manager data processing system 102 with respect to information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 may be implemented with conventional or later-developed hardware or software.
- integrated control manager data processing system 102 includes, but are not limited to access to and distribution of electronic records containing schedule events.
- integrated control manager data processing system 102 operates under instructions to assemble, based on the content of a template database 132 a user schedule 152 for a given user profile among user profiles 142 (e.g. first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148 ) containing a group of schedule events, such as a first event 112 , a second event 114 , a third event 116 , and a fourth event 118 .
- user profiles 142 e.g. first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148
- group of schedule events such as a first event 112 , a second event 114 , a third event 116 , and a fourth event 118 .
- integrated control manager data processing system 102 will have access to stored information, hereafter called assignments, sometimes internally stored in template database 132 and sometimes stored on database configuration 110 , relating to the location from which some events can be retrieved, but may have no such assignment information relative to the locations from which other events may be retrieved.
- assignments sometimes internally stored in template database 132 and sometimes stored on database configuration 110 , relating to the location from which some events can be retrieved, but may have no such assignment information relative to the locations from which other events may be retrieved.
- Fulfillment URLS 150 contains URLs that can be used to help users perform actions associated with specific events. Many of these events can be performed or confirmed by transmission of messages to one of information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 , such as client-to-database message 178 to ISO schedule database 106 and database-to-client message 180 from ISO schedule database 106 . Events from user schedule 152 are sent to first client 128 and second client 130 by notification engine 126 .
- Notification engine 126 is capable of receiving a schedule request 154 from a client, such as first client 128 and sending notification messages, such as notification message 156 to first client 128 and notification message 158 to second client 130 .
- notification engine 126 sends a query request 188 to query engine 190 .
- Query engine 190 sends a template request 192 to template database 132 and receives a template reply 194 in response.
- Query engine 190 also sends a profile request 196 to user profiles 142 and receives a profile reply 198 in response.
- Notification engine 126 can also send a notification message 158 in response to receiving a schedule alert 186 from master schedule database 176 .
- Template engine 138 can send a database request, such as database request 172 to health and environment database 108 and receive a database result transmission 174 . Template engine 138 also sends a user profile request 182 to template user profiles 142 and receives a profile result transmission 184 . Template engine 138 delivers current templates 136 as a template report 199 .
- Template database 132 contains data for determining what events to assemble for a user schedule 152 based on the content of a user profile (e.g., first user profile 140 ) and is generated by template engine 138 .
- Template database 132 contains current templates 136 and past template archive 134 .
- Past template archive 134 contains a record of past templates and schedules.
- First event 112 , second event 114 , third event 116 , and fourth event 118 are retrieved into user schedule 152 in master schedule database 176 by integrated control manager data processing system 102 through the sending of queries, which queries are based on current templates 136 , to information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 .
- queries which queries are based on current templates 136
- information technology schedule database 104 to information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 .
- FIG. 1 operates on the assumption that integrated control manager data processing system 102 will have access to information, stored in current templates 136 relating to the location among information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 at which first event 112 and third event 116 can be accessed.
- second event 114 and fourth event 118 the example illustrated with respect to FIG. 1 assumes that no location data is available to integrated control manager data processing system 102 that would be helpful in ascertaining the location of the events among information technology schedule database 104 , ISO schedule database 106 , and health and environment schedule database 108 of second event 114 and fourth event 118 .
- a client such as first client 128 can communicate directly with a database, such as ISO schedule database 106 , through messages, such as client-to-database message 178 and database-to-client message 180 .
- first query message 160 contains first query 120 , directed to information technology schedule database 104 , and includes a request for first event 112 , second event 114 and fourth event 118 .
- No request for third event 116 is included in first query 120 , because location data is available to integrated control manager data processing system 102 that indicates the presence of third event 116 on health and environment schedule database 108 .
- the response to first query 120 arrives at integrated control manager data processing system 102 in the form of first event message 162 , which contains first event 112 and data acknowledging the absence from information technology schedule database 104 of second event 114 and fourth event 118 .
- second query message 164 contains second query 122 , directed to ISO schedule database 106 , and includes a request for second event 114 and fourth event 118 .
- No request for third event 116 is included in second query 122 , because location data is available to integrated control manager data processing system 102 that indicates the presence of third event 116 on health and environment schedule database 108 .
- no request for first event 112 is included in second query 122 , because integrated control manager data processing system 102 received first event 112 in first event message 162 .
- the response to second query 122 arrives at integrated control manager data processing system 102 in the form of second event message 166 , which contains second event 114 and data acknowledging the absence from ISO schedule database 106 of fourth event 118 .
- third query message 168 contains third query 124 , directed to health and environment schedule database 108 , and includes a request for third event 116 and fourth event 118 .
- No request for first event 112 or second event 114 is included in third query 124 , because integrated control manager data processing system 102 received first event 112 in first event message 162 and received second event 114 in second event message 166 .
- the response to third query 124 arrives at integrated control manager data processing system 102 in the form of third event message 170 , which contains third event 116 and data acknowledging the absence from health and environment schedule database 108 of fourth event 118 .
- FIG. 2 a high-level logical flowchart of a process for checking a schedule and sending notices and performing business control task notification in accordance with the preferred embodiment of the present invention is depicted.
- the process starts at step 200 , which will typically correspond to activation of master schedule database 176 on integrated business control manager 102 .
- the process next moves to step 202 .
- master schedule database 176 verifies whether any schedules exist, which have not been checked recently for near-term event dates. If no such unchecked schedules exist, then the process ends at step 204 . If unchecked schedules exist, then the process next moves to step 206 , which depicts master schedule database 176 loading user schedule 152 .
- the process then proceeds to step 208 .
- master schedule database 176 on integrated business control manager 102 examines user schedule 152 for events with near-term dates. This examination for near term dates is accomplished by reviewing the required performance dates in first event 112 , second event 114 , third event 116 and fourth event 118 . If events with near term dates do not exist, then the process ends at step 204 . If events with near term dates do exist, then the process next moves to step 210 .
- master schedule database 176 sends a schedule alert 186 , containing any events with near-term required performance dates to notification engine 126 .
- the process next moves to step 212 , which depicts notification engine 126 processing schedule alert 186 by sending a notification 158 to second client 130 .
- the process then returns to step 202 , which is described above.
- step 300 a high-level logical flowchart of a process for preparing a schedule and performing business control task notification in accordance with a preferred embodiment of the present invention is illustrated.
- the process starts at step 300 , which corresponds to activation of notification engine 126 .
- the process then moves to step 302 .
- notification engine 126 receives a schedule request 154 from first client 128 .
- step 304 depicts integrated business control manager 102 comparing a user profile, such as fourth user profile 148 to data from current templates 136 in compliance with schedule request 154 . This is accomplished as notification engine 126 sends a query request 188 to query engine 190 .
- Query engine 190 then sends a profile request 196 to user profiles 142 and receives a user profile such as fourth user profile 148 in a profile reply 198 .
- Query engine 190 then sends a template request 192 to template database 132 and the template database replies by sending an appropriate subset of current templates 136 in a template reply 194 to query engine 190 .
- step 306 query engine 190 queries databases for attributes called for in the template from among current templates 136 received in template reply 194 , as is detailed below with respect to FIG. 4 .
- step 308 master schedule database 176 prepares, delivers, and stores a user schedule 152 . Delivery of a schedule can be accomplished by sending a schedule alert 186 to notification engine 156 .
- step 310 ends at step 310 .
- FIG. 4 there is depicted a high-level logical flowchart of a process for managing database records with events located in multiple registries in accordance with a preferred embodiment of the present invention. While the process of FIG. 4 has been illustrated in a simplified embodiment as a logical flowchart, wherein single operations are explained sequentially for the purpose of explanatory clarity, one skilled in the art will quickly recognize that the process depicted in FIG. 4 can be separated into a group of interacting processes, operating as modules or program objects in parallel processes and interacting with one another.
- assignment module 454 comprises steps 404 - 412 .
- Assignment module 454 performs steps related to identifying whether, for each requested event, a known schedule database location exists, such as information technology schedule database 104 as a location for first event 112 .
- the steps of assignment module 454 include analysis by integrated control manager data processing system 102 of current templates 136 in template database 132 as to which schedule database can appropriately provide a given event, and the assignment of the event to a list, which is then used by integrated control manager data processing system 102 in query preparation module 456 .
- Query preparation module 456 comprises steps 414 - 430 and step 450 .
- Query preparation module 456 prepares queries for integrated control manager data processing system 102 to send to databases across network 100 .
- the third module, query communication module 458 includes steps 432 - 440 and sends queries to databases across network 100 .
- step 400 depicts integrated control manager data processing system 102 beginning the process of creating a schedule by accessing, distributing and modifying events in databases that are distributed across multiple data processing systems connected to a network.
- Step 400 typically involves activation of a query process on integrated control manager data processing system 102 , and activation may come from a user or an automated query.
- step 402 illustrates integrated control manager data processing system 102 receiving schedule request 154 .
- Schedule request 154 is received at notification engine 126 .
- integrated control manager data processing system 102 processes a query for four events of one or more records.
- the requested events are first event 112 , second event 114 , third event 116 , and fourth event 118 .
- Step 404 depicts integrated control manager data processing system 102 determining whether any requested events (e.g., first event 112 , second event 114 , third event 116 , and fourth event 118 ) remain in an ‘unassigned’ condition.
- any requested events e.g., first event 112 , second event 114 , third event 116 , and fourth event 118 .
- an unassigned condition exists whenever, with respect to one of first event 112 , second event 114 , third event 116 , and fourth event 118 , integrated control manager data processing system 102 does not possess information as to the location among information technology schedule database 104 , ISO schedule database 106 and health and environment schedule database 108 on which the needed event is stored. If the location of all desired events is known, then the process of FIG. 4 moves to step 414 in query formation module 456 , which is described in detail below.
- step 406 illustrates integrated control manager data processing system 102 queuing a next event for identification of its location.
- step 408 illustrates integrated control manager data processing system 102 determining whether a database from among those to which integrated control manager data processing system 102 can send queries (e.g., information technology schedule database 104 , ISO schedule database 106 and health and environment schedule database 108 ) is assigned to provide the event in question.
- queries e.g., information technology schedule database 104 , ISO schedule database 106 and health and environment schedule database 108
- the determination as to whether a database among those to which integrated control manager data processing system 102 can send queries is assigned to provide the event in question can be made from data received in a request to access events in step 402 , from data stored on integrated control manager data processing system 102 or from data stored by other sources.
- step 410 depicts integrated control manager data processing system 102 assigning the event in question to a location list for the specified database.
- integrated control manager data processing system 102 assigns first event 112 to the list of events to be queried from information technology schedule database 104 .
- third event 116 on health and environment schedule database 108 is known, integrated control manager data processing system 102 assigns third event 116 to the list of events to be queried from health and environment schedule database 108 .
- step 408 if no location data is available for first event 112 , then the process proceeds to step 412 , which depicts integrated control manager data processing system 102 assigning an event to the list of events for which no database is known.
- step 412 depicts integrated control manager data processing system 102 assigning an event to the list of events for which no database is known.
- database locations are assigned and known for first event 112 and third event 116 , which would be assigned to query lists for their respective information technology schedule database 104 and health and environment schedule database 108 .
- no location data is available for second event 114 and fourth event 118 .
- Second event 114 and fourth event 118 would be assigned to the query list for those events for which no database location data is known.
- Step 404 If, in step 404 , no events remain which have not been assigned to the lists for a particular database or to the list for which no database location is known, the process then enters query preparation module 456 as the process moves to step 414 .
- Step 414 illustrates integrated control manager data processing system 102 adding any known unused database location data to the list of databases which will be queried with respect to events for which no location database is known. This data will typically be available from database configuration 110 .
- step 416 depicts integrated control manager data processing system 102 determining whether any unreceived events remain. If no unreceived events remain, then the process leaves query preparation module 456 and enters return module 460 as the process moves to step 442 , which will be described in detail below.
- step 418 illustrates integrated control manager data processing system 102 determining whether it has exhausted all of the possible databases that are available to receive queries for any unreceived events.
- the databases which are available to receive queries for unreceived events, will include those databases referenced in information stored on integrated control manager data processing system 102 , those databases referenced in information received from database configuration 110 , and those databases referenced in any information received in response to queries to previously queried databases. An individual database is exhausted after a query has been sent to it.
- step 420 depicts integrated control manager data processing system 102 queuing the next event for possible addition to the query, which is being prepared for transmission to the current database selected in step 420 .
- step 422 depicts integrated control manager data processing system 102 determining whether any of the desired events remain untried for the current database selected in step 420 . This step involves determining whether each of the unreceived events has been tried for the current database selected in step 440 .
- step 422 If, in step 422 , untried events remain, then the process of the preferred embodiment will move to step 424 , which illustrates the integrated control manager data processing system 102 designating the next event for possible addition to the query being sent the current database selected in step 420 . The process then proceeds to step 426 , which depicts integrated control manager data processing system 102 determining whether the database specified in step 424 to receive the query currently being formed is the desired database that is assigned as containing the event under consideration.
- integrated control manager data processing system 102 To determine if the database specified in step 424 to receive the query currently being formed in query formation module 456 is the desired database that is assigned as containing the event under consideration, integrated control manager data processing system 102 refers to the list prepared in assignment module 454 for the current database selected in step 420 , and ascertains whether the current event contained is identified on the list generated in assignment module 454 . If the specified database being tried is the desired database, which is known to contain the required event, then the process moves to step 428 , which depicts integrated control manager data processing system adding the current event to the query for the current database.
- step 426 the specified database is not the desired database
- step 430 illustrates integrated control manager data processing system determining whether any database is specified with respect to the event under consideration.
- Integrated control manager data processing system 102 determines that no database is specified for an event by searching for the current event in the list prepared by assignment module 454 , containing those events for which no database was specified. If no database is specified for the event under consideration, the process moves to step 428 , in which integrated control manager data processing system 102 adds the event under consideration, for which no location data is available, to the query being prepared for the current database selected in step 420 .
- step 422 If a specified database is available but the current database is not the specified database, then the process returns to step 422 , which is discussed above. Returning to step 422 , if no events remain untried for the current database, then the process moves to step 432 , which depicts sending a query to the current database.
- First query 120 is a query for first event 112 , fourth event 118 , and second event 114 .
- Second query 122 is a query requesting second event 114 and fourth event 118 .
- Third query 124 requests third event 116 and fourth event 118 .
- step 434 illustrates client data processing 102 receiving events.
- sending query 120 as a first query message 160 would result in the return of event 112 in first event message 162 .
- sending second query 122 as second query message 164 would result in receipt of second event 114 as second event message 166
- sending third query 124 as third query message 168 would result in receipt of third event 116 as third event message 170 .
- step 436 integrated control manager data processing system 102 stores location data for the events that it has received in step 434 .
- step 438 depicts integrated control manager data processing system performing operations on or with the received events.
- step 440 depicts the recording on un-received events, and is then followed by a return to step 416 , which is discussed above.
- step 442 depicts integrated control manager data processing system 102 determining whether a return of any events is required. If the return of events is required, the process of FIG. 4 then proceeds to step 444 , which depicts modification of events which require modification. The process then moves to step 446 , which depicts replacing the modified events in their original databases by reference to the stored location information. The process then ends at step 448 . If, in step 442 , integrated control manager data processing system 102 determines that no events require modification, then the process of FIG. 4 next moves to step 448 , where it ends.
- step 418 if, in step 418 integrated control manager data processing system 102 determines that all of its available databases have been queried and there are events that have not been found in any database, then the process moves to step 450 , which illustrates integrated control manager data processing system reporting failures and ends at step 448 .
- FIG. 5 a high-level logical flowchart of a process for preparing template data and performing business control task notification in accordance with the preferred embodiment of the present invention as depicted.
- the process starts at step 500 , which corresponds to activation of template engine 138 .
- the process next proceeds to step 502 .
- Step 502 depicts template engine 138 requesting a database and a user profile.
- Template engine 138 requests a user profile by sending profile request 182 to user profiles 142 .
- Template engine 138 requests a database by sending database request 172 to a database such as health and environmental schedule database 108 .
- the process then moves to step 504 which depicts template engine receiving a database and a user profile. As depicted in the example illustrated in FIG.
- template engine 138 receives a profile result transmission 184 containing first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148 .
- Template engine 138 also receives health and environment schedule database as part of database result transmission 174 .
- the process then moves to step 506 .
- Step 506 depicts template engine 138 determining whether it has exhausted available common events from first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148 . If common events from first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148 have been exhausted, then the process proceeds to step 507 , which depicts template engine generating a report.
- a template report 199 is sent to template database 132 , and the process then ends at step 508 .
- step 506 If at step 506 , common events from first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148 have not been exhausted, then the process proceeds to step 510 , which depicts template engine 138 identifying and processing a next common event from among two or more of first user profile 140 , second user profile 144 , third user profile 146 and fourth user profile 148 .
- step 512 depicts template engine 138 determining whether the common event processed in step 510 correlates to a common trait. If the common event correlates to no discernable common trait, then the process proceeds to step 514 , which depicts template engine 138 flagging the common event for later processing. If the common event correlates to a common trait in step 512 , then the process next moves to step 516 .
- Step 516 depicts template engine 138 adding the common event and common trait to template report 199 .
- the present invention provides a system, method and computer program product for accessing and distributing events in business control database that are distributed across multiple data processing systems connected to a network.
- the present invention provides facilities for sending a queries from a local integrated control manager data processing system to a remote database, wherein that query is composed of requests for events known to be stored on the database and events whose location is unknown.
- the present invention provides facilities for creating schedules and for notifying clients.
- the present invention improves interaction between clients and business control databases by providing an orderly and methodical system for dealing with events distributed across multiple databases.
Abstract
A method for performing business control task notification is proposed. The method comprises processing a combination of one or more databases and one or more user profiles to generate a schedule template and receive a request for a schedule. A computer program product compares attributes of the request for the schedule to a user profile and a schedule template to identify one or more events of the schedule template to be accessed from one or more of a plurality of distributed databases and forms a query to be sent to the one or more distributed databases. The query is sent to a particular database among the plurality of distributed databases. The computer program product receives a positive response to the query, indicating that the particular database contains a first event for the schedule, and the event. In response to receiving the event, the schedule is created. The schedule is stored. One or more current events in the schedule requiring a notification are identified, and the notification is sent to a destination.
Description
- The present application is a continuation of U.S. patent application Ser. No. 11/043,670 (Atty. Docket No. END920040158US1), filed on Jan. 25, 2005, and entitled, “Configurable Business Controls Task Notification,” which is incorporated herein by reference.
- 1. Technical Field
- The present invention relates in general to data processing and in particular to improving efficiency of data access, distribution and modification within distributed databases containing diverse event notifications. Still more particularly, the present invention relates to a system, method and computer program product for generating, accessing, distributing and/or modifying events in multiple business control databases that contain event reminders.
- 2. Description of the Related Art
- The profusion of business control schedules, representing processes wherein distributed employees and organizations must complete activities that define the operational compliance of a business with defined standards, has created an entangled and incomprehensible web of activities that must be performed by employees and organizations. Application of these processes runs from governmental compliance such as environmental, health, safety, and accounting regulation to business certifications such as ISO9000 and internal procedures such as information technology and security. In many industrial organizations, employees find themselves bombarded with multiple sets of business controls compliance tasks, coming from multiple sources, with no integrated system for delivery or prioritization.
- Conventionally, distributed database systems define and store records, such as user IDs, user groups and other information in a variety of different locations and storage systems related to specific functions. The existing standards-based information storage and retrieval methods (e.g. Distributed Computing Environment (DCE), Lightweight Directory Access Protocol (LDAP), Network Information System (NIS+) and others) were designed to serve disparate purposes.
- As can be foreseen from the description of each of the task types listed above, the emphasis on compliance with individual processes has encourage conflicting demands on employees. Further, because of the different purposes driving the designs of the business control procedures listed above, each procedure set has tended to reside within its own administrative tools, requiring employees to learn those tools.
- There is presently no adequate mechanism for managing events in multiple business control databases. The increasing need for employees to comply with multiple such business control systems has created an unfulfilled and increasing need for unified management of business control tasks, particularly in large organizations. What is needed is a way to enable integrated interaction with business control schedule events, which are distributed across several storage locations and tied to different tasks, for consolidated management of business control tasks.
- A method for performing business control task notification is proposed. The method comprises processing a combination of one or more databases and one or more user profiles to generate a schedule template and receive a request for a schedule. A computer program product compares attributes of the request for the schedule to a user profile and a schedule template to identify one or more events of the schedule template to be accessed from one or more of a plurality of distributed databases and forms a query to be sent to the one or more distributed databases. The query is sent to a particular database among the plurality of distributed databases. The computer program product receives a positive response to the query, indicating that the particular database contains a first event for the schedule, and the event. In response to receiving the event, the schedule is created. The schedule is stored. One or more current events in the schedule requiring a notification are identified, and the notification is sent to a destination.
- The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
-
FIG. 1 illustrates a distributed database in a network environment, in which preferred embodiments of the method, system and computer program product for performing business control task notification is implemented; -
FIG. 2 is a high-level logical flowchart of a process for checking a schedule and sending notices in performing business control task notification in accordance with a preferred embodiment of the present invention; -
FIG. 3 is a high-level logical flowchart of a process for preparing a schedule in performing business control task notification in accordance with a preferred embodiment of the present invention; -
FIG. 4 is a high-level logical flowchart of a process for querying schedule databases in performing business control task notification in accordance with a preferred embodiment of the present invention; and -
FIG. 5 is a high-level logical flowchart of a process for preparing template data in performing business control task notification in accordance with a preferred embodiment of the present invention. - With reference now to the figures and in particular with reference to
FIG. 1 , there is depicted an exemplary network environment with which the present invention may be advantageously utilized. The illustrated network environment includes a local orwide area network 100, such as the Internet or another packetized digital network. An integrated control managerdata processing system 102, an informationtechnology schedule database 104, an ISOschedule database 106, a health andenvironment schedule database 108, afirst client 128 and asecond client 130 are attached tonetwork 100, and communication is enabled through contact and routing information contained indatabase configuration 110. - Each of information
technology schedule database 104, ISOschedule database 106, and health andenvironment schedule database 108 contains business control schedule events stored in electronic records, representing processes wherein distributed employees and organizations must complete activities. Any employee or organization may be involved in the completion of activities reflected in business control schedules on one or more of informationtechnology schedule database 104, ISOschedule database 106, and health andenvironment schedule database 108. Employees interact with the schedules created by integrated control managerdata processing system 102 throughfirst client 128 andsecond client 130. Integrated control managerdata processing system 102 performs functions related to access and distribution and of events stored in electronic records, located on informationtechnology schedule database 104, ISOschedule database 106, and health andenvironment schedule database 108. Integrated control managerdata processing system 102 uses data stored indatabase configuration 110 to communicate with informationtechnology schedule database 104, ISOschedule database 106, and health andenvironment schedule database 108 overnetwork 100. - For the purpose of simplifying discussion of the invention itself, many details of integrated control manager
data processing system 102, which details are well within that which is known to one of skill in the relevant data processing arts, have been omitted from the discussion of the present invention. The operations of integrated control managerdata processing system 102 with respect to informationtechnology schedule database 104, ISOschedule database 106, and health andenvironment schedule database 108 may be implemented with conventional or later-developed hardware or software. - The functions of integrated control manager
data processing system 102 include, but are not limited to access to and distribution of electronic records containing schedule events. In the example shown with respect to integrated control managerdata processing system 102, integrated control managerdata processing system 102 operates under instructions to assemble, based on the content of a template database 132 a user schedule 152 for a given user profile among user profiles 142 (e.g. first user profile 140, second user profile 144, third user profile 146 and fourth user profile 148) containing a group of schedule events, such as afirst event 112, asecond event 114, athird event 116, and afourth event 118. For some offirst event 112,second event 114,third event 116, andfourth event 118, integrated control managerdata processing system 102 will have access to stored information, hereafter called assignments, sometimes internally stored intemplate database 132 and sometimes stored ondatabase configuration 110, relating to the location from which some events can be retrieved, but may have no such assignment information relative to the locations from which other events may be retrieved. - User schedule 142 is contained in
master schedule database 176 along withfulfillment URLs 150.Fulfillment URLS 150 contains URLs that can be used to help users perform actions associated with specific events. Many of these events can be performed or confirmed by transmission of messages to one of informationtechnology schedule database 104, ISOschedule database 106, and health andenvironment schedule database 108, such as client-to-database message 178 to ISOschedule database 106 and database-to-client message 180 from ISOschedule database 106. Events from user schedule 152 are sent tofirst client 128 andsecond client 130 bynotification engine 126.Notification engine 126 is capable of receiving aschedule request 154 from a client, such asfirst client 128 and sending notification messages, such asnotification message 156 tofirst client 128 andnotification message 158 tosecond client 130. Whennotification engine 126 receives aschedule request 154 fromfirst client 128,notification engine 126 sends aquery request 188 toquery engine 190.Query engine 190 sends atemplate request 192 totemplate database 132 and receives atemplate reply 194 in response.Query engine 190 also sends aprofile request 196 to user profiles 142 and receives aprofile reply 198 in response.Notification engine 126 can also send anotification message 158 in response to receiving aschedule alert 186 frommaster schedule database 176. -
Template engine 138 can send a database request, such asdatabase request 172 to health andenvironment database 108 and receive adatabase result transmission 174.Template engine 138 also sends auser profile request 182 to template user profiles 142 and receives aprofile result transmission 184.Template engine 138 deliverscurrent templates 136 as atemplate report 199. -
Template database 132 contains data for determining what events to assemble for a user schedule 152 based on the content of a user profile (e.g., first user profile 140) and is generated bytemplate engine 138.Template database 132 containscurrent templates 136 andpast template archive 134.Past template archive 134 contains a record of past templates and schedules.First event 112,second event 114,third event 116, andfourth event 118 are retrieved into user schedule 152 inmaster schedule database 176 by integrated control managerdata processing system 102 through the sending of queries, which queries are based oncurrent templates 136, to informationtechnology schedule database 104,ISO schedule database 106, and health andenvironment schedule database 108. For purposes of explanation, the example illustrated with respect toFIG. 1 operates on the assumption that integrated control managerdata processing system 102 will have access to information, stored incurrent templates 136 relating to the location among informationtechnology schedule database 104,ISO schedule database 106, and health andenvironment schedule database 108 at whichfirst event 112 andthird event 116 can be accessed. With respect tosecond event 114 andfourth event 118, the example illustrated with respect toFIG. 1 assumes that no location data is available to integrated control managerdata processing system 102 that would be helpful in ascertaining the location of the events among informationtechnology schedule database 104,ISO schedule database 106, and health andenvironment schedule database 108 ofsecond event 114 andfourth event 118. - A client, such as
first client 128, can communicate directly with a database, such asISO schedule database 106, through messages, such as client-to-database message 178 and database-to-client message 180. - The process for managing database records with events located in multiple registries in accordance with a preferred embodiment of the present invention, described in detail below with respect to
FIG. 4 , will result in the sending and receiving of several messages. As examples of these messages,first query message 160 containsfirst query 120, directed to informationtechnology schedule database 104, and includes a request forfirst event 112,second event 114 andfourth event 118. No request forthird event 116 is included infirst query 120, because location data is available to integrated control managerdata processing system 102 that indicates the presence ofthird event 116 on health andenvironment schedule database 108. The response tofirst query 120 arrives at integrated control managerdata processing system 102 in the form offirst event message 162, which containsfirst event 112 and data acknowledging the absence from informationtechnology schedule database 104 ofsecond event 114 andfourth event 118. - Similarly, second query message 164 contains
second query 122, directed toISO schedule database 106, and includes a request forsecond event 114 andfourth event 118. No request forthird event 116 is included insecond query 122, because location data is available to integrated control managerdata processing system 102 that indicates the presence ofthird event 116 on health andenvironment schedule database 108. Likewise, no request forfirst event 112 is included insecond query 122, because integrated control managerdata processing system 102 receivedfirst event 112 infirst event message 162. The response tosecond query 122 arrives at integrated control managerdata processing system 102 in the form ofsecond event message 166, which containssecond event 114 and data acknowledging the absence fromISO schedule database 106 offourth event 118. - As a final example,
third query message 168 containsthird query 124, directed to health andenvironment schedule database 108, and includes a request forthird event 116 andfourth event 118. No request forfirst event 112 orsecond event 114 is included inthird query 124, because integrated control managerdata processing system 102 receivedfirst event 112 infirst event message 162 and receivedsecond event 114 insecond event message 166. The response tothird query 124 arrives at integrated control managerdata processing system 102 in the form ofthird event message 170, which containsthird event 116 and data acknowledging the absence from health andenvironment schedule database 108 offourth event 118. - Turning now to
FIG. 2 , a high-level logical flowchart of a process for checking a schedule and sending notices and performing business control task notification in accordance with the preferred embodiment of the present invention is depicted. The process starts atstep 200, which will typically correspond to activation ofmaster schedule database 176 on integratedbusiness control manager 102. The process next moves to step 202. Atstep 202,master schedule database 176 verifies whether any schedules exist, which have not been checked recently for near-term event dates. If no such unchecked schedules exist, then the process ends atstep 204. If unchecked schedules exist, then the process next moves to step 206, which depictsmaster schedule database 176 loading user schedule 152. The process then proceeds to step 208. - At
step 208,master schedule database 176 on integratedbusiness control manager 102 examines user schedule 152 for events with near-term dates. This examination for near term dates is accomplished by reviewing the required performance dates infirst event 112,second event 114,third event 116 andfourth event 118. If events with near term dates do not exist, then the process ends atstep 204. If events with near term dates do exist, then the process next moves to step 210. - At
step 210,master schedule database 176 sends aschedule alert 186, containing any events with near-term required performance dates tonotification engine 126. The process next moves to step 212, which depictsnotification engine 126processing schedule alert 186 by sending anotification 158 tosecond client 130. The process then returns to step 202, which is described above. - With reference now to
FIG. 3 , a high-level logical flowchart of a process for preparing a schedule and performing business control task notification in accordance with a preferred embodiment of the present invention is illustrated. The process starts atstep 300, which corresponds to activation ofnotification engine 126. The process then moves to step 302. Atstep 302,notification engine 126 receives aschedule request 154 fromfirst client 128. The process then proceeds to step 304, which depicts integratedbusiness control manager 102 comparing a user profile, such as fourth user profile 148 to data fromcurrent templates 136 in compliance withschedule request 154. This is accomplished asnotification engine 126 sends aquery request 188 to queryengine 190.Query engine 190 then sends aprofile request 196 to user profiles 142 and receives a user profile such as fourth user profile 148 in aprofile reply 198.Query engine 190 then sends atemplate request 192 totemplate database 132 and the template database replies by sending an appropriate subset ofcurrent templates 136 in atemplate reply 194 to queryengine 190. - The process next moves to step 306. At
step 306,query engine 190 queries databases for attributes called for in the template from amongcurrent templates 136 received intemplate reply 194, as is detailed below with respect toFIG. 4 . Upon receipt of responses to database queries as a part of the process ofstep 306, the process then moves to step 308. Atstep 308,master schedule database 176 prepares, delivers, and stores a user schedule 152. Delivery of a schedule can be accomplished by sending aschedule alert 186 tonotification engine 156. The process then ends atstep 310. - With reference now to
FIG. 4 , there is depicted a high-level logical flowchart of a process for managing database records with events located in multiple registries in accordance with a preferred embodiment of the present invention. While the process ofFIG. 4 has been illustrated in a simplified embodiment as a logical flowchart, wherein single operations are explained sequentially for the purpose of explanatory clarity, one skilled in the art will quickly recognize that the process depicted inFIG. 4 can be separated into a group of interacting processes, operating as modules or program objects in parallel processes and interacting with one another. - Among these subprocesses, which can be described as modules and whose parts will be explained in greater detail below, assignment module 454 comprises steps 404-412. Assignment module 454 performs steps related to identifying whether, for each requested event, a known schedule database location exists, such as information
technology schedule database 104 as a location forfirst event 112. As will be detailed below, with respect to the example portrayed inFIG. 1 , the steps of assignment module 454 include analysis by integrated control managerdata processing system 102 ofcurrent templates 136 intemplate database 132 as to which schedule database can appropriately provide a given event, and the assignment of the event to a list, which is then used by integrated control managerdata processing system 102 in query preparation module 456. - Query preparation module 456 comprises steps 414-430 and
step 450. Query preparation module 456 prepares queries for integrated control managerdata processing system 102 to send to databases acrossnetwork 100. The third module, query communication module 458, includes steps 432-440 and sends queries to databases acrossnetwork 100. - The process of
FIG. 4 begins atstep 400, which depicts integrated control managerdata processing system 102 beginning the process of creating a schedule by accessing, distributing and modifying events in databases that are distributed across multiple data processing systems connected to a network. Step 400 typically involves activation of a query process on integrated control managerdata processing system 102, and activation may come from a user or an automated query. The process then proceeds to step 402, which illustrates integrated control managerdata processing system 102receiving schedule request 154.Schedule request 154 is received atnotification engine 126. As depicted with respect to the example inFIG. 1 , integrated control managerdata processing system 102 processes a query for four events of one or more records. The requested events arefirst event 112,second event 114,third event 116, andfourth event 118. - The process of
FIG. 4 next moves to step 404, which is part of an assignment subprocess, previously identified as assignment module 454. Step 404 depicts integrated control managerdata processing system 102 determining whether any requested events (e.g.,first event 112,second event 114,third event 116, and fourth event 118) remain in an ‘unassigned’ condition. For purposes of the discussion with respect toFIG. 4 in light of the example described with respect toFIG. 1 , an unassigned condition exists whenever, with respect to one offirst event 112,second event 114,third event 116, andfourth event 118, integrated control managerdata processing system 102 does not possess information as to the location among informationtechnology schedule database 104,ISO schedule database 106 and health andenvironment schedule database 108 on which the needed event is stored. If the location of all desired events is known, then the process ofFIG. 4 moves to step 414 in query formation module 456, which is described in detail below. - If, however, as in the example portrayed in
FIG. 1 , there exist events in an unassigned condition, for which location data is not available on integrated control managerdata processing system 102, then the process ofFIG. 4 next proceeds to step 406, which illustrates integrated control managerdata processing system 102 queuing a next event for identification of its location. The process then moves to step 408, which illustrates integrated control managerdata processing system 102 determining whether a database from among those to which integrated control managerdata processing system 102 can send queries (e.g., informationtechnology schedule database 104,ISO schedule database 106 and health and environment schedule database 108) is assigned to provide the event in question. The determination as to whether a database among those to which integrated control managerdata processing system 102 can send queries is assigned to provide the event in question can be made from data received in a request to access events instep 402, from data stored on integrated control managerdata processing system 102 or from data stored by other sources. - If a database is specified for the event in question, the process then moves to step 410 which depicts integrated control manager
data processing system 102 assigning the event in question to a location list for the specified database. With respect to the example portrayed inFIG. 1 , because the location offirst event 112 on informationtechnology schedule database 104 is known, integrated control managerdata processing system 102 assignsfirst event 112 to the list of events to be queried from informationtechnology schedule database 104. Similarly, because the location ofthird event 116 on health andenvironment schedule database 108 is known, integrated control managerdata processing system 102 assignsthird event 116 to the list of events to be queried from health andenvironment schedule database 108. - In
step 408, if no location data is available forfirst event 112, then the process proceeds to step 412, which depicts integrated control managerdata processing system 102 assigning an event to the list of events for which no database is known. In the example depicted inFIG. 1 , database locations are assigned and known forfirst event 112 andthird event 116, which would be assigned to query lists for their respective informationtechnology schedule database 104 and health andenvironment schedule database 108. However, no location data is available forsecond event 114 andfourth event 118.Second event 114 andfourth event 118 would be assigned to the query list for those events for which no database location data is known. After the completion ofstep 410 or the completion of step 412, the process returns to step 404. - If, in
step 404, no events remain which have not been assigned to the lists for a particular database or to the list for which no database location is known, the process then enters query preparation module 456 as the process moves to step 414. Step 414 illustrates integrated control managerdata processing system 102 adding any known unused database location data to the list of databases which will be queried with respect to events for which no location database is known. This data will typically be available fromdatabase configuration 110. - The process of
FIG. 4 then proceeds to step 416, which depicts integrated control managerdata processing system 102 determining whether any unreceived events remain. If no unreceived events remain, then the process leaves query preparation module 456 and enters return module 460 as the process moves to step 442, which will be described in detail below. - If any unreceived events remain, then the process of
FIG. 4 proceeds to step 418, which illustrates integrated control managerdata processing system 102 determining whether it has exhausted all of the possible databases that are available to receive queries for any unreceived events. The databases, which are available to receive queries for unreceived events, will include those databases referenced in information stored on integrated control managerdata processing system 102, those databases referenced in information received fromdatabase configuration 110, and those databases referenced in any information received in response to queries to previously queried databases. An individual database is exhausted after a query has been sent to it. - If the available databases have not been exhausted, then the process moves to step 420, which depicts integrated control manager
data processing system 102 queuing the next event for possible addition to the query, which is being prepared for transmission to the current database selected instep 420. The process then proceeds to step 422, which depicts integrated control managerdata processing system 102 determining whether any of the desired events remain untried for the current database selected instep 420. This step involves determining whether each of the unreceived events has been tried for the current database selected instep 440. - If, in
step 422, untried events remain, then the process of the preferred embodiment will move to step 424, which illustrates the integrated control managerdata processing system 102 designating the next event for possible addition to the query being sent the current database selected instep 420. The process then proceeds to step 426, which depicts integrated control managerdata processing system 102 determining whether the database specified instep 424 to receive the query currently being formed is the desired database that is assigned as containing the event under consideration. To determine if the database specified instep 424 to receive the query currently being formed in query formation module 456 is the desired database that is assigned as containing the event under consideration, integrated control managerdata processing system 102 refers to the list prepared in assignment module 454 for the current database selected instep 420, and ascertains whether the current event contained is identified on the list generated in assignment module 454. If the specified database being tried is the desired database, which is known to contain the required event, then the process moves to step 428, which depicts integrated control manager data processing system adding the current event to the query for the current database. - If in
step 426, the specified database is not the desired database, the process proceeds to step 430, which illustrates integrated control manager data processing system determining whether any database is specified with respect to the event under consideration. Integrated control managerdata processing system 102 determines that no database is specified for an event by searching for the current event in the list prepared by assignment module 454, containing those events for which no database was specified. If no database is specified for the event under consideration, the process moves to step 428, in which integrated control managerdata processing system 102 adds the event under consideration, for which no location data is available, to the query being prepared for the current database selected instep 420. - If a specified database is available but the current database is not the specified database, then the process returns to step 422, which is discussed above. Returning to step 422, if no events remain untried for the current database, then the process moves to step 432, which depicts sending a query to the current database.
- In the example illustrated with respect to
FIG. 1 , three queries are presented.First query 120 is a query forfirst event 112,fourth event 118, andsecond event 114.Second query 122 is a query requestingsecond event 114 andfourth event 118.Third query 124 requeststhird event 116 andfourth event 118. - Returning to
FIG. 4 , the process ofFIG. 4 next passes to step 434, which illustratesclient data processing 102 receiving events. As noted above, sendingquery 120 as afirst query message 160 would result in the return ofevent 112 infirst event message 162. Similarly, sendingsecond query 122 as second query message 164 would result in receipt ofsecond event 114 assecond event message 166, and sendingthird query 124 asthird query message 168 would result in receipt ofthird event 116 asthird event message 170. The process then proceeds to step 436, wherein integrated control managerdata processing system 102 stores location data for the events that it has received instep 434. The process next moves to step 438, which depicts integrated control manager data processing system performing operations on or with the received events. Operations performed on the received events will vary from embodiment to embodiment, and can include any operation that would be performed in the conventional. The process ofFIG. 4 next proceeds to step 440, which depicts the recording on un-received events, and is then followed by a return to step 416, which is discussed above. - Returning to step 416, if integrated control manager data processing system determines that no un-received events remain, the process next moves to step 442, which depicts integrated control manager
data processing system 102 determining whether a return of any events is required. If the return of events is required, the process ofFIG. 4 then proceeds to step 444, which depicts modification of events which require modification. The process then moves to step 446, which depicts replacing the modified events in their original databases by reference to the stored location information. The process then ends at step 448. If, in step 442, integrated control managerdata processing system 102 determines that no events require modification, then the process ofFIG. 4 next moves to step 448, where it ends. - Returning to step 418, if, in
step 418 integrated control managerdata processing system 102 determines that all of its available databases have been queried and there are events that have not been found in any database, then the process moves to step 450, which illustrates integrated control manager data processing system reporting failures and ends at step 448. - Turning now to
FIG. 5 , a high-level logical flowchart of a process for preparing template data and performing business control task notification in accordance with the preferred embodiment of the present invention as depicted. The process starts atstep 500, which corresponds to activation oftemplate engine 138. The process next proceeds to step 502. Step 502 depictstemplate engine 138 requesting a database and a user profile.Template engine 138 requests a user profile by sendingprofile request 182 to user profiles 142.Template engine 138 requests a database by sendingdatabase request 172 to a database such as health andenvironmental schedule database 108. The process then moves to step 504 which depicts template engine receiving a database and a user profile. As depicted in the example illustrated inFIG. 1 ,template engine 138 receives aprofile result transmission 184 containing first user profile 140, second user profile 144, third user profile 146 and fourth user profile 148.Template engine 138 also receives health and environment schedule database as part ofdatabase result transmission 174. The process then moves to step 506. Step 506 depictstemplate engine 138 determining whether it has exhausted available common events from first user profile 140, second user profile 144, third user profile 146 and fourth user profile 148. If common events from first user profile 140, second user profile 144, third user profile 146 and fourth user profile 148 have been exhausted, then the process proceeds to step 507, which depicts template engine generating a report. Atemplate report 199 is sent totemplate database 132, and the process then ends atstep 508. - If at
step 506, common events from first user profile 140, second user profile 144, third user profile 146 and fourth user profile 148 have not been exhausted, then the process proceeds to step 510, which depictstemplate engine 138 identifying and processing a next common event from among two or more of first user profile 140, second user profile 144, third user profile 146 and fourth user profile 148. The process then moves to step 512, which depictstemplate engine 138 determining whether the common event processed instep 510 correlates to a common trait. If the common event correlates to no discernable common trait, then the process proceeds to step 514, which depictstemplate engine 138 flagging the common event for later processing. If the common event correlates to a common trait instep 512, then the process next moves to step 516. Step 516 depictstemplate engine 138 adding the common event and common trait totemplate report 199. - As has been described, the present invention provides a system, method and computer program product for accessing and distributing events in business control database that are distributed across multiple data processing systems connected to a network. The present invention provides facilities for sending a queries from a local integrated control manager data processing system to a remote database, wherein that query is composed of requests for events known to be stored on the database and events whose location is unknown. Once an event is received from a remote database, the present invention provides facilities for creating schedules and for notifying clients. The present invention improves interaction between clients and business control databases by providing an orderly and methodical system for dealing with events distributed across multiple databases.
- While the invention has been particularly shown as described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. It is also important to note that although the present invention has been described in the context of a fully functional computer system, those skilled in the art will appreciate that the mechanisms of the present invention are capable of being distributed as a program product in a variety of forms, and that the present invention applies equally regardless of the particular type of signal bearing media utilized to actually carry out the distribution. Examples of signal bearing media include, without limitation, recordable type media such as floppy disks or CD ROMs and transmission type media such as analog or digital communications links.
- The present invention has been described in relation to particular embodiments that are intended in all respects to be illustrative rather than restrictive. Although specific terms are used, the description thus given uses terminology in a generic and descriptive sense only and not for purposes of limitation.
Claims (8)
1. An automated business control task notification service, said service comprising:
processing a combination of one or more databases and one or more user profiles to generate a schedule template;
receiving a request for a schedule;
comparing attributes of said request for said schedule to a user profile and a schedule template to identify one or more events of said schedule template to be accessed from one or more of a plurality of distributed databases;
forming a query to be sent to said one or more distributed databases;
sending said query to a particular database among said plurality of distributed databases;
receiving a positive response to said query, indicating that said particular database contains said first event for said record, and said event;
in response to receiving said event, creating said schedule;
storing said schedule;
identifying one or more current events in said schedule requiring a notification; and
sending said notification to a destination.
2. The service of claim 1 , wherein said step of comparing attributes of said request for said schedule to a user profile and a schedule template further comprises identifying one or more events of said schedule template to be accessed from one or more of a plurality of distributed databases, wherein a first event among said one or more events resides in an unknown database among said plurality of databases and it is known that a second event resides in a particular database among said plurality of databases.
3. The service of claim 2 , wherein said step of forming a query to be sent to said one or more distributed databases further comprises forming a query which query includes a request for said first event and a request for said second event.
4. The service of claim 1 , wherein said step of processing a combination of one or more databases and one or more user profiles to generate a schedule template further comprises allowing an authorized user to edit said template.
5. The service of claim 1 , wherein said step of sending said notification further comprises disabling reproduction of said notification.
6. The service of claim 1 , wherein said step of sending said notification further comprises disabling sharing of said notification.
7. The service of claim 1 , wherein said step of sending said notification further comprises disabling retransmission of said notification.
8. The service of claim 1 , wherein said step of processing a combination of one or more databases and one or more user profiles to generate a schedule template further comprises:
requesting one or more user profiles and one or more databases;
receiving one or more user profiles and one or more databases;
identifying a common event in said one or more databases that is common to one or more user profiles;
identifying a common trait associated with said common event; and
adding said common event to a said template.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/948,586 US20080091665A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/043,670 US7356538B2 (en) | 2005-01-25 | 2005-01-25 | Configurable business controls task notification |
US11/948,586 US20080091665A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/043,670 Continuation US7356538B2 (en) | 2005-01-25 | 2005-01-25 | Configurable business controls task notification |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080091665A1 true US20080091665A1 (en) | 2008-04-17 |
Family
ID=36698125
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/043,670 Active 2026-04-07 US7356538B2 (en) | 2005-01-25 | 2005-01-25 | Configurable business controls task notification |
US11/948,555 Abandoned US20080077467A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
US11/948,521 Abandoned US20080091664A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
US11/948,586 Abandoned US20080091665A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/043,670 Active 2026-04-07 US7356538B2 (en) | 2005-01-25 | 2005-01-25 | Configurable business controls task notification |
US11/948,555 Abandoned US20080077467A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
US11/948,521 Abandoned US20080091664A1 (en) | 2005-01-25 | 2007-11-30 | Configurable Business Controls Task Notification |
Country Status (1)
Country | Link |
---|---|
US (4) | US7356538B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11182600B2 (en) * | 2015-09-24 | 2021-11-23 | International Business Machines Corporation | Automatic selection of event video content |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10635260B2 (en) | 2007-01-22 | 2020-04-28 | Cerner Innovation, Inc. | System and user interface for clinical reporting and ordering provision of an item |
US7680779B2 (en) * | 2007-01-26 | 2010-03-16 | Sap Ag | Managing queries in a distributed database system |
US7912623B2 (en) * | 2007-09-25 | 2011-03-22 | Denso Corporation | Engine control system designed to manage schedule of engine control tasks |
EP2136323B1 (en) * | 2008-06-19 | 2013-01-02 | Tac AB | Assignment of alarms |
US10158734B2 (en) * | 2015-04-01 | 2018-12-18 | Google Llc | Trigger associated notification delivery in an enterprise system |
Citations (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5325091A (en) * | 1992-08-13 | 1994-06-28 | Xerox Corporation | Text-compression technique using frequency-ordered array of word-number mappers |
US5761665A (en) * | 1995-10-31 | 1998-06-02 | Pitney Bowes Inc. | Method of automatic database field identification for postal coding |
US5802518A (en) * | 1996-06-04 | 1998-09-01 | Multex Systems, Inc. | Information delivery system and method |
US6047260A (en) * | 1997-06-05 | 2000-04-04 | Attention Control Systems, Inc. | Intelligent planning and calendaring system with cueing feature and floating tasks |
US6122648A (en) * | 1999-01-11 | 2000-09-19 | Gohome Networks, Inc. | Method apparatus and system for improved content management and delivery |
US20020055089A1 (en) * | 2000-10-05 | 2002-05-09 | E-Vantage International, Inc. | Method and system for delivering homework management solutions to a designated market |
US20020133477A1 (en) * | 2001-03-05 | 2002-09-19 | Glenn Abel | Method for profile-based notice and broadcast of multimedia content |
US20020178077A1 (en) * | 2001-05-25 | 2002-11-28 | Katz Steven Bruce | Method for automatically invoking a software module in response to an internal or external event affecting the procurement of an item |
US6519763B1 (en) * | 1998-03-30 | 2003-02-11 | Compuware Corporation | Time management and task completion and prediction software |
US20030131018A1 (en) * | 2002-01-09 | 2003-07-10 | International Business Machines Corporation | Common business data management |
US20030140316A1 (en) * | 1998-02-23 | 2003-07-24 | David Lakritz | Translation management system |
US20040117046A1 (en) * | 2002-12-12 | 2004-06-17 | Renzo Colle | User interface for scheduling tasks |
US20040133889A1 (en) * | 2002-12-12 | 2004-07-08 | Renzo Colle | Scheduling tasks across multiple locations |
US20040143477A1 (en) * | 2002-07-08 | 2004-07-22 | Wolff Maryann Walsh | Apparatus and methods for assisting with development management and/or deployment of products and services |
US20040158568A1 (en) * | 2002-12-12 | 2004-08-12 | Renzo Colle | Scheduling resources for performing a service |
US20040267595A1 (en) * | 2003-06-30 | 2004-12-30 | Idcocumentd, Llc. | Worker and document management system |
US20050175201A1 (en) * | 2004-02-06 | 2005-08-11 | Herman Barry S. | Secure key reset using encryption |
US7133869B2 (en) * | 2001-03-06 | 2006-11-07 | Knowledge Vector, Inc. | Methods and systems for and defining and distributing information alerts |
US20070112574A1 (en) * | 2003-08-05 | 2007-05-17 | Greene William S | System and method for use of mobile policy agents and local services, within a geographically distributed service grid, to provide greater security via local intelligence and life-cycle management for RFlD tagged items |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6335927B1 (en) * | 1996-11-18 | 2002-01-01 | Mci Communications Corporation | System and method for providing requested quality of service in a hybrid network |
US7130807B1 (en) * | 1999-11-22 | 2006-10-31 | Accenture Llp | Technology sharing during demand and supply planning in a network-based supply chain environment |
US20020065828A1 (en) * | 2000-07-14 | 2002-05-30 | Goodspeed John D. | Network communication using telephone number URI/URL identification handle |
US7233933B2 (en) * | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US6714913B2 (en) * | 2001-08-31 | 2004-03-30 | Siemens Medical Solutions Health Services Corporation | System and user interface for processing task schedule information |
US20040193474A1 (en) * | 2003-03-31 | 2004-09-30 | Carl Digiacomo | Estimating, costing, and installation system for home renovation projects and tree-based profit distribution system |
-
2005
- 2005-01-25 US US11/043,670 patent/US7356538B2/en active Active
-
2007
- 2007-11-30 US US11/948,555 patent/US20080077467A1/en not_active Abandoned
- 2007-11-30 US US11/948,521 patent/US20080091664A1/en not_active Abandoned
- 2007-11-30 US US11/948,586 patent/US20080091665A1/en not_active Abandoned
Patent Citations (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5325091A (en) * | 1992-08-13 | 1994-06-28 | Xerox Corporation | Text-compression technique using frequency-ordered array of word-number mappers |
US5761665A (en) * | 1995-10-31 | 1998-06-02 | Pitney Bowes Inc. | Method of automatic database field identification for postal coding |
US5802518A (en) * | 1996-06-04 | 1998-09-01 | Multex Systems, Inc. | Information delivery system and method |
US6047260A (en) * | 1997-06-05 | 2000-04-04 | Attention Control Systems, Inc. | Intelligent planning and calendaring system with cueing feature and floating tasks |
US20030140316A1 (en) * | 1998-02-23 | 2003-07-24 | David Lakritz | Translation management system |
US6519763B1 (en) * | 1998-03-30 | 2003-02-11 | Compuware Corporation | Time management and task completion and prediction software |
US6122648A (en) * | 1999-01-11 | 2000-09-19 | Gohome Networks, Inc. | Method apparatus and system for improved content management and delivery |
US20020055089A1 (en) * | 2000-10-05 | 2002-05-09 | E-Vantage International, Inc. | Method and system for delivering homework management solutions to a designated market |
US20020133477A1 (en) * | 2001-03-05 | 2002-09-19 | Glenn Abel | Method for profile-based notice and broadcast of multimedia content |
US7133869B2 (en) * | 2001-03-06 | 2006-11-07 | Knowledge Vector, Inc. | Methods and systems for and defining and distributing information alerts |
US20020178077A1 (en) * | 2001-05-25 | 2002-11-28 | Katz Steven Bruce | Method for automatically invoking a software module in response to an internal or external event affecting the procurement of an item |
US20030131018A1 (en) * | 2002-01-09 | 2003-07-10 | International Business Machines Corporation | Common business data management |
US20040143477A1 (en) * | 2002-07-08 | 2004-07-22 | Wolff Maryann Walsh | Apparatus and methods for assisting with development management and/or deployment of products and services |
US20040117046A1 (en) * | 2002-12-12 | 2004-06-17 | Renzo Colle | User interface for scheduling tasks |
US20040133889A1 (en) * | 2002-12-12 | 2004-07-08 | Renzo Colle | Scheduling tasks across multiple locations |
US20040158568A1 (en) * | 2002-12-12 | 2004-08-12 | Renzo Colle | Scheduling resources for performing a service |
US20040267595A1 (en) * | 2003-06-30 | 2004-12-30 | Idcocumentd, Llc. | Worker and document management system |
US20070112574A1 (en) * | 2003-08-05 | 2007-05-17 | Greene William S | System and method for use of mobile policy agents and local services, within a geographically distributed service grid, to provide greater security via local intelligence and life-cycle management for RFlD tagged items |
US20050175201A1 (en) * | 2004-02-06 | 2005-08-11 | Herman Barry S. | Secure key reset using encryption |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11182600B2 (en) * | 2015-09-24 | 2021-11-23 | International Business Machines Corporation | Automatic selection of event video content |
Also Published As
Publication number | Publication date |
---|---|
US20080091664A1 (en) | 2008-04-17 |
US20060167847A1 (en) | 2006-07-27 |
US20080077467A1 (en) | 2008-03-27 |
US7356538B2 (en) | 2008-04-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7401054B1 (en) | Content bank for objects | |
US5878416A (en) | Automated system and method for matching an item of business property to a recipient | |
Desouza | Barriers to effective use of knowledge management systems in software engineering | |
US6697810B2 (en) | Security system for event monitoring, detection and notification system | |
US9281963B2 (en) | Method and system for email search | |
US6157915A (en) | Method and apparatus for collaboratively managing supply chains | |
US6230201B1 (en) | Configurable transaction routing system and method | |
US7233940B2 (en) | System for processing at least partially structured data | |
US8713175B2 (en) | Centralized behavioral information system | |
US7356538B2 (en) | Configurable business controls task notification | |
US20020188620A1 (en) | Calendar-enhanced directory searches including dynamic contact information | |
US20020157017A1 (en) | Event monitoring, detection and notification system having security functions | |
US20020035504A1 (en) | Lead suspect management | |
US20020059236A1 (en) | Computer system with access control mechanism | |
US20030018643A1 (en) | VIGIP006 - collaborative resolution and tracking of detected events | |
US20030014395A1 (en) | Communication triggered just in time information | |
US9203649B2 (en) | Processing of email based on semantic relationship of sender to recipient | |
US20090006411A1 (en) | Strategic Business Management System | |
US20040073607A1 (en) | Multimedia messaging system and method | |
US6879972B2 (en) | Method for designing a knowledge portal | |
US7882085B2 (en) | Database system and method with improved locks | |
US7912930B1 (en) | System and method for resource provisioning | |
US6957234B1 (en) | System and method for retrieving data from a database using a data management system | |
JPH03217954A (en) | Method and apparatus for controlling automatically distributing data object | |
US10313291B2 (en) | Method for determining predictive response time across enterprise communication systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |