16: Overview of 'building' package

Gallery
Tutorial
TRAIL: A SysML Pattern for Digital Twinning
Section
Topic level
INTERMEDIATE
UML keywords
AggregationKind
AggregationKind::composite
AggregationKind::none
AggregationKind::shared
SysML keywords
Block
Keywords
Slide kind
SysML Package Diagram
Click on the image to view it full size
It is assumed that any building (not just an office building) can have blinds and/or lights.

Advanced modelling concern

A «physical» Building has part properties light:Light[0..*] and/or blind:Blind[0..*] with AggregationKind 'composition'. These are matched by a «digital» @Building which has digital mapping equivalents *light:@Light[0..*] and *blind:@Blind[0..*].

As a first approximation, «physical» Light and «physical» Blind are not individually twinned. If one chose to do that (using a Composite Pattern with DigitalTwin), the «digital» @Building would then only reference «digital» @Light and «digital» @Blind.

Up next
17: Staging BDD for working environment temperature vs building energy consumption control loop
Notes
[CONVENTION]{SUBJECT-TO-CHANGE} Webel: Convention: [MIGHT CHANGE]: An '@' prefix in a DigitalTwin model indicates a «digital» Block that maps a non-digital «mappable» Block.
[POLICY]{STRICT} Webel Twin Pattern: It is a DigitalEntity (a.k.a. @Entity) - not the DigitalTwin that owns it - that directly «replicates» geometrical, spatial, and material aspects (only) of a single PhysicalEntity.
[POLICY]{STRICT} Webel Twin Pattern: A DigitalTwin manages a control loop including a PhysicalEntity and a DigitalEntity (a.k.a. @Entity) that «replicates» it. It typically includes at least one Sensor and at least one Actuator.
[WARNING]{INFORMATIVE} WARNING: In natural language casual conversation one often hears people speaking of a digital twin "replicating" or "twinning" a physical entity. If you do it that way literally, you will NOT have anything to manage the control system loop!
[POLICY]{STRICT} Webel Twin Pattern: The primary aim of the digitalEntity:@Entity of a DigitalTwin is to replicate its physical:PhysicalEntity as closely as possible (not to explore variants).
[POLICY]{STRICT} Webel Twin Pattern: Communication between the ControlSystem of a DigitalTwin and its digitalEntity:@Entity is via a dedicated protocol (ReadTwin, WriteTwin) distinct from the sensor reading or actuator driving signals.
Snippets (quotes/extracts)
 In contrast to traditional digital models, digital twins can connect with the physical ‘twin’ they model, changing alongside the physical system via real-time sensors and actuators.
 Sensors [DISPUTED] in office buildings for example, can adjust lights, blinds and temperature to balance optimal working environment with energy consumption, with the digital twin managing and adjusting in near real-time.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)