Manual

User manual

A walk through the application screen by screen: where things are, what each field means, and what each button writes. If you only want to get through your first project, the quick start says the same thing on one page.

Watch it: Creating reports

3:00

All three videos: Video guides

1 · Signing in

The application lives at app.siteenergy.hu. You sign in with an e-mail address and password, which we send to the contact address on the order when the subscription is activated.

  • We do not know your password — only its cryptographic hash is stored. If you forget it we set a new one; the old one cannot be recovered.
  • Signing in opens a session. After 30 days without use it expires by itself.
  • Sign Out logs you out. Before leaving, the program flushes pending changes, so it may pause for a moment.

Language

The flag button in the header switches between four languages: Hungarian, English, German and Polish. The choice is tied to the device, not the account, so the same account can be used in different languages on different machines.

One account = one data space What you enter on one machine appears on another, because the data belongs to your account rather than to the browser. Saving is automatic, with a few seconds' delay.

2 · Locations

After signing in you land on the Locations screen. A location is one site, one property, one project — all data (consumption, systems, demands, planned developments) belongs to a location, and locations are independent of each other.

  • + Add Location — a name is enough; the address comes next.
  • Click a card to enter the location.
  • in the corner deletes the location and all its data. This cannot be undone.

With at least two locations, the grid also offers creating an energy community (see chapter 14).

3 · The location data sheet

Inside a location, a pencil () sits next to the name in the header — that opens the data sheet. This is the most important settings page: coordinates, every price and the CO₂ factor come from here.

Examination year

The first field on the sheet, and deliberately so: everything below it belongs to that one year — the prices, the uploaded measured series and the cards' calculations alike. A blue badge on the locations grid and on the location home page shows which year a project was built for.

Next to the field, “New examination year” creates a new location for the year you pick. One location covers one year, because the hourly series follows that year's calendar. You choose group by group what to copy over: owner and address, energy prices, existing systems, demands, planned developments, financial settings, report data.

What it deliberately does not copy The old year's measured series (consumption curve, temperature, solar curve, EFC result) are never copied — carried over, they would silently show the wrong year's data. The cards' earlier calculation results are cleared too: run them again on the new year's data.

Owner and address

Private person and company details live in separate blocks; the company VAT number appears on the MEKH filing cover. On the site address, the “Same as owner address” checkbox copies and locks the owner's address — including the country, which also drives tariff filtering.

Coordinates

After you enter the address the geocoder resolves the coordinates, or you can click the exact point on the map. Without coordinates there is no solar production and no weather data — this is the single most common place to get stuck.

Exchange rate, CO₂, prices

EUR→HUF rate 390 by default, editable, and the official ECB rate can be fetched. The euro is the canonical value; forint fields mirror it, so changing the rate recalculates every forint figure.
CO₂ emission factor kg CO₂ per kWh of electricity. The ? icon opens a reference table by country and year — read off the right one and type it in.
Electricity price Fixed or stock (hourly) pricing. Stock pricing also needs an hourly price table uploaded, otherwise every hour falls back to the fixed price — and you are warned about it.
Feed-in price The settlement price for energy exported to the grid. Under gross settlement a separate export price can be set.
Gas / district heat price Only needed if you have such a demand. District heat has its own CO₂ factor (0.27 kg/kWh by default).
System usage and merchant fee Fixed monthly items. They also appear in the payback calculation.

Tariff catalogue

Thirty tariffs from four countries (HU, PL, AT, DE) are selectable; the list is filtered by the location's country, and a “show all countries” checkbox lifts the filter. Hungarian tariffs carry verified prices; for non-Hungarian entries the structure (components, zones, VAT) is real while the prices are reference values worth confirming against the supplier's price sheet.

Fetching the weather

In the “Wind and Outdoor Temperature Data” section, enter the measurement year and run the fetch. A single request downloads the hourly outdoor temperature and the 10 m wind speed and writes them into the data table.

Do not skip this step. Hourly distribution of building heating and cooling demand, the COP(T) curve of heat pumps and wind turbine output all depend on outdoor temperature or wind speed. Without it those calculations stop or fall back to estimates.

