UAC #

Name of UI (header row)

Description of UI (subsequent rows)

Enter N/A if a section is not relevant to the module

General notes to developer (header row)

Expected scenarios for testing (UAC rows)

Expected outcome in Testing

GoGreen cockpit [EB1] 

E.g. New feature / New logic / update UI only

A

Cockpit 

Update UI

1. Remove “Enter consumption” from the import status

Important: We keep the current logic; When an outstanding manual entry occurs, the import status is colored in red, and the months are highlighted in the cockpit chart. 

•  Missing manual entries occur when the date is the 16^th of each month, and the previous month(s) have “Actual data not registered” and have no actual values in the cockpit.[TG2]  The cell should be highlighted until a value has been added to the historic month.
• When the month(s) are updated, the import status turns back to green, and highlighted month(s) in the chart disappear. 

AT: PASS

a PASS

b (not part of the story; verified seems appropriate in standard scenarios)

A1

[AT update 10-10-2024]

Additional clarification of existing logic which covers all future points around when data is considered “missing”

Exceptions to showing data as missing

1. If there is no data entered in previous and current year for a resource, then we accept “null” as a valid state (ie they do not report this data).
   1. We start counting from the first month of data within that timeframe and accept “null” for any months prior to that within the previous and current year timeframe.
2. There are no warnings for missing Import data (other than the warning banner and graph), only for resources that are “Manual” 
3. The logic for the Enter consumption button (primary or secondary), the red highlights on pop-up cells, the list of months in the warning message below the table and the list of resources months in the Save pop-up all need to take this into account

Backlog 13187

Defect 13311 (also SAVE; now “not a bug”)

Defect 13315

A2.0

[AT updated 23-10-2024 will be done after the main release but noted here for reference with full spec]

2nd SPRINT: IN PROGRESS

Note: some additional clarifications added in A2.0 to A2.6 sections (highlighted yellow in text) where Import and Manual entry have slightly different logic to each other. [AT 03Mar2025]

Align logic for warning banner (cockpit), graph (cockpit) and pop-up

1. Logic for identifying missing data (both import and manual) should be the same for all parts of the cockpit
   •                             i.          Note that imported resources and manual entry resources do have different strands of logic
2. Logic for handling exceptions should be the same
3. Update required to warning banner
   1. This will align the primary/secondary logic of the ‘Enter consumption’ button
4. Update required to graph to show which months have missing data
5. Update may be required to pop-up table to handle additional exception when data entry starts part way through the “previous or current year” 
   1. Ensure that alert message, red highlights, save pop-up all use the same (latest) logic
6. Update to GoGreen index so that triggers use the same logic for manual entry categories

Out of original scope; 2^nd sprint

[TESTING: Jan2025]

Testing in all other sections below

A2.0.1

Some cockpits have a principal resource, and the ‘type’ of cockpit is based on the data type for this resource

Revised clarification [AT update 25-03-2025]

For cockpits which have a single “main” resource, the criteria is based on the type and status of that resource.  This affects all areas of logic.

1. Chemicals = Green
2. Waste = Mixed municipal waste
3. Towels & Linen = Towels large
4. Food waste = Production
5. For all other cockpits (Energy, Water, Fuels, Refrigerants) each resource is looked at individually

BACKLOG 17523

Tests will be done in 

Scenario testing (big picture and changing data).xlsx

A2.0.2

Logic for cockpits where the principal resource is “Import”

Revised clarification [AT update 25-03-2025]

Where the principal resource of a cockpit (A2.0.1a-d) is import type, then the following logic applies:

1. The banner will display the import status for the principal category AND for any other imported category in the cockpit, as follows:
2. When the category filter is set to “All”, the warning banner will look only at the principal resource and therefore will only display an import status type (red or green based on correct logic)
3. When the category filter is set to a specific category, the warning banner will show the correct banner type (manual or import) based on that category.[TG3] 
   1. The banner will be the correct colour for imported resources (this is expected to be the same as the principal)
   2. There will be no banner displayed for categories that are manual entry will be green for all manual entry categories as we will not check for missing manual data in them [TG4] 
4. The ‘Enter consumption’ button will look only at the principal resource and therefore will always be a secondary button (as import is secondary regardless of the banner colour). 
   1. This is true also when the filter is set to a specific resource including manual entry resources
5. Nothing in the pop-up (edit table) is highlighted as missing data, even if there are manual entry resources with data missing
   1. This includes the cell highlights, list of months below the table and the “save” warning pop-up
6. In the graph, months will be highlighted (amber) if there is “Actual data not registered” for a full month for ANY imported resource (not just the principal resource) using the correct logic for missing import data for graphs).[TG5] [AT6] [AT7] 
   1. When the category filter is “All”, all imported resources will have highlighted months
   2. When a single resource is selected, the graph will highlight months only if that resource is the principal resource or an imported resource.
   3. Missing manual entry data is not highlighted on the graph
7. The GoGreen index is not affected by this cockpit[TG8] [AT9] 

Scenarios in Staging as a reference:

Co Kista “Towels”

Aronsberg “Food Waste”

Scenarios in TEST03:

Hotel 1432 Chemicals;

Hotel 1813 Chemicals, Food waste or Waste;

Hotel 1594 Food waste, Towels or Chemicals 

Hotel 3358 Food waste or Chemicals

A2.0.3

Logic for cockpits where the principal resource is “Manual”

Revised clarification [AT update 25-03-2025]

Where the principal resource of a cockpit (A2.0.1a-d) is manual type, then the following logic applies:

1. When the category filter is set to ‘All’, the warning banner will consider both manual (principal resource only) and imported resources (non-principal)
   1. Warning banner will look first at the principal resource and therefore will display red if missing manual entries for that resource
   2. If there is no missing manual entries for the principal resource, but there are also imported resources for that cockpit, the warning banner will look at the import status for any imported resources and will display red or green based on the correct logic.
   3. The warning banner will not consider any other manual entry resources in this cockpit
   4. The logic for prioritizing warning banners remains the same in this scenario. [A2.3]
