Support for real-time queries concerning current state, data and history of a process

• US 20030225769A1
• Filed: 05/31/2002
• Published: 12/04/2003
• Est. Priority Date: 05/31/2002
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Jason, Zach, Ng, Andrew, Chkodrov, Gueorgui, Chao, Lucy, Clark, Wayne A., Yildirim, Tolga
• Granted Patent: US 7,571,187 B2
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: Y10S 707/947 Human resources
• CPC Class Codes: Y10S 707/956 Hierarchical
• CPC Class Codes: Y10S 707/958 Data cubes
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A computer-implemented method is provided for defining interesting portions of a workflow of a business or other type of process. Using a tracking profile editor, a portion of a given workflow is selected and associated with a named process part. Items of payload data to be used in reports are selected from a message schema associated with the given workflow. A profile is generated based on the given workflow and the selected items of payload data. A tracking profile compiler receives the created tracking profile and generates a star schema, a flattened view and OLAP cube based on the tracking profile. An interceptor extracts monitored workflow events and stores event information to a tracking stream, based on the tracking profile. A tracking service extracts information pertaining to the monitored events from the tracking stream and stores the information in the queryable database. The OLAP cube and the flattened view are updated based on the information written to the queryable database.

Claims

1. A method of establishing a tracking profile for selective monitoring and reporting of process state data pertaining to a displayed workflow representation of a process, comprising:

selecting at least one portion of the displayed workflow representation and associating the selected portion(s) with respective process part labels; and

generating a tracking profile based on the selected workflow representation portion(s), said profile establishing parameters for monitoring and writing to a queryable database process state data pertaining to instances of said process represented within said displayed workflow representation.

2. The method of claim 1, further comprising displaying a hierarchical representation of said process part labels, corresponding to a hierarchy of said selected workflow representation portions.

3. The method of claim 1, wherein said selecting of displayed workflow representation portions comprises selecting a parent workflow representation portion and a child workflow representation portion within said parent workflow representation portion.

4. The method of claim 1, further comprising compiling said tracking profile to generate a corresponding database schema.

5. The method of claim 1, further comprising compiling said tracking profile to generate a configuration for selectively monitoring process state data pertaining to instances of said processes.

6. The method of claim 1, further comprising compiling said tracking profile to generate a plurality of stored procedures utilized in monitoring and writing to said queryable database process state data pertaining to instances of said process.

7. The method of claim 6 wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating an end time of said process instance, and for setting a process completed state indicator for said instance.

8. The method of claim 6, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and for setting a process part running state indicator for said instance.

9. The method of claim 8, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and for setting a process part completed state indicator for said instance.

10. The method of claim 6, wherein said stored procedures comprise a stored procedure for establishing in said database a fact record for each new process instance.

11. The method of claim 4, wherein said database schema comprises a flattened view.

12. The method of claim 4, wherein said database schema comprises a star-schema.

13. The method of claim 4, wherein said database schema comprises an OLAP cube.

14. A method of establishing a tracking profile for selective monitoring and reporting of process state and payload data pertaining to a displayed workflow representation of a process, comprising:

selecting at least one portion of the displayed workflow representation and associating the selected portion(s) with respective process part labels;

selecting items of payload data to be used in reports, the items of payload data being selected from a message schema associated with the displayed workflow representation; and

generating a tracking profile based on the selected workflow representation portion(s) and the selected items of payload data, said profile establishing parameters for monitoring and writing to a queryable database payload and process state data pertaining to instances of said process represented within said displayed workflow representation.

15. The method of claim 14, further comprising associating at least one of the selected items of payload data with a label differing from the label of said item appearing in said displayed workflow representation.

16. The method of claim 14, further comprising displaying a hierarchical representation of said process part labels, corresponding to a hierarchy of said selected workflow representation portions.

17. The method of claim 14, wherein said selecting of displayed workflow representation portions comprises selecting a parent workflow representation portion and a child workflow representation portion within said parent workflow representation portion.

18. The method of claim 14, further comprising displaying a hierarchical representation of said message schema, from which selections of payload data items can be made.

19. The method of claim 18, further comprising displaying a hierarchical representation of the selected payload data items.

20. The method of claim 19, wherein the hierarchical representation of the selected payload data items differs from the hierarchy of the items as they appear in said hierarchical representation of said message schema.

21. The method of claim 14, further comprising compiling said tracking profile to generate a corresponding database schema.

22. The method of claim 14, wherein said message schema is an XML message schema.

23. The method of claim 14, further comprising compiling said tracking profile to generate a configuration for selectively monitoring process state and payload data pertaining to instances of said processes.

