Baselining a cargo
Visualising the concept of baselining cargos within Shell apps
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
- Bring useful insights/data into the Tender app removing the need for constant application/context switching.
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.
Current vs future flow
What we have now vs what I propose to improve in the flow.
Cargo tracking flow
Showing pain points (in red), to investigate and improve.
Cargo reporting flow
Showing pain points (in red), to investigate and improve.
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 ✅
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
Ship to Ship (STS)
Surfacing STS info for cargo trackers and analysts
Overview
To show Ship to Ship cargo transferral in the Shell cargo tracking app.
Team
- Handover of early stage work of previous designer and working closely with the Product Owner and users to gauge ease of use and level of detail needed.
User pain point
- When I want to include STS info in my tracking of cargo, I have to switch to an external application. I would like to see all the information in one place to improve my working process.
Business need
To implement key features/data within the app, in order to increase the user base.
Mapping the data
Ship to Ship handling, across all the data providers and layers.
Event mapping
How many events could there be to display at once?
Vortexa = 0-5 & Kpler = 0-3
Questions to continue to explore
Conducting interviews and mapping in various stakeholder/user feedback.
STS output
Ship to Ship info now available with a simple hover.
15 minute saving on each cargo tracked = Avg saving of 1.5 hours a day ✅
STS output cont.
Ship to Ship info now available on the Baselines table. 15 minute saving on each cargo tracked = Avg saving of 1.5 hours a day ✅
STS output cont..
Ship to Ship info now also available from the Voyage details page. 15 minute saving on each cargo tracked = Avg saving of 1.5 hours a day ✅
Adding search to filters
Improving the experience of load and discharge location filters that have over 500+ selections from a tree list
Overview
To reduce the time and effort a user makes when finding and selecting regions, countries and ports within a location filter.
Team
- Working closely with the developer on a proof of concept and final solution at speed.
User pain point
- Why is there not a search function for a tree list of over 500 items?
Business need
Reduce the time it takes for cargo trackers to set up/change load and discharge location filters.
Ideation
Search hierarchy within the filter component.
Build designs
With If, When, Then statements for handoff to developers and testers.
Vessels in critical zones
Proof of concept
Overview
Look into the feasibility and potential of Vessels in a critical location intelligence for cargo trackers and traders.
What will it take? How long will it take? What’s the potential value?
Team
- Working closely with the Data Engineers and Data Analysts to define, scope and value the potential feature.
User needs
- Greater intelligence for cargo trackers and traders.
Business needs
More timely and informed market trades.
Bahamas workshop
Vessel off course notes to follow up on.
Vessel off course
Existing technology and logic layed out to learn and potentially leverage from.
Current business processes utilised
Analogue process used for tracking vessels that are in critical zones.
Mapping critical zones
Output defined in collaboration with our stakeholders, the cargo tracking team and data analysts.
High level concepts
Storyboarding for Vessels in critical zones.
Notifications and monitoring scenarios
Further storyboarding for Vessels in critical zones.
Notifications to send outside of critical zones
Existing notification scenarios delivered via emails
1. Added
A cargo with a specific product from a region is added.
2. Dropped
- A cargo is no longer reported by Vortexa (according Vortexa it no longer exists or is merged), goes to dropped baselines page.
3. Changed
- Load or discharge country, materials, quantities etc.
BUSINESS NEEDS
More timely and informed market trades.
Change of direction or destination
Potential new and existing functionality explained, when entering, within or exiting a critical location.
Change of direction or destination
Existing functionality in non critical zones explained.
Known unknowns and requirements still to answer
