Log In

Commissioning

PART II: Structuring Projects and Digital Twins

Session 8: Tagging Objects and Activating Fault Detection

Course Code: CB-04
Goal: Prepare Digital Twins for real-time operational monitoring and Auto-Commissioning by tagging objects and activating fault detection analytics.

Session Overview

Duration: 1 Hour
Format: Instructor-led (via Microsoft Teams or in-person)
Level: Intermediate (Ideal for commissioning engineers, system integrators, and field technicians)

Resources Provided:

  • CUBE Box Tagging Protocol Guide
  • Fault Detection Activation Best Practices
  • Common Fault Triggers and Diagnostics Sheet
  • Tagging and Normalization Protocols Overview

Learning Objectives

By the end of this session, participants will be able to:

  • Apply tagging protocols for points such as Inputs, Outputs, and Calculated Points.
  • Normalize point names and values across different manufacturers for consistency.
  • Implement best practices for activating fault detection analytics.
  • Review field examples of real fault triggers and diagnostics.

Session Agenda

CB4.1 Tagging Protocols for Points: Inputs, Outputs, Calculated Points
  • Understanding Point Types:
    • Explanation of different point types in BMS systems (Inputs, Outputs, and Calculated Points).
    • Importance of tagging points for operational clarity and monitoring.

  • Tagging Protocols:
    • Overview of CUBE Box’s tagging protocols for various point types.
    • Step-by-step guide to tagging points in CUBE Box, including naming conventions and best practices for consistency.
CB4.2 Normalizing Point Names and Values Across Different Manufacturers
  • The Need for Normalization:
    • The challenges of working with devices from multiple manufacturers that use different naming conventions.
    • Why normalization is essential for smooth system integration and fault detection.

  • Best Practices for Normalizing Names and Values:
    • How to standardize point names and values to ensure consistency across systems.
    • Techniques for handling discrepancies in point definitions between devices from different vendors.
CB4.3 Best Practices for Activating Fault Detection Analytics
  • Overview of Fault Detection:
    • What is fault detection and why it is critical for real-time system monitoring.
    • How CUBE Box uses fault detection to identify operational issues before they escalate.

  • Activating Fault Detection:
    • Best practices for enabling and configuring fault detection analytics for various systems in CUBE Box.
    • Key settings and thresholds to consider for accurate fault detection.
CB4.4 Field Examples: Reviewing Real Fault Triggers and Diagnostics
  • Real Fault Examples:
    • Review field examples of common fault triggers, such as sensor malfunctions, system misconfigurations, or environmental changes.
    • Discuss how fault detection identifies and diagnoses these triggers in real-time.

  • Fault Diagnostics:
    • Understanding how CUBE Box presents diagnostics and actionable insights for resolving faults.
    • How to interpret diagnostic information to make timely corrective actions.

Hands-On Preview (Optional if time allows)

  • Tag a sample system’s Inputs, Outputs, and Calculated Points in CUBE Box.
  • Normalize point names and values for a multi-vendor system.
  • Activate fault detection and review a sample fault trigger and diagnostic report.

Post-Session Action Items

  • Review your system’s point tagging to ensure it follows standard protocols.
  • Normalize any inconsistent point names or values across your system.
  • Activate fault detection analytics for critical systems and verify their effectiveness.
  • Practice diagnosing real fault triggers in the system using CUBE Box diagnostic tools.

 Note: When scheduling, make sure to include this session code: CB-04.

Schedule Your One-to-One Session
Go Back to Commissioning Full Training