24. The method of claim 14, further comprising compiling said tracking profile to generate a plurality of stored procedures utilized in monitoring and writing to said queryable database payload and process state data pertaining to instances of said process.

25. The method of claim 24 wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating an end time of said process instance, and for setting a process completed state indicator for said instance.

26. The method of claim 24, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and for setting a process part running state indicator for said instance.

27. The method of claim 26, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and for setting a process part completed state indicator for said instance.

28. The method of claim 24, wherein said stored procedures comprise a stored procedure for establishing in said database a fact record for each new process instance.

29. The method of claim 28, wherein said stored procedures comprise a stored procedure for writing to said database payload data for each new process instance, in linking relationship with the respective fact record.

30. The method of claim 21, wherein said database schema compares a flattened view.

31. The method of claim 21, wherein said database schema comprises a star-schema.

32. The method of claim 21, wherein said database schema comprises an OLAP cube.

33. A machine readable medium having instructions recorded thereon which, when executed by a data processing device, configure said device:

to permit a user to select, with at least one input device, at least one portion of a displayed workflow representation, and to associate the selected portion(s) with respective process part labels; and

to generate a tracking profile based on the selected workflow representation portion(s), said profile establishing parameters for monitoring and writing to a queryable database process state data pertaining to instances of said process.

34. A machine readable medium having instructions recorded thereon which, when executed by a data processing device, configure said device:

to permit a user to select, with at least one input device, at least one portion of a displayed workflow representation, and to associate the selected portion(s) with respective process part labels;

to permit a user to select, with said at least one input device, items of payload data to be used in reports, from a message schema associated with the displayed workflow representation; and

to generate a tracking profile based on the selected workflow representation portion(s) and the selected items of payload data, said profile establishing parameters for monitoring and writing to a queryable database payload and process state data pertaining to instances of said process.

35. A data processing apparatus for establishing a tracking profile for selective monitoring and reporting of process state data pertaining to a displayed workflow representation of a process comprising:

at least one data storage device having stored thereon a workflow representation of a process;

a display for displaying said workflow representation;

at least one user input device; and

a processor operatively connected to said storage device(s), said display and said user input device;

wherein the at least one data storage device has stored thereon on a set of instructions which, when executed, configure said processor;

to permit a user to select, with said at least one input device, at least one portion of the displayed workflow representation, and to associate the selected portion(s) with receptive process part labels; and

to generate a tracking profile based on the selected workflow representation portion(s), said profile establishing parameters for monitoring and writing to a queryable database process state data pertaining to instances of said process.

36. The apparatus of claim 35, wherein said instructions, when executed, further configure said processor to display a hierarchical representation of said process part labels, corresponding to a hierarchy of said selected workflow representation portions.

37. The apparatus of claim 35, wherein the permitted selecting of displayed workflow representation portions comprises selecting a parent workflow representation portion and a child workflow representation portion within said parent workflow representation portion.

38. The apparatus of claim 35, wherein said instructions, when executed, further configure said processor to compile said tracking profile to generate a corresponding database schema.

39. The apparatus of claim 35, wherein said instructions, when executed, further configure said processor to compile said tracking profile to generate a configuration for selectively monitoring process state data pertaining to instances of said process.

40. The apparatus of claim 35, wherein said instructions, when executed, further configure said processor to compile said tracking profile to generate a plurality of stored procedures utilized in monitoring and writing to said queryable database process state data pertaining to instances of said process.

41. The apparatus of claim 35, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a start time of said process instance, and for setting a process running state indicator for said instance.

42. The apparatus of claim 41 wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating an end time of said process instance, and for setting a process completed state indicator for said instance.

43. The apparatus of claim 40, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and for setting a process part running state indicator for said instance.

44. The apparatus of claim 43, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and for setting a process part completed state indicator for said instance.

45. The apparatus of claim 40, wherein said stored procedures comprise a stored procedure for establishing in said database a fact record for each new process instance.

46. The apparatus of claim 45, wherein said stored procedures comprise a stored procedure for writing to said database payload data for each new process instance, in linking relationship with the respective fact record.

47. The apparatus of claim 38, wherein said database schema compares a flattened view.

48. The apparatus of claim 38, wherein said database schema comprises a star-schema.

49. The apparatus of claim 38, wherein said database schema comprises an OLAP cube.

50. A data processing apparatus for establishing a tracking profile for selective monitoring and reporting of process state and payload data pertaining to a displayed workflow representation of a process comprising:

