DX Chronicles ~MarsModel Development Log (9)~ 3-Layer Model Analysis Test (Business Layer Edition)
What is MarsModel (under development)?
A framework for transforming and updating business structures across management, business, functional, and operational layers through the introduction of IT systems.
It enables analysis, contemplation, decision-making, implementation, and reflection for Japanese companies unfamiliar with IT to decompose and reconstruct their business structures using IT systems.
Its feature is that by translating the business logic layer and data layer into modules suitable for each layer, even those with low IT literacy can appropriately grasp IT systems and reconstruct business structures.
Do you know the terrifying workflow version of PHS (Print, Hanko, Scan)?
To everyone living in Japan where Print, Hanko, Scan still survives, how are you doing? Yes, I am also in Japan.
What is Print, Hanko, Scan?
As mentioned in 'I want to do something about PPAP, but I also want to do something about PHS | PPT',
it is a mysterious custom of 'printing an email attachment, stamping it with a hanko, scanning it, and sending it back'.
However, there was a shocking workflow version of PHS!
However, the world is vast, and there is an advanced form of PHS called the 'workflow version of PHS'.
This is a business process with a distinctly Japanese charm, where PHS procedures are woven into the approval process using a workflow system.
So, let's defeat the workflow version of PHS using MarsModel (business layer)!!
I'm going to defeat the workflow version of PHS!
First, let's think about the reasons why PHS cannot be defeated.
The reasons why IT systems in the world are in a dire state can be narrowed down to the following three points.
What the system is doing is not understood
It is not known what information is needed to run that work
The work is complicated and cannot be thought through
Step 1: Let's unravel the movements of work, IT systems, and data!
This time, since it is an existing workflow (including PHS), I have super-simplified it, but it is generally something like this.
Here is an important and unique point of MarsModel, which is generally omitted: Write what the IT system is doing as a task, just like a person (*Note added) This will become important later on.
(*Note) An example of how to write without including the system can be found in the Ministry of Internal Affairs and Communications FY2017 Business Reform Model Project BPMN. Since the system tasks are omitted, I'm not sure if this really identifies unnecessary tasks.
Step 2: Identify what is absolutely necessary (tasks, IT system tasks, and data).
What is super important in a workflow is (1) the content of the approval request (application details) and (2) the record of the approval result. If you color them blue, it looks roughly like this.
Step 3: Identify what is necessary to do the absolutely necessary things (tasks, IT system tasks, and data).
Now, let's identify what is needed to do the "absolutely necessary things." Since it's a workflow, this mainly consists of (1) communication between the applicant and the approver, and (2) content verification. If you write it in yellow, it looks like this.
Step 4: Identify things that might not be necessary.
By this step, basically any tasks, IT system movements, or data that are not colored are mostly unnecessary. This time, I painted them red.
Step 5: Keep only what is necessary and check if there are any problems.
Finally, let's remove the tasks, IT system movements, and data that seem unnecessary and check if there are any problems.
The business layer of the MarsModel is at this stage for now.
So, using the workflow version of PHS as a subject, I have optimized the tasks using IT systems in the business layer using the MarsModel.
You might say "it's such a simple thing," but in fact, this workflow version of PHS is still sometimes found even in large companies. It is Japan that cannot even do such simple things.
[Remaining Task] Introduce the concept of time.