Seamless Integration of Data in E Government

837 views
703 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
837
On SlideShare
0
From Embeds
0
Number of Embeds
169
Actions
Shares
0
Downloads
28
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Seamless Integration of Data in E Government

  1. 1. Seamless Integration of Data in eGovernment Interoperability with WSO2
  2. 2. About WSO2 •  Providing the only complete open source componentized cloud platform –  Dedicated to removing all the stumbling blocks to enterprise agility –  Enabling you to focus on business logic and business value •  Recognized by leading analyst firms as visionaries and leaders –  Gartner cites WSO2 as visionaries in all 3 categories of application infrastructure –  Forrester places WSO2 in top 2 for API Management •  Global corporation with offices in USA, UK & Sri Lanka –  200+ employees and growing •  Business model of selling comprehensive support & maintenance for our products
  3. 3. Our Customers
  4. 4. Agenda ▪  About us ▪  Business problem statement ▪  Powered by WSO2 solution
  5. 5. About me Oscar Azañón Esteire ▪  CEO at Vitruvio Systems, S.L. ▪  15+ years of SW Architecture in different verticals: banking, Telco, eGovernment, etc. ▪  Coauthor of W3C’s TR Improving Access to Government through Better Use of the Web http://www.w3.org/TR/egov-improving/ ▪  Broad experience in SOA transformation programs.
  6. 6. About us ▪ Vitruvio Systems is a Software Architecture company, based in Spain (EU). ▪  Helped several organizations to embrace Service Oriented Architectures for eGovernment, implementing leading ESB stacks. ▪  Develop a SOA eGovernment platform. ▪  Independent SI, so we can asess the great value proposition in WS02 products.
  7. 7. Case Studies From Distributed systems to SOA. Help several public organizations to migrate from a Distributed Systems to SOA landscape. ▪ Radically improved capabilities, time-to-market, etc. ▪ Huge business case / value in SOA. ▪ Leading core eGov indicators and rankings nationwide..
  8. 8. Case Studies Interoperability. Help several public organizations to perform electronic exchange of documents, as opposed to paper-based exchange. ▪ This talk’s scope.
  9. 9. Case Studies Public Procurement – Auction! Public organizations buying goods where sellers bid to offer lowest price. ▪ All in digital format. ▪ Several MM€ bought through our platforms.
  10. 10. Business Problem statement Why did we do this?
  11. 11. Business Problem statement Paper-Based Exchange of information ▪ Citizens and companies to gather all documents from the different public organizations (or even the same). ▪ Public administrations to validate documentation and perform administrative business processes. ▪ Hundreds of thousands of paper documents for small to medium-size organizations. ▪ Public organizations are increasingly becoming digital.
  12. 12. Business Problem statement Interoperability in digital format – Use Case ▪ A citizen needs to perform a process with a Public Sector Organization (PS1). ▪ A document from a Third Party is required. ▪ Citizen agrees that interoperability can be used. ▪ PSO1 to request document to PSO2 on his/her behalf. ▪ Exchange happens in digital format. ▪ Data can now be used digitally – supports and fosters digital governments.
  13. 13. Business Problem statement Great (business?) benefits for all parties ▪ Citizens, private organizations, NGOs ▪ Public Organizations Applies also for departamental interoperability.
  14. 14. Business Problem statement Some elements in EU’s approach to interoperability ▪ The IDABC Programme (Interoperable Delivery of European eGovernment Services to public Administrations, Business and Citizens). 2005-2009. ▪ ISA (Interoperability Solutions for European Public Administrations), 2010-2015. ▪ European Interoperability Framework (EIF). Three dimensions ▪ Semantic ▪ Organizational ▪ Technical
  15. 15. Business Problem statement Some elements in EU’s approach to interoperability EU countries creating national interoperability frameworks to perform interoperability by digital means. ▪ Cross-country interoperability networks ▪ National-wide networks (Spain’s SARA) ▪ Public organizations plug-in into the networks and offer & use services.
  16. 16. Business Problem statement Semantic Dimension Ability of two systems to understand each other when defined by different organizations. ▪ Different sources, regulatory, mental models. ▪ Share data with unambiguous meaning. Avoid diverging interpretations of data. ▪ Doesn’t handle representation, but makes sure meaning travels with information. ▪ Usually involves handling metadata. ▪ Very (very) hard problem at an internet size – W3C semantic web. ▪ ISA joinup (osor.eu + semic.eu)
  17. 17. Business Problem statement Organizational Dimension Ability of Organizations and process to interoperate within their actuation scope. ▪ Legal dimension. What are the legal consequences of the data exchange? ▪ Entitlement. ▪ Agreements among PO.
  18. 18. Business Problem statement Technical Dimension ▪ A set of agreed upon norms and standards. ▪ Shared Schemas ▪ Web service invocation. ▪ Security: A&A. Non repudiation, integrity, etc. Credentials management. ▪ QoS ▪ Custody of records and audit ▪ Etc.
  19. 19. Powered by WSO2 A sample case – plugging one Public Organization into SARA
  20. 20. eGovernment solution
  21. 21. Powered by WSO2 WSO2 portfolio WSO2 provides an excellent product portfolio to address these situations. The basic pieces here being: ▪ WSO2 ESB ▪ WSO2 Governance Registry
  22. 22. Powered by WSO2 ALL is SOA patterns All integration scenarios handled by SOA patterns and infrastructure. ▪ WSO2 ESB runs integration sequences. ▪ WSO2 Governance Registry to perform resource management (i.e. WSDL).
  23. 23. Powered by WSO2 Basic integration sequence ▪ Authenticate client ▪ Sign request ▪ invoke ▪ Authenticate & validate response ▪ Log & Custody ▪ Generate reply ▪ Error handling
  24. 24. Integration Sequence Exchange sequence is parameterized in the ESB using Registry Elements
  25. 25. Integration Sequence Store all exchanged data with 0 lines of coding.
  26. 26. Greater Visibility See what happens in your network
  27. 27. Powered by WSO2 Conclusions ▪ Pattern based integration. ▪ Toolset to facilitate integration using parameterization. ▪ Greater capabilities / lower development / faster time-to- market as opposed to development.
  28. 28. Engage with WSO2 •  Helping you get the most out of your deployments •  From project evaluation and inception to development and going into production, WSO2 is your partner in ensuring 100% project success

×