Deviations

Identifying and resolving service resources that fail to reach their target states.

What is a Deviation?

A deviation occurs when a service resource fails to reach its target state after the service is enabled. When you enable a service, its resources should transition from disabled to enabled (or to another specified target state defined in the service commissioning file). The service commissioning file contains detailed specifications of all resources and their required states for proper service functionality.

However, various issues (such as hardware failures, network problems, or configuration errors) can prevent resources from achieving their intended states. When this happens, the affected service is marked as deviated.

Identifying Deviated Services

Cybus Connectware provides multiple ways to identify and investigate deviations:

Deviation Notifications

When a deviation occurs, a pop-up notification appears in the Admin UI. This notification provides an immediate alert that one or more services are not functioning as expected.

Deviation notification

• To view all deviated services, click the down arrow in the notification panel. This expands the list to show all services currently experiencing deviations.

Deviation Indicators

Deviation status is also displayed in multiple locations throughout the Admin UI:

• In the Service Overview

• Within the Service Details view for individual services

• In resource lists for affected services

List of Deviations

When you click on a deviation warning message, the system displays a detailed list of resources whose actual states differ from their expected states:

Deviated resources showing state discrepancies

Examining Deviated Resources

For a comprehensive analysis of which specific resources are causing the deviation:

1. Click on the deviated service name in the services list

2. Navigate to the Deviations tab for that service

3. Review the detailed comparison between expected and actual states for each resource

Deviations tab displaying expected vs. actual status for each deviated resource

Resolving Deviations

When addressing deviations, focus on:

1. Identifying the root cause (hardware, network, configuration)

2. Resolving the underlying issue

3. Re-enabling the service to verify the resolution. See Enabling Services.

Persistent deviations may require additional troubleshooting or consultation with your system administrator.