CoClass, BIP and BK04: how Swedish classification fits a decision chain
Three Swedish reference systems, three different jobs. Confusing them is one of the most common causes of unreliable classification in Swedish projects.
Swedish project data routinely carries several classification systems at once, and teams often treat them as interchangeable labels. They are not. Each answers a different question, and each has a different standing in a decision chain.
Three different questions
| System | Question it answers | Typical carrier |
|---|---|---|
| CoClass | What kind of built asset, system or component is this? | Classification codes on model objects and documents |
| BIP | How are properties and names written consistently? | Parameter and naming conventions in authoring tools |
| BK04 | How is product and supplier data structured commercially? | Product data and catalogue structures |
A CoClass code is a statement about the nature of the object. A BIP-conformant parameter is a statement about how information is written down. A BK04 structure is a statement about how products are organised for trade. Mixing them produces the classic Swedish BIM failure: a well-named object that nobody can price, or a priced product nobody can classify.
Where each one enters the chain
- Classification systems inform identity and system classification — the top of the chain, where an element's nature is established.
- Naming and property conventions improve the quality of evidence, which raises how much of a model can be classified without manual work.
- Product data structures belong further down, at product selection and price resolution, where a real SKU must satisfy a material requirement.
The ordering is not stylistic. A product taxonomy is supplier-side; it describes what is sold. A material class is upstream authority; it describes what is required. Letting a supplier taxonomy define a requirement inverts the chain and makes the requirement change every time a catalogue does.
Adapters, not assumptions
Consuming these systems well means writing deterministic adapters with provenance: the adapter records which source revision it read, what it mapped, what it refused to map, and why. Unmapped items stay visibly unmapped. Silent best-effort matching is the failure mode to design against.
Practical advice for Swedish project teams
- Agree which system is authoritative for which question before modelling starts, and write it into the information requirements.
- Keep Swedish terminology consistent in Swedish reference models; mixed-language parameters degrade every downstream match.
- Treat an empty classification field as a visible gap to resolve, not as a value to infer later.
- Record source revisions. A classification mapping without a version is not reproducible.