Reasons to consider systematization
The reason why system investment in Indonesia has been considered in recent years is that the importance of Indonesian factories has increased, and accurate and prompt information management and effective use of information has become a requirement, but there are two main cases: one is the case in which local systemization is considered at the request of the head office in Japan, and the other is the case in which systemization is considered out of necessity under Indonesia's current laws.
Japan headquarters policy.
- We want to unify the entire company and reduce the operational load.
- I want to be able to monitor the data from Japan.
- We want to link data to the Japanese system.
- I want to follow the same rules as in Japan (inventory evaluation method, items to be displayed on forms, etc.).
In Indonesia, driven by need.
- The accuracy of the data is low.
- Data entry is slow.
- The data entry load is high.
- The necessary data (forms) are insufficient.
- The data entered is not being used effectively.
The problem of systematization between Japan-led and Indonesia-led
In many cases, it is relatively large companies that are involved in Japan-led systemization, and the introduction of the same system as that of the Japanese factory is requested by the head office in Japan, and the introduction of the same system as the Japanese factory is supported by the information system department of the head office in Japan, but problems tend to occur, such as inability to use the expensive system, inability to ensure the accuracy of the input information, and inability to perform master maintenance.
On the other hand, it is often the case that the talk of Indonesia-led systemization occurs in a comparatively small and medium-sized company, and the system is selected by the Indonesian factory itself, and the whole business is not necessarily unified into the same system, and there are many cases that part of the EXCEL management remains, but in this case, the problems of frequent double input, no connection of business on the system, and the system depending on the individual tend to occur.
At the beginning of system implementation, there is a requirement definition phase in which the current business is reviewed and how it is incorporated into the system is decided.
The local majority vote is based on Pengambilan suara (majority vote), but since the power relations between departments affect the system specifications, the local key person who is the coordinator is important, while the Musyawarah type is a consensus system based on discussions and aims for unanimous agreement.
What the Indonesian staff thinks
The three sacred treasures that were synonymous with Japanese management in the 1990s - lifetime employment, seniority, and corporate unions - are now a thing of the past, as the business environment has become more and more severe with the rise of China and other Asian countries. However, the "Aun breathing" that still remains in Japanese companies that do not dare to make clear decisions has become an obstacle for American-style Indonesian office workers who take clear job descriptions as a matter of course when communicating with Japanese expatriates and the head office in Japan.
Why don't you explain to us until we are satisfied?" is a phrase I have heard many times in the field of system implementation in Indonesia, and I think that the local staff of Japanese companies overseas think the same thing about Japanese people.
System Implementation Methodology for Indonesia
For many years, I have never doubted that the most effective way to implement a system in Indonesia is to introduce the packaged software as a standard business flow without making any objections.
Recently, however, we realized that no matter how much we try to get them to accept the system as a standard form, if the gap between the new work flow and the current work flow is too large, the Indonesian staff will become skeptical of the results and will not accept them emotionally.
For example, in order to get 100 results, the current business process is to check 50 results before getting the next 50 results, but if the new system suddenly gets 100 results and the results are slightly different, Indonesian staff will be skeptical of the results, even if the results are improved to a more accurate number.
Therefore, even though the function of the new system can produce 100 at once, we dare to make the process from 0 to 50 run the same as the current business with external add-ons, and have them check the results, and then implement the remaining 51 to 100 in the function of the new system.
The purpose of systemization is to improve the current business, and replacing the exact same flow as the current business with a system will not have much of an improvement effect.
The business system development template Hana First is a semi-packaged product with high flexibility and customization, which was created as a result of trial and error in the field of system implementation in Indonesia for many years.