Users can import their own buildings or get support from ONUMA in the import process.
This is a one-time process to convert file-based BIM and CAD files into ONUMA System cloudBIM data, creating a digital twin that persists throughout operations and can be maintained and updated throughout the lifecycle.
All work is performed virtually. No site visits, field measurements, or in-person meetings are included.
All background information must be delivered as a complete, organized package.
We will provide a dedicated upload location, and the client is responsible for assembling one file per buiding.
Piecemeal delivery severely slows the process. The most time-consuming task is searching for, waiting for, or verbally walking through scattered files. A complete package avoids rework and unnecessary cost.
Once the client declares the package “complete,” we will perform a category-level evaluation. If files do not match the assumed category (e.g., provided materials place a building in Category 3 instead of Category 2), the scope and hours may need to be adjusted.
Each building can fall into a different category.
Newly completed buildings may qualify for Categories 1–2, while older facilities that only have PDFs, scans, or legacy CAD may fall into Category 3. Scope is assigned building by building.
If authoritative plans are missing, we can use secondary sources such as fire exit plans or safety diagrams, but these inputs automatically fall under Category 3 due to manual interpretation requirements.
After category evaluation, we begin the import workflow and provide the client with access to live plans in the ONUMA System for review and use.
Only the initial import cycle is included. Additional meetings, coordination, revisions, or supplemental file reviews fall under Additional Services.
This setup includes:
Building-level information
Space types and basic attributes
This setup does not include custom feature configuration, API integration, or coordination with other systems.
However, the resulting model becomes the foundation for enabling those future system connections.
Training, support, and consulting are separate services and handled on a project-by-project basis.
Architectural Model (Revit or IFC) delivered as one clean as-built model, not multiple unresolved versions.
Minimal pre-processing expected; any deviations will require additional cleanup hours.
BIM of a building with spaces ready for import to ONUMA
CAD drawings (DWG files) with organized, structured layers for walls, doors, room names and numbers
Clean, simple PDFs (plan-only) with readable room numbers (and names) - some overall dimensions or scale required.
Requires one plan per floor—no unresolved renovations or conflicting plan sets.
More than one plan per floor or inconsistent layers triggers additional review and cleanup.
Complex PDF plans or hand-drawn inputs containing extraneous graphics, notes, symbols, or clutter.
Requires manual conversion to isolate spaces and interpret architectural intent.
Often includes mixed renovations, unresolved overlays, or callouts.
Quality and quantity of background data may require a review step to confirm the cost.
Most time-consuming and least predictable. Effort will vary based on the quality of the documents.
Import driven by a structured spreadsheet containing:
Building name
Floor
Space name
Area
Key attributes
Can also connect to source data systems (e.g., Fusion).
System auto-generates space shapes with correct areas and metadata.
No floor plan resolution included—but serves as a strong baseline for later alignment.
FUSION Data is linked to ONUMA to auto-generate the right size spaces as blocks related to the building.
In the ONUMA | System FUSION GIS building shapes show up in the correct location. Buildings that do not have a FUSION GIS shape or location are located to the left of the site can can be moved to the correct location by the district.
GIS datasets containing accurate interior geometry suitable for direct import.
The level of effort depends on the type of GIS output (GeoJSON/Shape/etc.) or service (ArcGIS).
Ideal when the organization maintains GIS-based floor plans.
Can also be used to convert exterior GIS shapes.
This covers the import, organization, and validation of assets and asset data separate from the floor-plan category.
Assets must be provided in a complete, structured format (spreadsheet, COBie, BIM export, or FM system export).
Minimum required fields: Building, Floor, Space/Room, Asset Name, Asset Type, and any unique identifiers.
Assets located correctly in a BIM model (Revit) or listed with clear space associations will be imported directly.
Assets missing space associations will be placed in a temporary holding area for follow-up resolution by the client.
Manual reconciliation, deduplication, device matching, or interpretation of incomplete lists is considered Additional Services.
This category does not include asset condition assessment, lifecycle costing, CMMS integration, or API connections; however, it provides the foundation for these future integrations.