DATAMODEL.md — Workspace Management Data Model

Data model for the BBL Workspace Management Platform. Aligned with IFC 4.3 (buildingSMART), ArcGIS Indoors, Archilogic Space API, BuildingMinds, and CAFM conventions.

Overview

Entities

Entity	Description	DE Term	Data Source (Prototype)	IFC 4.3 Equivalent
Site	Location / campus area	Standort / Areal	`data/sites.json`	IfcSite
Building	Building / property	Gebäude / Liegenschaft	`data/buildings.geojson`	IfcBuilding
Floor	Storey / level	Geschoss / Stockwerk	`data/floors.geojson`	IfcBuildingStorey
Room	Room (smallest spatial unit)	Raum	`data/rooms.geojson`	IfcSpace
Workspace	Workspace within a room	Arbeitsplatz	Counter only (`workspaces`)	—
ProductCategory	Hierarchical product category	Produktkategorie	`data/categories.json`	IfcClassificationRef
Product	Catalog item (orderable)	Katalogartikel	`data/products.json`	IfcFurnitureType
InventoryItem	Tracked physical object (any type)	Inventarobjekt	`data/assets.geojson`	IfcFurniture
CircularListing	Circular economy listing (reuse)	Kreislauf-Angebot	`data/assets-circular.json`	—
Organization	Federal agency / organizational unit	Bundesstelle	Free text in checkout	—
Order	Order from the catalog	Bestellung	`state.cart` + checkout	—
OrderItem	Single order line item	Bestellposition	`state.cart[]`	—
PlanningExample	Showcase project for workspace planning	Planungsbeispiel	`data/planning-examples.json`	—
MultispaceModule	BBL Multispace workspace module	Multispace Modul	`data/multispace-module.json`	—
CadFile	CAD download section with file listings	CAD-Dateibereich	`data/cad-files.json`	—

Domain Model

graph LR
  subgraph Spatial Hierarchy
    Site -->|1:n| Building
    Building -->|1:n| Floor
    Floor -->|1:n| Room
    Room -->|1:n| Workspace
  end

  subgraph Product Catalog
    ProductCategory -->|1:n| ProductCategory
    ProductCategory -->|1:n| Product
  end

  subgraph Inventory & Circular Economy
    Product -.->|Type → Instance| InventoryItem
    InventoryItem -->|placed in| Room
    InventoryItem -->|0..1| CircularListing
  end

  subgraph Business Processes
    Organization -->|1:n| Order
    Order -->|1:n| OrderItem
    OrderItem -->|n:1| Product
  end

1. Spatial Hierarchy

The spatial hierarchy forms the backbone of occupancy planning. It follows the IFC principle IfcSite → IfcBuilding → IfcBuildingStorey → IfcSpace and extends it with a Workspace level for desk management.

1.1 Site (Standort)

A site encompasses an area or property with one or more buildings. In the Swiss federal administration, this typically represents an address group or campus.

Attribute	Type	Required	Description	DE Term	Reference
`siteId`	string	✓	Unique ID (e.g. `"ch"`, `"be"`)	Standort-ID	ArcGIS `SITE_ID`
`siteCode`	string		BBL internal site code	Standortcode	BuildingMinds `siteCode`
`name`	string	✓	Display name (e.g. `"Bern"`)	Bezeichnung	IFC `Name`
`nameLong`	string		Long name (e.g. `"Verwaltungsstandort Bern"`)	Langname	ArcGIS `NAME_LONG`
`type`	enum	✓	Site type	Standorttyp	BuildingMinds `type`
`address`	Address		Postal address (embedded)	Postadresse	BuildingMinds `addressIds`
`coords`	[lat, lng]		WGS84 coordinates	Koordinaten	—
`buildingCount`	integer		Number of buildings (derived)	Anzahl Gebäude	—
`validFrom`	date		Valid from	Gültig ab	BuildingMinds
`validUntil`	date		Valid until	Gültig bis	BuildingMinds

Enum SiteType:

Value (EN)	Value (DE)
Administrative site	Verwaltungsstandort
Military site	Militärstandort
Educational site	Bildungsstandort
Special-purpose site	Spezialstandort
Other	Andere

Prototype mapping: Corresponds to the canton nodes in LOCATIONS (be, zh, bs, lu). In a real model, the country node (ch) would be a top-level filter, not a Site.

1.2 Building (Gebäude)

A building is a single built structure with its own object code, address, and year of construction.

