uxdesignsteve

Cargo data | SaaS B2B


Baselining a cargo


Visualising the future of baselining cargos within Shell apps through a simple prototype

The Cargo Tracking Process


What pain points can we address to improve the flow?

Overview

Reduce the processes and time it takes a cargo tracker to gain the insights they need to send to traders.


Team

  • Design lead in Phoenix Team working across Tender, Shell’s flagship shipping app for crude oil.

User pain point

  • I want to see useful insights/data without constant application switching.

Business need

  • Streamline journeys, processes, reduce the number of clicks/interactions needed for a Cargo Tracker. Identify and present insights that will give Shell cargo trackers the edge at speed.


Cargo tracking flow


Showing pain points (in red), to investigate and improve.

Cargo reporting flow


Showing pain points (in red), to investigate and improve.

Current vs future flow


What we have now vs what I propose to improve in the flow.

Pain point 1 – Solved ✅


Columns added for Signal Ocean (SO) ingestion of ‘Data provider’ & ‘Intel source’ and ‘Provider/Intel source’ filters now available. This intel was previously only available from a 3rd party app subscription.


10 minute saving on each cargo tracked = Avg saving of 1 hour a day ✅

Pain point 2 – Solved ✅


Intelligence source history added under the Source tab and scraped email data from 'Intel source' now available from within Tender. This intel was previously only available from a 3rd party app subscription.


10 minute saving on each cargo tracked = Avg saving of 1 hour a day for cargo trackers ✅

Harmonising all app experiences


While at Shell my overarching remit was to harmonise interactions, components/journeys and common language across both flagship applications AMC & Tender. With a view for a Geneva wide roll out across the full suite of applications.

Team

  • The Design lead in Phoenix Team (Me) working across the 2 flagship apps, Tender & ACM.


User pain point

  • When I switch between Geneva applications, I would like to see consistent interactions and visual language within the user interface to utilise each application more effectively/speedily for my needed outputs. Make me think less…

Business need

  • To provide intel and data to users in clear and consistent patterns, across all apps and remove the need for external applications.

BUSINESS NEED

  • Streamline journeys, processes, interactions of number of clicks for a Cargo Tracker. Identify and present insights that will give Shell cargo trackers the edge.



TABLES


Tender Baselines - Geneva’s Cargo Tracking app


TABLES


ACM Maintenance table - Geneva's Asset Maintenance & Capacity app


TABLES


ACM Capacity table - Geneva's Asset Maintenance & Capacity app


TABLES


Asset Catalog table - Geneva's Asset Catalog app


TABLE INTERACTIONS


Adding an Event - + Create cargo


TABLE INTERACTIONS


Adding an Event - Maintenance event for Geneva's ACM app



TABLE INTERACTIONS


Adding an Event – + Capacity event for Geneva's ACM app


TABLE INTERACTIONS


Adding an Event - + New asset for Geneva's Asset Catalog app


TABLE INTERACTIONS


Editing an Event – Edit cargo for Geneva's Cargo Tracking app


TABLE INTERACTIONS


Editing an Event – Edit maintenance event for Geneva's Asset Capacity & Maintenance app


TABLE INTERACTIONS


Editing an Event – Edit Capacity event for Geneva's Asset Capacity & Maintenance app


TABLE INTERACTIONS


Editing an Event - Edit Asset for Geneva's Asset Catalog app