Stomra Guides

Stomra · Guide

Sharing by discipline

Share one live model with the other firms on a project: everyone reads it, and each firm changes its own discipline.

1 You change a duct, and a truss 2 Whose is each? checked record by record ALL YOURS Into the model at once every open tab sees it NOT ALL YOURS Kept as a suggestion nothing is changed yet THE OWNER Sees it, accepts it one Undo step, in their name accepted
The life of one change. The same check holds for a person and for that person's AI assistant.

The idea

On most projects several firms design one building: an architect, a structural engineer, building services engineers, an electrical designer. In Stomra they can all work in the same live model. Sharing by discipline makes that safe:

This is the way shared building models are usually protected: each team owns its information and changes someone else's only through a request that the owner accepts. In Stomra the request carries the change itself, so accepting it is one click.

Three roles

Viewer

Reads everything, writes markups and work orders. The default when you share with another organisation.

Discipline editor

Changes what the ticked disciplines own, directly. A change to anything else becomes a suggestion.

Project manager

Changes everything, the project setup included, and can accept suggestions to any part.

The owning organisation and its people have every discipline. What used to be called an editor of a project is a Project manager.

Share a project

  1. Open the project and choose Share in the top bar.
  2. Add an organisation, or a person by email.
  3. Choose a role: Viewer, Discipline editor or Project manager.
  4. For a Discipline editor, tick the disciplines they may change. At least one stays ticked.

A role given to an organisation holds for all its people, and follows its members as they join or leave. To give one of them less, choose Limit… beside the person (Limit what they may change) and tick the disciplines they may change at most. Every discipline takes the limit away. A limit only narrows: nobody is given more than their organisation has. Remove access takes a person or an organisation off the project.

ExampleRoleDisciplines
An example engineering firmDiscipline editorStructure
An example building services firmDiscipline editorVentilation, Heating and plumbing
The clientViewernone
One person at the services firm, a traineeLimit…Ventilation only

Who owns what

Nobody assigns owners element by element. Stomra works out the owner of every record from the record itself: its category, whether it is ticked as structural, and for pipes and ducts the system it belongs to.

DisciplineCodeOwns
ArchitectureAwalls, slabs and roofs that bear nothing, doors, windows, rooms, stairs, railings, furniture
StructureKbearing walls, slabs and roofs, beams, columns, foundations, framing, rebar
VentilationVducts, air terminals, air units
Heating and plumbingVSpipes, radiators, fixtures, drainage
ElectricalEdevices, boards, circuits, cables, cable trays
SprinklerSPsprinkler pipes and heads
SiteMterrain, grading, roads, parking, planting
Project setuplevels, grids, materials, the project and its information

The same owners decide where each record sits in the OpenEik model's discipline folders: see Disciplines in one model.

Working on a shared project

As a Discipline editor you have the whole model and all the tools. What changes is what happens when you touch something that is not yours.

The check runs twice: in your tab, so the answer is instant, and again by Stomra's server, so it holds whatever tool writes the change. Undo, imports and restores are checked the same way.

Suggestions

A suggestion is a change you would like made to someone else's part, with the change itself attached.

  1. Make the change as if it were yours. It is not applied. A bar over the status bar says Suggestion to Structure and how many changes it holds.
  2. Show draws the model with the suggestion made over the model as it is, the way Review compares two versions, with the changed parts lit. Discard forgets it; nothing was changed and nothing is sent.
  3. Send… asks for one sentence, such as “An opening 300 × 200 for the supply duct”, and sends it to the owners.

The people who hold that discipline, and the Project managers, hear of it under the bell. It is listed in Project ▸ Work orders, where suggestions live beside work orders. The owner can:

ChoiceWhat happens
Show over the modelThe model with the suggestion made, over the model as it is now.
Yes, do itThe change is made as one Undo step, in the owner's name, through the owner's own rights.
AskA question back to the person who suggested it.
DeclineNot made, with the reason.

