Process Encoding

• US 20070250812A1
• Filed: 04/24/2006
• Published: 10/25/2007
• Est. Priority Date: 04/24/2006
• Status: Abandoned Application

• Current Assignee: ServiceNow Incorporated
• Original Assignee: Microsoft Corporation
• Inventors: Rajarajan, Vij, Zizys, Giedrius, Sanghvi, Ashvinkumar
• Application Number:
  US11/379,964
• Publication Number:
  US 20070250812A1
• Time in Patent Office: Days
• US Class Current: 717/117
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Described are portable packages containing encodings of processes. The packages are portable and distinct from a technology stack. The packages may be in the form of declarative code for configuring the technology stack and can be plugged into the technology stack to allow the technology stack to play the packages, thereby automating the processes encoded by the packages. Also described are methods for authoring packages, technology stacks for playing packages, an application for loading (“plugging in”) packages and also possibly controlling the playing of packages.

Claims

1. One or more volatile and/or nonvolatile computer readable media storing a package, the package comprising:

configuration information for configuring discrete components of an enterprise technology stack to cooperatively automate a business process defined by the package, where the enterprise technology stack components comprise an extensible artifact store, a extensible workflow engine, and an extensible forms framework,

the configuration information comprising;

artifact definition information defining one or more types of enterprise artifacts that are part of the package'"'"'s business process, including at least types of human roles involved in the package'"'"'s business process and types of computing devices and/or software services involved in the package'"'"'s business process;

form definition information defining one or more interactive forms for entering and/or viewing information related to the package'"'"'s business process; and

workflow definition information defining one or more workflows of the package'"'"'s business process, the workflow definition information including references or links to the types of enterprise artifacts defined by the artifact definition information and links or references to the one or more forms defined by the form definition information.

2. One or more computer readable media according to claim 1, wherein the artifact definition information is capable of being used to configure the artifact store to instantiate and store representations of enterprise artifacts of the one or more types defined by the artifact information.

3. One or more computer readable media according to claim 2, wherein the workflow definition information is capable of being used to enable the workflow engine to instantiate workflow instances of the workflow defined by the workflow information.

4. One or more computer readable media according to claim 3, wherein the form definition information is capable of being used to enable displays throughout an enterprise to display interactive forms for entering and viewing information.

5. One or more computer readable media according to claim 1, wherein at least a portion of the configuration information is in the form of, or compiled from, a System Definition Modeling (SDM) language.

6. One or more computer readable media according to claim 5, wherein the SDM language is based on a standard markup language.

7. One or more computer readable media according to claim 6, wherein the standard markup language comprises XML.

8. One or more computer readable media according to claim 1, wherein the package is portable such that different applications can use the package to configure different instances of enterprise technology stacks to perform the business process defined by the package.

9. One or more computer readable media according to claim 1, wherein the package further comprises one or more references to one or more other packages.

10. One or more computer readable media according to claim 1, wherein the configuration information comprises declarative code.

11. One or more computer readable media according to claim 10, wherein the declarative code comprises an XML based language.

12. One or more computer readable media according to claim 1, wherein the business process defined by the package comprises an information technology (IT) management process.

13. One or more computer readable media according to claim 12, wherein the IT management process comprises a change management process.

14. One or more computer readable media according to claim 12, wherein the IT management process comprises an incident management process.

15. One or more computer readable media according to claim 12, wherein the IT management process comprises a release management process.

16. One or more computer readable media according to claim 10, wherein the process corresponds to a process defined in the Information Technology Infrastructure Library (ITIL).

17. One or more computer readable media according to claim 1, wherein the package further comprises a digital signature of the package that can be used to authenticate a provider of the package.

18. One or more computer readable media according to claim 1, wherein the package further comprises version information indication a version of the package.

19. A method of generating a package that describes a process, the method comprising:

storing process definition information in a portable package, where the process definition information comprises;

workflow definition information defining a workflow corresponding to the process, where the workflow definition, if plugged into a workflow engine, will enable the workflow engine to instantiate and execute instances of the workflow;

form definition information defining a form and information linking the form to the workflow defined by the workflow definition information, where the form definition information, if plugged into a forms framework, will enabling the forms framework to display the form to users; and

artifact definition information defining one or more classes of artifacts and information linking the artifacts to the workflow definition, where the artifact definition information, if plugged into an artifact store, will enable the artifact store to store artifacts of the type defined by the artifact definition information.

20. A method according to claim 19, wherein the storing further comprises storing, in the package, package information comprising information identifying an author of the package, a dependency of the package on another package, and a packaging schema that the package complies with.

21. A method according to claim 19, further comprising storing, in the package, linking information, that, if plugged into a linking framework, will enable the linking framework to link items in any one of the workflow engine, the forms framework, or the artifact store, with items in another one of the workflow engine, the forms framework, or the artifact store.

22. A method according to claim 19, wherein the storing of the process definition information comprises forming the process definition information as declarative code, where the workflow definition information, the form definition information, and the artifact definition information comprise respective portions of code in language implemented by the workflow engine, the forms framework, and the artifact store, respectively.

23. A method according to claim 22, further comprising storing, in the package, a reference to another package comprising other process definition information.

24. A method according to claim 19, wherein the process definition information further comprises linking information that, if plugged into a linking framework, will enable the linking framework to link different items defined by different portions of the process definition information that are stored on different of the workflow engine, the forms framework, and the artifact store.

25. A method according to claim 19, wherein the process definition information further comprises portal information that, if plugged into a portal framework, will enable the portal framework to display a portal that is part of the process defined by the process definition information.

26. A method according to claim 25, wherein the process definition information further comprises knowledge information that, if plugged into a knowledge framework, will enable the knowledge framework to provide to users knowledge related to the process defined by the process definition information.

27. One or more volatile or non-volatile computer readable media storing a package, the package comprising:

declarative code defining a business or IT management process comprising workflow of the process, types of artifacts of the process, and forms of the process, where the declarative code is capable of being plugged into an Information Technology (IT) stack and enabling the IT stack to play the process defined by the declarative code;

package identification information identifying the package; and

schema information comprising a schema, or a reference to a schema, according to which the package is formatted.

28. One or more computer readable media according to claim 27, wherein the package identification information comprises two or more of:

a manufacturer or author of the package, a version number of the package, another package that the package depends on, or a security certificate for authenticating the package.

29. One or more computer readable media according to claim 27, wherein the declarative code conforms to a system definition modeling language.

30. One or more computer readable media according to claim 27, wherein declarative code, which defines the business or IT management process, comprises a portion that can be used by a workflow framework in the IT stack, a portion that can be used by a forms framework in the IT stack, and a portion that can be used by an artifact store in the IT stack.

31. One or more computer readable media according to claim 30, wherein the workflow framework, the forms framework, and the artifact store are separate and autonomous components of the IT stack that can be installed and used independent of the other components.

32. One or more computer readable media according to claim 31, wherein the artifact store stores configuration items and relations therebetween.

33. One or more computer readable media according to claim 32, wherein the artifact store comprises a configuration management database (CMDB).

34. One or more computer readable media according to claim 27, wherein the declarative code, which defines the business or IT process, specifies people or roles involved in the process, and activity flow, via the IT stack, to and/or from the people or roles.