Experimental cooling data in KUBIK lab-building during the 2020 season. HOLISDER project pre-pilot testing activities.

Open data API in a single place

Provided by Zenodo

Get early access to Experimental cooling data in KUBIK lab-building during the 2020 season. HOLISDER project pre-pilot testing activities. API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2021.06.10 00:00
Created
2021.05.10
Available languages
English
Keywords
SCADA, Space cooling data, fan-coil, cooling demand
Quality scoring

Dataset description

The data in this dataset is derived from the one of the pre-validation tests of the HOLISDER European project http://holisder.eu/ . The testing premises consist of an enclosed area in the ground floor of KUBIK by TECNALIA Research & Innovation (a three floors experimental buildings, including an underground basement where central HVAC equipment are located). The ground floor is cooled through two fan-coil, as terminal units, while the cooling generation was performed by two chillers located in the basement. The SCADA system of the building records operation temperatures, mass flows, delivered power, fan-coils operation volume, setpoint temperatures and operation modes. The test was carried out from 01/07/20 to 31/10/2020 under strict cooling comfort boundaries in order to characterize the premise’s systems. One file is provided as a xlsx file with the following features with 10-minute frequency: (Disclaimer: Provided dataset is raw-data and null or error values were not deleted from it) Weather station              METEO_RoofSR_Global.PV: Global horizontal radiation METEO_GardenWS_AT.PV: Outdoor dry bulb temperature FANCOIL 1          F0N2_FCM1.Enable: Fancoil1 enabled F0N2_FCM1.PV: Fancoil1 thermostat reading F0N2_FCM1.SP: Fancoil1 thermostat setpoint F0N2_FCM1.ST_COOL_Mode: Fancoil on cooling mode F0N2_FCM1.ST_HOT_Mode: Fancoil on heating mode F0N2_FCM1.ST_VENT_Mode : Fancoil on fan mode F0N2_FCM1_C5.PV: Inlet water flow F0N2_FCM1_ST1.PV: Inlet water temperature F0N2_FCM1_ST2.PV: Outlet water temperature F0N2_FCM1_W5.kWh: Cumulative thermal supply F0N2_FCM1_W5.kWh_AC: Cumulative heat F0N2_FCM1_W5.kWh_AF: Cumulative cold F0N2_FCM1_W5.W: Thermal power FANCOIL 2          F0N2_FCM2.Enable: Fancoil2 enabled F0N2_FCM2.PV: Fancoil2 thermostat reading F0N2_FCM2.SP: Fancoil2 thermostat setpoint F0N2_FCM2.ST_COOL_Mode: Fancoil on cooling mode F0N2_FCM2.ST_HOT_Mode: Fancoil on heating mode F0N2_FCM2.ST_VENT_Mode : Fancoil on fan mode F0N2_FCM2_C6.PV: Inlet water flow F0N2_FCM2_ST1.PV: Inlet water temperature F0N2_FCM2_ST2.PV: Outlet water temperature F0N2_FCM2_W6.kWh: Cumulative thermal supply F0N2_FCM2_W6.kWh_AC: Cumulative heat F0N2_FCM2_W6.kWh_AF: Cumulative cold F0N2_FCM2_W6.W: Thermal power CHILLER 1            HVAC_BP301.OUT: Impulsion pump to distribution order HVAC_CP301.PV: Outlet cold water flow HVAC_ENF1_CVM.Hz: Frequency HVAC_ENF1_CVM.I_III: Average Intensity HVAC_ENF1_CVM.IR: Intensity phase R HVAC_ENF1_CVM.IS: Intensity phase S HVAC_ENF1_CVM.IT: Intensity phase T HVAC_ENF1_CVM.kVArh_in: Reactive Energy (R+) HVAC_ENF1_CVM.kVArh_out: Reactive Energy (R-) HVAC_ENF1_CVM.kWh_in: Active Energy A+) HVAC_ENF1_CVM.kWh_out: Active Energy (A-) HVAC_ENF1_CVM.PF_III: Power factor (average) HVAC_ENF1_CVM.PF_R: Power factor phase R HVAC_ENF1_CVM.PF_S:              Power factor phase S HVAC_ENF1_CVM.PF_T: Power factor phase T HVAC_ENF1_CVM.V_III: Combined Voltage HVAC_ENF1_CVM.VA: Apparent Power HVAC_ENF1_CVM.Var: Reactive Power HVAC_ENF1_CVM.VRS: Phases R-S combined voltage HVAC_ENF1_CVM.VST: Phases S-T combined voltage HVAC_ENF1_CVM.VTR: Phases T-R combined voltage HVAC_ENF1_CVM.W: Active Power HVAC_ENF1_m.OUT: Turning on order HVAC_Enfriadora1.SP: Control setpoint HVAC_SP301.PV: Cold water outlet HVAC_SP302.PV: Cold water inlet HVAC_WP301.kWh: Cumulative thermal energy produced (cold) HVAC_WP301.W: Thermal power (cold) CHILLER 2            HVAC_BP401.OUT: Impulsion pump to distribution order HVAC_CP401.PV: Outlet cold water flow HVAC_ENF2_CVM.Hz: Frequency HVAC_ENF2_CVM.I_III: Average Intensity HVAC_ENF2_CVM.IR: Intensity phase R HVAC_ENF2_CVM.IS: Intensity phase S HVAC_ENF2_CVM.IT: Intensity phase T HVAC_ENF2_CVM.kVArh_in: Reactive Energy (R+) HVAC_ENF2_CVM.kVArh_out: Reactive Energy (R-) HVAC_ENF2_CVM.kWh_in: Active Energy A+) HVAC_ENF2_CVM.kWh_out: Active Energy (A-) HVAC_ENF2_CVM.PF_III: Power factor (average) HVAC_ENF2_CVM.PF_R: Power factor phase R HVAC_ENF2_CVM.PF_S: Power factor phase S HVAC_ENF2_CVM.PF_T: Power factor phase T HVAC_ENF2_CVM.V_III: Combined Voltage HVAC_ENF2_CVM.VA: Apparent Power HVAC_ENF2_CVM.Var: Reactive Power HVAC_ENF2_CVM.VRS: Phases R-S combined voltage HVAC_ENF2_CVM.VST: Phases S-T combined voltage HVAC_ENF2_CVM.VTR: Phases T-R combined voltage HVAC_ENF2_CVM.W: Active Power HVAC_ENF2_m.OUT: Turning on order HVAC_Enfriadora2.SP: Control setpoint HVAC_SP401.PV: Cold water outlet HVAC_SP402.PV: Cold water inlet HVAC_WP401.kWh: Cumulative thermal energy produced (cold) HVAC_WP401.W: Thermal power (cold) Chillers room temperature HVAC_STA.PV: Air temperature in the basement where chillers are located (point A) HVAC_STB.PV: Air temperature in the basement where chillers are located (point B) HVAC_STC.PV: Air temperature in the basement where chillers are located (point C) HVAC_STD.PV: Air temperature in the basement where chillers are located (point D)
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks