AiMidWare

BUILDING AUTOMATION

Investigating a building-system fault

For a building-systems professional working across configuration files, documentation and observations.

A room’s wall switch does not operate its intended lights. The project file, device documentation and installer’s observations contain the information needed to investigate, but the relationships must be understood together.

Illustrative designs with invented inputs. They explain possible applications, not completed AiMidWare customer projects or currently available products.

Sample inputs

Intended function
The office wall switch should operate the office lighting group.
Project configuration
The switch sends to group address 1/2/10; the office lighting actuator listens on 1/2/11.
Observed behaviour
The actuator responds to its local test. It remains unconfirmed whether the deployed configuration matches the project file.

ILLUSTRATIVE RESULT

A configuration mismatch to investigate

Finding
The switch and intended actuator do not share the configured group address.
Working explanation
The mismatch could explain the symptom. The project file alone does not prove the live system is configured this way.
Next investigation
The integrator verifies the deployed configuration and relevant device traffic, then decides whether and how to correct it.

How the example works

  1. Data and tools

    Read the project data and relevant manuals. Extract device relationships and use deterministic checks to compare addresses, functions and configured links. Keep the source of each finding available for inspection.

  2. AI reasoning

    Connect the installer’s description with the configuration and documentation. Identify the address mismatch as a plausible cause, consider alternative explanations and determine what evidence would distinguish them.

  3. Deliverables and checks

    Produce an annotated relationship view and a focused diagnostic sequence. Show the relevant configuration entries, the proposed explanation and the checks needed before changing a live installation.

  4. Updates and follow-through

    As the professional records test results, update the diagnosis and the proposed next step. If the project file is stale, resolve that discrepancy before treating it as a reliable description of the installation.

Where a person contributes

The responsible professional confirms the diagnosis and controls changes to the installation. This example provides analysis and guided investigation; it does not assume authority to operate building equipment.

The business opportunity

AI can help an integrator work through project records and device documentation, while software checks the configuration for specific errors. The potential is shorter investigation time, more consistent technical work and a reusable diagnostic capability, delivered as a professional service or application.