Service-Oriented Government Mark Johnson Director Consulting, CGI-AMS Timothy Davis Senior Solution Architect Manager

1. Service-Oriented GovernmentMark JohnsonDirector Consulting, CGI-AMS Timothy DavisSenior Solution Architect Manager, Oracle

2. 2 Agenda Government Under Pressure SOA Concepts & Maturity Model Trends and Developments SOA in Government The Path to Successful SOA

3. 3

4. 4 Government’s Business Transformation Imperative Whether the organization requires dramatic changes or incremental improvements, managing government modernization in the face of growing constraints requires a new way of thinking.

5. 5 National Priorities

6. 6 Transforming Government

7. 7 Summary

8. 8

9. 9 SOA – Historical Progression

10. 10 A service … Is a unit of work done by a service provider to achieve results for the service consumer Is a software component that is capable of providing access to functions and data Is exposed to other components via a service description Appears as a “black box” to the service consumer Is interacted via message exchanges Encompasses a business perspective Decouples its interface from its implementation Is built to last

11. 11 Service-Orientation Service Orientation Use of “open” interoperability protocols that facilitate application assembly based solely on service descriptions and organized in a way that supports the dynamic discovery of appropriate services at run time Architecture A process of putting together components to achieve some overall goal A blueprint that comprises the components organized by layers, their visible properties, their relationships and interactions, and constraints A discipline that addresses cross-cutting concerns to manage complexity and encourage holistic thinking

12. 12 SOA - Bringing Business and IT Together Two parts. 1. the business direction. where the emphasis is on the identification of the business services that are defined, and the enablement of new business partnerships and business processes using these services. 2. the technology direction, where the emphasis is on the technology platform, the standards, and the new capability that enables these new business processes to be defined. It is important to emphasize that to define SOA, you need to include both these components.Two parts. 1. the business direction. where the emphasis is on the identification of the business services that are defined, and the enablement of new business partnerships and business processes using these services. 2. the technology direction, where the emphasis is on the technology platform, the standards, and the new capability that enables these new business processes to be defined. It is important to emphasize that to define SOA, you need to include both these components.

13. 13 Business Value of SOA Agility & Accelerated Delivery Separation of business process logic and business rules from applications Business processes can be changed easily Shorter time-to-deployment for changed processes Reduced Cost Consolidation of infrastructure leads to fewer components and hence reduced initial cost and license Simpler infrastructure management Higher Quality Eliminating redundancy reduces inconsistent data and inconsistent behavior Use of open standards and well-defined architectural constructs leads to better understanding

14. 14 Challenges Organization & Governance New processes in which many different IT and business players have a role Defining and validating services, Managing reuse Allocating costs - Who pays? Core funding from a central authority vs. Usage based billing for common services Free market to allow best services to survive vs. Forced monopoly to minimize overall costs Architecture Requires development discipline and methodologies that must be defined and enforced Software Need to invest in tools and technology to service-enable established IT assets Lack of SOA Expertise and Experience Few mature SOA methodologies

15. 15 Traditional ModelA Vertically Integrated Approach

16. 16 SOA Example HHS Reference Architecture

17. 17 SOA Example HHS Reference Architecture

18. 18 Centralized vs. Federated A successful SOA requires both centralized and federated components Singular vision & goals, governance, enterprise repository management, and many operational functions should be centralized Service development should be federated to the producing units Allow for local units to override/extend business rules (rules are hierarchical in nature – federal, state, local)

19. 19 SOA Maturity Model

20. 20

21. 21 Gartner Hype Cycle

22. 22 Gartner

23. 23 Gartner

24. 24 IDC and Aberdeen IDC report SOA spending will reach $8.6 billion in 2006—a 138 percent increase from 2005, when spending totaled $3.6 billion. By 2010, IDC estimates companies will spend upwards of $33 billion on SOA services Aberdeen Group From 2006 to 2010, SOAs could help Global 2,000 corporations save up to $53 billion in IT costs SOA can help save up to 25% on application development costs when used over the entire development life cycle

25. 25 18th Century, to the British Admiralty, when the Royal Navy found itself charged with protecting the empire’s vast interests in the face of an increasingly tight-fisted Ex-Chequer. Talk about SOA in government, local and state government18th Century, to the British Admiralty, when the Royal Navy found itself charged with protecting the empire’s vast interests in the face of an increasingly tight-fisted Ex-Chequer. Talk about SOA in government, local and state government