4 · The module picker

A location's main screen groups the modules three ways:

  • Existing System — what is already there. The consumption curve comes first, because it is the first step of the workflow; then solar, battery, chimney, heat demand, hot water, buildings.
  • Planned Development — what you want to examine: planned solar and battery, flue-gas heat recovery, thermal storage, heat pump, electric vehicle, building-envelope upgrade, solar thermal, CHP, wind, hydrogen.
  • Analysis — KPI dashboard, energy flow calculation, reports.

The badge at the bottom of each card shows how many items exist. Dimmed, unclickable cards are either waiting on a prerequisite (“Add a demand first”) or not included in your plan — in the latter case clicking says so.

5 · Existing systems

Solar

One card per system: peak power, tilt, azimuth, system loss and maximum inverter output. The last one is a real clip: hourly production is capped at that value, and the program reports how many hours were clipped.

The ⚙ Fetch and calculate hourly data button downloads hourly production for the location's coordinates and writes it into the data table. Run it once per system.

Battery

Capacity, C-rate (charge/discharge power relative to capacity), minimum state of charge. If you have an existing battery that was already running in the measurement year, upload its state-of-charge and discharge logs in the EFC as well — the system then uses actual behaviour instead of simulation.

Installation date and depth of discharge

Both solar and battery accept an installation date. From that day on the system counts: for earlier hours production is zero and the battery does not run. The card says what it does — a date before the examination year means the whole year counts; a date after it means the system did not operate in the year under review at all.

For batteries the depth of discharge (DoD) field defaults to 90%. The model never discharges below that floor — no real BMS does either. The card also prints the usable capacity (capacity × DoD). Setting DoD to 100% restores the old, floorless behaviour.

Hourly columns refresh on the next run. After changing the date or the DoD, re-fetch the solar curve and re-run the energy flow calculation — those are what write the system_hourly_data columns.

Chimney

The data needed to size flue-gas heat recovery (flue gas volume flow, temperature). Skip it if you are not planning recovery.

6 · Energy demands

There are three demand types and all follow the same logic: you give the annual demand, and the system distributes it across the hours of the year, then writes the hourly columns into the data table.

Technological heat Annual kWh, heater type (gas, electric, wood, oil, heat pump, district heat) and efficiency. For gas/oil/wood a native-unit field also appears (m³, litre, kg), two-way linked to the kWh value.
Hot water Annual litres, hot-water temperature and mains water temperature (13 °C by default). Energy demand is derived from these.
Buildings Heating and cooling basics, heating unit type, COP at +7/+2/−7 °C for heat pumps and EER at +7/+18 °C for cooling. Efficiency is computed hour by hour as a function of outdoor temperature — never from a single annual average.

Every card has a Calculate hourly data button. That is what writes the hourly columns, and until it has run, everything built on it (EFC, heat-pump evaluation, the MEKH area breakdown) works from incomplete data.

If you change a demand run Calculate again. Planned developments that reference it show a “stale calculation” flag — a reminder to re-run those too.

7 · Consumption curve (T-curve)

This is the system's most important input. What you load is grid draw in hourly resolution — not total consumption.

Format.xlsx, .xls, .csv
ResolutionHourly or finer; finer data is summed per hour
Date columnIts header should contain date, time, stamp, datum or idő
ValueIn kWh; multiple numeric columns are added together
Decimal markComma or point; semicolon-delimited, header-less supplier exports are recognised too
The check that matters most If the system finds no date column at all, it assumes 15-minute data and merges every four rows into one hour. On an hourly file that silently quadruples consumption. So after every import, read the summary: how many raw rows became how many hourly rows. The program always maps the data onto the examination year’s 8 760-hour axis (the leap day is dropped), so the result is exactly 8 760 rows from any resolution.

After the import a floating box shows the file name and the annual total, with a monthly bar chart underneath. Loading another file overwrites the previous one.

From a file — or pasted from Excel

Every hourly series can be given in two ways: by uploading a file, or by pasting straight from Excel. For the latter, select the value column in your spreadsheet (values only, no timestamp needed), copy it, then press 📋 Paste — or click the upload box and press Ctrl+V.

When you paste, the program asks for the time step (5, 15 or 60 minutes — it guesses from the number of rows) and the unit (Wh, kWh or MWh), and builds the time axis from those. The decimal mark is detected automatically: 0.674 and 0,674 both work, and formatted values such as 1,234.5 or 1 234,5 are understood too.

What pasting cannot check Without timestamps the program cannot see whether rows are missing from the middle of your series. If they are, every value after the gap is shifted in time. The paste window therefore states how many rows there should be and warns you by name if the count differs — check the time step first when that happens. If your data has a timestamp column, feel free to select it as well: the program recognises it and uses it instead.

Where an input expects several columns — the battery energy flow does — you do not have to paste them one by one: select them all at once and the program shows which column it reads as which field. It suggests the mapping from the header, and you can override it from a dropdown.

“This is what we read” — the confirmation step

Before anything is saved — whether it came from a file or from a paste — the program shows what it read: how many hours, over which period, the annual total, the largest and smallest hour, and the first few values. The unit can be switched here too, and the figures update at once.

If the size of the annual total suggests a unit mix-up (a thousandfold difference, typical of Wh), the window flags it prominently. This is the last point where a thousandfold error can be caught at a glance — it is worth a look.

Reactive energy (kvarh) — optional

Below the T-curve box sit two separate, optional boxes: one for the inductive and one for the capacitive reactive series. The method is the same (file or paste), but the two directions are never netted — and that is not a formality: a site's net cos φ can be a perfect 1.00 while it is being penalised in both directions. Netted, the page would tell you there is nothing to do.

The unit is kvarh — reactive energy, not amperes. It cannot be derived from amperes (without voltage and phase angle it does not add up), so ask your supplier for the kvarh series. Set the penalty thresholds (tan φ) and the reactive charge on the location data sheet, in the advanced tariff section. Without a charge the report shows quantities only — it will not invent a cost estimate.

With data present the report gains its own chapter: billable excess per direction, the suggested capacitor bank size, and whether a fixed or automatic bank is needed. Sizing uses the 95th percentile hour, not the maximum: a single outlier hour would make the bank expensive and push the rest of the year into over-compensation — that is, into a capacitive penalty.

Harmonics THD cannot be computed from active and reactive energy, so the page does not claim it. With non-linear loads (drives, rectifiers) a detuned bank is required, otherwise the bank can go into resonance — leave the measurement and the design review to a specialist.

8 · Energy flow calculation (EFC)

The EFC reconstructs: from measured grid draw and modelled solar production it works out what happened hour by hour — how much went to self-consumption, how much to the grid, how the battery behaved, and what actual total consumption was.

What you can upload — and what it adds

Inverter export log Makes the solar self-consumption/feed-in split measured rather than rule-based. A dropdown selects which series the file holds (self-consumption / battery charge / feed-in) — it can be loaded three times from separate files. This adds the most accuracy.
Battery SoC and discharge log Actual behaviour of an existing battery instead of simulation.
Hourly prices For stock contracts. Without them, stock mode still uses the fixed price.
Pre-install consumption If the solar system went up during the measurement year.

Uploaded feed-in data is validated: negatives are zeroed, values above the combined inverter and battery power are clamped, and if more than 5% of hours needed fixing the entire upload is rejected (the engine then computes feed-in itself). The status line tells you which happened.

The result

After the run a green status bar appears and expands downwards into a monthly chart (grid draw, total consumption, solar, feed-in, other sources). Hovering a line shows exact values in a tooltip; clicking the legend toggles series. Below it the annual summary: self-consumption, self-sufficiency, energy cost (with a €/Ft toggle), CO₂ and confidence.

Results can be downloaded as JSON and XLSX — that requires export entitlement.

9 · Planned developments

Eleven development types can be added, each on its own card. The logic is the same everywhere: you enter the technical and cost data, then Evaluate / Calculate computes the annual saving from a full hourly simulation and puts NPV, IRR and payback next to it.

