Documents

Overview

Everything you open, save or reuse in realvirtual WEB is a document — a GLB file that carries its geometry, hierarchy, component configuration, kinematics information and signal references together in one self-describing package. There is no separate “model” file type, and the file describes the twin without a separate schema or server-side scene configuration.

• Open it, and it becomes what the viewer is showing — the content currently loaded, representing a machine, a production area or a planning layout.
• Reference it, and it becomes an asset — a part or assembly reused inside another document, for example in the Layout Planner or the Editor.

A delivery can contain one prepared document or several examples that you choose from the document selector.

Document contents

A document can contain:

• The visible machine geometry and hierarchy
• Drives, sensors and transport behavior
• Signal names and component references
• Logic and simulation configuration
• Saved information used by HMI, Planner or DES workspaces

The exact functions available in the viewer depend on the metadata included in that document.

Classification: level and tags

Every document can carry a classification: a fixed level — Part, Assembly, Plant or Scene — plus any number of free tags. The level says how far up the structure a document sits; tags are yours to use for anything else, for example a project name or a machine family.

The classification is stored inside the file itself, so it travels automatically wherever the document goes — when you share it, export it, or copy it into another project. A document that has never been classified shows up as Unclassified; nothing about it is required.

To classify or reclassify a document, select it in the dashboard and use the level selector and tag chips in the detail pane. Tag entry suggests tags already used elsewhere in the project, so a project’s vocabulary stays consistent instead of drifting. Examples and other read-only documents show their classification for reference, without an editor.

The dashboard

What is open

A band across the top of the dashboard shows the document you currently have open — before the list of everything you do not. It stays in place when nothing is open, so you always know where the open document will appear.

The card carries two reference slots beside the document’s name:

Slot	What it binds
CONNECT configuration	The gateway configuration this document runs with — see interfaces and profiles
Knowledge file	The written knowledge that belongs to this machine

Both are filled by dragging the file from the list below onto the card; the card highlights the slot the drop will fill. A slot with nothing in it says so rather than staying blank, and it says so on a read-only document too — only the drop itself needs write access. Click a bound reference to jump to its file in the tree, or clear it with its own control. A reference whose file has since been deleted is shown as missing instead of quietly doing nothing.

Where a running gateway has something to say about a binding you just made — a profile switch that would cut live connections and is waiting for your confirmation, a gateway serving a different project, a binding that could not be saved — it says it on the same card, because the card is where you made the change.

Finding a document

Below the band, the dashboard has two views:

• Documents — your own documents together with the read-only examples that ship with a delivery. Filter chips let you narrow the list to one level, to Unclassified, or to a tag; the search box filters on top of that.
• Libraries — the sources attached to the current setup. A library is always explicitly attached: by the project’s own manifest, by a link parameter, or by you. Nothing is loaded because it happened to be in the bundle, so what you see is what someone decided you should see.

Your project appears as a tree, with folders you can create and documents you can move between them. A folder is a place, not a type: where a document sits says nothing about what it is — that is what the classification above is for.

Acting on a document

Select a document to open it, or use its context menu for further actions — duplicating, copying or moving it, or deleting it. The menu carries the actions that actually apply to that row, and nothing else: a refused action is absent rather than greyed out, so a menu never offers you something the row cannot do. On the project tree that means:

Action	What it does
New Folder	Creates a folder inside the selected folder or project
Rename…	Renames the document or folder in place, keeping its identity and every reference to it
Show in Explorer	Opens the file in the operating system’s file manager

Show in Explorer appears only when realvirtual CONNECT is running and the viewer is open on the same machine as the gateway. Opened from another computer it is absent by design — a window on a plant PC nobody is standing at is not help.

Editing a document saves it back where it already is. There is no separate publishing step and no second copy to keep in sync.

Copying and moving between projects

Use a document’s context menu to Copy to… or Move to… another project. Only projects you can write to appear as targets.

• Copy creates a new, independent document in the target project.
• Move keeps the document’s identity. Anything that already references it — a placement in a layout, for example — keeps working after the move.
• Deleting a document, or moving it away from its original project, does not erase it immediately: it goes into that project’s trash, where it can be restored.

Old scenes saved as JSON

Older projects may need a conversion step

Earlier versions of realvirtual WEB could save a scene in an older JSON-based format. As of this version, realvirtual WEB no longer reads that format — opening an affected project or scene produces a clear error message instead of a partial or silent load.

What to do: open the affected project once with realvirtual WEB 6.3.16, the last version that still converts the old format automatically, then update to the current version.

Quick Start

1. Open a delivery link, local GLB or the public demo.
2. If a document selector is available, choose the example or document you want to inspect.
3. Open the hierarchy and select a drive, sensor or transport component to confirm that component information is present.
4. Open the dashboard to see how a document is classified, or set its level and tags in the detail pane.
5. Use Copy to… or Move to… from a document’s context menu when you need it in another project.

See also

• Opening a twin
• Navigation and controls
• Signals and alarms
• Open Digital Twin Format