Risk Management | QualiWare Center of Excellence

QualiWare contains a comprehensive set of features and functions to related to all aspects of risk management.

Risk Management in QualiWare
Risk Menu
Risk Management Desktop
Business Continuity Management
Video Highlights

Risk Management in QualiWare

A risk can be associated to any type of object in the repository.

In QualiWare a Risk can be :

Associated to one of more objects, e.g a process (concerns)
Has a responsible person (HasResponsible)
Has a type (Type)
Associated to a risk category (HasRiskCategory)
Be reduced by a Control (Reduce)

A Control:

Is an activity in a process
Can be documented in an evaluation

Risk Menu in QualiWare

The Risk menu contains a set of lists of overviews, that supports the risks from identification, assessment, mitigation and monitoring.

Risk Management Desktop in QualiWare

The Risk Management desktop in QualiWare provides the user with fast access to all essential features related to all aspects of risk management.

Read more about the Risk Management Desktop here

Business Continuity Management

QualiWare 10.3 supports the development and implementation of a business continuity management system supporting ISO 22301. The new features are positioned under the Risk menu and contains four major deliverables:

Business Impact Analysis
Resilience Plan
Recovery plan
Contingency Plan

– as well as a series of relevant analysis report.

Read more about the Business Continuity here

Video Highlights

This video walkshrough the business continuity management elements in QualiWare.

Account Context Diagram

The purpose of the Account Context Diagram is to enable financial risk management by illustrating which processes create transactions on a given account, and which risks are related to this transaction.

Clustering

Clustering provides users with a new way of interacting with content in their repository. It provides an enhanced analysis capability directly from the 3D Visualizer by logically grouping objects based on their relationships, concepts, and definitions. Filters can be applied to the clusters through the table-based view using existing functionality to focus analysis efforts (for example only clustering objects that are related to a risk with a high impact). The number of clusters can also be defined by the user to provide a broader or more concise result.

API Architecture Metamodel

An Application Programming Interface (API) is a construct that enables communication between systems. Integration between systems in complex environments continues to be a business priority to support automation activities. An API can be purpose-built for a bespoke integration (typical of legacy systems), or alternatively a standard connector can be developed between industry standard systems such as ERP’s and Service Management platforms. Managing these integrations becomes a complex operational task as updates and new releases to the integrated systems (and enabling technologies), can lead to intensive release management and testing activities. Security is also of utmost concern when managing integrations as the API provides a potential entry-point from either system integration direction – the API has become a preferred target for malicious attacks on systems and networks.