management & technology consultants service-oriented architectures for e-government connecting...

Management & Technology Consultants

Service-Oriented ArchitecturesService-Oriented Architecturesfor E-Governmentfor E-Government

Connecting People and Public Services – The Irish Government’s SOA Initiative

Andrew S. TownleyMcLean, VA24-May-2006

© 2006 BearingPoint 2Management & Technology Consultants

Introductions

Andrew S. Townley

Principal ArchitectReach Public Services Broker


Agenda

Reach and its mission

Key project requirements

PSB technical overview

Lessons learned



Reach and its Mission


The Reach Agency

Established by Irish Government legislation in 1999 and 2000 to:

Develop a strategy for the integration of public services

Develop and implement the framework for electronic government

“To radically improve the quality of service to personal and business customers of Government and to develop and deploy the Public Services Broker to help agencies achieve that improvement”

“In particular Reach is to develop and implement an integrated set of processes, systems and procedures to provide a standard means of access to public services, to be known as the Public Services Broker (PSB)."

“To radically improve the quality of service to personal and business customers of Government and to develop and deploy the Public Services Broker to help agencies achieve that improvement”

“In particular Reach is to develop and implement an integrated set of processes, systems and procedures to provide a standard means of access to public services, to be known as the Public Services Broker (PSB)."

The Reach Mission:


Reach Governance

Social Security

Information Society

Public Service Reform

Governance Structures Cabinet Committee (chaired by PM) Secretary General Group

(permanent heads of Depts.) Assistant Secretary Group (CIOs) Reach Board (DSFA, Prime Minister,

Finance)

Governance Instruments Primary Legislation & Secondary Regulation Government Decisions Government (Prime Minister /Finance)

Circulars Funding decisions (Information Society Fund

& Annual Estimates) “Name & Shame” at Central Groups

Office of thePrime Minister

Department of Socialand Family Affairs

Department ofFinance

Reach


Reach Agency Objectives

Provide Standards & Regulations for e-Government

Develop and maintain a common data exchange format across agencies

Provide interaction policies and guidelines for agency service delivery

Establish the legislative and regulatory framework allowing service delivery

Provide Coordination & Leadership of e-Government Initiatives

Advance the e-Government program across the public service agencies

Coordinate and manage projects relating to e-Government service delivery

Devise the communications and marketing strategy for services offered by the PSB

Provide Implementation & Delivery of e-Government services

Procure the implementation of the PSB core architecture

Actively engage with public service agencies to deliver new services


Public Service Broker Objectives

Interoperability

Create a standards-based architecture

Define standardized, structured business documents

Common Service Catalogue

Provide shared access to services to both citizens and agencies

Centralize management and access control

Reusability

Services provide distinct business operations

Once deployed, services are available to authorized PSB users and agencies

Single Access Point

Centralized interface for both businesses and citizens

Visibility of pending service requests across all participating agencies


Technology Landscape, c.1999-2000

XML specification published (1998)

W3C XML Schema Working Group activity 1999-2001

Java enterprise computing takes off

JSP specification (1999)

J2SE v.1.3 (2000)

J2EE v.1.3 (2000)

Microsoft gets serious about the enterprise

Windows 2000/IIS 5/ASP 3 (2000)

COM+ combines COM/DCOM/MTS (2000)

C# and .NET framework (2000)

Web services platform starts to take shape

ebXML initiative starts (1999)

SOAP 1.1 released as W3C Note (2000)

WSDL 1.0 released (2000)

UDDI 1.0 released (2000)

Vendor Web Services toolkits become available (2000)


Pilot Projects (2001-2003)

Initial reachservices.ie portal

Initially launched in April 2002 with development started in 2001

Allowed individuals to self-register

Registration details verified against governmental databases

Provided initial point of access and government service taxonomy

Provided electronic forms delivery capabilities, but no forms delivered

Inter-Agency Messaging Service (IAMS)

Developed between 2002-2003 based on discussions in 2001

Proof-of-concept for the XML messaging broker

Provides delivery of life events between 3 government agencies

Initial cost of €81K with total expenditure < €200K for development

Delivers real business value reducing time of benefits payment receipt from 22 to 2 days


Reach Interoperability Guidelines (RIGs)

A set of documents intended to ensure interoperability of the PSB

Baseline

Intended to define the core interoperability architecture

Define the Reach XML Profile and Reach Canonical Form (RCF)

Define XML Namespace and W3C Schema profiles

Define Unicode, internationalization and versioning policies

