Skip to content
Planroom XRID
Project directory06 rooms

Browser-based review

Indonesia + Southeast Asia

Room 03 / System

Inspectable boundaries, roles, and history.

Planroom XR separates project sources, the review room, and outputs so each team can see what enters, who may act, and when something leaves.

Project boundary · access roles · history controls

Next: Plans
A tactile nested-room model uses timber, grey board, felt, and colored acrylic to connect eight spaces.
Room system

The nested-room model translates system boundaries into inspectable rooms, thresholds, and routes.

System boundary

Three working zones, one visible sequence.

Project sources enter the review room; decisions and exports move out only through explicit actions.

A / SourceProject tools and files
  • Discipline models
  • Drawings and documents
  • Field evidence
B / WorkspacePlanroom context
  • Federated views
  • Issues and comments
  • Decision history
C / OutputControlled handoff
  • Saved views
  • Issue register
  • Decision package

Access roles

Actions follow responsibility.

Roles do not change the project content. They determine who can set up the workspace, publish views, close decisions, or review only.

  1. 01
    Project admin

    Manage members, connectors, exports, and workspace closure.

    Manage
  2. 02
    Coordinator

    Publish views, assign issues, and route actions.

    Act
  3. 03
    Contributor

    Add comments, evidence, and responses in assigned context.

    Contribute
  4. 04
    Reviewer

    Open shared views and add scoped questions.

    Review

History and retention

Versions stay ordered; removal stays deliberate.

A new model does not overwrite its predecessor. The project admin defines the history window, export rights, and when a workspace closes.

A contemporary tropical civic building reveals connected rooms, timber screens, planting, and an accessible ramp.
Built environment

The built space provides factual context for checking changes between model, decision, and project condition.

Versions
Each publication adds one point to project history
Decisions
View, zone, reason, and responsible role stay attached
Exports
Only a project-admin action creates an output
Closure
A closed workspace becomes read-only before removal

Integrations and support

Connect project tools without obscuring data ownership.

Connectors bring models and documents into the workspace. The source stays named, sync can stop, and exports begin with an admin action.

Model authoring
IFC and project connectorsPer version
Documents
Drawings, PDF, and zone referencesOn demand
Issues
BCF and project registersTwo-way when enabled
Support
Team guides and onboarding sessionsBy plan

Apply these boundaries to a working view.

Choose the scenario, emphasis, density, and guest visibility.

Configure a view