Skip to content

Green Ampere · Reference 001

We are documentingour first project.Including what is still open.

Green Ampere is young. We could claim references — instead we show one, in full: the starting condition, the decisions, the current status, the open points.

Project number
001
Location
Vienna, Austria
Property
Residential property, several levels, extensive grounds
Size
around 400 m²
In progressPhotovoltaicsBattery storageEV charging infrastructureSmart building

The exact address of the property is not published, out of respect for the owners' privacy.

A well-appointed existing property whose technology has grown over the years: strong individual systems with no shared layer between them. The project brings them together into one coherent system and makes it visible through Aurora OS.

Image to follow
Exterior view at blue hour, building clearly recognizable — publication only with the owners' approval

Starting point

Plenty of technology. Little connection.

The property was well equipped. Every piece of that equipment had simply been planned on its own.

Scope of work

  • Survey of all systems and interfaces
  • System architecture and control logic
  • Network and segmentation — implemented
  • Integration of photovoltaics, storage, heat pump and EV charging infrastructure
  • Sensors, security, indoor climate, pool
  • Aurora OS as the shared interface
  • Coordination of the trade partners
  • 01

    Generation, storage, heat and charging each work on their own. Surplus is fed into the grid, while other loads draw from the grid later.

  • 02

    Pool, security, shading, lighting and climate each have their own way of being operated — every one of them works, none of them knows about the others.

  • 03

    The state of the building cannot be read in full anywhere. To find out what is happening right now, you have to look in several places.

  • 04

    The network and the sensors were never laid out for trades to talk to each other continuously and securely.

Systems

What is being brought in.

Every system carries the state it is actually in. Nothing is marked “implemented” until it is.

  • Implemented

    Network & segmentation

    A solid foundation, with building services kept separate from everyday use.

  • In progress

    Sensors

    Temperature, humidity, state and presence recorded for each area.

  • In progress

    Photovoltaics

    Existing generation is brought into the shared control logic.

  • In progress

    Storage

    Charging and discharging rules follow what the house actually needs.

  • In progress

    Heat pump

    Operation is tied to generation and to who is at home.

  • In progress

    Hot water

    Heated in surplus hours wherever possible.

  • Planned

    Buffer tank

    Thermal storage for surplus energy.

  • In progress

    EV charging infrastructure

    Charging follows surplus and the planned departure time.

  • In progress

    Pool & water systems

    Temperature, circulation and water readings become visible — and can be shifted to the right hours.

  • Planned

    Shading

    Controlled by sun position, indoor temperature and presence.

  • Planned

    Lighting

    Light scenes, and switching off when nobody is there.

  • In progress

    Security

    Alarm, door and window states in a single overview.

  • Planned

    Access

    Permissions for residents, guests and trade partners.

  • In progress

    Indoor climate

    Temperature and humidity per zone, instead of one setting for the whole house.

  • In progress

    Terrarium monitoring

    Temperature and humidity monitored, with an alert when values drift.

  • In progress

    Energy management

    The order in which surplus is used is defined and active.

  • In progress

    Aurora OS

    All states brought together in one view. The scope grows as more trades come online.

Progress

The path to a system.

  1. 01

    Taking stock

    Implemented

    A complete survey: which systems are in place, which interfaces they have, and which of those can actually be used. The result was one list of systems that can be controlled — and one of systems that cannot.

  2. 02

    System architecture

    Implemented

    Defining which layer makes which decision, which channels the systems use to talk to each other, and what happens when a component fails. This phase is the foundation for everything that follows.

  3. 03

    Network and sensors

    Implemented

    Building the technical foundation: separate network segments for building services, secured communication, sensors wherever a decision needs data.

  4. 04

    Integrating the trades

    In progress

    Connected step by step: generation, storage, heat, charging, pool, climate, security. Each trade is commissioned and checked on its own before the next one follows.

  5. 05

    Control logic and automation

    In progress

    The order in which energy is used, the response to an open window, what the house does when nobody is home: rules are defined, watched and tightened.

  6. 06

    Operation and refinement

    Planned

    Ongoing evaluation over a period long enough to mean something, so the rules can be matched to how the building is actually used.

Images from the project

  • Image to follow
    Mechanical room: storage, distribution, network
  • Image to follow
    Aurora OS in operation with real data from the property

Key figures

Numbers only after measurement.

There are no reliable before/after values for this project yet. Once measurements have been taken over a meaningful period, they will appear here — with the measurement period and the method. Until then, nothing appears here.

Findings

What we learned along the way.

Documented because it makes the next plan better — not because it reads well.

  • 01

    Taking stock is the most important step, and the most underestimated. Anything that cannot be controlled does not exist as far as an intelligent building is concerned — however good the equipment is.

  • 02

    Network and sensors first. Automation on a weak foundation produces faults that nobody can trace back to a device.

  • 03

    Commission one trade at a time. Connect several at once and, when something goes wrong, you can no longer say where it came from.

  • 04

    Automation that people do not understand gets switched off. Every rule needs a reason the system can show — otherwise it does not survive everyday life.

  • 05

    An existing building is not a new build. Some perfectly sensible rule will fail because of a component bought years ago without an interface. That belongs in the planning, not in the excuses.

Open

What is still missing here.

These sections are prepared. They stay empty until there is approved material.

  • Photo documentation, before / after

    Prepared. Nothing is published until the owners have approved it, and until we have images that match the brand's visual direction.

  • System architecture as a diagram

    It exists as a planning document. A version that can be shown publicly, without the details that need protecting, is in preparation.

  • Video: automation in operation

    Planned, once the control logic has run stably over a longer period.

  • Aurora OS screens from this project

    These follow once the interface covers the full scope of the property. Until then, this website shows nothing but demo data, marked as demo data.

  • Energy figures, before / after

    Only after a measurement period long enough to support a statement. Numbers without a measurement period and a method are not metrics.

The next project — same structure.

We document every project the way we document this one: starting point, decisions, status, open items.

Designed by Green Ampere. Powered by TailorMade Solutions.