Embed Size (px)
Citation preview
Towards an agreed cross-government services and information architecture
Working Document, April 2003
Contents
n Conceptual and logical views of cross-government technical architecture
n Intercept between centrally provided components (Office of the eEnvoy, OeE) and department provided
n XML to backend integrationn Front-end standards (eg. definition of
requirements for consumption by the likes of the Online Government Store)
Background
n To work towards an overall cross-government architecture that supports intermediaries, back office interoperability, and smart use of common services and components
VisionFor the Citizen: a simple, easy interaction with government services through their channel of choiceFor Government: to provide a step-change in the delivery and perception of integrated government services, with commensurate cost-savings
Gateway
DWP
localauthority
localauthority
NHSNet
IR
DfES
otherGovt dept
bank
pensionprovider
Gateway
OeE
DWP
localauthority
localauthority
NHSNet
IR
DfES
otherGovt dept
bank
intermediary
“My Services”(illustration only)
• Benefits Calculator and Claim• My Pension Forecast and Planner
• Pay Parking Fine• My Medical Records• Complete Tax Return
• View Council Proceedings• Schools Application Service
• Planning Application and Tracking• My Council Tax
• e-Vote• Report faulty street light
Business context - shifting the value-chain
1. Capture
2. Clean
3. Verify
4. Apply rules
5. Calculate entitlement
6. Award
7. Results/pay
Back
end
syst
ems
Back OfficeFront Office Channels
Migrate processes
Call Centres
CABOnlineGovtStore
JobcentrePlus
IREC
High Level Overview – Conceptual Cross-Government ArchitectureM
etadata Framew
ork
Security Framew
ork
Data Interoperability (XM
L)
Managem
ent and Operations
User Experience
Public Interfaces
Common Services
Providers
Web Services
Backend Systems – Data, Functionality
Authentication/Authorisation/Routing/Content Management etc
Web Services
Applications(portal, PC-based, etc)
Integration
Govt System Interfaces
Adaptors
UI C
ompo
nent
s an
d Pr
oces
ses
Dat
a So
urce
sD
ata
Acc
ess
Bus
ines
s Lo
gic,
W
orkf
low
Conceptual e-Government Architecture Overview
Intermediaries(eg NACAB,
Banks, Employers)
GovernmentPortals(central,Local)
CommercialPortals
(eg. Yahoo,MSN)
PC Applications(eg. Money,TaxSaver)
A & A Transactions
RelatedOrganisations (egPensions Industry)
User Experience
Public Interfaces
Common Services
Providers
Web Services
Helpdesk& MIS
Secure2-way
comms
CentralGovernment,
Local Authorities,Agencies, etc
Private Sector(eg. Upmystreet.com,
MapPoint.Net)
Portable Devices
(eg phones,PDAs)
iDTVKiosks,
Libraries,etc
NotificationsForms
(Store &Engine)
Rules
UKOnlinePortal
Circumstances&
PersonalisationPayments AppointmentsAddressUKOnline
CMS UDDISearch
Integration
XML to proprietary integration
Metadata Fram
ework
Security Framew
ork
Data Interoperability (XM
L)
Managem
ent and Operations
Orchestration
Web ServicesGovt System Interfaces
e-Government Conceptual Architecture Use Illustration
Intermediaries(eg NACAB,
Banks, Employers)
CitizenServices
(eg. NTC)
CommercialPortals
(eg. Yahoo,MSN)
PC Applications(eg. Money,TaxSaver)
A & A Transactions
RelatedOrganisations (egPensions Industry)
User Experience
Public Interfaces
Common Services
Providers
Direct User Interfaces + Web Service Interfaces
Helpdesk& MIS
Secure2-way
comms
CentralGovernment,
Local Authorities,Agencies, etc
Private Sector(eg. Upmystreet.com,
MapPoint.Net)
Portable Devices
(eg phones,PDAs)
iDTVKiosks,
Libraries,etc
NotificationsForms
(Store &Engine)
Rules
OnlineGovernment
Store
Circumstances&
PersonalisationPayments AppointmentsAddressUKOnline
CMS UDDISearch
Metadata Fram
ework
Security Framew
ork
Data Interoperability (XM
L)
Managem
ent and Operations
Orchestration
Web ServicesIntegration
Govt System Interfaces
Adaptors
Key Issues
n For the front-end delivery to work, Departments and the OeE need to agree standards (format and payloads) for web services exposed by departments both for specific content (OGS etc) and services (Gateway transaction)
n Departments then need to expose defined web service interfaces necessary to deliver the online content and services
n XML to existing system integration issues need to be resolved within the various departments to ensure consistency of delivery (and hence integration)
n Orchestration of processes both at the OeE level (cross-government orchestration of processes) and department level (cross-system) need to be defined and delivered for each specific new online service
n Agreement is needed as to where in the virtual architecture various components sit and whether they are centralised or federated – including the intercept between OeE components and departmental components
Web Services Standards
n Gateway will act as a web services broker, ensuring all web service calls can be made through the same common architecture and endpoints as message-based transactions
n Some common standards for web service delivery need to be defined (including eg. naming conventions, error handling responses and so on)
n The schema, meta content etc of the actual SOAP methods and calls needs to be defined for the interaction of content and services, with particular reference to the intermediary model
Web Services Delivery
n OeE and Departmental Services need to define the roadmap of web services that need to be delivered in order to support the defined content and services (pensions, benefits, etc)
n … they then need to be delivered
XML to Proprietary Integration
n Three principal elements:¨custom adaptors (specific integration tools
that map between eg. Mainframe and XML) and then expose as web services
¨web services interfaces hosted on the existing proprietary platform and exposing data and methods through native XML/SOAP
¨associated process logic to ensure data and application integrity
XML to Proprietary Integration
Backend Integration web service
Existing System(s)
MSMQ/MQbridge
COMTI /MVS
OLEDB /AS400, VSAM
DB2
Web Services
RelatedOrganisations (egPensions Industry)
Common Services
ProvidersCentral
Government, Local Authorities,
Agencies, etc
Private Sector(eg. Upmystreet.com,
MapPoint.Net)
IntegrationXML to proprietary integration
Orchestration
To Interfaces tier
Govt System Interfaces
ICL (VME)
XML integration
Interface With Legacy Application
Legacy Platform Proprietary API
Standards-based API
XML WS
Legacy Platform No Longer Viable
Migrate existing code to modern platform and expose capabilities as a web-services; use screen scrape approach; or scrap the application and build a completely new one.
Legacy Platform Is Viable
Write application that simply
calls API and maps its
functions & parameters to web-service methods and
properties
Write application or utilise
integration tool that produces web-services
Write application or utilise
integration tool that produces web-services
Use the web-service directly or via COTS
packages that add
functionality.
Legacy to open roadmap
Data and Application Orchestration
n Joined-up and multi-step interactions on franchise and intermediary delivery need orchestration to:¨ ensure data and application integrity across existing backend
systems¨ ensure complex, multi-party transactions possess data and
application integrityn Some of this is logically performed at the Common
Services tier (“middle office”), for processes that span more than one back-end entity
n Local orchestration within and across specific backend systems may also be needed in the back-office tier to ensure application-specific data integrity
Data and Application Orchestration – Cross Government
Orchestration• state and application logic• roll-back as appropriate across multiple departments• scheduling of complex, multi-party request responses• interaction with other components (eg rules engine)
Existing System(s)
MSMQ/MQbridge
COMTI /MVS
OLEDB /AS400, VSAM
DB2
web service
Existing System(s)
MSMQ/MQbridge
COMTI /MVS
OLEDB /AS400, VSAM
DB2
web service
Data and Application Orchestration – Departmental
• state and application logic• roll-back as appropriate across multi-systems• scheduling of complex, multi-party request responses• interaction with other components (eg rules engine)
Orchestration
Existing System(s)
MSMQ/MQbridge
COMTI /MVS
OLEDB /AS400, VSAM
DB2
web service
Central / Department Architectures Intercept – potential conceptualisation
General business applications:• finance• human resources• procurement• asset management• CRM
Dept-specific applications:• business processing• case handling• collaboration, search and analysis• content management• document management• records management • XML integration• Etc
Infrastructure:• systems mgt• security mgt• archive mgt• network mgt
AuthenticationAuthorisation
PaymentsRules
Secure MessagingTransactionsOrchestration
DotPSearch
HelpdeskNotifications
FormsCircumstances & Personalisation
Address
Department Architecture
Department Architecture
e-GovernmentCommon Architecture
General business applications:• finance• human resources• procurement• asset management• CRM
Dept-specific applications:• business processing• case handling• collaboration, search and analysis• content management• document management• records management • XML integration• Etc
Infrastructure:• systems mgt• security mgt• archive mgt• network mgt
Logical to Physical – Option 1 (centralised model)
Authentication, Authorisation, Payments, Rules,Secure Messaging, Transactions, Orchestration,
DotP, Search, Helpdesk, Notifications, Forms, Circumstances & Personalisation
Address
Authentication, Authorisation, Payments, Rules,Secure Messaging, Transactions, Orchestration,
DotP, Search, Helpdesk, Notifications, Forms, Circumstances & Personalisation
Address
Dat
a ce
ntre
1D
ata
cent
re 2
OeE Components
Dept A
Dept B
Dept C
Dept E
Dept F
Logical to Physical – Option 2 (federated model)
OeEAuthentication, Authorisation, Payments, Rules, Secure Messaging, Transactions, Orchestration, DotP, Search, Helpdesk, Notifications, Forms, Circumstances & Personalisation, Address
Dept AAuthentication, Authorisation, Payments, Rules, Secure Messaging, Transactions, Orchestration, Search, Helpdesk, Notifications, Forms, Circumstances & Personalisation, Address
Dept nAuthentication, Authorisation, Payments, Rules, Secure Messaging, Transactions, Orchestration, Search, Helpdesk, Notifications, Forms, Circumstances & Personalisation, Address
Single logical view externally of federated physical environment
DWP Illustrative
DepartmentalScope
(DWP)
e-Government Layered Architecture – DWP View–
Business Processes
Business Components
User Processes
Service Interfaces
Databases & National Services
DWP Databases
Citizens ’Database
Data Access Components
Components
Citizen >>>>
Agents >>>>
Private PensionProjections
External ServicesFrom 3rd Parties
Web Services
3rd Party LinksPension Forecast Retirement PlanBenefits EntitlementRegister Consents
Submissions
Reconcile Identity Manage Consents Grant Permissions Register & Enroll Agents
Compile Benefit Entitlement Compute Pension Forecast Manage Retirement Plan
Record Credentials
Record Delegations Enroll 3rd Parties
Maintain 3rd Party Links
Maintain History & Plans Information Service & Links Reminders & Acknowledgements
Citizens’ Events Maintenance
Issue DWP Event
Maintain DWP Event Links
Provide DWP “Lifeline”
Retrieve DWP Plan
Update DWP Plans
Demographics
ID X-Ref
FinancialInfo & Quotes
Receive Returns
ProvideAssessments
IR informationby Consent
Known Facts
Maintain Consents Provide Informationby Consent
Maintain DelegationsProvide BenefitsForecasts
Provide Pension Forecasts
Receive Claims
Provide Benefit EntitlementInformation
Tax CreditInformation
Provide EntitlementInformation
Submit DemographicChange
Provide Job Availability Information
Answer Citizen QueryGather Citizen Information
Provide “Better off” Calculation
Examples:
Inland RevenueServices
Web Services
Cross GovtService
Framework
Portal
Local AuthorityServices
Web Services
•Benefits Rules Engine•Pensions Rules Engine•Citizen Account Manager•Job Broker•“Better off” Calculator
•Information Gatherer•Appointments•Mediated Info Services•Job Centre +•NTC Gateway
CitizenServices
Web Services
Consents
ILA informationby Consent
Authority Delegations
•NIRS 2•Scheduled Payments•JSA
DepartmentalScope
(DWP)
e-Government Layered Architecture – DWP View–
Business Processes
Business Components
User Processes
Service Interfaces
Databases & National Services
DWP Databases
Citizens ’Database
Data Access Components
Components
Citizen >>>>
Agents >>>>
Private PensionProjections
External ServicesFrom 3rd Parties
Web Services
External ServicesFrom 3rd Parties External ServicesFrom 3rd Parties
Web Services
3rd Party LinksPension Forecast Retirement PlanBenefits EntitlementRegister Consents
Submissions
Reconcile Identity Manage Consents Grant Permissions Register & Enroll Agents
Compile Benefit Entitlement Compute Pension Forecast Manage Retirement Plan
Record Credentials
Record Delegations Enroll 3rd Parties
Maintain 3rd Party Links
Maintain History & Plans Information Service & Links Reminders & Acknowledgements
Citizens’ Events Maintenance
Issue DWP Event
Maintain DWP Event Links
Provide DWP “Lifeline”
Retrieve DWP Plan
Update DWP Plans
Demographics
ID X-Ref
FinancialInfo & Quotes
Receive Returns
ProvideAssessments
IR informationby Consent
Known Facts
Maintain Consents Provide Informationby Consent
Maintain DelegationsProvide BenefitsForecasts
Provide Pension Forecasts
Receive Claims
Provide Benefit EntitlementInformation
Tax CreditInformation
Provide EntitlementInformation
Submit DemographicChange
Provide Job Availability Information
Answer Citizen QueryGather Citizen Information
Provide “Better off” Calculation
Examples:
Inland RevenueServices
Web Services
Inland RevenueServices
Inland RevenueServices
Web Services
Cross GovtService
Framework
Portal
Local AuthorityServices
Web Services
Local AuthorityServices
Local AuthorityServices
Web Services
•Benefits Rules Engine•Pensions Rules Engine•Citizen Account Manager•Job Broker•“Better off” Calculator
•Information Gatherer•Appointments•Mediated Info Services•Job Centre +•NTC Gateway
CitizenServices
Web Services
CitizenServicesCitizen
Services
Web Services
Consents
ILA informationby Consent
Authority Delegations
•NIRS 2•Scheduled Payments•JSA
FirewallWeb Server
Wi
Inter-/Intranet
User ProcessLayer
Service Layer
BusinessLogicLayer
DataAccessLayer
PersistentDataLayer
UserInterface
Layer
DataAccess
Components
Serv
er M
anag
emen
t
AnyData
Source
Legacy & PackageAccess Controller
WirelessDevice
Mobile AccessController
PackageApplic-ation
PackageData
Access
PackageBusiness
Logic
PackageServiceControl
PackageDatabase
P
LegacyData
Access
LegacyBusiness
Logic
LegacyServiceControl
LegacyDatabase(Relational &
Flat File)
LegacyApplication
BrowserThin ClientRich Client
E-Government Application Architecture(Deployed within a layered Architecture)
CollaborationPlatform
Pres
enta
tion
Tier
Bus
ines
s Ti
erD
ata
Tier
User ProcessComponents
BusinessProcess
Components
Internet
3rd PartyData
Source
User Interface Components
LegacyData
LegacyDatabase(Relational &
Flat File)
LegacyData
Access
DataSource
Data AccessController
StoredProcedures
ServiceAgents
3rd PartyBusiness Logic
3rd Party
3rd Party
ApplicationIntegrator
Business Components
CustomSolution
E-BusinessSolution
Apps ServerSolution Legacy SolutionOperating
System
PDA
Directory
e-Business
Server
InfrastructureDatabaseSolution 3rd Party
OrchestrationEngine
MessagingEngine
ServiceInterfaces
DataEntity
Components
BusinessProcess
Layer
Web services
Web services
Windows Server 2003 External Platforms
Windows Server 2003
Internet Security & Acceleration Server 2000
Internet Information Services with ASP
Inter-/Intranet
User ProcessLayer
ServiceLayer
BusinessLogicLayer
DataAccessLayer
PersistentDataLayer
UserInterface
Layer
App
s C
ente
r Ser
ver 2
000
AnyDatabase
Host Integration Server2000
MobileInformation
Server
PackageApplic-ation
PackageData
Access
PackageBusiness
Logic
PackageServiceControl
PackageDatabase
P
LegacyData
Access
LegacyBusiness
Logic
LegacyServiceControl
LegacyDatabase(Relational &
Flat File)
LegacyApplication
.NET Enterprise Servers(Deployed within a layered Architecture)
ExchangePr
esen
tatio
n La
yers
Bus
ines
s La
yers
Dat
a La
yers
UserProcess
Components
ServiceInterfaces
Internet
3rd PartyDatabase
LegacyData
LegacyDatabase(Relational &
Flat File)
LegacyData
Access
SQL 2000Database
SQL 2000ServerStored
Procedures
3rd PartyData
Access
3rd PartyBusiness Logic
BizTalk Server 2000
Routing Engine
BizTalk ProcessAutomation
BizTalkDocumentExchange
Long RunningConversationsB
izta
lk D
ocum
ent
Tran
sfor
mat
ion
BusinessComponents
COM+Solution
BizTalkSolution
Host IntegrationSolution
OperatingSystem
Windows CEPDA
ActiveDirectory
InfrastructureSQL ServerSolution 3rd Party
DataAccess
Components
BusinessProcess
Components
WirelessDeviceBrowserThin ClientRich Client
Windows XP Professional
User Interface Components
BusinessProcess
Layer
MSMQ ListenersPersistent Messaging
.Net Remoting & DCOMApplication Endpoints
ASP.Net Web ServicesXML Web Services
Enterprise Services (Windows)
Role-based Security
Distributed Transaction Mgt
Business Component Hosting
Business EntityComponents
.NET Frameworks
XML - Serialisable Objects
ADO.NET DataSets
XML Document Management
Biz
Talk
Ada
pter
s (3
00+)
VS.N
et W
eb P
roxy
Web
Ser
vice
ASP.Net WebFormsDigital Dashboard
Sharepoint ServerUser Doc Workflow
Exchange WorkflowCollaboration Workflow
.Net Windows Forms
Offline Client
Windows UI
Smart Client UI
Office XPDocument I/O
Outlook XP Exchange FormsMessaging UI
ASP.Net Mobile ToolkitThin Device UIASP.NET
Web UI
Web services
Web services
Web Service Approaches
DepartmentalOnlineServicePortal
browser
Current
DepartmentalOnline
Service Engine
Proposed
Gatewayweb
Servicebroker
DepartmentalPortal
IntermediaryPortal
ISV Application
browser browserRich client
WS
DepartmentalOnline
Service Engine
Gatewayweb
Servicebroker
DepartmentalPortal
IntermediaryPortal
ISV Application
browser browserRich client
WS
DepartmentalOnline
Service Engine
WS
DepartmentalOnline
Service Engine
WS
Online Government Store (OGS) Models
DOTP ContentManagement
Dept A
Dept B
Web Service requirements
OGS DeptPortal
IntermediaryPortal
Web services broker
XML
XML
XML
- payload content (informational/text)
- franchise segmented markup (eg. parents)
- validity/timestamp
- associated online services
Security
- payload content (informational/text)
- service segmented
- transaction content (sync and async)
- payload content (informational/text)
- franchise segmented
- service segmented
- transaction content (sync and async)
- validity/timestamp
Living Examples
n Government Gatewayn Sandvik Toolingn US Navy
LegacySystem
Department 1 Department 2
LegacySystem
Department 3
LegacySystem
LA
LegacySystem
Authentication
Secure Messaging
Payment Service
User ID for Government
SAGE ACCOUNTING SOFTWARE
TransactionEngine
LA Portal
Common Portal Infrastructure
Dept 3 PortalDept 2 Portal
VirtualDepartment
Commercial Portal
WEB SERVICES LAYER
Government Gateway – Web Services as standard interface
Sandvik Framework
Infrastructure Services
Communication Services
Monitoring
Web Services
Security
An application, a program or a person
Metadata Library
<Sem
antic-Syntax>
Integration Brokers
Adapters
Application Servers
An application, a program
VolvoEBD
IBX Portal Router
SupplyOrder
Fax/emailGateway
X P C
BizTalk Server
CustomerOrder StockInquiry CustomerPrice
WebServiceClient
xCBL mapping
Sandvik Tooling
IBX
Volvo
UDDI Tooling Web Services
ERP
1
2
3
4
5
6
7
8
910
11
Web Services in use at Sandvik
1
2
US Navy Case Study - US Navy Reserve Mobilization
n Problem: ¨ multiple manual entries of data, partially manual
processes, and inconsistent processes across different organizations at different sites led to data inconsistency & errors
¨ an important legacy system did not meet new security and inter-operability requirements (NMCI)
¨ no “visibility” in status of processesn Solution:
¨ rapidly develop an application that connects processes across different organizations & make information available as web services
¨ rebuild a legacy application in new technology (ASP.NET)
¨ provide status reporting/tracking¨ “expose” information as a web services whenever there
was probability that other applications could use the information
