| Status | ||||||
|---|---|---|---|---|---|---|
|
On their desktop, this user has:
- Their firm's proprietary research & analytics platform containing liquidity tools and internal research. The product is running and the liquidity tool is open
- An installed chat application - product is running
- A third party research & analytics platform with 3 open applications:
- A Watchlist
- An Order Book
- An Overview of pricing and fundamental data
- A third party Charting Application hosted in a web browser
...
The user receives a message in the chat application containing an instrument identifier for Tesla. They want to do some analysis on Tesla and so see what applications are available through right clicking on the identifier for Tesla. They have the option to launch an app in their proprietary platform, or in the third party platform. The user decides to launch an app in the proprietary analytics platform.
Workflow 2
The user wants to do further analysis see internally created and shared information on Tesla and so launches a proprietary research app that opens showing internal research published on Tesla.
Workflow 3
The user wants to analyse Tesla's market depth so launches the Order Book app in the third party analytics platform. From the order book they decide that they want to trade on Tesla and open an app menu that shows all available trading applications. They select the third party EMS and a trade ticket instance is launched with the instrument, amount and side filled.do further analysis on Tesla and so launches a third party research and analytics platform that opens showing financial statements and calculated financial data (such as market capitalization, P/E ratio, growth rate, earnings margins, etc) and 3rd party research documents published on Tesla that they are entitled to access.
Workflow 4
The user decides that they don't want to make the trade yet and they want to do some technical analysis. The third party analytics platform has an integration with the third party charting application and the user launches the app, which opens in a browser window.
Workflow 5
The user wants to see information about another competitive international automobile company such as BMW. The user changes the selected identifier from Tesla to BMW in one app in the third party platform and the open applications, including the charting application, change to show information on BMW instead of Tesla.
Workflow 6
The user adds BMW and Tesla to a shared group of companies (aka a Watchlist) named "Automotive comparables" to a list within the watchlist. This group of companies is shared with all applications which use this group for any comparative analytics.
Possible to meet workflow using Broadcast, but not fully fit for purpose.
API would need to be extended to support channels.
Need to have FDC3 specific channels eg 'FDC3 Blue' and 'FDC3 all' - default channel
Option to declare which types the app wants to listen to
Interoperability Points
- API
- Intents
- Context