Skip to content

561 Group · Operations

MAPE-K: definition (Monitor, Analyze, Plan, Execute, Knowledge)

MAPE-K is the autonomic-computing control loop: Monitor, Analyze, Plan, Execute over a shared Knowledge base. The 561 Group applies it to a whole firm.

Operations

MAPE-K: definition (Monitor, Analyze, Plan, Execute, Knowledge)

MAPE-K is the reference architecture of autonomic computing in which a manager closes a control loop around a managed resource through four activities (Monitor, Analyze, Plan, Execute) that all read and write a shared Knowledge base. It was popularized by IBM's autonomic-computing program in the early 2000s and described by Kephart and Chess in 2003 (Kephart & Chess 2003)1 Jeffrey O. Kephart and David M. Chess. "The Vision of Autonomic Computing." Computer 36, no. 1 (2003): 41-50.. In the 561 Group it is the loop each agentic node runs.

What does each letter mean?

LetterActivityQuestion
MMonitorWhat does the managed resource look like now? Collect signals and turn them into observations
AAnalyzeIs adaptation required, and why?
PPlanWhat change should be made?
EExecuteApply the change through effectors
KKnowledgeThe shared models, policies, history and goals all four use

Where does the term come from?

Kephart and Chess proposed in 2003 that computing systems should manage themselves according to high-level objectives, borrowing "autonomic" from the autonomic nervous system. The vision organized self-management around four properties: self-configuration, self-optimization, self-healing and self-protection. The loop architecture was fixed in IBM's blueprint documents of 2004 and 2005. Its roots lie in cybernetics, the study of feedback and regulation founded by Norbert Wiener and developed by W. Ross Ashby.

What are the common misreadings?

Lenticule Science's survey lists three.

  1. It is not an algorithm. MAPE-K divides labor; it does not say whether analysis is rule-based, statistical or learned.
  2. The letters are not five services. An implementation may fuse stages or distribute the knowledge.
  3. K is not an appended database. It is the shared representation of goals, observations, admissible actions and uncertainty that lets the other stages understand each other.

The diagram also establishes none of observability, controllability, stability or safety. Those must be shown for the coupled system of loop, managed process and environment, and that is the open research problem the survey identifies.

How does the 561 Group use it?

The Group's design statement describes each node as running a service loop: paraconsistent, transfinitely valued data monitoring; content-addressed evidence-substrate analyzing; coordination-free deductive-truth planning; database-proof executing; through recursively self-improving knowledge. The firm's operating method adds verify and improve as explicit steps. Coesite Operations treats a company's recurring processes (publishing, repair, reconciliation) as loops with owned stages. See how to run a company as a MAPE-K loop and the design sentence, explained.

Is a loop an implementation?

No. A recorded requirement states that the Group wants to move toward treating its operations as MAPE-K loops; whether a specific loop runs is a dated question for the owning section.

Rendanheyi · Huidu Guanli · office and incumbency · research at Lenticule Science

References

  • Jeffrey O. Kephart and David M. Chess. "The Vision of Autonomic Computing." Computer 36, no. 1 (2003): 41-50.

Contents

Explore

Tagged

  • mape-k
  • autonomic-computing
  • control-loops
  • self-adaptive-systems
  • glossary