Skip to content
Seimora Group

Status Scope of services. Nothing on this site is a record of completed work.

Integrations

What Seimora exchanges with the software you already run, what is a roadmap item rather than a built connector, and why nothing in the delivery depends on either.

What is built, and what is not

Four of the six rows below are roadmap items. They are labelled in the row rather than in a footnote, because a supplier who is vague about integration status is telling you something about everything else they say.

Continuous line: Seimora’s scope Dashed line: By others Dotted line: Roadmap, not built

Seimora Group

Output
ModelsDrawingsCalculationsThe document registerCoordination

Sent and returned as

  • Tekla Structures, SDS2, Revit

    In service

    Model exchange, both ways

    Native model files and IFC, in and out.

  • IFC, DWG, DXF, Revit, PDF

    In service

    File exchange, both ways

    The formats steel work actually moves in. Nothing about a delivery requires a portal, a login or a plugin at either end.

Your team

Files you hold.

  • Procore

    Roadmap

    Outbound — drawings, RFIs, submittals

    Not built. The intent is to publish drawings and submittals into your Procore project and answer RFIs there, rather than asking your team to work in a second system. Until it exists, the exchange is files and your own upload.

  • Autodesk Construction Cloud

    Roadmap

    Outbound — drawings, RFIs, submittals

    Not built. Same intent as Procore, for teams running ACC instead.

  • Tekla PowerFab

    Roadmap

    Inbound — production status

    Not built. PowerFab is the fabricator's system of record, one shop at a time; the intent is to read production status out of it so a client sees one timeline.

  • Fabricator ERPs

    Roadmap

    Inbound — production status

    Not built. Shops that do not run PowerFab run something else, or a spreadsheet.

Diagram of what exists today. Seimora’s box, in the heavy line, holds its outputs and no package; the exchanges in service run continuous to your team. Dashed: your team and each platform, which are other parties’. Dotted and cut: a connector on the roadmap, not built.
Sample model. Not a Seimora project. Models head the list of what leaves Seimora's box above. Drag to rotate, pinch or use the buttons to zoom. Click a member.Loading the sample model.

No integration is load-bearing

This is an architectural rule rather than a marketing line: every connector this business ever builds has to have a manual path behind it, and the delivery has to work when the connector does not. If a platform changes its API terms tomorrow — which is their right and not something any supplier controls — your drawings still arrive.

Today that rule is trivially satisfied, because there are no connectors. It is written down now so that it still holds when there are.

There is no client portal

Client portal Does not exist

A delivery portal showing piece-level status across several shops is a later phase of this business. It does not exist, you cannot log in to it, and nothing on this site should be read as saying otherwise.

What exists today is files you hold. See how we work for what that actually looks like during a job.

Tell us what you run

If your team lives in Procore or ACC, say so with the enquiry. It will not change what you get; it will change how the files reach you.

Discuss Your Project

This site may use privacy-respecting, cookie-less analytics to understand overall traffic. Nothing loads unless you accept. Cookie policy