Preferences, Tariffs & Theming

Where these settings live

Click the account avatar at the foot of the left navigation rail, just below Catalogue (your initials, or ? while you are signed out), to open the account page, /account. Signed in, your preferences are its last section, Preferences, at /account/preferences; signed out, they follow the sign-in card (Your preferences, on the account page). The old /settings address opens the Preferences section, so a bookmark to it still works.

Most controls write their value the instant you change them and take effect live; there is no Save for your preferences. The exceptions are called out where they occur.

Your preferences, on the account page

Signed in, your preferences are the account page's last section (Your Account, Team & Cloud Runs), a band titled Preferences; signed out, they are the SETTINGS band, under the sign-in card. Either way the band is a title with a hairline rule, under which its three cards pack into one, two or three columns depending on how wide your window is:

• COLORS — the theme, the button, background and card colours, and Reset (Appearance: the application theme).

• LANGUAGE — the interface language and the currency symbol.

• DATA & MAINTENANCE — the preferences export/import pair.

They are settings like the rest of this chapter: global, kept in this browser and, while you are signed in, roamed through your account (What each setting is stored in, and what follows you). So they need no session — they are on the account page whether you are signed in or not — except on a deployment that asks you to sign in before anything else: there the sign-in page shows the sign-in card alone, and your preferences appear once you are signed in.

What each setting is stored in, and what follows you

This is worth answering before you start tuning anything: if you reload the page, open the app in another browser, or sit down at another machine, which of these settings come with you?

• This browser, always. Every setting is written into your browser's local storage as you change it. It survives a reload, a closed tab and a restarted machine — but it is tied to this browser profile on this computer. Another browser or a private window starts from the defaults until you sign in there.

• Your account, always. While you are signed in, the page roams your settings through your pvSpline account (Your Account, Team & Cloud Runs): they are pulled and merged when you sign in, pushed a moment after each edit, and re-checked periodically and whenever you come back to the tab. There is nothing to switch on — every browser you sign in from picks up the same settings. Someone else signing in on the same browser gets their own account's settings: one account's settings never travel into another's.

Appearance: the application theme

The COLORS card of the account page's preferences band chooses how the application itself looks.

Theme

Theme is a dropdown with four entries:

Colour overrides

Three colour wells sit under the theme picker. Each is a browser colour input: click the swatch to open your system colour picker.

• Button color — the accent used for primary buttons, active states, progress and highlights. It overrides the accent of whichever theme is selected; the application derives the hover and pressed shades from it automatically. Reset, at the foot of the card, drops the override and goes back to the theme's own accent (see below).

• Background — the page background. Default #222831.

• Cards — the surface colour of cards and panels. Default #393e46.

Reset

The Reset button at the foot of the COLORS card restores every colour on it: Button color goes back to the theme's own accent, and Background and Cards to their defaults. Your Theme is kept. The change is silent; the controls simply move to their default values in front of you.

Language and currency

The LANGUAGE card, beside COLORS on the account page, holds two dropdowns.

Language offers System — follow your browser's language — plus Français and English, the two languages the application ships. The change is applied immediately: the interface re-renders in the new language without a reload.

The language also decides how numbers are written wherever the page writes them: in English with a decimal point and a comma between thousands (14.52 MWh, 12,345.6), in French with a decimal comma and a narrow space between thousands (14,52 MWh, 12 345,6). It is this setting that counts, not your computer's regional format: System gives French when your browser's preferred language is French, and English for any other. What pvSpline writes for you follows it too — wording built from your results (a payback reads 9 years or 9 ans), the one-line diagram on Diagram and its exports, and the report and workbook of a cloud run, which keep the language the page had when you started the run (Reporting & Export). That run's messages on the Warnings card of Results are in the same language wherever pvSpline has them translated, and in English otherwise; so are the warnings of a batch, the problems the project check reports, and the reason the Map tab gives when it finds no tilt for a zone. The table rows of a CSV export keep a plain decimal point in every language, so a spreadsheet reads them as numbers. The language never decides the electrical code the Diagram tab sizes cables under: that is the project's own Electrical code (Electrical Design & the One-Line Diagram).

Currency sets the currency symbol used in the results. Leave it at Same as language to derive the symbol from the interface language, or pick an explicit ISO-4217 code from the list (Euro, US dollar, Pound sterling, Swiss franc, Canadian dollar, Australian dollar, Japanese yen, Chinese yuan, Indian rupee, Brazilian real, Moroccan dirham, Czech koruna, Danish krone, Hungarian forint, Israeli shekel, South Korean won, Mexican peso, Norwegian krone, New Zealand dollar, Polish złoty, Russian ruble, Swedish krona, Turkish lira and South African rand). Each entry shows the currency's name, its glyph and its code.

This is a display choice: it changes the symbol printed against money on the results page — the financial projection's strip and exports (The multi-year financial projection) — and in the project browser's summary bar. It does not convert any monetary value you have already entered.

Behaviour

What the application does on its own is not a setting: it is the same for everyone, and there is no switch to look for.

• Weather is fetched for you. The irradiation series is fetched from PVGIS without your asking: when you first place the site on the Project tab, before a run on a project that has no weather yet, and again when the site moves far enough to need fresh data. The weather fetch button on the Production tab is there to refresh it or to try again (Running a Simulation & the Production Tab).

• The 3-D view follows the map. Every polygon, module-layout, building and vegetation edit reaches the streamed 3-D view a fraction of a second after it lands in the project (The 3D Earth Site View).

• A 3-D session starts when you start it. Opening 3D view never starts one by itself — on the cloud a session is metered by the minute (The 3D Earth Site View).

• Settings follow your account. While you are signed in, they roam through your pvSpline account (What each setting is stored in, and what follows you).

• Full screen is your browser's own. Use the browser's full-screen command — F11, or Ctrl+Cmd+F on a Mac — to give the page the whole screen.

Administrator accounts find a BEHAVIOUR card in the preferences band too, holding the Map imagery dropdown (IGN (Géoplateforme) or Google); for everyone else the plan view always draws on IGN Ortho orthophotography (The Map & Site Design Tab).

The project browser's Hide Signed and Organise by date switches are not among your preferences: they sit in the browser's own header (The Project Tab).

Interpolation, time resolution and starting runs

Your preferences do not set the interpolation method or the time resolution: both are saved with each project. Set Interpolation method and Time resolution on the Production tab, in the Simulation band of the configuration cards (The Configuration card), and they apply to every run of that project, single or batch. Leaving both on Engine default stores nothing and lets the engine choose — the same 5-minute step the (recommended) annotation marks.

Nothing recomputes on its own: every run is one you start — Run the project on Results, Ctrl+Enter from anywhere in the app except while the cursor is in a text field, or the stale badge's Re-run (The stale badge: when results stop matching the project).

Data and maintenance

The DATA & MAINTENANCE card, the last of the account page's preferences band, carries the settings export/import pair.

• Export preferences downloads your whole settings document as pvspline-settings.json through the browser's normal download flow.

• Import preferences… opens a file picker for such a file and applies it value by value. A progress bar shows the read, then a line reports how many preference values were applied. If the file is not a settings document — or if it is one but contains nothing this application understands — you get an explicit error instead of a silent no-op.

Import/export is the fastest way to copy a tuned setup between machines or share a house style with colleagues, and it is the way to move settings to a browser you do not want to sign in from. Picked files above roughly 67 MB are refused before they are read.

About, credits and legal notices

The version you are running, the credits for the data pvSpline reuses and the legal documents are not among your preferences: the section-sign (§) button at the foot of the navigation rail opens them from any tab, signed in or not, on the legal notices page, /legal (Legal notices and version information).

The project's consumption-rate and grid-pricing cards

