GSVDESIGN

BIM method

The cloud
project platform

When the project requires it, designers, consultants and client work on a shared cloud collaboration platform. GSVDESIGN sets it up and runs it under the rules of its own BIM Standard: every piece of data has a name, a state and an owner, and every step is logged.

4 states

Work in progress, shared, published, archived

1 naming rule

Eight fields, the same for every party

Every step

Checked, approved and logged

Open formats

IFC for exchanges between disciplines

01

How data flow

Each team works in its own restricted area; only checked containers reach the shared area, and only approved ones become documents valid for use.

Data flow in the cloud project platformInformation containers move from each team's work-in-progress area to the shared state, then to published and finally to the archive, passing a check or an approval at each step; issues return to work in progress.Work in progressEach team's WIPSharedCoordinationPublishedApproved for useArchivedHistory and as-builtGSVDESIGNdesignersDisciplineconsultantsClient /contracting authorityQuality andnaming checkReview andapprovalClose-outand handoverModels and drawingsin progressrestricted areaDiscipline modelsin progressrestricted areaShared containersfederated modelsclash detectionassigned issuesversions and comparisonReview andcommentsread only, markupsApproved documentsfor tender, permitsor constructiontracked transmittalswith receiptProject archivesuperseded versionsas-built modelactivity logissues and clashesreturn to work in progress
The path of an information container: every change of state passes a check or an approval and is logged.
  1. Work in progressEach team (GSVDESIGN, discipline consultants) models and draws in its own area, visible only to its members.
  2. Quality checkBefore sharing, the model passes the BIM Standard check: naming, parameters, working views removed, georeferencing.
  3. Sharing and coordinationShared containers are federated into a single coordination model; automatic clash detection creates assigned issues with due date and status.
  4. Back to work in progressIssues and clashes return to the responsible team, which fixes them and shares the new version; versions are compared directly on the platform.
  5. Review and approvalA review workflow with designated reviewers moves documents to the published state, valid for tender, permits or construction.
  6. Transmittal and archiveDeliveries use tracked transmittals with receipt; superseded versions and the as-built model go to the project archive.

02

Areas, folders and access rights

The folder structure follows container states and disciplines. Rights are assigned by role and company, not by individual: whoever joins a team inherits the role's permissions.

Work in progress
Restricted areas per team: read and write for members only.
Shared
Read access for all project teams, upload only after checking.
Published
Read only; upload only through the approval workflow.
Archived
Read only, retained for the whole life of the asset.

03

Model coordination and issues

Architecture, structure and building services models are overlaid automatically at every new shared version. Clashes are grouped, assigned to the owner and tracked to closure, together with issues raised by reviewers on drawings and models, with markups and measurements directly in the web viewer.

  • Issues with owner, due date, status and comment history.
  • Formal requests for information between client, designers and contractor, with tracked answers.
  • Coordination meetings prepared on open issues and closed with minutes.

04

BIM Standard rules on the platform

  • Eight-field naming of information containers, based on the UNI EN ISO 19650 series, checked on upload.
  • Shared coordinates published from a single site model, in the RDN2008 / UTM reference system.
  • Model quality check before every share, with written criteria for consultants' deliveries too.
  • IFC export in open format for exchanges between disciplines and with the client.
  • On public projects, the information requirements and the approved information management plan prevail.
The GSVDESIGN BIM Standard Common data environment and CDE manager

05

What we do for the project

  • Platform set-up: structure, roles, permissions, naming templates, review workflows.
  • Onboarding and training of all parties: client, consultants, contractor.
  • Model coordination and issue management throughout design and construction.
  • Periodic reports on the status of containers, issues and approvals.
  • Project close-out: as-built model, archive, export of the data to the client in open formats.

Let us bring your project's data together

All services Request a meeting