the “joining up” national project

The “joining up” national project

The workflow national project

At Newcastle University we are responsible for the Overall Framework and Learning Evaluation.

This is the α version of the technical component of the framework.

Integrates platforms within an enterprise: our computers and networks become a unified resource

Hardware and Operating System Layer

Middleware

Preserves and manages data over space and timePersistent data layer

Local interaction

Local interaction

Application layer with local event handling and workflowApplication layer

Transaction Management

Transaction Management

Modes and means of access

Channels



Middleware


Local interaction

Local interaction


Applications are WEB enabled

CRM

Shared Workflow

Knowledge Portals

eCommunity

Each of these “integration products” has its own origins in concepts of resource management or process management.

Resource Integration

Identifiers and identities

Process Integration

Master IndexShared Workflow and Message Hub

PortalIntegration layer

Modes and means of access

Channels

Application Adapters

Domain of Integration



Middleware


Local interaction

Local interaction


The information systems and communications utility.

Commodity products and services


Middleware

Persistent data layer



Local interaction

Channels

Local interaction

Support for users to shape and govern their information environment.

Application layer

Domain of Integration Structure and infrastructure


Middleware




Channels

Local interaction

Local interaction

Application layer

Box shifting

Software technology licensing

Software development and support

Integration Engines:CRM, BPR, media/content, Knowledge/document Management

Commodity devices and services

Syste

ms In

teg

ratio

n an

d chan

ge m

an

age

me

nt.

Ap

plicatio

ns service

provision

/ In-ho

use

Communications infrastructure Communications services


Portal

Application layer


Middleware




Channels

Local interaction

Local interaction

Application layer

Outsource: we do it all for you…

Box shifting





Syste

ms In

teg

ratio

n an

d chan

ge m

an

age

me

nt.

Ap

plicatio

ns service

provision

/ In-ho

use


Middleware


Integration layer

Channels

Local interaction

Local interaction

Box shifting





Syste

ms In

teg

ratio

n an

d chan

ge m

an

age

me

nt.

Ap

plicatio

ns service

provision

/ In-ho

use


Middleware




Channels

Local interaction

Local interaction

Application layer

“Best of breed”: The IT department in control

Box shifting





Syste

ms In

teg

ratio

n an

d chan

ge m

an

age

me

nt.

Ap

plicatio

ns service

provision

/ In-ho

use


Middleware




Channels

Local interaction

Local interaction

Application layer

Strategic integration:

Box shifting





Syste

ms In

teg

ratio

n an

d chan

ge m

an

age

me

nt.

Ap

plicatio

ns service

provision

/ In-ho

use


Middleware




Local interaction

Channels

Local interaction

Portal

Index

Hub

Application layer

Domain of IntegrationOther

Domains

We are not alone: There are other domains around us.


Middleware




Local interaction

Channels

Local interaction

Portal

Index

Hub

Hub

to H

ub in

tera

ctio

ns

Application layer


Domains


Universal point of Access

• Is offer X in your catalogue the same as offer Y in mine? – Shared identifiers and publication space.

• If brokers and intermediaries (information value-adders) are to create new virtual domains (partnerships) they need tools and facilities.

• Sometimes we need to be able to “google” the whole federation…

• This universal service creates the signaling for an information economy.– Financial value– Social value– Political value

Portal Portal

Universal point of Publication and Recourse

• The audit trail may lead to a boundary: where do you go then, escalation has to stop somewhere.

• Can you deliver my scripts and can I deliver yours?

• How do I tell the people who need to know?– Individually addressed messages,– Role and workflow based structured messages,– Narrow-cast,– Universal broadcast,– Publication.

Shared Workflow and Message Hub

Hub

Who gives the identity management service the right to do this and how?

Identity Management

I have identifier B in domain XDomain id XA

Domain id XB

Domain id XC

Domain id XD

Appl

icat

ion

xaAp

plic

atio

n xb

Appl

icat

ion

xcAp

plic

atio

n xd

Master Index X

Index Index

and identifier C in domain Y.

If application xb needs to talk to application ym about me, then it must do so via a hub to hub message.

This requires that the identity management service, at the federation level, must confirm that XB ≡ YC ≡ “Me”.

Appl

icat

ion

yk

Appl

icat

ion

ymDomain id YA

Domain id YB

Domain id YC

Domain id YD

Appl

icat

ion

yj

Appl

icat

ion

ylMaster Index Y


Middleware




Local interaction

Channels

Local interaction

Portal

Index

Hub

Hub

to H

ub in

tera

ctio

ns

Application layer

Federal points of access: the catalogue of catalogues

Universal point of publication, recourse and resolution.


DomainsFederation Services


Federated Identity Management Services


Middleware




Local interaction

Channels

Local interaction

Portal

Index

Hub

Application layer

Federal points of access: the catalogue of catalogues

Federated Identity Management Services

Universal point of publication, recourse and resolution.


DomainsFederation Services

Smart Cards: Integrating the integration technologies

Accepting networks

Identity tokens and keys

Brand Apps

Pocketable data

the “joining up” national project

Documents