Asset Management Desktop | QualiWare Center of Excellence

Being on the Asset Management Desktop, Architects and Business Users can define strategic asset management plans including objectives, capabilities, processes and improvements. Document the full asset portfolio originating from investments, products, equipment and applications. Configure the QualiWare GO augmented reality app, to make sure assets and related documentation are readily available when required.

Desktop Journey

With QualiWare’s purpose driven desktops, users are enabled to have centralized workspaces for each area within the QualiWare Enterprise Architecture and GRC platform. Doing so allows users to use preconfigured reports and dashboards as they populate their repositories and start on their respective journeys. The journeys all carry a methodology of Plan, Do, Check, Act which encapsules:

Getting Started for content creation, and import of data
Overview for establishing overview and maintaining relationships
Evaluate for analyzing the content from different perspectives
Planning, communication and review for creating change initiatives, tracking and implementing change

Getting started

Each Desktop has a “Getting Started” tile that provides easy access to the most relevant features in relation to the focus on the desktop.

Strategic Asset Management Plan

Each Desktop has a “Getting Started” tile that provides easy access to the most relevant features in relation to the focus on the desktop.

Read more about the Desktops

Explore the general introduction to desktops using the links:

Asset

The Asset object enables you to keep track of your assets, their status and maintenance procedures

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.