The prices a project is billed at sit on the Project tab (/project), on two cards: CONSUMPTION RATES and GRID PRICING. Unlike the catalogue editor below, they edit the working project itself. Each starts with a source selector — where its prices come from — and, under manual entry, a Granularity dropdown that shows only the fields the chosen scheme uses. Whatever it hides plays no part in the run — the run bills only what the card shows — and the rates and prices it hides are kept for when you switch back. One exception: until From an hourly CSV has a grid loaded, or Tempo (EDF) its prices filled in, the run falls back to the rates the card hides — and once you type one Tempo price, any you leave blank bills at 0. A run warns in each of these cases, naming how many Tempo prices are blank.

Above the selector, each card names the part of the bill it holds and points to the other card for the rest. CONSUMPTION RATES holds the energy part, the price of each kWh you buy from the grid; GRID PRICING holds the power part — the kVA subscription and the overshoot penalties — and the export rules, net metering and the injection cap. In Full export, which hides CONSUMPTION RATES, GRID PRICING leaves out its pointer to that card.

Consumption rates

• Rate source — where the rates come from: Manual entry, From the catalogue, From a PDF bill or From an hourly CSV. With Manual entry you choose the scheme and type every rate yourself. The catalogue and the bill fill the card from a catalogue tariff or a supplier bill and then lock what they set — the Granularity, the rates, the Summer months, the Tempo colour prices and the hourly price curve — so the card always shows the tariff a run bills; a line under the selector names it (Where the rates come from). From an hourly CSV replaces the typed rates with a price for every hour of the year, loaded from a file (The hourly price grid). A project opens on the source its rates came from; one that carries no consumption tariff at all opens on From the catalogue.

• Granularity — Flat rate, Peak / Off-peak, Peak / Off-peak × Season or Tempo (EDF); the row is absent while the source is From an hourly CSV, or while a catalogue tariff or a bill prices the project by the hour. The choice also reshapes the monthly grid on the Consumption tab (The Consumption Tab): Flat rate keeps a single value per month, as the hourly CSV does, and switching to either adds each month's off-peak figure into it, which leaves the off-peak column at 0 if you later return to a split scheme. A project that has never stored a scheme — an imported file, typically — opens on From an hourly CSV if it carries a full 8760-value price curve, on Peak / Off-peak × Season if it carries any rate or peak-hour window, and on Flat rate otherwise.

• A project that carries no consumption tariffs at all shows, under Manual entry, This project has no consumption tariffs. and an Add tariffs button that creates them.

• The rate fields, in €/kWh from 0 to 10, to four decimals: Flat rate alone; Peak hours and Off-peak hours; or, in the seasonal scheme, Winter Peak Hours, Winter Off-Peak Hours, Summer Peak Hours and Summer Off-Peak Hours. They are hidden under the hourly CSV and in the Tempo scheme, whose prices come from elsewhere.

• Summer months — in the seasonal scheme, twelve month toggles choosing which months bill at the summer rates and follow the summer schedule. April to October are summer until you change them, unless the project brings summer months of its own — an imported project file, for instance — which the toggles then show.

• In Tempo (EDF), six prices in €/kWh — Blue off-peak, Blue peak, White off-peak, White peak, Red off-peak and Red peak — plus White curtailment and Red curtailment in %: the share of those days' consumption you curtail or defer (0 = none), which reduces both the Tempo bill and the total consumed. The day colours come from the Tempo calendar (The Tempo calendar editor).

• Under From an hourly CSV the card holds the hourly grid's line (The hourly price grid); in Tempo (EDF) it ends on the Tempo calendar row and its editor (The Tempo calendar editor).

In the two peak/off-peak schemes the card ends with the peak-hour schedule: one vertical 24-hour timeline headed HP/HC hours, or two — Winter schedule and Summer schedule — in the seasonal scheme. Each band on a timeline is a peak-hours (HP) window; the rest of the day is off-peak. Drag a band's knob to retime it, or hover a printed time and type it exactly. The + button on a timeline's header adds a window — 08:00–10:00 first, then the first free two-hour gap — and × removes the last one; each season holds up to three. An empty timeline reads No time ranges in this project.

In Peak / Off-peak the single HP/HC hours timeline applies to every month, summer included, and the project keeps its summer windows as a copy of it. A separate summer schedule set under Peak / Off-peak × Season is therefore overwritten once you switch to Peak / Off-peak and then leave the tab or start a run, and does not come back if you return to the seasonal scheme: both timelines then start from the HP/HC hours windows.

Where the rates come from

The Rate source at the head of the card decides who sets the prices.

From the catalogue adds a Catalogue tariff dropdown listing the tariffs you have favourited in the catalogue (The tariff catalogue editor) that price consumption — a grid-only tariff such as a TURPE network charge is offered on the GRID PRICING card instead. Pick one and the card shows Applying the rate… while it copies every rate into the project, with the scheme they belong to. The pick also sets the GRID PRICING level from the tariff's grid model, and so what the network side bills. The dropdown's last entry, Add from the catalogue…, applies nothing: it opens the catalogue's Tariffs tab, where hearting a tariff adds it to the list.

From a PDF bill adds a PDF bill row whose Choose a PDF… reads the rates, the subscription and the off-peak windows off a supplier bill; the importer and its confirmation dialog are described in The Consumption Tab. Applied with tariffs ticked, it also sets the GRID PRICING level to Subscription when the bill itemises a subscription, or to TURPE + peak-shaving when it prints an overshoot price. Applied with Update the project's HP/HC schedule timelines (both seasons) ticked, it rebuilds the timelines from the bill: the hours outside the bill's off-peak windows become the peak-hour windows, the same in both seasons, and replace every window the timelines held. An import that leaves tariffs unticked does not make the bill the source.

Once a tariff or a bill has been applied, the fields it set are greyed out: the Granularity, the rates, the Summer months, the six Tempo colour prices and the hourly price curve. A line under the selector names their origin — Rates of the “…” tariff. or Rates read from the bill “…”., with the bill's file name — and stays with the project, so it opens on the same source next time. What a tariff does not set stays editable: the peak-hour schedule, which depends on the meter, the Tempo day calendar and the Tempo curtailment shares. To adjust a rate, switch the source back to Manual entry: the rates stay as the source set them, now editable, and the project no longer names a catalogue tariff or a bill once you leave the tab. From an hourly CSV is manual entry's twin for a price file: nothing locks, and the project names no source either.

Picking From the catalogue or From a PDF bill changes nothing by itself. Until a tariff is applied from it, the rest of the card steps out of sight — the project's own rates would otherwise show under the new source's name — and the line under the selector says what to do: No catalogue tariff applied yet: pick one and its rates fill the card. or No rates read from a bill yet: choose a PDF and its rates fill the card. Rates typed under Manual entry during the same visit are set aside when you switch; switching back shows the rates the project holds. A project with no consumption tariff opens on From the catalogue in just this state: pick a tariff, or choose Manual entry to type the rates yourself.

A level that a catalogue tariff takes from its grid model, or a bill from its subscription or overshoot price, switches the import/export reconciliation off on a project that had Net metering, just as picking that level on the GRID PRICING card does.

Two rate mistakes are flagged on the Project entry of the rail: All consumption tariffs are 0 and Off-peak tariff higher than peak (unusual).

Grid pricing

The GRID PRICING card bills the network side. Like CONSUMPTION RATES it opens on a Source: Manual entry, the rows below typed by hand, or From the catalogue, a Grid tariff dropdown of the grid-only tariffs you have favourited in the catalogue (a TURPE network charge, say) — picking one fills the rows in one go, after which they show, still editable, under Grid pricing filled from “…”. The rows below stay editable. Until then the line reads No grid tariff applied yet: pick one and it fills the grid pricing. and the rows stay out of sight. A project that holds any grid pricing opens on Manual entry; one that holds none opens on From the catalogue. The selector is a card setting, not a project one: the project records what the rows hold, not where it came from. Under manual entry, its Granularity offers None, Subscription, TURPE + peak-shaving and Net metering, and the level you pick decides both the rows the card shows and what the run bills:

• None shows no price row and bills no grid charge — the choice for an all-inclusive tariff whose energy price already carries the grid fee;

