SODIS360
EN
Talk to us
Menu

Software platform for the built environment

Manage design, construction and operations in one connected system

When plans, documents, site records and asset data live in separate places, every decision takes longer. SODIS 360 connects the work from design through construction and operations, so teams can act on the same current information.

See planned work, progress and dependencies in the same project schedule.

Connected work

Follow a decision all the way through the project

A model element, a document revision and a site task should not become three separate stories. Keep the relationships visible so each team can see what changed, who is responsible and what happens next.

  • Find the sourceOpen the object or document behind a question.
  • See the impactFollow its links to work, reviews and responsibilities.
  • Keep the historyPreserve the decision as the project moves forward.
Explore the data model →
BIM context in the SODIS 360 interface.
BIM context in the SODIS 360 interface.

Why connected data matters

A continuous record from design to operations

  1. Design package
  2. Site work
  3. Inspection record
  4. Asset history

Each team sees the records relevant to its work while the links between them remain available to the next team.

Connected work

Put the schedule and the evidence on the same page

A date in a Gantt chart is useful only when the team can see the work behind it. SODIS 360 connects planned activities with progress, quantities, site records and budget context.

  • Spot slippageCompare planned dates with the state of work today.
  • Check the causeMove to the related documents and records.
  • Act with contextAssign follow-up work to the right people.
See construction workflows →
Construction schedule with work hierarchy and time scale.
Construction schedule with work hierarchy and time scale.

Connected work

Carry useful information into operations

Handover should leave the facilities team with more than a folder of files. Spaces, equipment, manuals, service requests and maintenance history can remain connected to the asset.

  • Know the assetFind location, properties and related documents.
  • Plan the workUse service history when scheduling maintenance.
  • Keep continuityBuild on information captured during delivery.
Explore building operations →
Equipment record and maintenance context.
Equipment record and maintenance context.

Implementation

Start with one process

Choose a practical starting point, validate it with your team and extend the configuration when the process works.

Configure

Agree the objects, roles, statuses and workflow to be used.

Bring in data

Prepare the documents and reference data needed for the first process.

Next step

Show us the process you want to connect

We can walk through a relevant workflow and the information your team would need to manage it.