Agent-based Virtual Organization by klutzfu53


									Agent-based Virtual Organization

    Michał Szymczak, Grzegorz Frąckowiak,
           Maria Ganzha, Maciej Gawinecki,
      Marcin Paprzycki, Myon-Woong Park

         Systems Research Institute
         Polish Academy of Science
➲   Organization → team(s) engaged in project(s)
➲   Completion of project requires
    ●   cooperation between workers (team members)
    ●   sharing information between
        ●   workers in a team
        ●   teams
    ●   resource / information provisioning / flow
        ●   based on
            ●   hierarchical structure of team(s) and of the organization
            ●   “needs” of individual workers
    ●   generation of reports
    ●   task scheduling
    ●   quality control
    ●   etc...
Representation and Adaptation – what?
➲    Representation of domain specific knowledge
➲    Representation of structure of interactions
    ● flow of resources
    ●   organization → hierarchical structure
        ●   workers → team
        ●   team has manager(s) that have managers that have…
    ●   every member of an organization „has” role(s)
        ●   duties, responsibilities, tasks, reports, …
➲   Representation of user profiles:
    ●   interests, skills, needs
➲   Adaptability – what evolves?
    ●   organization
    ●   different project – different roles / interrelations
    ●   project(s) over time
    ●   interests, skills, needs of workers
Representation and Adaptation – how?
➲   Ontologies
    ●    “everything” → ontologically demarcated resource
        ●   human or non-human
    ●    every resource has (at least one) profile
        ●   for human resource – samples:
            ●   experience (Experience Profile)
            ●   personal information (Personal Profile)
            ●   position within the organization (Organization Profile)
➲   Software agents
    ●    human resources “have” Personal Agents (PA)
        ●  represent workers in the Virtual Organization (VO)
        ● support humans in fulfilling assigned roles
    ●    agent interactions – organizational structure
                      Virtual Organization
➲   Standard (e.g. Wikipedia)
    ●   group of individuals
    ●   geospatially distributed
    ●   working together
➲   Here
    ●   existing “real” organization mapped into an agent-
        based organization in which the key concepts are
        ●   notion of a resource uniformly applied to all entities
        ●   ontological demarcation of resources
            ●   domain specific ontology
            ●   ontology of an organization
            ●   agents and their interactions represent structure of the organization
AML Social Model
    Found Approaches – Ontologies
➲   TOVE – University of Toronto
    ●   based on research in actual structure of an enter-
    ●   Prolog based
    ●   does not seem to be active since February 2002
➲   OntoWeb
    ●   based on RDF Schema
        ●   RDF Schema do not allow use of quantifiers – reduce
            available reasoning
    ●   lack of support for access restrictions
Basic (Generic) Resource Profile
Privilege Profile
IST Experience Profile
                        Roles and Agents
➲   Developing agent systems → Prometheus /
    Gaia way
    ●   start with roles
        ●   modeling of the “nature of the problem domain”
    ●   establish interactions
        ●   interaction is communication
        ●   interaction is messaging
        ●   no direct interactions (FIPA requirement)
    ●   roles (than interact) transformed into
        ●   agents
        ●   agent-teams
        ●   and their interactions
    ●   Agents in the system
        ●   VOAgent
            ●   core agent “skeleton”
            ●   can be adapted to take multiple roles
Role-focused Use Case Diagram
AML Mental Model
            Adaptability in the System (1)
➲   Scenarios
    ●   worker undertakes a new / changes role
    ●   new product to be serviced introduced to the system
        ●   workers need training
        ●   training should be representable in their profile
    ●   change in requirements of a project
    ●   workers leave and new workers come to the organi-
    ●   management predicts that a specific project is going
        to be introduced
    ●   management wants new area of competence to be
        added to the organizational portfolio
    ●   changes in the organizational structure
            Adaptability in the System (2)
➲   Approach based on DynamiCS Project
    ●   used in e-commerce
    ●   base / skeleton agents + modules dynamically load-
    ●   allows for minimizing network traffic
        ●   only what is needed is transported across the network
➲   VOagent → base agent
    ●   core extensions
        ●   Personal Agent (similar to P. Maes)
            ●   base functionalities (meeting scheduling, reporting, calendaring,
                searching for resources)
        ●   auxiliary agent(s)
    ●   extending to fulfill roles
Agent Adaptivity Injector Agent
Sample Applications
Duty Trip Application
      at the IST
➲   IST researcher
    ●   applies for a duty trip
    ●   IF the trip approved
        ●    Needs recommendations
            ●  who to visit?
            ● where to stay?
            ● where to eat?
        ●    Needs to file a Duty Trip Report
➲   Travel Support Subsystem
    → part of the OPM → con-
    sider that advising = provid-
    ing with focused list of re-
    Duty Trip
➲   Duty trip ontology
    links with the “ontolo-
    gy of travel”
    developed for the
    Travel Support Sys-
    ●   restaurant
    ●   hotel
    ●   golf (coming soon)
                   Training in the System
➲   Example of “different” adaptability
➲   User profile contains information about skills
➲   Scenarios
    ●   reactive
        ●   project tasks not completed “well”
            ●   QoS reports about it
        ●   project to be undertaken → missing skills in the organiza-
    ●   proactive
        ●   project(s) predicted / final stages of negotiation
        ●   management decides to modify organizational scope
➲   Competence Management Unit (role)
➲   Training Management Unit (role)
             Training in the System
➲   Activity diagram
    ●   role-based
                 Concluding Remarks
➲   System is being developed as we speak
    ●   interface (in Korean)
    ●   GIS component
        ●   use of Jena?
    ●   module injection
    ●   interface agent-world to non-agent world
    ●   ontological matching
    ●   recommender for the GA and DTS
➲   More about software agents and agent systems
    ●   Saturday after lunch
    ●   what would you like to see?

      OCTOBER 20-22, 2008

2008 International Multiconference on
  Computer Science and Information


To top