Stomra Guides

OpenEik · Guide

Electrical in OpenEik

How an OpenEik model records a building's electrical installation as design intent: devices, boards, circuits and what feeds what, with the wiring derived.

N1A1 EQLQ 3G1.5 N1A1 G6 home run DM box SP fromfromfromfrom
Each arc is one device's from: a link on that device's record to the device that feeds it. A box that feeds two runs is a branch. The home run, the arcs and the cable metres are derived, never stored.

What it covers

Part XIII of the OpenEik specification states a building's electrical installation as design intent, so that the model can answer from its own records: what is on circuit G6 of board N1A1, how many metres of each cable the job needs, and whether every bathroom outlet is behind a 30 mA residual-current device.

Part XIII is part of OpenEik since version 0.2, and binds every conformance class it names. In 0.1 it was a proposal, which no class of 0.1 required; a 0.1 reader keeps its records as they are.

RecordWhere
A device or a board, an element of category electricalelectrical/<level>/electrical/<id>.json
Its typetypes/electrical/electrical/<id>.json
A circuit, or the supplyproject/circuits/<id>.json
A cable carrier: conduit, tray, ladder or trunkingelectrical/<level>/cableCarrier/<id>.json
A modelled cable, where a designer routes one legelectrical/<level>/cable/<id>.json
A lighting scenea member of a 3D view

What feeds what is intent, and is stored. The wiring's geometry is derived: the arcs on a plan, the home runs, the routes and lengths of the legs, the loads and the phase balance. National rules, symbol shapes and bus addresses stay out: they belong to the country, the drawing and the application. Brands and national codes are plain values: KNX or DALI is a value of a control system, a connector such as type F a value of a connector, and purpose codes and cable names plain strings. Nothing in the standard is a national code list.

Devices and boards

Every outlet, switch, light, junction box, board and meter cabinet is an element of category electrical. It is a place in plan with a facing, a height above its level, and its type's size.

A double outlet for the dishwasher, its centre 500 mm above the floor, on circuit G6, fed from the outlet before it:

{
  "category": "electrical",
  "electrical": {
    "circuitId": "circuit-n1a1-g6",
    "from": "outlet-kitchen-1",
    "purpose": "DM"
  },
  "height": 80,
  "id": "outlet-kitchen-dm",
  "levelId": "level-0",
  "name": "Double outlet",
  "offset": 500,
  "profile": [
    [8000, 6830],
    [8000, 5830]
  ],
  "revision": 0,
  "typeId": "type-el-outlet-2",
  "width": 150
}

The type

An electrical type says what the device is (kind), what it is mounted on (wall, ceiling or floor), its depth and the default height a new device gets. Optional members describe it further: sockets, connector, protective earth, IP rating, phases, rated current, power, how a control works (wired, bus or radio, and on which system), a switch's contacts and gangs, and a luminaire's light output: luminous flux, colour temperature, beam angle and which way its light goes.

GroupKinds
Outletsoutlet, ceilingOutlet, dataOutlet, tvOutlet, evCharger
Controlsswitch, dimmer, button, sensor
Luminaireslight, spot, track, emergencyLight
DistributionjunctionBox, board, meterCabinet
Otherspeaker, accessPoint, equipment (a hard-wired load), other

A purpose code belongs to the element, not the type, because one outlet type serves a dishwasher in one place and a washing machine in another. A linear luminaire or a lighting track has a length of its own; every other device takes its type's width and height.

Circuits

A circuit is a record of its own, a file in project/circuits/: a group of devices on a board, with its protection and its cable. One record per circuit, so that changing one circuit's fuse touches one file, and two people changing two circuits do not conflict.

{
  "boardId": "board-n1a1",
  "cable": {"area": 1.5, "conductors": 3, "earth": true, "type": "EQLQ"},
  "designation": "G6",
  "id": "circuit-n1a1-g6",
  "name": "Kitchen outlets",
  "phases": ["L1"],
  "protection": {
    "characteristic": "C",
    "device": "breaker",
    "rating": 10,
    "rcd": {"designation": "Q1", "sensitivity": 30, "type": "A"}
  },
  "revision": 0,
  "voltage": 230
}

That is "EQLQ 3G1.5, N1A1 G6" on L1, behind a C10 breaker and the 30 mA type A residual-current device Q1. The record holds the parts of a cable tag, not the tag: "FXQJ 4x25/16" is four conductors of 25 mm² with a 16 mm² protective conductor beside them.

Protection

A breaker, a fuse or an RCBO, its characteristic (B, C, gG …) and rating, and the residual-current device in front of it.

A shared RCD

Circuits of one board that give the same RCD designation, Q1 say, share one residual-current device.

The supply

A circuit with no board is the supply from outside the model: its protection is the main fuse, its cable the service cable.

Boards feeding boards

A board names the circuit that feeds it. So the supply feeds the meter cabinet, a circuit of the meter cabinet feeds the main board, and the main board's circuits feed the devices.

A board schedule lists each board's circuits by designation in natural order, G2 before G10, whatever order the files are in.

Feed chains and control

What feeds what: from

Each device names the device it is fed from: the one before it on its circuit's chain. A device fed straight from its board names none. So the devices of a circuit make trees, and a junction box or an outlet that feeds two others is where the chain branches, which a plain list could not say. Adding a device at the end of a chain touches one file.

What works what: controls

A switch, a dimmer, a button or a sensor names the loads it works: lights, a switched outlet, equipment. This is apart from how the loads are fed. Two two-way switches and an intermediate switch between them each name the same light. A bus or radio control is recorded the same way; its group address stays the application's data.

Lighting scenes and aimed lights

Which luminaires are on is the state of a 3D view, not of a luminaire. A view may hold a lighting scene: the luminaires that are on, or all of them, and a dim level for any that is not at full. Switching a light changes the view and leaves the element as it was, so the building's history does not fill with switching, and several views give several scenes, such as "Evening, kitchen on" beside "Night, all off". The view's date and time say when the scene is seen.

A floodlight, a spot or an uplight can be aimed: its beam's tilt from straight down and its turn in plan, relative to the way the device faces. Its type can state how far the beam is meant to reach. No target point is stored, so the aim moves and turns with the device. Without an aim, a luminaire points as its type's light distribution says.

Cable carriers and modelled cables

A cable carrier, a conduit, tray, ladder or trunking, is a run like a pipe or a duct: points in plan, a height for each above its level, and a width or diameter from its type's catalogue of sizes.

Most cables stay derived. Where a route matters, a main cable, a feeder to a sub-board, a run through a tray, the designer can model that one leg and leave the small connecting cables alone:

What is derived

These are worked out from the records and never stored:

How a leg's route is estimated, and which hints are given, is the application's. An application that keeps derived results keeps them in its own folder, never in a record.

Checks, deletes and IFC

What a validator checks

Deletes leave nothing dangling

In IFC

Each circuit becomes an IfcDistributionCircuit named by its designation, under one electrical distribution system, with its devices as members. Each device becomes the IFC class of its kind: an outlet an IfcOutlet, a switch an IfcSwitchingDevice, a light an IfcLightFixture, a board a distribution board. Chains and sub-board feeds become port connections, and wired control becomes switch-to-light wiring. IFC has no place for a bus or radio binding, a residual-current device's type or a luminaire's light output, so those go in property sets. IFC has no class for a charging point either, so a charger is a user-defined electric appliance.

In Stomra

Stomra's electrical design writes these records, draws the electrical plans and the circuit schedule from them, and shows a 3D view's lighting scene when you walk the model. Because the records are OpenEik's own, any other tool that reads OpenEik reads the same installation.