160 likes | 283 Views
A Usage-Based Unified Resource Model. 24th International Conference on Software Engineering and Knowledge Engineering - SEKE 2012 1st of July 2012. Yves Wautelet Samedi Heng Manuel Kolp (Presenter). Outline. Problem Statement Resource Ontology Case Study Conclusion and Future Work.
E N D
A Usage-Based Unified Resource Model 24th International Conference on Software Engineering and Knowledge Engineering - SEKE 2012 1st of July 2012 Yves Wautelet Samedi Heng Manuel Kolp (Presenter)
Outline • Problem Statement • Resource Ontology • Case Study • Conclusion and Future Work
Research Context: Resources are Everywhere Human Agent Team Resource Objects Human Agent Competency They all have a usage Software Agent Functionality
IS Require Resources to Realize Services Resource Interfacing requires standardization Interface Information Systems Service Realization Resources
Competency and Functionality: What For? Contract • … to deliver services! • Service Realization depends of Resources • Resources are complex elements • Quality • Cost of Use • Status • Configuration • …
Case Study: Coking Plant By essence an Resource-Oriented world Hundreds of different types of agents : software, machines, automates, humans, sensors, effectors, controllers, pyrometers, mobile devices, conveying belts, etc Advantages in information management, process automation, resource and production planning, decision making, etc.
Sintering Blast furnace Coking Plant 4 Marcinelle Marchienne Marcinelle Steel plant Electric furnace Marcinelle Marcinelle Continuous casting slabs Marcinelle Pocket metalurgy Marcinelle
Contribution of the Ontology Application and Lessons Learned Technical details can be found in the paper Improves the structural complexity i.e. the application design with respect to defined metrics Unified catalogue of available resources in the form of a yellow page system: allowed a better dynamic resource utilization Redefinition of resources as runtime dynamic elements. Default object-oriented development used resources as static and passive Better global understanding of resource utilization. Allows the identification of possible bottlenecks and re-optimize the production planning for adequate resource utilization
Contribution of the Ontology Application and Lessons Learned (cont’d) Computing and storing into the caching system for pre-positioning of resources such as the pusher machine, coke car and guide coke. Expressing the process from a resource-based point of view which allows focusing on interoperability and evolutionary aspects.
Conclusion and Future Works • Heterogeneous resource allocation supported by active software • Conceptual model which proposes to centralize resources’ offer and demand through the concepts of functionality and competency • Common semantic for consumers (i.e. services) to rent resources that can themselves advertise their offer so that consumption contracts can be set up • Future work include: • Extending the ontology with a process covering the whole software development life cycle from (agent-based) analysis to service level agreements. • The development of a dynamic dimension allowing to document and implement a multi-agent system resources management as well as the realization on a case study in the field of outbound logistics is under progress.