{"slug":"/3d-scanning/scan-to-cad-modelling-levels-lod","title":"Scan-to-CAD Modelling Levels: What Each LOD Step Costs in Hours","description":"Scan-to-CAD levels compared: LOD 200 to intelligent piping, the relative modelling hours behind each, and how to tell when a drawing set was the real need.","h1":"How much of the point cloud actually needs to become a model?","answer":"Modelling level drives as-built cost more than scanning does. Two scales apply: BIMForum LOD describes how much detail is modelled, USIBD LOA describes how accurately it matches reality. Effort roughly triples from generic solids to spec-driven intelligent piping. Buy intelligent objects only where something downstream reads the attributes; otherwise a dimensioned drawing set delivers the same answer.","expansion":"Two published scales govern the answer and they are not interchangeable. The BIMForum Level of Development Specification — current edition 2025, which added an optional LOD 250 between approximate and accurate geometry — describes how much of an element is modelled and how far it can be relied on. The USIBD Level of Accuracy Specification, document C120 version 3.0, describes how close the result sits to the real steel, in five bands running from coarser than 5 cm at LOA10 to finer than 1 mm at LOA50, stated at 95% confidence. LOD without LOA buys detail without tolerance. Effort scales with element and connection count, so a congested process area costs multiples of an open one at the same level, and small-bore pipe dominates the hours. The decision that saves the most money is the earliest one: identify who opens the file and in what software, then buy only the level that consumer can read. [Deliverable formats](/3d-scanning/point-cloud-to-cad-deliverables) follow from that.","source":"BIMForum Level of Development (LOD) Specification, 2025 edition (LOD 100-500, LOD 350 for trade coordination, optional LOD 250 introduced 2025, organised by CSI UniFormat). AIA E201-2022, which succeeded AIA G202-2013 as the contractual LOD reference. USIBD Level of Accuracy (LOA) Specification, document C120, version 3.0 (2019), five bands at 95% confidence, tolerance ranges derived from DIN 18710, distinguishing measured from represented accuracy. Effort ratios are planning figures for congested process areas, expressed relative to an LOD 200 baseline and intended to be calibrated on a pilot bay. Verified August 2026.","table":{"caption":"As-built deliverable levels, relative modelling effort and what each cannot do","columns":["Deliverable","What it contains","Effort vs LOD 200","Right when","Cannot do"],"rows":[["Registered point cloud","Measured reality, nothing interpreted","0x (scanning only)","Dimension checks, visual verification, permanent archive","Clash detection, quantities, isometric extraction"],["Mesh or dumb surface","Continuous surface with no object identity","0.3x","Virtual walkdowns, access and egress, scaffold and rigging studies","Attribute queries, material take-off, iso extraction"],["Dimensioned 2D drawing set","Plans, sections and dimensions extracted from the cloud","0.4x","Tie-in packs, foundation and clearance checks, nozzle orientation records","Anything a person cannot read off a page"],["LOD 200 generic solids","Approximate size, shape and location; pipe as centreline at nominal diameter","1.0x (baseline)","Layout studies, rough clash, early planning, equipment envelopes","Fabrication-grade dimensions"],["LOD 300 accurate geometry","Real dimensions, locations and orientations fitted to the cloud","1.8x","Revamp design, detailed clash, as-built record of record","Support and connection coordination"],["LOD 350 with interfaces","Adds supports, connections, penetrations and interfaces between systems","2.6x","Trade coordination, buildable tie-ins, congested brownfield work","Fabrication detailing, which is LOD 400"],["Spec-driven intelligent piping","Catalogue-bound components carrying line, service, spec, material and insulation attributes","3.5x","Isometric extraction, MTO, twin attribute anchoring, reuse across studies","Stay correct without a named update owner"]],"note":"Effort figures are planning ratios against an LOD 200 baseline for congested process areas, dominated by element and connection count rather than by area or point count. Calibrate against one 15-20 m pilot bay before pricing a unit. Open areas, tank farms and racks fall well below these ratios."},"facets":[{"q":"What is the difference between LOD and LOA?","a":"LOD is how much of the element is modelled and how far you may rely on it — BIMForum's 100 to 500 scale. LOA is how close the modelled surface sits to the real steel — USIBD's five bands at 95% confidence. A model can be highly developed and dimensionally wrong, or crude and exact. Specify both, per discipline, or you have bought detail without tolerance."},{"q":"Which LOD should I ask for in an as-built plant model?","a":"LOD 300 covers most operational needs: accurate geometry with real dimensions, locations and orientations fitted to the cloud. Step to LOD 350 only where tie-ins must be buildable, because that level adds supports, connections and penetrations and carries the largest hour increase on the ladder. Set the level per discipline — pipe, steel, equipment, electrical — rather than applying one level across a whole unit."},{"q":"Do I need intelligent piping objects or will a mesh do?","a":"A mesh wins whenever the consumer is a person looking: walkdowns, access reviews, scaffold planning, rigging studies, contractor familiarisation. Intelligent objects earn their cost only where software reads the attributes — isometric extraction, material take-off, spec-driven clash, or anchoring inspection records to components. Count the downstream consumers first, because the modelling cost is fixed and the return is entirely in reuse."},{"q":"What does LOD 500 mean for an operating plant?","a":"LOD 500 means field-verified as-built, which is a statement about verification rather than about geometric detail. A scope asking for \"LOD 500 as-built\" without naming what was verified, by whom and against what tolerance has bought a phrase. Write the requirement properly instead: LOD 300 geometry, verified against the registered point cloud, delivered with a deviation map and a stated tolerance band."},{"q":"How do I price a scan-to-CAD modelling job?","a":"Model one pilot cell — a single congested bay of 15 to 20 metres — at the level you think you want, and count the hours. Multiply by element density across the unit. That number prices the job more reliably than any per-square-metre rate, and it surfaces the occlusion and small-bore problems while they are still cheap to solve. Area rates hide the two things that actually drive cost."},{"q":"How accurate is a model built from a laser scan?","a":"Two numbers govern it, and they fail independently. Measured accuracy is how close the registered cloud sits to the real object, evidenced by the registration report's residuals. Represented accuracy is how close the model sits to that cloud, evidenced by a deviation analysis. A 4 mm registration feeding a model fitted by eye produces errors nobody can trace. Ask for both numbers in writing."}],"sections":[{"heading":"Two scales, one decision","paragraphs":["Two published scales govern an as-built model and they answer different questions. The BIMForum Level of Development Specification says how much of the element is modelled and how far you may rely on it — LOD 100 through 500, with LOD 350 added for trade coordination and an optional LOD 250 introduced in the 2025 edition to close the gap between approximate and accurate geometry. The USIBD Level of Accuracy Specification says how close the modelled surface sits to the real steel. A model can be highly developed and inaccurate, or crude and dimensionally exact.","Buyers ask for LOD 300 and assume they have specified accuracy. They have not. LOD 300 means accurate geometry with size, shape, location and orientation modelled, and it says nothing about the tolerance those dimensions were held to. That is a separate clause, and USIBD C120 exists to write it. Two contractors can both deliver a defensible LOD 300 model of the same pipe rack with a centimetre of difference between them, and both are right against the scope you wrote.","The contractual reference for LOD moved from AIA G202-2013 to AIA E201-2022, and legacy documents still cite the older form. For an operating plant neither AIA form is the point — the BIMForum specification's organisation by CSI UniFormat is what makes it usable, because it lets you set a different level for pipe, for structural steel, for equipment and for electrical inside one scope. Set them separately. Nothing forces one level across a whole unit, and applying one everywhere is the fastest route to overpaying."]},{"heading":"The LOD ladder read for an operating plant","paragraphs":["LOD 100 is a placeholder, a symbol standing in for something whose real size is unknown. It has almost no place in an as-built scope, because the survey already knows the size. LOD 200 is generic geometry at approximate quantity, size, shape and location: pipe as centrelines at nominal diameter, equipment as blocks with correct envelopes, steel as generic members. For a rig study, an access review or a rough clash check, LOD 200 answers the question completely and costs less modelling time than anything above a mesh.","LOD 300 is where most useful as-built work sits: accurate geometry, real dimensions, real locations, fitted against the cloud rather than transcribed from the P&ID. LOD 350 adds the interfaces — supports, connections, penetrations, the things that make a tie-in buildable and that the fabricator has to hit. The step from 300 to 350 is where a modelling team stops drawing pipe and starts drawing everything the pipe touches, which is why the hour count moves more between those two levels than anywhere else on the ladder.","LOD 400 is fabrication-level and belongs to the fabricator, not to the as-built survey. LOD 500 is the level that gets misused: it means field-verified as-built, a statement about verification rather than about detail. A scope asking for \"LOD 500 as-built\" without saying what was verified, by whom, against what tolerance, has bought a phrase. Write it properly instead — LOD 300 geometry, verified against the registered cloud, reported with a deviation map and a stated tolerance."]},{"heading":"Accuracy is a separate purchase","paragraphs":["The USIBD Level of Accuracy Specification, document C120, defines five bands at 95% confidence. LOA10 is coarser than 5 cm. LOA20 spans 5 cm to 15 mm. LOA30 spans 15 mm to 5 mm. LOA40 spans 5 mm to 1 mm. LOA50 is finer than 1 mm. The bands were drawn from the tolerance ranges in DIN 18710, and the version to cite is 3.0, published in 2019. Each band is an achievable procurement target rather than a marketing claim, which is exactly why it belongs in the scope.","The specification separates measured accuracy — how close the survey sits to the real object — from represented accuracy, how close the model sits to the survey. Those are two different failures. A registration with 4 mm residuals feeding a model built by eye against a coarse cloud produces a 30 mm error nobody can trace to either cause. Ask for both numbers. The registration report gives you the first, a deviation analysis of the finished model against the cloud gives you the second, and that analysis is a short automated output almost nobody requests.","Set the band by consequence rather than by ambition. A tie-in flange face that a prefabricated spool must land on needs LOA30 or better plus a field-verified check before fabrication release. A rack elevation used for access planning is satisfied at LOA20. Equipment envelopes for a layout study are satisfied at LOA10. Applying LOA30 across an entire unit because one flange needed it is the accuracy version of the same overspend that a proper [deliverables specification](/3d-scanning/point-cloud-to-cad-deliverables) exists to prevent."]},{"heading":"Where the modelling hours actually go","paragraphs":["Modelling effort tracks element count and connection count, not floor area and not point count. Ten thousand square metres of open tank farm models in a fraction of the time of one congested compressor house, because the hours are spent identifying, fitting and connecting discrete objects. Small-bore pipe is the dominant cost in every process unit: it is numerous, it is poorly captured because it hides behind larger pipe and structure, and it demands the same object-by-object attention as a 24-inch header while carrying a fraction of the value.","The second driver is occlusion. A point cloud holds only what the scanner saw, and a modeller working a shadowed region either interpolates, flags it, or asks for a return visit. Interpolation is fast and silently wrong. Flagging is honest and generates a punch list. The return visit is the only complete answer and it costs a mobilisation. Deciding that policy up front — flag and schedule, never interpolate — changes the quoted hours and changes what the finished model can be relied on for.","The third driver is attribute population. Geometry is a one-time fit; attributes are data entry against a source of truth. Line numbers, service, specification, insulation, material and inspection references have to come from a register that is itself correct, and reconciling a piping line list against what the scan actually shows is often the largest single line in a model quote. Where that register already lives in an [asset system](/erp), the reconciliation is worth doing once and keeping."]},{"heading":"When intelligent piping objects pay for themselves","paragraphs":["An intelligent piping object knows it is a 6-inch, 150-pound, carbon steel elbow in a named line, and it inherits from a specification. That knowledge earns money in four places: automatic isometric extraction, material take-off, spec-driven clash and interference checking, and attribute anchoring for anything downstream that reads the model. If the project pulls isometrics or an MTO from the model, intelligent objects pay for themselves on the first package, because the alternative is a draughtsman producing the same isometrics by hand.","The fourth use is the one that compounds. When corrosion and inspection records hang off the geometry, they hang off objects with identity — this spool, this line, this component — and that identity is what makes [inspection data on a twin](/digital-twins/inspection-data-on-a-twin-what-it-changes) navigable rather than decorative. A dumb surface can display a heat map. It cannot answer \"show me every 6-inch line in this service with less than five years of remaining life\", because it does not know what any of its triangles are.","Reuse across studies is the multiplier. A spec-driven model that feeds a stress package, a fitness-for-service assessment and an RBI programme is paid for three times against one modelling cost. A model built for one revamp and archived is paid for once. Count the downstream consumers before you buy intelligence, because the cost is fixed at the front and the return is entirely a function of how many times the model gets opened again."]},{"heading":"When a dumb surface or a drawing set is the right answer","paragraphs":["A mesh or dumb surface wins whenever the requirement is visual and spatial: virtual walkdowns, access and egress reviews, scaffold planning, crane and rigging studies, laydown and route checks, contractor familiarisation before a shutdown. It builds fast, opens on modest hardware, and it carries no attributes that can become wrong. A large share of the value operators attribute to 3D models is delivered entirely at this level, and buying intelligence for it converts a two-week deliverable into a three-month one.","A dimensioned 2D drawing set wins whenever the answer is a set of numbers on a page: a tie-in dimension pack, a platform or foundation check, a nozzle orientation record, an equipment replacement clearance study. The consumer is a person reading a drawing, and no intelligent model improves that experience. Extracting the sections and dimensions from a cloud costs a fraction of modelling the same region, and the deliverable opens in any PDF viewer on any device for the next twenty years.","Both of these are legitimate final deliverables rather than steps towards a real model. The industry habit of describing them as low levels pushes buyers upward for reasons of vocabulary rather than requirement. What decides it is the consumer: a person looking, a person dimensioning, or a piece of software reading attributes. Only the third case requires an intelligent model, and only the third case justifies its maintenance."]},{"heading":"The expensive mistake, and the four questions that catch it","paragraphs":["The recurring overspend is a full intelligent piping model bought for a project whose actual requirement was a dimensioned drawing set and a walkable cloud. It happens because the scope is written from the deliverable menu rather than from the consumer, and because \"as-built model\" sounds like one thing. The result is a three-month modelling programme producing an asset that gets opened twice, drifts out of date at the first shutdown, and is never trusted again by the people it was bought for.","Four questions prevent it. Who opens this file, by name and role? What software do they open it in, and do they hold a licence? What decision does it inform that a dimensioned drawing cannot? And who updates it after the next management-of-change? If the fourth question has no owner, the intelligent model is a wasting asset and the money belongs in a better cloud with better registration instead — a cloud does not go stale, it only gets old.","The reverse mistake is rarer and cheaper to fix: buying a mesh when isometrics were needed, discovering it in month two, and modelling the affected region properly. Under-buying is recoverable because the cloud is still there. Over-buying is not, because the hours are spent. That asymmetry is the whole argument for staging the purchase — cloud first, model the region that earns it, and keep the [master data formats](/3d-scanning/point-cloud-file-formats-e57-las-rcp) open so the second stage stays competitively priced."]},{"heading":"Writing a modelling scope that can be priced and accepted","paragraphs":["Start with a pilot cell. Pick one congested bay of 15 to 20 metres, model it at the level you think you want, and count the hours. That number, multiplied out by element density across the unit, prices the job more reliably than any per-square-metre rate, and it exposes the occlusion and small-bore problems while they are still cheap. Every as-built programme that lands on budget started with a pilot; the ones that overrun started with an area rate and a hopeful assumption about congestion.","Then write the four clauses that make acceptance objective: the modelling level per discipline, the accuracy band per discipline with the USIBD citation, the occlusion policy — flag and schedule, never interpolate — and the verification deliverable, which is a deviation analysis of the model against the registered cloud with a stated tolerance and a colour map. Add the attribute schedule as a named list of fields and the register each field is sourced from, and the argument about what \"complete\" means disappears before it starts.","Close with ownership. Name who holds the model, in what format, and what event triggers an update. A model attached to a live [digital twin](/digital-twins) with a management-of-change gate stays true; a model in a project folder decays from the first bolt turned. If nobody will own it, buy the drawing set and keep the cloud. To scope a specific unit, [request a quote](/contact) with the pilot cell defined and the consumer named."]}],"faq":[{"q":"Is LOD 350 worth the extra cost over LOD 300?","a":"It is worth it in congested brownfield areas where a prefabricated tie-in has to land first time, because LOD 350 adds the supports, connections and penetrations that decide whether a spool fits. It is not worth it across a whole unit. Specify LOD 350 for the tie-in regions and the interfaces, LOD 300 for the surrounding as-built record, and let the rest sit lower."},{"q":"Can a point cloud be converted to CAD automatically?","a":"Automated extraction works well on straight, well-exposed cylindrical runs and degrades sharply with occlusion, insulation, small bore and fittings — which is where the hours are. Every production workflow uses automation for the easy 60% and human fitting for the rest, plus a human check on all of it. Treat vendor claims of full automation as claims about open racks, not about compressor houses."},{"q":"What is a deviation map and why should I ask for one?","a":"It is a colour rendering of the finished model measured against the registered point cloud, showing where modelled geometry departs from measured reality and by how much. It takes minutes to produce and it is the only objective acceptance test for represented accuracy. Without it, you are accepting a model on the contractor's word that it was fitted carefully rather than drawn approximately."},{"q":"Who owns the as-built model after the project?","a":"Whoever is named in the scope, and if nobody is named the answer in practice is nobody. Name the holder, the native format, the exchange format, and the event that triggers an update — most usefully any management-of-change that touches geometry. An unowned intelligent model is worth less than a maintained drawing set, because it looks authoritative while quietly going wrong."},{"q":"How long does an as-built model take?","a":"The pilot cell answers it. Model one congested 15 to 20 metre bay at the target level, count the hours, and scale by element density rather than by area. Congested process areas run several times the effort of racks and tank farms at the same level, and small-bore pipe dominates. Any schedule quoted before a pilot is an estimate of an area, not of the work."}]}