OEM - Balancing Control and Innovation

Presenter: Michael Ogrinz, Principal Architect, Global Markets Technology, Bank of America Securities, LLC

architect role is liason between business and IT, get to work with technology but don't have to worry abbout 2am support calls
Showed the Froogle example with rebates
Ease of Use = Business Value, who cares about the exact definitions?
Example at BOA - people joining conference calls, mashing up data from AT&T call center, whitepages.com to show who is on the conference calls
When bringing in new tech at BOA, it sounds like products go through levels of acceptance, such as "emerging"
They'll never use a mashup to broker a trade, but they would use mashups to quickly prototype how the UI should look for these systems
Generation Y vs Generation BabyBoomers
Leverage mashups for dashboards, discovery (of new ways to relate data), usability (quick testing of new UIs), application monitoring (quick, not really reliable, but useful in some circumstances)
Drawbacks: regulatory for who provides the data, brittle (who provides the SLA?),
SIFR - product for helping to secure mashup data so it doesn't get reused where you don't want it to be, basically renders the sensitive data as images

----
WSO2 Mashup Server Architecture, Apache licensed, make money from support and training.