Virtual Sites
How Virtual Sites models a site as a navigable Digital Twin: the four tabs, the Studio's five stages, scenes, plans, camera placement, versions and publishing, and what is not available.
- Versione
- 0.2
- Ultimo aggiornamento
- Disponibilità
- Parzialmente disponibile
Sfoglia la documentazione
In questa pagina
Questo documento è attualmente pubblicato solo in inglese. Leggi la versione inglese di riferimento
Virtual Sites is where a site becomes a model. An organisation builds a navigable Digital Twin of a site from 360° scenes and floor plans, places its cameras in the model, and publishes a version that the rest of Virtik then uses as the site's spatial reference. It is the module the other modules are designed to read from: when a camera has been placed in a twin, Detection's Live wall and Response's Incident Scene can show the zone, level and building it covers. Command Center offers only an Open Virtual Site link.
The four tabs
| Tab | What it holds |
|---|---|
| Overview | A portfolio of the organisation's sites on a map, with a rail of Sites, Groups and Activity, and the commands New Twin, Import Source, Share and Export. Import Source only opens the Studio, and Export produces a CSV. |
| Studio | Where a Digital Twin is created, built, reviewed and published. |
| Library | A table of sites with New Site, Import and Refresh, filters (All, Operational, Attention, No model, Draft, Published, Archived) and per-row actions: Open in Command Center, Open in Analytics, Copy site ID, Open in Studio, View tour, Copy public link (only if the tour is already public and published), Export / publish…, Duplicate model, Archive model or Restore to draft, and Delete model… |
| Analytics | Reporting on the portfolio. |
Only the Studio is tied to the organisation's plan: if the plan does not include it, the Studio says so and the other tabs remain. In the Overview, Groups are arrangements you make while viewing; they are not saved.
One twin per site
A Digital Twin always belongs to a site, and a site has one active twin. If a site already has one, New Twin says so and offers to open it. If the organisation has no sites yet, it tells you to create one first; see Your first site.
The Studio's five stages
The Studio starts at "What do you want to create?", with cards for the ways to begin: capture with Virtik Mobile, import 360° images, upload photos or video, import LiDAR, import drone capture, import a floor plan, import BIM or CAD, or build from existing Virtik site data. A twin then moves through five stages.
- Capture
- Bring in source material. The Studio creates a single-use pairing code, valid for 15 minutes, which is entered on the phone under "Join a Studio capture"; the phone can also start a capture directly. The Studio's capture panel also shows a notice that the phone cannot join in the current build, although the mobile application contains a join screen; treat phone pairing as unverified. Sources can also be imported.
- Build
- Assemble the twin. Automatic reconstruction is not available in this release (see below), so a twin is assembled by hand in the Advanced editor.
- Review
- Check quality findings and changes, and resolve anything that blocks approval.
- Publish
- Submit for review, approve, then publish a version. An administrator is required to approve and to publish, and Publish stays disabled until the twin has a ready representation (a 360° tour built or linked).
- Operate
- The published twin is the site's operational model. This stage shows how fresh it is: when it was last captured and when it was approved, which the screen labels "Last verified".
What a twin contains
The Advanced editor has sections for scenes, floors, the viewer menu, security objects, patrol routes, hotspots, documents, annotations, plans, zones and routes, representations, layers and AI proposals.
- Scenes are 360° panoramas. A scene has a name, an initial view, optional latitude, longitude and altitude, and can be placed on a plan.
- Plans are floor-plan images. You set the scale from one known distance, then align the plan by rotation (degrees clockwise from the plan's top to true north) and an anchor point. A plan shows whether it is aligned.
- Security objects are things placed on a plan. A camera object links to a camera the site already has; the Studio never creates a camera.
- Hotspots can be of eight kinds: Navigation, Info, Camera, External link, Document, Media, Security object and Asset or equipment.
- Notes can be added to a twin as internal annotations.
Writes to a twin carry the revision they were based on, so two people editing at once cannot silently overwrite each other.
Versions and publishing
A twin version moves through draft, processing, needs review, approved, published and superseded. Approval is blocked while AI proposals, proposed spatial changes or open critical findings are pending. Publishing makes a version the operational twin and freezes it: a published version can no longer be edited, and a later change is a new version. Publishing records who published it and when; a reason belongs to the version, and is entered when an update version is opened.
Who can do what
Everyone in the organisation can read the twins of the sites they have access to. Creating and editing needs an administrator or editor role. Approving and publishing needs an administrator.