Building Management System Command Annotation Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current building management systems lack efficient user interfaces and data management capabilities, particularly in annotating commands and generating reports, as well as effectively representing and managing diverse building equipment configurations.

Innovation Solution

A building management system with a system manager that includes a user interface for command input, annotation, and report generation, along with graphical representation of equipment, allowing for annotation storage, equipment definition, and dynamic graphic assignment based on device characteristics, enabling users to create and manage aliased and exception graphics for equipment types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a building management system implements basic command control functionality, then the system can control building equipment, but it lacks efficient data management capabilities for annotating commands and generating reports

Engineering Contradiction:
Improvecommand annotation capabilityVSAvoidsystem structure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements an annotation box nested within the command control interface. When a user issues a command, an annotation box appears embedded in the same interface, allowing users to add notes without leaving the command control screen. This nested structure preserves command annotation capability while avoiding the need for separate annotation software or complex multi-application workflows.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Loss of information

If the system stores detailed annotations for every command, then comprehensive reporting capability is achieved, but data management complexity increases

Engineering Contradiction:
Improvecommand history and annotationsVSAvoiddata management structure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The annotation database serves multiple functions: it stores annotations for individual commands, generates equipment-specific reports by filtering annotations related to specific equipment identifiers, and provides comprehensive system-wide reporting. This multi-functional design allows the same data structure to support both detailed tracking and various reporting needs without requiring separate storage systems for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments annotations by equipment identifier, allowing the system to retrieve and report only annotations related to specific equipment when needed. This segmentation enables efficient query performance and report generation by avoiding the need to process all annotations system-wide when only equipment-specific information is required.

Inventive Principle:
Principle #1Segmentation

3Measurement precision

If the system provides detailed graphical representation of each equipment type, then equipment monitoring accuracy is improved, but the complexity of managing diverse equipment configurations increases

Engineering Contradiction:
Improveequipment representation accuracyVSAvoidequipment configuration management
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates graphical copies (icons) that represent different equipment types. Each equipment type has an associated icon that visually represents its function or category. When equipment is added to the system, the appropriate icon is automatically selected and displayed, providing accurate visual representation without requiring complex graphical models or detailed specifications for each piece of equipment.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If the system allows custom annotation input for each command, then user flexibility is improved, but the ease of operation decreases due to additional input requirements

Engineering Contradiction:
Improveannotation customizationVSAvoidcommand input process
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The annotation box is optional and appears as an available feature rather than a mandatory field. Users can choose to add annotations when they deem necessary, but are not required to fill them out for every command. This partial action approach provides flexibility for users who need detailed annotations while maintaining ease of operation for those who prefer quick command entry without additional input.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10644897B2Building management system user interfaces
Publication Date: 2020.05.05 JOHNSON CONTROLS TECHNOLOGY CO
  • US10644897B2 patent drawing
  • US10644897B2 patent drawing
  • US10644897B2 patent drawing

AI summary

A building management system includes a plurality of devices of building equipment and a system manager. The system manager is configured to control the devices of building equipment and generate a user interface. The user interface includes a command widget configured to allow a user to input a first command to control a first device of the plurality of devices of building equipment and an add annotation box configured to allow a user to add an annotation to the command. The system manager is further configured to control the first device in response to the command and store the annotation in an annotation database.