Universal Timber Slab: Simulated Multidisciplinary Performance Data for UTS Solid Timber Slab in Triangular Slab Bays at 1m Resolution

This ensures compatibility with the computational design method and future developments. All data is stored in JSON files that contain BHoM objects. Using SI units unless spefified differently.

Data Structure Following the structure of BHoM and JSON files, the data is organized in a nested structure. For each design geometry, a "Performance" section contains multiple "PerformanceSolutions" per bay. Thus, each disciplinary layer can autonomously generate different solutions, while a versioning system enables them to refer to and align with outputs from other layers, maintaining links between interconnected results.

Below you can find the description of the relevant data points that are the core results to measure and reproduce the dataset layer by layer. Layers 1-3 - Computational Design, design and Geometry Defines the geometry and organization of the slabs. Input Datapoint: Evert specimen defined in the default set at Slab Building Blocks dataset conforming Layer 0.

Output Datapoints: UTS.Slab: Slab general data container UTS.Slab.Baylayout.Bays.Bay: Bay geometry data container Performance Solutions Each bay of the slab is analyzed individually and different disciplines calculate different performance solutions based on the case and the previous information. Layer 4 - Slab Rerquirements Assumptions for slab dimensioning, such as floor occupancy, vibration requirements and additional loads.

Datapoint: PeformanceSolution.Requirements Input Datapoints: None Location: UTS.Slab.Baylayout.Bays.Bay.Performance.PerformanceSolutions Datapoint container: PeformanceSolution.Requirements Output Datapoints: OccupationalUse AdditionalDeadload ServiceClass FireRequirement MaxDeflectionFactor VibrationRequirement Layer 5 - Structural Design Engineering assessment and validation of slab performance under various load cases.

Input Datapoints: Bays - from Layers 0 to 3 Requirements - from Layer 4 Location: UTS.Slab.Baylayout.Bays.Bay.Performance.PerformanceSolutions Datapoint container: PeformanceSolution.Structure Output Datapoints: CalculatedSlabBuildUp EigenFrequencyRequirement MaxEstimatedDeflection MaxUtlization Layer 6 - Acoustics + Building Physics Simulation of acoustics performance and building physics parameters under defined load cases.

Input Datapoints: Bays - from Layers 0 to 3 EigenFrequencyRequirement - from Layer 5 Location: UTS.Slab.Baylayout.Bays.Bay.Performance.PerformanceSolutions Datapoint: PeformanceSolution.BuildingPhysics Output Datapoints: NormalizedSoundPressure_L_n ([dB]) SoundReductionR ([dB]) HeatAmount ([kWh/m²]) EffectiveHeatStorageCapacity_C_eff ([kg/m²]) EstimatedOverheatingHours ([Kh]) Layer 7 - Fabrication The data for the fabrication is removed due to IP protection, yet the calculated results at the Bill of quantities (BOQ) are taken into account for other Peformance Layers.

Input Datapoints: Bays - from Layers 0 to 3 CalculatedSlabBuildUp - from Layer 5 Location: UTS.Slab.Baylayout.Bays.Bay.Performance.PerformanceSolutions Datapoint: PeformanceSolution.Fabrication Output Datapoints: BOQ Layer 8 - Life Cycle Assessment Evaluation of different scenarios for the environmental performance results based on the bill of quantities (BOQ). Input Datapoints: BOQ - from Layer 7 Location: UTS.Slab.Baylayout.Bays.Bay.Performance.PerformanceSolutions Datapoint: PeformanceSolution.LCA Output Datapoints: GPW (Global Warming Potential) ([kg CO2 eq./m²] for modules A1 - C4 according to EN 15804) PEF (Product Enviromental Footprint [-/m²]) File naming Name example: Slab_2_3_5_LT1_CR2_GC5 Name parameters: Slab_A_B_C_LT#_CR#_GC# Each parameter is indexed with an integer to keep the names simple. -Triangle Edge Length (A_B_C) = refers to the triangle edges selection parameter in our sample domain.

The range for this data set was 4 to 12 meters.. -Column Head Radii (CR): CR2 = 0.65m -Lamella Thickness (LT): LT1 = 0.03m (with max 200x Bend Radius) -Group Count Cap (GC): 5 max. The amount of lamella groups (packages) was capped at 5.