Yale Solutions Design October 2012

Slides:



Advertisements
Similar presentations
Light Enterprise Architecture
Advertisements

Connected Health Framework
Presentation Title | Date | Page 1 Extracting Value from SOA.
Supporting New Business Imperatives Creating a Framework for Interoperable Media Services (FIMS)
Life Science Services and Solutions
Risk & Novelty Collaboration & Engagement Efficiency & Effectiveness Transferability & Scalability ▪Led government as first agency to implement enterprise-wide,
JUNE 2007 page 1 EDS Proprietary Applications Modernization Services Modernizing the Applications Portfolio.
Current impacts of cloud migration on broadband network operations and businesses David Sterling Partner, i 3 m 3 Solutions.
BENEFITS OF SUCCESSFUL IT MODERNIZATION
Applying the SOA RA Utah Public Safety ESB Project Utah Department of Technology Services April 10, 2008 Prepared by Robert Woolley.
Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
Delivering Mission Agility Through Agile SOA Governance 13 th SOA e-Government Conference 4/12/2012 Presented by Wolf Tombe Chief Technology Officer (CTO)
Enterprise Integration Architecture IPMA Professional Development Seminar June 29, 2006 Scott Came Director, Enterprise Architecture Program Washington.
© 2006 Carnegie Mellon University Establishing a Network Centric Capability: Implications for Acquisition and Engineering Dennis Smith Complex System Symposium.
Service Oriented Architecture Concepts March 27, 2006 Chris Armstrong
Federal Student Aid Technical Architecture Initiatives Sandy England
Independent Insight for Service Oriented Practice Communicating SOA.
© 2006 IBM Corporation IBM Software Group Relevance of Service Orientated Architecture to an Academic Infrastructure Gareth Greenwood, e-learning Evangelist,
June 3, 2015 Government Technology Forum: Service Oriented Architecture (SOA) Jonathan Natarajan Enterprise Integration Program Manager.
Stuart Sim Chief Architect Global Education & research Sun Client Solutions Blog:
Amanda Felix BUS 550 Tuesday, May 24,  Traditional methods are not enough!  Reduce costs, improve efficiency and spur innovation!  Information.
1 MAIS Student Administration Advisory Group Meeting #31 October 4, 2006.
Enterprise Architecture The Arkansas Approach. Key Areas What is enterprise architecture? Why is it important? How you can participate Current status.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
Realising the Potential of Service Oriented Architecture Kris Horrocks Connected Systems Division Microsoft.
Systems Integration & Consulting June Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities.
enterprise S.O.A. SOA What? why R U here? mandated to build company portal understand how to fit GIS into a portal technology enthusiast.
Private Cloud: Application Transformation Business Priorities Presentation.
INTEGRATION OF E - BUSINESS WITH ERP SYSTEM P RESENTATION ON INTEGRATION OF E - BUSINESS WITH ERP SYSTEM Presenting by Presenting by, Shruti raj Anushree.
Getting Smarter with Information An Information Agenda Approach
SOA – Development Organization Yogish Pai. 2 IT organization are structured to meet the business needs LOB-IT Aligned to a particular business unit for.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
a Service Oriented Architecture
IBM Software Group - IBM Systems Group © 2006 IBM Corporation IBM Software Group | IBM Systems Grouppage 1 Team Collaboration Software Selling Strategy.
1. 2 IT innovations in specialized areas where competitors will have difficulty copying Excellence in design of processes and activities and how they.
A Microsoft Perspective Kirby Bartholomew Product Manager Application Platform & Developer Marketing
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Service Oriented Architecture Ruwan Wijesinghe.
International Telecommunication Union Geneva, 9(pm)-10 February 2009 ITU-T Security Standardization on Mobile Web Services Lee, Jae Seung Special Fellow,
1 Hasan Rizvi Senior Vice President Fusion Middleware Development.
Service Oriented Architecture (SOA) at NIH Bill Jones
Progress SOA Reference Model Explained Mike Ormerod Applied Architect 9/8/2008.
1 The Benefits of an SOA in the Contact Center Brian Garr Program Director, IBM Speech Solutions.
Service Oriented Architectures Presentation By: Clifton Sweeney November 3 rd 2008.
1 Geospatial and Business Intelligence Jean-Sébastien Turcotte Executive VP San Francisco - April 2007 Streamlining web mapping applications.
Service Oriented Architecture (SOA) Dennis Schwarz November 21, 2008.
© 2005 IBM Corporation IBM Business-Centric SOA Event SOA on your terms and our expertise Operational Efficiency Achieved through People and SOA Martin.
Catawba County Board of Commissioners Retreat June 11, 2007 It is a great time to be an innovator 2007 Technology Strategic Plan *
Last Updated 1/17/02 1 Business Drivers Guiding Portal Evolution Portals Integrate web-based systems to increase productivity and reduce.
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
ARE YOUR APPLICATIONS HOLDING YOUR BUSINESS BACK?
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
IEEE IT (Information Technology) Strategy – 2005 Unapproved.
Driving Business Agility at Pfizer Martin Brodbeck Application Architecture Director Pfizer Global Pharmaceuticals June 7, 2004.
Robert Mahowald August 26, 2015 VP, Cloud Software, IDC
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Basics of SOA Testing Assurance Services Unit 24 February 2016.
 TECHNOLOGIA is a startup company in Bangalore in 2007 which is completely owned by emirates telecommunication corporation- ETISALAT.  It has helped.
8a Certified. About Us  Headquarters in Vienna, VA  Service Disabled Veteran-owned Small Business  SBA 8(a) program participant  Small Disadvantaged.
Service Oriented Architecture Enabling the Agile and Flexible Business of the 21 st Century.
Driving Value from IT Services using ITIL and COBIT 5 July 24, 2013 Gary Hardy ITWinners.
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
CIM Modeling for E&U - (Short Version)
Application Portfolio Optimization
Enterprise Architecture at Penn State
SOA Strategies for Enterprise X
Introduction to SOA Part II: SOA in the enterprise
Matthew Farmer Making Azure Integration Services Real
OU BATTLECARD: Oracle SOA Training & Certification
Presentation transcript:

Yale Solutions Design October 2012 Service Oriented Architecture (SOA) Enterprise Architecture (EA) Enterprise Service Bus (ESB) Yale Solutions Design October 2012

Current Integration Challenges All issues, technical and non-technical need to be addressed in order to effect positive architecture change across the enterprise. Each team follows unique standards for technology selection, design, build, and deployment Connectivity is point to point and not reusable Projects are always time bound which forces teams to make decisions at the project level Improvements happen at the team or project level

Current Integration Challenges: Results Fortunately there is a proven way forward! It will require a significant paradigm shift, however. Few assets/services are shared/reused (even within teams) Redundancies may exist (which yield disparate results) The Development teams operate within their respective domain and are therefore unable to collaborate on standards There is inconsistent behavior across teams in terms of solution delivery Clients miss opportunity to benefit from team collaboration Separate, discreet application construction and deployment does not scale

Sample EDS System Connectivity 4

Definitions Page What is an Enterprise Service Bus (ESB)? A secure and robust middleware environment that enables systems to interoperate independently of technology An integration facilitator that allows internal and external systems to share information Implements SOA through Virtualization and management of service interactions What is Service Oriented Architecture (SOA)? An architecture strategy that drives a close alignment to the business by deconstructing IT systems into discreet services that perform business functions Services communicate via the ESB and may be reused Can drive architecture disintermediation via the composition of independent services into mashups or apps Examples: search, impersonation, login, person lookup, course lookup, etc.

Why do we need an ESB and SOA? Systems no longer connect directly thereby allowing greater control and enforcement of the following principles: Standards Security Governance Reusability Consistency Data Integrity We can build and leverage a suite of business services that can be assembled into composite applications Multiple channels (Web, Portal, Cloud, etc. ) can be authenticated to access shared services Data synchronization managed through the ESB Publish/Subscribe queue

Additional Benefits and Opportunities Standardized, Streamlined, and Simplified Architecture Teams spend less time on complex and redundant architectures and now focus on business process, reuse, and quality ITS team focus, collaboration, and consistency SOA practices enable ITS to shift focus to becoming a ‘Change Ready’ and ‘Change Enabled’ organization Teams collaborate to build shared services vs. siloed applications Individual customizations replaced by standardized and governed practices Improved Customer Service Client benefits range from helping define business services and processes, to being able to consume shared services ITS’ ability to adapt to changing business needs enables positive and consistent business process improvement Clients move from being ‘customers’ to ‘partners’

Cost/Relationship Savings Opportunities One time Service Reuse Maintenance reduced through consolidation and reduced redundancy of business functionality Pre-built services pulled ‘off the shelf’ to compose applications thereby reducing the time to build and deploy (same as COTS) Recurring Operational costs Maintenance and support of services Improved System Quality Deployed services are certified thereby reducing defect remediation Improved Data Quality Redundant data access minimized and replaced by standardized data services that can be reused by authorized personnel

