By role
AI for building services: reconcile systems, schedules and briefs
Start with one system and two conflicting documents. A useful result shows the exact source of each difference and the engineer who needs to resolve it.
Contents · 5
Most of this guide is general practice for working with any AI assistant on building-services documents. ARAI's own part is the drawing: it reads, checks and edits DWG/DXF files and answers building-code questions with sources. System design, load calculations and equipment selection stay with the engineer and their design software.
Start where information crosses a discipline boundary
An air-handling unit changes, but its old electrical load remains in the power schedule. A riser is renamed on the plan and keeps its previous tag on the schematic. These are useful first tasks for AI in building services: compare supplied records and return a short, traceable list of differences.
Choose one system rather than uploading an entire project and asking whether it works. For HVAC, that might be a system schematic, equipment schedule and electrical information request. For plumbing, use a riser diagram and valve schedule. For electrical work, compare the load list with the distribution schedule. Each comparison needs a defined relationship, not merely similar words.
The output should distinguish an actual contradiction from missing evidence. “Not found in the supplied schedule” is defensible. “Missing from the design” requires a wider search. Include unreadable pages and unmatched tags so that a clean-looking report cannot conceal an incomplete comparison.
Assemble a small, versioned input package
Use documents from one agreed issue, or explicitly ask for a change comparison between two issues. Record filename, revision, date, authoring discipline and status. A supplier quotation is not automatically the approved equipment selection.
Keep identifiers intact. AHU-01 and AHU01 may refer to the same item, but do not silently merge them. The matching key might need building, level, zone and system as well as equipment tag. Include the project's approved naming exceptions.
| Input | Essential context | Useful output |
|---|---|---|
| Equipment schedule | Revision, selected configuration, units | Missing or conflicting fields |
| Electrical brief | Installed and design loads kept separate | Changed consumers and open questions |
| Schematic | System boundaries and operating modes | Unmatched tags and connections to inspect |
| Supplier data | Exact model and dated document | Requirement-to-evidence comparison |
Export tabular data where possible, retaining row identifiers. A legible sheet crop helps resolve an ambiguous symbol, but does not establish hidden geometry or prove that a route is buildable.
Check units before comparing numbers
Flow in litres per second and cubic metres per hour can describe the same duty. Record original units, the conversion used and the normalized value. Keep pressure, electrical power and thermal capacity in separate fields. A missing value is unknown, not zero.
Operating modes also matter. Normal, standby, smoke-control and maintenance conditions should not become one total. Let the responsible engineer define which consumers operate together and which design method applies. AI can organize the input and identify omissions; a plausible sum does not establish the design load.
For equipment selection, use the actual manufacturer's data for the proposed configuration. Ask for page references against each requirement: duty point, supply, dimensions, maintenance access, controls and accessories. An absent curve remains an unanswered selection question.
A prompt for an equipment substitution
Suppose an illustrative replacement unit lists a 3 kW fan motor and a 12 kW heater, while the earlier electrical brief lists a 2.2 kW motor. The task is to identify changed inputs before the electrical engineer updates the design.
Compare AHU-01 in the electrical brief revision C and supplier schedule revision D. Preserve original values and units. Identify changed consumers, source pages and missing operating-mode information. Do not calculate a design load or select protective devices. Return a discrepancy table and a revised information request for review.
A useful answer identifies the motor change and newly listed heater separately. It may state that the two listed ratings sum to 15 kW, but cannot label that sum the feeder design load without the remaining inputs. Review the exact product configuration before passing the brief to another discipline.
Close the information loop
Give each confirmed issue an owner, required response and affected documents. After the supplier or engineer answers, update the source schedule and issue the revised brief. Then check downstream references: the narrative specification may still describe the superseded unit.
Keep calculation results tied to a reproducible calculation file and accepted assumptions. Any regulatory check needs the project's jurisdiction, applicable edition and actual source text. Interface language does not select those requirements.
ARAI works with DWG/DXF drawing information; that is a practical next step when a coordination question concerns drawing geometry. Start with a bounded request to identify the relevant objects and available measurements, rather than ask it to design a complete HVAC or electrical system. Prepare a drawing question in ARAI. For the reporting structure, see AI drawing checks.
Ask ARAI about your project
Prepared by ARAI’s editors with AI assistance. Product information was checked against official sources as of the update date. Report an error at hello@arai.build.