What we produce
BIM is a secondary business line at MaViAl next to software development, and it is run as a production service: you define the information requirements, we deliver models and documents that meet them. Each area has its own page with scope, deliverables and rates.
- Revit modelling — architectural, structural and MEP models from LOD 200 to LOD 400, built on your template or ours.
- Architectural BIM — design development models, plans, sections, elevations, schedules and sheet sets, including redline incorporation.
- Structural BIM — concrete and steel load-bearing structures in Revit or Tekla, coordinated with architecture and services.
- MEP BIM — HVAC, plumbing and electrical models, provisions for openings and clearance zones.
- Tekla steel detailing — fabrication models, single-part, assembly, GA and erection drawings, NC/DSTV and DXF files, bolt lists and bills of materials.
- Rebar detailing — reinforcement models, bar bending schedules and reinforcement drawings for cast-in-place and precast concrete.
- Timber and frame houses — CLT, GLT and LVL structures, timber frame and light-gauge steel frame buildings.
- Scan-to-BIM — as-built models from registered point clouds you supply (E57, RCP, RCS).
- CAD-to-BIM — conversion of DWG and PDF drawings into Revit models, plus 2D drafting support.
- Revit families — parametric families and clean-up of existing libraries.
- BIM coordination — federation, clash detection, BCF issue tracking and coordination reports.
- Quantity takeoff and estimating — model-based quantities and, for Polish projects, fixed-price cost estimate packages.
Selected automation is also available where it saves real hours: Dynamo scripts, parameter and schedule workflows, and data exports through the Revit API.
Software, file formats and deliverables
Production runs in Autodesk Revit and Tekla Structures. Coordination uses Navisworks, and we work inside the common data environment you already have — Autodesk Construction Cloud / BIM 360 or Revizto, for example. Point clouds are handled through ReCap. We do not tie a project to one vendor: if your workflow is openBIM, IFC is the exchange format and the native files stay internal.
| Purpose | Typical formats |
|---|---|
| Native models and families | RVT, RFA, Tekla model |
| Open exchange | IFC 2x3 / IFC4 (model view definition agreed per project), BCF |
| Coordination | NWC / NWD, clash reports |
| Drawings | PDF sheet sets, DWG / DXF |
| Fabrication | NC / DSTV, DXF for plates, BTL / BTLx where the timber workflow supports it |
| Data | XLSX / CSV schedules, bills of materials, bolt lists, COBie fields where required |
Tell us the exact software version at the start. A Revit model upgraded by a newer release cannot be opened in an older one, so we match your version rather than the latest.
LOD 200–400 and information requirements
Most of our models sit between LOD 200 and LOD 400, with LOD 350 for interfaces and clearances. We use LOD as a framework for the scope, not as a replacement for requirements: the written scope lists which elements reach which level and which parameters they carry.
- LOD 200 — generic geometry for massing, early coordination and design options.
- LOD 300 — accurate size and location; the model supports documentation.
- LOD 350 — interfaces, supports, connections and clearances between trades.
- LOD 400 — fabrication-oriented geometry; requires an element matrix and reliable source information.
On US projects we follow the BIMForum LOD Specification, where LOD 350 comes from. On European projects the same thinking is often expressed as level of information need (LOIN) together with AIA/EIR and a BIM execution plan; information management follows ISO 19650 principles. More detail is on the pages for German projects and US projects.
How a project runs
- Brief. You send drawings, models or point clouds, plus the BEP or information requirements, the software version and the deadline.
- File review. We check completeness and quality of the inputs and list gaps, risks and assumptions.
- Written scope and price. A fixed price, a price band or an hourly budget, with LOD per element, deliverables, milestones, revision cycles and acceptance criteria.
- Production. Modelling and drawings on the agreed template, with progress uploads to your CDE or a shared folder at the agreed rhythm.
- QA. Checks against the acceptance criteria before anything leaves the team.
- Handover. Native files, exports and a short handover note with open items and assumptions.
For a new collaboration we often start with a small pilot — one level, one steel assembly or one family set — so that both sides can test template, naming and communication before the main scope.
What helps us quote quickly
- Discipline and project stage
- BEP, AIA/EIR or other information requirements
- Software and exact version, template, naming rules
- Source drawings, models or registered point clouds
- Required LOD/LOIN, classification and parameters
- Output formats, milestones and the final deadline; for steel, the tonnage and the unit (metric tonne or short ton)
Quality control
Quality is checked against criteria written into the scope, not against a general feeling of done. Typical checks are model health (warnings, shared coordinates, naming, parameters), consistency between model, drawings and schedules, and completeness against the element matrix. For Tekla work a second person in a checker role reviews drawings before release. Scan-to-BIM models get alignment checks against the point cloud, and areas the scan does not show are marked as assumptions instead of being modelled as fact.
Where you have a model checking routine of your own — Solibri rules, a client checklist or an IFC validation step — we run our output through it before handover when the tool is available to us, or fix the findings you send back.
What stays with you
A BIM production partner is not the designer of record. To keep responsibilities clear:
- Engineering design, calculations and statutory sign-off — German Bauvorlageberechtigung, Polish building licences or a US PE stamp — remain with your licensed professionals; MaViAl does not provide them.
- Code compliance and authority approval are the responsibility of the design team; we model and draw to the standards and decisions you give us.
- The model is only as accurate as the inputs. A coordination model does not replace verification on site or site measurement.
- Laser scanning and site visits are not part of our service; software licences and cloud platforms are allocated in the written scope.
Projects in Germany, the EU and the USA
All work is delivered remotely. For German projects that usually means working with AIA and BAP, Leistungsphasen under HOAI, openBIM exchange and TGA coordination. For US projects it means imperial units, US shop-drawing conventions, USD pricing and an honest view of the time difference: Central European Time is six hours ahead of New York and nine ahead of California, so we plan short overlap windows and asynchronous BCF communication. For other EU countries we work in English to the client's national standards and templates.
Rates at a glance
| Service | EU (EUR, net) | US (USD, net) |
|---|---|---|
| Revit modelling, hourly | from €32/h | from $55/h |
| Revit model by area, one discipline, LOD 200–400 | €2.5–14/m² | $0.25–1.40/sf |
| Tekla detailing, hourly | from €38/h | from $50/h |
| BIM coordination, hourly | from €50/h | from $75/h |
| Revit family | from €60 | from $75 |
| Minimum standard BIM project | €900 | $1,200 |
Indicative figures, net of VAT or sales tax. A binding quote follows the file review. Role rates, per-tonne steel prices, drawing prices and coordination packages are on the BIM pricing page.
Frequently asked questions
Do you work in our Revit template?
Yes, that is the default. Send the template, title blocks and naming rules with the brief; if you have none, we propose a lean template and agree it before production starts.
Can you take over design responsibility or stamp drawings?
No. We produce models and drawings to your design decisions. Engineering design, calculations, code compliance and statutory sign-off stay with the licensed professionals on your team.
Do you come to site for laser scanning?
No. Scan-to-BIM starts from a registered point cloud supplied by you or your survey partner. We report gaps and occluded areas as assumptions.
Which IFC version do you deliver?
IFC 2x3 or IFC4, with the model view definition and property sets agreed per project. Before the first exchange we run a test export and check it with a report against the agreed checklist.
How fast can you start?
That depends on current workload and the size of the scope. The file review usually comes first, and the start date is written into the scope together with the milestones.
How do we communicate during production?
By email and through your CDE or issue tracker, with BCF for model-related issues. Short calls are scheduled within overlapping working hours.
Can we start with a small test job?
Yes. A pilot on one level, one assembly or a small set of families is a good way to check template, naming and quality before a larger order. It is priced like any other scope, with the minimum project value applying.
Send us your BIM scope
We review your files and confirm scope and price before production starts.
Official sources
Indicative net prices; the binding scope, deadline and price are confirmed in writing before work starts. MaViAl does not take over the responsibility or statutory sign-off of the designer of record.
