0. Information Exchange: A Look forward
Presenter: David Rapoport
Project Leader, Next Generation Data Exchange
J.P. Morgan Worldwide Securities Services

1. Information Exchange: A look forward
Objective
To present thoughts and ideas around the future of information exchange and engage in an open discussion on movement forward
The Need for Innovation
Current State
A View into the Future
Open Discussion 1

2. Framework for Discussion: The Need for Innovation
There is much for us to do day to day. Still, strategic thinking requires that we peer well into the future, while still keeping our eye on immediate needs.
Quality of Experience: how much value add can be extracted from your experience with J.P. Morgan
Margins: We are all, constantly, under pressure to deliver better margins
Time to market: The demand for, and rates of, change will only increase
Mutual clients: Some of our clients are also your clients. Delivering value is mutually beneficial
Change Management: Agility needs to have a stable foundation
Advanced Planning for Growth: Technology needs to endeavor to be as agile as possible to not only support growth, but to be a catalyst in it
Mobile and Distributed Workforces
Regulatory and Political Climate Changes
Information Explosion: Key data for decisions grow each year and sources mix structured and non-structured data
Middle and Back Office Outsourcing: Rapid and seamless transitions are vital- as is an uptick in service 2

3. Key Challenges and Current State
Scale and complexity
Scale is enormous and will only continue to grow
Demand for seamlessness across the enterprise increasing and becoming more complex
Limitation of current tools
Struggles to keep up with increased complexity of demands
Lack of agility increases time to market
Implementation of robust, self service model not fully realized
Change management cumbersome, compromising risk management of agility
Industry standards vs. customization
Industry standards are important, but often lag behind the demand of clients
Formats used lack an exhaustive, formal specification, many extensions
Client Expectations
Lower latency is increasingly a demand
True STP often hindered by use of 3rd party data and applications
Greater demand to smooth out the LOB distinctions
Increased demand to keep up with the rate of change
New products and services
Regulatory changes
Client side innovations

4. Shaping the Future Together
Current state provides good service. We want to provide outstanding, sustainable service. Some options to explore:
Service Layer for data distribution: A RESTful state of being
API’s and Connectors for “pull” distribution of data
Standard methodologies for connecting to JPM for clients and 3rd party tools and services
Lower latency access to JPM data
Adaptors in “the cloud” to smooth away walls between products
Distribution of Visually Rendered Data
Next Generation of “Reports”
Configurable representation and delivery of dynamic data
Delivery to JPM tools or to client side tools, depending on need and ability
JPM helps out with presentation vs. Services/Adaptors where presentation is client side
Mobile device distribution
Services for Application Events and Integration
Currently a good suite of online tools. However,…
Online tools increase complexity of the end-user landscape
Minimize client, end-user, complexity via API exposure to key JPM applications
Enable greater B2B BPM 4

5. Shaping the Future Together
Event Driven Distribution
Richer choice and methodology
Intelligent Mixing of Events: e.g. Thresholds with events in the news and markets
Broader distribution channels: e.g. SMS, Mobile Applications, events over APIs/Services to client side applications
Requiring Requirements Changes
Requirements process is not as efficient as it can be
Untestable requirements are deleterious to change management
Deep and thorough understanding of change impact analysis is vital
Reduce time to market and risk through tighter control and connection of requirements documentation to build
Self Service that Benefits the “Self” Over the “Server”
Greater flexibility in interfacing with J.P. Morgan : Only “deal-breaker” rules should stand in our way
Greater transparency for on boarding custom inbound files/messages through improved flexibility in aligning J.P. Morgan 's capabilities with client requirements
Breaking down some of the product walls, currently in place, to allow clients access to our data without significant concern from its source at J.P. Morgan
Greater configurability around exactly what, where and when J.P. Morgan information goes
Accessing J.P. Morgan via mobile devices 5

6. Coda- XML: Do We Need a Kickstart
Within the Enterprise, XML of Various Flavors is Well Established:
Richer choice and methodology
Internal messaging
Data transformation and translation
Configuration in SOA and OO applications
Document construction
Between Enterprises, in Financial Services, the Uptake has been Lighter. Where do you see yourselves going?
FpML
FiXML
BPEL
Questions?