prisma design sprint - prisma- · pdf fileprisma reporting section design sprint 12-16 june...

Prisma reporting section

Design sprint

12-16 June 2017

Welcome

Coffee, internet, toilets, smoking

4

Namahn

Human-centred design, digital,

product-service systems

An experienced, international,

multidisciplinary team:

— 17 designers, 3 staff + expert

network

— Founded in 1987

Studio in the centre of Brussels

Design sprint5

• Human centered

• Co-creative

• Iterative and evidenced

Activities6

High-level conceptual design

Framing

Conceptual design

User insights and design challenge

Scenarios and wireflows

High level screens

WireframesPrototype

Test User feedback

Day 1

Day 2

Day 3

Day 4

Day 5

Agenda day 1

– Insights from interviews

– Design challenges

Lunch

– Future scenarios of use

7

The briefing

Prisma reporting section9

Reporting section is one of

the least used and

appreciated section of the

platform.

How can we provide an easy

and intuitive way to extract

relevant data from the

Prisma platform?

User research

Interviews11

Remote interviews with

Shippers:

• Wingas (DE)

• ENI (ITA)

• Gunvor Services (CH)

• Hera Trading (ITA)

Research questions

• General information

• Trigger

• Finding relevant data

• Extracting the data

• Using the extracted data

Quotes

“We want to buy from the cheapest”

“We need an overview of the market (offer, demand, pricing) more

than an overview of our bookings”

“I don’t know what this section is about”

“I need to export single reports for each of the network points I am

interested in”

12

Results 13

Trigger Report/analysisSearch for

relevant data

Extract the

selected data

Overall findings14

• Various triggers: end of an auction, seek for congested points, get an

overview of the market, operational purposes, optimise portfolio planning,

forecasting purposes, etc.

• Diverse frequency: daily, weekly, monthly, yearly

• Quantity: Large number of network points to report on

• Awareness: most users are unaware of this section and about what they can

do with it

• Look and feel: reporting wizard feels like a hassle to use

• Granularity of the results: the need of both aggregated and detailed data

• Performance and reactivity: not optimal

Specific pain points (1/3)

Filtering

• Filters are too limiting (time span, single network point) and they do

not match the users goals

o Cumbersome: large number of network points to filter 1-by-1

o Filtering own data is difficult (only sorting)

o Network point based and not route based

• Default filters are more annoying than helping

Entry field

• Lack of understanding: the users don’t always know what is expected

from them, feels cumbersome

15


Taxonomy

• Variations of network point names are confusing (bundled, unbubdled)

• Need to know the exact spelling of the network point

Context

• Lack of context, the user is not sure he is selecting the right network

point (e.g. Some users use ENTSOG to double check.)

• Lack of legend, the user do not understand the meaning of all the

icons

Timespan

• Limited timespan for activities: yearly overview is not possible

16


Data overview:

• Data lacks aggregation (e.g. only one network point)

• Completeness (partial view, e.g. extra fees not included)

• Harmonisation (e.g. prices/runtime)

Data reuse

• Data exported are sometimes incomplete, incorrect

• Difficult to manage, manipulate (e.g. rework xls. sheet one by one)

• Poor readability

• No warning if there are > 5000 transactions exported in the csv.

17

Most needed information

• Marketable and marketed capacity of different network

points, market areas and TSOs

• Regulated tariff

• Prices including fees and surcharge

• Congestion points

• For SM: trade ID, trade date and not accepted proposals

18

Goals 19

Exploratory

purpose

Platform

Operational

purposes

Future

forecast

• Perform market analysis

• Overview of demand (other bids)

• Overview of offer (e.g. including unaccepted

proposal for CFO)

• Optimise portfolio planning

• Overview of their own bids and contracts within Prisma

• Overview of specific market activities

• Forecast future capacity and pricing fluctuations

• Export future auctions

Inspiration

21

Dashboard

with key

performance

indicators

Quick symbols

in table for

fluctuations

22

Route-based not

point-based

Suggestions

23

Geographical overview + extra details per point

24

Overview + expandable details per network point

25

Overview per market area

(geographical)

Overview per market type

(auction, secondary)

marketed / marketable

capacity

26

Total overview

Granular data

Material flow Sanky (in/out)27

• Production vs.

consumption

• Offering vs. demand

• Market overview

• Market overview

left) > detailed view

(right)

• Trends by product

category

28

• Price alert

• Suggestions

• Indication of

sellers and

products at a

network point

29

• Bundled details

• Route

interconnections

• Show map option

30

• Indicate lowest

fare

• Day/Month/Year

view

• Product type

• Product runtime

31

• Network point

overview of all

consumptions

• Detail of the

consumption by

hovering over

• Filtering options

32

• Filtering (location,

product type,

operator, etc.)

• Overview of general

usage

• Dashboard view

33

