KLUSA offers many possibilities to map company-specific processes, methods and roles. You can switched on or off entire project management methods, such as risk management. The administrator can make the most of these modifications by himself in KLUSA.
KLUSA is growing with your project management organization. For instance, the organization starts with a few roles and the central methods such as work breakdown structure and schedule. Additional methods such as resource management, cost management and risk management can be gradually added.
If the company wants to implement the project portfolio management as a further stage of maturity, then KLUSA also offers the necessary tools for this purpose: benefit analysis, project priority in portfolios and scenario analyzes.
The elements of the project management process that have effects on the tool are essentially:
- Roles and their responsibilities in the process
- Process flows, typically for project approvals and change requests
- Project management methods (e.g. cost management, risk management)
KLUSA offers a high level of flexibility in order to meet the customizing of the individual requirements and processes. In KLUSA, the parameter for this purpose are:
- Permissions (who is allowed to do what?)
- Structuring the information (who gets what information?)
- Definitions of fields (How is it called?)
- Portals to use KLUSA in different departments with different authorizations and notions
- Instance-wide activation or deactivation of modules, functions, and fields
Roles and rights
Roles are speaking and intuitive terms with a professional and functional meaning defined by the company. Examples include project managers, resource managers (typically department managers), controllers or team members.
You can define for each role, which objects can be edited or read in KLUSA. Usually, a project manager can write data of his project, but a team member only has reading access.
KLUSA comes with installed standard rolls. You can adapt and customize these roles respectively. Of course, you can create new roles can based on detailed rights. You can change and extend roles at will and at any time. Thus, you can add more differentiated roles at a later stage, in order to introduce, for example, the role of the work package managers.
Portals divide an instance and form specific project groupings. For instance, you can use portals to assign different departments to different units in KLUSA.
Thereby, each project is assigned at least to one or more portals. You can view and edit a project only in those portals where it is assigned.
Portals also include resource pools. Thus it is possible to make resources visible for only one portal or to make them available system-wide.
Portals allow the structuring and arranging of a complex and large number of projects. A company division thus only works with the relevant projects and is not bothered with data from other divisions. Important: The view of all projects of all portals is not lost and remains fully preserved for higher management.
The KLUSA Customizing offers the following changes:
- Provide customer-specific templates for Microsoft® Excel, Word, PowerPoint, Print templates, etc.
- Switching on / off functions instance-wide (make them visible / invisible); you can already switch on / off many features completely via catalogs and rights
- Renaming field labels to customer-specific terminology
- Adaptation via entire configuration sets or individual configuration keys