Planned solarCandidate systems; the optimizer searches their size
Planned batteryCapacity and C-rate range for the optimizer to pick from
Heat pumpLinked to an existing demand; hourly via COP(T)
Building envelope upgradeOne per building; the new demand is distributed with the original's profile
Electric vehicleResidential (one car) or corporate fleet; smart charging on solar surplus and cheap hours, optional V2G
Solar thermalAnnual yield, distributed hourly along the solar profile
Flue-gas heat recoveryFrom the chimney data; recovered heat as an hourly column
Thermal storageCharge and discharge simulated hourly; charges in cheap hours
CHPElectricity side hourly, heat and fuel economically
Wind turbineFrom the 10 m wind speed, with a power curve
HydrogenCharge–discharge arbitrage on hourly prices
Why hourly? The value of a heat pump or an electric car depends on when it consumes. On monthly averages every development looks better than it is. So each one is evaluated on its own hourly profile, together with existing solar and battery behaviour.

10 · Optimizer

It starts from the dark banner at the bottom of the planned-development page (“Goal Selection & Optimization”). Five goals are available:

  1. Black-out backup — what battery carries you through an outage. The size comes from your measured consumption curve: the program scans every window of that length in the year and sizes for the worst. It gives a distribution (P100 / P99 / P95 / median) rather than a single number, and names the binding constraint: if the required C-rate is above 1, more capacity will not help — you need a higher-C product.
  2. Peak shaving — reducing the demand charge. The output is the recommended contracted capacity itself: the lowest peak still sustainable, plus a safety margin. The page also charts the year hour by hour before and after, and the 24 hours of the peak day, so you can see when and by how much the battery steps in.
  3. Income / NPV — maximum net present value, with discount rate, lifetime and degradation.
  4. Self-sufficiency cost optimum — a coloured matrix: rows are battery kWh, columns solar kW, each cell the lowest total annual cost. The optimum cell is outlined.
  5. Basket — tries every combination of the enabled developments and finds the best package. A capital budget can be set.

For goals 1–4 a checklist on the left selects which developments to include. ⚡ badged items couple hourly (they reshape the consumption curve); € badged ones only economically. If an hourly column is missing for an item, the program names the Calculate you need to run.

The basket goal also accepts two constraints on the development list: a mutually exclusive group (“at most one of these”) and a prerequisite (“this one only if that one is in too”). Items tied to the same heat demand get a suggested group automatically; a manual value always wins. Several capital budgets can be set at once (base / extended / extra) — one run answers all three.

After a run, 📄 Report opens a two-page optimization report with the inputs and the detailed result.

“Not worth it” is also a result If every cell of the matrix is more expensive than the starting point, the program says so instead of calling the least bad cell an optimum.

11 · KPI dashboard

The location's current state on one screen: consumption, self-consumption, specific yield, battery throughput, cost, CO₂, self-sufficiency. Denominators for the specific indicators (floor area, headcount, revenue) are set here or on the ISO 50001 panel — the report uses the same ones.

12 · Reports

The printable system report consists of the following chapters, each appearing only when there is data for it:

  • Cover and executive summary
  • Economics, sensitivity analysis (tornado chart)
  • Robustness (P50 / P90)
  • Inventory of planned technologies
  • ISO 50001 EnPI — energy baseline, indicators, significant energy uses, SMART target
  • CO₂ balance
  • ESG — Scope 1 and Scope 2 (location- or market-based), avoided emissions, intensity
  • Reactive energy and power-factor correction — if a kvarh series has been uploaded (see chapter 7)
  • Subsidies and net capital cost
  • The best development package (if an optimization has run)

The header offers ⚙ Details (metadata), 💶 Subsidies, 📊 ISO 50001, 🌍 ESG settings bars and a €⇄Ft toggle. Output: print/PDF and a standalone HTML file.

About the HTML export fonts are referenced by relative path. If you move the file to another folder the typography falls back to system fonts — the content stays intact. When appearance matters, print to PDF from the live page.

Chapter picker, development settings, planned state

The 📄 Report button first opens the chapter picker: you tick what goes into the document. A chapter without data is shown disabled and the app names the reason — it is never silently dropped. Your selection is remembered.

