manAge an agent architecture for manufacturing control

  • 格式:pdf
  • 大小:89.03 KB
  • 文档页数:10

manAge: an agent architecture for manufacturing controlTapio HEIKKILÄVTT Automation, Machine Automation, PO Box 13023, FIN-90571, Oulu, Finlande-mail : Tapio.Heikkila@vtt.fiMartin KOLLINGBAUMUniversity of Cambridge, Department of Engineering, Institute for Manufacturing,Mill Lane, Cambridge, UK CB2 1RXe-mail : mjk27@eng.cam.ac.ukPaul VALCKENAERSKatholieke Universiteit Leuven, Department of Mechanical Engineering,Celestijnenlaan 300B , B-3001 Leuven, Belgiume-mail : Paul.Valckenaers@mech.kuleuven.ac.beGeert-Jan BLUEMINKVTT Automation, Machine Automation, PO Box 13023, FIN-90571, Oulu, Finlande-mail : geert-jan.bluemink@vtt.fi

AbstractIn this paper we introduce agent concepts to implement control algorithms and application architectures forflexible control in manufacturing. We list requirements for the implementation of the agent itself, assessexisting concepts of agent architectures, and give a more detailed overview about the building blocks of anadequate agent system architecture by describing the “manAge” agent system implementation.

1. IntroductionThere is a variety of manufacturing controlparadigms, which are investigating solutions forsystems of high flexibility, from the point of view ofoperating the system (systems operation aspects) aswell as maintaining the system structures andconfigurations (systems engineering aspects).According to Dilts et. al. (1990) flexibility is anessential property of systems, which follow theconcept of distributed or partly distributedarchitectures. From this point of view it isunderstandable that agent technologies are adoptedto design and implement flexible systems inmanufacturing. Agents provide the structural andoperational flexibility as a built-in property. In thispaper we therefore describe a specific agentarchitecture, “manAge”, which provides genericspecifications and structures for agents inmanufacturing applications. As the “manAge”concept is intended to be used in real-worldenvironments, we are considering reliability as animportant aspect. For this we include persistent datamanagement facilities into the agent architecture,which allows an agent to handle information and

knowledge in a persistent way. This should enableagent-based control applications to recover fromfatal system failures. Guilfoyle and Warner (1994) list followingproperties, which comprise an agent architectureand must be tackled in a development process:• agent organisation (span of control, roles,chain of commands)• agent roles (different roles during problemsolving, e.g. managers, workers, disputees)• agent coupling (balance between interactingand problem solving), e.g. loosely coupled(low interaction, high problem solving),tightly coupled (high interaction, lowproblem solving)• agent communication (organisation,common languages), e.g. low levelprotocols (send, receive), high levelprotocols (contract net, speech acts)• agent interaction (how effect to each others,change common environment), e.g. co-operation, competition, hostility• agent complexity/sophistication (problemsolving ability), e.g. coarse grained (few,clever agents), fine grained (many simpleagents), cognitive (model of itself andothers), non-cognitive (no internal model)We use agents in application environments, whereagents have to control and (at least partly) plan theirlocal operations, cope with uncertainty by reactingto unforeseen events (disturbances), and have torecover from such situations without disturbingglobal goals like throughput maximisation. Planningis here considered to cover all the calculations toprepare a control strategy before execution. Wetherefore add additional requirements for agentarchitectures to those above. We distinguishbetween requirements, which are related to theagent system and those, which are purely agentrelated. In terms of agent-system relatedrequirements we identify following aspects:• different categories of agents, specialised inways characteristic to the categories• knowledge or access to knowledge on typesof agents and availability of them to theother agents• communication of manufacturingknowledge, e.g., product knowledge(BillOfMaterials) and productionknowledge (process plan)• communication of process knowledge(resource eligibility, productionplans/programs, etc.) between agents• communication of process executionknowledge between agents (goals, state &load level of resources, etc.)As agent-related aspects we list the following:• planning/decomposition of global goals(orders) to local goals (local orders) withinthe resources (accept changes)• management of local goals (orders), plans(production programs) and state information(load levels)• connection to physical equipment withinresource agents• detect disturbances by observation ofabnormalities on-line (accept externalevents or events from the physical resource)• manage the plan execution byreceiving/accepting process executionevents from other agents and equipment