Semantic Technologies in the Business Grid Collaboration Lifecycle

1. Semantic Technologies in the Business Grid Collaboration Lifecycle Dr Ioannis Kotsiopoulos ioannis@cs.man.ac.uk BREIN - Semantic Week 09

2. Presentation Outline • BREIN Vision, Overview, Scenarios • Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles • BREIN Ontologies • Knowledge Aware Grid Services in BREIN • What to take away BREIN - Semantic Week 09

3. BREIN Vision Create an infrastructure that will increase the level and dynamism of collaborations among companies, with special focus on SMEs Objectives • ‘To take the Grid to business’ • Enable participants to easily interact • It provides an Intelligent, adaptive framework • Increase the stability and dynamism of the framework through a set of innovative technologies • Optimize the collaboration so as to meet the individual participant’s business objectives • Provide business entities with a means to optimize their service provisioning (regarding the respective business goals) BREIN - Semantic Week 09

4. BREIN Vision in Business Terms Business aspects will be improved with this project: Service Level Agreement Cost Reduction Simplicity for users Negotiation between customer provider to define terms in the service provision is done as a contract. Provider should satisfy the terms agreed or penalties should be applied. Hides the high complexity in the current Grid infrastructure to users Reduces the human interaction in business tasks by automating them Providing easy way of usage Outsourcing of infrastructure capabilities, to reduce the investment in hardware and software SaaS model can be applied Reliability Enhanced Security and Privacy Increases business competitiveness SLA guaranteed with penalties in case of violations The framework is dynamic and can adapt to changing situations Self-Management, Self-Configuration Complex collaboration chain, driven by each party's business objectives Enterprises pursue their own business objectives Optimized business benefits for all parties Privacy and confidentiality of data with encrypted communications and applied security policies Trust in enterprises (enterprise historical reputation) BREIN - Semantic Week 09

5. The team • Coordinated by Telefonica I+D and technically lead by U. Stuttgart • 16 partners with experience in Workflow Management, Multi-agent technologies, Business Process Modelling, Security, HPC and Semantic technologies. • Strong emphasis on industrial partner scenarios; visionary scenarios (10 years vision) and the validation scenarios (what can be shown short term). • ANSYS is leading the Virtual Engineering Scenario: use HPC and traditional computational Grid but want to increase flexibility, agility, reliability to provide new services to their customers • Stuttgart Airport: Bring Grid Computing processes to manage ground handling services and resources: buses, passengers, airplanes, catering, fuelling, luggage transportation, etc. BREIN - Semantic Week 09

6. Presentation Outline • BREIN Vision, Overview, Scenarios • Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles • BREIN Ontologies • Knowledge Aware Grid Services in BREIN • What to take away BREIN - Semantic Week 09

7. Semantic Grid Principles Embedding and implicit metadata is the enemy of shareability and reuse in an open and decoupled and collaborative environment.Expose it.Manage it.Make it a first class citizen.Machine processable metadata is machine actionable metadataEnrich it.With meaning.Semantics. Systematic management of metadata in Grid middleware Semantic enrichment of metadata in Grid middleware Source: Carole Goble

8. Service-Oriented Knowledge Utility The architecture comprises services which may be instantiated and assembled dynamically, hence the structure, behaviour and location of software is changing at run-time A utility is a directly and immediately useable service with established functionality, performance and dependability, illustrating the emphasis on user needs and issues such as trust Services are knowledge-assisted (‘semantic’) to facilitate automation and advanced functionality, the knowledge aspect reinforced by the emphasis on delivering high level services to the user Source: David De Roure

9. Presentation Outline • BREIN Vision, Overview, Scenarios • Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles • BREIN Ontologies • Knowledge Aware Grid Services in BREIN • What to take away BREIN - Semantic Week 09

10. Service Customer – Provider Interaction Lifecycle Capture Business Process Dissolve BOC Promote ED Workflow Engine Create Workflow Use Service SA-SLA Semantic SLA Negotiation Select Service Discover Service QoS Service Selection Negotiate BREIN - Semantic Week 09

