The goal
A hotel that makes as much energy as it uses across the year.
Net zero rarely fails on hardware. It fails because generation, storage, plant and occupancy are each optimised alone — so the building buys at the wrong hour and gives away its own production at another. The missing part is coordination, and coordination is a software problem.
The platform
Every small property is bespoke. That is exactly why it needs a platform.
A ten-unit guesthouse has the same coordination problem as a three-hundred-room hotel, and none of the budget for the engineering that solves it. Pan Ciepełko carries that variability in configuration rather than in code, so an architect or an investor can get a designed, priced, deployable energy system for a small building — and the second one costs a fraction of the first.
- 01
Read
An architect or an investor uploads the plans. The drawings are read automatically, the building becomes a model, and sensors, meters and controllers are placed where the building needs them.
- 02
Design
Sources, circuits, buffer and controls laid out for this building and no other. Nothing is a template — the model is these rooms, these risers, this plant.
- 03
Configure
The control software is built for this building out of the same model — its circuits, its buffer, its rooms. Not a generic controller with the parameters filled in, but logic shaped to the plant that will actually stand there.
- 04
Simulate
Before anything is ordered, the design and its software run against real history — past hourly tariffs, past weather, the equipment specified and the very logic that will run the building. The payback figure in the offer comes from a simulation, not a spreadsheet assumption.
- 05
Hand over
Electrical and hydraulic drawings come out of the same model — schematics, cable and pipe runs, panel layouts, a bill of materials. The architect or investor hands them to the installers for review and approval, and the trades price from a document rather than a conversation.
And then it runs the building
Sources
Panels, wind, heat pumps, storage and the grid connection stop being separate installations. Meters, inverters and plant controllers from any vendor feed one model of what the building makes, holds and draws.
Forecast
Tomorrow's weather, tomorrow's hourly prices, and tomorrow's arrivals. The booking system already knows which rooms will be occupied — the plant should know it too.
Shift
Heat, cool and charge when energy is cheap or self-made; coast when it isn't. The building's own thermal mass does the storing, so the guest never feels the decision.
Account for it
Generation, consumption and cost per system and per period — the numbers for an owner's reporting, for a payback case, and for the distance still left to net zero.
Down to the circuit
A hotel is not one thermal zone. It is dozens of circuits and a stratified tank.
The software models the hydronic layout the building actually has, and acts at that level — which circuit gets flow and at what temperature, which layer of the buffer is charged, and when.
- Mixing circuits and their heating curves
- Valve and pump setpoints per circuit
- Buffer tank charge, layer by layer
- Hot water loop and recirculation timing
- Heat pump flow temperature
- Battery and inverter dispatch
That is where the room to move is. A heat pump earns its efficiency from low flow temperatures; a buffer keeps its usable capacity only while it stays stratified rather than mixed. Both are given away the moment control is applied to the building as a whole.
Who it's for
Hotel investors and architects — and the small properties they build.
Small hotels, guesthouses and apartments in Poland and Central Europe. New build or existing plant, equipment from a dozen manufacturers, often with panels or a heat pump already specified. The platform is built to work with what the project already has.
Selected projects