|Publication number||WO1997031320 A1|
|Publication date||28 Aug 1997|
|Filing date||21 Feb 1997|
|Priority date||22 Feb 1996|
|Also published as||CA2290594A1, EP0954813A1|
|Publication number||PCT/1997/104, PCT/AU/1997/000104, PCT/AU/1997/00104, PCT/AU/97/000104, PCT/AU/97/00104, PCT/AU1997/000104, PCT/AU1997/00104, PCT/AU1997000104, PCT/AU199700104, PCT/AU97/000104, PCT/AU97/00104, PCT/AU97000104, PCT/AU9700104, WO 1997/031320 A1, WO 1997031320 A1, WO 1997031320A1, WO 9731320 A1, WO 9731320A1, WO-A1-1997031320, WO-A1-9731320, WO1997/031320A1, WO1997031320 A1, WO1997031320A1, WO9731320 A1, WO9731320A1|
|Inventors||Noel Robert Yeates, Sandra Kay Zubrinich|
|Applicant||Cullen Egan Dell Limited|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (10), Referenced by (33), Classifications (3), Legal Events (10)|
|External Links: Patentscope, Espacenet|
"Strategic Management System"
Field of the Invention
The present invention relates to improvements in systemising a range of management processes that are undertaken in the normal course of operating a business, organisation or a network of businesses or organisations. Background of the Invention
In any business or organisation, there are a large number of tasks which involve the participation and coordination of individuals or groups of individuals at particular points in time or over a period of time to achieve maximum benefit, output or productivity of the group, utilising minimum resources.
Various computer packages available in the market place go part of the way to assisting in undertaking organisational planning and performance measurement. These packages are primarily directed at the achievement of certain goals within a given time schedule. Unfortunately, these packages do not allow an organisation to achieve a fully effective integrated strategy wherein their plans are fully aligned and active within the organisation. Further, these systems do not allow for instantaneous feedback by way of performance measurement including benchmarking tests and process improvement. Existing systems further separate the process of planning from those of measurement, benchmarking, process improvement and risk management. When such a separation takes place, substantial synergisms are lost, in that consistency across an organisation may be disrupted and access to shared information limited. For example, known systems may allow a manager in an organisation to undertake the formation of a strategic or business unit plan in isolation and without reference to any planning undertaken by colleagues elsewhere in the organisation or without reference to the strategic direction of the organisation. Further, existing systems are based on the collection and analysis of retrospective information and are therefore only capable of developing organisational plans based on past data and are therefore retrospective in their management approach.
Further, current systems of organisational planning do not include information or reference to the business processes that are applied within an organisation. Current systems are further often based around financial targets and actions rather than an analysis of the business processes within the planning entity. In any large organisation, the processes that an organisation adopts are normally critical to its competitiveness. Further, it is to an organisation's advantage to increase the amount of value derived from its resources and processes. Such resources and processes are considered by most organisations as being essential for the improvement in performance of the organisation and may include the organisation re-engineering their processes to be of greater value. Current planning systems do not link business processes to organisational strategy. Further, current systems do not align and analyse any assumptions that are made during organisational planning that may impact on current and future objections across the organisation. Although reference is often made to an assumption, there is generally no attempt in current systems to analyse the impact of assumptions and the possible impacts on and across an organisation, and its strategy, should the assumption prove to be invalid.
Further, current performance measurement systems normally only present simple figures in a spreadsheet or graphical format. No analysis is undertaken of any performance data with regard to its effect on other business units within an organisation and the effect on a range of specific performance indicators within the organisation. Summary of the Invention
It is an object of the present invention to provide for an improved form of performance measurement and planning system through the integration of organisational plans and performance measures so as to provide a substantial synergistic effect.
In accordance with an aspect of the present invention there is provided a computer system for performance measurement and planning, comprising: organisation planning means for the entering, aligning and linking a number of different organisational plans; indicator determination means for determining a series of indicators for said organisational plan; benchmarking means for benchmarking said indicators against internal or external measurements or targets; and wherein said organisational planning means, said indicator determination means and said benchmarking means are interlinked into a single co-ordinated system.
Preferably, there is provided a computer based framework which provides a fully integrated or linked approach to organisational planning, the measurement of performance and the undertaking of benchmarking of current organisational performance with other business units, organisations or groups of organisations.
Further, preferably all levels of an organisation are interlinked and use a consistent planning structure based on shared information. Hence, the workings of all levels of an organisation are networked together as are the business unit plans and measurement procedures to be conducted with reference to the overall strategy and all other tasks being undertaken by the organisation.
Further, measures throughout a plan hierarchy may be related to a common set of Key Result Areas. Business Objectives and their actions, where defined, may be linked to a common set of Strategic Objectives, and each objective may be in turn linked to a set of Strategic Objectives. This assists in developing a consistent approach to achieving the overall aims of an organisation and in promoting a strategic management approach within the organisation.
Further, the system of the present invention is preferably capable of capturing performance data in real time thereby permitting a manager to upgrade and amend plans and other documents so that they are always current. Hence, organisational planning can be undertaken based on current data and the plans developed based on prospective views of an organisation. This introduces the concept of continuous planning as part of strategic management behaviour.
Further, the present invention preferably provides that any assumptions made during the planning process can be analysed to examine the possibility that they may prove incorrect and thereby provide an assessment of the likely impacts and actions that will be required of an organisation as a result of the impact of an invalid assumption. Preferably, the present invention also includes the identification of both responsibility and authority lines and accountability lines for specific actions.
Preferably, there is further provided tools to assist managers to analyse and model the performance of an organisation at multiple levels, thereby allowing managers to integrate performance analysis and modelling into their planning process.
Preferably the present invention allows for the flexibility to change organisational design and adopt to whatever configuration is needed to suit their changing needs including support of hierarchical, flattened and matrix organisation structures.
Further, there is preferably provided means for inserting benchmarking data with an organisation's current or actual data for analysis.
Preferably the indicator determination means includes means for determining a series of indicators for said organisational plan and graphically representing those measures, analysing those measures or modelling those measures to provide measurement information of past events or leading information about future events or alternatives available to the organisation. The preferred embodiment of the present invention is designed to operate on a general purpose computer or a desktop personal computer either operating in isolation or included in a network of computers. The present invention could be implemented on a wide range of computers utilising standard and widely accepted programming languages and graphical user interfaces in the normal manner and in a way that data may be retrieved to produce reports or a text, graphical or in any another form.
The preferred embodiment of the present invention provides for a strategic management system that systemises and integrates the planning, measurement, project and benchmarking activities throughout an organisation, group or network. It further preferably provides a comprehensive and logical approach to understanding an organisation and how it functions, both in isolation and as an integral part of a large organisation. As a result, management is able to determine, integrate and direct strategy, in addition to directing change and performance within and external to the organisation.
Further, it focuses the key people in an organisation on any changes in the external business environment and the organic nature of an organisation. By integrating planning, measurement and benchmarking the management of an organisation is required to think and act holistically, and can adopt a culture of shared ownership and responsibility. As a result, more people will be willing to accept accountability and commitment to fulfilling the potential of the organisation. This forms the basis for strategic learning and strategic awareness, leading overtime to strategic behaviour.
The system is capable of either enforcing or optionally sharing information in any form of operational structure. In this regard it is omni-directional and has a capacity to share and transfer information between plans. Further, it has the capacity for information to be accessed through a series of security checks. Information is able to be shared securely amongst a wider range of people within the organisation and for that information to be transferred within a hierarchical, matrix, linear or non-directional form. The capacity to share information and experience and undertake a range of self-assessment procedures and comparative exercises whether as part of the performance measurement function or the benchmarking function, encourages the use of strategic management behaviour and facilitates the process of organisational learning. This supports the concept of self assessment through performance measurement and benchmarking as part of strategic management behaviour. Preferably the system is capable of being used in whole or in part and is flexible in the demands that it makes of the user. Similarly, it is flexible in satisfying the needs of the user and can be adapted to provide as much or as little functionality as is required. Further many parts of the system are non- reliant on other parts of the systems. In this regard the user is able to access and utilise as much or as little of the system as is required without limiting the desired functionality. In this regard the level of flexibility available to users allows the user to be self-determining in the quantity of the system that is accessed at any point in time or over time.
The increased synergism and awareness of the organisation and how it functions, both in isolation and as an integral part of a large group, provides a basis for the members of the organisation to work cooperatively towards best practice. Further, the preferred embodiment allows the organisation to choose the degree of management or autonomy and flexibility that suits its particular culture and corporate objectives. A resulting increase in strategic awareness and strategic behaviour through increased awareness often results. In this way, the preferred embodiment supports strategic learning and other changed management and improvement initiatives that may be operating within the organisation. Preferably, senior managers set the overall direction for an organisation. However, people at all levels have a valid and essential role in participating in planning and contributing to the development of strategic and business objectives.
Further, the preferred embodiment collects appropriate internal data for measurement . Performance indicators are structured in the context of the organisation's overall strategy and objectives. Indicators of both financial and non-financial performance are preferably utilised to focus the organisation on areas central to its overall success. Preferably, the embodiment of the invention encourages continuous improvement by using internal and external benchmarks to ensure an organisation is focused on the best industry practice as measured in accordance with those benchmarks for the organisation's core processes and activities. The preferred embodiment can assist organisations to establish and communicate clear strategic objectives and effective measures of performance. The benchmarking capability supplements the communication process and ensures that managers are constantly aware of internal performance and how it compares with best industry practice.
In summary, the preferred embodiment can include or result in the following advantageous features:
1. The demonstration of leadership emanating from top management by clearly translating vision, values and strategy throughout the organisation and providing a consultative approach to organisational planning and performance measurement which in turn encourages ownership by the members of the organisation. Further, consistency is provided in communication, linking strategy, objectives and actions. The system supports a commitment to continuous improvement and best practice and allows for strategic management and strategic learning .
2. The preferred embodiment provides an integrated and holistic approach that links strategy, objectives, processes and measurement with implementation structures. The identification of assumptions and risks and the analysis of the impact of invalid assumptions and project management are treated as integral parts of the planning and performance measurement processes in a prospective way. 3. The measurement of per ormance through key result areas and indicators provides a balance between financial and non-financial performance measures and allows cross-functional measures for supporting performance gap analysis. Utilisation of the cross- functional indicators eliminates conflicting measures across an organisation.
4. The benchmarking process is treated as integral part of strategic management, and the focus is on continuous improvement including identifying the gap between actual and best practice performance.
5. Analysis tools can be used while viewing plan.
6. An ability to share information up, down and across the organisation.
7. The development of plans may emanate from the objectives and needs from originating business units or from support units with the intention of achieving a "grand plan" for the organisation that considers the objectives and resource requirements of all parts of the organisation. This may be achieved in a way that is either individually based or consensus driven. The system has the flexibility for the organisation and/or its parts to define the methods for establishing plans and developing performance measurement and benchmarking protocols. 8. An ability for parts of an organisation to develop reports of performance measurement from a range of sources and to analyse those reports as well as to receive interpretative applied management information as to performance.
9. An organisation can model information and develop alternative routes to improving performance by considering a series of interrelationships between performance measures within the organisation, business unit, team or at an individual level. In these respects the system can accommodate a variable range of complexity in the interrelationship and reports these interrelationships graphically or in narrative forms. Further, it can provide interpretative information as to the range of possible outcomes and relate these outcomes to a range of planning options. The system can then interpret these in the context of the impact of the outcome on the overall objectives of the organisation and provide a gauge as to the likelihood of the overall objective, whether at a business or strategic level, being met.
10. An ability to secure planning information and manage the security of information during the planning cycle whilst communicating broadly strategic imperatives and data.
11. An ability to manage the dynamic development process through the provision of structured and relevant information from a wide range of sources to the planning process. This is done by providing in real time and within a framework, information that considers the current and prospective issues that should be considered in the planning process facilitating an environment of strategic management and promoting the cultural environment that encourages organisational learning.
12. An ability to consider the resource requirements and the benefits that would be derived from setting and achieving an objective and measuring progress toward achieving the objective in an on-going environment.
Other advantages of the invention will be evident from the subsequent discussion of its preferred embodiments.
Brief Description of the Drawings
Notwithstanding any other forms which may fall within the scope of the present invention, preferred forms of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:
Fig. 1 illustrates one form of construction of an entity interrelationship in accordance with the preferred embodiment;
Fig. 2 illustrates the overall organisational perspective utilised in the planning mode of the preferred embodiment;
Fig. 3 illustrates a table of planning sections and work areas to be constructed in each planning section in accordance with the preferred embodiment;
Fig. 4 illustrates one form of user interface for the entry of objectives into the planning database,-
Fig. 5 illustrates one form of user interface for the entry of measure of data into the planning database of the preferred embodiment;
Fig. 6 illustrates a form of user interface for the entry of funding details into the plan database of the preferred embodiment; Fig. 7 illustrates the process of risk analysis utilised in the preferred embodiment; and
Fig. 8 illustrates the process of locking information from one plan work area to another plan work area. Description of the Preferred Embodiment
The preferred embodiment of the present invention is implemented on a network personal computer utilising standard operating systems, language and user interfaces. For example, the embodiment can be ideally implemented in Microsoft's Visual C++ (Trade Mark) utilising a standard windowing systems such as Microsoft Windows NT (Trade Mark) or Microsoft Windows 95 (Trade Mark) .
The preferred embodiment is best implemented by means of a number of large adaptable database and various user interface programs which are constructed, in the normal manner to create, view and modify the contents of the database. Initially, an "entity database" is created of entities within an organisational hierarchy. The entity database is designed to have entities added and deleted at any time and for each new entity to be provided or added to the database. Preferably the entity database is constructed or amended only by a user having privileged access (such as a network administrator) . A user is prompted, by means of the user interface, for various details on the entity. These details can include prompts for the name of the entity, a description of the entity's nature and function, a entity type description which can for example, include such descriptions as business unit, company, department, division, joint venture, team, individual etc. Further, the entity entry contains a description of its relationship to the other defined entities. The nature of possible relationships can be user defined in an arbitrary manner and can include colleague, competitor, customer, joint venture partner, land lord, subsidiary, employee etc. Finally, the entity entry includes details on the entity including such matters as addresses, phone numbers, contacts etc.
Turning now to Fig. 1, there is illustrated an example layout 1 of entities eg. 2 as defined at the end of the entity definition phase. Although the actual entities and their interrelationship is totally user definable within the entity database, the form of entity database as shown in Fig. 1 is based around the core entity of the organisation 3. This entity 3 is related to external supplier, customer and competitor entities and itself includes a number of department entities each of which has a manager, a number of sections and with each section having a number of employee persons.
The next step in the preferred embodiment is to create a plan for each desired entity within the organisation.
Turning now to Fig. 2, the overall structure of an organisation is assumed to have an overall relationship as indicated 10. This can be divided into two main perspectives being the organisational perspectives 11 and the operational perspective 12. The operational perspective 12 is further divided into the fields of business activities 13, support activities 14 and project activities 15. Each of the perspective 11, 12 are further divided into a number of plan sections eg. 16 (vision and mission) , the operation of the planned sections being described further hereinafter.
As mentioned previously, an interactive plan database is then constructed having one current plan for each desired entity (in addition to historical plans and "work in progress" plans stored as required) .
Turning now to Fig. 3, there is illustrated the structure 20 of a single plan. The plan 20 includes, for each plan section (eg. vision and mission 21) a series of work areas 22 that need to be completed for that particular plan section, with a tick at the row - column intersection meaning that the column work area is required to be completed for the particular row plan section. The manner of building up a plan 20 is preferably "guided" by means of a user interface. However, ideally a user can enter the details for any plan section's work areas they require and the user interface preferably provides for such an adaptive form of data entry. Taking first the plan work areas 22 for the entry of information, they are as preferably follows: To Plan
The to plan work area differs from other areas in that it does not allow the entry of data but rather provides a list of prompts that the user should consider in working through each of the subsequent work areas for a particular plan section. Hence, the to plan work area provides a check list to ensure proper preparation for the entry of data into the selected plan section. The information could be provided via an interactive user interface and preferably is designed to be updated and amended during the life of an organisation. The prompts that should be considered in the planning process can be changed and accommodated to suit the needs of the user or groups of users in real time and to facilitate a highly interactive planning environment within an organisation. The use of amendable plans facilitates a dynamic planning environment within an organisation that promotes organisational learning and the development of a strategic management culture . The information that can be utilised within this task can be sourced from a variety of places and updated regularly. Current Work Area
The current work area provides a location for the storage of information relating to the current position of the entity. Preferably this information is entered within the computer system in a free text flowing form and can include text, charts, graphic information imported from other Windows applications. This, of course, includes the importing of information from other plan areas and from the plans of other entities. Intended Work Area This area is provided in the same form as the current work area and is provided for the entry of details of the desired position at the end of the plan period. Key Result Areas (KRA's) The KRA's are only defined for the limited plan sections being the strategic objectives and the business objectives. The KRA's are designed to give the organisation a focal point for developing performance measures against the strategic and business objectives. Typical KRA's include customer satisfaction, business development, revenue growth, innovation etc. The KRA's are preferably short and "succinct" and designed to capture, in a few words, the essence of strategic focus. For each KRA to be inserted in a list, its name and description are also preferably inserted. Objectives
In the objective work area, entry of the objectives set for the particular plan section is provided.
Preferably, details of the actions required to achieve each objective and the processes that will be affected by the objectives are also provided.
Turning now to Fig. 4, there is illustrated merely one form of user interface suitable for the entry of "objectives" information into the objectives database. The interface 40 includes a list of the currently defined objectives 41 with a currently selected objective having its name 42 and description 43 displayed. Means 44 is provided for adding further objectives. For each objective, a list 45 of actions required to achieve the objectives is provided with the ability to add 47, delete 48 or edit 49 the action information associated with the objective. Upon activation of the add action button 47 a further dialogue box can be provided for the addition of further actions, associated descriptions and various other relevant information such as target dates, responsibilities and authorisations as required, the information subsequently being stored with each action of a particular objective.
There is further provided 50 a list of the processes likely to be affected by the objective. The list of processes can be selected from an overall process type database which lists all the organisations business processes. A user can then select 51 processes from the overall global list which will be affected by a current objective .
Measures Work Area
In the measures work area, the key performance indicators (KPIs) for each objective are entered. These key performance indicators are then matched to the overall relevant key resource areas (KRAs) previously entered. Turning now to Fig. 5 there is illustrated one form of user interface for entry of KPI measures. For each objective in the objectives list 61, the key performance indicators for that objective is listed 62. Means can be provided 63, 64 for the adding or deletion of key performance indicators from a global KPI list. For each KPI within the list 62, means is provided for data entry 63 specifying desired targets. Also, means is provided 64 for the entry of key resource indicators that are relevant to the key performance indicator selected. Funding Work Area
The funding work area identifies the resources required to achieve each objective. Turning now to Fig. 6 there is illustrated one form of suitable user interface for the data entry of funding information. For each objective in the objectives list 71 a resource list 72 is provided in addition to means for the adding 73 and deletion 74 and editing 75 of the resource details. Various total information can be provided and further, data entry area 77 can be provided for the adding 78 and deleting 79 of incurred expenditures. Risk Work Area
The risk work area is used to detail the assumptions and perceived risks for each plan section. It provides a form of scenario analysis that is preferably capable of addressing impacts of invalid assumptions and the actions required for planning for such impacts . The risk area preferably operates by perceiving an organisations internal and external operating environment at any point in time. Preferably, the risks work area allows the construction of a hierarchical structure of assumptions and risk implications. Essentially, the risks work area can comprise a list of assumptions with each assumption having a structure 90 as illustrated in Fig. 7. For each new assumption 91, a user interface is provided for initially setting out the name and description of the assumption. Next, means as provided for attaching a list of new identifiable risks 92 for each new assumption. Preferably, an arbitrary number of new identifiable risks can be provided with again a name and description of the resultant identifiable risk also being provided. For each new identifiable risk eg. 93 there is preferably provided means for entering a list of risk impacts eg. 94 again in a name and description format. A probable date on which the risk may also be provided. Additionally, there is provided a means for relating the risk impacts to a list of relevant entities that will be impacted. Optionally, a list of performance measures that may be affected by the risk should it materialise may be provided. For each risk impact 94 there is preferably provided a means for entering a list of new risk actions 95 which allow for the entry of various actions to be taken as a result of the risks impacts including a name and description of the action, a responsible entity and an impacted plan section. Hence, the overall risk work area results in a hierarchical structure 90 that can include as much, or as little detail as required. In this way, a database of assumptions, their associated risks, their likely impacts and what actions should be taken can be constructed in advance allowing for a more holistic approach to risk assessment.
Returning now to Fig. 3, the various work areas are to be completed for each plan section eg. 21 as required. The plan sections are themselves divided into organisational and operational perspective with the organisational perspective recording the organisational profile, external environment, vision and mission, core values, strategic objectives and business objectives. Where the entity that is having a plan created for it is below the organisational entity, this information can be directly inherited from the plan for an organisational entity. Where the entity is inheriting information from another plan, that information can be preferably transferred or shared from any other plan in the structure. Information that is transferred or shared can be done so either in whole or in part and can be transferred to a specific plan or to a number of plans. Preferably, the entry of information into each work area is proceeded by the "to plan" section which details how to go about the entry process and what factors should be considered. This can be automated by automatically following the relationship of subordination to fill out the organisational perspective of subordinate entities.
Turning now to each plan section of Fig. 3, the organisational profile contains historical aspects of the organisation, the external environment provides an overview of the external operating environment and the factors that may impact on the organisation. In the risk work area of the external environment, the risks associated with the external environment assumptions that should be analysed. In the vision and mission section 21, a concise statement of the organisations business purpose should be set out and again the risks associated with the mission assumptions should be set out.
In respect of the core values section, these values can be documented in the current work area. Further, utilising the objectives, measures and funding work areas, documentation of how the core values are to be understood and demonstrated throughout the organisation and the extent to which the core values are shared can be monitored and assessed. In respect of strategic objectives, the strategic objectives of the organisation are set out. This includes the recording of the organisations key result areas (KRAs) with a similar process being undertaken for the business objectives section. Next, in respect of the operational perspective, records of the internal operating environment and its objectives and actions are kept. Preferably, there is a distinction made between those plan sections that directly support the organisations customers (the business activities) and those plan sections that indirectly support the organisation's customers (support activities) . In respect of the various business activities, the work areas are utilised to enter details in respect of the following:
* Revenue - sources of revenue for the organisation including sales, investment, grants, programs or funds, asset disposal. * Markets - managing sources of revenue and managing produces and services. Entry of the details of the advertising and promotion of the organisation and its products, services, pricing, location, market research and business development is provided. * Relationships - managing internal and external relationships, including staff, unions, customers, suppliers, capital markets, stockholders and shareholders, regulatory agencies, government etc.
* Operations - includes activities associated with the organisation of resources for the production or the delivery or products and services.
* Logistics - includes inbound and outbound activities such as purchasing, inventory management, transport and storage. * Research - includes all research and development activities up to the point of commercialisation. These include the development of new products and services, basic and applied research and the application of innovation to products and procedures. For some organisations such as universities and research centres, research activities may be a key product or service.
In respect of the support activities being those activities which indirectly support the organisation's customers, the following details are entered in each plan section:
* Human Resources - the organisation and deployment of a labour force. This includes remuneration, performance and reward schemes, training and development, recruitment and separation procedures, change management, occupational health and safety etc.
* Information Management - the organisation and facilitation of information. This includes technology, systems, hardware, software, platforms, robotics, reporting protocols, data management, consultation and support .
* Financial Management - budgeting, accounting, auditing, risk management. * Asset Management - managing the assets of the business required to produce revenue or provide a service. This includes acquisition and management of capital, and investment in land, buildings and equipment; including, asset utilisation, measurement, maintenance and disposal.
* Risk Management - the identification and management of all categories of business and personal risk.
There is also provided the plan sections for project activities including a project program, a new project plan and a new benchmark plan section area. The preferred embodiment treats the aggregation and funding of projects as integral to the planning and performance measurement process and applies a number of the work areas to each project activity.
The project program plan section provides a frame work for identifying, proving and managing the organisations development and benchmark projects in line with strategy. The new project plan section provides a management view of the scope of work required, background to the project and an identification of those persons sponsoring the project and forming the projects with the relevant details being entered within the corresponding work areas. The new benchmark plan section allows for the planning of new benchmark structures to be submitted for relevant the authorisation.
The performance measurement process can proceed for each entity by the extraction of the entity's indicators entered as part of each plan section's "measures" work area. These indicators can be collected together in a table. Preferably, a separate database of indicators is kept for each entity thereby constructing a performance database. Preferably, the performance database includes means for entering measurement data for each of the indicators where required. The performance data can be defined to be entered over arbitrary time intervals however, monthly time intervals are suitable.
Preferably, there is also provided a user interface to the performance database for the construction and graphing of the entered performance figures including means for constructing derived indicators which can be constructed from an arbitrary user defined factored combination of the entity's performance indicators, with full graphing and reporting facilities being provided. The user interface preferably also allowing the construction of models to test, and examine hypotheses as required. Alternatively, the performance measurements and data can be written out to a file and interactively interrogated by means of standard accounting software packages such as Microsoft Excel .
The preferred embodiment also preferably provides for the ability to benchmark one of an entity's indicators against any of the indicators of any other entity defined within the entity database. Upon entry of the data associated with each of the selected indicators, graphing and reporting functions are provided for the production of output reports highlighting the interaction of the indicators selected.
It would be understood that the preferred embodiment provides only a skeleton which can be utilised and adopted by an organisation to, over time, customise the application in accordance with requirements. In particular, each organisation will have its own reporting and analysis requirements depending on the functions carried out by the organisation. The preferred embodiment however, provides an integrated planning, performance measurement and benchmarking system which can be adapted to the needs of the organisation.
Further, the organisation's senior management can develop, over time, a series of benchmarks and indicators which they wish to utilise as prime indicators of the organisation's performance.
Further, when utilised in a computer networked environment by multiple users, the ability to lock data so that it can not be changed or perhaps even viewed by other parties is preferably provided. It will be evident that the preferred embodiment has particular application in a networked environment where multiple users can interactively edit their own plans. In a refinement of the preferred embodiment, there is provided the ability for one entity to lock data from, say entity A's work area into the corresponding area of entity B's work area. An example of this process is illustrated in Fig. 8 wherein the revenue plan section of entity B 100 includes, as normal, a current work area where free flowing text is entered. A "locking" user interface can then be provided for entity B 101 to lock the contents of entity A's revenue current work area 102 into the entity B's revenue current work area 100. In this way, entity A can ensure that entity B is aware of all of entity A's consideration on that particular issue in formulating its own current work area. Preferably, any updating of the entity A revenue current work area is further reflected in the entity B revenue current work area as well . In this way, entity B is encouraged to take a more holistic approach in its planning process. Preferably, in a multi-user organisation environment, there is provided the ability to arbitrarily lock information from work areas of one entity's plan to another entity's plan. In particular, locking the current, intended and objective work areas have been found to be particularly useful when utilising this feature.
As a further refinement, when operating in a multiČ user environment, there is preferably provided the usual security mechanisms, popular in modern operating systems of allowing each user to set security levels for the plan sections of their responsibility. This can include allowing or barring other users from reading or altering information contained in each relevant plan section.
It would be appreciated by those persons skilled in the art of computer programming that numerous variations and/or modifications may be made to the description as previously described particularly in the customisation of the user interfaces to the various databases and the customisation of the database in accordance with local requirements. These modifications and variations would not depart from the spiritual scope of the invention as broadly described. The present discussion therefore of the preferred embodiment is to be considered in all respects to be illustrative and not restrictive.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|WO1992007318A1 *||11 Oct 1991||30 Apr 1992||Iex Corporation||Method and system for planning, scheduling and managing personnel|
|WO1996010793A1 *||29 Sep 1995||11 Apr 1996||Yufik Yan M||Probabilistic resource allocation system with self-adaptive capability|
|WO1996030852A1 *||28 Mar 1996||3 Oct 1996||Hogan Systems, Inc.||Method of and system for financial institution budgeting and planning|
|GB2242292A *||Title not available|
|US5172313 *||10 Jan 1990||15 Dec 1992||Schumacher Billy G||Computerized management system|
|US5303147 *||24 Sep 1990||12 Apr 1994||Hitachi, Ltd.||Computer aided planning method and system|
|US5303166 *||14 Apr 1992||12 Apr 1994||International Business Machines Corporation||Method and system for automated network benchmark performance analysis|
|US5331545 *||1 Jul 1992||19 Jul 1994||Hitachi, Ltd.||System and method for planning support|
|US5406477 *||10 Jun 1994||11 Apr 1995||Digital Equipment Corporation||Multiple reasoning and result reconciliation for enterprise analysis|
|US5459656 *||26 Feb 1993||17 Oct 1995||Park City Group, Inc.||Business demand projection system and method|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|WO1998044440A1 *||27 Mar 1998||8 Oct 1998||Bellsouth Intellectual Property Corporation||A system and method for generating an invoice to rebill charges to the elements of an organization|
|WO1998044441A1 *||27 Mar 1998||8 Oct 1998||Bellsouth Intellectual Property Corporation||A system and method for associating services information with selected elements of an organization|
|WO1999059093A1 *||7 May 1999||18 Nov 1999||E-Talk Corporation||Performance evaluation tool and method|
|WO2000000937A1 *||30 Jun 1999||6 Jan 2000||Sun Microsystems, Inc.||Distributed budgeting and accounting system with secure token device access|
|WO2001009780A1 *||28 Jul 2000||8 Feb 2001||Da Vinci Innovation Pty Ltd||Management tool and method|
|WO2001039027A2 *||22 Nov 2000||31 May 2001||Accenture Llp||Decision management in a merger and acquisition environment|
|WO2001039027A3 *||22 Nov 2000||6 Dec 2001||Accenture Llp||Decision management in a merger and acquisition environment|
|WO2002048935A1 *||7 Dec 2001||20 Jun 2002||Skill Development Associates Ltd||Integrated business management system|
|WO2003077168A1 *||11 Mar 2003||18 Sep 2003||Akzo Nobel Coatings International B.V.||On-line benchmarking|
|WO2004053744A1 *||10 Dec 2003||24 Jun 2004||Bhp Billiton Innovation Pty Ltd||Evaluation system and method|
|US6072493 *||30 Mar 1998||6 Jun 2000||Bellsouth Corporation||System and method for associating services information with selected elements of an organization|
|US6125354 *||30 Mar 1998||26 Sep 2000||Bellsouth Intellectual Property Corporation||System and method for generating an invoice to rebill charges to the elements of an organization|
|US6418420||30 Jun 1998||9 Jul 2002||Sun Microsystems, Inc.||Distributed budgeting and accounting system with secure token device access|
|US6571235||23 Nov 1999||27 May 2003||Accenture Llp||System for providing an interface for accessing data in a discussion database|
|US6604084||1 Jul 1998||5 Aug 2003||E-Talk Corporation||System and method for generating an evaluation in a performance evaluation system|
|US6615182||1 Jul 1998||2 Sep 2003||E-Talk Corporation||System and method for defining the organizational structure of an enterprise in a performance evaluation system|
|US6671692||23 Nov 1999||30 Dec 2003||Accenture Llp||System for facilitating the navigation of data|
|US6671693||23 Nov 1999||30 Dec 2003||Accenture Llp||System for effectively collecting and disseminating data|
|US6901426||1 Jul 1998||31 May 2005||E-Talk Corporation||System and method for providing access privileges for users in a performance evaluation system|
|US6985872 *||10 Jun 2002||10 Jan 2006||Clicksoftware Technologies Ltd.||Method and system for assigning human resources to provide services|
|US7346529 *||7 May 2002||18 Mar 2008||David R. Flores||Method for developing an enterprise alignment framework hierarchy by compiling and relating sets of strategic business elements|
|US7716571||27 Apr 2006||11 May 2010||Microsoft Corporation||Multidimensional scorecard header definition|
|US7716592||30 Mar 2006||11 May 2010||Microsoft Corporation||Automated generation of dashboards for scorecard metrics and subordinate reporting|
|US7752144 *||24 May 2000||6 Jul 2010||Lockheed Martin Corporation||Multi-disciplinary information engine for total ownership cost estimation of complex systems|
|US7840896||30 Mar 2006||23 Nov 2010||Microsoft Corporation||Definition and instantiation of metric based business logic reports|
|US8190992||21 Apr 2006||29 May 2012||Microsoft Corporation||Grouping and display of logically defined reports|
|US8261181||30 Mar 2006||4 Sep 2012||Microsoft Corporation||Multidimensional metrics-based annotation|
|US8321805||30 Jan 2007||27 Nov 2012||Microsoft Corporation||Service architecture based metric views|
|US8495663||2 Feb 2007||23 Jul 2013||Microsoft Corporation||Real time collaboration using embedded data visualizations|
|US8606588||23 Nov 1999||10 Dec 2013||Accenture Global Services Limited||Merger and acquisition knowledgebase|
|US9058307||26 Jan 2007||16 Jun 2015||Microsoft Technology Licensing, Llc||Presentation generation using scorecard elements|
|US9392026||23 Jul 2013||12 Jul 2016||Microsoft Technology Licensing, Llc||Real time collaboration using embedded data visualizations|
|US20070265899 *||11 May 2006||15 Nov 2007||International Business Machines Corporation||Method, system and storage medium for translating strategic capabilities into solution development initiatives|
|28 Aug 1997||AK||Designated states|
Kind code of ref document: A1
Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE HU IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG US UZ VN YU AM AZ BY KG KZ MD RU TJ TM
|28 Aug 1997||AL||Designated countries for regional patents|
Kind code of ref document: A1
Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF
|30 Oct 1997||DFPE||Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)|
|19 Nov 1997||121||Ep: the epo has been informed by wipo that ep was designated in this application|
|21 Aug 1998||ENP||Entry into the national phase in:|
Ref country code: CA
Ref document number: 2290594
Kind code of ref document: A
Format of ref document f/p: F
Ref document number: 2290594
Country of ref document: CA
|17 Sep 1998||WWE||Wipo information: entry into national phase|
Ref document number: 1997903149
Country of ref document: EP
|4 Dec 1998||NENP||Non-entry into the national phase in:|
Ref country code: JP
Ref document number: 97529667
Format of ref document f/p: F
|24 Dec 1998||REG||Reference to national code|
Ref country code: DE
Ref legal event code: 8642
|10 Nov 1999||WWP||Wipo information: published in national office|
Ref document number: 1997903149
Country of ref document: EP
|3 Sep 2002||WWW||Wipo information: withdrawn in national office|
Ref document number: 1997903149
Country of ref document: EP