Attribute	Type	Required	Description	DE Term	Reference
`buildingId`	string	✓	Unique ID (e.g. `"b-001"`)	Gebäude-ID	ArcGIS `FACILITY_ID`
`siteId`	string	✓	FK → Site	Standort-FK	ArcGIS `SITE_ID`
`name`	string	✓	Display name (e.g. `"Bundeshaus Ost"`)	Bezeichnung	IFC `Name`
`objectCode`	string	✓	BBL object code (e.g. `"1502.AB"`)	Objekt-Nr.	BBL-specific
`address`	Address	✓	Full postal address	Postadresse	—
`centroid`	[lng, lat]		WGS84 centroid in GeoJSON order [lng, lat]	Zentroid	—
`geometry`	GeoJSON		Building footprint polygon (GeoJSON Polygon)	Gebäudeumriss	ArcGIS `FACILITY_AREA`
`yearBuilt`	string		Year / period of construction (e.g. `"1892"`)	Baujahr / Bauperiode	BBL `Bauperiode`
`status`	enum	✓	Building status	Gebäudestatus	BBL-specific
`category`	enum	✓	Building category	Gebäudekategorie	BBL-specific
`areaGross`	number		Gross floor area in m² (e.g. `12450`)	Bruttogeschossfläche	IFC `GrossFloorArea`
`heightRelative`	number		Building height in m	Gebäudehöhe	ArcGIS `HEIGHT_RELATIVE`
`floorCount`	integer		Number of storeys (derived)	Anzahl Geschosse	—
`photo`	string		Image URL / Unsplash ID	Bild-URL	Prototype
`validFrom`	date		Valid from	Gültig ab	BuildingMinds
`validUntil`	date		Valid until	Gültig bis	BuildingMinds
`extensionData`	json		Custom fields for client-specific attributes	Freifelder	BuildingMinds

Enum BuildingStatus:

Value (EN)	Value (DE)
Existing	Gebäude bestehend
Under construction	Im Bau
Planned	Geplant
Renovation	Sanierung
Demolition	Rückbau
Decommissioned	Stillgelegt

Enum BuildingCategory:

Value (EN)	Value (DE)
Administrative	Verwaltungsgebäude
Special-purpose	Spezialgebäude
Residential	Wohngebäude
Storage	Lagergebäude
Technical	Technisches Gebäude
Mixed-use	Mischnutzung
Other	Andere

Object code format: {Wirtschaftseinheit}.{BuildingLetters} — e.g. 1502.AB. The Wirtschaftseinheit is a BBL-internal economic unit identifier, the letters uniquely identify each building within that unit.

Prototype mapping: Stored as GeoJSON FeatureCollection in data/buildings.geojson. Each feature has a Polygon geometry (building footprint) and a centroid property in [lng, lat] format for point marker placement. Direct 1:1 correspondence to the Building nodes in LOCATIONS.

1.3 Floor (Geschoss / Stockwerk)

A floor represents a horizontally bounded level within a building. Follows the IFC principle of IfcBuildingStorey with explicit storey ordering.

Attribute	Type	Required	Description	DE Term	Reference
`floorId`	string	✓	Unique ID (e.g. `"b-001-eg"`)	Geschoss-ID	ArcGIS `LEVEL_ID`
`buildingId`	string	✓	FK → Building	Gebäude-FK	ArcGIS `FACILITY_ID`
`name`	string	✓	Display name (e.g. `"1. OG"`)	Anzeigename	ArcGIS `NAME`
`nameShort`	string	✓	Short name for floor filters (e.g. `"1"`)	Kurzname	ArcGIS `NAME_SHORT`
`levelNumber`	integer	✓	Building-specific level number (e.g. `0` = GF)	Geschossnummer	ArcGIS `LEVEL_NUMBER`
`verticalOrder`	integer	✓	0-based ordering: GF=0, basement<0, upper>0	Vertikale Ordnung	ArcGIS `VERTICAL_ORDER`
`areaGross`	number		Gross floor area in m² (e.g. `2650`)	Bruttogeschossfläche	ArcGIS `AREA_GROSS`
`heightRelative`	number		Storey height in m (e.g. `3.50`)	Geschosshöhe	ArcGIS/IFC
`workspaceCount`	integer		Number of workspaces (derived or stored)	Anzahl Arbeitsplätze	Prototype
`roomCount`	integer		Number of rooms (derived or stored)	Anzahl Räume	Prototype
`geometry`	GeoJSON		Floor outline polygon (GeoJSON Polygon)	Geschossumriss	ArcGIS `LEVEL_AREA`
`floorPlanUrl`	string		URL to 2D floor plan image (SVG/PNG)	Grundriss-URL	Archilogic Export
`floorPlanGeojson`	string		URL to GeoJSON room layout	Grundriss-GeoJSON	Archilogic GeoJSON
`bimModelUrl`	string		URL to IFC/glTF 3D model	BIM-Modell-URL	Archilogic Export

