PTO/SB/57 (02-09)
`Approved for use through 02128/2013. OMB 0651-0064
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.
`(Also referred to as FORM PT0-1465)
`REQUEST FOR EX PARTE REEXAMINATION TRANSMITTAL FORM
`
`68354 U.S. PI <P
`
`Address to:
`I \l\l\\1\\l\ \Ill I II Ill Ill\\ 1\11 I II \\IIIII\ I Ill\
`Mail Stop Ex Parte Reexam
`Attorney Docket No.: OPEN2200-1 90°09960
`Commissioner for Patents
`P.O. Box 1450
`Date: October 18, 2011
`Alexandria, VA 22313-1450
`[8] This is a request for ex parle reexamination pursuant to 37 CFR 1.510 of patent number
`7,603,674
`issued October 13, 2009
`. The request is made by:
`- - - - - - - -
`0 patent owner.
`18] third party requester.
`[8J The name and address of the person requesting reexamination is:
`Ariyeh Akmal
`
`1.
`
`2.
`
`1301 W. 25th Street, Suite 408
`Austin, Texas 78705
`
`a. A check in the amount of$. ______ is enclosed to cover the reexamination fee, 37 CFR 1.20(c)(1 );
`
`b. The Director is hereby authorized to charge the fee as set forth in 37 CFR 1.20(c)(1)
`to Deposit Account No. 503183
`; or
`
`c. Payment by credit card. Form PT0-2038 is attached.
`
`4.
`
`3. D
`[8]
`D
`[8] Any refund should be made by D check or I8J credit to Deposit Account No. _5_0_3_1_8_3 ___ _
`
`37 CFR 1.26(c). If payment is made by credit card, refund must be to credit card account.
`[8] A copy of the patent to be reexamined having a double column format on one side of a separate paper is
`enclosed. 37 CFR 1.510(b)(4)
`6. 0 CD-ROM or CD-R in duplicate, Computer Program (Appendix) or large table
`D Landscape Table on CD
`7. D Nucleotide and/or Amino Acid Sequence Submission
`If applicable, items a. - c. are required.
`a. D Computer Readable Form (CRF)
`i. D CD-ROM (2 copies) or CD-R (2 copies); or
`ii. D paper
`c. D Statements verifying identity of above copies
`8. D A copy of any disclaimer, certificate of correction or reexamination certificate issued in the patent is included.
`[8] Reexamination of claim(s) 1-173
`9.
`is requested.
`18728/2811 SSTEVEHS 88888881 583183
`10. [8] A copy of every patent or printed publication relied upon is submitted h'ir~f~~uding aJirulng thereof on
`2::>,1J,89 DA
`Form PTO/SB/08, PT0-1449, or equivalent.
`'
`11. D An English language translation of all necessary and pertinent non-English language patents and/or printed
`
`5.
`
`b. Specification Sequence Listing on:
`
`9888~ ~
`
`publications is included.
`
`[Page 1 of2)
`This collection of information is required by 37 CFR 1.510. The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO to
`process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection is estimated to take 18 minutes to complete,
`induding gathering, preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any comments on
`the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Oflicer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS
`ADDRESS. SEND TO: Mail Stop Ex Parte Reexam, Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`If you need assistance in completing the form, ca/11-800-PT0-9199 and select option 2.
`
`HP_1003_0001
`
`

`
`PTO/SB/57 (02-09)
`Approved for use through 02128/2013. OMB 0651-0064
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995 no persons are required to respond to a collection of infonnation unless it displays a valid OMB control number
`
`12. (g) The attached detailed request includes at least the following items:
`
`a. A statement identifying each substantial new question of patentability based on prior patents and printed
`publications. 37 CFR 1.510(b)(1)
`b. An identification of every claim for which reexamination is requested, and a detailed explanation of the pertinency
`and manner of applying the cited art to every claim for which reexamination is requested. 37 CFR 1.510(b)(2).
`
`13. D A proposed amendment is included (only where the patent owner is the requester). 37 CFR 1.510(e)
`14. (g) a. It is certified that a copy of this request (if filed by other than the patent owner) has been served in its entirety on
`the patent owner as provided in 37 CFR 1.33(c).
`The name and address of the party served and the date of service are:
`Joseph E. Chovanes
`
`5 Great Valley Parkway, Suite 329
`
`Malvern, PA 19355
`
`Date of Service:
`
`; or
`
`October 18, 2011
`D b. A duplicate copy is enclosed because service on patent owner was not possible. An explanation of the efforts
`
`made to serve patent owner is attached. ~ MPEP 2220.
`15. Correspondence Address: Direct all communications about the reexamination to:
`
`The address associated with Customer Number:
`
`(g)
`OR
`D Firm or
`
`Individual Name
`
`Address
`
`City
`
`Country
`
`I
`
`44654
`
`I
`
`I State
`
`I Zip
`
`Telephone
`
`I Email
`16. ~ The patent is currently the subject of the following concurrent proceeding(s):
`D a. Copending reissue Application No.
`D b. Copending reexamination Control No.
`D c. Copending Interference No.
`~ d. Copending litigation styled:
`Case No. 2:11-CV-01609-JCJ, YYZ, LLC v. Metastorm, Inc.
`and Open Tji!'1ft {j6r~ oration, USDC, E. D. of Pennsylvania
`":'J.::•l< ~ome public. Credit card Information should not be
`WARNING: lnf
`included on ttk.foD6. Pro ede crec ~t ca d infonnation and authorization on PT0-2038.
`V
`I
`-
`October 18, 2011
`---
`Authorized Signature
`Date
`51,388 D For Patent Owner Requester
`Ariyeh Akmal
`Registration No. (g) For Third Party Requester
`Typed/Printed Name
`
`-..........;
`
`[Page 2 of2)
`
`HP_1003_0002
`
`

`
`APPENDIX ''E''
`
`UNITED STATES PATENT
`NO. 7,603,67 4
`
`Page 208
`
`REQUEST FOR REEXAMINATION OF
`U.S. PATENT NO. 7,603,674
`
`HP_1003_0003
`
`

`
`liD~ 1111 ~~~~~ U~IIUIIII~ IIIII m ~Ill lin ~~~11~11~11
`
`US007603674B2
`
`(12) United States Patent
`Cyr et al.
`
`(tO) Patent No.:
`(45) Date of Patent:
`
`US 7,603,674 B2
`*Oct. 13, 2009
`
`(54) APPARATUS AND SYSTEMS FOR
`MEASURING, MONITORING, TRACKING
`AND SIMULATING ENTERPRISE
`COMMUNICATIONS AND PROCESSES
`
`(75)
`
`Inventors: Vincent R. Cyr, Glen Mills, PA (US);
`Kenneth Fritz, Glen Mills, PA (US)
`
`(73) Assignee: VYZ, LLC
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 272 days.
`
`This patent is subject to a terminal dis(cid:173)
`claimer.
`
`(21) Appl. No.: 11/398,133
`
`(22) Filed:
`
`Apr. 5, 2006
`
`(65)
`
`Prior PubUcation Data
`US 2006/0200804 AI
`Sep. 7,2006
`
`Related U.S. AppUcation Data
`(63) Continuation of application No. 091737,494, filed on
`Dec. 15,2000, now Pat. No. 7,062,749.
`
`(51)
`
`Int. Cl.
`G06F 13100
`(2006.01)
`(52) U.S. CL ........................... 719/313; 709/217; 707/1;
`707/10
`(58) FieldofCiasslficatlonSearch ................. 717/103;
`705/9; 709/231,227, 202, 206, 217; 719/314,
`719/315,316, 313; 707/3, 10, 1
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,404,501 A
`5,887,167 A
`5,949,998 A
`5,960,200 A
`
`4/1995 Carr et al.
`3/1999 Sutton
`9/1999 Fowlow et al.
`9/1999 Eager et al.
`
`6,018,627 A
`1/2000 Iyengar et al.
`3/2000 Du etal.
`6,041,306 A
`5/2000 Leymann et al.
`6,065,009 A
`712000 Wagner
`6,092,102 A
`9/2000 Leymann et al.
`6,122,633 A
`6,278,977 81
`8/2001 Agrawal et al.
`6,405,266 81 •
`6/2002 Basset al.
`. ................. 7191328
`7/2002 Leymann et al.
`6,415,297 Bl
`9/2002 Kidder et al. . ............. 379/9.03
`6,445,774 81 •
`10/2002 Ferri et al.
`6,460,175 81
`10/2002 Stuart
`6,466,935 81
`6,487,548 81 • 11/2002 Leymann et al. .. .. . .. .. . ... • . 7(1713
`12/2002 Smith et al.
`6,501,950 81
`U2003 Todd
`6,510,429 81
`3/2003 Dadiomov et al.
`6,529,932 81
`6,543,047 Bl
`4/2003 Vrhel et al.
`
`(Continued)
`
`OTIIER PUBLICATIONS
`
`"A Performance StudyofCiient-Broker-Server Systems", Omotunde
`Adebayo et al, ACM, Nov. 1997, pp. 1-15.•
`
`(Continued)
`Primary Examiner-Andy Ho
`
`(57)
`
`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 mes(cid:173)
`sages 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.
`
`173 Claims, 6 Drawing Sheets
`
`HP_1003_0004
`
`

`
`US 7,603,674 B2
`2
`
`U.S. PATENT DOCUMENTS
`
`6,553,438 B1
`6,601,233 B1
`6,662,355 B1
`6,671,728 B1 •
`6,681,245 B1
`6,725,445 B1
`6,728,947 B1
`6,757,710 B2
`6,789,252 B1
`6,901,430 B1
`6,943,681 B2
`7,057,752 B1 •
`
`4/2003 Coffman et al.
`7/2003 Underwood
`1212003 Caswell ct al.
`1212003 Mayberry ................... 709/227
`112004 Sasagawa
`4/2004 Leyma.n.n ct al.
`4/2004 Bengston
`6/2004 Reed
`9/2004 Burke et al.
`5/2005 Smith
`9/2005 Rezvani ct al.
`6/2006 Klotz, Jr ............ ; ....... 358/1.15
`
`OTHER PUBLICATIONS
`
`"A Publish/Subscribe CORBA Persistent State Service Prototype",
`ACM, Apr. 2000, pp. 231-255.•
`Adaptive Plug-andPlay Components for Evolutionary Software
`Development, Mira Me:zin.i et al, ACM, 1998, pp. 97-116.•
`Wide Worldlow Development Methodology, L. Baresi et al, ACM,
`Mar. 1999, pp. 19-28.•
`"Implementing SAP RJ3 How to Introduce a Large System into a
`Large Organization," pp. 1-73, N.H. Bancroft et al., 1997.
`"SAP An Executive Comprehensive Guide," Grant Norris et al., pp.
`1-13, 1998.
`Wmdows NT Server Operating System. Microsoft Message Queuing
`Services, Microsoft, 1997, pp. 1-38.
`
`Messaging & Queuing Using the MQI, bumie Blakey et al., Jun. 26,
`1995, Whole Book.
`Building Distributed Applications with Message Queing
`Middleware, Peter Houston, Microsoft Corp., Mar. 1998, 7 pages.
`"Special Issue on TP Monitors and Distributed Transaction Manage(cid:173)
`ment," Ron Obermarck et al., Data Engineering, Mar. 1994, vol. 17,
`No. I, IEEE Computer Society, 32 pages.
`"Remote Queues: Exposing Message Queues for Optimization and
`Atomicity," E.A. Brewer et al., MCM, 1995, pp. 42-53.
`Cummings, Enterprise Integration with Worldlow Management,
`Nov. 1, 1999.
`Ebbers, et al, Image and Worldlow Library, Apr. 1999.
`Van De Putte, et al, Business Integration Solutions with MQ Series
`Intergrator, Aug. 2000.
`Stegmaier, et al, Image and Worldlow Library, Feb. 1998.
`Eller, et al, Image and Worldlow Library, Oct. 1997.
`Van Den Enden, et al, A Case Study in Application Integration, Oct.
`16,2000.
`Cummings, Enterprise Integration with Asynchronous Messaging
`Services, Oct. 6, 1999.
`ffiM, Software Announcement MQSeries Worldlow 3.2. Adds Sup(cid:173)
`port fore-business and New Platforms, Jun. 15,1999.
`Leymann, et al, Production Worldlow, excerpts, 2000.
`Alonso, et al, Exotica!FMQM, Aug. 1995.
`Alonso, et al, Distributed Data Management, 1997.
`
`• cited by examiner
`
`HP_1003_0005
`
`

`
`U.S. Patent
`
`Oct. 13, 2009
`
`Sheet 1 of 6
`
`US 7,603,674 B2
`
`,...
`e ;::,
`
`.~
`1..1.:
`
`~
`s
`8
`
`J
`
`II.
`
`II.
`
`I
`i
`
`<
`
`< I
`
`ID
`
`ID
`
`jJ I·
`!)
`
`II
`
`~~ J
`!HI
`
`UJ
`
`I
`I jH I
`
`HP_1003_0006
`
`

`
`U.S. Patent
`
`Oct. 13, 2009
`
`Sheet 2 of 6
`
`US 7,603,674 B2
`
`o-----.
`
`0
`
`....
`
`I
`
`II
`l I
`1)
`l r
`II :I
`l I
`Jl
`l
`~~
`~
`l
`J)J}
`l
`IJJ ""
`r
`I m r - - -1 - - - ___ ,
`
`u.
`
`w
`
`c
`
`CJ
`
`w
`
`c
`
`CJ
`
`1111
`
`1111
`
`<
`
`HP_1003_0007
`
`

