Skip to content

Align EmsGOPACSAsset UI panels with documented attribute groupings#37

Open
Miggets7 wants to merge 4 commits into
feature/gopacs-redispatch-docsfrom
feature/gopacs-asset-panel-grouping
Open

Align EmsGOPACSAsset UI panels with documented attribute groupings#37
Miggets7 wants to merge 4 commits into
feature/gopacs-redispatch-docsfrom
feature/gopacs-asset-panel-grouping

Conversation

@Miggets7
Copy link
Copy Markdown
Contributor

@Miggets7 Miggets7 commented May 6, 2026

Description

Reorganises the EmsGOPACSAsset panels in ems/src/main/resources/ems/config/asset-types.json so that an operator can tell at a glance which attributes belong to which flow. The current single-page layout mixes shared, UFTP-intraday, and redispatch concerns and merges Bid and Workflow attributes into one panel.

This is the EMS-extension default that EmsOptimisationSetupService.updateManagerConfig() merges into the running manager config when an operator triggers the CREATE_ENERGY_MANAGEMENT_SYSTEM flow.

What changed

  • README (ems/README.md) — renamed the Status group to Announcement and reordered the Bid rows so the operator-editable redispatchBidPrice is listed before the read-only suggestion rows.
  • Panel layout (asset-types.json) — eight info panels in the main column:
    1. notes (hideOnMobile)
    2. Configuration — contractedEAN
    3. Intraday — Flex Request — currentPower*, power{Maximum,Minimum}FlexRequest
    4. Intraday — Flex Order — powerLimit{Maximum,Minimum}ProfileFlexOrder
    5. Redispatch — Bid — redispatchBidPrice first, then suggestions
    6. Redispatch — Workflow — redispatchConfirmBid first, then redispatchBidStatus
    7. Redispatch — History — redispatchAnnouncement/BidHistory
  • Column-1 sidebarlocation, built-in history timeline, linkedUsers, plus Redispatch — Configuration (the redispatchEnabled toggle) and Redispatch — Announcement (status fields).

Miggets7 added 4 commits May 6, 2026 14:39
Renames the "Status" group to "Announcement" so it matches the
new "Redispatch — Announcement" panel title in asset-types.json,
and reorders the Bid rows so the operator-editable
redispatchBidPrice is listed before the read-only suggestion
rows, mirroring the in-UI panel order.
Splits the single "Configuration" panel so contractedEAN (shared)
and redispatchEnabled (redispatch-only) live in their own groups,
relabels the UFTP panel to reflect intraday flex traffic and splits
it into Flex Request / Flex Order, separates Redispatch Bid (price
and suggestions) from Workflow (confirm + status state machine),
and surfaces redispatchAnnouncementHistory / redispatchBidHistory
as an explicit "Redispatch — History" panel. Operator-editable
attributes are placed first within their panel.

Closes openremote/denhaag#162.
Mirrors the EmsEnergyOptimisationAsset layout: a hideOnMobile
notes panel at the top of the main column, and the standard
sidebar trio (location, history, linkedUsers) in column 1, so the
GOPACS asset page picks up free-text notes plus the platform's
location, history-timeline and access-management widgets.
@Miggets7 Miggets7 requested a review from a team May 6, 2026 13:20
@Miggets7 Miggets7 self-assigned this May 6, 2026
@MartinaeyNL
Copy link
Copy Markdown
Member

Adding this to the internal sprint board, as it's a separate PR from the one in the D***** custom project.

@MartinaeyNL MartinaeyNL requested a review from igorrutka May 27, 2026 08:17
@MartinaeyNL MartinaeyNL removed the request for review from a team May 27, 2026 08:17
@igorrutka
Copy link
Copy Markdown
Contributor

  • Change intraday to day-ahead

Suggestions:

  • Merge configuration panels into 1 panel
  • Merge bid inputs into 1 panel
  • Switch place Redispatch — History and Redispatch — Announcement panels for more logical layout (both history panels on the right)
gopacs layout changes 1 gopacs layout changes 2

@igorrutka igorrutka requested a review from pierrekil June 2, 2026 10:40
@igorrutka igorrutka removed the request for review from pierrekil June 2, 2026 10:42
@Miggets7
Copy link
Copy Markdown
Contributor Author

Miggets7 commented Jun 3, 2026

@pierrekil agreed with Igor's suggestions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants