24
Connected Government Reference Architecture Connected Reference Architecture Webinar Series Nuwan Bandara Senior Lead, Solutions Architecture @nuwanbando 03/04/2015

Connected Government Reference Architecture

  • Upload
    wso2

  • View
    730

  • Download
    2

Embed Size (px)

Citation preview

Page 1: Connected Government Reference Architecture

Connected Government Reference Architecture

Connected Reference Architecture Webinar Series

Nuwan Bandara

Senior Lead, Solutions Architecture @nuwanbando

03/04/2015

Page 2: Connected Government Reference Architecture
Page 3: Connected Government Reference Architecture

Problems in Government ProcessorsPaper based processes

Cost of in-person service

Silo’d systems & data

Fraud detection and Prevention

Avoiding contradictions between different levels of authorities

Longer processes due to missing some automation

Not using the “known” data, documents

No transparency to the process and states

“Citizen Centric” mindset

Page 4: Connected Government Reference Architecture

Stakeholders

central government

state / local government

citizens state agencies private sector

Page 5: Connected Government Reference Architecture

Connected government modelsCentrally owned and managed

Centrally owned, but locally managed

Locally owned and managed

Page 6: Connected Government Reference Architecture

What does the stakeholders need

Data

Applications

Services

Workflows

Rules

Policies

Page 7: Connected Government Reference Architecture

Needs into perspective

Citizen portal

Employee applications

Dashboards for CxOs (the elected members)

Automated tasks / jobs

Document repositories

Reports

APIs

SMS / IVR based applications

Sensors

Accessibility

Security

Scaleability

Privacy

Reliability

functional

quality of services

Page 8: Connected Government Reference Architecture

Devices & servicesInfrastructure devices sensors and services connecting to the private

government cloud

Page 9: Connected Government Reference Architecture

Protocols & Data formatsMainframe / COBOL

SOAP / XML over HTTP

JMS / message queues

Fat files / Files over FTP

REST / JSON over HTTP

Custom binary protocols (infrastructure sensors)

Page 10: Connected Government Reference Architecture

InteroperabilitySolving interoperability through a connected bus architecture

Page 11: Connected Government Reference Architecture

Data fedaration & mediationLocal government data

Private & public institutional data

Federal data

Citizen data

Infrastructure data

Consolidated / aggregated data views

Page 12: Connected Government Reference Architecture

Data fedaration & mediation

service bus cloud services

data bus

Page 13: Connected Government Reference Architecture

Data governance & entitlementProtecting the privacy of the citizen

Protecting state & federal laws

Complying to state & federal confidentiality

Data protection

Page 14: Connected Government Reference Architecture

Data governance & entitlement

data bus

service bus cloud services

iden

tity

& e

ntit

lem

ent b

us

Page 15: Connected Government Reference Architecture

Complex eventsSurveillance and national security

Infrastructure monitoring (power grid / telco grid / water grid)

Transportation systems monitoring (national highway system / domestic aviation system etc)

Citizen services (retirement benefit tracking / social security / medicare etc)

Page 16: Connected Government Reference Architecture

Complex events

com

plex

eve

nts p

roce

ssor

event queue

email / alerts

dashboards

service bus

gov cloud

Page 17: Connected Government Reference Architecture

Availability & scalabilityGovernment PaaS

Elastic scaling of services and platform

Minimum HA setup

Multi zone / region based availability

Page 18: Connected Government Reference Architecture

The connected reference architecture

data bus

Gov cloud

service bus

Gov API gateway

secu

rity

gat

eway

even

t pro

cess

orbi

g da

ta a

naly

tics

event queue

data queue

cloud services

services workflows

Page 19: Connected Government Reference Architecture

WSO2 view on reference model

data bus

Gov cloud

service bus

Gov API gateway

secu

rity

gat

eway

even

t pro

cess

orbi

g da

ta a

naly

tics

event queue

data queue

cloud services

services workflows

Page 20: Connected Government Reference Architecture

ChallengesDisconnected mode - not all areas / stakeholders are connected

Bringing all state / federal agencies to a single architecture / platform

Automating everything

Understanding documenting and government workflows

Human factor

Page 21: Connected Government Reference Architecture

Case studiesSri Lanka e-Government Infrastructure – Crishantha Nanayakkara, ICTA - http://

wso2.com/library/conference/2014/10/wso2con-usa-2014-cloud-based-soa-e-

government-infrastructure-in-sri-lanka/

A Case Study on Consolidation of Middleware Platform - Badri Sriraman, Karsun

Solutions LLC - http://wso2.com/library/conference/2014/10/wso2con-usa-2014-a-case-

study-on-consolidation-of-middleware-platform/

State of Arizona’s Enterprise Services Platform (AESP) Journey - Aaron Sandeen, State

of Arizona - http://wso2.com/library/conference/2014/10/wso2con-usa-2014-state-

of-arizonas-enterprise-services-platform-journey/

Page 22: Connected Government Reference Architecture

A thin slice demonstration

license renewal service

insurance service

emission test service

license service

payment service

Page 23: Connected Government Reference Architecture

Technical implementation

REST/JSON SOAP/XML

OAuth 2.0

SOAP/XML

API Management

Service OrchestrationServices

analytics

Page 24: Connected Government Reference Architecture

//Questions ?

Thank you !