B2B Integration:

Government and Business

Networks and Extended Enterprises

The Agenda
B2B and G2G Examples & Overview
B2B Technologies (Lite & Heavy)
B2B Standards

Copyright: A. Umar
B2B and G2G as Major Areas of Work

B2B,
B2b

C2B, C2b
Customer Business
B2N
B2E

Network N2N
G2B, N2E
g2b

G2N
C2G, C2g Legend:
Customer Government C= customer
G2E B= Biusiness
b = Small Business
G2G, E = Employees
G2g G = Government
g = Small government
Copyright: A. Umar N = Network of businesses
Or governments)
 B2B Exchanges (Small to Large and Complex)

Org Unit A Org Unit B

Private
Private Process
Network
Process
(private or public)
Public Public Private
Private Data/Process
Process Data/Process Process

Private Private
Process Process

People, Processes & Technologies Issues:

Within a Department Governance
Within a Company Information Exchange
Between Companies Technical Architectures
Between Countries
 Governance Challenges
Interservice Governance (Goals, Strategies)

Service N
Service 1 Service 2

Interservice Connectivity Services

Many issues: Example: Document exchange

Legal & Policy
Privacy, security
Project Management
Systems Management
Technology Oversight
between agencies of a govt
Each agency served its citizens
for a fee
G2G: One agency cannot charge
another
Information Exchange Models (B2B Frameworks for Purchasing)

Org Unit A Org Unit B

1. Send Request (place order)

Private
Private Process
Process 2. Signal Receipt of Request
Public Public
Data/Process Data/Process Private
Private
Process Process
3. Fill Order Request

Private Private
Process
4. Signal Receipt of Order Process

Terminology (vocabulary, Ontology) -- Ontology Mapping Tables

Choreography: Workflow and Exchange Protocol
Many B2B Frameworks:
NIEM for G2G, HIE for Healthcare, PIPs for supply chains, FIX for
Financial Exchanges, RYO - Roll Your Own
 SOA-based Integrated Architecture Needs to be Extended
Enterprise App1 App2 App3
Service
Bus (ESB)

Broker ( Integration Hub) Directory, Security &

Administrative Services

App4 App5

A Broker (Hub) provides communications services between

= Adapter various service providers and consumers
May be simple (email, FTP)
= Service Interface An ESB that provides Directory, Security &
Administrative Services
Many commercial All applications (business components) provide services
ESBs (Mule, Biztalk, that are invoked through well defined interfaces
Websphere, etc) Adapters are used for message and protocol translations
 General B2B Pattern (SOA at Large)
Agency1 Agency 2 Agency3

Broker: B2B Integration Bus (BIB)

Value Added
= Private Process Component (VAC) = Public Proce
= Connector for BIB VAC = Information Exchange Models
Service specific ontologies and mapping tables
Workflow management (Choreography) ,
Govt Policy enforcer
Other Intelligence
 B2B Technical Architecture General View
Business 1 Business 2
Internal Network PKI and
DMZ DNS Internal Network
DMZ

Internal Applications
Internal Applications

Public Internet

Virtual Private Network Virtual Private Network

Proxy
Proxy Public Process
Public Process Node
Node

Directory and Firewall Firewall Directory and

Firewall
security service Firewall security service

DMZ = Demilitarized Zone

PKI = Copyright:
Private KeyA. Infrastructure
Umar
DNS = Domain Name Server
 More Detailed View

End User Bus (user Interface)

Agency1 Agency 4
Agency 2 Agency3
Agencies

Inter-
B2B Integration Bus (BIB)
agency
= Private Process = Public Process (BIB Client)
Copyright: A. Umar
= Adapter/Connector for BIB Different Levels of Issues (at Least Two)
 B2B Bus (Broker)
ARCHITECTURE CHOICES
Centralized broker
all documents stored in a doc repository,
All businesses/agencies access the repository to get info
Good news, bad news

Decentralized broker
all documents stored in target agencies ,
All agencies use the client to browse the directory to first
find the docs and then access the documents from the
target sites
Good news, bad news

Copyright: A. Umar
 Additional Capabilities
Broker main components: Broker as a server to agency
Directory get document request from a service
provider in an agency
Broker server
authenticate and find the location from the
Data dictionary directory
time stamped and transaction log forward the requests to the target agency
Doc repository get response from the target agency and
Doc clients (agents) forward to the client agency (may need to
enforcement of legal restrictions consolidate from multiple agencies)

Broker features (ESB) Client Features

Security (PKI vs no PKI) Doc Client (agent features) as a sender to
broker
Communicstions, etc
get document request from a service
Routing provider in an agency
Conversion authenticate and forward the requests to the
receive requests from Broker
Additional software neeeded get response from the broker and forward to
Interagency payment system the service provider
Oracle Policy Automation System Doc Client (agent features) as a receiver
from the broker
get document request from the broker
authenticate and forward the requests to the
agency service provider
get response from the agency and forward
to the Broker
Copyright: A. Umar
 Choices in B2B Trade
Representation of information (e.g.,
purchase order)
Choreography between business
partners (e.g., what happens if order
cannot be fulfilled)
Transport mechanisms:
Loosely coupled: email, FTP, MOM,
Pub/sub
Tightly coupled: HTTP (get, Post), SOAP-
RPC Copyright: A. Umar
a) High Level View
of a B2B System

b) Closer Look at the

B2B Gateway

