Multi-Agent Based ERP

2003. 10. 10.

MAI Lab.

Joon Kim

A prototype multi-agent ERP system:

an integrated architecture and a conceptual framework

Bih-Ru Lea, Mahesh C. Gupta, Wen-Bin Yu Department of Business Administration, School of Management and Information Systems, University of Missouri Department of Management, College of Business and Public Administration, University of Lousville Department of Information, Science and Technology, School of Management and Information Systems, University of Missouri Technovation(2003)

Contents

   Problems with existent ERP systems Software agent MAERP architecture *MAERP: Multi-Agent based ERP

MAI Lab. Oct.

3/25

Problems with ERP implementation

  Technical aspects  Technology readiness of an organization    Complexity of commercial ERP software Data loss due to the compatibility of data architectures Adequacies of redesigned business process Organizational factors     Resistance to change Inadequate training Underestimated implementation time and cost Strategic view of technology adoption

MAI Lab. Oct.

4/25

Software agent

 Properties     Autonomy Social ability – communication Reactivity Pro-activeness

MAI Lab. Oct.

5/25

Software agent

 Capabilities        Exploiting domain knowledge Tolerating error Using symbols and abstractions Exhibiting goal-oriented behavior Learning from the environment Operating in real time Communicating using natural language

MAI Lab. Oct.

6/25

Software agent

 Types of software agents        Collaborative Interface Mobile Information/Internet Reactive Hybrid Smart

MAI Lab. Oct.

7/25

…

MAERP

*

architecture

Users in department j Interface Agent j Coordination Agent j Intranet/network Users in department i Interface Agent i Coordination Agent i … Data Collection Agents j Task Agents j 1 … Task Agents j n Data Collection Agents i Task Agents i 1 … Task Agents i n *MAERP: Multi-Agent based ERP

MAI Lab. Oct.

8/25

MAERP architecture

    Coordination agent Data collection agent Task agent Interface agent

MAI Lab. Oct.

9/25

MAERP architecture

 Coordination agent      Receiving instruction from / reporting to human users via an interface agent Assigning data collection / receiving data from a data collection agent Relaying the dataset Assigning tasks to / receiving feedback from task agents Communicating with other coordination agents

MAI Lab. Oct.

10/25

MAERP architecture

  Coordination agent Data collection agent     Retrieving information requested by its coordination agent Querying specific DBs within the department Performing data warehousing Preparing dataset on request from coordination agent

MAI Lab. Oct.

11/25

MAERP architecture

   Coordination agent Data collection agent Task agent    Receiving data from coordination agent Performing data analysis Reporting the results back to coordination agent

MAI Lab. Oct.

12/25

MAERP architecture

    Coordination agent Data collection agent Task agent Interface agent    Communicating b/w human users and a coordination agent Interpreting results Preparing reports for human users

MAI Lab. Oct.

13/25

MAI Lab. Oct.

14/25

Revolutionising Plant Automation – The PABADIS

*

Approach

PABADIS White Paper Project by the European Community under the “Information Society Technology” Programme(1998-2002) *PABADIS: Plant Automation Based on Distributed Systems

PABADIS project overview

   International IMS research project Partners  Greece, France, Austria, USA, Canada, Switzerland & Germany Objective  To enable environment an with innovative scalable plug-and-participate and context driven adaptability and flexibility from the ERP-System to the single machine control in single piece production plants

MAI Lab. Oct.

16/25

Motivation

Transition from rigid to reconfigurable system

MAI Lab. Oct.

17/25

Motivation

  Reconfigurability and flexibility Advantages of mobile agents     Reducing network load Actual condition of a plant decided by agents No permanent network connection needed Increasing the flexibility of the system

MAI Lab. Oct.

18/25

General idea

    Automation using distributed systems Flattening network hierarchy IP-based networks down to the control level Plug-and-participate environment Agents assigned to each physical instance Tightly connected information

MAI Lab. Oct.

19/25

System topology

* *CMU: Cooperative Manufacturing Units

MAI Lab. Oct.

20/25

Agent types

   Residential agents  Interface b/w CMUs and the agent community  Tied to specific CMU Product agents    Associated with actual work pieces Control the manufacturing process Scheduling, resource allocation, reporting Plant management agents  Organize the system-wide mfg. Process  Quality management, reporting

MAI Lab. Oct.

21/25

Workflow in a PABADIS plant

*RA: Residential Agent

MAI Lab. Oct.

* 22/25

Communication b/w LUS

*

& agents

*LUS: Look Up Service

MAI Lab. Oct.

23/25

Benefits

   System flexibility improvement  Vertical flexibility   Distribution of MES functions Use of mobile product agents  Horizontal flexibility  Easy system redesign Simplification of system design   Reduction of the production process control Plug-and-participate technology Refinement of the SCM   Increased system clarity and system openness Extending the system to the whole supply chain

MAI Lab. Oct.

24/25

Application areas

      Production with a high variation and small lot size Furniture industry Car manufacturing Auto industry suppliers Ancillary industry of aerospace industry Ancillary industry of machine building

MAI Lab. Oct.

25/25