• from Subscription on: Subscribed power (kVA, whole numbers) and Subscription price (€/kVA per month), billed as 12 × the subscribed power × the price each year — at Subscription, that is all this card bills;

• TURPE + peak-shaving and Net metering add Overshoot price (€/kVA·h), Peak demand price (€/kW·month, on each month's peak draw) and Peak window (minutes; 0 keeps the default 15 minutes), and bill the overshoot penalty and the peak demand charge on top of the subscription (the demand charge even without one);

• Net metering adds Billing period (Monthly or Annual, default Annual), Offset ratio (0–1) and True-up tariff (€/kWh) for the surplus. Picking it switches the import/export reconciliation on; picking any other level switches it off, and so does any other level that From catalogue or From PDF bill sets.

Peak-shave target (kW) is not a price: it is the power the battery's Peak shaving, Time of use and Weak-grid backup strategies run at (Storage, EV & Specialized Systems). Its row shows at TURPE + peak-shaving and Net metering, and at any level while the BATTERY card's Dispatch strategy is one of those three.

In every mode the Injection cap row summarises the export limit — No cap, Uniform cap 6 kW or Custom schedule (12 capped cells), for example. Edit schedule opens a 12 × 24 grid in place, one cell per month and hour of the day, in kW; -1 means no cap. Type a value in Apply to all cells and press Apply to fill the whole grid, or press Clear all to remove every cap. The engine applies the cap per 5-minute slot and curtails the energy above it.

Once a grid-only tariff is favourited in the catalogue — one with a grid model and no consumption price, such as a TURPE network charge — the card ends with a From the catalogue row. Picking a tariff there fills the rows above from it in one step and confirms with Grid pricing filled from “…”.; the rows stay editable, and the consumption rates and their source are left as they were. That dropdown, too, ends on Add from the catalogue…, which opens the catalogue's Tariffs tab.

The tariff catalogue editor

Electricity tariffs are authored in the component catalogue: open Catalogue (/catalogue), choose the Tariffs category, and click Add part… — or select a row and click Edit. Either opens the part editor panel, a single form grouped into identity, buy side, and sell side & grid. The general catalogue mechanics — search, favourites, fingerprints, who may edit — are covered in The Component Catalogue.

Authoring tariffs needs the Manager or Admin role in your company. For other roles Add part…, Edit and Import a file… are absent, and the catalogue says Catalogue changes require the Manager or Admin role.

Granularity and which fields matter

The Granularity dropdown decides which purchase-price fields are meaningful. All the rate fields stay visible whatever you choose; only the ones belonging to the selected granularity are saved onto the record, so fill in those and leave the rest alone.

Sell side and grid charges

Feed-in tariff is the price paid to you for exported PV surplus, in cents per kWh, and Feed-in tariff indexation is its annual escalation in percent — model a long-term feed-in contract by giving it a small yearly rise.

The Grid dropdown selects how network charges are billed. Applying the tariff to a project sets the project's GRID PRICING level to match — None, Subscription or TURPE + peak-shaving — and that level decides what the project is billed (The project's consumption-rate and grid-pricing cards):

A new record whose Grid is left on its blank choice (—) carries no grid model, and applying it leaves the project's level as it is.

When a grid charge applies, Subscribed power is your contracted capacity in kVA, Price per kVA·month the monthly capacity price (Enedis publishes this per year, so divide by 12), and Overrun price the penalty per kVA·h when you exceed the subscribed power, billed for a TURPE tariff only.

Attaching a catalogue tariff to a project

A catalogue tariff reaches a project through the Rate source of the working project's tariff card (The Project Tab): set it to From the catalogue and pick the tariff in the Catalogue tariff dropdown, which lists the tariffs you have marked as favourites in the catalogue that price consumption. Picking one copies every rate into the project in a single step and locks them on the card until its source is switched back to Manual entry (Where the rates come from). If it offers no tariff, nothing has been hearted yet — its last entry, Add from the catalogue…, takes you straight to the catalogue's Tariffs tab so you can do it. A grid-only tariff — a TURPE network charge, say — is applied from the GRID PRICING card's own Source instead.