Copyright: A. Umar
Examples and Usage Scenarios
Integration between government agencies
(document exchange logic)
HINs between healthcare agencies
Supply chain management between consumers
and suppliers
B2B trade between partners
Company partnerships, mergers and
acquisitions
Social networks between diverse groups
An ICT village (ICT community)
Others
Considerations
Common features
Copyright: A. Umar
Unique features
 General B2B Pattern
Organization 1 Organization
Organization 2 Organization 3

B2B Integration Bus (BIB) - Broker

= Private Process Value Added

= Public Process
Component (VAC)
= Connector for BIB
VAC = Information Exchange Model
Service Specific Ontologies
Workflow Management (Choreography) ,
Regulation/Policy Enforcer
Other Intelligence
 More Detailed View
Agency1 Agency 4
Agency 2 Agency3

B2B Integration Bus (BIB)

= Private Process Value Added

= Public Process
Component (VAC)
= Adapter/Connector for BIB VAC includes service specific features:
A workflow manager,
Supply chain manager,
Govt A.
Copyright: Policy
Umar enforcer
Ontology mapping
 Using aExternal
Value Added Component (VAC)
Clients External External
App1 App2
Internet

Gateway
Portal Internal . Namespace
. View . Security
Clients
Integration

Enterprise Service Bus (ESB)

Front-end Directory, Security & B2B
Hub Administrative Services Hub

Value Added
Hub1 Hub3
Component
VAC include unique features
A workflow manger,
App1,, 10 Supply
Copyright:chain manager, App30,,45
A. Umar
= Adapter B2B Hub, Govt Policy enforcer, ontology mapping
 Example: Macedonia Document Exchange
EU Requirement:
20 Documents (e.g., police reports, health info)
Exchanged between all EU countries
Many issues:
Some countries are underdeveloped (Balkan sates, southern
Russia,,)
How can they participate
Starting point: doc exchange between 5 agencies
Problem: citizen needs passport, has to supply 5 documents
from 5 different agencies
Goal: each agency should be able to get the needed
documents
Many challenges:
Legal restrictions (transfer between agencies, no one gets paid)
Architecture issues (main components, how will they fit with each
other)
Project Management issues (who manages what)
Copyright: A. Umar
 Macedonia Technical Architecture Vision

Citizens Service Bus (user Interface)

Agency1 State
Agency 2 Agency3
Agencies

MIS
Macedonia Information Bus (MIB)

= Private Process = Public Process (MIB Client)

Copyright: A. Umar
= Adapter/Connector for MIB Different Levels of Issues (at Least Two)
Example: Child Welfare System
An interstate child welfare system is being instituted to address this
problem by providing a child welfare broker (CWB) that gets info
from multiple states. The system is an SOA-based system that
operates at a B2B level. It operates as following (simplified view):
Each state keeps its own database (CWD)
A user sends a query about a child and the query is sent to the CWB
The CWB sends a standard message (the format of this xml-
message is pre-agreed) to all 50 states plus some other govt
agencies
The recipients receive this message, translate it to its local format if
needed and queries the local CWD
The results are sent back to the broker
The broker gets all messages, consolidates them and creates a
uniform response
the broker is also responsible for security, authentication and legal
restrictions

Copyright: A. Umar
 Example: Childwelfare system
Citizens Service Bus (user Interface)

State1 State
State 2 State3

Child Welfare Broker

= Private Process = Public Process

Copyright: A. Umar
= Adapter/Connector for B2B Different Levels of Issues (at Least Three)
Bahrain: eGovernment Strategy for Connected Governance

SCICT
National
eGovernment eServices Mobile
Contact
eGovernment Portal Centres Gateway
Centre
Authority
Enterprise Architecture
BPR &
Authentication (Single Sign on, Smart card)
Legal

Capacity Services Case Social

Tourism
Building Gateway Management Information

Marketing &
G2E portal G2B Gateway eProcurement Real Estate
Awareness

International
Education eHealth Customs eOffice
Events

International National Data Set

Benchmarking
Data Security
Programme
Management Government Data Network
Monitoring &
Data Centre
Evaluation
Copyright: A. Umar
 Many Examples
Well Known Examples: JNET, Child welfare
information Gateway, NIEM Website, Federal CIO
Report
Other Examples (B2B, G2G, N2N) small to large:
Exchanges between small cities & small
agencies
Virtual inventories, supply chains for retails and
food distribution
Electronic Fund Transfer: SWIFT and FIX
Europe 2020 Services, South to South
Red Cross (80 agencies in 50 countries)
Between US and Europe on Intellectual Property
 Other Examples
USPTO Begins New Electronic Priority
Document Exchange Program
the United States Patent and Trademark Office
and the European Patent Office (EPO),
implemented a new service to allow certified
copies of patent application priority documents
to be exchanged between the two offices
electronically. http://www.uspto.gov/web/offices/
com/sol/notices/72fr1664.pdf

Copyright: A. Umar
 Concluding Comments

B2B activities are evolving

within an enterprise
B2B SCM
B2B emarket
Variety of enabling technologies
workflows
EAIs
XML for B2B purchasing
EDI
Others
B2B Platforms are becoming commercially
available Copyright: A. Umar
 Voice Annotations
For Voice Annotated Discussion of these slides, please review the
following Video Clips.

B2B Application Integration Concepts, Duration = 39 Minutes, URL=

:http://harrisburgu.adobeconnect.com/p4tdz0g7dvl/

B2B Integration Examples, Duration = 18 minutes,

url = URL for Viewing: http://harrisburgu.adobeconnect.com/p8xwsye1cr7/

Copyright (A. Umar)