levelNumber vs verticalOrder: ArcGIS Indoors distinguishes between the building-specific level number (LEVEL_NUMBER, e.g. for elevator displays) and the sortable order (VERTICAL_ORDER). In Swiss buildings with UG/EG/OG designations (basement/ground/upper), this separation is useful: levelNumber can represent the official BBL floor designation, while verticalOrder serves sorting and navigation.

Swiss floor naming convention:

Name	DE Term	`levelNumber`	`verticalOrder`
UG	Untergeschoss	-1	-1
EG	Erdgeschoss	0	0
1. OG	1. Obergeschoss	1	1
2. OG	2. Obergeschoss	2	2
3. OG	3. Obergeschoss	3	3

Prototype mapping: Stored as GeoJSON FeatureCollection in data/floors.geojson. Each feature has a Polygon geometry (floor outline, inset from the building footprint by a wall margin representing the structural envelope). Rooms are stored separately in data/rooms.geojson and joined at runtime via floorId. Direct 1:1 correspondence to Floor nodes in LOCATIONS.

Floor plan note: The prototype shows a map placeholder in the "Karte" tab. In the target architecture, this would reference either a static SVG (floorPlanUrl), an interactive GeoJSON floor plan (floorPlanGeojson), or a 3D model (bimModelUrl), comparable to the Archilogic Floor Plan Engine or the BuildingMinds 3D viewer.

1.4 Room (Raum)

A room is the smallest spatial unit — a physically bounded area within a floor. Corresponds to IfcSpace / ArcGIS Units / Archilogic Space.

Attribute	Type	Required	Description	DE Term	Reference
`roomId`	string	✓	Unique ID (e.g. `"b-001-eg-101"`)	Raum-ID	ArcGIS `UNIT_ID`
`floorId`	string	✓	FK → Floor	Geschoss-FK	ArcGIS `LEVEL_ID`
`name`	string	✓	Room number (e.g. `"EG01"`)	Raumnummer	IFC `Name`
`nameLong`	string		Long name (e.g. `"Reception Ground Floor"`)	Langname	IFC `LongName`
`useType`	enum	✓	Room use type	Raumnutzungstyp	IFC `ObjectType`, ArcGIS `USE_TYPE`
`areaGross`	number		Room area in m² (e.g. `28.5`)	Raumfläche	ArcGIS `AREA_GROSS`
`heightRelative`	number		Clear room height in m	Lichte Raumhöhe	ArcGIS `HEIGHT_RELATIVE`
`capacity`	integer		Maximum occupancy / workspaces	Kapazität	IFC `Pset_SpaceOccupancyRequirements`
`isBookable`	boolean		Room is bookable (meeting rooms etc.)	Buchbar	BuildingMinds Booking
`occupancy`	enum		Occupancy status	Belegungsstatus	CAFM
`organizationId`	string		FK → Organization (assigned tenant)	Organisation-FK	CAFM
`geometry`	GeoJSON		Polygon geometry of the room	Geometrie	Archilogic/ArcGIS
`extensionData`	json		Custom fields	Freifelder	BuildingMinds

Enum RoomUseType (aligned with SIA 416 / DIN 277):

Value (EN)	Value (DE)
Office	Büro
Meeting room	Sitzungszimmer
Open space	Open Space
Reception	Empfang
Kitchenette	Teeküche
WC	WC
Corridor	Korridor
Storage	Lager
Technical room	Technikraum
Cloakroom	Garderobe
Print room	Druckerraum
Focus room	Fokusraum
Lounge	Lounge
Cafeteria	Cafeteria
Training room	Schulungsraum
Archive	Archiv
Other	Andere

Enum OccupancyStatus:

Value (EN)	Value (DE)
Vacant	Frei
Partially occupied	Teilbelegt
Fully occupied	Vollbelegt
Blocked	Gesperrt
Under renovation	Sanierung

Prototype mapping: Rooms are stored as standalone GeoJSON features in data/rooms.geojson. Each feature has a roomId ({floorId}-{nr}), floorId, buildingId, nr (room number), type (use type), area (m²), workspaces (workspace count), and a Polygon geometry. Rooms are arranged in a double-loaded corridor layout within each floor footprint: a central E-W corridor (2.5 m wide) divides rooms into north and south wings (5.5 m room depth). Room widths are proportional to their area. Room types are color-coded on the map (Büro = blue, Sitzungszimmer = orange, Open Space = green, Empfang = purple, etc.). At runtime, rooms are reconstructed as arrays per floor for backward compatibility with the location tree.

1.5 Workspace (Arbeitsplatz)

A workspace is the finest functional unit — an individual desk or station within a room that can be assigned to a person or function. This concept originates from CAFM systems and the BuildingMinds workspace management feature.

