Groupware time tracking

• US 20060277544A1
• Filed: 04/20/2006
• Published: 12/07/2006
• Est. Priority Date: 04/22/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Vogler-Ivashchanka, Iryna, Bjoernsen, Christian G., Bar-On, Dana Cohen, Wood, Eric, Kol, Nir, Samson, Frederic E.
• Granted Patent: US 9,111,253 B2
• Time in Patent Office: Days
• US Class Current: 718/100
• 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/10 Office automation; Time management
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]

Abstract

Embodiments of the present invention provide methods and apparatuses enabling groupware to track time associated with a workflow task. A workflow object representing a workflow task is provided. The workflow object is associating with a time period, a project code, and an identifier of a groupware client user participating in the workflow task. In response to an event indicating completion of the workflow task, the time period, the project code, and the identifier is automatically transmitted to a backend application.

Claims

1. A method for tracking time associated with a workflow task comprising:

providing in a groupware client a workflow object representing a workflow task;

associating with the workflow object a time period, a project code, and an identifier of a groupware client user participating in the workflow task; and

in response to an event indicating completion of the workflow task, automatically transmitting to a backend application the time period, the project code, and the identifier.

2. The method of claim 1, further comprising:

calculating the time period based on input indicating a start time and an end time.

3. The method of claim 2, wherein the event occurs when a current time is equal to the end time and the method further comprises:

comparing the current time with the end time.

4. The method of claim 1, wherein the event occurs when a graphical user interface tool in the groupware client is selected and the method further comprises:

receiving input indicating selection of the tool.

5. The method of claim 1, further comprising:

receiving from the backend application a summary of time periods associated with the project code or the identifier; and

presenting the summary in the groupware client.

6. The method of claim 1, further comprising:

providing a list of project codes based on the identifier; and

enabling the user to select the project code from the list.

7. The method of claim 1, further comprising:

enabling the user to search for the project code.

8. The method of claim 1, wherein providing the workflow object comprises providing the workflow object to a potential participant of the workflow task.

9. A machine readable medium having instructions which when executed by a processor cause the processor to perform operations comprising:

transmitting to a first groupware client a workflow object representing a workflow task, the workflow object created in a second groupware client and associated with a start time, an end time, and a project code designated by an organizer of the workflow task;

receiving from the first groupware client a response to the transmitting;

relaying the response to the second groupware client; and

when the response includes an acceptance of participation in the workflow task, automatically creating in the first groupware client a calendar entry based on the start time and the end time.

10. The medium of claim 9, wherein the operations further comprise:

receiving a designation of a second project code; and

associating the second project code with the workflow object.

11. The medium of claim 10, wherein receiving the designation comprises receiving the designation from the first groupware client, and the operations further comprise:

associating the second project code with the workflow object in association with an identifier of a user of the first groupware client.

12. The medium of claim 9, wherein the workflow object is selected from the group consisting of:

a calendar object, an email object, a task list object, and a contacts object.

13. A device for processing time associated with a workflow task comprising:

a groupware interface to receive, from a groupware client, a request to change a property of a workflow object representing a workflow task, the workflow object associated with a time, a project code, and one or more user identifiers; and

a backend application, connected to the groupware interface, comprising;

a reporting module to determine if the property was incorporated into an external report;

a storage interface to transmit the property to a storage system in response to the request if the property was not incorporated into the external report; and

a notification module to transmit an error message to the groupware client in response to the request if the property was incorporated into the external report.

14. The device of claim 13, wherein the external report comprises an invoice.

15. The device of claim 13, wherein the reporting module comprises:

an internal reporting module connected to the groupware interface to generate an internal report summarizing times associated with the project code or associated with at least one of the one or more user identifiers.

16. The device of claim 13, wherein the reporting module comprises:

an external reporting module connected to an external system to generate the external report based on the time, the project code, and the one or more user identifiers.

17. The device of claim 13, wherein the backend application further comprises:

an alert module to transmit to one or more groupware clients an alert based on the time, the alert relating to compliance with a time tracking policy.

18. The device of claim 13, wherein the backend application further comprises:

a validation module connected to the groupware interface and a database to receive project codes from the groupware client via the groupware interface and to determine validity of the project codes based on data stored in the database.

19. The device of claim 13, wherein the backend application further comprises:

a default module to provide a default project code to associate with the workflow object, the default project code based on at least one of;

the workflow task, the time, and the one or more user identifiers.

20. The device of claim 13, wherein the backend application further comprises:

a default module to provide a default time to associate with the workflow object, the default time based on at least one of;

the workflow task, the project code, the one or more user identifiers, and a status of a project assigned to the project code.