Skip to content

Electrical System Type

This rule checks whether Electrical Systems in your model have a valid and appropriate System Type assigned.

⚠️ Systems with an undefined or incorrect type may be excluded from documentation, quantity takeoff, or clash detection—and can cause misinterpretation during IFC export or downstream coordination.

What Is Checked

DAQS verifies the value of the System Type parameter for electrical circuits. Each circuit must belong to one of the defined system types, depending on its purpose and design intent.

  • Systems marked as UndefinedSystemType are flagged as incomplete.
  • Optional: your model can be configured to allow or disallow specific types depending on the project or company standards.

Accepted System Types

Member Name Description
UndefinedSystemType System has no assigned type (⚠️ should be avoided)
Data System used for data transmission (e.g., network cabling)
PowerCircuit Standard power supply system (lighting, sockets, etc.)
Telephone System used for telephone infrastructure
Security Security-related electrical systems (e.g., access control, cameras)
FireAlarm Fire detection and alarm system
NurseCall Patient alert and response systems (typically in healthcare projects)
Controls Building automation and control systems
Communication General communication infrastructure
PowerBalanced Balanced power circuits (often three-phase)
PowerUnBalanced Unbalanced power circuits (e.g., single-phase circuits)

Why This Matters

Assigning the correct system type ensures:

  • Proper grouping and filtering in schedules
  • Accurate load calculations and panel assignments
  • Logical separation of services for coordination (e.g., separating FireAlarm from Power)
  • Correct classification during IFC or COBie export

How to Fix

  1. Select an electrical circuit in the model.
  2. Open its Type Properties or check the System Type field in the Properties palette.
  3. Choose the appropriate system type from the dropdown list.
  4. Repeat for other circuits as needed, or use schedules to bulk-edit where possible.

💡 Tip: If your project uses custom system types or tags (e.g., for telecom or specialty systems), let DAQS know so the rule can be extended accordingly.

Best Practice

  • Avoid using UndefinedSystemType — every system should reflect its real-world function.
  • Set system types as part of your company templates or family types to ensure consistency across projects.