Basic “Service Based” Architecture The initial SOA architecture includes the creation of reusable interface services that connect disparate systems. Enables initial system/data decoupling. Enterprise Service Bus CIMS Teaching Fellows Med Apps Services (Global or Local) Systems Users Services HR Banner Transport Layer DW

Future SOA Environment (Sample) New applications will take full advantage of composite applications via services. User interface is completely decoupled from the data source. ESB Data Service Banner HR Alumni Vendor Packages Web Access Cloud Vendors Mobile System of Record Standard access mechanism Data Service DW

Data Synchronization with Queues Change events are published to a common transient queue where multiple applications can subscribe to the same topic App 1 App 2 App 3

“Build-to-Change” versus “Build-to-Last” The SOA Imperative: “Build-to-Change” versus “Build-to-Last”

SOA Services Strategy and Delivery SOA lifecycle management moves us from a linear thinking mode to a circular or evolutionary process. Start Evaluate, Enhance, De-commission Identify and Define Governance Governance Monitor Develop/ Modify Test/ Deploy

Community / ITS Relationship The alignment between the community and ITS can be improved and facilitated through a well-defined and governed Enterprise Architecture process Enterprise Architecture is a Critical Success Factor for the entire Yale community to achieve their expected results

Enterprise Architecture The ESB and SOA technologies are enablers: The end goal is managed Enterprise Architecture. Links ITS to the Yale Community by translating Yale’s vision and strategy into scalable and adaptable technology principles and models Manages current and future state technology vision Enables a ‘going in position’ when evaluating software, vendors, or new projects Manages risk and cost through standardization, reusability, and governance Consistently maintains a view at the enterprise level to ensure efficient utilization and orchestration of all resources

Enterprise Architecture Enterprise architecture principles drive a global perspective within an organization across business, data, application, and technology domains. Business Architecture Strategy Process Services Organization Data Architecture Entities Sources Access Governance Applications Architecture Standards Platforms Integration Technology Architecture Frameworks Infrastructure Operations

Starting with a Mission 17 The Mission should define the strategy and all activities should map back and fully support it Data Architecture Define, support, secure, and maintain the types, sources, and relationships of data necessary to enable the goals of the organization in a way that is complete, consistent, trusted, and understandable by all constituents.

Why Focus on Architecture? IT Strategy Business Strategy Enterprise Architecture Enterprise Architecture provides the tight cohesion and loose coupling between IT and Business strategies It is the ‘glue’ that ties together Business and IT strategies and enables them to drive each other Enterprise Architecture can provide the technology innovation engine that enables ITS to better serve business partners

Responding to Business Change via Architecture Managing Change is Key Business Driver Benefits of SOA Respond Better, Faster, Cheaper to Change Align ITS with Business Agility, Flexibility Reusability Improved Quality Platform, Technology Independence Reduced Redundancy Change is Constant Customer Needs SaaS / PaaS Solutions Vendor Solutions ITIL Legacy System Support Integration across all environments

“Build-to-Change” versus “Build-to-Last” The SOA Imperative: “Build-to-Change” versus “Build-to-Last”

‘Change Ready’ Organization Flexibility Speed Agility Adaptability Responsiveness Thoughtfulness Innovation Collaboration Rapid Evolution How do we accomplish this? Organizational alignment Tools Architecture Processes Mind-set Commitment ...Leveraging our Strengths

Why focus on Change Readiness now? Strong need to integrate disparate environments to ensure consistency and data synchronization across all platforms. Key Building Blocks and Drivers are in-place or underway ITIL Relatively new organizational model Student Information Systems (YaleBluebook, Leep Frog, etc.) Cloud Vendor proliferation (SalesForce, ServiceNow, QB, etc.) Rethinking ERP environment DARCY / Blackbaud Identity and Access Management Initiative

What will this do for us??? If we are successful, we will become Able to adjust to any newer technology or business trends more rapidly and calmly Able to integrate both internal and external systems and data in a consistent manner that models our standards Able to drive more effective and consistent technology decisions through a well thought out strategic architecture plan More effective at collaboration between teams and with our customers Better service providers to our customers

Current Services Status

Change Management for SOA & EA ITS needs to embrace five key aspects of change management as we move forward toward general adoption. Yale Adoption of SOA & EA Sponsorship Governance Communications Training Organization

Thank you for your time!

Appendix