This page collects the questions that come up most often before a project starts. For the wider category questions — what a digital twin is, how commissioning works, what drives cost — see the guides on mpandoglobal.com.
The most common questions concern what project data is needed to start, whether a BIM model is required, how the twin is delivered, whether it updates when units sell, how multilingual deployment works, and how MTWIN relates to MPANDO Sales OS. MTWIN is the digital twin; Sales OS is the sales operating system; they share inventory but can be deployed separately.
MPANDO GLOBAL Inc. is the corporate parent and MPANDO TECHNOLOGY is its technology arm. MTWIN is its digital twin brand and product; MPANDO Sales OS is a connected property-sales operating layer. They are not separate companies. The official MTWIN address is mtwin.mpandoglobal.com.
M represents MPANDO; twin means a counterpart. MTWIN creates a professional digital counterpart of a physical property project from approved design data. Visual fidelity and data connections are scoped per project; automatic sensor or BIM synchronization is not implied.
MTWIN is the visual and experience layer — the photoreal, walkable project twin. Sales OS is the operations layer — inventory, customers, offers, payment plans, reporting and commissions. They share inventory data, so a unit's state is the same in both, but either can be deployed on its own.
Architectural drawings (DWG, RVT or IFC), a site plan, the unit schedule, and material and finish decisions. Commercially: the price list, payment plan rules, and who holds pricing authority.
No. A BIM model accelerates production but is not required; a model can be built from DWG plans, elevations and the site plan, with additional modelling effort.
Yes, and that is where the commercial value is highest, because there is no physical building for a buyer to visit. Approved drawings and material decisions are sufficient.
As a desktop application, a laptop build, a browser experience through MTWIN Web, or cloud streaming. Most deployments use at least two formats — typically a sales-office installation plus browser delivery.
Yes when deployed with Sales OS, because inventory is read from a single source. Deployed standalone, inventory is supplied as a file and updated on a release cycle.
Yes. MTWIN and Sales OS interfaces are configurable for multilingual operation. MPANDO publishes in English, Turkish, German and French; additional language scope is assessed per target market.
Data ownership and usage rights are set out in the engagement contract and confirmed per project. MPANDO does not publish client project material as reference without agreement.
No. The concept films and sample Sales OS records published here are fictional, privacy-safe demonstration material produced to show the intended product experience. They are not evidence of a delivered client project.
It follows scope, but the determining factor is decision clarity rather than production speed. On a project where architectural and material decisions are frozen and the unit schedule is final, delivery proceeds predictably.
There is no list price; cost follows scope across six factors — area modelled, visual quality, interaction depth, data integration, delivery platform and update model. See the cost guide on mpandoglobal.com for how to structure a budget and compare proposals.
Send your project details — location, type, unit count, drawing format and primary purpose — to info@mpandoglobal.com. A scope conversation is arranged from there.
Last updated: · Guides on mpandoglobal.com ↗
Send us your project details and what you are trying to solve; we will answer against your actual scheme rather than in general terms.