Description

Design and implement a solution for displaying dynamic tariffs on the price components page. Network operators can now indicate if they offer dynamic tariffs, including a minimum and maximum value for their network usage.

Design

See Figma Mockups

Technical Details

(from readme.sparqlbook)
A recent addition to the electricityprices cube are dynamic tariffs. Observations may include a lowest and highest rate, and also a URL where the operator makes more details available in a machine readable form.

PREFIX cube: <https://cube.link/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
BASE <https://energy.ld.admin.ch/elcom/electricityprice/>

SELECT *
WHERE {
  <observation/> cube:observation ?obs .
  ?obs 
    <dimension/lowestrate> ?lowestrate ;
    <dimension/highestrate> ?highestrate ;
    <dimension/urltr> ?urltr
} 

LIMIT 10

• The lowestrate and highestrate are indicating the price of the Network usage price component
• Network operators can specify dynamic network usage prices if they want (e.g. different tariffs based on the time of day). If they do, they can now specify the highest and lowest (normalized) price that they charge → lowestrate and highestrate
• This means that both the Network usage and the Total will be dynamic (as specified in the original design)
  • The dynamic values for the network usage we get from LINDAS
  • The dynamic values for the total we need to calculate ourselves (I think... as far as I understood based on the "fixed" network usage and the delta to the lowestrate/highestrate)
  • We still also get the 'normal' (non-dynamic) network usage, as this is the value used across the rest of the app. The dynamic values are not used for any calculations; only for the display in the price components break down
• The current implementation on REF, showing dynamic values for all price components is wrong

Data Handling Notes

• Initial State: The new fields "DynamischerTarifHoechster", "DynamischerTarifNiedrigster", "MesswesenCHF", and "MesswesenRp" are currently initialized with 0 or undefined values -> see ongoing discussion in 2369
• Data Availability: data availability can be checked here:
  • PROD: https://s.zazuko.com/UEBDua
  • INT: https://s.zazuko.com/2wFUfzP
  • INT: number of operators with values > 0: https://s.zazuko.com/3kt6fCK

Additional Context

-> see Notion

Related Jira Ticket:

PELCOMDB-2369