Abstract:
A computer-implemented method for creating a consolidating model includes converting a plurality of network specific models into a plurality of network common models wherein the plurality of network common models has a common granularity level and common technical terms. A consolidated model skeleton is then created based on the plurality of network common models wherein the consolidated model skeleton includes one or more common functions from each network specific model of the plurality of network specific models. Finally, unconnected functions in the consolidated model skeleton are connected with a branched function.

Description:
DESCRIPTION OF THE RELATED ART  
       [0001]     Process configuration for contemporary enterprise systems is a major task given the amount of business processes that these systems target and their rich functionality. Especially in large corporations, however, different parts of the organization may require for configuring processes differently. This may result from geographical dispersion and the resulting necessity for obtaining different national laws, different parts policies in different parts of the organization or the management structure in the organization. In a scenario where different parts of the organization can freely configure their parts of an enterprise system, and also with the business processes of the enterprise system, it is no longer possible to look at generalized business processes from an “organization as a whole” perspective. Thus, there exists no consistent support for a consolidated view on business process management from the perspective of the entire organization.  
         [0002]     For example, an organization may primarily exist of three subunits—each located in different countries. To perform a business process, such as invoice processing, each subunit has a need to configure the software-supported generalized process to meet their own needs. These needs can include abiding by local law, conforming to subunit management preferences and responding to customer requirements. As a result, each subunit has their own unique process. To provide consistent process related guidance for all three subunits, the challenge lies in how to merge those three processes into one single process model yet still allow for the requirements of each subunit.  
         [0003]     One option for merging these similar, yet disparate, processes is to re-code a brand new singular process for all of the subunits. This approach would typically involve a team of programmers and stakeholders to plan the project, execute the project and finally provide support after installation. Obviously, this could be a very expensive option and time-consuming operation. Additionally, once the project is completed, any new requirements would most likely require even more time and money to implement.  
         [0004]     Yet another possible alternative is to implement an entirely new system. This option would also be rather time-intensive and most certainly expensive. As a result, this path is also not so desirable.  
         [0005]     In view of the foregoing, it may be useful to provide methods and systems that facilitate process consolidation of varying aspects of an organization while still allowing for customization to meet the needs of those varying aspects of the organization.  
       SUMMARY OF EMBODIMENTS OF THE INVENTION  
       [0006]     The present invention is described and illustrated in conjunction with systems, tools and methods of varying scope which are meant to be exemplary and illustrative, not limiting in scope.  
         [0007]     A computer-implemented method for consolidating models, in accordance with an exemplary embodiment, includes converting a plurality of network specific models into a plurality of network common models wherein the plurality of network common models has a common granularity level and common technical terms. A consolidated model skeleton is then created based on the plurality of network common models wherein the consolidated model skeleton includes one or more common functions from each network specific model of the plurality of network specific models. Finally, unconnected functions in the consolidated model skeleton are connected with a branched function.  
         [0008]     A computer-implemented method for consolidating models, in accordance with another exemplary embodiment, includes converting a plurality of network specific models into a plurality of network common models wherein the plurality of network common models has a common granularity level and common technical terms wherein a compiler converts a network specific model of the plurality of network specific models to the common granularity level if a granularity level of the network specific model is coarser than the common granularity level, and wherein a decompiler converts a network specific model of the plurality of network specific models to the common granularity level if a granularity level of the network specific model is finer than the common granularity level. A consolidated model skeleton is then created based on the plurality of network common models wherein the consolidated model skeleton includes one or more common functions from each network specific model of the plurality of network specific models. Finally, unconnected functions in the consolidated model skeleton are connected with a branched function.  
         [0009]     In addition to the aspects and embodiments of the present invention described in this summary, further aspects and embodiments of the invention will become apparent by reference to the drawings and by reading the detailed description that follows.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0010]      FIG. 1  is a block diagram illustrating a network communication system;  
         [0011]      FIG. 2  is a flowchart illustrating a method for process consolidation, in accordance with an exemplary embodiment;  
         [0012]      FIG. 3  is a block diagram further illustrating the model conversion process of  FIG. 2 , in accordance with an exemplary embodiment;  
         [0013]      FIG. 4A  is an exemplary block diagram further illustrating the process of creating the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment;  
         [0014]      FIG. 4B  is an exemplary block diagram further illustrating the process of connecting the unconnected functions of the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment;  
         [0015]      FIG. 5A  is another exemplary block diagram further illustrating the process of creating the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment; and  
         [0016]      FIG. 5B  is another exemplary block diagram further illustrating the process of connecting the unconnected functions of the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment.  
     
    
     DETAILED DESCRIPTION  
       [0017]     An aspect of the present invention contemplates methods and systems for process consolidation. Varying models that characterize the differing operations of an organization are converted to an integrated model. Common processes of the converted models are identified and a new model is constructed based on the common processes. Non-common processes are then incorporated to allow for customization for the differing operations of the organization. Advantageously, aspects of the present invention enables implementation of an organization-wide ERP software system yet still allow for customization for various subunits. As a result, an organization can efficiently implement ERP software and still meets the needs of the various subunits. Moreover, it supports a centralized and integrated view on the various ways of operation.  
         [0018]      FIG. 1  is a block diagram illustrating a network communication system  10 . Included in system  10  are various networks N 1    20 , N 2    30  and N 3    40 , and a server  50 , all of which can communicate with each other over wide area network (“WAN”)  60 . Networks N 1    20 , N 2    30  and N 3    40  typically house the operations of varying aspects of an organization. These varying aspects can perhaps represents different geographic locations, business units or divisions of the organization. Server  50  typically performs processes that are common to the entire organization, for example email.  
         [0019]      FIG. 2  is a flowchart illustrating a method  70  for process consolidation, in accordance with an exemplary embodiment. After a start operation, network specific models are converted to a common granularity level and varying technical terms are also converted to standard terminology, at an operation  80 . The network specific models represent the customized processes of the varying aspects of the organization of essentially the same generic business process, for example procurement. At operation  90 , a consolidated model skeleton is created based on functions that are common to all of the converted models. Finally, at an operation  100 , any remaining functions that are not common to the converted models are added in and connected as branched functions. As a result, a single model is created that can be used by the entire organization, yet still provide varying levels of customization for different parts of the organization.  
         [0020]      FIG. 3  is a block diagram  110  further illustrating the model conversion process  80  of  FIG. 2 , in accordance with an exemplary embodiment. Included in block diagram  110  are models of varying granularity levels. Model M 1    120  has a coarse granularity, model M 2    130  has a standard granularity level and model M 3    140  has a fine granularity level. Since all the models need to be converted to the same granularity level, only those models that are not standard need to be converted. It should be noted that the only requirement is that the models all have the same granularity level and as such any one particular granularity level can be labeled as ‘standard’. In the block diagram  110 , a granularity level in between coarse and fine has been selected as the standard granularity level. However, the coarse and fine granularity levels and other varying levels of granularity could also be the standard.  
         [0021]     To convert M 1    120  to the standard granularity, it is processed through a coarse to standard compiler  150 . The converted model is then processed through a coarse to standard dictionary  160  so that the converted model  170  will have a common set of technical terms. In a similar manner, M 3    140  is processed through a fine to standard decompiler  180  and a fine to standard dictionary  190 .  
         [0022]      FIG. 4A  is an exemplary block diagram  200  further illustrating the process  90  of creating the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment. Included in block diagram  200  are converted models M 1    210  and M 2    220 . Model M 1    210  contains functions F 1 , F 2 , F 3  and F 5 . Model M 2    220  contains a slightly different set of functions—F 1 , F 2 , F 4  and F 5 . A consolidated model skeleton  230  is therefore created from the functions common to both models M 1    210  and M 2    220 —F 1 , F 2  and F 5 . To complete the consolidated model skeleton  230 , functions F 3  and F 4  need to be incorporated.  
         [0023]      FIG. 4B  is an exemplary block diagram  230  further illustrating the process  100  of connecting the unconnected functions of the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment. As previously indicated by the consolidated model skeleton  230  of  FIG. 4A , functions common to both models M 1    210  and M 2    220  were first used as a starting point. Now that they have been added, functions unique to each of the models M 1    210  and M 2    220  need to be incorporated. In this particular example, function F 3  of model M 1    210  and function F 4  of M 2    220  are the functions that make the models unique. Functions F 3  and F 4  are therefore incorporated into consolidated model skeleton  230  as branched functions  250  and  260 . By implementing the branched functions  250  and  260 , one consolidated model can be employed yet still retain the uniqueness of models M 1    210  and M 2    220 . For example, if the process of model M 1    210  needs to be performed, then branched function  250  will be employed, after functions F 1  and F 2  are completed. Similarly, if the process of model M 2    220  is desired, then branched function  260  will be used, after functions F 1  and F 2  are completed.  
         [0024]      FIG. 5A  is another exemplary block diagram  270  further illustrating the process  90  of creating the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment. In this particular example, it is desired to merge another model M 3    280  into consolidated model skeleton  230 . To achieve this, the common functions are laid out into a new consolidated model skeleton  290 . The functions common to skeleton  230  and model M 3    280  are F 1 , F 2  and F 4 .  
         [0025]      FIG. 5B  is another exemplary block diagram further illustrating the process of connecting the unconnected functions of the consolidated model skeleton of  FIG. 2 , in accordance with an exemplary embodiment. After the common functions have been identified and incorporated into consolidated process skeleton  290 , the balance of the functions need to be added—F 3 , F 4  and F 5 . To achieve the functionality of consolidated process skeleton  230  and model M 3    280  in consolidated model skeleton  290 , functions F 3 , F 4  and F 5  are added in as branched functions  310 ,  320  and  330 . Consolidated process skeleton  290  now has the individual functionality of all three models (M 1    210 , M 2    220  and M 3    280 ) in one consolidated model.  
         [0026]     While this invention has been described in terms of certain embodiments, it will be appreciated by those skilled in the art that certain modifications, permutations and equivalents thereof are within the inventive scope of the present invention. It is therefore intended that the following appended claims include all such modifications, permutations and equivalents as fall within the true spirit and scope of the present invention.