Models, layers, and walls, on one twin desk
MeetCarbon Cloud Digital twin keeps 3D models, energy and carbon layers, and wall layouts on one platform. Models are glTF or GLB, with one default and a map placement. A wall is created at a chosen resolution and shared as a public or password link, or an existing energy-carbon screen can be embedded. Energy accounting, thing models, and the park carbon ledger stay in their own products. This page is models and playback.
- glTF / GLB
- Upload, preview, set default
- 3 layers
- Model, flow, carbon heat
- 6 presets
- Plus a custom size
- Public or password
- A read-only link to share
- Park model · set as defaultModel
- City overview · check cardsWall
- Public link · copyPlay
From a model to a wall you can play
Four steps match menus already in the product. After the model is on a layer, the wall is composed per scene and shared with a public or password link.
Upload
Put a glTF or GLB in the model library, set the default, and write the map placement.
Layer
Energy flow and carbon heat sit on the default model. Filters and period switch on the layer page.
Compose
Create a wall at a resolution and drop in metrics, charts, and tables.
Play
A public link is read-only without login. A password link checks first. Screens from the same origin can stay in sync.
What you see in Digital twin
The menu groups models and layers, wall playback, and widgets. Open any item to see the job it actually does.
Overview
See counts for models, scenes, devices, and layers, then jump to scenarios or layers. The counts on the overview are in-page samples.
- Four counts
- Three shortcuts
- Counts are samples
Counts, flows, and emissions in the samples only show the screen layout.
Three built-in layouts, cards first, numbers later
City overview, project monitor, and AI dispatch are layout names on the wall. The lists below are the cards on each one. Business figures on those cards are samples.
Fits a hall overview. Card names come from this layout. Values follow the connected data source.
The three layouts can change cards and data sources. The saved layout stays on that scene.
Set the pixel size, then place the cards
A new scene picks one of the six presets below, or you type width and height. Select a preset to see its pixels.
Outside the presets you can type width and height. The scene list marks that size as custom.
Resolution sets the canvas in pixels. Cards are then dragged onto that canvas.
Setup owns models, composition owns the wall, playback owns the room
Energy briefings check where layer and layout figures come from. Accounting rules stay in the energy and park products.
Are the default model, placement, and semantics in place?
- Model list
- Default flag
- Coordinates and semantics
Models, semantics, and sources enter the same wall
Every card has to match a data source. Energy formulas and thing models are not rewritten here.
glTF / GLB models
The library stores files, previews them, and marks the current default.
Building semantics
JSON semantics and a WGS84 or GCJ-02 placement live on the model.
Layer filters
Flow switches among power, heat, and gas. Heat switches among region, site, fuel, and time.
Widget data sources
API, sample data, or database. New widgets start on samples and can be tested first.
Public or password links
The playback address follows the scene access mode. Embed screens use a login link.
What this page does not rebuild
- Sub-metering and hosted energy live in integrated energy management.
- Device onboarding and thing models live in IoT device management.
- The park carbon ledger and neutralization path live in zero-carbon parks.
- Mapping each device onto a 3D model is still in development.
Business figures on scenarios, flow, heat, and the three layouts are in-page samples. After a data source is connected, its response applies.
Load one model, then open one wall
Use this order for the first screen. Sample numbers on the layers can be replaced later. The model and the link can be ready first.
- 1One glTF or GLB
- 2Placement datum: WGS84 or GCJ-02
- 3Layers to show: flow, heat, or both
- 4Wall resolution and access mode
- 5Whether cards start on samples or an API
The device-twin entry is already in the menu. Mapping is still in development. The first wall does not depend on that page.
- 01
Upload the model
Store it, preview it, and set it as the default.
You get · Default model - 02
Write the placement
Add coordinates, and building semantics when you have them.
You get · Located - 03
Check a layer
Open flow or heat and confirm the filter and the default model.
You get · Layer visible - 04
Create a scene
Pick a resolution and choose public or password.
You get · One canvas - 05
Place cards
Drag metrics and charts from the library. Start on samples, then switch to an API.
You get · Ready to play - 06
Send the link
Copy the read-only or password link. Embed screens get a login address.
You get · Room can open it
Models, layers, and playback stay on one platform
Digital twin is the screen you can see. Accounting, device onboarding, and the park carbon ledger have their own products.
A default model first
glTF or GLB enters the library, and one file is marked current.
Layers sit on the model
Flow and heat use that default model.
Resolution before cards
Canvas pixels are set, then cards are dragged.
New widgets start on samples
An API or database can be attached later, and tested first.
Public and password stay apart
A read-only link needs no login. A password link checks first.
Sync stays on one origin
Name a master among screens from the same site.
How it meets nearby products
Models and playback stay on this page. Energy, devices, and the park carbon ledger are read in their own products, then written into a widget data source.
Park walls, city overview, project monitor, and halls on one playback desk
These four already point at a playback mode you can open. Per-device mapping onto a model is not delivered yet.
Keep playback apart from accounting and device onboarding
Can a device be mapped onto the 3D model?
The device-twin menu is already there. Opening it shows a note that the work is still in development. What you can use today is model upload, layers, and walls. Per-device mapping is not delivered yet.
Can the scenario and layer figures be quoted directly?
Quote them only as samples. Reduction, investment, and payback on the scenario page, and the statistics on flow and heat, are in-page samples. After a data source is connected, its response applies.
Does AI dispatch send commands from this page?
AI dispatch is the name of a wall layout, with cards for status, effect, benefit, a control panel, and a log. Dispatch math and commands are completed in energy and microgrid products.
How do several screens stay in sync?
Sync is limited to the same browser origin, and one screen can be the master. A different site, or a browser without this capability, plays each screen on its own.
Is there a map card in the widget library?
The widget library does not enable a map card today. The wall basemap defaults to a 3D globe and can switch to a 2D Tianditu map.
Can the energy-carbon wall link open without login?
The copied address for the preset embed, Energy-carbon wall, requires login. Anonymous read-only is for native walls whose access mode is public.
Start with one screen’s resolution and model
Tell us whether it is a park energy wall, a city overview, a project monitor, or a public hall link. We will walk through the model, layers, layout, and playback address for that scope.