Applying a tariff writes more than the buy rates. Its Grid model becomes the project's GRID PRICING level (Net metering for an imported tariff that enables it), so an all-inclusive tariff also stops a subscription the project was billing; a tariff with no grid model leaves the level alone. On a project that had Net metering, a tariff that sets any other level also switches the import/export reconciliation off, as picking that level on the card does (The project's consumption-rate and grid-pricing cards). Its Feed-in tariff becomes the project's Feed-in tariff on the SIMULATION card and its Feed-in tariff indexation the Feed-in tariff inflation on the FINANCIAL card. The feed-in tariff is paid only in the Full export and Self-consumption + export system types (The Project Tab), so on a Self-consumption + storage project the copied rate earns nothing.

The hourly price grid

A tariff that does not fit any typed scheme — market-indexed pricing, a bespoke commercial contract, an EJP or professional bill — is billed from a file: a price for every hour of the year. On the working project's tariff card, set the Rate source to From an hourly CSV. The typed-rate fields and the Granularity leave the card, and one line takes their place.

• A paragraph first states the format the file must have: one price (€/kWh) per line in its first column, 8760 values, an optional header row that is skipped, with commas, semicolons or tabs as separators — then the clock its rows follow and how 29 February is read, the rules below.

• Hourly CSV — the Choose a CSV… button. Choosing the file is the import: it is read, checked and applied to the working project in one step, with a progress bar while the engine has it. There is no parse step and no confirmation; Ctrl+Z takes the grid back if it was the wrong file. A file the engine cannot read is refused with the format it expected, and the project is left as it was.

• Clear — deletes the grid from the project.

The engine reads the file by these rules:

• Columns and decimals. With a semicolon or a tab between the columns, a comma inside a column is a decimal comma (0,1534;…). A file of a single column whose every line is one number written with a decimal comma (0,1534) is read the same way. Otherwise a comma separates the columns and the decimals take a point (0.1534). Only the first column is read.

• The clock. Row 1 is 1 January, 00:00–01:00, on the site's local clock, summer time included. Every day has 24 rows, one per hour of the clock, also on the two days the clocks change: the hour skipped in spring keeps its row, and the hour repeated in autumn is priced twice at its one row.

• 29 February. The grid has no row for it: in a leap year, that day is priced at 28 February's prices. A leap-year file of 8784 values is accepted and its 29 February dropped, so every later day keeps its own prices. Any other number of rows is refused.

• A file whose first column is not a price — a time stamp first, say — is refused rather than misread.

The line under the button states what prices the project. While no grid is loaded it is the warning No hourly grid loaded yet: choose a CSV and its 8,760 prices replace the typed rates., in the same tone as a source picked but not applied: the run then falls back to the rates the card hides, which a run's Warnings card flags. Once a grid is loaded it reads Hourly grid “…” loaded (8760 values): it replaces the four peak / off-peak rates., naming the file for the rest of the visit; a reopened project names the grid without its file.

Choosing the file first writes any change still pending on the tab's cards into the project (The Project Tab), so the grid is applied to the project as you see it. A picked file is checked for size before it is read, so an oversized file is refused immediately with both numbers named rather than after a long upload. The ceiling is about 25 MB. A tariff CSV is far below it — 8760 numbers is well under a megabyte — so in practice you meet this only with the wrong file.

A catalogue tariff or a bill can price the project by the hour too (an EJP bill, say). The card then opens on that source with the grid named on the same line, read-only like the rest of what the source set.

The Tempo calendar editor

EDF's Tempo tariff colours each of the 365 days of the year Blue, White or Red, with progressively higher prices; Red days (typically winter working days) are the most expensive. The Tempo calendar editor lets you paint that day-colour calendar by hand, with no CSV at all.