Two blocks at the top of the picker decide what the report is about:

  • Development settings — the green Save the development setting button under an optimisation result names one modernisation solution. The report writes a full, separate analysis of every ticked setting and compares each with the existing system. You can also build a custom setting by hand in the 📁 Manage settings dialog (rename, copy and delete live there too).
  • Planned state — with no setting ticked, the report analyses this single planned state: the optimiser's winning package, the items you marked, every calculated development, or your own custom pick.

The document is therefore split into three sections — A) Existing state (chapters driven by the measured hourly data), B) Planned (modernised) state (one analysis per setting) and C) Comparison — and the table of contents prints the section titles too.

The analysis is recomputed, the charts are frozen. The planned state's energy balance, economics and emissions are rebuilt from today's data for every setting; the optimiser's own charts show the moment you saved them. If the two have drifted apart, the page says so.

Validating expert

The Credentials page, opened from the locations header, is where you register the energy experts who sign off the reports: name, chamber specialty and registration number (several of each, via the “+” button), a portrait, and a stamp or signature image. The catalogue knows the designations of four countries (HU, DE, AT, PL), and every country also has a free-text “Other” option — designations get renamed, and a closed list would eventually block you.

You pick the validator for a given report in the chapter selector. The name goes on the cover as a single line, and a separate validation page closes the document: every specialty with its registry, every registration number, the stamp image, plus a place and date for the signature.

An inserted stamp is a facsimile A stamp or signature inserted as an image is not an electronic signature. Authentication is completed when the expert signs the finished document electronically — which does not happen inside this program.

Findings and photos

The 📷 Findings button in the report toolbar lets you extend the document with free text and captioned site photos. This too is data, not a hand-edited document: the report can be regenerated at any time and your additions survive.

Word export and project comparison

Besides printing and the HTML export, a Word file is available. Charts are rasterised into images for it, because Word does not render SVG — without that step the diagrams would silently vanish from the document.

The ⇄ Compare button puts two projects side by side in one report. The program detects whether you are comparing two years of the same site (time series) or two different sites (benchmark), and orders the content accordingly. For a time-series comparison it also applies weather normalisation based on degree days, separating a genuine improvement from a milder winter. If the fit is poor, normalisation is skipped and the page names the reason — it will not hand you a silent number.

Cover colour

The ⚙ Details bar offers ten cover colours (forest green, midnight blue, petrol, graphite, indigo, plum, terracotta, amber, steel blue, olive). Clicking one saves immediately and redraws the cover. The comparison report's cover takes the same colour — the two usually reach the client together.

Printing to A4

The report is sized for A4: 210×297 mm with a 15 mm top and 16 mm side/bottom margin. The on-screen preview uses exactly the same type area, so what you see is what lands on paper.

  • Every chapter starts on its own page — no page carries the tail end of the previous chapter.
  • Anything longer than one page gets a continuation page: its own header, the same chapter number and a "(continued)" marker — so every printed page is a complete, headed page.
  • Charts, stat tiles, table rows and callout boxes are never split; the header of a multi-page table repeats on each page.
  • Every page carries a page number. The cover is deliberately full-bleed and unnumbered — its background reaches the paper edge while its labels stay inside the margin.
  • Long names (company, site, card) wrap even without spaces: they neither overflow the page nor get truncated.
Print settings. The app takes care of printing background colours — you do not need to switch on "Background graphics". Do switch off the browser's own headers and footers in the print dialog, otherwise the date and URL are printed over the report's own page number.

13 · MEKH filing

The Hungarian energy-expert annual report (Government Decree 122/2015, § 7/A) is produced as a separate, Hungarian-language report. The 🇭🇺 MEKH button opens the editor bar for the filing's own fields: reporting period, POD identifier, inverter details, expert name and registry number, list of measures, audit findings, sub-metering, area breakdown.

Its chapters: cover, table of contents, company profile, annual energy balance (with previous year and change), organisational/technological breakdown, specific indicators, energy-saving measures, audit, sub-metering, charts, appendices (monthly breakdown, methodology, HMKE data sheet).

