Switzerland is useful as a regional adapter because the Swiss references combine ISO 19650 terminology, national glossary work, public procurement guidance and operation-oriented BIM2FM practice.
Contents
Why Switzerland is useful
Switzerland is useful as a regional profile because it is multilingual, procurement-aware and lifecycle-oriented. It also sits between German, French and Italian terminology, which makes it a good example for local terminology and procurement adapters.
| Need | Swiss reference | How we use it |
|---|---|---|
| Common terminology | National Glossary by BdCH/bSCH, CRB, SBB, SIA. | Language tags and glossary pages. |
| Process model | BIM-Abwicklungsmodell. | Workflow model and role/state naming. |
| Public clients | KBOB recommendations on BIM. | Procurement and data-sovereignty arguments. |
| Operation handover | BIM2FM, AIM, data field catalogue. | Lifecycle event families beyond BCF. |
| International fit | SN EN ISO 19650, EN 17412, buildingSMART standards. | Compatibility with broader openBIM tooling. |
Reference stack
The Swiss stack is not a replacement for buildingSMART International. It is the national process layer on top of the international standards.
buildingSMART International -> IFC, BCF, IDS, bSDD, openCDE ISO / EN / SN EN -> ISO 19650, EN 17412, EN ISO 29481 Bauen digital Schweiz / buildingSMART Switzerland -> BIM-Abwicklungsmodell, National Glossary, Stufenplan, Expert Groups KBOB -> public-client BIM recommendations Gemeinwert / BIM-CVP -> signed event workflow and interoperable clients
BIM-Abwicklungsmodell
The BIM-Abwicklungsmodell explains information management in digital planning, construction and operation across the life cycle. For this wiki, its most useful contribution is structure: it separates organisation, project and asset/operator layers and links information requirements to use cases, information delivery and CDE workflow.
| Concept | Workflow meaning | Event implication |
|---|---|---|
| Organisation needs | Strategic information requirements above one project. | 30880 reusable requirement sets. |
| Project delivery | PIM and project-specific delivery rules. | 30902, 30904, 30970. |
| Asset operation | AIM handover and operation information. | Lifecycle and maintenance event families. |
| Use cases / IDM | Define why information is exchanged. | Project use-case tags and IDS references. |
| CDE workflow | Stateful information containers. | ISO state tags and approval events. |
KBOB and public clients
KBOB is important because it frames BIM for public and institutional clients. For BIM-CVP, KBOB-style requirements translate into explicit contract annexes: open standards, structured data delivery, data ownership, security, liability and clear handover rules.
National Glossary
The National Glossary matters more than it looks. If German, French and Italian teams use different words for the same role or state, the software must not silently collapse them. BIM-CVP should store stable internal codes and render national labels per language.
| Internal code | Swiss/ISO-facing label | Why code wins |
|---|---|---|
appointing-party | Client / Auftraggeberseite | Same role can render differently by country. |
lead-appointed | Lead appointed party | ISO-compatible for international projects. |
info-manager | Information manager / BIM manager context | Country-specific title, stable permission group. |
Shared | Shared / geteilt / condiviso | State machine must not depend on UI language. |
BIM2FM and AIM
BIM2FM is where the workflow stops being only planning coordination. The owner needs an Asset Information Model, data fields for operation, and a way to connect project information to facility management. In the event model this means BCF is only the first workflow; maintenance, product data, site diary, LCA and approvals are the next layers.
PIM during design/construction -> IFC file references -> BCF topics -> IDS validation -> approval handover -> AIM package -> operation data field catalogue -> maintenance cycles -> product data and evidence links
Event mapping
| Swiss process object | Event mapping | Notes |
|---|---|---|
| BIM-Abwicklungsmodell profile | 30902 project extensions | Value lists, roles, stage naming, language policy. |
| KBOB public-client requirements | 30880, 30970 | Requirement sets and formal approvals. |
| National glossary term | lang tags, content label maps | Stable internal code, multilingual rendering. |
| BIM2FM data field | 30881, 30962, product data events | Handover and operation data. |
| CDE state | iso19650-state, 30970 | State transition requires signed approval. |
Read on
- buildingSMART International — global standards layer
- Workflow model — implementation process
- ISO 19650 — state and role model
- Field guide: Switzerland