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 2010
1
Summary



LGAF: A Laboratory for applying Process Management in eGovernment
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
2
What is LGAF?


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
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.
2.
3.
4.
Enterprise Service Systems and Components
o
Enterprise Content Management System (E-CMS)
o
Business Process Management System (BPMS)
o
Identity Management System (IMS)
LGAF Interface
o
LGAF portal + ServicesPortal
Enterprise Service Bus (ESB)
Gateway to Legacy Applications

Municipal ERP

Document Registration

Municipal Family Registry
5
LGAF Architecture: Core Layers
BetaCMS|LGAFportal + LGAFServicesPortal (GWT)
Human Workflow Engine + LGAF
ServicePortal
BetaCMS-based webapps (portal, wiki)
OTA Executable Process Models
OTA Content Management Standards and
Models + Executable Templates
Business Process Management System
(Intalio|BPMS)
Enterprise Content Management System
(BetaCMS)
ESB (Mule)
core operations
OTA API (open to everybody)
core documents
WSDLs
Local ESB
OTA Legacy Systems
6
LGAF: Open Standards and Open Source
Software

Technology stack from a process management standpoint

Enterprise Content Management & Business Process Management(at the
center)
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
o




7
LGAF follows European Standards for EGovernment Services

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
8
LGAF and SOA

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
9
Business Process Model
Orchestration
10
Does LGAF have orchestration limits? Only
the sky! [see next page]


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



o
Credit and Debit Cards: Re-direction
E-banking
(Transaction Validation)
Example: micro-payments system

Re-direction to IPX payment page
11
Tax and Fines Payment: a Case of an opendesign process
Process “hides” behind an evolving
document evolution. In each step
document is enhanced with
information
related to the process.
Citizen
Fills
Description
Route
to the
the Tax
payment
way. Citizen
can pay:
Basic
components
to the •Credit
Appropriate
(mini
Portal).
CardForm
(LGAF
e-payment
tool)
•Initializer
•E- banking (LGAF e-payment
tool)
•Payer
•Micro payment (Ericsson)
is notified
about
the
•Payee Citizen
Employee
check the
validity
•Something Else…. Sub process:
payment
and if theIf validation
is is
•Taxstatus
Description
of payment
transaction.
the validation
positive
receives
the produces
receipt
•Payment
System
Vendorthe receipt
positive,
Back office
•Transaction
Details
number
of the payment
•Validation Details and Receipt
A unique
Citizen
is key
informed
that describes
About thethe
Final
payment
Amount.
Accepts
values
produced
not
Payment or non. The Tax is Registered in
Check ifisor
the
Taxthe
is Affiliated
Municipal BackOffice
12
Case: Recycling of Electrical Appliances
Request
Form
To do list Creation
If Item not collected the procedure
is repeated
Task Assignment to an employee or department. Set Collection Date, or do collect or fill a report
Notify Citizen about the status of the request
Registration
13
[Note for an advanced audience]
LGAF Process Modeling Framework (PMF)


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
14