`
`U.S. Patent
`
`Oct. 13, 2009
`
`Sheet 3 of6
`
`US 7,603,674 B2
`
`Summary Of Orders
`
`Your Information
`
`Company
`Dow Chemical
`
`Location
`Midland, MJ
`
`Current Orders. Quotes. and lnguldas
`
`Data
`3/2712000
`312912000
`313112000
`
`Transaction ID
`0003
`2102
`2204
`
`Older Numba'
`800000
`839400
`940302
`
`Current Status
`INVOICE
`MANUFACTURE
`ORDER
`
`Figure 3
`
`HP_1003_0008
`
`

`
`U.S. Patent
`
`Oct. 13, 2009
`
`Sheet 4 of6
`
`US 7,603,674 B2
`
`Order History and Traddng lnfonnalion
`111qa1rr CRIIllliiC41S&!m a 1t1&
`YClat Jnfauaaloo
`
`:
`
`Caqr&y
`Dow~
`-
`ClnWil Ordrlr stllua ·li,....dllai Glw:iiOIVDOnlllr(cid:173)
`
`EIJNVOICE
`
`Qrdct !\ctrft
`
`~ IJOOD3
`
`Jlallldll... llaf:lllflal.le" UDIIt ollleuallt Qllalilr
`Order....,
`
`BOX
`
`1
`
`Milt Ed
`2JJJ
`
`IWllJIRY
`?e.
`............
`¥.ilt3D) Zt:C» 2IJIDG1
`
`1hl Pll:a....MII IdS•
`
`-
`::::=-
`IIAHUFACTURE
`.f" 0.
`
`--~~~~~~,~~~4~a~o----~~~--- •
`SHJP
`. . . . . . . . . . . 1'181:11:111J .....
`.... 0.
`3l:l1l2lm 2taJ UPS
`1Zt5DSS 11!1»13
`
`Figure 4
`
`HP_1003_0009
`
`