2. When the category filter is set to a specific category, the warning banner will show for the principal category and for ANY imported categories. tThe correct banner type (manual or import) will be based on that the category type.
   1. The banner will be the correct colour for imported resources 
   2. The banner will be the correct colour for the principal resource (using missing manual entry logic)
   3. There will be no banner will be green for any other resource that are manual entry as missing data is not checked
3. When the category filter is set to ‘All’ the ‘Enter consumption’ button will look only at the principal resource and therefore will show as primary or secondary based on whether or not there is missing data in that resource only.
4. When the category filter is set to a specific category, the Enter consumption button warning banner[TG10] [AT11]  will be secondary for all resources except the principal resource
   1. the button for the principal resource will be primary or secondary based on missing manual data logic.
5. In the pop-up (edit table), only missing data in the principal resource is highlighted as missing data, even if there are other manual entry resources with data missing
   1. This includes the cell highlight, list of months below the table and the ‘save’ warning pop-up
6. The graph will highlight for the principal resource (manual) AND any imported resources as below:
   1. Months will be highlighted red if the principal resource has missing data (based on correct logic for missing manual entries). This applies when the category filter is “All” and when the principal resource is selected.
   2. When the category filter is “All[AT12] ” and there are also imported resources in this cockpit, the graph will also highlight in Amber if there is “Actual data not registered” for a full month for ANY imported resource (using the correct logic for missing import data for graph). Note that if there is manual (principal) data and import data missing on the same month the alert will show red but the tooltip lists all resources.
   3. When a single resource is selected, the graph will highlight months only if that resource is the principal resource or an imported resource.
   4. Missing manual entry data for any other resources (not the principal) is never highlighted on the graph.
7. The GoGreen index will be affected only by the principal resource

Scenarios in Staging as a reference:

Co Kista ‘Waste”

Q The Box “Towels”

Q The Box “Waste” 

Scenarios in Test03

Hotel 1432 Towels, Food waste or Waste;

Hotel 1813 Towels;

Hotel 1594 Waste

Hotel 3358     Towels or Waste [Towels has null data in principal – worth testing]

A2.1

Clarification of logic for missing import data

Missing import data general logic

1. Each import has a schedule (eg houly, daily, weekly, monthly, yearly etc)
2. There is an allowed delay after the expected schedule time
3. Import data (eg file) is only considered missing once the delay date/time has passed
   1. Need to check timezones are correctly handled within this logic
4. Missing import data (eg file) is reflected in the warning banner  and graph only (not the pop-up)
5. Warning banner turns red if file missing after delayed time (see A2.3)
6. Graph shows amber red highlight on month where there is data missing (regardless of file import status) (see A2.5)

AT PASS

See scenarios xls for tests

A2.2

Clarification of logic for missing manual data

Missing manual data general logic for cockpits following a monthly cycle (all cockpits except Refrigerants)

1. Manual data is considered missing from 16^th of a month if there is no data at all for the previous month 
   1. Need to check timezones are correctly handled within this logic
2. Missing manual data is reflected in the 
   1. warning banner (A2.3)
   2. ‘Enter consumption’ button (A2.4)
   3. Graph (A2.5)
   4. Enter consumption window (incl red cells, alert message, save pop-up details) (A2.6) 
   5. GoGreen index trigger (A2.7)
3. Only ‘Previous year’ and ‘Current year’ are checked for missing manual data [based on Today() ]
   1. If there is no data at all for a manual category in either previous or current year, this category is excluded from the warning (no data is expected)
   2. If data starts part way through the previous or current year AND there is no data in the preceding 1 year, only months after the first entry count as missing data.     Months in current/previous year prior to the first entry are excluded from the warning 
   3. Points #i and #ii apply to all cockpits except “Refrigerants”.   See d and 
   4. REFRIGERANTS cockpit has a different life cycle (annual) so needs a longer time period for checking: 
   5. Note that “Fuels” cockpit will now follow the same monthly cycle logic as all other cockpits [change to previous UAC for Fuels]  

AT PASS

See scenarios xls for tests

Backlog 16840

Examples to clarify #c.ii:

1). Today() is 04 March 2025.

Current year includes Jan 2025

Previous year includes Jan-Dec 2024

Preceding year is Jan-Dec 2023.

2. Today() is 18 March 2025.

Current year includes Jan-Feb 2025

Previous year includes Jan-Dec 2024

Preceding year is Jan-Dec 2023.

A2.2.1

Clarification of logic for missing manual data for cockpit “Refrigerants”

[CLARIFICATION AT 22.01.2025]

Missing manual data general logic for cockpits following an annual cycle (currently only Refrigerants)

1. The following logic only applies whilst a cockpit is manual entry; imported cockpits/resources follow import logic.
2. The following logic is by exception only and not a standard variant for most cockpits or resources
   1. It must be possible (and straight forward) to find and change any hard-coded logic in the cockpit in the future should they need the more standard monthly cycle.
3. Manual data is considered missing if not entered after 12 months 
   1. Examples: 

Data for Sept 2023 is considered missing from 1^st Sept 2024.  

On every day in January 2025, check month total Jan 2024; on 1^st Feb 2025 start checking month total Feb 2024

1. Need to check timezones are correctly handled within this logic

4. Missing manual data is reflected in the 
   1. warning banner (A2.3)
   2. ‘Enter consumption’ button (A2.4)
   3. Graph (A2.5)
   4. Enter consumption window (incl red cells, alert message, save pop-up details) (A2.6) 
   5. GoGreen index trigger (A2.7)
   6. Only 2 years are checked using "Last year_Today()” as a basis. From that date, ‘Previous year’ and ‘Current year’ (up to Today() minus 1 year) are checked for missing manual data 

Examples: 

