fp5 ist egov project presentation at the french prime minister cabinet in 2002

French PM Cabinet Paris 15 November 2002

Dr. Efthimios Tambouris

Archetypon S.A.

An Integrated Platform for Realising Online One-Stop Government:

The eGOV project

French PM Cabinet Paris 15 November 2002 2

The eGOV Team

Dr. Efthimios Tambouris

e-Government Unit Manager, Archetypon S.A.

Mr. John Malone

CEO, Archetypon International

Mr. Frederique Loeurng

Project Officer, European Commission


Presentations and demonstrations

Project Overview

Our Conceptual e-Government Framework

Project Organisation and Management

Technical Approach

Use Scenarios and Slides Demonstrations


Project Fact Sheet

Name: An Integrated Platform for Realising Online One-Stop Government

Contract: IST-2000-28471

Duration: 24 months

Budget: 4,782,211 €

EC Funding: 2,500,000 €

Person Months: 468.2

Web Site: www.egov-project.org; www.egovproject.org (available in English, German, French and Greek)

E-mail: [email protected]

http://www.egov-project.org/



http://www.egovproject.org/


The Consortium

• IKV ++

• Archetypon S.A.

• NCSR ‘Demokritos’

• Ministry of Interior, Public

Admin & Decentralisation

• Municipality of Amaroussion

• Siemens • University of Linz • Ministry of Public service and Sports • Federal Computer Center • IDHEAP

• Tieto Enator

PO: Frederic Loeurng

• Beijing?


Archetypon S.A. and e-Government

Archetypon:

A Hellenic, independent IT company

Stable rhythm of growth (from 35 to 150 employees in the last 5 years)

International Market focused (customers: Microsoft, IBM, Siebel, European Commission…)

Activities: e-Government, e-Solutions, S/W engineering & testing factory, multi-lingual content, digital media, telecoms, consulting.

e-Government Unit:

Coordination of IST EURO-CITI and eGOV projects

Initiator and partner in IST SmartGov project

Many scientific publications

Members act as Team Members in CEN and Dublin Core-GOV Working Group.

Members act as peer-reviews in significant e-government workshops and conferences e.g. EGOV conference (within DEXA), KMinGOV, e-government track within Bled e-commerce conference etc.

Members act as thinks tank members, consultants, experts etc. in a number of projects, panels, groups etc.


To specify and develop the eGOV integrated one-stop government platform which consists of the following major building blocks:

Portal platform

Service Repository and Service Creation Environment

GovML as the connecting ‘glue’

To develop public services using the Service Creation Environment

To deploy and evaluate the platform in three countries (Austria, Greece, Switzerland)

To investigate relevant process models

To disseminate and exploit the project’s results

Project Objectives


e-development in context

Political System

Administration

Citizen

Business

Formulate Public Policy

B2B

e-democracy e-government

(G2B)

e-government

(G2C)

e-commerce

G2G

G2E


e-government

is e-business of the state

hence practices and experiences from e-commerce might be applicable to e-government

but e-government and e-commerce have significant and considerable differences!

Some differences with significant impact in IT & consulting projects:

Law (the private sector is free to do anything except what is explicitly forbidden by law while the public sector cannot do anything unless it is explicitly legislated)

Mission (the public sector does not chose its “customers” and has to be concerned about the limitation of exclusions and digital divide)

e-government and e-commerce


e-government domain characteristics

Design-for-all

Compatibility with ISO 13407 and the international templates of W3C (Web Accessibility Initiative) that have recently been adopted by the EU.

Design according to the Citizen's needs

A Human-centric model of service provision based on life events.

Interoperability

Adoption of open templates and architectures (Web Services, XML).

Maturity level

Materialization of solution in all levels (Information, offering of electronic forms, support of bilateral communications, transactions).


e-government: Planning for change

There must be visible and committed leadership within both the political and administrative arms of government.

There must be the right infrastructure and implementation programme, with clear accountability for results.

There must be a clear policy statement, set deliverables and a timetable.

There must be a framework for an authentic e-government strategy.


Level of Sophistication of e-government services

The EC has proposed a four-stages framework:

Stage 1 - Information: online information about public services

Stage 2 - Interaction: downloading of forms

Stage 3 - Two-way interaction: processing of forms, including authentication

Stage 4 - Transaction: case handling; decision and delivery (payment)

In addition to those, in the USA a fifth stage has been proposed:

Stage 5 - Integration: services integration based on users needs