Attribute	Type	Required	Description	DE Term	Reference
`workspaceId`	string	✓	Unique ID (e.g. `"ws-001-eg-101-a"`)	Arbeitsplatz-ID	CAFM
`roomId`	string	✓	FK → Room	Raum-FK	—
`name`	string	✓	Display name (e.g. `"Desk A"`)	Bezeichnung	—
`workspaceType`	enum	✓	Workspace type	Arbeitsplatztyp	BuildingMinds Work Area
`isAssigned`	boolean		Permanently assigned?	Fest zugewiesen	CAFM
`assignedTo`	string		Personnel number / name of assigned person	Zugewiesene Person	CAFM
`organizationId`	string		FK → Organization	Organisation-FK	CAFM
`equipment`	string[]		List of assigned InventoryItem IDs	Ausstattung	—
`position`	{x, y}		Position in floor plan (pixels or meters)	Position	Archilogic Asset
`rotation`	number		Rotation in degrees	Rotation	Archilogic Asset

Enum WorkspaceType (aligned with BBL workspace standards):

Value (EN)	Value (DE)
Focus workspace	Fokus-Arbeitsplatz
Flex workspace	Flex-Arbeitsplatz
Sit-stand workspace	Steh-Sitz-Arbeitsplatz
Meeting seat	Besprechungsplatz
Lounge seat	Lounge-Platz
Hot desk	Hotdesk
Phone booth	Telefonkabine
Other	Andere

Prototype mapping: In the prototype, workspaces exist as a workspaces counter at floor/room level but are not modeled as independent entities.

2. Product Catalog

2.1 ProductCategory

Hierarchical categorization of the furniture catalog. Supports up to 3 levels.

Attribute	Type	Required	Description	DE Term
`categoryId`	string	✓	Unique ID (e.g. `"stuehle"`)	Kategorie-ID
`parentId`	string		FK → ProductCategory (null = root category)	Eltern-FK
`label`	string	✓	Display name (e.g. `"Stühle"`)	Anzeigename
`sortOrder`	integer		Sort position within level	Sortierposition

Prototype mapping: Direct 1:1 correspondence to categories.json. The hierarchical nesting (children) is modeled via parentId.

2.2 Product (Katalogartikel)

A catalog item in the BBL standard assortment — an orderable furniture type with price and availability.

Attribute	Type	Required	Description	DE Term
`productId`	integer	✓	Unique ID	Produkt-ID
`name`	string	✓	Product name (e.g. `"Bürostuhl Giroflex 64"`)	Produktbezeichnung
`description`	string		Short description	Kurzbeschreibung
`brand`	string	✓	Brand / manufacturer (e.g. `"Giroflex"`)	Marke / Hersteller
`categoryId`	string	✓	FK → ProductCategory (main category)	Hauptkategorie-FK
`subcategoryId`	string		FK → ProductCategory (subcategory)	Unterkategorie-FK
`price`	number	✓	Price in base currency (excl. VAT)	Preis
`currency`	string	✓	ISO currency code (default `"CHF"`)	Währung
`isNew`	boolean		Marked as "New"	Neu
`isCircular`	boolean		Used furniture (circular economy)	Kreislaufwirtschaft
`photo`	string		Product image path relative to `assets/` (e.g. `"images/barhocker-dietiker-ono.jpg"`)	Produktbild-Pfad
`photos`	string[]		Gallery image paths relative to `assets/` (optional)	Galerie-Bilder
`dimensions`	Dimensions		Dimensions (W×D×H cm) — used by floorplan editor for placement sizing and 3D extrusion height	Abmessungen
`color3d`	string		Hex color for 3D extruded fallback geometry (e.g. `"#64748B"`)	3D-Farbe
`shape2d`	enum		2D floor plan shape: `"circle"` \| `"rect"` \| `"diamond"`	2D-Form
`model3d`	string	✓	GLB/glTF model path relative to `assets/` (e.g. `"3d/barhocker.glb"`); empty string = fallback to extruded geometry	3D-Modell-Pfad
`weight`	number		Weight in kg	Gewicht
`material`	string		Primary material (e.g. `"Fabric Anthracite"`)	Hauptmaterial
`color`	string		Color	Farbe
`articleNumber`	string		Manufacturer article number	Herstellerartikelnr.
`availability`	enum		Availability status	Verfügbarkeitsstatus
`leadTimeDays`	integer		Lead time in business days	Lieferfrist

Embedded Dimensions:

{ width: number, depth: number, height: number, unit: "cm" }

Enum Availability:

Value (EN)	Value (DE)
Available	Verfügbar
Limited availability	Begrenzt verfügbar
On request	Auf Anfrage
Unavailable	Nicht verfügbar

Asset directory structure:

assets/
├── 3d/          ← GLB/glTF 3D models referenced by model3d
└── images/      ← Product images referenced by photo/photos

All asset paths in products.json are relative to the assets/ directory. Code in root-level pages resolves as assets/{path}, while the floorplan editor (in floorplan-editor/) resolves as ../assets/{path}.