Current scope35

Plan

Control

Analyse

Forecast

now

Future scope?36

• Must

• Should

• Could

• Don’t

Exploratory

purpose

Platform

Operational

purposes

Future

forecast

• Perform market analysis

• Overview of demand (other bids)

• Optimise portfolio planning (cheaper options)

• Overview of offer (e.g. unaccepted proposal for CFO)

• Overview of their own bids and contracts

• Overview of specific market activities

• Forecast future capacity and price

• Export future auctions

Must

Transparency (all users) + support their market analysis (shippers)

Provide to all users (anonymized):

— Past overview

• Have a detailed overview of capacity offered on the market in the past (regulatory obligation)

• Which capacity sold VS offered and pricing information

— Present/future overview

• Have detailed overview of “to be” auctioned capacity (Analytics & Operations)

• Limited cached reports for non users

Provide to the shippers:

— Detailed overview of personal bids and corresponding allocation

(Nomination, internal, controlling, billing and accounting)

— Export data in the most reusable and convenient format (csv, excel)

37

Should38

• Have a clear distinction between custom VS standard reports

• Allow filtering to get interesting/relevant data

• Limit the amount of data to export/report + technical limitations of

backend (e.g. Time of process #ppl)

• Provide notification about finished report

• Provide possibility to cancel report generation

• Have template reports (save filters)

• Not store data for too long

Could

• Show difference between what was bought and the actual flow of capacity

usage (e.g. Entsog)

• Provide a report generation progress/status(e.g indicate time, status bar,

e-mails, SurveyMonkey)

• Allow to schedule reporting (e.g. Extract this report every month)

• Allow to export unlimited data

• Allow portfolio management (also contracts outside Prisma)

• Provide an aggregated overview including all transactions types

(Demanded/available/sold capacity)

• Set standard default views( Hide "dashboard' until standard view set)

39

Don’t

• Export to non-manipulatable file format

• Provide forecast, just the relevant trend

40

Scenarios of use

Prisma reporting Design sprint Day 2

Activities45


Framing

Conceptual design


Scenarios and Wireflows

WireframesPrototype

Test User feedback

Day 1

Day 2

Day 3

Day 4

Day 5

High level screens

Agenda day 2

10:00 to 15:00 Namahn + Prisma core team

– Revise scenarios

– Define high level screens (wireflows)

15:00 -16:00 Namahn + Prisma core team + Users

– Present scenarios and high level screens (wireflows)

– Gather feedback from users (shippers)

16:00 -17:00 Namahn + Prisma core team

– Conclusions and next steps

46

Future state scenarios

Scenarios/user goals:

1. Forecast (Make money – Short term)

2. Obligation to deliver from A to B (Long term)

3. Analysis of past auctions

4. My transactions / Portfolio management

47

1. Forecast (make money )

1. Trigger

• Notice a price difference between two areas (day ahead trading)

• How can we take advantage of it?

2. Selection of market areas (capacity/product type/ period/price)

3. List of available connection points matching the search

4. Check available capacity now : sort by cheapest or check recent

future data (capacity & pricing)

5. Set up a comfort bid based on these data

48

2. Obligation to deliver (Long term)1. Trigger

• Obligation to deliver (Long term trading)

2. Selection of market areas

3. Capacity: gap between obligation and already secured capacity

4. Additional filters: product type/period/price

5. List of available connection points matching the search

6. Check available capacity: sort by cheapest

7. Check past data for each resulted interconnection point (capacity marketable and

marketed)

8. Set up a comfort bid based on these data

49

3. Analysis of past auctions

1. Trigger

• What happened last year in the yearly auctions?

2. Filters: product type/period

3. List of connection points and related auctions matching the

search

4. Check past data for each resulted interconnection point (

capacity marketable and marketed)

5. Export excel with these data for further market analysis

50

4. My transactions / My portfolio

1. Trigger

• Report on my past transactions / Analyse own portfolio

2. Filters: own transactions / period/ TSO / deal Id /

transaction time

3. Check each transaction:

• Deal ID , Price, Amount of capacity allocated and requested,

number of rounds (capacity required at each round)

• See past secondary trades

4. Export report

51

High level wireflows52

Questions for shippers (1)

Search

• How often do you trade across multiple market areas?

• Do they need to search by market areas or by network points?

• What to mean by ‘you need to export network point by network point?’

• If you have an unbundled capacity available. How would you search for

the other unbundled point?

• At what level would you like to select the product type?

• (Product type meaning the runtime of the product)

53


Frequency

• Do you need auction results, transaction data, etc.,regularly?

o Specify time frame

o Specific frequency

Timespan

• Do you search data for last few days, monthly, yearly?

o If yearly is needed, do they need a trend overview on several years?

o Up to one year or year to year for an overview of the trends?

• For within day, would you need information from 2 years ago?

54


Data

• What is the information they need at first glance?

• On what level do you need data to be already there?

• What kind of data do you need to do your forecast?

• How do you use/axtract data to make your market analysis? (to

you rely on several platforms?

• To what extent would you like this data to be aggregated?

• Is the data available now sufficient enough for your to make

your own market analysis?

• (Limited dataset for trends/forecasts?)

55

Question for shippers (4)

Result/View

• Do you want an overview of all the availabilities between two

market areas or several network points?

o Are fasted routes, cheapest route, etc. needed?

• Is it interesting to have an overview of acquired capacity?

(outside prisma)

o E.g. upload your own company contracts

o E.g. portfolio management

• (M/L/E shippers) vs. Small/medium shippers ? How do you do

your marketing analysis

• Data points(export/contectors) VS source of truth(graphics/ui)?

56

Question for shippers (5)

Generated reports

• Do they need the same report several times?

• Is storing needed?

Pricing

• How do you check pricing?

• How are you sure that the price available is accurate?

• Pricing, do they need the final price of a product?

57

Shippers general feedback

• Most common use case: they mainly have two market areas

• Filter by market area: listing out all the combinations from going to market area 1

to market area 2 is very useful for them especially for market analysis/exploratory

purposes

• Time frame depends on ST or LT purposes (e.g. For Within Day, few days up to one

week is enough)

• Different approach used depending on network points you usually trade (favorites)

and network points that you do not trade yet

• Use of data: identify stress in capacity or variation of price vs. usual price

• Clear information on what is bookable and usable is requested (available vs

marketed vs used)

• Need to go on several different platforms to get all the needed information

58

Shippers feedback/requests

1. Market entry analysis > explore new routes

2. ST decisions: few days up to a week back needed

3. “focused view” limit list of points that are allowed to be used

4. Show either “slice’ on the booked capacity or the point [graph]

5. Save filters and schedule reporting > very useful

6. Generate monthly ad-hoc report is useful

7. Customize LT reports requested

8. Save filtering, criteria and results + sharing option internally

9. Customise columns in their report

59

Shippers feedback/requests

10. If one network point is ”owned” they would prioritize this route

11. Complex on Belgian and Netherlands with many routes options

12. Show bundled and unbundled points connecting market areas +

connecting “external areas’

13. Self defined warning of additional fees for TSO

14. Show secondary transactions

15. Upload their past transactions would be an added value for them

60

Conclusions and open points

• Different granularity of the graph and showed info for

LT and ST (Day ahead VS Quarterly)

• Limit past data of short term

• Market areas + selection/filtering of network points

based on favourites

• Aggregation of data between two market areas?

• Traders? Different use case?

61

Activities63


Framing

Conceptual design



WireframesPrototype

Test User feedback

Day 1

Day 2

Day 3

Day 4

Day 5

High level screens

Agenda day 3

09:00 - 15:00 Namahn + Prisma core team

– Define conceptual design of the screens (sketches)

15:00 – 17:00 Namahn

– Digitalisation of the screens

64

Conceptual design65

Digitalisation of the screens – V166

Agenda day 4

09:00 – 9:30 Namahn + Prisma core team

– Revise screens

09:30 – 10:30 Namahn + Prisma core team + Users

– Present high level screens and ideas

– Gather feedback from the users

10:30 – 15:00 Namahn + Prisma core team

– Iterate conceptual design based on feedback

– Detail design of the screens (wireframes)

– Define test protocol and tasks

- Test prototype

68

Activities69


Framing

Conceptual design



WireframesPrototype

Test User feedback

Day 1

Day 2

Day 3

Day 4

Day 5

High level screens

Interactive prototype – V270

Activities72


Framing

Conceptual design



WireframesPrototype

Test User feedback

Day 1

Day 2

Day 3

Day 4

Day 5

High level screens

Agenda day 5

10:00 – 14:30

– Remote user tests with 3 users

• User test 1: 10:30 - 11:30

• User test 2: 11:45 - 12:45

• User test 3: 13:30 - 14:30

14:30 – 15:00

– Conclusions and next steps

73

User scenarios

Scenario 1: You have to move gas from Germany to Austria in the

next month and you want to make use of next monthly auctions (this

is a regular activity). You need a better understanding of the market

to make the best decision about how to participate to this auction.

Scenario 1 (bis): You want to check out the past yearly auctions.

How would you proceed?

Scenario 2: You want to know which capacity you traded last month.

How would you do this in the Prisma platform?

Scenario 3: How would you save filters so that you can easily run the

search in the future?

Scenario 4: You want to retrieve reports exported previously. How

would you do this on the Prisma platform?

74

Remote user testing75

Feedback gathering & iteration – V376

Next steps

prisma design sprint - prisma- · pdf fileprisma reporting section design sprint 12-16 june...

Documents