Batik Semar, PT is one of the oldest and largest Batik and Clothing Industry in Indonesia. The business process is complex, therefore they invited us to solve the business problem and develop the sophisticated MRP system. Batik Semar is implementing Business Unit Concept, it is like having few small companies inside Batik Semar, so it has a better method to define which unit that is performing well or which unit that is generating loss. MRPro solved the entire business problem, because it is agile or easily adjusted and cover all the manufacturing process, from Order, Production Line, Material Supply to Accounting.

http://www.batik-semar.com

Immense amount of product and category gave a real problem to the company. It was simply made the old system looked very lame. The director needs real time access to their data online to make specific managerial decision, the finance department needs fast access to generate actual report on time, the production manager needs all the item usage to be registered, and more. MRPro should be capable of handling large amount of transaction with decent speed, have an intuitive screens to make the learning curve short and accessible through Internet.

As like the other large scale manufacturing industry, Batik Semar focuses on managing product and material, production line, finance, and most of all system integration.

Our team adopted a four-phased approach to mitigate risk and Agile Development Methodology, given the scale of the project and large people on the client side that was involved in the project. The four phases include Proof-of-Concept, Pilot Project, Pilot Expansion and Hands-On Modules.

1. Analysis and Consulting – Proof of Concept
We analyze the whole system by interviewing heads of division and the operational staffs. And based on the old system we analyze the weaknesses and optimize the operational flow. On this phase we focused on creating solutions based on our analysis and propose the Proof of Concept to the client.

2. Pilot Project
The Pilot Project was based on the P-O-C; we demonstrated the process flow and pre-release screen to the users, so they got the picture of the system at the initial stage. We encouraged every user to give us feedback at this phase; after we reviewed the feedback we released the updates of Pilot Project. This phase was a subject of repetition.

3. Pilot Expansion
Successful demonstrations of the concept lead to building the project functionally

4. Hands-On Modules
Every module release, we created a real process scenario and invited corresponding end-users to try the new module, and asked for the feedback. The end-users were rotated; hence all users on the factory will be familiar with the new system in the end of the project.