Prototype mapping: Direct 1:1 correspondence to products.json. The fields dimensions, color3d, shape2d, and model3d are implemented in the floorplan editor — products define visual geometry (dimensions, color, shape, 3D model) and assets reference products via productId. The model3d field is present on all products; empty string triggers fallback to extruded geometry in the 3D viewer. The fields weight, material, color, articleNumber, leadTimeDays are extensions beyond the current prototype.

3. Inventory & Circular Economy

3.1 InventoryItem (Inventarobjekt)

A physical instance of a product — a specific tracked object located at a particular place that is inventoried. Covers furniture, IT equipment, fixtures, appliances, and any other physical item. Corresponds to the IFC concept IfcFurniture or Archilogic Asset.

Attribute	Type	Required	Description	DE Term	Reference
`itemId`	string	✓	Unique ID (e.g. `"INV-2024-001234"`)	Inventar-ID	IFC `GlobalId`
`productId`	integer		FK → Product (catalog reference, if assignable)	Produkt-FK	IFC `IsTypedBy`
`name`	string	✓	Display name (e.g. `"Bürostuhl Giroflex 64"`)	Bezeichnung	IFC `Name`
`inventoryNumber`	string	✓	BBL inventory number (e.g. `"INV-2024-001234"`)	Inventarnummer	CAFM
`serialNumber`	string		Manufacturer serial number	Seriennummer	—
`brand`	string		Brand (redundant if productId is set)	Marke	—
`categoryId`	string		FK → ProductCategory	Kategorie-FK	—
`buildingId`	string		FK → Building (current building)	Gebäude-FK	—
`floorId`	string		FK → Floor (current floor)	Geschoss-FK	—
`roomId`	string		FK → Room (current location)	Raum-FK	IFC `ContainedInSpatialStructure`
`workspaceId`	string		FK → Workspace (if assigned)	Arbeitsplatz-FK	—
`status`	enum	✓	Current status	Status	CAFM
`condition`	enum		Physical condition	Zustand	Prototype
`acquisitionDate`	date		Acquisition date	Beschaffungsdatum	CAFM
`acquisitionCost`	number		Acquisition cost CHF	Beschaffungspreis	CAFM
`organizationId`	string		FK → Organization (responsible agency)	Organisation-FK	CAFM
`position`	{x, y}		Position in floor plan	Position	Archilogic Asset
`rotation`	number		Rotation in degrees	Rotation	Archilogic Asset
`qrCode`	string		QR code content (URL or inventory number)	QR-Code	Prototype "Scan"
`notes`	string		Notes	Bemerkungen	—

Enum InventoryStatus:

Value (EN)	Value (DE)
Active	Aktiv
In storage	Eingelagert
For disposal	Zur Abgabe
Reserved	Reserviert
In transfer	Im Transfer
Disposed	Entsorgt

Enum InventoryCondition:

Value (EN)	Value (DE)
Very good	Sehr gut
Good	Gut
Acceptable	Akzeptabel
Needs repair	Reparaturbedürftig
Defective	Defekt

Prototype mapping: Active inventory items are stored as GeoJSON features in data/assets.geojson with Polygon geometry (small rectangles positioned within the assigned room). data/assets.geojson is the single source of truth for all inventory items (61 items). Each asset feature includes a centroid property [lng, lat] for future drag-to-reposition editing. Assets are displayed on the map at zoom >= 18. Items are linked to their spatial location via buildingId, floorId, and roomId.

Product-driven enrichment: All 61 assets have a productId set, linking them to a Product in data/products.json. At load time, the floorplan editor enriches each asset with derived _* properties from its product:

Enriched Property	Source	Description
`_product`	Product object	Full product reference
`_model3dUrl`	`product.model3d`	Resolved GLB model URL
`_name`	`product.name`	Display name
`_brand`	`product.brand`	Brand
`_categoryId`	`product.subcategory \|\| product.category`	Category ID
`_height`	`product.dimensions.height / 100`	Height in meters for 3D extrusion
`_color3d`	`product.color3d`	Hex color for 3D fallback geometry
`_shape2d`	`product.shape2d`	2D floor plan shape

Renderers use enriched _* properties with fallback to raw asset properties (e.g. _name || name) for backward compatibility. The raw fields name, brand, categoryId, baseHeight, topHeight are retained in assets.geojson because the occupancy page reads them directly via Mapbox GL expressions.

3.2 CircularListing (Kreislauf-Angebot)

When an inventory item is released for reuse, a circular listing is created — comparable to a posting in an internal marketplace.