Define a REST-style reliable messaging transfer protocol

Provide general service development guidelines

Define the structure of the Reach Envelope

Data Model

Define canonical XML elements for shared business data elements

Service Interface Protocols

Defines message exchange patterns and external policies for available services

For more information, see http://sdec.reach.ie

http://sdec.reach.ie/




Key Requirements for the PSB


Centralized Access to Public Services

Ubiquitous access

Self-service via Web, phone and kiosk

Assisted phone services

Assisted walk-in services

Automated interactions

Aggregated services

Unified status reporting

User-centric

Self-management of personal details

Targeted service delivery through personalization


Architectural Flexibility and Coherence

<XML/>

HTTPBTF

RPC

MQSeries SOAPJM

S


Identity Management for e-Government

CSCS

AACS – Credential ServiceAA – Agency Application

Reach ProjectScope



PSB Technical Overview


Logical Architecture


Architectural Layers

HTTP-based protocolboundary

reachservices.ieportal is just

another service


Messaging Infrastructure

Send a message Must be in a Reach Envelope

Put in “mailbox”

Asynchronous operation

Reach Envelope Source

Destination

Message type

Identities

Message ID

Message body

Receive a message Will be in a Reach Envelope

Retrieve from “mailbox”

Asynchronous operation

Send

Receive

<ReachEnvelope> <Version>1.7</Version> <MessageType Local=””>R1752</MessageType> <MessageSource Local=””>MXXX</MessageSource> <MessageDestination Local=””>M029</MessageDestination> <Identities> <Submitter>{TrustedHost-Principal}</Submitter> <Requestor Type=”MXXX”>{Local user name}</Requestor> <Subject Type=”PPSNo”>3853527D</Subject> </Identities> ... <Body> <R1752:PSI200FindIdentity xmlns:...> ... </R1752:PSI200FindIdentity> </Body></ReachEnvelope>


Example Service Request Message

<R1750:PSI500AuthenticationRequest xmlns:R1750="http://sdec.reach.ie/rigs/rigs/rig1750/v0_6/schemas"

xmlns:R0101="http://sdec.reach.ie/rigs/rig0101/v0_7/schemas“

xmlns:R0111="http://sdec.reach.ie/rigs/rig0111/v0_5/schemas"




xmlns:R0133="http://sdec.reach.ie/rigs/rig0133/v0_1/schemas">

<R0133:Reference>

<R0133:RequestDate>2005-02-10T09:00:00</R0133:RequestDate>

<R0133:RequestReference>qwerty</R0133:RequestReference>

<R0133:RequestLanguageContext LanguageCode="en" />

</R0133:Reference>

<R0101:PublicServiceIdentity PPSNo="1956525F">

<R0101:PersonIdentitySet>

<R0111:PersonName>

<R0111:FirstName Type="Forename1">RICHARD</R0111:FirstName>

<R0111:LastName Type="Surname">O'DONOGHUE</R0111:LastName>

<R0111:OtherName>

<R0111:LastName Type="MothersBirthSurname">MURPHY</R0111:LastName>

</R0111:OtherName>

</R0111:PersonName>

<R0101:AddressDetails Type="residential" Usage="ie.welfare.psi">

<R0114:Country>

<R0114:CountryCode>IE</R0114:CountryCode>

<R0114:CountryName>Ireland</R0114:CountryName>

<R0114:AdministrativeArea Type="County">

<R0113:AdministrativeAreaName Code="C" Type="ie.reach.sdec.CountyName">CORK</R0113:AdministrativeAreaName>

<R0114:Locality>

<R0114:AddressLine Type="Line1">2 MOURNE AVE</R0114:AddressLine>

<R0114:AddressLine Type="Line2">DILLONS CROSS</R0114:AddressLine>

</R0114:Locality>

</R0114:AdministrativeArea>

</R0114:Country>

</R0101:AddressDetails>

<R0115:PersonInfo>

<R0115:Sex>1</R0115:Sex>

<R0115:BirthInfo>

<R0115:BirthDate>1951-08-29</R0115:BirthDate>

<R0115:DOBVerified>true</R0115:DOBVerified>

</R0115:BirthInfo>

</R0115:PersonInfo>

</R0101:PersonIdentitySet>

</R0101:PublicServiceIdentity>

</R1750:PSI500AuthenticationRequest>

Document-oriented Message includes all

necessary context

Generated by requestor agent based on user input

Self-describing Each element in schema

