4.1.3.3.1. Building
A building is the highest level of a physical structure.
A building belongs to a site
A building is composed of one or multiple floors
Some devices can be associated at the site Level
For example, a fleet of floor cleaning machines is often associated to a building where it operates
4.1.3.3.1.1. FDS compliance requirements
4.1.3.3.1.1.1. Object Model
4.1.3.3.1.1.1.1. Space object for the building space type
The space type in the generic space object must be
“building”
The digital twin information provider must provide a space object that contains a space_type_specific object defined in the following diagram

Even though a building belongs to a site, it is possible that the building has its own postal address. Wen provided, the address object must follows Apple’s (Indoor Mapping Data Format) specifications
When the digital twin information provider provides additional information about the building, the composed_of property must be an array representing the list of floors in the building.
The type of the space objects represented by the list of space IDs must be “floor”
A building must be part of a site
The part_of property in the space generic object must refer to the site space the building belongs to
The detailed API specifications for each object can be found in the reference chapter.
4.1.3.3.1.1.2. Web API (Pull Model)
The digital twin information provider must implement the Web API as defined in the pull model specifications
4.1.3.3.1.1.3. Publish/Subscribe (Push model)
Note
No publish/subscribe messages related to digital twin information are defined in FDS Version 2
4.1.3.3.1.2. Use case example
4.1.3.3.1.2.1. Building space type
Note
Join FDS to get access to examples and use cases.