Use Case 2: Buy Side Portfolio Manager

Preconditions

On their desktop, this user has: 

• An installed full-service market data terminal with news, quotes, research management, etc. The application is open and FDC3 compatible.
• A third-party portfolio management system. The application is closed and not FDC3 compatible.
• An installed application for the chat tool used by the firm. The application is open and FDC3 compatible. It also has a proprietary integration to the portfolio management system.
• The default web browser for the OS
• The default mail application for the OS

On their mobile device, this user has:

• The default mail application for the device
• The default web browser for the device
• The installed application from the market data provider
• The installed application for the chat tool used at the firm

Workflow 1 (non-desktop)

While out of the office, the user receives an email alert from his market data provider that a new research report has been posted which mentions a company that user is interested in. The user wants to read the report and clicks on the link in the email report. The market data application is launched and shows the research report.

Not currently supported by the API, should we have a fdc3:// handler 

Decision needed on yes/no and then how. 

whats after // ? 

Workflow 2

Back in the office, the user wants to follow up on the report so he goes to his email client, finds the email and clicks the link. The market data application on the desktop displays the research report.

As above - on desktop 

Workflow 3

While reading the report the user wants to look up what the firm’s internal analysts have written about the company. The user hovers over the company identifier in the report and launches a tool within the terminal that shows the firm's internal research. A note from one analyst is intriguing so the user wants to know more. The user hovers over the name and launches the chat tool with a conversation with the analyst in focus and some details regarding the note is already posted to the chat.

Supported by find intents by context - viewAnlaysis and startChat 

types sent through payload eg FDC3.contact, FDC3.instrument, FDC3.phrase in order to pass the message through the startChat intent

Posting the chat automatically is not supported. Happens when the user send the message

Workflow 4

During the chat, the analyst sends a link to a web site containing some further details regarding the company and the reason for the note posted. The user clicks on the link and the web browser opens. The user reads the article and continues to chat with the analyst.

Achieved through URLs 

Workflow 5

During the chat, the analyst shares a chart with some important observations highlighted. The user clicks on the chart image in the chat and the terminal opens a live version of the chart with the observations highlighted.

Sharing hml chart through protocol handler. Similiar to 1 & 2 

Workflow 6

During the chat, the user realizes that some changes should be done to their holdings in the company so hovers over the company identifier and launches the portfolio management system. While looking over the holdings the user also wants to contact the firm’s trader who is listed within the system. The user hovers over the name and launches the chat tool with a conversation with the trader in focus.

1. Context lookup by type to find intent 

2. Context types passed eg fdc3.instrument, fdc3.contact - composite object of instrument and the chat contact to send to the portfolio management system 

3. Context lookup by type eg fdc3.contact 

Interoperability Points

Context Data WG, API WG, Intents WG, Financial Objects Program

Missing overall: protocol handler