CorPeuM software has been architected to support a continuous approach to planning that encompasses the processes of strategic planning, tactical planning, financial planning, forecasting, management reporting, statutory reporting and risk management.
The CPM cycle typically starts when management of an organization decides on the strategic plan for the next 3-5 years. This strategic model contains objectives, strategies and financial guidelines that form the basis for the CPM processes that follow.
The tactical plan model is developed during the tactical planning process where initiatives, projects and investments that are needed to reach the strategic objectives are assessed. To each element of the tactical plan, resources, outcomes, milestones and priorities are assigned.
The financial plan or budget is simply the financial translation of the tactical plan. It summarizes the financial impact of the decisions made during the planning process and serves as a control mechanism during the execution of the plan.
The forecasting and management reporting processes enrich the strategic, tactical and financial planning models with actual and forecast figures. These are delivered through scorecards, dashboards, reporting packs and briefing books that allow internal and external consumers to review performance and make decisions on adjustments to the various plans in order to keep the organisation on track.
CorPeuM contains all the components necessary to support this cycle in a single application. Over time a range of functionality will be released that enhances specific processes that will increasingly set CorPeuM apart from other solutions.
The CorPeuM interface is the same whether the user is an administrator involved in setting up and maintaining an application, or they are just involved in entering data and running reports. The interface runs in most web browsers (e.g. Internet Explorer, Firefox) and on most operating systems (e.g. PC Windows, Mac)
CorPeuM employs a modern technology architecture that uses Microsoft SQL Server as its BI platform. On top of this is the CorPeuM Platform contains all services to manage users, processes, data and business logic.
CorPeuM Functionality provides specialised capabilities to support the different CPM processes such as strategic planning, tactical planning, budgeting, etc. while companies can use these capabilities to build their own custom applications, for example detailed sales analysis or a costing application.
The Reporting and Analysis layer allows all available information within CorPeuM to be analyzed and reported via the web or Excel.
The CorPeuM platform is composed of functionality-rich, predefined components for modelling, process management, reporting and security. A CorPeuM application is built by combining components into models, processes and reports.
CorPeuM has a central calendar upon which organisations can build the various calendars in use throughout the organisation. For example, some information may need to be planned weekly, while others are monthly. For retail, the concept of seasons are important as well as knowing when the various public holidays occur which could impact business.
CorPeuM allows organisations to set up as many calendars as required and then using how these link to the internal calendar, is able to combine data across calendars.
This means CorPeuM can support organisations where divisions may have different year-ends to the corporate year-end.
Each User who accesses CorPeuM has a User Passport assigned to them. This Passport references all the information relative to the roles of the user, the data they can access, what functionality they can use and their own personal settings. The latter includes their contact details and the language they wish to use when accessing CorPeuM.
Roles are part of a user’s passport and defines how they participate in the various processes defined in CorPeuM. Each user passport can contain multiple roles. A role can, optionally, have one or more dimension members as parameters.
Role hierarchies define an approval process or an escalation path should a particular task not be completed. These hierarchies can differ between dimensions and members.
The management processes of planning, budgeting, forecasting and reporting consist of a series of tasks that must happen in the right order. In most organisations, menus are used to direct and control users through these tasks. In contrast, CorPeuM was designed with built-in process management capabilities that are totally integrated into all aspects of the product and provides a far more flexible and effective way of leading users through the actions they need to perform. These capabilities include:
Screenshot 1: Example of a to do list
Screenshot 2: Example of a Process driven Project.
Results are reported in CorPeuM through Reporting Models, which combine data from data models as well as other reporting models. Reports can include grids of data, charts, dashboards and special visual components such as strategy maps. Multiple reports can be combined into books, which can then be published as either static reports where the content reflects ‘a point in time’, or dynamic so that the results shown come from the latest results held in the reporting model. When creating a reporting model, users can select the data as it was during any part of a process, which makes it ideal for creating detailed audit reports that show how data has changed from one activity to another.
CorPeuM users a ‘block’ concept to producing reports. These blocks can consist of dimensions and members, which are then positioned on a page as rows, columns and pages of a report. This greatly simplifies the creation of reports and allows complex row and column combinations not possible with other reporting systems.
Trail The ability to track a number from input to final result is essential for financial audits as well as for checking how a budget or actual value was arrived at. Just as important is the ability to see the impact of change from one period to another and how summary results have been impacted by a structure or accounting change. Good corporate governance requires such tracking.
Process Audit Trail
Each step in a process stores its modifications and adjustments to existing values as increments, together with information about process, task, user and time of change. This means that a step in a process will never overwrite the values collected by a previous step or other processes, but it will store the difference with the previous value. This way of storing values allows for a full audit trail of every value in the system and also provides full or partial roll-back of a process.
Structure Audit Reporting
As well as monitoring how data has been transformed through the different management processes, CorPeuM also tracks how model structures have changed over time. This information can be used in reports where results can reflect the latest version of a dimension, the structure at a specified point in time, or how dimension structures have changed over time.