Adaptable workflow and communications system

• US 20040230466A1
• Filed: 05/11/2004
• Published: 11/18/2004
• Est. Priority Date: 05/12/2003
• Status: Abandoned Application

• Current Assignee: Radaptive Incorporated
• Original Assignee: Radaptive Incorporated
• Inventors: Davis, James E., Ganesh, Balasubramaniam, Holmes, Kenneth L.
• Application Number:
  US10/844,006
• Publication Number:
  US 20040230466A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/063118 Staff planning in a project environment
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A data driven workflow solution that normalizes business communications by systematically recording related business communications from disparate communications channels in a common format such that the related business communications are automatically integrated into the associated business processes and which flow solution is flexible for capturing additional data elements or to adapt to changing tasks associated with the business processes is disclosed

Claims

1. A method for managing projects, requests, tasks, approvals and associated communications regardless of source of said projects, said requests, said tasks, said approvals, the method comprising the computer-implemented act of:

normalizing said projects, said requests, said tasks, said approvals and said associated communications based on a common data object model, wherein said common data object model enables logical relationships between a plurality of related objects and a message object associated with said common data object model.

2. The method of claim 1, wherein said common data object model comprises:

a core object;

a relationship object; and

said message object.

3. The method of claim 2, wherein records associated with said core object and said message object are instantiated by any combination of communications channels, including email, instant messaging, voice, and workflow application entries.

4. The method of claim 1, further comprising the act of:

using an automation facility that is based on said common data object model;

wherein said automation facility develops an application logic that is implemented by using a form-driven administration interface; and

wherein said automation facility automatically creates one or more business rules based on said application logic.

5. The method of claim 2, further comprising the act of:

using a common user interface that is based on said common data object model, wherein said common user interface is adapted for presenting a unified view of said related objects, said core object, said message object, and said relationship object using a GUI window with associated sub-windows.

6. The method of claim 5, wherein said common user interface is HTML web-based.

7. The method of claim 1, further comprising the act of:

using a data-driven mechanism for describing and instantiating said projects, said requests, said tasks, said approvals and associated data elements.

8. The method of claim 7, wherein said data-driven mechanism is adapted for one or more of:

collecting a first information based on said requests;

creating said tasks and related dependencies based on said requests;

collecting a second information based on each of said tasks;

driving one or more automation functions based on said tasks;

validating said associated data elements; and

sending notifications based on one or more events.

9. The method of claim 2, wherein said core object is of any type based on business objectives.

10. The method of claim 9, wherein said any type includes:

a core-ticket object type;

a core-group object type;

a core-other object type;

a core-assets object type;

a core-documents object type; and

a core-people object type;

11. The method of claim 1, wherein said plurality of related objects is of any type based on business objectives.

12. The method of claim 11, wherein said any type includes:

a request object type;

a project object type;

a task object type;

an approvals object type;

a human resources system object type;

an LDAP object type;

a users object type;

a group object type;

an SLA agreements object type;

a contracts object type;

a maintenance agreement object type;

a main asset object type;

a purchasing system asset object type;

a scanning system object type;

an inventory system object type;

a files object type;

an images object type;

a fax object type;

a employee object type;

a customer object type;

a vendor object type; and

a skills object type.

13. The method of claim 1, further comprising the act of:

using an integration mechanism for integrating input and output from integrating tools, work assist tools and terminal emulators into said common data object model.

14. The method of claim 13, wherein the act of integrating includes:

capturing input commands associated with using said work assist tools and terminal emulators;

capturing output associated with said input commands;

storing said captured input commands and said captured output in an associated message object.

15. The method of claim 1, further comprising the act of:

using a subscription mechanism for allowing end-users to subscribe to messages.

16. A common data object model for managing projects, requests, tasks, approvals and associated communications regardless of source of said projects, said requests, said tasks, said approvals, wherein said common data object model enables logical relationships between a plurality of related objects and a message object associated with said common data object model.

17. The common data object model of claim 16, wherein said common data object model comprises:

a core object;

a relationship object; and

said message object.

18. The common data object model of claim 17, wherein records associated with said core object and said message object are instantiated by any combination of communications channels, including email, instant messaging, voice, and workflow application entries.

19. The common data object model of claim 16, wherein said common data object model is associated with an automation facility;

and

wherein said automation facility develops an application logic that is implemented by using a form-driven administration interface; and

wherein said automation facility automatically creates one or more business rules based on said application logic.

20. The common data object model of claim 17, wherein said common data object model is associated with a common user interface, wherein said common user interface is adapted for presenting a unified view of said related objects, said core object, said message object, and said relationship object using a GUI window with associated sub-windows.

21. The common data object model of claim 20, wherein said common user interface is web-based.

22. The common data object model of claim 16, wherein said common data object model is associated with a data-driven mechanism for describing and instantiating said projects, said requests, said tasks, said approvals and associated data elements.

23. The common data object model of claim 22, wherein said data-driven mechanism is adapted for one or more of:

collecting a first information based on said requests;

creating said tasks and related dependencies based on said requests;

collecting a second information based on each of said tasks;

driving one or more automation functions based on said tasks;

validating said associated data elements; and

sending notifications based on one or more events.

24. The common data object model of claim 17, wherein said core object is of any type based on business objectives.

25. The common data object model of claim 24, wherein said any type includes:

a core-ticket object type;

a core-group object type;

a core-other object type;

a core-assets object type;

a core-documents object type; and

a core-people object type;

26. The common data object model of claim 16, wherein said plurality of related objects is of any type based on business objectives.

27. The common data object model of claim 26, wherein said any type includes:

a request object type;

a project object type;

a task object type;

an approvals object type;

a human resources system object type;

an LDAP object type;

a users object type;

a group object type;

an SLA agreements object type;

a contracts object type;

a maintenance agreement object type;

a main asset object type;

a purchasing system asset object type;

a scanning system object type;

an inventory system object type;

a files object type;

an images object type;

a fax object type;

a employee object type;

a customer object type;

a vendor object type; and

a skills object type.

28. The common data object model of claim 16, wherein said common data object model is associated with an integration mechanism for integrating input and output from integrating tools, work assist tools and terminal emulators into said common data object model.

29. The common data object model of claim 28, wherein integrating includes:

capturing input commands associated with using said work assist tools and terminal emulators;

capturing output associated with said input commands;

storing said captured input commands and said captured output in an associated message object.

30. The common data object model of claim 16, wherein said common data object model is associated with a subscription mechanism for allowing end-users to subscribe to messages.