eGovernment interoperability

eGovernment InteroperabilityWorld-wide initiatives and future research directions

Dr. Luis GuijarroAssociate ProfessorLecturer on Information SocietyE-Forum member

AgendaCurrent initiatives in e-GovernmentinteroperabilityAnalysisFuture reseach on e-GovernmentinteroperabilityIssues to address

E-Gov interoperabilityinitiatives

Timeline1996 1997 1998 19991999 2000 2001 2002 2003 2004

T. Carcenac, “Pour une administration

électronique citoyenne”

Cabinet Office “e-Government. A

strategic framework for public services in the

Information Age”

CIO Council,FEAF 1.1

1720/1999/EC, “Interoperability and

access to TEN for IDA”

Clinger-Chen Act“Information Management

Technology Act”

OMB “e-Government

Strategy

TODAY

E-Gov EA Guidance 2.0d

E-Envoy,e-GIF

e-GIF 4.0 e-GIF 5.0d

ATICA,CCR 1

CCR 2d

EC Enterpise DG,Architecture Guidelines 4.1 Architecture Guidelines 6.1


E-Government Interoperability FrameworkOffice of the e-Envoy (UK)Mandatory specifications and policies forjoined-up and web enabled governmentKey policies

Internet and web standardsBrowser interface for accessXML for data integrationMetadata for content management


Le Cadre Commun d’Intéroperabilité (CCR)Agence pour les TIC dans l'Administration(France)Recommendations for strengthening Publicelectronic systems coherence and forenabling multi-agency electronic servicedelivery


IDA Architecture Guidelines (AG)IDA (Interchange of Data betweenAdministrations) programme (EU)Concepts and reference for optimum inter-operablity between European Institutions, European Agencies, and Administrations in Member States


E-Gov Enterprise Architecture Guidance(EAG)

Federal Chief Information Officers Council(USA)Mandatory target conceptual architecture forFederal E-Gov programsSelected standards for consideration in E-Gov initiatives

Analysis and future directionsFramework

Two-phase interoperability roadmapEnabling the interoperabilityLeveraging the interoperability

First phase: definitionEnabling the interoperability

Interoperability is the ability to exchangefunctionality and interpretable data betweentwo software entities. It can be defined in terms of 4 enabling requirementes: communications, request generation, data format, and semantics.

Source: Mowbray (1995), The essential CORBA

E-GIFE-GIF 5 draft Specifications

Interconnection: IPv4, HTTP, S/MIME ...Data integration: XML, XSL, UML, RDFContent Management Metadata

XML and e-GMSAccess

DTV Internet, workstation, mobile phone, game console, PDA, smart card

CCRCCR 2 Standards

Interconnectivité: IPv4, FTP, S/MIME...Données: XML, XSLT, UMLFormat et supports: TIFF,MP3,XML,CGM...Les architectures applicatives: J2EE, RMI/IIOP...

IDA AGIDA AG 6.1 Service Profiles

Document archivingDocument exchangeContent interoperabilityWWWMiddlewareMessage transferFile transfer

Workflow managementDirectoryNetwork managementGroup workingCarrierTelecommunicationsWANSecurity

E-Gov EAGE-Gov EAG 2.0 draft Standards

Human computer interface servicesHTML, Symbian Epoc ...

Data interchange servicesWAP, J2EE, .NET, WS ...

Network servicesMIME, T.120, H.323...

Data management servicesJDBC, WebDAV ...

Security servicesS/MIME, SAML ...

First phase: analysisInternet and WWW technologies build theinteroperability framework coreTwo approaches:

OSI legacy: e-GIF, CCRPOSIX legacy: IDA AG, e-Gov EAG

Hereby, informationCAN seamlessly flow between InstitutionsCANNOT seamlessly flow for servicedelivery to citizens

First phase: future directionsGoal: Interoperability efficiency

Service interoperabilityWeb Services

• Service “description, discovery and integration”• Actors: W3C, OASIS

SemanticsSemantic Web

• Higher abstraction level for interoperability• Actors: W3C

Second phase: definitionLeveraging the interoperability

Build the enterprise architectureEnterprise architecture refers to a comprehensive description of all the keyelements and relationships that make up anorganizationAlignment between

• Business processes and goals• IS applications and middleware systems

Zachman Framework

e.g. DATA

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/SetsProc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business LocationLink = Business Linkage

e.g. Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. Technology Architecture

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g. Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

Source: Zachman Institute for Framework Advancement, <www.zifa.com>, as of July 2000

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGYENTERPRISE

e.g. Business Plan

E-GIFE-Services Development Framework

IDA AGInteroperability model

dimensions

E-Gov EAG

ArchitecturesModels

Second phase: analysisE-Gov initiatives are using tools provided by

Enterprise engineeringCIMOSA, PSL, EDOC

Software engineeringUML, Object-oriented Analysis and Design

Now, informationCAN seamlessly flow for service delivery tocitizens

Second phase: futuredirections

Goal: interoperability effectivenessPublic service modelling

FEAF Business Reference ModelChange management

Transition• from baseline architecture• to target architecture

Issues to addressIs technology a bottleneck fordeploying e-gov at myAdministration?

Which technology will speedmy transition to e-gov?

Can I know the processes atmy Administration?Am I ready for e-govtransition? May I manage thechange?