Dave Mayo President, Everware-CBDI Driving Government Transformation: Service Oriented Government April 28, 2009 7th SOA for e-Gov Conference Dave Mayo President, Everware-CBDI Make the case that federal gov needs to be service oriented to meet its challenges and objectives.
Dave Mayo - Background President, Everware-CBDI Enterprise Architecture Service Oriented Architecture Model-Driven Solution Delivery 2009 Federal 100 Award (Federal Computer Week) Vice-Chair, IAC EA-SIG and Chair, Services Committee (Industry Advisory Council/Enterprise Architecture Shared Interest Group) Economics, EA & Information Engineering Sr. Advisor to DHS EA Program Information Strategic Planning Business Case/ROI Analysis White Papers Succeeding With Component Based Architectures (IAC, 2004) EA: It’s Not Just for IT Anymore (JEA, 2005) Services and Components Based Architectures (CIOC, 2006) Practical Guide for Federal Service Oriented Architecture (CIOC, 2008) Service Oriented Government: Performance Driven Results (Draft, IAC, 2009)
Everware-CBDI Independent specialist SOA firm Merger of established UK and US companies in 2006 25,000+ subscribing architects worldwide Enabling structured, enterprise level SOA Facilitating SOA standards Widely used best practices, reference architecture, repeatable processes - Services Architecture & Engineering (CBDI SAE™) SOA Solution Business including Education, Consulting, Knowledge products Everware-CBDI
Topics Background Setting the Stage: SOA in the Federal Government SOA Fundamentals SOA & EA SOA Critical Success Factors Practical Guide to Federal SOA Future of SOA: Service Oriented Government Recommendations Expectations from New Administration Money is being spent NOW. So, now is the time to invest in SOG. Future budget will be lower and the need for the SOG savings will be greater.
We have a few problems… Inconsistencies in process, semantics, technology Redundancy in business processes, systems, data Lack of interoperability Stakeholders must engage with multiple organizations to achieve a single objective Difficulties sharing information Organizational rigidities prevent quick responses IT not well aligned with business objectives and difficult to change
Strategic Issues Facing Federal Agencies Change is Ubiquitous & Discontinuous Increasing complexity – all aspects Often unforeseen (threats, environmental, legislative, budget) Impacts all facets of the business Organizations are increasingly unable to adequately respond Organizational barriers Process rigidities Silo’d applications & inflexible IT infrastructure Need to improve operational effectiveness Integration across the enterprise & entire supply chain Reduce cycle times for virtually all processes Improve access to data needed for operational decisions We’ve already hit the wall.
The Solution: The Agile Enterprise Business cycle-time must be faster than rate of change in external factors IT must be able to keep up with business changes Agile organizations require adaptable architectures 1980’s and earlier 1990’s New Millennium 3rd party service providers Extranet Internet Customers Organization Focus Mainframe centric Monolithic Internal use Business Process Focus Client/Server Monolithic Business-to-business via EDI -file transfer Virtual organizations Distributed Functions Service oriented Web 2.0 Mashups Near real-time
Minimize the impact of changes at each level on the other levels The Key to Agility Minimize the impact of changes at each level on the other levels Business Impacts Frustration Demand Applications Impacts Technology Key Techniques: Separation of Concerns: SOA Abstraction: Model Driven Systems Engineering
EA is the Most Valuable Tool to Support Government Transformation Architecture is necessary to manage complexity Models assist in understanding, prioritizing and communicating FEA is the only tool available for cross-agency analysis Many government value chains cross agency boundaries (and government levels, too) Fundamental value of EA is aligning investments with priorities But it must be a service-oriented EA!
-- OASIS SOA Reference Model version 1.0 SOA Fundamentals "Let's start at the beginning. This is a football. These are the yard markers. I'm the coach. You are the players." Vince Lombardi Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. Service: The means by which the needs of a consumer are brought together with the capabilities of a provider. -- OASIS SOA Reference Model version 1.0 SOA – Lego approach Service – dry cleaning. Most of you have heard this story from Green Bay Packer’s history before. It has achieved legendary status in NFL lore. The Packer franchise had been losing for close to ten straight years. They were again at the bottom of the standings, and morale was at an all time low. Enter Vince Lombardi as the new coach. He is charged with turning this franchise into a winning team, and he believes the team can become a winner. He started leading practices himself, inspiring, training, motivating. But at one point, he got so frustrated that he started blowing the whistle to stop the practice. "Everybody stop and gather around," he said. Then he knelt down, picked up the ball, and said, "Let's start at the beginning. This is a football. These are the yard markers. I'm the coach. You are the players." He went on, describing the most elementary concepts in the game of football to lay a solid, common foundation for his team. Today there are many definitions for Service Oriented Architecture. Just about every vendor has their own definition. All are similar, but none are really the same. There are some independent definitions available and we present two here. OASIS has released an SOA Reference Model that is intended to become an industry standard for basic SOA vocabulary. The jury is still out on whether or not this will be adopted by the industry, but it is available today.
SOA Basics SOA is an architectural best practice for EA All organizations need agility; therefore all need SOA SOA should be the predominant architectural pattern in all agency EAs Services affect everything Service oriented enterprise (SOE) Service oriented architecture (SOA) Service oriented infrastructure (SOI) 11 © 2008 Everware-CBDI Inc 11
Is Cloud Computing going to replace SOA? SOA Confusion Is SOA dead? Services Anarchy Net-centricity Focus is on finding, sharing & exploiting information to achieve superiority Is Cloud Computing going to replace SOA? Cloud Computing = Software as a Service + Infrastructure as a Service.
SOA Mismatch Claims of organizational agility and better alignment between IT and the business But often the definition of SOA is technology based Web services (WS-*, JBOWS) Integration technology (eg, ESB) Business benefits are derived from SOA as a flexible architecture of collaborating services
SOA Critical Success Factors Trust Security Service Certification SLAs Testing & Monitoring (adaptive/collaborative/continuous) Consistency Semantic - Data Service Reference Architecture (EA) SOA Readiness & Maturity Org Change Management Management of the SOA Adoption Process Federated Governance Enforceable Contracts Funding & Cost Recovery Service Oriented Acquisition Technology Platform Infrastructure as a Service - Cloud Computing Discovery – Repositories/Registries
SOA Vision: Flexible, Federated Business Processes BT-ECI Module 02 SOA Overview Enabling reuse of Services in different scenarios Service Ticket Collection Identification Enabling alternative implementations to provide the same Services Enabling a virtual federation of participants to collaborate in an end-to-end business process Service Enabling aggregation from multiple providers, or flexible choice of provider Ticket Sales Service Availability Service Payment Ordering The provision of Services enables businesses to collaborate in real-time with business partners and customers – up and down the supply chain. Many businesses will already outsource commodity capability – such as logistics. SOA enables the services of 3rd party providers to be integrated into the overall system as if they were internal resource – so there should be no loss of information flows when capability is outsourced. SOA therefore enables the virtualization of business resources, through Outsourcing, insourcing, offshoring, etc Secondly, in the example of the Payment service, services that are properly designed to be shareable can be reused in new scenarios. Not just shared by many customers, but if the service is more abstract and generalized it can also be reused in different processes and even different context. For example, <CLICK> a service that is used to take payments in one context, might be used for identification in another. Finally, in the example of the flight availability services, <CLICK> information can be aggregated or selected from multiple providers of the same commodity service. Airlines differentiate on the price of their flights, the quality of their service, not on the way ticket prices are processed. The motivation for SOA therefore is <CLICK> Business Agility, Business Efficiency, increasingly in a global context Motivation: Business Agility Business Efficiency Globalization Service Service Inventory Logistics Service Manufacturing Enabling virtualization of business resources Outsourcing, insourcing, offshoring, etc © 2008 BT Global Services, and Everware-CBDI Inc
SOA Organizational Impact: Twin Track Development Service Portfolio based on highly reusable services Strict separation of provider and consumer Requires service oriented demand forecasting Enables just in time assembly Volatile, short-term, process specific Solutions Immediate Business Needs Solution Process Consume, Assemble Solution Customized Versions Specific Requirement Standard Versions The Consumer/Provider concept was frequently used in Component Based Development Service Portfolio Plan Service Portfolio Provisioning Process Provide Services and Service Automation Units Stable, Long-term, Reusable Assets
Practical Guide to Federal SOA: Keys to Implementation (SOE) Service Oriented Enterprise Treat SOA adoption as an organizational change initiative Build community processes and collaborative platforms Establish Federated Governance Establish service funding and charging mechanisms Service based SDLC with incremental development Shift to service based procurement Advance institutional knowledge and capture best practices
PGFSOA: Keys to Implementation (SOA) Service Oriented Architecture Use EA to align with business objectives Introduce Services as a First-Order Concept in your EA Establish a Service Based Target Architecture Adopt model based architecture and pattern based design Enable automatic compliance and alignment Leverage legacy assets to enable evolutionary progress
PGFSOA: Keys to Implementation (SOI) Service Oriented Infrastructure Focus on enterprise security, scalability, and interoperability Infrastructure as a service Establish discovery and trust mechanisms Repositories/Registries Information assurance & identity management Establish an adaptive and collaborative testing and certification environment
SOA Adoption Roadmap Objectives of the SOA Roadmap: SOA Readiness Assessment & Business Case SOA Adoption Roadmap Planning SOA Maturity Assessment SOA Adoption Management SOA Implementation Initiatives Objectives of the SOA Roadmap: Provide a framework for assessing an organizations SOA capability maturity. Present a roadmap for evolving an organization’s SOA capability. Theme: …“managed” adoption of a new approach achieves the objectives of the organization more quickly and at a higher level of maturity.
SOA Maturity Model Ecosystem Common ecosystem services eliminate organizational boundaries and enable broader economic activity Service concepts standardized across industry sectors and or LOBs Enterprise Enterprise level shared services create enterprise adaptability and consistency SOA enables enterprise wide consistency of business information and processes Integrated Shared services integrate silos, rationalize EAI contracts Integrated approach reduces complexity, cost and increases adaptability Applied Project based SOA activity Service architecture enables business adaptability for limited scope Early Learning Initial SOA activity Experimental
SOA Adoption Streams SOE SOA SOI Management . Management tools including vision, strategy, funding, charging, measurement and monitoring and SOA adoption plans and management. Defined policies, roles, responsibilities and skills required to create, operate, manage and govern a service environment. Capability to execute classes of project and or program, defined as project patterns The business models and business transformation plans that shape a service oriented business and integrate and drive requirements for service architecture The service architecture and Service Portfolio Plan (SPP) The reference framework including concept model, reference architecture and process to enable and coordinate federated service delivery and execution. Life cycle support architecture and implementation to support planning to delivery service states. Operational infrastructure architecture and implementation to support the run time service life cycle states. . Organization SOE Projects & Programs . Business Design . . Service Architecture SOA Framework and Process . LifeCycle Infrastructure . SOI Operational Infrastructure . Early Learning Applied Integrated Enterprise Ecosystem Maturity Level
Service Oriented Government Virtual Government Value Chains Combination of: Enterprise Architecture (Federal Gov is the Enterprise) Business Process Management Service Oriented Architecture Independent of Federal Organizational Structure Starting Points: Federal Enterprise Architecture (FEA) Reference Models, Segment Architectures PGFSOA (2008) Architectural Principles for US Government (2006)
OMB Future Direction: Services The Historical Approach … The Future Approach … Treasury IT & Services Service for Citizens DOJ VA State DOD USDA HUD DOI EPA Health Mortgage Insurance Commercial Provider HHS IT & Services DOJ Treasury VA USDA DOD State HUD DOI EPA HHS IT & Services Commercial Provider Service for Citizens = Agency-specific Service = Common Service = Service for Citizens = Commercial Provider Source: Dick Burk
Service Oriented Government The Historical Approach - Agency Focused… Citizen Service: Many agencies and offices; not one government Performance: No common framework for performance measurement across agencies; minimal budget-performance integration IT & Services: Redundancy within and across agencies Budget Allocation: Allocation of funds by Agency; minimal cross-Agency analysis The Future Approach - Mission and Service Focused… Citizen Service: One government Performance: Common performance measurement framework for OMB and all agencies; robust budget-performance integration IT & Services: Minimal redundancy in IT spending; component-based architecture promotes reuse Budget Allocation: Budget analyses take business lines into consideration; funds allocated to support cross-agency collaboration Source: Dick Burk, 2005
SOG in Action: NYC Business Express NYC Business Express Common Intake Portal BPM Engine Departmental Services NYC Department of Buildings NYC Dept of Health & Mental Hygiene IRS Business Express Process Services Intake Portal & Rules Engine Open a Restaurant
Recommendations OMB Agency Executive Management IT Managers Architects Mine Segment Architectures for commonality Establish Communities of Interest Require agencies to consume & share services Agency Executive Management Define goals in terms of value chains of extended ecosystem Insist on linkages between performance measures and processes/data/applications/technology IT Managers Acquire capabilities (services), not systems Manage portfolio of services vs. applications Architects Ensure the architecture support business leadership (fit for purpose) Service orient the EA and solution architectures Technologists Establish the platform and governance (eg, SLAs) to enable the transformation Decouple technologies – technology agility (eg, Cloud computing)
Expectations from New Administration Transparency Rapid Response Citizen-focused Transformation Efficiency (cost savings) New Technology & Innovation Effectiveness (performance) Bottom-line: An Agile Enterprise We need to do more with less, and faster.
Enterprise Service Solutions Thank you. Questions? Dave Mayo dmayo@everware-cbdi.com (703) 246-0000 x103 www.everware-cbdi.com Research Portal: www.cbdiforum.com Download the PGFSOA: http://www.whitehouse.gov/omb/e-gov/pgfsoa.aspx