Attribute	Type	Required	Description	DE Term
`listingId`	string	✓	Unique ID	Angebots-ID
`itemId`	string	✓	FK → InventoryItem	Inventar-FK
`offeredBy`	string	✓	FK → Organization (offering agency)	Anbietende Stelle
`price`	number		Transfer price CHF (0 = free transfer)	Abgabepreis
`condition`	enum	✓	Condition at time of listing	Zustand
`description`	string		Free text description	Beschreibung
`photos`	string[]		Image URLs	Bilder
`listingStatus`	enum	✓	Listing status	Angebotsstatus
`listedAt`	datetime	✓	Creation date	Erstellt am
`expiresAt`	datetime		Expiration date	Ablaufdatum

Enum ListingStatus:

Value (EN)	Value (DE)
Active	Aktiv
Reserved	Reserviert
Awarded	Vergeben
Expired	Abgelaufen
Withdrawn	Zurückgezogen

Prototype mapping: Direct 1:1 correspondence to data/assets-circular.json These items are also included in data/assets.geojson for map display. In the target architecture, a CircularListing would be a separate entity referencing a specific InventoryItem.

4. Business Processes

4.1 Organization (Bundesstelle)

An organizational unit of the Swiss federal administration acting as client and user of spaces and furniture.

Attribute	Type	Required	Description	DE Term
`organizationId`	string	✓	Unique ID	Organisation-ID
`name`	string	✓	Name (e.g. `"Bundesamt für Bauten und Logistik"`)	Bezeichnung
`abbreviation`	string		Abbreviation (e.g. `"BBL"`)	Kurzform
`department`	string		Parent department (e.g. `"EFD"`)	Departement
`costCenter`	string		Cost center (e.g. `"KST-4200-001"`)	Kostenstelle
`contactName`	string		Contact person	Kontaktperson
`contactEmail`	string		Contact email	E-Mail
`billingAddress`	Address		Billing address	Rechnungsadresse

Prototype mapping: Captured as free text fields in the checkout form ("Bundesstelle / Organisation", "Kostenstelle", "Kontaktperson", "E-Mail").

4.2 Order (Bestellung)

An order placed by a client (federal agency) from the product catalog.

Attribute	Type	Required	Description	DE Term
`orderId`	string	✓	Unique order number	Bestellnummer
`organizationId`	string	✓	FK → Organization (orderer)	Besteller-FK
`orderDate`	datetime	✓	Order timestamp	Bestellzeitpunkt
`status`	enum	✓	Order status	Bestellstatus
`billingAddress`	Address	✓	Billing address	Rechnungsadresse
`deliveryAddress`	DeliveryAddress	✓	Delivery address incl. building/room	Lieferadresse
`deliveryNotes`	string		Delivery instructions	Lieferhinweise
`totalAmount`	number		Total amount excl. VAT (derived)	Gesamtbetrag
`currency`	string	✓	ISO currency code (`"CHF"`)	Währung
`costCenter`	string		Cost center for billing	Kostenstelle
`orderedBy`	string		Name of the ordering person	Besteller
`orderedByEmail`	string		Email of the ordering person	Besteller-E-Mail

Enum OrderStatus:

Value (EN)	Value (DE)
Draft	Entwurf
Submitted	Übermittelt
In progress	In Bearbeitung
Partially delivered	Teilgeliefert
Delivered	Geliefert
Completed	Abgeschlossen
Cancelled	Storniert

Embedded DeliveryAddress:

{
  buildingId:   string     // FK → Building (optional)
  buildingName: string     // Free text if Building not linked
  floor:        string     // Floor / room (e.g. "3. OG, Raum 312")
  street:       string
  postalCode:   string
  city:         string
  country:      string     // default "CH"
}

Prototype mapping: The 3-step checkout (cart → address → submit) implements the ordering process. Fields are taken directly from the form.

4.3 OrderItem (Bestellposition)

A single line item within an order.

Attribute	Type	Required	Description	DE Term
`orderItemId`	string	✓	Unique ID	Positions-ID
`orderId`	string	✓	FK → Order	Bestell-FK
`productId`	integer	✓	FK → Product	Produkt-FK
`quantity`	integer	✓	Order quantity	Bestellmenge
`unitPrice`	number	✓	Unit price at time of order	Stückpreis
`lineTotal`	number		Line total (quantity × unitPrice, derived)	Positionsbetrag

Prototype mapping: Corresponds to state.cart[] entries with { productId, quantity }.

5. Shared Types

5.1 Address (Postadresse)

Embedded object, not a standalone entity.

{
  street:      string    // "Bundesgasse 3"
  postalCode:  string    // "3003"
  city:        string    // "Bern"
  canton:      string    // "BE"
  country:     string    // "CH"
}

6. Relationships (Entity-Relationship)