`
`U.S. Patent
`
`Oct. 13, 2009
`
`Sheet 5 of6
`
`US 7,603,674 B2
`
`Figure5
`
`HP_1003_0010
`
`

`
`U.S. Patent
`
`Oct. 13, 2009
`
`Sheet 6 of6
`
`US 7,603,674 B2
`
`Figure 6
`
`Figure 7
`
`Figure 8
`
`Figure 9
`
`Figure 10
`
`HP_1003_0011
`
`

`
`US 7,603,674 B2
`
`1
`APPARATUS At.~D SYSTEMS FOR
`MEASURING, MONITORING, TRACKING
`AND SIMULATING ENTERPRISE
`COMMUNICATIONS AND PROCESSES
`
`CROSS REFERENCE TO RELAJED
`APPLICATION
`
`This application is a continuation of and claims the benefit
`of U.S. patent application Ser. No. 091737,494 filed Dec. 15,
`2000, entitled Apparatus and Methods for Isolating and
`Reviewing Data from Multiple Sources, now issued U.S. Pat.
`No. 7,062,749.
`The present invention relates to apparatus and systems for
`measuring, monitoring, tracking and simulating enterprise
`communications and processes. More particularly, the
`present invention relates to computer-based apparatus and
`systems for measuring, monitoring, tracking and simulating
`enterprise communications and processes in an asynchronous
`messaging environment.
`
`BACKGROUND OF THE INVENTION
`
`The activities of a business or enterprise can be grouped
`into processes. Processes are business operations that are 2s
`separated as desired and usually occur across business units.
`For example, the process of taking orders and turning those
`orders into revenue may be known as Order to Cash. The
`processes are comprised of sub-processes. For example,
`Order to Cash may be broken down into sub-processes such 30
`as Receive Order Inquiry, Provide Customer Quotation, Cre-
`ate Customer Outline Agreement, Create Sales Order, Sched(cid:173)
`ule Production, Manufacture Product, Ship Product and
`Invoice Customer. Each sub-process may in turn be broken
`down into discrete activities such as providing customer num- 35
`her, entering that customer number, establishing pricing,
`determining a shipping date, etc.
`The processes, sub-processes and activities operate, in
`part, by communicating information. For example, users may
`communicate through etnail. As another example, applica- 40
`tions may communicate amongst themselves through elec(cid:173)
`tronic data interchange ("EDI") and other similar services.
`Communication occurs horizontally, that is, among a process,
`sub-process and activities, as well as vertically, that is,
`between processes, sub-processes and activities.
`Whether communications occur horizontally or vertically,
`among applications or users, communications are increas(cid:173)
`ingly asynchronous or message based. That is, enterprise
`communications were formerly primarily synchronous, or
`connection oriented, in which a connection is established so
`with prior coordination between communication end points
`with data then being transmitted over the connection. Enter(cid:173)
`prise communications are now increasingly asynchronous, or
`connectionless, transmitting data without prior coordination
`between communication end points, such as through "event ss
`based" communications which use messages to move data
`instead of large files.
`Asynchronous or message based communications permit
`loosely coupled connections among and between systems
`because the end points do not have to be prepared to receive 60
`the data when the message is transmitted. Loosely coupled
`connections permit more flexibility in assembling processes.
`Flexibility in assembling processes is desirable in order to
`permit quick reaction to changing business conditions: if a
`particular sub-process or activity becomes unusable, the pro- 65
`cess can be reassembled with a new sub-process or activity.
`For example, if a Manufacture Product sub-process in the
`
`2
`Order to Cash process at Widget Co. enterprise has a specific
`factory identified to manufacture the product and that factory
`has a fire or other disaster, making it unusable, Widget Co.
`will need to substitute a new factory. The ripple effect of that
`substitution among all of Widget Co.'s processes will change
`any number of parameters. A loosely coupled asynchronous
`connection among Widget Co.'s processes provides rapid
`substitution of the new factory for the old because the end
`points of communication to the new factory do not have to be
`10 predetermined before communications begin with the new
`factory. Thus, the flexibility of the asynchronous message
`based communication has permitted quick response to chang·
`ing business conditions.
`Despite this flexibility, asynchronous or message based
`15 communications are problematic because of their loosely
`coupled nature. At any given time, precise information on the
`progress of the processes is difficult to obta.in:-messages
`may be in transit and not instantly locatable. For example, if
`a customer calls for the status of an order, an enterprise
`20 customer service representative may be able to determine
`nothing more than the fact that the order has been received
`and that the scheduled ship date is X. There is often no ability
`to drill down into the information levels and review the status
`in more granularity, such as the location of the good, the
`manufacturing status, etc., because the information required
`to review that status is in transit and unable to be reviewed.
`Of course, if the enterprise lacks the ability to access status
`information, business partners of the enterprise will similarly
`lack that ability. Thus, asynchronous communications may
`well increase inefficiency among business partners as well.
`The difficulty in reporting caused by message based archi •
`tecture also makes it difficult for the enterprise to measure the
`efficiency of its processes and their sub-process. Asynchro·
`nous messaging, with its indeterminate transmission of infor·
`mation, means a company may not be able to easily measure
`the interval between each sub-process, e.g. the time between
`Scheduling Production and the Manufacturing of a Product,
`and so easily measure the efficiency of their operations.
`Finally, asynchronous messaging may provide an enter-
`prise with an ability to model and simulate processes. That is,
`since information flows can be readily estimated through
`enterprises with asynchronous messaging, and processes can
`be easily modeled from those flows, asynchronous messaging
`modeling provides the potential to model and simulate pro-
`45 cesses. That potential is not realized with present technology,
`however. Moreover, since as described above, enterprises
`lackinfurmation on the processes they have implemented, the
`enterprises are handicapped in their ability to modify those
`processes or plan new processes. A modeling and simulation
`tool, demonstrating processes, sub-processes and their activ(cid:173)
`ity or granular detail level would be extremely helpful, and
`would give the enterprise an opportunity to assemble, test,
`adjust, and simulate processes and their details.
`Accordingly, it is an object of the present invention to
`provide a tool for simulating message based architectures.
`It is a further object of the present invention to. provide
`monitoring capabilities for enterprise processes.
`
`BRIEF DESCRIPTION OF TilE DRAWINGS
`
`FIG. 1 shows a view of a process.
`FIG. 2 shows a view of a process of a preferred embodi-
`ment.
`FIG. 3 shows a screen of a preferred embodiment.
`FIG. 4 shows a screen of a preferred embodiment.
`FIG. S shows a screen of a preferred embodiment.
`FIG. 6 shows a partial view of a preferred embodiment.
`
`HP_1003_0012
`
`