In Sept 2024, Last year_Today() is in Sept 2023, so ‘current year’ is 2023 (up to and incl Sept 2023) and ‘previous year’ is all months in 2022.

In Jan 2025, Last year_Today() is in Jan 2024, so ‘current year’ is 2024, up to and incl Jan 2024) and ‘previous year’ is all months in 2023.

1. If there is no data at all for a manual category in either previous or current year, this category is excluded from the warning (no data is expected)
2. If data starts part way through the previous or current year AND there is no data in preceding 1 year, only months after the first entry count as missing data.     Months in current/previous year prior to the first entry are excluded from the warning 

AT PASS

See scenarios xls for tests

Backlog 16840

Examples to clarify #d.h:

1). Today() is 04 March 2025, so last year_today() is 04 March 2024.

Current year includes Jan-Mar 2024

Previous year includes Jan-Dec 2023

Preceding year is Jan-Dec 2022.

A2.3

Clarification of logic for warning banner

Warning banner (cockpit) logic

1. The warning banner shows the last status of data for the cockpit or cockpit category 
   1. There is no change required to the data here for imported or manual cockpits with data
   2. There is no change required for cockpits with no data; we will continue to not show a banner for these
2. The banner shows for imported and manual categories
3. Basic colour logic:
   1. If there is manual data or import file missing the banner is red
   2. If the data or file is within accepted timeframes the banner is green
4. If the cockpit category filter is set to “All”, the banner displayed will follow this order of priority to display the most important banner on top [see A2.0.2 and A2.0.3 for clarification when a cockpit has a ‘principal’ resource that affects this logic]:
   1. If there is a manual category within the cockpit with missing data (red), that banner is displayed under “All”. 

1. If there are several categories in this scenario, display the banner for the 1^st one in the category sort order.

1. If all manual categories are updated, but there is an imported category with missing file data, that banner is displayed under “All”. 

1. If there are several categories in this scenario, display the banner for the 1^st one in the category sort order.

1. If all categories are up to date (manual and import) display the import status banner for the first [AT13] category in the category sort order.   

5. If the cockpit category filter is set to a specific category the banner must refresh to show the status for that category

[TESTING: JAN 2025, AT] Pass

a PASS

a.i PASS

a.ii PASS

b pass

c pass

c.i pass

c.ii pass

d pass

d.i PASS

d.i1 (Towels & Linen) PASS

d.ii PASS

d.ii1 (Food Waste) PASS

e PASS

BUT CHECK when change cockpit to Refrigerant or Fuel for company vehicle (16288)

Tests carried out in NCH 1813, all cockpits and categories; using “All” setting and using individual categories (d)

Data added to manual entries to change red banners to green     (Heating, Water)

Data removed from manual entries to change green banners to red (above plus)

More scenarios in 

Warning scenarios based on data_Hotel 1813.xlsx

Defect 16681

A2.4

Clarification of logic for Enter consumption button

Enter consumption button (cockpit) logic

1. The Enter consumption button is a primary button if the banner displayed is red AND for a manual entry category
   1. This is true even if the category is set to All (see A2.3e.ii as the banner should be red on top)
2. The Enter consumption button is a secondary button if the banner displayed is green
3. The Enter consumption button is a secondary button if the banner displayed is red but for an imported category
4. The Enter consumption button is a secondary button if the cockpit does not have any data and so has no warning banner

PASS

A2.5

Clarification of logic for Graph

Graph alerts (cockpit) logic

1. The Graph displays a red highlight on any month that has missing data
   1. This includes months with missing imported data at daily level; months to check is based on appropriate logic and time delay (see A2.1) Also see A2.5.1 and A2.5.2 for handling missing data (not just missing file [AT 22 Jan 2025])
   2. This includes months with missing manual entries based on appropriate logic (see A2.2) 
