“Gundam Sortie Workflow” defined in this article is composed of roughly four tasks: “1. Detecting Enemies”, “2. Order Action Station”, “3. Sortie Command” and “4. Sortie”. However, there is a case that no sortie is actually done. So we must take care of where the bifurcated points are defined and when the process is finished on the way. Let’s learn more detail!
First, this process starts from “1. Detecting Enemies”. There are two cases such as radar detects enemies automatically and humans find enemies visually. Anyhow, a flight controller must report to the Captain. From the point of view of designing workflow, you should not list detailed development in this case. We want to focus on abstract process such as “report to the Captain”.
By the way, if you report to the captain orally, the business record cannot remain (rather the workflow system has no role in this case). I sincerely recommend to report with ”Questetra BPM Suite SaaS Edition” .
…Yes! Using this workflow, Captain Bright Noah could check the situation by email even if he has been working at his own desk or has been exercising in the gym (!!?).
…Yes! “Alert in the ship” will be automated if the alert system works together with RESTful. This is convenient.
…Rather, what were reported and when they were reported are automatically saved as “business record” . This is so convenient.
By the way there are two flight controllers in the White Base. As you know, Oscar Dublin and Marker Clan are the only two. Therefore, the process of this workflow will stagnate if those two persons are absent. This fact is to be specified as “risky item” in the Risk Control Matrix (RCM) documents.
[Gundam Sortie Workflow]