Only someone whose disciplines cover every record a suggestion changes can accept it. If those records have changed since it was made, it says so and cannot be accepted until it is made again.

Opening requests

The commonest request between disciplines is a hole: a duct or pipe through a beam, a wall or a slab. It has a record of its own, the opening request, so the engineer who needs the hole can place it without touching the part it goes through.

Beam B12 · Structure's Supply duct · Ventilation's Opening request 300 × 200 · waits STRUCTURE Cut Decline…
The request is Ventilation's to place and move; the answer is Structure's. The beam is cut only on Cut.
  1. Select the duct, pipe or cable carrier and choose Systems ▸ Openings ▸ Request openings. Stomra places a request wherever the run passes through a wall, slab, roof, beam or column, sized by the run with 25 mm on each side.
  2. The request is yours: move or resize it until it is answered. It cuts nothing. It is drawn dashed, with a cross, in plans; in sections and 3D you see its outline, and in walk mode you can walk through it.
  3. The owner of the part it goes through answers it. Systems ▸ Openings ▸ Opening requests selects the first one waiting for your answer. In the Inspector, Cut makes the hole in the host (a slab's void, a wall's opening, a beam's hole) as one Undo step; Decline… answers with a sentence.

In an IFC export, a waiting request is written as a provision for a void, so coordination tools can show it too.

Suggestions in other tools: BCF

BCF is buildingSMART's open format for an issue with a viewpoint and the elements it is about. Project ▸ Exchange ▸ BCF out writes the project's suggestions and opening requests as a .bcf file (BCF 3.0), one topic each, with its viewpoint, its elements, its status and its thread. BCF in reads topics from another tool (3.0, or 2.1) as work orders on the elements they name. A topic brought in once is not brought in again.

Assistants

An AI assistant working in your tab has exactly your disciplines, no more. The check looks at the change, not at who or what made it. So a ventilation engineer's assistant can route ducts freely; when a duct needs a hole in a truss, it places an opening request or its change is kept as a suggestion, and it tells you so. Assistants on both sides can coordinate this way, with people accepting.

How assistants pick up work orders and suggestions is in Work orders.

The same rules on EikHub

The sharing rules travel inside the model. Every version Stomra saves carries an owners file, project/owners.json, written from the Share dialog: the owning organisation and each Project manager organisation own everything, and each Discipline editor organisation is a party for each discipline it writes. When the project is pushed to EikHub, EikHub reads the same file and asks each owner whose part a proposal touches to approve it. Another tool that reads OpenEik reads the same rules.

To let another organisation work on the building on EikHub too, share it from the EikHub section of the Share dialog: pick the organisation, give its address on EikHub, check the name EikHub finds, then share. How owners approve on EikHub is in EikHub basics; the owners file itself is explained in Disciplines in one model.

An example, step by step

The L-house, designed by an architecture firm that owns the project.

  1. Share. The architect shares the project with an engineering firm as Discipline editor for Structure, and with a building services firm as Discipline editor for Ventilation and Heating and plumbing. The client gets Viewer.
  2. Each works on their own. The structural engineer ticks the load-bearing walls as structural; they become Structure's. The ventilation engineer routes the supply ducts. Everyone sees everyone's work as it happens.
  3. A duct meets a beam. The ventilation engineer selects the supply duct and chooses Request openings. One request appears where the duct crosses beam B12, dashed, waiting for Structure.
  4. Structure answers. The structural engineer opens Systems ▸ Openings ▸ Opening requests, checks the beam and chooses Cut. The hole is made in their name.
  5. A suggestion. The ventilation engineer also needs a non-bearing wall moved 100 mm for a shaft. The change is held: Suggestion to Architecture · 1 change. They send it with a sentence; the architect shows it over the model, chooses Yes, do it, and the wall moves as one Undo step.
  6. The client reads the model and writes markups and work orders, and changes nothing.