Method and system for synchronizing multiple user revisions, updating other strategy maps in the databases that are associated with the balanced scorecard

• US 7,440,978 B2
• Filed: 01/14/2005
• Issued: 10/21/2008
• Est. Priority Date: 01/14/2005
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hulen, Corey, Yang, Vincent Feng, Chan, Stella Y., Booth, Noah H.
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US11/035,754
• Publication Number:
  US 20060161596A1
• Time in Patent Office: 1,376 Days
• Field of Search: 707 1- 2, 707/10, 707100-102, 707/104.1, 707200-203, 709/203, 709210-215, 709220-224, 715/229
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A client may revise a balanced scorecard by adding, deleting and/or moving objects on a strategy map. Multiple clients may attempt to revise the strategy map simultaneously. Non-conflicting revisions are synchronized with the strategy map in a scorecard database. A conflicting revision may be generated when objects associated with one client'"'"'s revisions cannot be reconciled with the objects associated with another client'"'"'s revisions. Conflicting revisions may be resolved by giving one client'"'"'s revisions priority over subsequent client revisions. Any identified zombie objects are removed from the strategy map before synchronization with the scorecard database. The revised strategy map is saved in the scorecard database. The revised objects are synchronized with the corresponding scorecard and any associated strategy maps in the scorecard database.

Claims

1. A computer-implemented method for synchronizing multiple user revisions to a balanced scorecard, comprising:

retrieving, on a web server, a strategy map from a database, wherein the strategy map corresponds to the balanced scorecard;

implementing an optimistic lock on the strategy map allowing a plurality of clients to edit the strategy map simultaneously;

receiving, on the web server, a first revised strategy map from a first client, wherein the first revised strategy map includes revisions to objects in the strategy map by the first client;

receiving, on the web server, a second revised strategy map from a second client, wherein the second revised strategy map includes revisions to objects in the strategy map by the second client;

resolving, on the web server, conflicts between objects of the first revised strategy map and objects of the second revised strategy map to generate a resolved strategy map, wherein resolving the conflicts comprises;

prioritizing the revisions associated with the first client over the revisions associated with the second client when the first revised strategy map associated with the first client is saved in the database before the second revised strategy map associated with the second client is saved in the database,

identifying a zombie object in the second revised strategy map when a given object is removed from the first revised strategy map by the first client and the given object is further revised by the second client, and when the first revised strategy map associated with the first client is saved in the database before the second revised strategy map associated with the second client is saved in the database, and

removing the identified zombie object from the second strategy map;

saving the resolved strategy map from the web server to the database;

synchronizing the objects of the resolved strategy map with the corresponding balanced scorecard in the database;

updating other strategy maps in the database that are associated with the balanced scorecard.

2. The computer-implemented method of claim 1, further comprising:

displaying the strategy map to the first client when the first client selects the strategy map; and

displaying the strategy map to the second client when the second client selects the strategy map.

3. The computer-implemented method of claim 1, wherein an object is revised by one of:

adding the object, deleting the object, and moving the object.

4. The computer-implemented method of claim 1, wherein saving the first revised strategy map further comprises saving the first revised strategy map with most recently saved revisions to the objects when the objects are not scorecard objects.

5. A system for synchronizing multiple user revisions to a balanced scorecard, comprising:

a database that comprises a strategy map that corresponds to the balanced scorecard;

a server coupled to the database, wherein the server is arranged to implement an optimistic lock on the strategy map allowing a plurality of clients to edit the strategy map simultaneously;

a first client coupled to the server, wherein the first client is arranged to;

retrieve the strategy map from the database, and

revise objects on the strategy map;

a second client coupled to the server, wherein the second client is arranged to;

retrieve the strategy map from the database, and

revise objects on the strategy map; and

a synchronization module that is arranged to;

resolve conflicts between the objects of the revised strategy map revised by the first client and the objects of the revised strategy map revised by the second client wherein resolving the conflicts, the synchronization module is further arranged to;

prioritize the revisions associated with the first client over the revisions associated with the second client when the revised strategy map associated with the first client is saved in the database before the revised strategy map associated with the second client is saved in the database,

identify a zombie object in the revised strategy map revised by the second client when a given object is removed from the first revised strategy map by the first client and the given object is further revised by the second client, and when the revised strategy map associated with the first client is saved in the database before the revised strategy map associated with the second client is saved in the database, and

remove the identified zombie object from the strategy map revised by the second client,

save a resolved strategy map in the database,

synchronize the objects of the resolved strategy map with the corresponding balanced scorecard in the database;

update other strategy maps in the database that are associated with the balanced scorecard.

6. The system of claim 5, wherein the first client and the second client are arranged to revise objects by one of:

adding the object, deleting the object, and moving the object.

7. A computer-readable storage medium having computer executable instructions for synchronizing multiple user revisions to a balanced scorecard, comprising:

retrieving, on a web server, a strategy map from a database, wherein the strategy map corresponds to the balanced scorecard;

implementing an optimistic lock on the strategy map allowing a plurality of clients to edit the strategy map simultaneously;

receiving, on the web server, a first revised strategy map from a first client, wherein the first revised strategy map includes revisions to objects in the strategy map by the first client;

receiving, on the web server, a second revised strategy map from a second client, wherein the second revised strategy map includes revisions to objects in the strategy map by the second client;

resolving, on the web server, conflicts between objects of the first revised strategy map and objects of the second revised strategy map to generate a resolved strategy map wherein resolving the conflicts comprises;

prioritizing the revisions associated with the first client over the revisions associated with the second client,

identifying a zombie object in the second revised strategy map when a given object is removed from the first revised strategy map by the first client and the given object is further revised by the second client, and when the first revised strategy map associated with the first client is saved in the database before the second revised strategy map associated with the second client is saved in the database, and

removing the identified zombie object from the strategy map;

saving the resolved strategy map from the web server to the database;

synchronizing the objects of the resolved strategy map with the corresponding balanced scorecard in the database; and

updating other strategy maps in the database that are associated with the balanced scorecard.