Local Government Access Framework (LGAF)

roomagitatedInternet και Εφαρμογές Web

8 Δεκ 2013 (πριν από 3 χρόνια και 11 μήνες)

47 εμφανίσεις

1


LGAF Project
:


e
-
Gov Applications Development

(or how to integrate different application flavors in a
consistent, open
-
ended, value stream)












http://lgaf.kedke.org/wiki

Athens
,
Greece

March
20
1
0



LGAF: A Laboratory for applying Process Management in e
-
Government


LGAF: SOA Architecture


LGAF: Technology


E
-
CMS and GWT


BPMN
-

BPMS


Web Services


Application Development with BPM: Cases


MUN: Taxes and Fines Payment


MUN: Recycling of Electrical Appliances


Summary


2


LGAF = Local Government Access Framework (Project for “Coordination
of Local Government Authorities” /
ΚΕΔΚΕ
)


LGAF is a platform


Supports Online Services to:

o
Local Citizens
(
e.g. Family Record Certificates, Municipal Tax Payments,
Recycling of Electrical Appliances etc)

o
Business (e.g. Municipal Tax Payments)


Establishes online task management of the activities related to online services delivery

o
Public Employees


LGAF mission


Defines a framework for
digitizing e
-
gov

services
provided by Local Government
Authorities through
the automation of business processes

o
Enterprise Technologies
-
based Content Management

o
Business Process Modeling and Execution

o
Data components Modeling and Document Modeling

What is LGAF?


3

LGAF Architecture in detail:

a two parts system



4

+

LGAF Architecture: Core Principles and
Core Components


Core Principles


Design Impetus: Operate as an Open Platform (SOA)


Working Model: Software
-
as
-
a
-
Service (
SaaS
)


Core Components

1.
Enterprise Service Systems and Components

o
Enterprise Content Management System (E
-
CMS)

o
Business Process Management System (BPMS)

o
Identity Management System (IMS)

2.
LGAF Interface

o
LGAF portal +
ServicesPortal

3.
Enterprise Service Bus (ESB)

4.
Gateway to Legacy Applications


Municipal ERP


Document Registration


Municipal Family Registry




5

LGAF Architecture: Core Layers


6

BetaCMS|LGAFportal

+
LGAFServicesPortal

(GWT)

Human Workflow Engine
+
LGAF
ServicePortal

OTA Executable Process Models

Business Process Management System
(
Intalio|BPMS
)

Local ESB

WSDLs

core operations

core documents

OTA Legacy Systems

OTA Content Management Standards

and
Models + Executable Templates

Enterprise Content Management System
(BetaCMS)

OTA API (open to everybody)

BetaCMS
-
based webapps (portal, wiki
)

ESB (Mule)


Technology stack from a process management standpoint


Enterprise Content Management & Business Process Management
(at the
center)

o
E
-
CMS: BetaCMS

o
BPMS: Intalio|BPMS

o
GWT
-
based Interface for Process Participants (all interactions through a
single UI)


Enterprise Service Bus
(at the frontier)

o
Mule ESB


Enterprise Service Bus (at the Municipality level)

o
Mule ESB
(could be anything else)


Data Transferring
(inside and outside)

o
Web Services (SOAP Services)



Data Modeling

o
XML Schemas

LGAF: Open Standards and Open Source
Software


7


European Interoperability Framework


Defines SOA as the proposed architecture


Use XML for Data Modeling And Transferring


Three layers of Interoperability

o
Organizational

o
Semantic

o
Technical


Greek e
-
GIF (e
-
Government Interoperability Framework)


Process Modeling, Reusable Business Services


Code Lists, Core Data Components, Data Types

LGAF follows European Standards for E
-
Government Services


8



LGAF applies SOA principles


Everything is
a service (ESB
, processes, IAMS, E
-
CMS, BPMS),
described through WSDL


Data exchange format in XML. SOAP is used for supporting data
exchange. Data modeling is performed with XML Schemas


Loose coupled services (e.g. Municipal Portion Service) using the
ESB


The BPMS Layer performs the orchestration of third systems (legacy
apps etc.) and humans (participants) to create Composite Services
and Applications


LGAF and SOA


9


10

Orchestration

Business Process Model

Does LGAF have orchestration limits? Only
the sky!
[see next page]


11


LGAF is a core of OS technologies “at the center


Open to integrate, at the “periphery”, with vendor or OS


Third
-
party Systems


Applications

o
Example: document management system

o
Example: fines collection system (PDA
-
enabled)

o
Example: e
-
payment systems


Credit and Debit Cards: Re
-
direction


E
-
banking


(Transaction Validation)

o
Example: micro
-
payments system


Re
-
direction to IPX payment page

Tax and Fines Payment: a Case of an open
-
design process


12

Citizen Fills the Tax Description

to the Appropriate Form (mini Portal).

Check if the Tax is Affiliated or non. The Tax is Registered in
Municipal BackOffice

Citizen is informed About the Final Amount.

Accepts or not the Payment

A unique key that describes the payment
values is produced

Route to the payment way. Citizen can pay:


Credit Card (LGAF e
-
payment tool)


E
-

banking (LGAF e
-
payment tool)


Micro payment (Ericsson)


Something Else….

Sub process: Employee check the validity
of payment transaction. If the validation is
positive, Back office produces the receipt
number of the payment

Sub process: Citizen is notified about the
payment status and if the validation is
positive receives the receipt

Process “hides” behind an evolving
document evolution. In each step
document is enhanced with
information related to the process.
Basic components


Initializer


Payer


Payee


Tax Description


Payment System Vendor


Transaction Details


Validation Details and Receipt

Case: Recycling of Electrical Appliances


13

Request
Form

Registration

Notify Citizen about the status of the request

Task Assignment to an employee or department. Set Collection Date, or do collect or fill a report

To do list Creation

If Item not collected the procedure
is repeated


Business Process Modeling Notation (BPMN)


Business Process Modeling in 3 stages


Stage 1: Understanding the sequence of activities which compose the
business process (as


is)


Stage 2: Enhance the model with participants/roles and “service” from
third systems (contains horizontal and vertical abstractions). Define
re
-
usable processes. The BMPS layer orchestrates all participants
and systems (to


be)


Stage 3: The model is enhanced with “execution details” and data
mapping. It produces executable “BPEL code” which runs over the
BPMS engine

[Note for an advanced audience]

LGAF Process Modeling Framework (PMF)


14