160 likes | 234 Views
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. Local interaction. Local interaction.
E N D
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.
Local interaction Local interaction Application layer with local event handling and workflow Application layer Preserves and manages data over space and time Persistent data layer Integrates platforms within an enterprise: our computers and networks become a unified resource Middleware Hardware and Operating System Layer Transaction Management
Each of these “integration products” has its own origins in concepts of resource management or process management. Channels Modes and means of access Knowledge Portals Shared Workflow eCommunity Applications are WEB enabled Local interaction Local interaction Application layer with local event handling and workflow Application layer Preserves and manages data over space and time Persistent data layer Integrates platforms within an enterprise: our computers and networks become a unified resource Middleware Hardware and Operating System Layer CRM Transaction Management
Channels Modes and means of access Integration layer Resource Integration Portal Identifiers and identities Master Index Shared Workflow and Message Hub Process Integration Application Adapters Local interaction Local interaction Application layer with local event handling and workflow Application layer Preserves and manages data over space and time Persistent data layer Integrates platforms within an enterprise: our computers and networks become a unified resource Middleware Hardware and Operating System Layer Domain of Integration
Commodity products and services Support for users to shape and govern their information environment. Local interaction Local interaction The information systems and communications utility. Structure and infrastructure Domain of Integration Channels Integration layer Portal Master Index Shared Workflow and Message Hub Application layer Persistent data layer Middleware Hardware and Operating System Layer
Commodity devices and services Integration Engines: CRM, BPR, media/content, Knowledge/document Management Systems Integration and change management. Applications service provision / In-house Local interaction Local interaction Software development and support Software technology licensing Box shifting Communications services Channels Integration layer Portal Master Index Shared Workflow and Message Hub Application layer Persistent data layer Middleware Hardware and Operating System Layer Communications infrastructure
Commodity devices and services Commodity devices and services Integration Engines: CRM, BPR, media/content, Knowledge/document Management Integration Engines: CRM, BPR, media/content, Knowledge/document Management Systems Integration and change management. Systems Integration and change management. Applications service provision / In-house Applications service provision / In-house Local interaction Local interaction Local interaction Local interaction Software development and support Software development and support Software technology licensing Software technology licensing Box shifting Box shifting Outsource: we do it all for you… Channels Channels Integration layer Integration layer Portal Portal Master Index Master Index Shared Workflow and Message Hub Shared Workflow and Message Hub Application layer Application layer Persistent data layer Persistent data layer Middleware Middleware Hardware and Operating System Layer Hardware and Operating System Layer
Commodity devices and services Integration Engines: CRM, BPR, media/content, Knowledge/document Management Systems Integration and change management. Applications service provision / In-house Local interaction Local interaction Software development and support Software technology licensing Box shifting “Best of breed”: The IT department in control Channels Integration layer Portal Master Index Shared Workflow and Message Hub Application layer Persistent data layer Middleware Hardware and Operating System Layer
Commodity devices and services Integration Engines: CRM, BPR, media/content, Knowledge/document Management Systems Integration and change management. Applications service provision / In-house Local interaction Local interaction Software development and support Software technology licensing Box shifting Strategic integration: Channels Integration layer Portal Master Index Shared Workflow and Message Hub Application layer Persistent data layer Middleware Hardware and Operating System Layer
Other Domains Portal Index Hub Local interaction Local interaction We are not alone: There are other domains around us. Domain of Integration Channels Integration layer Portal Master Index Shared Workflow and Message Hub Application layer Persistent data layer Middleware Hardware and Operating System Layer
Other Domains Portal Index Hub Local interaction Local interaction We are not alone: There are other domains around us. Domain of Integration Channels Integration layer Portal Hub to Hub interactions Master Index Shared Workflow and Message Hub Application layer Persistent data layer Middleware Hardware and Operating System Layer
Universal point of Access Portal Portal • 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
Universal point of Publication and Recourse Shared Workflow and Message Hub Hub • 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.
Master Index X Application xc Application xb Application xd Application xa I have identifier B in domain X Domain id XA and identifier C in domain Y. Domain id XB Domain id XC If application xb needs to talk to application ym about me, then it must do so via a hub to hub message. Domain id XD Master Index Y Application ym Application yk Application yl Application yj This requires that the identity management service, at the federation level, must confirm that XB ≡ YC ≡ “Me”. Domain id YA Domain id YB Domain id YC Domain id YD Identity Management Index Index Who gives the identity management service the right to do this and how?
Federal points of access: the catalogue of catalogues Federated Identity Management Services Universal point of publication, recourse and resolution. Local interaction Local interaction Federation Services Other Domains Domain of Integration Channels Integration layer Portal Portal Index Hub to Hub interactions Master Index Shared Workflow and Message Hub Hub Application layer We are not alone: There are other domains around us. Persistent data layer Middleware Hardware and Operating System Layer
Accepting networks Identity tokens and keys Local interaction Local interaction Brand Apps Pocketable data Federation Services Other Domains Domain of Integration Channels Federal points of access: the catalogue of catalogues Integration layer Portal Portal Federated Identity Management Services Index Master Index Shared Workflow and Message Hub Hub Universal point of publication, recourse and resolution. Application layer Smart Cards: Integrating the integration technologies Persistent data layer Middleware Hardware and Operating System Layer