BIM Modeling Services: Architectural, Structural and MEP BIM Explained
BIM modeling services cover architectural, structural and Mechanical, Electrical and Plumbing models that can be coordinated, quantified and issued. This guide explains discipline scopes, federation, standards and how to buy modeling work well.
BIM modeling services are the production of discipline models that other people can coordinate, draw from, quantify, and hand over. The three building-services families of models on most projects are architectural, structural, and Mechanical, Electrical and Plumbing (MEP). Each has different elements, different failure modes, and different reasons to outsource. A single label — “BIM modelling” — hides those differences and produces vague proposals.
A model is a structured representation of a built asset at a stated purpose and Level of Development. Purpose might be spatial coordination, drawing production, quantity extraction, fabrication, or facilities handover. The same building can have different models or different views of one model for those purposes. Asking for “the BIM” without a purpose is how files become museums of leftover geometry.
Authoring software is commonly Revit. Exchange is commonly IFC. Review is commonly Navisworks or an IFC checker. Modelling services include the authoring. They may include the exchange setup. They should not silently include design decisions. The modeller implements drawings, models, and written instructions; the designer of record remains the designer of record.
Architectural BIM modelling
Architectural models carry the spatial container: levels, grids (often shared), toposurface or toposolid site context as scoped, walls, curtain walls, floors, roofs, ceilings, stairs, ramps, shafts, rooms or spaces, doors, windows, and components needed for the purpose. For coordination, the envelope and the major internal walls matter more than every furniture family. For drawings, annotation and typical details matter. For quantities, types and finishes matter. State the purpose.
Rooms are the architectural model’s quiet test. If rooms leak because walls are not bounding, area schedules fail and energy or occupancy studies cannot start. If room names ignore the client’s numbering, every other consultant will invent a parallel system. Put numbering in the BIM Execution Plan.
Phasing is architectural modelling. Existing and new must be distinguishable. Demolition modelled as “hide these walls” without phasing will break drawings and quantities.
Facade modelling can dominate cost. A unitised curtain wall with real panel types is not a generic glazed wall. If the facade is a specialist package, the architectural BIM may only reserve a volume until that specialist issues a model. Write the reservation.
Structural BIM modelling
Structural models carry the load path: foundations, piles or rafts as scoped, columns, beams, braces, walls, slabs, cores, and openings that structure owns. Connection detail depends on LOD. Early models need correct locations and approximate sizes. Coordination models need sizes that an engineer has issued. Fabrication may leave Revit for a detailing tool; do not assume one model does every steel plate.
Openings and embeds are the social life of structural BIM. MEP needs holes. Architecture needs slab edges and set-downs. If the structural modeller waits for “final MEP,” coordination never starts. Reserved openings at a stated date are a modelling deliverable.
Analytical honesty: use structural categories. A transfer beam modelled as an in-place blob will not schedule and will clash as a mystery solid. Reinforcement modelling is a separate, expensive scope; do not imply it with a pretty section if it was not bought.
MEP BIM modelling
MEP models carry systems: air, hydronic, steam if any, domestic water, drainage, fire protection as scoped, electrical containment and equipment, extra-low voltage containment as scoped. The modelling unit is the system, not the colourful extrusion. Connectors on equipment, slopes on gravity pipes, and insulation policy are part of modelling quality. See the dedicated MEP BIM services article for coordination depth.
Plant rooms and risers are the highest-value modelling zones. Typical floors repeat. Unique plant does not. Buy unique zones first.
Federation: one building from several files
Discipline files should share coordinates, level names, and a publish calendar. Architecture often hosts rooms. Structure and MEP link architecture. Copy/monitor grids with an owner. A federated Navisworks file is a review container, not a substitute for native authoring files.
If three specialists model three disciplines, the buyer must buy coordination or appoint an in-house coordinator. Modelling services without federation rules produce three beautiful islands. See clash detection.
IFC federation is used when native files cannot be the common language, including some client and regulatory paths. Test exports. Singapore BIM submissions use IFC with local additions where BIM submission applies; that is not identical to a project coordination IFC. See BIM in Singapore.
Standards that actually affect modelling
A BEP names purposes, naming, coordinates, software versions, and responsibilities. ISO 19650 describes information management; projects may map it lightly or fully. Classification (Uniclass, OmniClass, or a local system) matters if quantities or asset data are in scope. LOD tables matter if reliance is in scope. Company templates matter if the file must return in-house.
What does not help: stacking five logos on a proposal (“we follow all standards”). Ask which clause of which document will be visible in the file you receive on Friday.
Deliverables of a modelling service
Native files, a link list, a type list or content library note, sample schedules, a warnings summary, an assumption/RFI log, and optional drawing sheets. For construction, shop drawing extraction is extra. For handover, parameter fills are extra. For 4D/5D, coding is extra. Name them.
File hygiene is modelling quality: worksets, purged unused where safe, no exploded CAD, pinned grids, and a size that matches the building rather than a buried import.
Buying modelling without blurring design
Write “model as per drawing set X, query conflicts, do not redesign.” If you want the specialist to propose duct routes, that is a design-assist package and needs an engineer to accept routes. Marketplaces fail when a cheap modeller is later blamed for a plant that does not fit because nobody issued a plant layout.
Use milestones: typical bay, typical floor, unique zones, remaining copy with QA. Fund on BIMProSG against those, not against “model complete.”
Quality checklist by discipline
Architecture: rooms bound, phasing correct, wall types from legend, stairs as stairs. Structure: members typed, openings reserved, no blob frames. MEP: systems assigned, gravity sloped, plant connectors, insulation policy. All: coordinates shared, version correct, RFIs listed, LOD table matched.
Site, civil and the building model’s edge
Building BIM modelling often stops at a slab edge while the project’s risk sits in a retaining wall, a road, or a drainage invert. If civil is another software (Civil 3D or equivalent), the modelling brief should still name the interface: shared coordinates, a mesh or solid of the proposed ground, and who updates the interface after a level change. A pretty architectural model that floats 400 mm above the civil surface is a coordination failure at the first site meeting.
Car parks, ramps and vehicle envelopes are modelling problems that architecture and structure share with services. A duct that “fits” in a section may kill a van’s headroom. If vehicle envelopes are in scope, model them as clashable solids. If they are not, do not claim the basement is coordinated for traffic.
Content libraries, manufacturer models and performance
Modelling speed on week two depends on content decisions on week one. Manufacturer “BIM objects” are often meshes with bad categories. A modeller who inserts them unedited will slow the file and break schedules. Either the buyer supplies a vetted library, or the modelling service includes a content-cleanup milestone, or both agree to simple placeholder families until selection. See Revit family creation.
Performance is a modelling deliverable. A 1.5 GB house model is a symptom: imported CAD, imported meshes, over-modelled furniture, nested families with too many voids, and unused design options. Ask for a file-size and warning-count note at each milestone. You are not buying a number for its own sake; you are buying a file your hardware can open in a meeting.
Design options, alternatives and the cost of indecision
Revit design options are real modelling labour. Two facade options are not “the same model with a checkbox” if both must be coordinated with structure and MEP. Price options as options. If the client is still choosing a scheme, buy schematic modelling, not coordination modelling. Level of Development should drop when indecision rises, or the specialist will be paid to coordinate fiction.
Groups and typical units help until they hide a unique shaft. Modelling services should include a rule: typical floors are grouped; unique floors are not; shafts that pass through typical floors are monitored. A freelancer who groups an entire tower including a unique plant floor will spend the revision budget fighting the group.
Handover of a modelling package to the next team
The next team may be a contractor, a coordinator, or the client’s in-house BIM person. They need: software version, template notes, workset map, link paths, password-free files, a list of third-party plugins that were not supposed to be required, and a one-page “how to continue this model.” Without that, outsourcing saves money only until the first internal edit.
If the next use is quantities, the modelling package must have included the classification and type discipline from the start. You cannot sprinkle quantity take-off onto a generic-model soup at the end. If the next use is shop drawings, views and view templates should already exist. If the next use is 4D, elements need codes that match the programme. Modelling for “everything later” is how everything later fails. Pick the primary purpose and name the secondary purposes as extras.
Worksets, phasing and the modelling rules that survive a second author
A model that only one person understands is not a modelling service; it is a hostage file. Worksets (or the project’s equivalent split) should match trades, buildings, or shared-versus-private so a second author can enter without hiding the wrong thing. Phasing should be used for renovation, not as a dumpster for “I might need this later.” Design options should be named after the decision they represent, not Option 1 through Option 9.
Pinning: grids and levels pinned, imported CAD pinned if it must remain, and coordinates not casually unpublished. A freelancer who unpublished coordinates to “fix something” mid-job has created a federation incident. The method note should forbid it unless the BIM Execution Plan owner instructs it.
Warnings: some Revit warnings are noise; some are missing rooms and overlapping walls. A modelling package should include a warning policy: which families of warnings must be zero, which may remain with a list. Buyers should open the warnings dialogue at milestone review. If the specialist is offended, they are not ready for a shared file.
Typical details, 2D and the lie of “the model contains everything”
Many construction truths still live in 2D typical details: flashings, fire-stopping, waterproofing laps. A modelling service that claims to contain everything will either over-model at huge cost or will fake 3D that cannot be built. The honest BEP lists which details remain 2D and which assemblies are 3D types. Quantity take-off and 5D must read that list or they will miss the expensive thin things.
Annotation in the model (tags, keynotes) is part of modelling if drawings are a purpose. It is not required for a clash-only model. Mixing purposes without view templates produces sheets that look coordinated and print as soup.
Multi-building sites, links and performance
A campus with many buildings should not be one Revit file. Links, a site file, and a federation in Navisworks are the usual pattern. Modelling services must state which building they author and how they consume the site. Shared coordinates are the BEP. File size and hardware are acceptance topics: a model that only opens on the specialist’s workstation is not delivered.
Linked CAD that remains for tracing should sit on a clearly named workset. Linked point clouds should be regioned. Linked consultant files should be versioned in the filename. A modelling milestone that arrives with “link not found” is incomplete.
Specification alignment without turning modellers into specifiers
Wall types should follow the specification names where the spec exists. The modeller should not invent a new thermal value. If the spec and the drawing legend disagree, that is an RFI, not a creative type. Fire ratings on doors and walls are parameters with legal consequences; they should be copied from the schedule, not guessed from a hatch.
Mechanical equipment duties should come from the engineer. A modeller who “improves” a fan size to fit a room has performed a design act. The brief should forbid it. The issue log should catch it.
Acceptance tests for a modelling milestone
Open the named version. Confirm origin against a grid intersection. Confirm levels. Produce a sample schedule (rooms, walls, ducts, or beams). Cut a section through a known congested place. List RFIs. List deviations. If drawings are in scope, print one sheet at scale. If IFC is in scope, export a sample and open it in a second tool. Fail the milestone if the first five tests fail, even if the 3D looks impressive.
These tests should be in the BIMProSG order so approval is not a taste debate. Taste is for presentation views, which should be last.
Modelling for fire, acoustics and other performance specialists
Fire engineers and acoustic consultants often need rooms, ratings, and sometimes specific constructions. They may not need hangers. A modelling service should know which parameters they will read. Fire rating on walls and doors should come from schedules. Acoustic ratings should not be invented. If a specialist model (fire or facade) will be linked, the architectural BIM should reserve volumes rather than duplicate the specialist geometry. Duplicate geometry is a clash factory.
Landscape, interiors and the edge of “building BIM”
Interiors fit-out models can be separate files with a later freeze. Landscape may be civil. If you ask a building modeller to model every planter, say so; it is extra. If you do not, exclude it. Mixed-use podiums with many tenancies need a strategy for tenant models that arrive late. The base-build model should have reserved shafts and load allowances as instructed, not guessed tenant kitchens.
Quality of rooms and circulation
Room-bounding errors are modelling defects. So are stairs that do not meet the next floor, ramps with no slope, and doors that swing through structure. A modelling QA pass should include a walk of circulation in 3D and a room schedule versus the finish plan. This is not glamorous and it catches expensive mistakes. Put it in the milestone test.
Delivering to a contractor
If the next user is a contractor, they will care about constructability and about stripping design options. Provide a clean set, a list of known residuals, and a note of placeholders. Do not deliver a design-option museum. See MEP contractors if services are the contractor’s problem.
Continuous modelling versus package modelling
Some hires sit in the file every day. Some deliver a package and leave. The BEP and the commercial model must match. A package modeller should not be expected to attend every design meeting after delivery without a retainer. A sitting modeller should not be expected to work without a central file protocol. Price follows the mode. See cost.
Name the purpose on the order: coordination, drawings, quantities, or handover. Modelling for an unnamed purpose produces a file that is slightly wrong for all of them. BIMProSG briefs should start with that noun.
One model or three? Usually one file per discipline, federated. A single file for a house can work. A single file for a hospital usually does not.
Do we model furniture? Only if the purpose needs it (coordination of labs, client walkthroughs). Otherwise it slows the file.
Who owns the template? The buyer, if the file must return. The specialist, if it is a throwaway coordination container — and then you may pay later to rebuild.
Can modelling include clash resolution? Resolution needs decisions. Modelling can implement decisions. Coordination should be a named service.
What about families? Supply them or buy family creation. Random downloaded content is a risk.
When is Scan to BIM the modelling method? When existing conditions beat drawings. See Scan to BIM.
Are 4D and 5D modelling services? They are linking services on top of a trustworthy 3D model. See 4D and 5D.
Sources and reference notes
ISO 19650, BIMForum LOD Specification, AIA LOD documents, buildingSMART IFC, and Autodesk Revit category documentation are the usual public references. They do not define a single modelling fee. National codes define design, not file structure. Singapore submission modelling must follow official CORENET X and BIM submission notes, not this marketplace explainer.
Image brief
A triptych: architectural cutaway, structural frame, MEP systems, then a federated overlay. Label Mechanical, Electrical and Plumbing. No fake completeness meters.
A buyer’s guide to Revit modeling services: architectural, structural and MEP scopes, file hygiene, family work, deliverables, pricing factors, and a hiring checklist for specialist freelancers.