01 / Spatial Geometry
Spaces and assets in one coordinate system
Turn drawings, floor plans, and equipment specifications into a testable 3D environment where walls, doors, lifts, hazards, and navigation maps stay aligned.
3D Environment & Digital Twin Studio
Whatever the space, we turn it into an interactive 3D world
Buildings, exhibitions, campuses, factories, or robot test environments—from spatial modeling and interactive presentation to simulation.
LIVE 3D DELIVERY SAMPLE
Asteria innovation campus digital twin
Drag to rotate · Scroll to zoom · Select an object to inspect
10
scenarios already run
Asteria Innovation Campus scene, including obstruction, spill, elevator fault and crowd scenarios
3
floors fully modeled
Asteria 1F–3F already built as a testable digital twin
4
standard scenario scripts
Obstruction, spill, elevator fault, crowd — ready to apply to your site
7
working technical modules
From the scene and elevator to hazard detection and the decision layer — not just a 3D model
One site, three layers of testable context
A 3D twin should explain every run—not just resemble the building.
TwinSite combines spaces, assets, events, and system relationships in one digital twin for presentation, planning, spatial understanding, simulation, and validation.
02 / Scenario Timeline
Every event and outcome, replayable
Model blockages, spills, lift faults, and crowds as repeatable events. Compare routes, response times, and pass results across robot versions.
03 / System Graph
Relationships across spaces and systems
Connect zones, assets, interactive elements, sensors, and records—then add robots, missions, and validation results when simulation is required.
When all you have is a plan or static model, key decisions still return to the site
2D plans leave too much open to interpretation
Plans and still renders make scale, circulation, and spatial relationships difficult to understand across teams.
Every layout change creates another version gap
When booths, equipment, partitions, or routes change, drawings, images, and decks easily fall out of sync.
A static 3D model can be viewed, not operated
A visual-only model cannot represent moving doors, lifts, equipment states, scenario events, or system tests.
How it works
From source material to an interactive 3D scene, we match the level of interaction, simulation, and validation to the job.
-
1
Scope the scene and its job
Share plans, dimensions, equipment lists, or references, then define whether the scene is for presentation, planning, training, or validation.
-
2
Build the USD scene and floor maps
We build your site into a USD scene and auto-generate floor plans and navigation maps for every level.
-
3
Add interaction and live systems
Make doors, lifts, equipment, lighting, labels, and controls interactive, with external data connections where required.
-
4
Build presentation or simulation scenarios
Create guided views, layout variants, event scripts, hazards, or crowd conditions around the project’s actual use.
-
5
Publish, review, and deliver
Deliver a browser-based experience, scene assets, and required records; robotics projects can also include validation reports.
-
6
Optional ongoing maintenance
When your site changes — a renovation, an added floor — we keep the twin in sync under a maintenance plan.
What you get
Extensible 3D scene assets
USD, glTF, or browser delivery with spatial, material, equipment, and object structure intact.
Spatial data and scene structure
Floors, zones, circulation, and equipment locations organized for presentation, planning, operations, or simulation.
Interactive elements and live states
Add doors, elevators, equipment, cameras, information layers, or live data states as needed.
Presentation or simulation scenarios
From guided tours and layout options to crowds, hazards, and robot testing—composed around the use case.
Handoff and operating documentation
Scene operation, asset structure, and scenario setup; validation projects can also include test records.
If your work needs a 3D environment, this is a place to start
Architecture, interiors, exhibitions, and spatial design
Plans and still renders cannot fully communicate scale, circulation, or layout variants.
Present, review, and switch layouts inside an interactive 3D environment.
Campuses, factories, hospitals, and facility operations
Spatial, equipment, and operational information lives across disconnected tools.
Place spaces, assets, and status in one shared digital-twin context.
Robotics, simulation, and systems integration
New sites and failure conditions often remain untestable until teams arrive on site.
Validate navigation, equipment interaction, and scenarios virtually before deployment.
Why us
More than a polished render: a reusable spatial asset designed around real work.
Built around the intended use
Presentation, design review, facility operations, and simulation each require a different level of detail and interaction.
Space, objects, and systems can interact
Scenes can include equipment state, information layers, and scenario logic instead of stopping at static geometry.
Proven on a demanding simulation case
We validated the foundation with a multi-floor elevator and robot-navigation environment; the same capability extends to other spaces and industries.
Validation progress for our robotics simulation case
Verified
- The Asteria Innovation Campus scene has run 10 scenarios
- Elevator integration works across floors in simulation
In progress
- We don't yet have real build-hour numbers for a new site
- Real-robot elevator positioning drifts inside the car — not yet validated on hardware
Next
- Find one robot vendor for a month-long pilot run on the Asteria scene
- Use that pilot's actual build hours to set our site-build pricing
FAQ
How long does it take to build a site?
We don't have a fixed turnaround yet, because we don't have real build-hour numbers of our own. We'll measure it on your first site, then use that to quote and schedule going forward.
What do I need to provide?
Right now every site is set up by hand, so we need your floor plans, elevator specs, and the scenarios you want tested first. Shortening this with on-site scanning is something we may look at later, but we don't have that pipeline yet.
What format do I get back?
A USD scene file, floor plans and navigation maps, elevator and door controller configs, standard scenario scripts, and a test report.
Can it work with our ROS 2 stack?
Our sites are built and validated against a ROS 2 / Nav2 integration — navigation goals, no-go zones, speed limits, and arrival checks all run in simulation. We've only validated this on our own wheelchair platform so far, not on other vendors' hardware, so your stack would need its own validation run.
How is this different from a generic 3D model or site scan?
A generic 3D model is static. Our scenes have a moving elevator, switchable floor hazards, and a set of ready-made scenario scripts — built to actually run navigation tests against, not just to look at.
Book a 30-min walkthrough
Tell us about the space, how it will be used, and what source material exists. We'll define the right depth of 3D scene for the project.