Structural engineering
Self‑organizing project data
Siiv organizes a project's data as the work happens, so a project ends up with a record of how it got that way.
The problem
Where the project record actually lives
A project's real record is in emails and notes. Decisions, approvals, revised sketches, and the reason a wall moved are spread across threads, attachments, meeting notes, and folders named by whoever happened to save them.
When the question comes back a year later, someone spends hours piecing together who changed what and why, and many times the "who" has left the firm.
What Siiv does
Coordination data and design data, connected over time
week 1
The architect emails a revised sketch
2 attachments
week 2
Model v1 issued
week 3
The shear wall moves six inches west
decided against model v1
week 6
The engineer of record approves it
approval kept with the thread
week 9
Model v2 issued
41 elements changed
a year later
Why is this wall where it is?
Answered from the record
the sketch the decision the approval model v1 model v2
-
01
Coordination data
The email, the attachments, the sketches, and the decisions inside them. Captured as the work happens, with nothing to file and nothing to name.
-
02
Design data
The models, the schedules, and the elements they describe. Siiv holds which version of the design a decision was made against.
-
03
Connected, and kept over time
The two stay tied together as the project changes, so the reason behind a decision is still attached to the thing it changed.
Where do you want to start?
Thank you
Got it. Someone will be in touch shortly.