The public / internal switch hides internal appendices, and the table of contents and page numbering follow automatically.

The filing is computed from your own data; where data is missing it prints “— kitöltendő —” (to be filled in) rather than an estimate.

14 · Energy community

Two or more locations can be linked at hourly resolution. Each hour the system matches feed-in from one location against grid draw at another, and shares only when the match is better for both parties than the grid — so the community never makes anyone worse off.

Settlement is parametric: grid-fee discount (with four presets), net grid fee, optional internal price, setup and operating cost. The result: shared kWh, community and net benefit, CO₂, a per-member breakdown and monthly charts.

The grid fee defaults to the median of the members' own grid fees, and the field states where the number comes from. The reason is methodological: a shared kWh takes the place of an imported kWh, so the fee in question is the member's own — not a separate community-level figure. Median rather than mean: one outlier or mistyped member should not shift the base. The fee can be overridden at any time, and one click returns you to the median; if a manual value differs materially, the page warns.

A location can belong to one community at a time. The module is part of the Complex plan.

Hourly resolution — shared energy is an upper estimate These figures are computed at hourly resolution, consistent with the rest of the app. Statutory settlement, however, is quarter-hourly, so mismatches within an hour are invisible here and the shared energy shown tends to be higher than the real figure. The page states this as a permanent note under the KPI row.

15 · Your data and saving

  • Automatic saving. Every change is saved to your account with a few seconds' delay. If the network drops, pending changes are held in the browser and replayed at the next sign-in.
  • Project save/load. A location's full state can be exported and restored as a file.
  • ⬇ Export JSON — the location's data for machine processing.
  • The data table. Calculations write into a shared hourly table (system_hourly_data) with a fixed column order. This table is what the reports and the optimizer read.
  • Client data is your data. For it, you (or your employer) are the controller and Tápió Építő Kft. acts as processor — the details are in the privacy notice and the annex to the Terms.

16 · Plans and limits

Entitlements travel with the subscription and apply automatically after sign-in. Anything you are not entitled to appears dimmed and, when clicked, explains why it is unavailable.

Trial Every module can be tried, but saving and export are unavailable; reports can be viewed on screen and carry a “TRIAL” watermark. The trial ends by itself and never turns into a subscription.
BasicEntry-level sizing: existing systems, demands, consumption curve, EFC, system report.
AdvancedFor consulting work: planned solar, battery, heat pump, envelope, electric vehicle, optimizer (goals 1–4).
ComplexThe full toolkit: every development type, basket optimization, MEKH filing, ESG, ISO 50001, energy community.

The exact contents can be compared on the pricing page.

17 · Troubleshooting

The system deliberately tells you when something is missing rather than quietly estimating. So the following are not errors but tasks.

“Download the outdoor temperature first”

Hourly outdoor temperature is missing. Location data sheet → measurement year → fetch the weather. Once per location.

“Enable at least one distribution”

Distributing the annual demand needs at least one distribution: monthly, weekly or daily. Monthly is on by default; switch it back on if you turned it off.

“T-Curve data not found”

No consumption curve is loaded for this location, or the import was not saved. Load it again and wait for the confirmation with the row count.

“solar split is MODELED (no export data)”

There is no inverter export log, so the solar self-consumption/feed-in split is rule-based. The result is usable, but self-consumption is typically overestimated.

“stock pricing selected but no hourly prices linked”

Stock pricing is set but no hourly price table is present. Either upload hourly prices or switch the location to fixed pricing.

The area breakdown differs from the annual balance (MEKH)

The area breakdown is computed from the card settings, the annual balance from the hourly columns. A difference above 2% means “Calculate hourly data” has not run on one of the demands.

A development card shows a “stale calculation” flag

The demand or building it links to has changed since. Re-run the development's evaluation so the saving is computed from fresh data.

A result does not show up on my other machine

Saving runs with a few seconds' delay. If you closed the browser right after a change, wait a moment and refresh. The language setting is deliberately tied to the device and never syncs.

Did not find what you were looking for? Write to info@siteenergy.hu — we extend the manual based on real questions.