2. If the missing data is for a manual entry resource the highlight is red (current solution)
3. If the missing entry is for an imported resource, the highlight is amber (new UAC)
   1. Amber colours to use are Orange-500 [#F0AD24] for the outline and Orange-100 [#FFF1E0] for the fill; this is the same as other sense check messages [Changed 04Mar2025 AT]
4. If the cockpit category is set to All, the same logic applies as to the warning banner:
   1. If there is any category with missing entries (imported or manual) the month is highlighted
   2. If that month has manual entries missing it is red, and the tooltip lists only the manual entry resources that are missing (see A2.5.3)
   3. If that month has ONLY imported entries missing it is amber and the tooltip lists only the imported resources that are missing (see A2.5.3)
5. If the cockpit category is set to a specific category the highlighted months/colour are specific to that category

AT: PASS

A PASS

I PASS

Ii PASS

B Pass

c. Backlog 16843

d PASS

di pass

d.ii/d.iii backlog 17650

E PASS

A2.5.1

EXTRA Clarification of logic for Graph (imported resources with red banner)

Graph alerts (cockpit) logic (Imported resources with red banner)     [AT/HP 14.01.2025] For import categories the logic for which month to display a highlight on is as follows:

1. If the warning banner has red status (import file is missing after ETA) then check for missing data in previous and current year up to end last month
2. When checking months, highlight in red amber (A2.5c) any month (meeting #a) which has “Actual data not registered” for any day in the complete month.
   1. If there is no data at all (in any month) in previous or current year then we ignore missing data, so no months are highlighted
   2.                            ii.          If data starts part way through the time period (previous/current year) apply the same logic as for manual entry to see when to start highlighting missing data (see logic A2.2) [Clarification added 04Mar2025]
   3.                           iii.          When checking for “start” date check for data type both manual and import [Clarification 12Mar2025]
3. Months earlier than previous year are not highlighted
4. Months with some days missing with “actual data not registered” are not still highlighted even if there is some data for some days
5. Months with “0” are not highlighted, only with “null” “Actual data not registered”. [Additional note: ‘actual data not registered’ where the predicted value is so low that it does not display on the graph (daily = 0) are also excluded]

AT: PASS

Defect 16371

Defect 16723

Backlog 16840

C PASS

D PASS

E PASS

A2.5.2

EXTRA Clarification of logic for Graph (imported resources with green banner)

Graph alerts (cockpit) logic (Imported resources with green banner)     [AT/HP 14.01.2025] For import categories the logic for which month to display a highlight on is as follows:

1. If the warning banner has green status (import files are all up to date), then check for missing data in previous and current year up to end month prior to last import file received
2. When checking months, highlight in red amber (A2.5c) any month (meeting #a) which has “Actual data not registered” for any day in the complete month.
   •                             i.          If there is no data at all (in any month) in previous or current year then we ignore missing data, so no months are highlighted  [AT Clarification: added during testing as should match A2.5.1 scenario]
   •                            ii.          If data starts part way through the time period (previous/current year) apply the same logic as for manual entry to see when to start highlighting missing data (see logic A2.2) [Clarification added 04Mar2025]
   •                           iii.          When checking for “start” date check for data type both manual and import [Clarification 12Mar2025]
3. Months earlier than previous year are not highlighted
4. Months after a received import file are not highlighted if there is no later file expected yet
5. Months with some days missing with “actual data not registered” are not still highlighted even if there is some data for some days
6. Months with “0” are not highlighted, only with “null” “Actual data not registered”  [Additional note: ‘actual data not registered’ where the predicted value is so low that it does not display on the graph (daily = 0) are also excluded]

AT: PASS 

Defect 16368

Backlog 16840

C PASS

D PASS

E PASS

F pASS

A2,5,3

Changes to the tooltip on the graph highlight [AT Change requirement 28-01]

The tooltip on the graph monthly-highlight should be different for imported resources and manual entry resources

1. Red highlights (manual entry) have a tooltip with the text: “Consumption manual entry missing for <list_manual_resources_missing>”
2. Amber highlights (import) have a tooltip with the text: “Import missing for <list_import_resources_missing>”
3. For a single resource there will only be one type of colour on the graph
4. When the filter is set to ‘All’ there may be different colours on the graph on different months. As per A2.5d for any single month, a red highlight takes priority over the amber highlight; the red highlight is specific only to the manual entry resources that have missing data.
5. Both tooltips should be in TAT (tool even if not on-screen)

backlog 17650

A2.6

Clarification of logic for Enter consumption pop-up

Enter consumption pop-up alerts logic

1. Validate that the Enter consumption pop-up uses the same logic as the Warning banner to determine if there are missing manual entries (see A2.2)
2. This logic applies to when cells are highlighted red
3. This logic applies to when the alert message appears under the table (with the list of months) and which months are listed
4. This logic applies to the list of categories with missing data in the Save pop-up
5. This logic may need amending to account for data that starts part way through the ‘previous/current year’ window (A2.2c.ii)
6. f.        There are no alerts within the pop-up relating to Imported categories

AT: PASS 

A PASS

B pass

C PASS

D PASS

E PASS

F pASS

A2.7

GoGreen Index

The impact of missing data for GoGreen index should align more closely with the logic for all missing manual entry data (A2.2)

1. The valid measurement for this is in “Do” and is called “Enter actual consumption data” (see screenshot) 
2. The trigger for GoGreen index is not affected by import categories so only shows for cockpits which are set as ‘manual entry’ cockpits. If a cockpit is set as ‘import’, the manual entry measurement is excluded from the index score. This follows the current logic looking to see (for some cockpits) if a specific resource in a cockpit has a mapped account and does not consider other resources in that cockpit even if they are manual entry. 
   1. Chemicals = “Green”
   2. Towels & Linen = “Towels large”
   3. Waste = “Mixed municipal waste”
   4. Food waste = “Production”
   5. The measurement is included for all other cockpits (Energy, Water) if they have any manual entry resources (It is excluded if all resources are imported)
   6. Fuels & Refrigerants cockpits are excluded from the index completely
3. Where a cockpit is determined as “manual”, the index counts the number of months with “Actual data not registered” for the required manual entry resources:
   1. For cockpits where only 1 resource is checked to see if import or manual entry, then only that same resource is checked for missing data (b.i – b.iv). 
   2. For all other cockpits (b.v) all manual entry resources are checked (but each month is counted only once)
   3. Imported resources in any cockpits are ignored
4. the measurement should use new logic to determine when to count “Actual data not registered” as “missing data”; this should take into account when to start looking for data (current year and previous year, based on when data was first received) and when to stop looking for data (previous month if after 15^th current month; previous – 1 month if before 16^th current month). use the full set of logic as defined in A2.2 and should cover all months in the Current/Previous years (using correct logic in A2.2c).  Please check[AT14] [TG15]  to ensure:
   1. It is checking more than 1 month back
   2. It is switching to most recent previous month on 16^th 
   3. The count of months should match the months highlighted RED in the graph for relevant resources (or cockpits)
5. If there are manual entries missing, the statement under the heading “How are you doing?” should follow the current [AT16] logic:“........”[AT17] [TG18]  This is probably:
   1. If 0 months with outstanding entries: “You have no outstanding manual entries”
   2. If 1-3 months with outstanding entries: “You have outstanding manual entries in <mmm yyyy>, <mmm yyyy> and <mmm yyyy>.
   3. If >3 months with outstanding entries: “You have outstanding manual entries in <yyyy> and <yyyy>.
   4. Months and years should be listed in chronological order.
6. Based on the number of months missing data, the index score is reduced, following the current logic in Production.

AT: PASS

Defect 17032

A Pass

B Pass

C Pass

D Pass

E Pass

F defect 17274

B

Cockpit

AT: Update to InVision showing text change to button

Update UI

1. The “Add Consumption” button should be placed to the right of the import status, NB: Change the name from Add consumption to “Enter consumption” [ST19] [HP20] [ST21] 

               B.1 The “Add Enter consumption” button is always visible even if the cockpit categories are all import type should ONLY be visible when the cockpit category (for example, Water, Energy, waste) is classified as a manual entry. If category has imported values, the button should be deactivated and not visible to the user.

               B.2 The Add Enter consumption button should be displayed as a primary button (Blue) when there is an outstanding manual entry [TG22] [HP23] and white color (secondary button) if no manual entries are required. Outstanding manual entries should be checked from January of the previous year until the previous month. From each month 16^th the button should turn blue as from this date the previous month should be updated.[ST24] [HP25] 

               B3. When I, as a user, click on “Add   

                      Enter consumption,” a pop-up 

                         appears with the option to make 

                      manual entries.  (It is possible to see the imported entries as well.)

Logic on when a cockpit is a manual entry and should have the "Enter consumption” button activated.

If no accounts are mapped to the cockpit category in the PMI mapping table, it is classified as a manual entry. 

Example[AT26] : In the Energy cockpit, an account is mapped to Electricity but not heating. Then, we display the “Add Enter consumption” button on the filters “All” and “Heating,” but not in Electricity, as it has an account mapped.

IMPORTANT

In the waste and food waste cockpit we measure if there is an account mapped to “Production” in food waste cockpit and “Mixed municipal waste” for waste. If these are mapped there is NO manual entry.

Chemicals and T&L we only count the cockpit as manual entry if there is no account mapped to one of the sub-categories (resource types).

Same logic applies to Chemicals here the category is “Green” chemicals and for Towels & linen it is “Towels Small”.[TG27] [HP28] 

AT: PASS

Defect 13172

(Defect 13154: not a bug; spec updated)

Important information for the developer

The headliner (title) is “Enter energy consumption”

The resource type “Energy” should display the cockpit name from which resource cockpit you selected the manual entry. Example: if I enter add consumption in the cockpit Towels & linen then we display “Enter Towels & linen consumption” 

AT: PASS

1

Enter consumption UI

1. “Enter consumption by” as tick box

• When “Month” is selected, the table displays each month in the selected year
• When “Year” is selected, the monthly cells are greyed out, and only the year column is open for entries. See 1.A[EB29] 
• Default is “Month”

The new development of the “Enter consumption” replaces the current pop-up “Add consumption”

[EB30] 

AT: PASS

a PASS

b PASSwaiting

c PASS

PASS

2

Enter consumption UI

1. Date picker “Year selection”[EB31] 

• Default: When entering the “manual entry”, the year selected should be the same year as in the cockpit date selector. 
• No memory functionality. 
• Option to select historical years only. 
• No option to select days or months.

AT: PASS

a PASS

b PASS

c PASS (Fixed clarification)

d PASS

2.1

Date picker clarification: AT 08-10-2024 

As the only option is to select “Years” the left panel from Style guide is hidden in the date picker (Note that this image does not show future years as disabled but this is still the requirement)

1. Should use the updated UI from the style guide.  This includes update to the date field, plus validating the UI of the date picker itself
   1. For this date field the navigation arrows are not included.  InVision shows correct date field style now
2. As there are restrictions on future dates, should not be possible to use navigation arrows in date picker beyond valid decade currently (2020-2029)
   1. If cockpit date is in future year, default date should be the last valid year when user opens pop-up
3. It is not necessary to be able to select years earlier than 2000; Restrict navigation in date picker (arrows and years) so that 2000 is earliest valid year and decade 2000-2009 is earliest decade. 
   1. If cockpit date is in a past year earlier than 2000 (unlikely but possible), default date should be 2000 when user opens pop-up

Backlog 13174

Note that navigation arrow restrictions in date picker should get updated when Summary P&L released; cannot test b & c at this point.

3

1. “Enter consumption in”: Should have a tick box with options conditional on the resource

• For Energy = kWh (default) and MWh (conversion from kWh to MWh /1000)
• For Water = m³ (default) and Liter (conversion from m³ to liters /1000)
• For Waste = kg (default) and Ton (Conversion from Kg to Ton /1000)
• For Food waste = kg (default) and Ton (Conversion from Kg to Ton /1000)
• For Chemicals = kg (default) and no other options 
  1. For Towels & linen = Units (default) and no other options  

AT: PASS

a-f  PASS on UI, options, default, value when change switch, export

Defect 13213

(Defect 13200)

4

 (Download/Upload) 

Important information for developer: We are using the same logic as in the data upload center using step 1,3 and 4. Follow same logic as specified in CO2 Factor spec.

https://projects.invisionapp.com/d/main#/console/22185908/470857829/preview

AT: 11-10-2024 Clarification on file name

1. Download and upload function

• When I click on the download icon, a a pop-up will be displayed (4a), and you should have the option to select “Google sheet” or “Excel sheet.”
• The content in the download template is the same as in the view selected. INCLUDING: Category type, example; Energy. Year and measurement type, kWh or MWH as an example.
• Export file name should include Property name and Cockpit name
• See further details about the export in 4.1 below (follow up work)
• When I click on the upload icon, I should be able to upload the template into the table, via the data upload center, and added values should [ST32] [HP33] [ST34] be entered NB. Cells with a lock (imported values) will not be updated with new values when importing the[TG35]  template. This also applies to current and future month(s),[TG36] [HP37]  ONLY historical month(s) should be updated with an upload template.
• If there is an error with the upload, we display a warning message as well as a message on successful import.
• Import error is only related to an import which didn´t occur.
• Further details about the import in 4.2 below

[TG38] [HP39] AT: PASS (initial release

a PASS

b defect 13200

c Backlog 13199

4.1

[AT Clarificaiton 10-10-2024 follow up work (details tbc)]

InVision updated to show this layout[AT40] [AT41] :

Energy Cockpit Preview Mode - InVision

Excel file with updates Template for export and import.xlsx

Export has 2 options to allow for same layout as table or a layout which can be imported

1. Click on export icon will give pop-up with option to select Excel or Google Sheets (default excel)
2. Additional option will be to select layout of the export file:
   1. “Data [AT42] table (as displayed)” 
   2. “List [AT43] format (required for data import)”
   3. Default will be “Data table”
3. Data table layout is the current delivered export option which shows the same data as in their view (see excel tab Horizontal)
4. List (import) layout is a new option which has the column options required for import (see excel tab Vertical):
   1. Property name
   2. Property code
   3. Cockpit category (resource)
   4. Month
   5. Year
   6. Value
   7. Unit of measure (UOM)
5. Content for the import layout will differ based on the selected view for data table “Month” or “Year”:
   1. “Month” will list a row for each month in the year per resource
   2. “Year” will be a single row per resource with “Annual” (or 0) in the Month column and the Year Total in the value 
6. Each row in the data represents the content needed for one cell in the data table (see excel for example)
7. Export icon has a tooltip which says “Export data”

Follow up work AT: PASS

Backlog 13403

Backlog 13469 (point g only)

A PASS

B PASS

C PASS

D PASS

Defect 13511

E PASS

F PASS

G PASS

4.2

[AT Clarification 09-10-2024 tbc] 

Upload function when click the import icon; this is now follow up work:

Excel examples: Template for export and import.xlsx

1. Upload icon has a tooltip which says “Import data via upload center”
2. When click the upload icon, page opens at the import files page of the upload tool for GoGreen manual entries.
   1. User can navigate to this page themselves via the menu: Data upload centre>GoGreen manual entries>Import files
3. Default landing is Step 1 (to select a file)
4. Click Next shows Step 1: all rows of file (current process)
5. Step 2 is prepopulated with:
   1. transaction type: GoGreen manual entries
   2. field mapping: standard mapping from a manual entry download (set this up based on import layout, see excel file)
   3. all mandatory fields are mapped
   4. data preview will display 1^st row of manual data (as normal but ignore import rows if first, or just first row of data?)
6. f.        Step 3 validation (see suggestions in excel file) to include: 
   1. Standard validation of property name/code as in other modules
   2. Standard validation of UOM as in other modules
   3. do not allow text (numbers only) Do we need extra logic on how to handle thousand separators or decimal points in ‘text’ as these can be different based on user config in excel
   4.                           iv.          Default “If transaction exists:” should be “Overwrite”
   5.                            v.          Import will not over-write content in resources that are Import type, even if on the spreadsheet 
   6. Import will not populate current or future month with values, even if on the spreadsheet
   7. Year data vs Month data: if -in the same Property_Resource -  there are values for both a year (Month column says “0” or “Annual”) and a month in the same year, use the Year value and ignore all month values.
   8. In “Value”, null is valid response and should be treated as “Actuals not registered”
7. Step 4 update as usual process
8. User can download a blank template from the download tab in the Upload centre.  This contains the same columns as the Export>Import layout file (4.1) and is shown in the excel file

Follow up work AT: PASS

Backlog 12743

A PASS

B PASS

b.i PASS

c PASS

d PASS

e PASS (upload centre needs an upgrade)

e.i PASS (Not a bug 13507)

e.ii PASS (but not automatic)

e.iii FIXED Google sheets (defect 13507) Excel PASS after selecting mapping

e.iv PASS after selecting mapping

f PASS 

I PASS (appropriate)

Ii PASS (ok)

Iii PASS not tested other number formats which use , for decimal

Iv PASS

V PASS

Vi FIXED defect 13512

Vii FIXED defect 13525

Viii FIXED (no defect id)

g FIXED (defect 13506 was UOM in ton/m3

defect 13525 was blank month)

h FIXED defect 13570

5

Enter consumption UI

1. Label “Update manual missing entries”[TG44] [HP45] [HP46] 
2. The label is static, meaning it will show even if there are no outstanding/missing entries 
3. Cells with outstanding entries (missing) are highlighted in red color in the table.
4. Missing manual entries occur when the date is the 16^th of each month, and the previous month(s) have “Actual data not registered” and have no actual values in the cockpit. The cell should be highlighted until a value has been added to the historical month.
   1. See clarification in A1 where no entries in current/previous year

When I have entered my values/consumption, the color of the cell turns white. 

AT: PASS

a PASS

b PASS

c PASS

Defect 13157

Backlog 13187

Need backlog to fully test b and c

OK with old logic though (15/10).

Defect 13315 (also A1)

6

1. Display source data in the table 
2. The relevant resources are displayed if the resource is activated in the hierarchy.
3. To the right of the name, we display the selected “Enter consumption in” (3). For example, if kWh are selected in “Enter consumption” (section 3), then we display (kWh) after the source category name.
4. If an account is mapped to the resource, we display a “import” icon as per UI[TG47] [HP48] , and [ST49] you, as a user, should not be able to modify the cells/values. 
5. NB. User roles “d2o” and “GoGreen Admin” should be able to click on the import icon, and all the cells should be open for modification, and the icon change to manual entry and I as a user can edit the imported figures. When I save the changes, the cell should be locked. 
6. When I click on the manual entry icon (of an import type resource), the cell should be locked and the icon change to import (same logic as in Room Live forecast legacy). 
7. Any manual changes to an import type resource should not will be overridden by the next import, if that month is included in the import. Example: Today a new import override any manual entry, in this  case, if you manual update an imported value, it should not be overridden when the cell are locked by using the import icon.[ST50] [ST51] [ST52] [EB53] [HP54] [TG55] [HP56] 

AT:  PASS

Defect 13137

Defect 13155

Defect 13156

Defect 13173

a PASS

b PASS

c PASS (not UI)*

*add tooltip see C1

d PASS

e PASS

f STAGING TEST

UI Backlog 13176

7

Enter consumption UI 

1. Display source data in the table 
2. If an account is a manual entry, we display a manual entry symbol 
3. -            When I mouse over a cell with a manual 
4. entries: I should see a tooltip with the information: Date and name of the user who made the last entry.[ST57] [HP58] [ST59] 
5. When I mouseover a cell from imported resource, I should see a tooltip with the information: Date of last update and name of user if was changed by manual entry.
6. I should be able to modify all cells that are manual entries and values entered earlier.
7. Values are displayed with thousand separators and NO decimals[ST60] [HP61] 

AT: PASS

a PASS (not UI)

b PASS

c Backlog 13203

d PASS

e PASS (defect 13217)

UI Backlog 13176

QUERY: Prob need update no dp rule esp in MWh, m3 and Ton; answer: (see C2)

8

Enter consumption UI

1. Table cells

• The current month should NOT be open for manual entries, and all future months (current month +1) should be closed and displayed in dark grey color with no option to make any entries. See example 1.A 
• CURRENT and ALL future months are not displayed with values as we only display monthly actual values. The cells on current and future months should be greyed out see 1.A as an example.  [EB62] 

AT: PASS

a PASS

b PASS

Defect 13149 

8.1

[AT: 10-10-2024 Clarification and changes to UI of data table]

Following changes to UI to match new style guide

1. Source data icon should be grey as standard
   1. When import icon is clicked to change to manual (or clicked again to change back to import) this will show as blue until the user clicks Save.
2. Comparative column (prior year) is in italics
3. Annual total year has a border after it (separating total from January)
4. Annual total year is in Medium font, not Regular
5. Check the colour of the “hover” row to ensure not too dark
6. Table should expand lengthways to include up to 10 rows of data (based on full screen).   A scrollbar should be used for more than 10 rows.   
   1. Check UI of scrollbar

Backlog 13176

Note that “italics” for prior year was on hold but delivered with Production sprint [AT 22 Jan 2025]

8.2

TBC

[AT: 10-10-2024 Clarification and changes to data fields tbc]

FUTURE RELEASE – DO NOT DO YET

Suggested changes to editable fields (need confirm if this is new standard)

1. Can tab across from one editable field to the next for quicker data entry
   1. Tab right goes to next editable field in same row or 1^st editable field in next row after reaches end current row
   2. Tab right stops in last editable field in table if no further editable fields and keeps mouse focus there
   3. Tab left tabs backwards through editable fields (reverse logic to above)
2. Up and down arrows do NOT change the number in the data field
3. Up and down arrows move user into previous / next editable field in same column
   1. Same logic as tab
4. Editable field means ones where update type (icon) is manual and month is historic (ie any enabled field)

Do not deliver or test now

9

Enter consumption UI

1. Attention >.: you have outstanding entries in <mmm 2023yyyy>
2. When a manual entry is outstanding in a previous year, and current year, we display the month and year which has an outstanding manual entry and displays the yearthis text in red color[ST63] 
3. When there is more than one year, we display all years months with an outstanding manual entry (as a comma-separated list). Mar 2023, Apr 2023 and Jan 2024. May-23, Apr-23 and Jan-24. Oldest to newest orde[TG64] [HP65] r etc.. 
   1. Date format as per Style guide <mmm yyyy>(no hyphen)
4. We only measure the current and last year
5.  Only number entries no text, and no decimals.[EB66] 

• NB: Below “you have outstanding [EB67] entries” with 2 rows in space between.
• Please enter a static text as help: “Information: Manual entries should be completed by the 15th of each month for the previous month.”

AT: PASS

Backlog 13184

a Defect 13152

b defect 13233

Backlog 13184

c PASS

d PASS

QUERY: some UOM need decimals; answer see C2

e PASS (matches InVision)

f PASS

e & f (defect 13227: not a bug “static means not variable, not ‘always there’”)

10

Enter consumption UI

[AT: Change of wording in pop-up message 10-10-2024]

Updated in InVision:

AT: 2^nd update of wording 15-10-2024; not yet in InVision

SAVE Button

You have outstanding entries. 

• When [AT68] you SAVE the “Enter consumption”, and there are missing manual entries, a pop-up occurs with the text: You have missing entries in May 2023, Sep 2023. Do you still want to continue?
• When you SAVE the ‘Enter consumption’ and there are missing manual entries, a pop-up occurs with the text:
• “You have missing manual entries in these categories:
  • o   <Category 1>
  • o   <Category 2> etc
• Do you still want to continue?”
• Standard buttons beneath the message:
  1. Primary button “Continue”
  2. o   Secondary button “Cancel”
• Logic for which categories to include in the list is same as detailed in A and A1 (manual categories which already include some data in Current_Year or Previous_Year but which have missing data in some of these months [Current_Year or Previous_Year]). 
  1. This list will show the missing categories for the year I am editing/saving[AT69] .
• When I click on button “Continue” “Not now”, the pop-up closes and entries which has been made are saved
• When clicking on button “Cancel” “Complete”, the pop-up disappears, and the Enter consumption table is visible and shows the same year I was editing first year with a missing manual entry.
• If there are no outstanding entries, we do not display “You have missing manual entries.”
• When I click on SAVE, and it is successful, the entered values are distributed into the per month(s). (Curr[TG70] [HP71] ent logic) based on guest nights (total cons.umption per month / total guest night) = X.
  1. X per guest night multiplied by the number of guests per day in the month.
• If there are no guests, we distribute equally per day in the month. 
• This applies for both month(s) and year 

AT: PASS

UI:

Backlog 13185

Backlog 13204

Defect 13311 (now “not a bug”)

Functionality incl Data allocation:

Backlog 13135

Defect 13136

Defect 13158

Defect 13171

Defect 13173

Defect 13191

Defect 13192

Defect 13193

Defect 13191

11

Enter consumption UI

Help icons (?) next to “Enter consumption.”

It should be possible to use the text authoring tool to make the text in the help icon

PASS

12

1. “Prior year” is, per default, the year selected in the “select year” (2) -1 with the option to select the last three years (limited to the last three years). 
2. The values in the column cell is the yearly consumption from the selected year and in the same format as in selected in the “Enter consumption” example: kWh

A PASS

B PASS (spot check within table)

12740 Done

13

1. In the table before the first month, “Jan”, we display the year selected in section 2 “, Select year.”
2. The sum is the sum of the months entered.
3. If “Enter consumption by” month is selected, the cell is non-editable.
4. When Year is selected, the cell is editable, and all monthly cells are greyed out.

A PASS

B Pass

C PASS

D PASS

Please enter the text below the 

14

[AT 15-10-2024: added so functionality is documented. 

Points a and b are not standard UX in NextGen pages as the Cancel button does not normally double up as a Close button and would not be enabled until changes made. This was requested by HP. They are accepted for now.]

Cancel button

1. Always enabled
2. If no changes are made this functions same as a Close button
3. No warning message is needed if no unsaved changes
4. If changes have been made, this will Cancel unsaved changes
5. Standard “unsaved changes” pop-up appears

AT: PASS

15

[AT 15-10-2024: added for clarification but this is standard UI and UX in NextGen pages]

Unsaved changes

If user changes their view or closes the consumption pop-up via any method with unsaved changes there is a standard warning pop-up message

1. “Changes view” includes selecting new date in the date picker
2. “Changes view” does not include changing the Month/Year radio buttons or the UOM radio buttons
3. “Closes the pop-up” includes following actions (when there are unsaved changes):
   1. Pressing Cancel 
   2. Pressing X to close
   3. Navigating away within the cockpit (may not be a valid option)
   4. Navigating away using the PMI main menu
   5. Closing the browser (tab or window)

4. Standard warning pop-up message for unsaved changes has options of “Cancel” and “Continue”
   1. “Cancel” closes the warning pop-up and the navigation action is cancelled 
      1. Enter consumption table stays as is with unsaved changes still showing; Save and Cancel buttons are still enabled
   2. “Continue” carries out the navigation action
      1. Unsaved changes are lost

AT: PASS

a Defect 13214   PASS

b Defect 13213   PASS

c PASS i-iv 

c.v.PASS (added to 13318)

d PASS

d.i Backlog 13318

d.ii. PASS

C0

Production sprint (small changes as well as A2)

Small changes to add into Production sprint

C1

Tooltip on category update icon

[Addition to B6 Display source data in the table #c category icon]

Please advise if technical issues / long task.

Icon (category update type) has a tooltip

1. The icon (import or manual) will display a tooltip if user hovers over it
2. Text for tooltip is:
   1. Manual entry icon: “Enter consumption data manually”
   2. Import icon: “Consumption data is imported”
   3. Both tooltips should be in text authoring (unless a technical issue with this)
3. The tooltip always displays the correct text to match the current icon for import categories eg:
   1. If user (with d2o/GoGreen Admin rights) switches from imported to manual by clicking the icon
   2. If user switches back to import by clicking the icon
   3. After Save manual changes and icon automatically changes back to import 

[TESTING: Jan2025 AT]

BACKLOG 14710 PASS

a PASS

b PASS

b.i PASS

b.ii PASS

b.iii PASS

c PASS

c.i PASS

c.ii PASS

c.iii PASS

C2

Number formats for all cells in table (Clarification and update)

[Replaces/updates B7 Display source data in the table #e no dp]

Required

Number formats in data cells

1. For default UOM (kg, kWh, liter, Unit), the values in the table are displayed with thousand separator and no decimal places
2. When UOM (“Enter consumption in...”) is changed to Ton, MWh or m3, the values in the table are displayed with thousand separator and with 2 decimal places.
   1. 2 decimal places is fixed so place values align within each column; eg 254 is displayed as 254.00; 25.4 as 25.40 
3. A user can enter data to the same number of decimal places that are displayed 
   1. For default UOM cannot enter decimal places; for Ton, MWh and m3 can enter up to 2dp.
4. The export file includes the number of decimal places based on the UOM setting.
5. These rules apply to both imported and manual entry categories (rows)
6. These rules apply in both monthly and annual columns, including Prior year column.

[TESTING: Jan 2025, AT] PASS

A PASS

B PASS

b.i PASS

c PASS

c.i PASS

d PASS

e PASS

f  PASS 15306

Testing in NCH Hotel 1813

All cockpits tested (a-c, e and f, spot checked d all export variations)

ID

Description of change

Importance

Backlog / Story

Completed date

1

Update of UX/UI editable cells in a table using tab to navigate etc (8.2)

Low

After table UI style guide confirmed

2

Tooltips on update type icon

Medium (but quick win)

Production sprint C1

3

Tooltips on export/import icons (add with export/import backlog 4.1/4,2?)

fixed

24-10-2024

4

When UOM is MWh, m3 or Ton: display with 2dp and allow entry to 2dp

Critical

Production sprint C2

5

Export should store all values as numbers (incl thousands that show separator)

Low

Style guide to decide

6

Update to export to allow import template format (incl change to pop-up) (4.1)

fixed

Backlog 13403

24-10-2024

7

Import functionality (4/4.2)

fixed

Backlog 12743

24-10-2024

8

Text below warning in should be permanent not based on warning line (tbc) (9)

Medium

‘not a bug’ 13227

9

Cockpit page should refresh automatically if data updated in pop-up (tbc)

fixed

Defect 13192

17-10-2024

10

Performance of cockpit page (table, graph)

tbc

11

Review of warning banner and graph alerts (to match pop-up logic)

High

Section A2 

Production sprint A2

12

Use of Cancel button as a Close button (to be reviewed / updated)

Low

Style guide to decide

13

Enter consumption button to be on page even without warning banner

fixed

13346

21-10-2024

14

Update logic for imported resources esp for graph alerts (when file exists but data still missing and refine logic when file is missing and null data for 2years)

Medium (if quick win)

Production sprint A2

15

Change logic for Refrigerant to run on Annual cycle (not monthly)

High

Production sprint A2