at least one data storage device having stored thereon a workflow representation of a process;

a display for displaying said workflow representation;

at least one user input device; and

a processor operatively connected to said storage device(s), said display and said user input device;

wherein the at least one data storage device has stored thereon on a set of instructions which, when executed, configure said processor;

to permit a user to select, with said at least one input device, at least one portion of the displayed workflow representation, and to associate the selected portion(s) with receptive process part labels;

to permit a user to select, with said at least one input device, items of payload data to be used in reports, from a message schema associated with the displayed workflow representation; and

to generate a tracking profile based on the selected workflow representation portion(s) and the selected items of payload data, said profile establishing parameters for monitoring and writing to a queryable database payload and process state data pertaining to instances of said process.

51. The apparatus of claim 50, wherein said instructions, when executed, further configure said processor to permit a user to associate at least one of the selected items of payload data with a label differing from the label of said item appearing in said displayed workflow representation.

52. The apparatus of claim 50, wherein said instructions, when executed, further configure said processor to display a hierarchical representation of said process part labels, corresponding to a hierarchy of said selected workflow representation portions.

53. The apparatus of claim 50, wherein the permitted selecting of displayed workflow representation portions comprises selecting a parent workflow representation portion and a child workflow representation portion within said parent workflow representation portion.

54. The apparatus of claim 50, wherein said instructions, when executed, further configure said processor to display a hierarchical representation of said message schema, from which selections of payload data items can be made.

55. The apparatus of claim 54, wherein said instructions, when executed, further configure said processor to display a hierarchical representation of the selected payload data items.

56. The apparatus of claim 55, wherein the hierarchical representation of the selected payload data items differs from the hierarchy of the items as they appear in said hierarchical representation of said message schema.

57. The apparatus of claim 50, wherein said instructions, when executed, further configure said processor to compile said tracking profile to generate a corresponding database schema.

58. The apparatus of claim 50, wherein said message schema is an XML message schema.

59. The apparatus of claim 50, wherein said instructions, when executed, further configure said processor to compile said tracking profile to generate a configuration for selectively monitoring process state and payload data pertaining to instances of said process.

60. The apparatus of claim 50, wherein said instructions, when executed, further configure said processor to compile said tracking profile to generate a plurality of stored procedures utilized in monitoring and writing to said queryable database payload and process state data pertaining to instances of said process.

61. The apparatus of claim 60 wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a start time of said process instance, and for setting a process running state indicator for said instance.

62. The apparatus of claim 61 wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating an end time of said process instance, and for setting a process completed state indicator for said instance.

63. The apparatus of claim 60, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and for setting a process part running state indicator for said instance.

64. The apparatus of claim 63, wherein said stored procedures comprise a stored procedure for writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and for setting a process part completed state indicator for said instance.

65. The apparatus of claim 60, wherein said stored procedures comprise a stored procedure for establishing in said database a fact record for each new process instance.

66. The apparatus of claim 65, wherein said stored procedures comprise a stored procedure for writing to said database payload data for each new process instance, in linking relationship with the respective fact record.

67. The apparatus of claim 57, wherein said database schema compares a flattened view.

68. The apparatus of claim 57, wherein said database schema comprises a star-schema.

69. The apparatus of claim 57, wherein said database schema comprises an OLAP cube.

70. A data processing system for monitoring and reporting process state data pertaining to instances of a process represented within a stored workflow representation, comprising:

at least one data storage device having stored thereon;

said workflow representation; and

a queryable database, said database having a schema established based upon a tracking profile, said tracking profile being based on one or more selected portions of the stored workflow representation;

monitoring means for monitoring process state data pertaining to instances of said process, within parameters established by said tracking profile, and for writing said process state data to said database in accordance with the database schema; and

reporting means for selectively reporting process state data written to said database, in accordance with parameters established by said tracking profile.

71. The system of claim 70, wherein the database schema comprises a flattened view.

72. The system of claim 70, wherein the database schema comprises a star-schema.

73. The system of claim 70, wherein the database schema comprises an OLAP cube.

74. The system of claim 70, wherein the monitoring means comprises a stored procedure for writing to said database a timestamp indicating a start time of a process instance, and setting a running process state indicator for said instance.

75. The system of claim 74, wherein the monitoring means comprises a stored procedure for writing to said database a timestamp indicating an end time of said process instance, and for setting a process completed state indicator for said instance.

76. The system of claim 70, wherein the monitoring means further comprises a stored procedure for writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and for setting a process part running state indicator for said instance.