Set Granularity to Tempo (EDF) on the working project's tariff card. The card ends on the Tempo calendar row, whose state reads Typical calendar, Custom calendar or, for the rest of the visit after an import, Custom calendar (…) with the file's name. Under it, Edit the Tempo calendar unfolds the editor in place — the same fold as the injection-cap schedule on GRID PRICING — and folds it away again. The editor shows each day at the colour the simulation bills it: a stored calendar by date, and otherwise the typical calendar laid on your consumption year (below).

• Import a CSV… opens the file picker straight away; its tooltip states the format: one date, colour pair per line, the date as YYYY-MM-DD (or D/M/YYYY) and the colour as 1/2/3 or blue/white/red; days you do not list stay blue. Choosing the file applies the calendar to the project; a file the engine cannot read is refused with that same format, and the project is left as it was.

• Reset puts the typical calendar back, at once.

• Below, a 12 × 31 grid — one row per month, one square per day; short months simply have fewer squares. Click a day to cycle its colour Blue → White → Red → Blue.

• A running count under the grid shows how many Blue / White / Red days you have assigned, next to EDF's reference quotas (300 / 43 / 22).

• While the typical calendar shows, a last line names the dates it is laid on: the consumption year the simulation bills — the dates your consumption data covers, or the year a generated profile is laid out on — or, while the project holds no consumption, the year the simulation falls back on.

Every change is saved: a painted day reaches the project a moment after the click — a run of clicks lands as one change, which one Ctrl+Z takes back — and an import or a reset at once. The grid and the state line follow each change. There is nothing to save, cancel or confirm; an import or a paint made while a Tempo pick is still pending on the card writes that pick with it, so the card stays on Tempo. A paint keeps the colours the grid showed — the typical calendar on your consumption year, with your changes — and the calendar is then read by date, like an imported one.

The reference calendar is not a naive fill: it follows EDF's published rules, so Red days fall only on winter weekdays that are not public holidays, White days avoid Sundays and holidays, Sundays and summer stay Blue, and no run of non-Blue days exceeds five. That matters because the engine prices each day by its colour, so which days are Red changes both the bill and the modelled battery behaviour — not just the annual totals.

The typical calendar is built on the weekdays of one reference year, and the simulation reads it on each real date: a date takes the reference day that falls on its own weekday, at most three days away (a week further at the edge of the year or of the winter season), and the year's own public holidays stay Blue. So Red days fall Monday to Friday whatever the year, and the counts stay within a day or two of the quotas. A calendar you import or paint is read by date, as it is.

How tariffs flow into the calculation

A tariff you author here is not just bookkeeping — it feeds three parts of the simulation engine:

• Consumption billing (The Consumption Tab). The buy-side prices — flat, peak/off-peak, seasonal, Tempo or hourly-CSV — are applied to each interval of your load to compute what the electricity costs, and the subscription and overrun charges that the GRID PRICING level bills add the network component — none at None, the subscription alone at Subscription.

• Financials (Running a Simulation & the Production Tab, Reporting & Export). The feed-in tariff and its indexation value the PV surplus you export — in the Full export and Self-consumption + export system types only; a Self-consumption + storage project sells none, unless net metering credits it — while avoided purchases value the energy you self-consume; together with the billed grid charges these drive savings, payback and the long-term financial cascade.

• Battery dispatch (Storage, EV & Specialized Systems). Time-of-use structure is exactly what makes a battery worthwhile: the dispatch logic uses the peak/off-peak or Tempo price signal to decide when to charge and discharge, so the tariff you pick directly changes the modelled battery savings. Flat rate and the From an hourly CSV source give it no peak/off-peak window to steer by, so the Time of use strategy then plans like Self-consumption (default); under the hourly CSV the battery's savings are still valued at the hourly curve.

Field reference

Appearance — Colors

On the account page's preferences band, like the LANGUAGE, BEHAVIOUR and DATA & MAINTENANCE cards below.

Language

Behaviour

Data and maintenance

Consumption-rate card

Grid-pricing card

Tariff catalogue editor — identity

Tariff catalogue editor — buy side

Tariff catalogue editor — sell side and grid

Hourly price grid

Tempo calendar editor