11. Service Provider – Provider Interaction Lifecycle Negotiate Semantic Scheduler Dissolve Semantic Service Offer Discovery Schedule resources Multi-agent decision making Adapt SA-SLA Outsource Resources Semantic SLA Negotiation Monitor Resources BREIN - Semantic Week 09

12. Presentation Outline • BREIN Vision, Overview, Scenarios • Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles • BREIN Ontologies • Knowledge Aware Grid Services in BREIN • What to take away BREIN - Semantic Week 09

13. Architecture Overview BREIN - Semantic Week 09

14. The Pillars of BREIN Semantic Infrastructure Specification for semantic Annotations (SA-SLA) - Backward compatible - Light weight approach • Conceptual model • - Business ontology • - QoS ontology • Technology ontology • Grid Resource Ontology • Knowledge Aware Grid Services • Semantics Scheduling • SLA negotiation & matching • Workflow execution • Multi-agents • Architecture • S-OGSA • BREIN Semantic Infrastructure BREIN - Semantic Week 09

15. The Pillars of BREIN Semantic Infrastructure • Architecture • S-OGSA • BREIN Semantic Infrastructure BREIN - Semantic Week 09

16. S-OGSA Model Knowledge Service Grid Service Is-a Is-a Is-a Semantic Binding Knowledge Entity Grid Entity 1..m 1..m 0..m 0..m Is-a Is-a Is-a Knowledge Resource Grid Resource Is-a Is-a Is-a Ontology Rule-Base Virtual Machine Airport Bus BREIN - Semantic Week 09

17. S-OGSA Model • Semantic-OGSA • Semantic Grid Reference Architecture • Alow-impact extension of OGSA • Mixed ecosystem of Grid and Semantic Grid services • Services ignorant of bindings • Services binding aware but unable to process them • Services binding aware and capable of processing (part of) them • Everything is OGSA compliant Model expose provide/ consume Mechanisms Capabilities use Final review, Manchester, 17th July 2007

18. Presentation Outline • BREIN Vision, Overview, Scenarios • Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles • BREIN Ontologies • Knowledge Aware Grid Services in BREIN • What to take away BREIN - Semantic Week 09

19. The Pillars of BREIN Semantic Infrastructure • Conceptual model • - Business ontology • - QoS ontology • Technology ontology • Grid Resource Ontology • Architecture • S-OGSA • BREIN Semantic Infrastructure BREIN - Semantic Week 09

20. The BREIN Roadmap Business Usage Evaluation Profiles Process Structure ... Semantic Week

21. Semantic Modelling Services Ontology feedback Modelling process using card sorting Top-down by domain experts Ontology input Bottom-up by knowledge engineers Ontology Domain input Domain feedback Modelling process using BPM4SOA Semantic Week

22. Conceptualmodel Information involved Ontologies Domain independent QoS Ontology Business Ontology Technology Ontology Sector (scenario) dependent VE Service VE Resource Grid Resource Enterprise-specific domain dependent ANSYS Amazon BREIN - Semantic Week 09

23. The Pillars of BREIN Semantic Infrastructure Specification for semantic Annotations (SA-SLA) - Backward compatible - Light weight approach • Conceptual model • - Business ontology • - QoS ontology • Technology ontology • Grid Resource Ontology • Architecture • S-OGSA • BREIN Semantic Infrastructure BREIN - Semantic Week 09

24. SA-SLA: Motivation, problem area • Semantic Interoperability during negotiation of SLAs • Several competing protocols • Different terminologies between Service Providers • Different metrics used for definition of QoS • Different types of services or resources from Service Providers • Different benchmarking methods • Different languages • Providers and consumers are collaborating on a global scale • New specifications will just add more confusion and introduce new interoperability problems • Modifying existing specifications without thinking of backward compatibility will increase interoperability problems BREIN - Semantic Week 09

26. Presentation Outline • BREIN Vision, Overview, Scenarios • Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles • BREIN Ontologies • Knowledge Aware Grid Services in BREIN • What to take away BREIN - Semantic Week 09

