anchor.diff:  | `Indeterminate` | _1_            | Light green / `#990` | No Severity could be associated with this event.
   |===
   
  -==== Calculation of the operational status
  +=== Calculation of the operational status
   
   The operational status of a _Business Service_ is correlated in two steps.
   First, the status of each contained element is mapped to the _Business Service_.
   For _Reduction Keys_ and _IP Services_ the status is based on their alarm status.
   For contained _Business Services_ the operational status is used.
   
  -===== Map Functions
  +==== Map Functions
   
   The mapping can be performed by one of _Map Functions_ listed below:
   
  -.State calculation _map functions_
  +.State calculation _Map Functions_
   [options="header, autowidth"]
   |===
   | Name       | Description
  
positive.code: | `Ignore`   | Ignores the severity of the managed entity
  |===
  
  ===== Reduce Funtions
  
  Finally, the list of mapped status values are then aggregated into the operational status of the _Business Service_.
  For this operation the following _Reduce Functions_ are available:
  
negative.code: | `Threshold`     | Uses the highest severity found more often than the given threshold.
  |===
  
  ==== Operational status changes
  
  If a _Business Service_ changes its operational status an _OpenNMS_ event of the type `uei.opennms.org/bsmd/serviceOperationalStatusChanged` is fired.
  The log message of the event contains the name of the _Business Service_.
  Additionally, the previous operational status and the new operational status are included.
  Please note, that this event has no node, interface or service associated.
  
  === Business Service Daemon
  
  Internally the _Business Service Monitoring_ feature is driven by the _Business Service Daemon_ (bsmd).
  It is responsible for tracking the operational status of all _Business Services_ and for sending events in case of operational status changes.
  Every time the configuration of a _Business Service_ is changed a reload of the daemon's configuration is required.
  This includes changes like the name of the _Business Service_ or its attributes as well as changes regarding the _Reduction Keys_, contained _Business Services_ or _IP Services_.
  
  ==== Reloading configuration
  
  A configuration reload can be initiated by an `uei.opennms.org/internal/reloadDaemonConfig` event with the parameter `daemonName` set to `bsmd`.
  If the reload of the configuration is done an event of type `uei.opennms.org/internal/reloadDaemonConfigSuccessful` is fired.
  The following options to trigger a configuration reload are available:
  
  * Use the `Reload` button on the `Manage Business Services` page in the administration section of the web UI.
  * Send the `reloadDaemonConfig` event directly to trigger the reload
  * Use the `send-event.pl` script
  
  [source,shell]
  