Customizing TBSM views to add information from System Automation

The EEZ_SystemAutomationResource service template contains text-based incoming status rules which retrieve the System Automation Observed State and other System Automation specific states of a resource. This information can be used in TBSM Views in order to enrich service instances with information coming from System Automation for Multiplatforms.

The following text-based incoming status rules are available:
Table 1. Text-based incoming status rules for TBSM
Rule Name Description
SAObservedStateValue Retrieves the field SAObservedState from a resource status change event.
Possible values:
  • Unknown
  • Online
  • Offline
  • Starting
  • Stopping
  • NotApplicable
SADesiredStateValue Retrieves the field SADesiredState from a resource status change event.
Possible values:
  • Online
  • Offline
  • NoChange (i.e. the resource’s automation goal cannot be changed by an operator)
SAOperationalStateValue Retrieve the field SAOperationalStateValue from a resource status change event. List of Operational State values giving more fine-grained information about the current state of the resource. For a list of possible values, see the SystemAutomation.baroc file.
SACompoundStateValue Retrieve the field SACompoundStateValue from a resource status change event. Compound State indicating whether the resource is working as desired or has encountered an error. Possible values:
  • Ok
  • Warning
  • Error
  • Fatal
SAExcludedFromAutomationValue Retrieve the field SAExcludedFromAutomationValue from a resource status change event. Flag indicating if the resource is excluded from automation (i.e. automation is suspended).
Possible values:
  • NotExcluded
  • Excluded