Governmental Web Presence: Website vs. Portal

Website Portal Basic homepage Homepage organised by

customer groups/interests

List of agencies List key services

Mainly static information Information and Interactions

Some transactions Transaction rich

Organised by agency Organised by used needs

Often stand-alone to IT Fully integrated to IT systems

Weak customer support Full customer support

Source: Accenture, 2001


The Ultimate e-government realization: One-Stop Government

Definition:

The integration of public services from a customer’s (citizen or business) point of view.

Characteristics:

Services must be integrated (technological and organisational challenge)

The integration must follow citizens needs (human, technical and organisational challenge)

Life-events and business-episodes as guiding metaphors for integration:

The life-event concept: Life-events describe situations of human beings where public services may be required.

The business-episode concept: Business episodes describe topics of companies and self-employed citizens that may trigger public services or interactions with public authorities.


Human centered Service Provision

From a model based on the internal organization of the Public Sector to a model based on the needs of the citizen

Municipality

Directorate of Urban Planning

Directorate of Technical Service

Directorate of Citizenship

Ministry of the Interior

Tax Office

CITIZEN

BIRTH

SCHOOL

WORK

HEALTH

TRAVEL

MARRIAGE

PENSION

DEATH


Service Provision Model

PORTAL ΣΥΣΤΗΜΑ ΠΑΡΟΧΗΣ

ΥΠΗΡΕΣΙΩΝ ΚΑΙ ΠΕΡΙΕΧΟΜΕΝΟΥ

G2G

System for Providing

Services and Content and for

Coordination Activities

Each channel has its own system for

connection with the back-office


Project Scope

Scope:

Portal

Mid-office

Integration with back-office and channels

Out of scope:

Back-office automation

Implementation of communication channels


eGOV Conceptual Model

Life-event

eGOV Composite

Service

Public Content

eGOV Elementary

Service

Back-office process

Public Service

Metadata

Content eGOV Elementary

Service

eGOV Elementary

Service


eGOV Layered Architecture

Service A

Citizen

Service B

Service Implem.

Element. Service Public

Service

Public Service

Public Service

Life Event

Service Implem.

Element. Service

Composite Service

Public Authority 2

Public Authority 1

Mid-office Portal

Public Authority responsible for one-stop government

Back-office


Main Benefits of eGOV Approach

Benefits to citizens and businesses:

Invocation of integrated public services based on the life-event

concept

Invocation of individual public services

Benefits to public authorities:

eGOV services may be re-used in many different life-events

Existing automated public services can be provided to the

citizens through the eGOV platform

Automated as well as non-automated public services can be

integrated in the eGOV platform

The eGOV conceptual model is implemented based on standards and state of the art technologies (XML, RDF, UDDI, WSDL, SOAP, etc.)


Project Overview


Technical Approach




Project structure – Gantt Chart

Workpackage name 01 02 03 04 05 06 07 08 09 10 11 12

Year 1

13 14 15 16 17 18 19 20 21 22 23 24

Year 2

WP0.1. Project Management

and Coordination

WP1.1. Specification of Portal

and Network Architecture

WP1.2. Specification of Services and

Investigation of Process Models

WP2.1. Implementation of the Network

Architecture and the eGOV Portal

WP2.2. Implementation of the SCE

and the Service Repository

WP2.3. Implementation of GML

Syntax and Filters

WP2.4. Development of the eGOV

Process Models

WP3.1. Integration and

Trials Configuration

WP3.2. Trials evaluation

M2

D021

D111

D121

MilestonesM5

D211

D221

D231

D241

Deliverables

M6

D311

D312

M7

D321

D032

D022

D012

D031 D011

WP0.2. Dissemination and Exploitation

WP0.3. Assessment and Evaluation

M1 M3 M4


Achievements so far (1/2)

Technical Achievements

Citizens, Businesses, and Public Authorities Requirements gathered using questionnaires including online ones

Specifications of eGOV Portal, Network Architecture and services derived

Process Models at participating local authorities surveyed

Implementation of Portal nearly completed

Implementation of the network architecture (SCE, SR,STT,SDT) nearly completed

Implementation of GovML filters nearly completed

GovML data and metadata vocabulary almost finalised

Contribution to standards (GovML presentation at CEN)

Process Models and re-engineering methodology developed

Necessary commercial software products determined


Achievements so far (2/2)

Managerial Achievements

Firm management, coordination and quality processes in place

Creation and maintenance of the project’s Web site in four

languages (English, German, French and Greek)

Creation of dissemination material (A3-size and A4-size folder,

poster, “briefcase”)

Participation in numerous events

Several scientific publications in conferences and journals

Several companies/universities expressed their interest to join

the eGOV consortium

Potential products identified and initial exploitation and use plan

constructed


Dissemination and Promotion Activities

Elaboration of websites http://www.egov-project.org; http://www.egovproject.org in

English,

French,

German and

Greek

Creation of promotional material (leaflets, briefcase) in several languages




http://www.egovproject.org/


Scientific Publications / Standardization

Partners organise workshops and present eGov results at all relevant conferences. - participation in 23 events - 10 scientific publications

GovML is the eGOV contribution towards the international standardisation bodies. A presentation at CEN (European Committe for Standardization) has already been made.


Project Overview


Technical Approach




Technical Objectives

Portal

To specify and implement the Life-Event Portal

Network architecture

To specify and implement the Service Creation

Environment (SCE) and the Service Repositories (SR)

GovML

To implement the GovML syntax and filters

Process Models

To develop the eGOV process models and re-

engineering methodology


Overview of the Technical Architecture

Life Event Portal

INTERNET

Service Repository

Service Runtime Environment

Service Creation Environment

Service Repository



eGOV Middleware eGOV Middleware

Access through multiple devices

The eGOV platform consists of:

The Life Event Portal, deployed in one public authority responsible for one-stop government

The eGOV Middleware, deployed in all participating public authorities


eGOV components: Life Event Portal

Main functionality of the life event portal consists of:

Authentication

User registration

Personalisation

Service invocation

Content retrieval

Multilinguality

Wireless support

Metadata management

and query invocation

Portal

result Service Description

Service Description

Content Meta Data Description Service

Meta Data Description

Service Request

Service Response

Service Repository

Service Runtime

Environment Content

Repository

UDDI SIR


eGOV components: SCE, SRE and SRs

Main functionality:

Incorporation of service

implementations

Web service creation

Definition of service flow

Service description

Service publishing

Managing service flow

Service tracking

Elementary Service

Interface

Service Metadata

Service & Content Repository


Us

er

I/F

Service Description Tool

Web Service Creation Environment

Service Requestor I/F Service Admin I/F


Service Requestor

(Portal)

Service Management

Elementary eGOV

Services Composite eGOV

Services

Basic eGOV

Services

STT ESI SDC ASL


GovML Data vocabulary:

Three XML vocabularies for describing the structure of information about public services:

General description of Public Services

General description of Life Events

Specific description of Public Services

GovML Metadata vocabulary:

Metadata element set (application profile) based on Dublin Core

Implements RDF schema specification

eGOV components: GovML

GovML documents

General description

Specific description

Public Services

Life Events

XML XML

XML

Metadata Element Set


General Description vocabulary

Element Element 1 Title 11 Attention

2 Description 12 Periodicity

3 Language 13 Time to deliver

4 Related Services 14 Cost Information

5 Audience 15 Service Hours

6 Public authority type 16 Employee Hints

7 Eligibility 17 Citizen Hints

8 Required Documents 18 FAQ

9 Procedure 19 Result

10 Law

General description data vocabulary for public services

Element 1 Title

2 Description

3 Language

4 Related Services

5 Law

General description data vocabulary for life-events


Specific Description vocabulary

Element Element 1 Title 14 Cost

2 Description 15 Cost Information

3 Language 16 Service Hours

4 Public Authority name 17 Contact Details

5 Public authority department

18 Employee Hints

6 Required Documents 19 Citizen Hints

7 Electronic Documents 20 FAQ

8 Eligibility 21 Service Code

9 Procedure 22 Level of automation

10 Attention 23 Public authority address

11 Delivery channel 24 State

12 Periodicity 25 Name of service

13 Time to deliver

Specific description data vocabulary for public services


Production of GovML documents


Service Repository

XML storage mechanism

GovML (XML)

GovML (XML)


GovML metadata element

RDF schema

The core of GovML metadata element set is Dublin Core

Elements of EGMS, PRISM have also been used

Element Metadata standard 1 Title Dublin Core

2 Creator Dublin Core

3 Subject Dublin Core

4 Publisher Dublin Core

5 Date Dublin Core

6 Type Dublin Core

7 Format Dublin Core

8 Language Dublin Core

9 Relation Dublin Core

10 Coverage Dublin Core

11 Audience EGMS

12 Has Translation PRISM


