1 / 21

Agenda

Agenda. Introduction Technical processes, Context, Smart Workflows Scenario Machine maintenance process Challenges and Requirements Related Work The Integration Process Pattern Realization Prototypes Conclusion. Business process managed with workflow engine. event notifications.

sancha
Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agenda • Introduction • Technical processes, Context, Smart Workflows • Scenario • Machine maintenance process • Challenges and Requirements • Related Work • The Integration Process Pattern • Realization • Prototypes • Conclusion

  2. Business process managed with workflow engine event notifications contextqueries business-production gap context world model managed by a context provisioning system Technical process (e.g. production) managed by MES/PPS Systems Introduction get toolfrom stock start toolexchange tool is attrited tasks,information mobile workers sensors, machine states

  3. Contribution • Bridge the business-production gap • Gaining flexibility, transparency and efficiency for the execution of technical processes • Allow the modeling of technical processes using workflow technology by • Providing a new technique to integrate context data into workflows: Context Integration Processes (CIP) • Provisioning of various information about the physical world, (e.g. sensor data, status of machines, tools and workers) in a context provisioning system • Introduction of Smart Workflows

  4. What is Context? Primary Contexts Time • "Context is any information that can be used to characterize the situation of an entity. An entity is a person, place, or object that is considered relevant to the interaction between a user and an application, including the user and applications themselves."[A. K. Dey: Understanding and Using Context, Personal Ubiquitous Computing] • A Smart Workflow is a workflow that uses context information captured by sensors in a smart environment. entity (hammer) Type Mobile Object Location Factory Resource Tool Secondary Contexts State=OK Used by= Machine ID

  5. Example - Machine Maintenance Process • Smart Factory (smart environment) • Tool location, state, usage tracking Preparation Stock Machine smartcart Transport

  6. Challenges and Requirements • Smart Workflow modeling • How can a domain expert easily model a Smart Workflow • Set of domain specific functional interfaces • Context provisioning • How to capture, manage and provide context information in an efficient way • High amounts of distributed context information • Support for primary contexts • System integration • How to integrate these contrary requirements in a extensible modular architecture • Support reuse of existing functions

  7. Related Work • SQL for querying context in BPEL workflows • Solutions: II4BPEL from IBM, Oracle, Microsoft • Could be used for integration of context information into workflows but it is not domain oriented • Difficult for domain experts to use • Only one context schema supported • PerCollab, uFlow • Provide context awareness in fixed workflow model • No reusable domain specific functions supported • Context Toolkit, Location Stack, CML • Systems for handling of context information • Either no web service interface or no powerful enough context model

  8. The Integration Process Pattern • Solves the problem of • integration of different systems with complex interfaces • reusability of web services by a hierarchical stack Workflows using Services service user ( e . g . Smart Workflow , application ) semantical domain specific interface domain specific Integration Processes ( IPs ) Integration Processes (IP) domain independent IPs domain independent IPs core IPs (for system X) core IPs (for system A) technical IT-system specific interface Integrated Systems system A system X

  9. Smart Workflow Realization • Concrete application of the CIP pattern • Components already available for usage: • BPEL for workflow layer • Nexus System for context provisioning Smart Workflow Layer (BPEL) Context Integration Layer (CIP) Context Provisioning Layer (Nexus Platform)

  10. BPEL workflows on Smart Workflow Layer Smart Workflow Layer order new tool no spare part in stock? find spare part prepare tool transport tool to preparation yes continueon event startobservation Context Integration Layer ToolAttritedEvent QueryTool ToolTransportCompleteEvent Context Provisioning Layer

  11. Nexus System for Context Provisioning Smart Workflow Layer Context Integration Layer Context Provisioning Layer Nexus Node Event Service Navigation Service Map Service Federation Component Federation Tier ASR Service Spatial Model Server Map Server Location Server Tier

  12. Structure of Integration Process • Every IP is implemented as BPEL workflow • Can be used as autonomic sub process • Has a Web-Service interface • Distribution of IPs to different servers is possible • Structure of IPs follows one of three patterns BPEL engine SW IP IP IP IP IP

  13. Context Integration Layer • Excerpt of the set of IPs needed for the integration of Nexus into Smart Workflows • Hierarchical inheritance of functionality

  14. Integration Process Structure Pattern 1 • Message Forwarding • Get document in Nexus Format • Pass to concrete Nexus Service • Reply with Nexus Language • Used for integration of Nexus Services • Mainly used by core IPs

  15. Integration Process Structure Pattern 2 • Transformation • IP provides adapted interface • Transformation step for request and reply from complex to less complex format • Mainly used by domain independent IPs

  16. Structure Pattern 3 on a Concrete Examples • Context Event handling • Most challenging IPs because of asynchronous communication (using S-Addressing) 17

  17. Integration Process Structure Pattern 3 • Free structure • Used for complex functionality

  18. Prototypes: Logistics with Smart Workflows Oracle BPEL Engine executing smart workflows control and monitor find new parcel find postman nearby parcel show e.g. map, position of parcel, route to pickup or delivery or human tasks postman takes task create parcel delivery task for postman BPEL Dashboard monitor delivery monitor pickup Context Integration Processes mobile device query new parcel and postman nearby monitor transport completion event Event Demo Client movement simulation (parcel and postman) Nexus Platform • Additional Prototypes: machine maintenance process, handling of individual customer orders (production)

  19. Conclusion • Introduction of Smart Workflow modeling • Workflows that cross boundaries to physical world • Usage of BPEL to orchestrate Integration Processes • Context provisioning • Usage of Nexus System • Federated context management system • Global scale augmented world model • System integration • Repository of Integration Processes • Allow domain expert to model their Smart Workflow themselves using a modeling tool and the IPs • Implement technical processes using workflows • By that: Bride the business-production gap

More Related