1 / 36

HOLONIC ENTERPRISE AS A COLLABORATIVE INFORMATION ECOSYSTEM

. FIPA Meeting London, UK 2001. HOLONIC ENTERPRISE AS A COLLABORATIVE INFORMATION ECOSYSTEM. MIHAELA ULIERU. INTELLIGENT SYSTEMS GROUP HEAD: Dr. Douglas Norrie http://isg.enme.ucalgary.ca The University of Calgary CANADA. HOLONIC ENTERPRISE.

aclair
Télécharger la présentation

HOLONIC ENTERPRISE AS A COLLABORATIVE INFORMATION ECOSYSTEM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIPA Meeting London, UK 2001 HOLONIC ENTERPRISE AS A COLLABORATIVE INFORMATION ECOSYSTEM MIHAELA ULIERU INTELLIGENT SYSTEMS GROUP HEAD: Dr. Douglas Norrie http://isg.enme.ucalgary.ca The University of Calgary CANADA

  2. HOLONIC ENTERPRISE • HOLARCHY of Collaborative Enterprises (Entity: Systems, “things”, AGENTS) - holons • Balance AUTONOMY - COOPERATION • Replicationinto self-similar structures at multi-resolution levels (fractal)

  3. HOLONIC ENTERPRISE ENTERPRISE Field Cluster CC CC RESOURCEr EC RESOURCE EC CC CE CE CE RESOURCE EC CE CE CE CC CC RESOURCE ENTERPRISE CE CE CE EC RESOURCE EC CE CE CE CE CE CE CC CC RESOURCEr EC RESOURCE EC CC Dynamic Virtual Cluster CE CE CE RESOURCEr EC CE CE CE CE CE CE Field Cluster HOLONIC ENTERPRISE AS A HOLARCHY

  4. COLLABORATIVE LEVELS • 1. INTER-ENTERPRISE (supply chain) • 2. INTRA-ENTERPRISE (planning/scheduling • 3. MACHINE CONTROL (manufacturing) • ? What do we ABSTRACT into agents at each Level - to provide the desired functionality/results

  5. Timeout A Request A Ready A Waiting A Requested A-B Waiting B Reply B Ready B Request B Timeout B Requested B-C Ready C Reply C Reply C IE:ASP: EE:ANS: Inference EngineActive Schema Pool Execution EngineAgent Naming Sub-system Flow of Information between the Inter and Intra-Enterprise Levels University of Calgary Intelligent Systems Group Calgary, Alberta, Canada InterfaceAgent • Group behaviors • Task • Agent classes • Interaction patterns • Coordination constraints • Task ordering constraints • Results constraints: task- related information, topics • Execution constraints • ACL message protocols Request Reply CollaborativeAgent Model Request Reply Conversationschemata KnowledgeAgent Database Specify Deploy Convert Conversation Managers (centralized or distributed) Java threads Colored Petri Nets Abstract conversation Schema Verify Production Planning Scenario Message IE I/O Schemaclass Recognizing Situation EE Selecting a rule ASP Rule variableinitialization SchemataLibrary Executing the rule Agentnaming Sending messages ANS Conversation Manager Updating and Memorizingstate information Schemainstance YP Schema execution Schema instantiation Internal Conceptualization of a Conversation Manager Conversation Schema as a Colored Petri Net Schema instantiation and execution

  6. Task Task Decomposition Sub-Task Sub-Task Sub-Task Virtual Cluster 1 Virtual Cluster 2 Partial Cloning Partial Cloning Machine1 Machine2 Tool1 Tool2

  7. PATTERNS OF HOLONIC COLLABORATION • Common mechanisms that characterize the information ecosystem created by the three levels of a holonic enterprise: • Dynamic Virtual Clustering configured to minimize cost and enabling for flexible, re-configurable structures • Mediator Agent (decisions on cluster configuration) • Partial Cloning (enterprises, internal resources, physical machines)

  8. METAMORPHIC ARCHITECTURE HOLONIC ENTERPRISE

  9. HOLONIC PATTERNS INTERACTION

  10. TASK DECOMPOSITION • Task distribution among the cluster’s entities (“outside-in view” from the Mediator to each collaborative entity • Task deployment within each entity (“inside-out” view from the entity to the Mediator) • ONTOLOGY “PATTERN”: - “peer-to-peer” (task distribution) - “inter-level” (task deployment)

  11. INTER-ENTERPRISE

  12. The Networked Economy Wireless Portal eMarketplace

  13. Business Model in the 20th Century Customers Suppliers Partners Employees

  14. Business Model in the 21st Century Enterprise Portals enable Integrated and sharing of Information, Services and Applications among Suppliers, Employees, Partners and Customers. Customers Suppliers Partners Employees

  15. What is a Portal? Targeted Communities Key Services Aggregated for... Employee Employee Content Content Communication Supplier Communication Supplier Collaboration Any Device Access Collaboration Partner Partner Commerce Commerce Customer Care Customer Care Customer Customer

  16. Channel Partner Supplier Firm Customer Enterprise Information Portals Transform the Business Value Chain Traditional Model of Business Value Chain Firm Becomes… Partners Suppliers The Enterprise Information Portal Customer Portal Enabled Business: “iValue Chain”

  17. INTER-ENTERPRISE • FORCES TO BE BALANCED: - Cost Minimization (maximum synergy: cluster the ‘best’ partners) - BALANCE Autonomy-Cooperation - ‘On-demand’ tracking; on-line failure reporting - On-line re-configuration (to keep ‘optimal’ cluster)

  18. VIRTUAL ORGANISATIONS

  19. SERVICES AND MECHANISMS • Metamorphic Architecture: Interoperability (FIPA); Security Standards • Virtual Clustering: Mediator needs Grouping Policies (obligation, authorization, constraining). Contractual frameworks that enable nested management structures in policy-restraining contexts and under security constraints (COOPERATION DOMANINS)

  20. THE COOPERATION-COMMUNICATION LAYER infrastructure • URL: [protocol://] [id@] host : port [/path] An Architecture for Collaborative MAS23

  21. PARTIAL CLONING • ATTRIBUTES to be abstracted into agents: which goods and services does the enterprise provide and what makes its competitive advantage?; marketing strategies (attributes that enable penetration into a cluster and be chosen when a new cluster is formed)

  22. MEDIATOR • “INSIDE-OUT” - Enterprise-to-cluster negotiation: ISSUE: obtain and maintain the TRUST of the mediator in charge with the coordination of the collaborative cluster • “Otuside-In” - Cluster-to Enterprise decisions: Flexible Utility Function (is cost of keeping the partner worthwhile). [Jennings - “keep partner whose proposal is most similar to opponent’s last offer, but whose trust degree is higher”

  23. Task Distribution/Decomposition • Mediators can enforce Compliance Mechanisms (e.g. ‘reputation’ and ‘regimentation’) on the partners to coerce them to fulfill their obligations. • Negotiation Frameworks (Jennings) using ‘influence’ (Interactive contractual design)

  24. INTRA-ENTERPRISE • FORCES TO BE BALANCED: • 1. Need to keep one’s position within the collaborative cluster • 2. Need to stay Competitive • REQUIRED SERVICES: • 1. Dynamic scheduling to accommodate new orders “on the fly” (re-prioritize; re-configure) • 2. Security Policies; Advertising; Bidding; Interfacing with each cluster; “look-out”

  25. PATTERNS • Mediator Agent: channels all access to the system to ensure security and robustness of the collaborative ecosystem inside the enterprise (Static and Dynamic Mediators) • Dynamic Virtual Clustering: GT • Task Decomposition: On-line re-scheduling of the production resources (e.g. EA) Work flow reconfiguration across the organization • ONTOLOGIES: deploy scheduled task down to the machine control level (Jim Christensen)

  26. A Robust, Scalable Infrastructure Platform Sun’s Three Main Investment Areas Massive Scale H/W S/W Integratable Stack Continuous Real-time

  27. MACHINE CONTROL LEVEL • GOAL: ensure production continuity through machine reliability and rapid reconfiguration in case of break-down • FORCES: enable user to develop the application by ‘plugging’ function blocks; compile the code and distribute it on the appropriate resources for execution; manage timing and precedence relationships while executing the distributed FB; safety, etc.

  28. MACHINE LEVEL • Self Configuration and Dynamic Reconfiguration of Intelligent Machines (physical holons) • Deployment of self-(re)configuring, intelligent, distributed automation elements. • Ontologies for manufacturing process-task-operation-controller (e.g.function block) mapping (e.g., PSL)

  29. PATTERNS OF HOLONIC CONTROL

  30. Mapping Holonic Systems into MAS via Mediators

  31. PURPOSE OF PD&M • These patterns have specific particularities within each level of the collaborative holarchy. • The purpose of our work is to identify these particularities and clearly define the mechanisms that would enable their implementation on the grounds offered by the FIPA architecture: • E.g. ONTOLOGIES: inter-’thing’ communication • Agent - ‘peer-to-peer’ • Level: deployment (‘outside-in’); bidding/advertising (‘inside-out’)

  32. NEXT MEETING OF THE PD&M WG • ACAI 01 – Summer School Multi-Agent Systems and their Applications http://cyber.felk.cvut.cz/ACAI01 • Prague, July 2-13, 2001 • joint event of AgentLink, ECCAI, CTU and University of Vienna • 24 invited lecturers (K. Sycara, E. Durfee, M. Wooldridge, M. Tambe, S. Kraus, Y. Demazeau, F. Labrou, W. Wahlster) • accompanied by workshops and student sessions

More Related