Making good data quality requests for your models
What it is for
The digital models of your portfolio underpin many uses in Stonal: viewing plans by building group, themes, field surveys with EDIT, analysis reports, synchronisation with your ERP. A modelling or model update request that is complete from the start is processed faster, without back-and-forth, and gives a result you can use straight away.
This page helps you prepare your request: which type of request to choose and which documents to attach.
Which type of request?
| Your situation | Type of request | Steps (carried out by Stonal or by you, in full or in part) |
|---|---|---|
| A new development, an acquisition, a portfolio not yet in Stonal | New modelling | 1. Building the portfolio sheet · 2. Revit modelling compliant with Stonal prerequisites (charter, metalibrary) · 3. Quality check and integration into Stonal |
| A model already in Stonal, but with a building, a floor or partitions that are wrong or missing | Modelling supplement | Same process, limited to the elements concerned |
| A major refurbishment or works that change the structure (partitions, redistribution of units, extension…) | Model update | 1. Updating the portfolio sheet · 2. Updating the original Revit file · 3. Quality check and integration |
| Data attached to the model to correct: naming, codes, addresses, dates, conditions | Data correction | Correction in the database and display check |
Replacing, adding or removing equipment without changing the structure (replacing bathtubs with showers, for example) does not, in most cases, need to go through Stonal. These updates are made with EDIT or, for organisations equipped with GraphlakeThe Stonal interface for viewing and managing plans: it is what the Plans tab displays., with the Query tool, which allows bulk updates. A request is only needed when the model requires a graphical rework.
The 3 golden rules
1. Name the request precisely
One building group per request. Give the code and name of the building group, the number of units and the nature of the request.
Example: "Group 1405 – Les Fougères – 24 units – Update following refurbishment"
2. Detail the request
For an update: the nature of the works, the dwellings concerned, the changes to make.
Example: "Bathtubs replaced with showers in the 24 units of building A; attributes to update: equipment type, installation date"
3. Attach the necessary documents
| Document | New modelling / supplement | Model update | Data correction |
|---|---|---|---|
| Plans: floors, elevations, sections, site plan, in RVT format if possible, otherwise DWG or PDF | Essential | Essential (post-works plans) | — |
| As-built file (DOE) | Recommended | Essential | — |
| Portfolio sheet, if you produce it, otherwise an export of your portfolio codes (from your ERP, or from the Query tool for Graphlake organisations) | Essential | Essential | If codes need completing |
| ERP extract (codes, addresses, stairwells) | Recommended | If units change | Essential if codes need completing or updating |
| Photos or any other useful item | If available | If available | — |
| Approved quote or schedule of rates, or at least the purchase order or service order reference | Essential if the service is priced | Essential if priced | Depending on your contract |
The attached documents (as-built file, plans) are also filed in the building group's document management: they remain available after integration.
Do you model yourself or through a contractor?
Read the Stonal modelling prerequisites (Revit files, BIM charter, metalibrary) in the FAQ From Abyla to Graphlake, and require them in your design or survey contracts. A compliant Revit file reduces the cost and lead time of integration.
The full process can be tested on a first model, with Stonal support to plan: contact your Stonal representative.
What Stonal checks before delivery
So that your model can be used everywhere (themes, EDIT, reports, ERP synchronisation), Stonal checks at each integration:
- the naming of sites, buildings, floors and dwellings, in line with your naming charter;
- a valid portfolio code at each level (site, building, dwelling), essential for synchronisation with your ERP;
- for each dwelling and usable zone: the stairwell and the address;
- the life-cycle information of components: construction date, condition, date of last renewal;
- the filing of the documents (plans, as-built file) in document management.
If information is missing from the documents provided, Stonal comes back to you before integration.
Where to send your request?
On the Stonal customer portal: serviceclients.stonal.com