erDiagram
    Site ||--o{ Building : "contains"
    Building ||--o{ Floor : "contains"
    Floor ||--o{ Room : "contains"
    Room ||--o{ Workspace : "contains"
    Room ||--o{ InventoryItem : "hosts"
    Workspace ||--o{ InventoryItem : "assigned"

    ProductCategory ||--o{ ProductCategory : "hierarchy"
    ProductCategory ||--o{ Product : "categorizes"

    Product ||--o{ InventoryItem : "Type → Instance"
    Product ||--o{ OrderItem : "ordered"

    InventoryItem ||--o| CircularListing : "reuse"

    Organization ||--o{ Order : "places"
    Organization ||--o{ Room : "uses"
    Organization ||--o{ Workspace : "assigned"
    Organization ||--o{ InventoryItem : "responsible"

    Order ||--o{ OrderItem : "contains"

7. IFC / Prototype Delimitation

The data model deliberately adopts terms and structures from IFC 4.3 without replicating the full complexity of the BIM standard. The following table shows the key mapping decisions:

This Model	IFC 4.3 Equivalent	Simplification
Site	IfcSite	No geo-referencing (EPSG)
Building	IfcBuilding	No IfcRelAggregates hierarchy
Floor	IfcBuildingStorey	No elevations / Z-values
Room	IfcSpace	No CompositionType (COMPLEX/PARTIAL)
Workspace	— (no IFC equivalent)	CAFM extension
InventoryItem	IfcFurniture	No geometry (Brep/SweptSolid)
Product	IfcFurnitureType	Simplified type definition
ProductCategory	IfcClassificationReference	Flat hierarchy instead of IfcClassification

8. Data Source Mapping (Current → Target)

Entity	Prototype Source	Target System (Example)
Site	`LOCATIONS` canton nodes	SAP RE-FX / Real Estate Master
Building	`data/buildings.geojson`	SAP RE-FX / Real Estate Master
Floor	`data/floors.geojson`	SAP RE-FX + CAD/BIM
Room	`data/rooms.geojson`	SAP RE-FX + BIM (IFC)
Workspace	Counter only (`workspaces`)	CAFM system / Booking tool
Product	`data/products.json`	SAP MM / Catalog API
ProductCategory	`data/categories.json`	SAP MM / Catalog API
InventoryItem	`data/assets.geojson`	SAP PM / CAFM system
CircularListing	`data/assets-circular.json`	Circular marketplace service
Organization	Free text in checkout form	LDAP / Admin Directory
Order	`state.cart` + checkout	SAP MM / Order portal
OrderItem	`state.cart[]` entries	SAP MM / Order portal
PlanningExample	`data/planning-examples.json`	CMS / Content API
MultispaceModule	`data/multispace-module.json`	CMS / Content API
CadFile	`data/cad-files.json`	DMS / Content API

9. Content & Inspiration

9.1 PlanningExample (Planungsbeispiel)

A showcase project illustrating a completed or reference workspace planning implementation. Used on the platform to provide inspiration and demonstrate best practices for different workspace scenarios.

Attribute	Type	Required	Description	DE Term
`title`	string	✓	Project title (e.g. `"Administration Building Bern"`)	Titel
`description`	string	✓	Short description of the project scope and approach	Beschreibung
`photo`	string	✓	Image URL / Unsplash photo ID	Bild-URL

Prototype mapping: Direct 1:1 correspondence to data/planning-examples.json. Each entry represents a reference project card shown in the inspiration section.

9.2 MultispaceModule (Multispace Modul)

A standardized workspace module from the BBL Multispace Handbuch. Each module defines a coherent furnishing concept for a specific workspace scenario — from individual desks to meeting rooms and service areas. Based on the Handbuch Multispace (v8, 31.10.2025) of the Federal Office for Buildings and Logistics (BBL).

Attribute	Type	Required	Description	DE Term
`module`	string	✓	Module number (e.g. `"1"`)	Modul-Nr.
`title`	string	✓	Module title (e.g. `"Modul 1 – Standardarbeitsplatz"`)	Titel
`description`	string	✓	Description of the module concept	Beschreibung
`photo`	string	✓	Image URL / Unsplash photo ID	Bild-URL
`areaPerWorkspace`	string		Area guideline (e.g. `"3.0 m²"`, `"variabel"`)	Flächenrichtmass
`elements`	string[]		List of furniture/equipment elements	Ausstattungselemente

Module overview (Handbuch Multispace v8):

Nr	Title	Area per Workspace
1	Standardarbeitsplatz	3.0 m²
2	Team Arbeitsplatz	25–35 m²
3	Fokus Arbeitsplatz	3.0 m²
4	Formelle Sitzungen	19–25 m²
5	Telefon-/Videokonferenzbox	4.5 m²
6	Informelle Sitzungen	4–23 m²
7	Interaktive Sitzungen	30–65 m²
8	Team Ablage	variabel
9	Locker, Garderoben	variabel
10	Service Funktionen	variabel

Prototype mapping: Direct 1:1 correspondence to data/multispace-module.json. Each entry represents a module card in the planning section, with a detail page accessible via #/multispace-module/{moduleNr}.

9.3 CadFile (CAD-Dateibereich)

A downloadable CAD section grouping related architectural drawings, floor plans, and 3D models. Each section contains multiple files in various formats (DWG, PDF, IFC, SKP) that planners can download for workspace design.

Attribute	Type	Required	Description	DE Term
`id`	string	✓	Unique section ID (e.g. `"open-space"`)	Bereichs-ID
`title`	string	✓	Section title (e.g. `"Open Space"`)	Titel
`files`	CadFileEntry[]	✓	Array of downloadable files	Dateien

Embedded CadFileEntry:

Attribute	Type	Required	Description	DE Term
`name`	string	✓	File display name	Dateiname
`format`	string	✓	File format (e.g. `"DWG"`, `"PDF"`, `"IFC"`, `"SKP"`)	Format
`size`	string	✓	Human-readable file size (e.g. `"245.30 kB"`)	Dateigrösse
`date`	string	✓	Publication / last updated date	Datum

Prototype mapping: Direct 1:1 correspondence to data/cad-files.json. Each entry represents an accordion section in the CAD downloads area, with nested file entries shown as download rows.

10. Extension Potential

The following entities are not modeled in the current prototype but would be relevant for production use:

Entity	Description	DE Term	Standard Reference
AreaMeasurement	Area metrics (HNF, NNF, VF per SIA 416)	Flächenkennzahlen	BuildingMinds, DIN 277
Booking	Room / workspace booking	Raum-/Arbeitsplatzbuchung	BuildingMinds Booking
MaintenanceTask	Maintenance and repair orders	Wartungsaufträge	CAFM / SAP PM
Document	Linked documents (CAD, photos, contracts)	Verknüpfte Dokumente	IFC IfcDocumentReference
Detail	Architectural elements (walls, doors, windows)	Architekturelemente	ArcGIS Indoors `Details`
EnergyRating	Building energy rating (GEAK, Minergie)	Energiebewertung	BuildingMinds
FloorPlanLayer	Planning layers (furniture, electrical, HVAC)	Planungsebenen	Archilogic Layout
Person	Employees with workspace assignments	Mitarbeitende	LDAP / HR
Lease	Lease contracts and conditions	Mietverträge	SAP RE-FX

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DATAMODEL.md — Workspace Management Data Model

Overview

Entities

Domain Model

1. Spatial Hierarchy

1.1 Site (Standort)

1.2 Building (Gebäude)

1.3 Floor (Geschoss / Stockwerk)

1.4 Room (Raum)

1.5 Workspace (Arbeitsplatz)

2. Product Catalog

2.1 ProductCategory

2.2 Product (Katalogartikel)

3. Inventory & Circular Economy

3.1 InventoryItem (Inventarobjekt)

3.2 CircularListing (Kreislauf-Angebot)

4. Business Processes

4.1 Organization (Bundesstelle)

4.2 Order (Bestellung)

4.3 OrderItem (Bestellposition)

5. Shared Types

5.1 Address (Postadresse)

6. Relationships (Entity-Relationship)

7. IFC / Prototype Delimitation

8. Data Source Mapping (Current → Target)

9. Content & Inspiration

9.1 PlanningExample (Planungsbeispiel)

9.2 MultispaceModule (Multispace Modul)

9.3 CadFile (CAD-Dateibereich)

10. Extension Potential

FilesExpand file tree

DATAMODEL.md

Latest commit

History

DATAMODEL.md

File metadata and controls

DATAMODEL.md — Workspace Management Data Model

Overview

Entities

Domain Model

1. Spatial Hierarchy

1.1 Site (Standort)

1.2 Building (Gebäude)

1.3 Floor (Geschoss / Stockwerk)

1.4 Room (Raum)

1.5 Workspace (Arbeitsplatz)

2. Product Catalog

2.1 ProductCategory

2.2 Product (Katalogartikel)

3. Inventory & Circular Economy

3.1 InventoryItem (Inventarobjekt)

3.2 CircularListing (Kreislauf-Angebot)

4. Business Processes

4.1 Organization (Bundesstelle)

4.2 Order (Bestellung)

4.3 OrderItem (Bestellposition)

5. Shared Types

5.1 Address (Postadresse)

6. Relationships (Entity-Relationship)

7. IFC / Prototype Delimitation

8. Data Source Mapping (Current → Target)

9. Content & Inspiration

9.1 PlanningExample (Planungsbeispiel)

9.2 MultispaceModule (Multispace Modul)

9.3 CadFile (CAD-Dateibereich)

10. Extension Potential