Semantic Technologies in the Business Grid Collaboration Lifecycle Dr Ioannis Kotsiopoulos Page 1BREIN - Semantic Week 09

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 2BREIN - Semantic Week 09

BREIN Vision Objectives To take the Grid to business ‘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) Create an infrastructure that will increase the level and dynamism of collaborations among companies, with special focus on SMEs 3BREIN - Semantic Week 09

BREIN Vision in Business Terms Business aspects will be improved with this project: Privacy and confidentiality of data with encrypted communications and applied security policies Trust in enterprises (enterprise historical reputation) 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 Cost Reduction Simplicity for users Service Level Agreement Reliability Increases business competitiveness Enhanced Security and Privacy SLA guaranteed with penalties in case of violations The framework is dynamic and can adapt to changing situations Self-Management, Self-Configuration Outsourcing of infrastructure capabilities, to reduce the investment in hardware and software SaaS model can be applied Complex collaboration chain, driven by each party's business objectives Enterprises pursue their own business objectives Optimized business benefits for all parties 4BREIN - Semantic Week 09

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. 5BREIN - Semantic Week 09

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 6BREIN - Semantic Week 09

Semantic Grid Principles 7 Systematic management of metadata in Grid middleware 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 metadata Enrich it. With meaning. Semantics. Semantic enrichment of metadata in Grid middleware Source: Carole Goble

Service-Oriented Knowledge Utility 8 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 The architecture comprises services which may be instantiated and assembled dynamically, hence the structure, behaviour and location of software is changing at run-time Source: David De Roure

Business Grid Collaboration Lifecycle The actors –Typical Service Consumers; i.e. an engineer who wants to use a simulation service –Service Provider; i.e. A software company that wants to offer its software as a services –Service Provider (or Cloud Provider); a company like Amazon that wants to offer its resources as a service The BREIN Lifecycle –External: Capture Business Process, Create Workflow, Discover Service, Negotiate, Select Service, Use Service, Dissolve –Internal: Negotiate, Schedule resources, Outsource Resources (external lifecycle), Monitor Resources, Adapt, Dissolve 9BREIN - Semantic Week 09

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 10BREIN - Semantic Week 09

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

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

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 13BREIN - Semantic Week 09

Architecture Overview BREIN - Semantic Week 09 14

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

The Pillars of BREIN Semantic Infrastructure Architecture -S-OGSA -BREIN Semantic Infrastructure Architecture -S-OGSA -BREIN Semantic Infrastructure 16BREIN - Semantic Week 09

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

18Final review, Manchester, 17th July 2007 S-OGSA Model –Semantic-OGSA –Semantic Grid Reference Architecture –A low-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 Capabilities Mechanisms provide/ consume expose use

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 19BREIN - Semantic Week 09

The Pillars of BREIN Semantic Infrastructure Conceptual model - Business ontology - QoS ontology -Technology ontology -Grid Resource Ontology Conceptual model - Business ontology - QoS ontology -T-Technology ontology -G-Grid Resource Ontology Architecture -S-OGSA -BREIN Semantic Infrastructure Architecture -S-OGSA -BREIN Semantic Infrastructure 20BREIN - Semantic Week 09

The BREIN Roadmap Semantic WeekPage Usage Evaluation Structure Process Profiles Business

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

Conceptual model Information involvedOntologies Domain independent Business OntologyTechnology Ontology Sector (scenario) dependent QoS Ontology VE ServiceVE Resource Enterprise-specific domain dependent ANSYSAmazon 23BREIN - Semantic Week 09 Grid Resource

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

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 25

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 27BREIN - Semantic Week 09

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

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

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 SLA Negotiation Architecture

Semantic Provisioning Service: Annotation tool I

Annotation tool II

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 34BREIN - Semantic Week 09

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) 36BREIN - Semantic Week 09

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

Backup Slides 38BREIN - Semantic Week 09

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

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. 40BREIN - Semantic Week 09