Reference scenario and demo plan - PowerPoint PPT Presentation

neal
reference scenario and demo plan n.
Skip this Video
Loading SlideShow in 5 Seconds..
Reference scenario and demo plan PowerPoint Presentation
Download Presentation
Reference scenario and demo plan

play fullscreen
1 / 25
Download Presentation
Reference scenario and demo plan
104 Views
Download Presentation

Reference scenario and demo plan

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Reference scenario and demo plan

  2. Networked enterprises and multi-organization Web applications (1) • Networked enterprises can significantly benefit from new-generation web applications • able to share data and services distributed in different organizations • Web applications can be created by composing distributed services hosted in different administration domains • “distributed multi-organization Web application”

  3. Networked enterprises and multi-organization Web applications (2) • Distributed multi-organization web applications: • services are handled under the assumption of "open world" and are provided by different organizations • they can be modified or replaced, they can disappear, and new services with different features may become available • services are executed outside the consumer infrastructure and control, at a business partner’s site • Workflow management systems can have a particular relevance for the development of these applications

  4. The network of enterprises

  5. Internal architecture of the ArtDeco enterprise

  6. Wine industry • Wine industry is one of the most relevant in Italy • It shows quite conservative attitudes • Even if it is organized in consortia, these do not really encourage collaboration between their members • It could greatly benefit from a new vision of their business and from new IT technologies • Peripheral devices to control cultivation, harvesting, fermentation, storage, delivery… • Encourage interaction with the external environment (other actors, similar companies, complementary services, …)

  7. Our main scenario • Two wine companies located in the same area • GialloRosso • BiancoRosso • Both have a similar organization but different information systems. • Surprisingly, they share some information, for instance, • GialloRosso makes available to BiancoRosso its access to data from GamberoRosso

  8. Players Carrier

  9. Production and distribution

  10. Production and distribution

  11. Part 1: Adaptive workflow (11.20-11.50)A9 (with links to A10 and A11)

  12. Adaptation of cultivation process to vineyard conditions • A daily process is started : planning is defined but… • Weather conditions are favorable to the formation of parasites (e.g. PowderyMildew) • The system decides to insert in the process some specific treatments (spraying of pesticides) • Rain is inferred by listening data from a pluviometer (in alternative, humidity sensors could be used) • The system decides to remove the irrigation activity from the daily process • Rain becomes heavy • The system decides to insert an agronomist visit in the process • The agronomist visit is executed; the agronomist inserts the status of the vineyard in the system • The harvesting is replaced with an activity for buying grapes

  13. Part 2: Life-long verification for adaptive systems(11.50-12.05)A10

  14. Life-long verification helps in checking that changes in WF are acceptable • A daily process is running: • The workflow is managed with the following rules: • on (PowderyMildew) add Spraying; • on (Rain) drop Irrigation; • on (Rain) drop Spraying; • on (HeavyRain) add AgronomistVisit; • and with the following constraint: • Pruning ->! WeedsRemoving; • The model checking of the process is ok • A new management rule is inserted inthe knowledge base: • on (PowderyMildew) add Pruning; • The model checking of the workflow shows some problems and the rule insertion is not performed

  15. Part 3: Data Analysis (12.05-13.00)A4, A6, A7

  16. Contextual data analysis • At GialloRosso the oenologist and the agronomist interact with the data related to harvesting and to the wine ageing • the information they interact with depend on their role and on the workflow phase • The agronomistinserts information relatedto the nature of the naturalphoenomena • The agronomist and the oenologistask information relatedto the phase • At BiancoRosso the sales manager: • analyzes sales data • in a different moment analyzes the market trends, then • reads similar information in natural language from the web • GialloRosso performs market analyses by accessing its own information combined with market information collected by its ally BiancoRosso

  17. … Analysis on unstructured data are crucial for many other sectors • The case of fashion using IBM Omnifind

  18. Part 4: Data Acquisition from the field (13.45-14.25)A11

  19. How can we obtain information from the environment? • WSN single hop and multi hop • Two integration approaches with the system backend • Web service and definition and management of SLAs • Perla

  20. Part 6: How do we cooperate with the enterprises in the network?(14.45-15.05)A9

  21. Can wegetnewcollaborationopportunities? • GialloRossoworkflowisstucked… • An urgentrequestfor a wine pallet isarrivedbut no carrierisavailable • … byobserving the otherneighborenterprises … • … wediscoverthatBiancoRossohas a truck leavingfrom the samedestinationofGialloRossorequest… • What a greatopportunityforourworkflow…

  22. Part 6: Discovering new processes(14.25-14.45)A5

  23. Discovering new processes: rationale • As in every SME, in GialloRosso the workflow does not control everything! • … but we can discover new processes by analyzing usage data from various tools, e.g., office tools

  24. Part 7: Integration of models(15.05-15.25)A9

  25. Part 8: How can we match all this with business?(15.50-16.10)A1, A2, A3