Service-level management

Formalize and automate the management of business and IT services to increase delivery quality and minimize delivery costs

The provision of services for external customers or internal departments is a central task of an IT organization. Versio.io supports IT organizations in the automated management of IT services to increase the delivery quality and minimize the delivery costs.

Service detection & documentation

Service discovery and continuous documentation of service configuration is the critical foundation for executing service management.

Versio.io offers you a full-stack service discovery auto-mechanism. The service topology can be extended with service components from other data sources (cloud provider, IT service management) to achieve a complete picture of the service.

All components as well as the topology are historized. This means that you can view the state of the service at any desired point in time.

The term 'service' is often understood differently by different people. Attached are a few examples of what we consider a service to be:

Application (e.g. CRM application)
Application programming interface (API, e.g.)
Batch-job (e.g. billing, backup)
Infrastucture components (e.g. host, virtual machine)
Network
Business service (e.g. first level support)

Service change monitoring

To manage a service it is necessary to perceive its changes in order to be able to react to them.

Versio.io continuously captures the state of each component of a service and can thus detect the change. In the Versio.io Operation Diary all changes are filtered and displayed transparently for all service components.

Service governance & compliance

The change of a component of a service can affect its delivery quality or its cost.

Versio.io offers the possibility to verify any change according to customer-specific functional, operational or security-relevant requirements. It can detect and document the occurrence as well as the resolution of a violation. On the basis of corresponding events, customer-specific alerts can be executed.

Practical examples of how to verify a service change:

Operational requirements (naming conventions, anti-pattern configuration etc.)
Identify known IT vulnerabilities
Detect outdated product versions of service components
Detect product versions no longer maintained or serviced by the manufacturer

Service root cause analysis

When the service provided is compromised, you want to quickly identify the root cause of the problem.

Versio.io offers two options to identify the root cause. The first one is the Operation Diary, which shows you the change in the period of the problem. A change can be the trigger of the problem.

Furthermore, Versio.io can verify the content of each change and thus identify and alert an unwanted condition in business real-time.

Service level agreements & objectives

Customer and service provider define by means of service level agreements (SLA) and service level objectives (SLO) the delivery quality of the service to be provided.

Versio.io records the SLA and the associated SLOs. Through historization, Versio.io can capture and downstream process SLO compliance over time. Furthermore, a fully automated cost allocation of the SLA/SLO violations is given.