Feature: Plug in some data into the mock "Live Plant Status board" dashboard

[daconjurer]

Currently the Live Plant Status board dashboard shows fake seed data. The idea is to implement a first draft of the data ingestion flow, load data into the database and serve it to the dashboard.

This ticket will most likely branch into more concrete ones but it can be used as a pin for the high-level feature.

Tasks to implement this:

Fetch data from the database

• Fetch the data from the database and present it in the "plant status" view #15
• Add calculations for plant status resolution #17
• Refactor database reading to provide filtering/batching (and ideally injectable into the view) #18

Fetch plant metadata from the BMRS API

• Write BMRS API client (this will probably be split into smaller subtasks that can be tackled in the background) #19
• Plug the BMRS API client into theBMRSDataService service #20

Enable filtering on the UI

• Update the state resolution logic to use the appropriate data from the Plant table #21
• Plug in request filtering query parameters into the database reading #22

[daconjurer]

Current State: The view (viz/views_plant_status.py) and template (templates/plant_status_board.html) for the "bingo board" are built but use a hardcoded list of Python dictionaries for data.

The BMRSDataService in etl/services.py already fetches and stores the MEL (Maximum Export Limit) and FPN (Final Physical Notification) data into the TimeSeriesData model. By querying this model we can start populating the main generation figures for each plant.

The current ETL does not yet fetch balancing mechanism data (for "Balancing" status) or Bid-Offer Acceptances (for "Accepted Bid" status). The next step after integrating existing data will be to expand the BMRSDataService to fetch from the BOALF dataset mentioned in docs/data-sources.md