27. The Pillars of BREIN Semantic Infrastructure Specification for semantic Annotations (SA-SLA) - Backward compatible - Light weight approach • Conceptual model • - Business ontology • - QoS ontology • Technology ontology • Grid Resource Ontology • Knowledge Aware Grid Services • Semantics Scheduling • SLA negotiation & matching • Workflow execution • Multi-agents • Architecture • S-OGSA • BREIN Semantic Infrastructure BREIN - Semantic Week 09

28. Negotiation example • RAMMemory: 7.5 GB • ComputeUnit: 4 ECU • Storage: 850GB • Platform: 64 bit • Price: $0.4 per instance hour Negotiation AMAZON • ANSYS request • CPUName: IntelCore Duo • CPU Speed: 2 GHz • Capacity: 400 MB • Price: 27 euros per day • DiskSpace: 250GB Negotiation • MemoryPerTask: 7.5 GB • ClockCPUSpeed: 100 MHz / process • StorageCapability: 850GB • Cost: 5 euros/task/hour CUSTOMER Software engineering company BSC 29

29. SLA Negotiation Architecture Basic Principles • Use annotations only when you need them • Ignore annotations if your SLA negotiator does not understand them • Use SLA mediator and Common Ontology to request matching information BREIN - Semantic Week 09

30. Semantic Provisioning Service: Annotation tool I

31. Annotation tool II

32. Metadata Management within the Infrastructure • Now I have an SLA, how do I deal with it? • Need a flexible and adaptive infrastructure to support it • Failure to satisfy an SLA means penalties and reputation damage • Things change too frequently for administrators to react • Need automation • Need intelligent decision making • I also need Cloud Computing as an outsourcing option BREIN - Semantic Week 09

33. Semantic Scheduler BREIN - Semantic Week 09

34. Allow integration with Clouds • Outsource Service when can’t handle locally • Local resources unavailable • QoS level not available • Customer does not see this happen • They just asked for service • Service Provider needs… • Place that can achieve the same task • Control over QoS level, price, etc. • Ability to use multiple second-tier Service Providers BREIN - Semantic Week 09

35. What to take away • Semantics can be found throughout the lifecycle of business collaborations • Metadata carry knowledge and they need to be managed in a systematic and principled manner • BREIN brings Grids to Business and Semantic Technologies are the transport vehicle • BREIN applies semantic technologies in order to improve automation, interoperability, simplicity, flexibility, reliability, and extensibility • BREIN wants to apply successful Semantic Technologies from other projects (already extends OntoGrid and UniGrids) BREIN - Semantic Week 09

36. Thank you for listening Any questions? Acknowledgements The Semantic Group of the BREIN Consortium John Brooke and Carole Goble

37. Backup Slides BREIN - Semantic Week 09

38. BREIN Ontologies imports Taken from SUPER S-BPMN Business layer QoS ontology • Annotate SLAT files We could add BPMO Business Ontology • Allow to link business activities with IT implementations • Allow describe non-funtional properties Implementation layer OWL-S OWL-WS Services IT Workflow Infraestructure layer Technical ontology BREIN - Semantic Week 09

39. Tools and components which use it • Tools which allow for annotating non-functional descriptions • SASLAT GUI: It allow for annotating SLA parameters in TSLA by QoS ontology. • SLA translator (SLAT): Ontology manager which stores the QoS ontology. • Service description GUI: It is a GUI to create semantically service descriptions and annotate non functional properties with the business ontology. • Workflow Editor: A tool to draw business process in terms of workflow, which allows users to describe businesses processes properties by using business ontology. • BREIN components which will be reasoner with business ontologies • SESS: The service selection is based on service non-functional properties (like QoS metrics) which are annotated in SLA files by semantic metrics. • SLA Negotiator: Since the SLA files that the SLA Negotiator is working on, are annotated semantically, it will consume the QoS ontology in order to understand the metrics semantically annotated. • BREIN Software Agents: Software agents use semantically annotations of web services they represent when communicating with other agents; thus such annotations will also be used on the conceptual level of agent-to-agent communication. Annotations with regard to the BREIN Business Ontology are required for reason about received messages from other agents. BREIN - Semantic Week 09