Full URI of XML schemas

Modular & versioned Element re-use from 6

separate schemas

“Tied together” by RIG1750

Full versioning of each separate schema

RIG0101:PublicServiceIdentity

RIG0114:Country

RIG0113:AdministrativeAreaName

RIG0115:PersonInfoRIG0115:PersonInfo

RIG0133:Reference

RIG0111:PersonName


Complete Response Message

<R1751:PSI500AuthenticationStatus










xmlns:R1751="http://sdec.reach.ie/rigs/rig1751/v0_6/schemas">

<R0133:Reference>

<R0133:RequestDate>2005-02-10T09:00:00</R0133:RequestDate>

<R0133:RequestReference>qwerty</R0133:RequestReference>

<R0133:RequestLanguageContext LanguageCode="en"></R0133:RequestLanguageContext>

</R0133:Reference>

<R1751:Status>

<R1751:StatusCode>1.5001</R1751:StatusCode>

<R1751:StatusComment>Identity Confirmed</R1751:StatusComment>

</R1751:Status>

<R1751:PSISent>



<R0111:PersonName>

<R0111:Title></R0111:Title>


<R0111:FirstName Type="Forename2"></R0111:FirstName>

<R0111:MiddleName Type="OtherForenames"></R0111:MiddleName>


<R0111:Suffix></R0111:Suffix>

<R0111:OtherName>


</R0111:OtherName>

<R0111:FormerName Type="BirthSurname">

<R0111:LastName Type="Surname"></R0111:LastName>

</R0111:FormerName>

</R0111:PersonName>


<R0114:Country>


<R0114:CountryName>Ireland</R0114:CountryName>



<R0114:Locality>



<R0114:PostalCode></R0114:PostalCode>

</R0114:Locality>


</R0114:Country>


<R0101:AddressDetails Type="correspondance" Usage="ie.welfare.psi">

<R0114:Country>


<R0113:AdministrativeAreaName Code="" Type="ie.reach.sdec.CountyName"></R0113:AdministrativeAreaName>

<R0114:Locality>

<R0114:AddressLine Type="Line1"></R0114:AddressLine>


</R0114:Locality>


</R0114:Country>


<R0115:PersonInfo>

<R0115:Sex>1</R0115:Sex>

<R0115:BirthInfo>



</R0115:BirthInfo>

<R0115:DeathInfo></R0115:DeathInfo>

<R0123:Nationality>IE</R0123:Nationality>

</R0115:PersonInfo>



</R1751:PSISent>

<R1751:PSIReturned>



<R0111:PersonName>

<R0111:Title>MR</R0111:Title>


<R0111:FirstName Type="Forename2"></R0111:FirstName>

<R0111:MiddleName Type="OtherForenames"></R0111:MiddleName>


<R0111:Suffix></R0111:Suffix>

<R0111:OtherName>


</R0111:OtherName>

<R0111:FormerName Type="BirthSurname">

<R0111:LastName Type="Surname"></R0111:LastName>

</R0111:FormerName>

</R0111:PersonName>


<R0114:Country>


<R0114:CountryName>IRELAND</R0114:CountryName>



<R0114:Locality>




</R0114:Locality>


</R0114:Country>


<R0101:AddressDetails Type="correspondance" Usage="ie.welfare.psi">

<R0114:Country>


<R0113:AdministrativeAreaName Code="" Type="ie.reach.sdec.CountyName"></R0113:AdministrativeAreaName>

<R0114:Locality>

<R0114:AddressLine Type="Line1"></R0114:AddressLine>


</R0114:Locality>


</R0114:Country>


<R0115:PersonInfo>

<R0115:Sex>1</R0115:Sex>

<R0115:BirthInfo>



</R0115:BirthInfo>

<R0115:DeathInfo></R0115:DeathInfo>

<R0123:Nationality>IE</R0123:Nationality>

</R0115:PersonInfo>



</R1751:PSIReturned>

</R1751:PSI500AuthenticationStatus>


End-to-end Message Delivery

Integration FrameworkRequestor Agent Provider Agent


Canonical Service Agent Architecture

BusinessProcess

Logic

ServiceActivator

MessageTransferProtocol

MessagingGateway

WS-BEPLProprietary process language

Custom code

JMS APIMSMQ API

RM4GS/JCAApache Sandesha

freebXMLJBI Binding Component

WS-ReliabilityWS-ReliableMessaging

ebMSBTF

RRMTPIIOP

.NET Remoting