26. 26 SOA Examples – City Government Local Government - Citizen services DCStat (http://www.adtmag.com/print.aspx?id=18271) Integrates data stored on individual systems 150 data sets, crime statistics, city services requests, geographic features, etc Analyzes data to reveal patterns and trends Notifies city officials of potential problems SOA architecture Integration with a agency legacy systems J2EE backend, .NET as the presentation Benefits Improved services Reduced costs During the initial demo – after consolidating information, found that there were 2,600 abandoned vehicles in the DC streets. Lesson learned - would not have required the DCStat prototype to become the base application. During the initial demo – after consolidating information, found that there were 2,600 abandoned vehicles in the DC streets. Lesson learned - would not have required the DCStat prototype to become the base application.

27. 27 SOA Examples – County Government County Government – Legacy Assets Miami-Dade County Majority of applications on mainframe Leveraged SOA to expose legacy applications Standardized access to Property Tax System Answer Center Project Allows the public call, fax, email or enter queries over the web for any issue Single access point Extensive integration with legacy systems Benefits Improved customer service levels Reduced costs Level 1, with aspects of Level 2 & 3 Integrated SOA in development processes Integration with externals

28. 28 SOA Examples – State Government Human Services – Child Welfare Wisconsin & DC SACWIS Systems built with web services Inter-application functionality External agency integration Mobile device integration Potential for value-add services Master Data Management Common eligibility determination  Benefits Flexibility and responsiveness Reduced Cost  Lesson learned – when you rely on other departments, make sure you have established the rules of governance – (SLAs, joint problem resolution, etc) Lesson learned – when you rely on other departments, make sure you have established the rules of governance – (SLAs, joint problem resolution, etc)

29. 29 SOA Examples – State Government Enterprise State Government California Enterprise Architecture Program SOA a key component (segment) of the Enterprise Architecture SOA Blueprint that supports business Defined SOA principles and Established SOA Center of Excellence SOA leadership, governance, and management of components Expected Benefits Reduced total cost of ownership More responsive to changing business requirements, reduce the time to develop new applications Attempting level 4/5 Enterprise governance, tracking performance Full business processes via SOA

30. 30 SOA Examples Federal Government

31. 31 SOA Examples Federal Government A Complex Process SimplifiedAviation System Standards publishes new flight procedures every 56 days and issues change notices every 28 days. The FAA is moving away from manual processes that result in new paper charts for distribution. With Oracle products, the entire process is becoming automated. Previous versions of the procedures will be stored in FAA systems, changes to the airspace and flight routes will be managed electronically, and new chart generation will be automated. Data integration, process tracking and spatial referencing will help Aviation System Standards simplify production and maintenance of flight procedures. This automation will remove potential for manual errors, reduce time to chart delivery and increase work capacity. "Highways in the Sky"The FAA's airspace navigation system includes on-ramps, off-ramps, and "highways in the sky." Continuous maintenance is required to keep flight procedures current with new obstructions to airspace such as cell-phone towers and high-rise buildings. With Oracle Database 10g's spatial functionality, including GeoRaster and vector data capabilities, the FAA will be able to consolidate aeronautical information into a virtual data store. Oracle Application Server 10g and Oracle MapViewer are important in enabling the FAA to quickly identify which flight routes are affected by a new structure and assist in taking the necessary steps to help keep the airways flowing safely. Beyond increasing flight safety and improving processes, the information stored in the FAA's spatially enabled database will provide other federal agencies with valuable data. For example, other government organizations supporting programs with similar processes could layer specific geographic and non-geographic information they manage to create more accurate intelligence views and track anomalous patterns. A Complex Process SimplifiedAviation System Standards publishes new flight procedures every 56 days and issues change notices every 28 days. The FAA is moving away from manual processes that result in new paper charts for distribution. With Oracle products, the entire process is becoming automated. Previous versions of the procedures will be stored in FAA systems, changes to the airspace and flight routes will be managed electronically, and new chart generation will be automated. Data integration, process tracking and spatial referencing will help Aviation System Standards simplify production and maintenance of flight procedures. This automation will remove potential for manual errors, reduce time to chart delivery and increase work capacity. "Highways in the Sky"The FAA's airspace navigation system includes on-ramps, off-ramps, and "highways in the sky." Continuous maintenance is required to keep flight procedures current with new obstructions to airspace such as cell-phone towers and high-rise buildings. With Oracle Database 10g's spatial functionality, including GeoRaster and vector data capabilities, the FAA will be able to consolidate aeronautical information into a virtual data store. Oracle Application Server 10g and Oracle MapViewer are important in enabling the FAA to quickly identify which flight routes are affected by a new structure and assist in taking the necessary steps to help keep the airways flowing safely. Beyond increasing flight safety and improving processes, the information stored in the FAA's spatially enabled database will provide other federal agencies with valuable data. For example, other government organizations supporting programs with similar processes could layer specific geographic and non-geographic information they manage to create more accurate intelligence views and track anomalous patterns.

32. 32 NAVSEA September 16, 2004 (Derived from: Conversation with Dave Scheid, NAVSEA Port Hueneme and W White.) Organization deploying: Naval Surface Warfare Center (NSWC) under NAVSEA   Goal: to have a seamless data flow from people who create infomation to the people who consume it—i.e. the sailor on the deck plate who requires tech procedure and knowledge to his job. Tech procedure are created on the shore. Flow must be seamless between Creation of information Publication of information Distribution of information (out to ship) Shore – Need to access reliability data, historical, current supply info via apps: SCM, R&D apps, Test and evaluation, Engineering SOA Examples Federal Government Sea – sailor just needs to have the right info at the right time. Need apps: -          tech procedures -          current drawings -          updated maintenance specs -          current alteration info   Sailor fixes things at sea and operates things – operator and maintainer. Sailor is on average on a ship for 3 to 6 years. As changes are made to operating procedures, these need to be updated and oftentimes a sailor does not have the chance to go back to school for training.   The seamless access to data is compounded by the fact that the ships move all over the world, all the time. Must have the ability to seamlessly put together.   Current Implementation Timeframe: -          Piloting now with 2,500 (started already) users and involves about 20-25 apps. Using Plumtree Portal. AD directory. -          Plan is to then rollout to other warfare centers in FY06 and 07 (one year’s time), to around 15,000-20,000 users.   Use of COREid NAVSEA is most interested in the access control portion and to set up policies for individuals to access thee different applications. -          They want SSO as well as the logging capability for security concerns. In the future, they will likely adopt a federated model to share access across the US Naval organizations, including - NAVSEA, NAVSUP, (support) and SPAWAR, NAVAIR. Sea – sailor just needs to have the right info at the right time. Need apps: -          tech procedures -          current drawings -          updated maintenance specs -          current alteration info   Sailor fixes things at sea and operates things – operator and maintainer. Sailor is on average on a ship for 3 to 6 years. As changes are made to operating procedures, these need to be updated and oftentimes a sailor does not have the chance to go back to school for training.   The seamless access to data is compounded by the fact that the ships move all over the world, all the time. Must have the ability to seamlessly put together.   Current Implementation Timeframe: -          Piloting now with 2,500 (started already) users and involves about 20-25 apps. Using Plumtree Portal. AD directory. -          Plan is to then rollout to other warfare centers in FY06 and 07 (one year’s time), to around 15,000-20,000 users.   Use of COREid NAVSEA is most interested in the access control portion and to set up policies for individuals to access thee different applications. -          They want SSO as well as the logging capability for security concerns. In the future, they will likely adopt a federated model to share access across the US Naval organizations, including - NAVSEA, NAVSUP, (support) and SPAWAR, NAVAIR.

33. 33 SOA Examples Local Government

34. 34 SOA Examples Local Government

35. 35

36. 36 The Path to a Successful SOA Project

37. 37 Step 0 | Select An Application

38. 38 Step 1 | Build Portfolio of Services

39. 39 Step 2 | Wire Through An Enterprise Service Bus

40. 40 Step 3 | Orchestrate into End-to-End Processes

41. 41 Step 4 | Expose through Rich User Interfaces

42. 42 Step 5 | Deliver Real-time Dashboards

43. 43 Step 6 | Secure Interactions

44. 44 Step 7 | Scale On Demand

45. 45 Overall themes and recommendations Business drives architecture Need a vision to guide SOA evolution SOA creates opportunities for “pluggable business” SOA applies to many scenarios Services must be designed in a process-centric way Learn from emerging patterns in the real world Orchestration is a good first step into greater levels of SOA flexibility

46. 46 Questions and Comments

47. Thank You Timothy Davis 951.514.9951 timothy.davis@oracle.com