How it Works
The Import workflow is a critical part of the system architecture to enable open, trusted discussion between Proponents and Regulators.
The workflow has been proven to be robust and scalable thousands of times over across highly complex scenarios, engineering and architectural proposals and massive complex urban environments of thousands of square kilometres.
Now, we have more improvements to make it easier and better for all. It is an Upflow.
Offline Workflow: Regulator Imports and Manages 3D Proposals.
Currently, reviewing a proposal is done by the Regulator receiving a Proposal as an FBX or some other format (eg SKP, RVT, MAX, DWG etc). The Proponent shares a 3D Proposal and the Regulator 3D staff do the “import” workflow in preparation for evaluation.
The Import Workflow is a multi-step process.
- The User imports one or more 3D models (say, of a building) into the Context Model. While import is ‘drop and drag’ easy, there are many steps. For example 3D Model files provided can be in strange formats, huge in file-size and un-optimised with every bathroom tap. The Importer thus has to optimise, fix and clean these models taking them through multiple packages (and thus getting licenses to them) and sometimes inventing workflows on the fly (we have seen some real corkers). Materials and textures can be a real challenge.
- The files provided may not be geo-referenced (architectural models usually aren’t), so the Importer will have to manually locate the Proposal – which in itself may require rotation, movement, orient and sometimes even scale. XY- precision is difficult, and Z or RL (height) precision is just as hard. The Importer will need to clear the site of existing content, create cutting splines and setup and manage the layers.
- The Importer-User may then want the Proposal to look nice so may add associated objects, which all takes time, such as trees, and cars and other assets.
- After all this, when a meeting with the Proponent and Regulator occurs, there may be disappointment with how it sits together. This will be the first time the architects and others will see their vision in the model, and they may be surprised, and even frustration and potentially embarrassment – never a good mix.
Our workflow remains industry leading, but we have improved it more to save this hard work on behalf on the Regulator, and to give more control to the Proponent, we have alternate workflows.
Online Workflow: Proponent Imports 3D Proposals – and Submits.
Where the Proponent team can access the Model via the Platform they can be the “Importer” themselves. When they have sorted out and are happy with all the details, the Proponent can export their Layer as a complete .UCE file and email/fileshare. The Regulator simply does one-click Import UCE and the Proposal snaps exactly into place, cutting splines stay true, layers and naming remain.
I spell out the steps to make this happen below. This of course can only occur once a Base Model is available in our Platform.
- Base Model Access is provided via Access Groups. An Access Group is granted access to Models (eg Bob is part of Dev1 Access Group and can see all the group’s Models). Monthly Model Access fees can be charged on a per Access Group or per User basis. The access fees for Models are set by the IP owner.
- New Approvals / Permits etc can be added to the Context Model to inform Proponents of adjacencies to consider. The Regulator provides a UCE with models (and preferably the originals) as UCE files to us. We quote to clean, otpimise and publish them for all Model Users to see as an un-editable Option to show/hide.
- Urban Engine (UE) Desktop is licensed per Seat / Workstation. UE Desktop licenses can be shared among Access Group members by Group Admins via our Portal. Any Registered UC User can login to a Licensed UE to get to their Models.
- All Users can of course email files to each other to import for private discussions. This information remains stored on local computers, not streamed from online.
- Proponents have an incentive to update the Model around their site and contribute to the greater whole – they can use our resources for Certified Base Model updates to assure trust and quality.
How to make this happen?
Regulators just need to talk with us to be sure your Model is hosted online and set a price for Model Access for third parties. Then we simply grant Model Access to Proponents. The Model Access fees get recycled back into Model updates to ever improve the model. A virtuous cycle.