`
`us 7,603,674 82
`
`3
`FIG. 7 shows a partial view of a preferred embodiment.
`FIG. 8 shows a partial view of a preferred embodiment.
`FIG. 9 shows a partial view of a preferred embodiment.
`FIG.10 shows a partial view of a preferred embodiment.
`
`S~YOFTHEThNENTION
`
`=
`
`4
`saging broker. For example, IBM's MQSeries messaging
`broker provides a component that can be configured to per(cid:173)
`form a copying function for the messages it receives, and so
`create monitoring messages for the messages it receives.
`The specific data contained in the monitoring messages (in
`this embodiment, this data is copied from the original mes(cid:173)
`sages passing between the sub-processes) is organized into
`data fields. Those data fields are path specific in this embodi(cid:173)
`ment. For example, assume a customer calls the enterprise
`(Widget Co.) whose process is shown in FIG. 1 and asks
`whether or not Widget Co. has a certain product (fype A
`Widgets.) That customer request will begin the Receive Order
`Inquiry sub-process which will end with the generation of a
`Receive Order Inquiry message traveling to the Provide Cus(cid:173)
`tomer Quotation sub-process through the messaging broker
`component. When the messaging broker receives the message
`on Path A, it will create a monitoring message, and send the
`monitoring message to the central database repository, as
`shown in FIG.l.ln this embodiment, the data contained in the
`monitoring message is generated from the message on Path A.
`Other preferred embodiments may alter or add data to the
`monitoring messages aside from that contained in the original
`message.
`The monitoring message contains, in this embodiment,
`specific data fields. (Of course, other embodiments may have
`different ~ta fields.) Those data fields are:
`
`The present invention comprises apparatus and systems for
`measuring, monitoring, tracking and simulating enterprise
`communications and processes in an asynchronous messag- 10
`ing environment. For each original message sent within a
`process, sub-process or activity, the preferred embodiments
`of the present invention send a separate monitoring message
`containing data from the central message repository or data(cid:173)
`base. This data may include date, time, customer number, IS
`materials, quantity, amount, or other infonnation, and be
`copied from the original message. Other embodiments may
`add data to the monitoring message aside from that contained
`in the original message.
`This centtal message repository or database is comprised 20
`of infonnation passing through the enterprise. In effect, the
`database provides a collection point or an "end point" for the
`asynchronous communications, and so allows the flexibility
`of asynchronous communications to be combined with the
`precision of synchronous communications. The database can 25
`be reviewed in any number of ways. For example, the data(cid:173)
`base can be queried to obtain specific information about that
`particular order or customer or could be examined across
`larger time spans such as days, weeks, or months, to gauge
`trends or performance. Of course, some preferred embodi- 30
`FIELDS
`IDENTIFIERS
`ments may wish to create mirror databases or other databases ___ P_ROC_E_s_s_to_ENTIFtE ___ R. _____ Pro-ID-, - - - - -
`that can be used in various ways.
`SUB-PROCESS IDENTIFtER
`SbProto,
`An enterprise's information flow can also be readily mod·
`eustno,
`CUSTOMER NUMBER
`eledand simulated through creating new process, sub-process
`PART NUMBER
`Partno,
`and/or activities or altering existing process, sub-process or 35 ~~
`Qty,
`activities. The infonnation flows from those creations or
`TIME
`alterations can be collected in one or more databases and
`examined as desired.
`
`DETAILED DESCRIPTION OF THE PREFERRED
`EMBODIMENTS
`
`FIG. 1 shows a sample process, Order to Cash, which is
`comprised of various sub-processes: Receive Order Inquiry,
`Provide Customer Quotation, Create Customer Outline 45
`Agreement, Create Sales Order, Schedule Production, Manu(cid:173)
`facture Product, Ship Product and Invoice Customer. The
`dashed line arrows connecting the sub-processes are the com(cid:173)
`munication paths between the sub-processes. In the example
`shown in the figure, the sub-processes actually communicate so
`through a messaging broker, such as an IBM MQSeries com(cid:173)
`ponent, and the paths to and from the component are identi(cid:173)
`fied identically. This messaging broker permits certain
`sophisticated messaging uses, such as message queuing,
`some data translation, etc.
`A messaging component is added to the messaging broker,
`through methods known in the art. This messaging compo(cid:173)
`nent creates a "monitoring"' message for each original mes(cid:173)
`sage received by the broker. This monitoring message con(cid:173)
`tains, in this embodiment, specific data generated from the 60
`original messages passing between the sub-processes. The
`monitoring message with its data is then sent from the mes·
`saging broker to a central database repository or database (the
`terms "repository" or "database" are used interchangeably
`throughout.)
`The messaging component may be, in some embodiments,
`or may not be, in other embodiments, provided by the mes·
`
`The first field, the PROCESS IDENTIFIER field, provides
`40 the identifier for the process, for example, the value "Order to
`Cash" because the monitoring message is being created
`within the Order to Cash process. The second field, the SUB(cid:173)
`PROCESS IDENTIFIER field, provides the identifier for the
`sub-process, for example, the value "Inquiry" because the
`monitoring message is being created within the Inquiry sub(cid:173)
`process. This embodiment prepopulates these PROCESS
`IDENTIFIER and SUB-PROCESS IDENTIFIER fields, with
`the appropriate values.
`The CUSTOMER NUMBER field is assigned to the par(cid:173)
`ticular customer generating the inquiry. The PART NUM(cid:173)
`BER field is the identifier for the particular part and the
`QUANTITY for the particular quantity. DATE and TIME are
`the data and time the message is generated. Other message
`fields for other paths of this embodiment are shown in Table
`ss l. Of course, some, all or none of these fields may be present
`in other embodiments, as well as other fields as desired. For
`example, one or more ACTIVITY IDENTIFIER fields may
`be present in monitoring messages in other embodiments.
`The monitoring message data populates one infonnation
`flow or transaction reconi ("transaction record.") As monitor(cid:173)
`ing messages progress through any given process and/or sub(cid:173)
`process, the transaction reconi is updated. Once the monitor(cid:173)
`ing messages complete the transaction record, all of the
`infonnation needed to measure that transaction through the
`6S process is contained in one reconi in the central message
`database. (Of course, if the monitoring messages do not fully
`populate the transaction record, e.g., the transaction is
`
`HP_1003_0013
`
`

`
`US 7,603,674 B2
`
`5
`aborted in mid process, then these abandoned records may be
`made available as well with an indication that they were
`abandoned.)
`The central message database can be reviewed in any num(cid:173)
`ber of ways, in order to measure, monitor and track enterprise
`communications and processes, e.g., to provide information
`or generate reports. Using the central message database to
`provide information or generate reports "off loads" the infor(cid:173)
`mation access or reporting processes from the applications
`that generate messages initially, e.g., sub-processes such as 10
`those seen in FIG. 1. This off loading relieves some of the
`monitoring pressure from the source applications so that, for
`example, any queries that might have been made to the source
`applications and interfere with or slow down the operation of
`the soun::e applications can now be made through the central 15
`message database.
`The information retrieved from the central message data(cid:173)
`base may include, but is not limited to, information about any
`particular order or customer, infonnation about process effi(cid:173)
`ciency, "snapshot" or time slice information, information 20
`across time spans such as days, weeks, or months, informa(cid:173)
`tion to gauge trends or perfonnance, etc. Also, in some
`embodiments, a "real-time" tool may be used to track the
`progress of transaction records and/or processes and use dis(cid:173)
`tribution methods such as broadcasting, WAP, etc. to provide 25
`the information to users. For example, if a process such as
`pipeline capacity for oil and natural gas transmissions is
`implemented and monitored through an embodiment of the
`present invention, the central message database will con(cid:173)
`stantly broadcast unused pipeline capacity, which informa- 30
`tion in turn can be used to sell, trade or barter that unused
`capacity. As another example, information about an enter(cid:173)
`prise's processes can be made available over an intranet,
`extranet, the Internet, etc. to business partners or other enti(cid:173)
`ties. One example would be providing information to stock 35
`analysts so that they could track any particular enterprise's
`productivity or other areas of interest Another example
`would be providing information to actual or potential busi(cid:173)
`ness partners to check production capacity, shipping capacity,
`or other areas of interest. In some embodiments, with regard 40
`to external entities, communication channels between the
`external entities and the enterprise might well be established,
`so that central message databases exist on both ends of the
`communication channel.
`The central message database allows for broader analysis 45
`of trends that may include: time between sub-processes, vari(cid:173)
`ances by customer, variances by order amount, bottlenecks in
`the process, etc. For example, it would be possible to deter(cid:173)
`mine how many orders stood between Order and Invoice. This
`may allow for the acceleration of some orders so they could be so
`booked by quarter close. For example, a vendor bottleneck
`may be identified in the course of review of the processes,
`sub-processes and/or activities. For example, seasonal varia(cid:173)
`tions in processes, sub-processes and/or activities may be
`identified as well.
`Of course, some embodiments may create mirror databases
`and/or generate other databases that can be used by various
`entities. For example, an enterprise may create a number of
`central message databases which could track processes, sub(cid:173)
`processes and/or activities in whole or part. These databases 60
`could also be combined as desired
`Monitoring message database(s) may be used, in some
`embodiments, in various ways, either in addition to or instead
`of central message database(s.) For example, a monitoring
`message database or a central message database may be used 65
`to generate messages and feedback to the processes, sub(cid:173)
`processes, activities and/or applications, as well as to users
`
`6
`and/or administrators (herein generally "users.") Various
`messages transmitted from sub-process applications such as
`error messages would generate special monitoring messages
`which would be added to a message monitoring database.
`Other events, exceptions, triggers and thresholds, could be
`tracked as well in various embodiments and be used to signal
`conditions, problems, etc. by various methods such as
`"flagged" or specially designated messages or other indica(cid:173)
`tors.
`Access to the database( s) is, in the preferred embodiments,
`on a secured or authorized basis, with different users obtain(cid:173)
`ing different levels of access to the data in the database.
`FIG. 3 shows a screen shot of an example of a preferred
`embodiment where access was made available to a customer
`over a corporate extranet. The screen shot is of a report,
`generated through an XML link to the central message data-
`base, of that particular customer's orders. In the preferred
`embodiments, the customer has the option to "drill down"
`through this screen to other screens for further detail. So, for
`example, FIG. 4 shows a result of one such operation, where
`the customer had drilled down from the screen of FIG. 3. Of
`course, these records may vary depending on the status of the
`transaction, that is, whether the transaction is in the middle of
`the process, at the beginning of the process, etc. Furthermore,
`other reporting options may be seen depend