77. The system of claim 76, wherein the monitoring means further comprises a stored procedure for writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and for setting a process part completed state indicator for said instance.

78. The system of claim 70, wherein the monitoring means comprises a stored procedure for establishing in said database a fact record for each new process instance.

79. The system of claim 70, wherein said reporting means is further arranged to automatically determine whether data in the queryable database satisfies a predefined condition, and when said data in the queryable database satisfies said predefined condition, said reporting means is arranged to automatically perform a predefined action.

80. The system of claim 79, wherein the predefined action comprises sending an email.

81. The system of claim 79, wherein the predefined action comprises automatically generating a report and distributing the report over a network.

82. The system of claim 79, wherein said predefined condition comprises a defined trend.

83. A data processing system for monitoring and reporting payload and process state data pertaining to instances of a process represented within a stored workflow representation, comprising:

at least one data storage device having stored thereon;

said workflow representation; and

a queryable database, said database having a schema established based upon a tracking profile, said tracking profile being based on one or more selected portions of the stored workflow representation and items of payload data selected from a message schema associated with the stored workflow representation;

monitoring means for monitoring process state and payload data pertaining to instances of said process, within parameters established by said tracking profile, and for writing said process state and payload data to said database in accordance with the database schema; and

reporting means for selectively reporting process state and payload data written to said database, in accordance with parameters established by said tracking profile.

84. The system of claim 83, wherein the database schema comprises a flattened view.

85. The system of claim 83, wherein the database schema comprises a star-schema.

86. The system of claim 83, wherein the database schema comprises an OLAP cube.

87. The system of claim 83, wherein the monitoring means comprises a stored procedure for writing to said database a timestamp indicating a start time of a process instance, and setting a running process state indicator for said instance.

88. The system of claim 87, wherein the monitoring means comprises a stored procedure for writing to said database a timestamp indicating an end time of said process instance, and for setting a process completed state indicator for said instance.

89. The system of claim 83, wherein the monitoring means further comprises a stored procedure for writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and for setting a process part running state indicator for said instance.

90. The system of claim 89, wherein the monitoring means further comprises a stored procedure for writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and for setting a process part completed state indicator for said instance.

91. The system of claim 83, wherein the monitoring means comprises a stored procedure for establishing in said database a fact record for each new process instance.

92. The system of claim 91, wherein the monitoring means further comprises a stored procedure for writing to said database payload data for each new process instance, in linking relationship with the respective fact record.

93. The system of claim 83, wherein said reporting means is arranged to display a snapshot of an OLAP cube including selected portions of said process state and payload data written to said database.

94. The system of claim 93, wherein said reporting means is further arranged to display additional portions of said payload data and said process state data in response to a user interaction with the displayed snapshot of the OLAP cube.

95. The system of claim 93, wherein said reporting means is further arranged to display details of an item of the payload data in response to a user interaction with a displayed hierarchical representation of types of the payload data.

96. The system of claim 93, wherein said reporting means is farther arranged to permit a user to change a displayed dimension of the snapshot of the OLAP cube, to cause said reporting means to display different information.

97. The system of claim 93, wherein said reporting means is further arranged to permit a user to change a displayed measure of the snapshot of the OLAP cube, to cause said reporting means to display different information.

98. The system of claim 93, wherein said reporting means is further arranged to permit filtering of displayed data of the snapshot of the OLAP cube in response to a user interaction with the snapshot of the OLAP cube.

99. The system of claim 83, wherein said reporting means is further arranged to generate a report based on a query that combines said process state data with said payload data.

100. The system of claim 83, wherein said reporting means is further arranged to automatically determine whether data in the queryable database satisfies a predefined condition, and when said data in the queryable database satisfies said predefined condition, said reporting means is arranged to automatically perform a predefined action.

101. The system of claim 100, wherein the predefined action comprises sending an email.

102. The system of claim 100, wherein the predefined action comprises automatically generating a report and distributing the report over a network.

103. The system of claim 100, wherein said predefined condition comprises a defined trend.

104. A method for monitoring and reporting process state data pertaining to instances of a process represented within a stored workflow representation, utilizing a data processing system including at least one data storage device having stored thereon said workflow representation and a queryable database, said database having a schema established based upon a tracking profile, said tracking profile being based on one or more selected portions of the stored workflow representation, said method comprising:

monitoring process state data pertaining to instances of said process, within parameters established by said tracking profile, and writing said process state to said database in accordance with the database schema; and

selectively reporting the process state data written to said database, in accordance with parameters established by said tracking profile.

105. The method of claim 104, wherein the database schema comprises a flattened view.

106. The method of claim 104, wherein the database schema comprises a star-schema.

107. The method of claim 104, wherein the database schema comprises an OLAP cube.

108. The method of claim 104, wherein the monitoring comprises writing to said database a timestamp indicating a start time of a process instance, and setting a running process state indicator for said instance.

109. The method of claim 108, wherein the monitoring comprises writing to said database a timestamp indicating an end time of said process instance, and setting a process completed state indicator for said instance.

110. The method of claim 104, wherein the monitoring further comprises writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and setting a process part running state indicator for said instance.

111. The method of claim 110, wherein the monitoring further comprises writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and setting a process part completed state indicator for said instance.

112. The method of claim 104, wherein the monitoring comprises establishing in said database a fact record for each new process instance.

113. The method of claim 104, wherein said reporting of process state data further comprises automatically determining whether data in the queryable database satisfies a predefined condition, and when said data in the queryable database satisfies said predefined condition, automatically performing a predefined action.

114. The method of claim 113, wherein the predefined action comprises sending an email.

115. The method of claim 113, wherein the predefined action comprises automatically generating a report and distributing the report over a network.

116. The method of claim 113, wherein said predefined condition comprises a defined trend.

117. A method for monitoring and reporting process state and payload data pertaining to instances of a process represented within a stored workflow representation, utilizing a data processing system including at least one data storage device having stored thereon said workflow representation and a queryable database, said database having a schema established based upon a tracking profile, said tracking profile being based on one or more selected portions of the stored workflow representation and items of payload data selected from a message schema associated with the stored workflow representation, said method comprising:

monitoring process state and payload data pertaining to instances of said process, within parameters established by said tracking profile, and writing said process state and payload data to said database in accordance with the database schema; and

selectively reporting the process state and payload data written to said database, in accordance with parameters established by said tracking profile.

118. The method of claim 117, wherein the database schema comprises a flattened view.

119. The method of claim 117, wherein the database schema comprises a star-schema.

120. The method of claim 117, wherein the database schema comprises an OLAP cube.

121. The method of claim 117, wherein the monitoring comprises writing to said database a timestamp indicating a start time of a process instance, and setting a running process state indicator for said instance.

122. The method of claim 121, wherein the monitoring comprises writing to said database a timestamp indicating an end time of said process instance, and setting a process completed state indicator for said instance.

123. The method of claim 117, wherein the monitoring further comprises writing to said database a timestamp indicating a time of entry of a process instance into a selected process part, and setting a process part running state indicator for said instance.

124. The method of claim 123, wherein the monitoring further comprises writing to said database a timestamp indicating a time of exit of said process instance from said selected process part, and setting a process part completed state indicator for said instance.

125. The method of claim 117, wherein the monitoring comprises establishing in said database a fact record for each new process instance.

126. The method of claim 125, wherein the monitoring further comprises writing to said database payload data for each new process instance, in linking relationship with the respective fact record.

127. The method of claim 117, wherein said reporting of payload and process state data comprises displaying a snapshot of an OLAP cube including selected portions of said process state data and said payload data.

128. The method of claim 127, wherein said reporting of payload and process state data further comprises displaying additional portions of said payload data and said process state data in response to a user interaction with the displayed snapshot of the OLAP cube.

129. The method of claim 127, wherein said reporting of payload and process state data further comprises displaying details of an item of the payload data in response to a user interaction with a displayed hierarchical representation of types of the payload data.

130. The method of claim 127, wherein said reporting of payload and process state data further comprises permitting a user to change a displayed dimension of the snapshot of the OLAP cube, to cause said reporting means to display different information.

131. The method of claim 127, wherein said reporting of process state and payload data further comprises permitting a user to change a displayed measure of the snapshot of the OLAP cube, to cause said reporting means to display different information.

132. The method claim 127, wherein said reporting of process state and payload data further comprises permitting filtering of displayed data of the snapshot of the OLAP cube in response to a user interaction with the snapshot of the OLAP cube.

133. The method of claim 117, wherein said reporting of process state and payload data further comprises generating a report based on a query that combines said process state data with said payload data.

134. The method of claim 117, wherein said reporting of process state and payload data further comprises automatically determining whether data in the queryable database satisfies a predefined condition, and when said data in the queryable database satisfies said predefined condition, automatically performing a predefined action.

135. The method of claim 134, wherein the predefined action comprises sending an email.

136. The method of claim 134, wherein the predefined action comprises automatically generating a report and distributing the report over a network.

137. The method of claim 134, wherein said predefined condition comprises a defined trend.