Enterprise patterns: CESAR #entarch

The patterns OODA (Observe, Orient, Decide and Act) is very well know ( see https://en.wikipedia.org/wiki/OODA_loop ). But what’s happen AFTER it? In other words, is it possible to recommend a generic behavioral pattern when an action is taken by the OODA pattern?

This blogpost proposes a Coordination, Event Streams, Analytics, Rules (CESAR) pattern. This pattern is used after the OODA pattern because a process (initiated by the OODA) must coordinate some activities, continuously monitor (from many different sources) the permanently changing situation, make some predictions via analytical tools, and select the best next actions in accordance with existing rules.


Post a Comment