Determine if mode has not changed at least once during the course of a week

Applicable Systems

  • Primary: AHU, RTU, MUA, ERV

Objective/Method/Outcome

  • Objective: Determine if mode has not changed at least once during the course of a week
  • Method: Monitors the mode TL, and generates an insight if the mode has not changed at least once during the course of a week.
  • Outcome: An insight is generated if the equipment mode hasn’t changed over the week.

Logic

The logic flow starts by taking the Mode data and using the Delta block to check out the possible changes in the input value. If the number of changes is lower than one time per week, an insight will be triggered

   {
   if ((Agg(Mode(sample n+1)-Mode(sample n)) < 1 time/week), Insight_Flag, No_Insight)
   }
Determine if mode has not changed at least once during the course of a week

Description / Method

Monitors the mode TL, and generates an insight if the mode has not changed at least once during the course of a week (user adjustable).

  1. Review mode change sequence.

Message

Mode of operation has not changed at least once for this week. Please review mode sequence.

Notes

All thresholds are adjustable. Please note that the aggregation interval can be changed from weekly aggregation, as required (example: daily aggregation) by editing the Aggregate Block [24]. The rule has been designed to determine if the faulty condition is true when the first set of samples for the seventh day arrive in Kaizen. The rule also generates a CTL to store the count of mode changes every day.

Default Values for Constants

  • Weekly_Threshold: 1

Rule Template Type

  • Insight Type: Fault Detection
  • Trigger Type: Active High

Default Priority

Medium

Inputs

Inputs Units Default Value Tags Description
Mode     mode Occupancy Indicator
Weekly_Threshold   1   Minimum number of times mode change should occur without triggering an insight