US2012331482A1PendingUtilityA1
Apparatus and Systems For Measuring, Monitoring, Tracking and Simulating Enterprise Communications and Processes
Individually held — no corporate assignee on recordPriority: Dec 15, 2000Filed: Sep 21, 2011Published: Dec 27, 2012
Est. expiryDec 15, 2020(expired)· nominal 20-yr term from priority
G06Q 10/00
57
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
The present invention comprises apparatus and systems for measuring, monitoring, tracking and simulating enterprise communications and processes. A central message repository or database is constructed, comprised of monitoring messages sent from process messaging systems. The database may then be accessed or queried as desired. A simulation tool assists in reviewing present and proposed processes and sub-processes before modifying existent systems or creating new systems.
Claims
exact text as granted — not AI-modified1 .- 55 . (canceled)
56 . A computerized method for use in an asynchronous messaging environment, wherein said messaging environment comprises at least one original message comprised of original message data, comprising:
a first process, sub process, application, or activity sending said original message comprised of said original message data to a second process, sub process, application or activity via a messaging broker, providing a monitoring message, wherein said monitoring message comprises a copy of at least some original message data comprising said original message; and, transmitting said monitoring message to a repository,
wherein said original message data comprises the status of a process, sub process or activity.
57 . A method as in claim 56 wherein said repository is a central message repository.
58 . A method as in claim 56 wherein said repository is a message monitoring repository.
59 . A method as in claim 56 wherein said original message data is provided in data fields.
60 . A method as in claim 59 wherein said data fields comprise process identifier information or sub process identifier information.
61 . A method as in claim 56 wherein said repository stores at least some original message data.
62 . A method as in claim 56 wherein the data in said repository may be used to generate messages to one or more processes, sub processes, activities, applications, users and/or administrators.
63 . A method as in claim 56 wherein the data in said repository may be used to generate feedback to one or more processes, sub-processes, activities, applications, users and/or administrators.
64 . A method as in claim 56 further comprising generating a monitoring message.
65 . A method as in claim 58 further comprising generating messages and/or feedback to the group consisting of processes, sub-processes, activities, applications, users and/or administrators.
66 . A method as in claim 65 wherein said messages comprise error messages.
67 . A method as in claim 65 wherein said messages comprise event messages.
68 . A method as in claim 65 wherein said messages comprise exception messages.
69 . A method as in claim 65 wherein said messages comprise trigger messages.
70 . A method as in claim 65 wherein said messages comprise threshold messages.
71 . A method as in claim 65 wherein said messages comprise flagged indicators.
72 . A method as in claim 65 wherein said messages comprise specially designated messages.
73 . A method as in claim 56 further comprising distributing information regarding the progress of transaction records and/or processes using a real time tool.
74 . A method as in claim 56 wherein said data fields are path specific data fields.
75 . A method as in claim 56 further comprising providing access to said repository.
76 . A method as in claim 75 further comprising providing access to a user and/or administrator.
77 . A method as in claim 56 further comprising reviewing said repository.
78 . A method as in claim 56 further comprising providing the status of a process, sub process and/or activity.
79 . A method as in claim 56 further comprising providing access to said repository through a display.
80 . A method as in claim 79 further comprising further comprising providing the status of a process, sub process and/or activity through a display.
81 . A method as in claim 56 wherein providing a monitoring message, wherein said monitoring message comprises a copy of at least some original message data comprising said original message, further comprises providing said monitoring message through a messaging component.
82 . A method as in claim 56 further comprising simulating said method.
83 . A method as in claim 82 further comprising simulating said method with real time data, processes, sub processes and/or activities.
84 . A method as in claim 56 further comprising simulating said method prior to implementation.
85 . A method as in claim 56 further comprising simulating said method prior to integration into an enterprise.
86 . A computerized method for assembling and simulating enterprise communications and processes comprising:
providing at least two sub processes; and assembling said at least two sub processes into a simulated process wherein a first of the at least two sub processes communicates with a second of said at least two sub processes by providing a message with output data and said second of at least two sub processes accepts said message as providing input data.
87 . A method as in claim 86 further comprising providing said method with real time data, processes, sub processes and/or activities.
88 . A method as in claim 86 further comprising simulating said method prior to implementation.
89 . A method as in claim 86 further comprising simulating said method prior to integration into an enterprise.
90 . A method as in claim 86 further comprising providing said method via a display.
91 . A method as in claim 86 further comprising providing said method via a process development environment screen display.
92 . A method as in claim 86 wherein said data is provided in a data field.
93 . A method as in claim 86 further comprising providing a user with tools to construct a sub process.
94 . A method as in claim 93 further comprising providing a user with said tools through a screen display
95 . A method as in claim 93 wherein said tools identify properties of said sub process.
96 . A method as in claim 95 wherein said properties comprise a process, sub process, application, activity, message queue and/or data field.
97 . A method as in claim 86 further comprising providing a message queue construction tool.
98 . A method as in claim 97 wherein said message queue construction tool provides alternatives for queue manager, input queue and/or output queue.
99 . A method as in claim 95 further comprising providing an application construction tool.
100 . A method as in claim 99 wherein said application construction tool provides one or more applications at either end of a queue or path to receive said message.
101 . A method as in claim 100 further comprising providing a section of particular data fields.
102 . A method as in claim 86 further comprising providing activities.
103 . A method as in claim 86 further comprising altering an existing process, sub process or activity.
104 . A method as in claim 86 further comprising altering an existing process, sub process or activity.
105 . A method as in claim 86 wherein said simulation occurs before modifying existent systems or implementing new systems.
106 . A system for use in a networked asynchronous messaging environment, wherein said messaging environment comprises at least one original message comprised of original message data, comprising:
a first process, sub process, application, or activity for sending said original message comprised of said original message data to a second process, sub process, application or activity; a messaging broker for transporting said original message between said first and second process, sub process, application, or activity; a monitoring message, wherein said monitoring message comprises a copy of at least some original message data comprising said original message for sending to a repository for storage of said at least some original message data, wherein said original message data comprises the status of a process, sub process or activity.
107 . A system as in claim 106 further comprising a display for providing the status of a process, sub process and/or activity.
108 . A system as in claim 106 wherein said at least some original message data comprises process identifier information or sub process identifier information.
109 . A system as in claim 106 further comprising a message for sending to one or more processes, sub processes, activities, applications, users and/or administrators.
110 . A system as in claim 106 further comprising feedback to one or more processes, sub-processes, activities, applications, users and/or administrators.
111 . A system as in claim 106 wherein said original message data is at least partially simulated original message data.
112 . A computer-readable storage medium storing program code for an asynchronous messaging environment, wherein said messaging environment comprises at least one original message comprised of original message data, comprising:
a first process, sub process, application, or activity sending said original message comprised of said original message data to a second process, sub process, application or activity via a messaging broker, providing a monitoring message, wherein said monitoring message comprises a copy of at least some original message data comprising said original message; and,
transmitting said monitoring message to a repository, wherein said original message data comprises the status of a process, sub process or activity.
113 . A computer-readable storage medium storing program code as in claim 112 wherein said repository is a central message repository.
114 . A computer-readable storage medium storing program code as in claim 112 wherein said repository is a message monitoring repository.
115 . A computer-readable storage medium storing program code as in claim 112 wherein said repository stores at least some original message data.
116 . A computer-readable storage medium storing program code as in claim 112 wherein the data in said repository may be used to generate messages to one or more processes, sub processes, activities, applications, users and/or administrators.
117 . A computer-readable storage medium storing program code as in claim 112 wherein the data in said repository may be used to generate feedback to one or more processes, sub-processes, activities, applications, users and/or administrators.
118 . A computer-readable storage medium storing program code as in claim 112 further comprising generating a monitoring message.
119 . A computer-readable storage medium storing program code as in claim 112 further comprising reviewing said repository.
120 . A computer-readable storage medium storing program code as in claim 112 further comprising providing the status of a process, sub process and/or activity.
121 . A computer-readable storage medium storing program code as in claim 112 wherein providing a monitoring message, wherein said monitoring message comprises a copy of at least some original message data comprising said original message, further comprises providing said monitoring message through a messaging component.
122 . A computer-readable storage medium storing program code as in claim 112 further comprising simulating said method.
123 . A computer-readable storage medium storing program code as in claim 112 further comprising simulating said method with real time data, processes, sub processes and/or activities.
124 . A computer-readable storage medium storing program code as in claim 112 further comprising simulating said method prior to implementation.
125 . A computer-readable storage medium storing program code as in claim 112 further comprising simulating said method prior to integration into an enterprise.Join the waitlist — get patent alerts
Track US2012331482A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.