eGOV components: Process Models

Homogenised terminology and integrated service modelling

Consists of

Public services

Process steps and primary

services

Portal

Front-office

M a

p

p i n

g

Life-event / business situation

Processes

have

Consists of

Back-office


One-stop Process Models: Example

Example of an integrated process model (abstract level) for the public service “marriage at the civil office”

Process flow describes the tasks of the citizen at the portal layer and the interaction with the back-office of the respective PA


Technologies & Deployment Platform

eGOV Middleware

eGOV Portal

• BEA WebLogic Application Server

• BEA WebLogic Portal Server

• IONA XML bus

• WOKUP Mobile Extensions

• BEA WebLogic Application Server

Content Directory

• Profium SIR • Protégé

Service Directory

• SUN UDDI

Service Repository

• Oracle 8i

Service Description

Tool

Service Tracking

Tool

ESI SDC ASL GovML Filters GovML

GovML

Portal Applications (Portlets)

Web Services

WSDL/SOAP

XML/XSLT

J2EE

RDF

UDDI

SR API Technologies used

Products & Tools

eGOV Implementation

• ADONIS Modeling Tool



Project Overview


Technical Approach



Use scenarios

Use Scenario 1: eGOV Portal (citizen’s point of view)

Use Scenario 2: eGOV Service Lifecycle (public authority’s point of view)


Use Scenario 1

eGOV Portal (citizen’s point of view)

eGov Portal

Authentication SIR UDDI Actual content Actual service

Life-events

Marriage

We are going to get married!

Where could we find information

and help with our problems and

arrangements?

•How do we get hold of information?

•Is it worth the effort to register?

•How do we do it?

Looks good! But…

Now we are in!

Where could we find information

concerning our situation??

…so about getting married…

Here we start digging for

information…

Useful information and hints!!

Could it be possible to make

some arrangements as well?


Use Scenario 2

eGOV Service Lifecycle (public authority’s point of view)

A new public service to eGOV portal

SD CD

2. Service

description

3. Portal for citizens

1. Service creation

and run-time

/**

* Constructor.

*

* @param regQueryUrl Query Url to Registry component, optional: could be given

in property, @see EgovRegistry

* @param regHttpProxyHost Proxy Host (if beyond firewall) to Registry component, optional:

could be given in property,

* @see EgovRegistry

* @param regHttpProxyPort Proxy Port (if beyond firewall) to Registry component, optional:

could be given in property,

* @see EgovRegistry

* @exception EgovException If bad arguments or logger initialisation fails

* @see EgovException

*/

public EgovWSClient(String regQueryUrl, String regHttpProxyHost, String regHttpProxyPort) throws

EgovException

/**

* Gets the wsdl url and access point url of a Service and it's service id.

* Only one fetch from UDDI needed.

* <br/> A. Service name match: Only partial match needed.

* <br/> B. Service id match: Perfect match needed.

* <br/> Final match is logical AND operation between A and B.

*

* @param serviceName Service name

* @param serviceId Service id

* @return String array, 0: WSDL Url, 1: Access Point Url

* @exception EgovException If service failed


*/

public synchronized String[] getWsdlAndAccessPointUrls(String serviceName, String serviceId)

throws EgovException

/**

* Retrieves the data from url.

*

* @param url Url as String

* @return Data from url as String

* @exception EgovException If service failed.


*/

public String getData(String url) throws EgovException

/**

* Connect to service.

*

* @param url Access Point Url as String

* @param params Paramters for the service and SOAP parameters

* @return Xml Response Message as String

* @exception EgovException If service failed.


*/

public String connectToService(String url, String params) throws EgovException

/**

* Convert to string.

*

* @return String String representation of object

*/

public String toString()

1. Create service

• process modelling

• service implementation

• Web service creation

SD

2. Create service decription

• specific description

• general description

SR

3. Create service metadata

• metadata model

• service metadata

…

Life Event

...

...Marriage

Resource

Civil

MarriageReligious

Marriage...

CD

4. Invoke eGOV service

CD SD


Demonstration



SDT - Login


SDT - Welcome


SDT - Service Description Manager


SDT - Edit Page and Workflow


SDT - Service Description Manager Search


SDT - Content Manager


SDT - Content Manager Edit Page and Workflow


SDT - User Manager List


SDT - User Manager Edit


Thank you for your attention!

Questions/Comments?

fp5 ist egov project presentation at the french prime minister cabinet in 2002

Presentations & Public Speaking