WebLogic IntegrationBizTalk Server Engine

Message-driven EJBSession EJB

JBI Service EngineCustom code


PSB Identity Management Communities

Enforced separation of concerns

Personal users cannot directly send messages

Agency fulfillment users cannot access personal services

Independent identity proofing

Maximum registration level dependent on community

Identity proofing process tailored to each community

Identity Assertion

Combination of registration level and authentication level

Attempts to account for the integrity of the access channel

Agency Service Fulfillment Users

Integration Framework Principals

reachservices.ie Personal Users


Service Access Control

IDMACS Access Check

PSB Service

Principal Service UI

XML

ServiceRequest

Agency Service

1. Can the principal access the URI?

2. Can the principal send messages to the service?



What We’ve Learned So Far


When to Use “Standards”

If they are sufficiently mature

Can be based on individual assessment or vendor implementations

You understand the parts that are missing or broken

The fundamental aspects are not under revision

Just because a specification is published doesn’t make it a standardJust because a specification is published doesn’t make it a standard

If they fit the problem you’re trying to solve

Pay attention to the 80/20 rule

Does the benefit justify the cost?

Technology and specifications are notare not in the driver’s seat

Everything should be made as simple as possible, but no simpler– Albert Einstein


Technology Operational Costs

Allow incremental adoption based on ROI for the participants

No more “big bang” deployments

SOA means as long as you do the what the how isn’t as important

Pay attention to licensing and upgrade costs

Understand your platform and deployment constraints

Be prepared for unexpected adoption rates that could affect TCO

Minimize assumptions and dependencies

Service implementations should be “black boxes”

Just because a service is deployed here today doesn’t mean it won’t be deployed in another environment tomorrow

Monitoring, diagnosis and manual intervention is critical

Operations needs consistent, accurate views of the running system

Don’t forget about “priority manual intervention” and build in the mechanisms


Interoperability

It’s about the messages

Identify the fundamental information used by a business process

The data will be around a lot longer than the systems that process it

Specify the essentials, let the rest vary

Core data elements and their meanings

Reliability constraints

Invocation interface

Think “the Internet”

Embrace loose coupling

Tools, technologies and techniques are generally transient

Isolate the moving parts—hide them behind standardized interfaces

Minimize centralized control—let the participants own their processes


Engagement with Government Agencies

Don’t underestimate organizational dynamics

Each agency has a unique personality and way of doing things

Encourage collaboration, not mandatory adoption of “one true way”

“You can lead a horse to water…”

Set realistic expectations

Early adopters will likely bear the brunt of the costs

ROI will be incremental, and generally not immediate

Spell out data and process ownership, reconciliation and failure recovery scenarios

Offer added value

Federated identity management provides access to registered user base

Auditing, logging and non-repudiation of message exchanges

Offer incremental adoption

Agency capabilities are not all equal

Essential to deliver capabilities to the SOA quickly and cost-effectively


Service Implementation

Build the right levels of abstractions

Easy to make services too fine-grained

Don’t worry about details not relevant to what the service does

Strive for portability

Design and build for change

Well-defined interfaces between business logic and message transfer

Strive for cost-effective scaling

Scale out, not up

Minimize statefulness

Don’t accidentally depend on tools and capabilities you don’t really need

Build a service, not an application

The service should be generally useful, not tied to a given requestor


Further Information

The reachservices portal: http://www.reachservices.ie/

The Services and Data Exchange Catalog (SDEC): http://sdec.reach.ie/

PSB Service Design Guidelines, rig0019: http://sdec.reach.ie/rigs/rig0019/

The Reach Envelope, rig0100: http://sdec.reach.ie/rigs/rig0100/

RRMTP, rig0007: http://sdec.reach.ie/rigs/rig0007/

PSB requirements and tender documents: http://www.reach.ie/procurement/

Inter-Agency Messaging Service information: http://www.reach.ie/iams/

EU e-Government case study #625 on REACH IAMS (2003): http://unpan1.un.org/intradoc/groups/public/documents/other/unpan022024.pdf

http://www.reachservices.ie/


http://sdec.reach.ie/rigs/rig0019/



http://www.reach.ie/procurement/

http://www.reach.ie/iams/

http://unpan1.un.org/intradoc/groups/public/documents/other/unpan022024.pdf

management & technology consultants service-oriented architectures for e-government connecting...

Documents

government services

public service agencies

public services broker

egovernment reach

egovernment service

public services broker

government service taxonomy

integration of public