ERP · Enterprise Resource Planning
Enterprise Resource Planning
What is ERP?
- Enterprise-wide management of finance, HR, production, and more
- Scattered data, unified
- The backbone of company operations
What actually changes when you adopt ERP is not the software but the way people work. If the “item name” in the purchasing team’s Excel sheet and the “part number” on the production team’s drawings used to differ and people simply reconciled them by instinct, ERP forces both to use the same code. The order for posting journal entries, approval authority, even the point at which inventory is deducted must follow the flow the system defines, so an ERP rollout is not an IT project but a business standardization project. Success depends less on product performance than on who decides the master data and processes.
Your options split by company size. So-called Tier 1 systems such as SAP S/4HANA and Oracle are for large enterprises handling overseas subsidiaries and complex cost structures, while mid-sized and small companies look at products such as Douzone, Younglimwon, and MS Dynamics. Deployment splits into on-premise, where you run your own servers, and cloud, where you pay a monthly fee. A single site typically takes 6 to 9 months, and multiple entities or plants 12 to 18 months. Be clear about the boundaries too. MES, which captures equipment output by the second, CRM, which handles customer touchpoints, and groupware centered on approvals and bulletin boards are systems to integrate with, not replace. ERP is the ledger that records the results of money and goods in motion, and it is common for implementation and consulting fees to exceed the license cost.
The most common failure is piling on customizations because “our company is special.” The more you rewrite the standard screens, the less able you are to install the vendor’s regular upgrades, and a few years later, when the developer who built it leaves, you are left with a system nobody dares to touch. The second is skipping the inventory count and item-code cleanup because the go-live date is looming. The moment book quantities and warehouse quantities diverge, the business teams pull Excel back out, and once a double set of books hardens, ERP becomes an empty shell that only adds data entry. Leadership has to accept first that go-live is not the finish line but the day data starts to accumulate.
Seungtae ParkHands-on AX instructor who teaches AI business development and marketing automation by building real systems
John KimInstructor John Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”ERP evolved in the 1990s from manufacturing resource planning (MRP) into an enterprise-wide integrated system, and vendors such as SAP brought it into the mainstream.
Let’s look at a hypothetical case. Company A, an auto-parts manufacturer with two plants in Gyeonggi Province, has 320 employees and annual revenue of about KRW 78 billion (≈ US$58,357,000). Orders and purchasing ran on Excel, accounting on a separate program, and inventory on the warehouse foreman’s handwritten ledger, so the monthly close took 12 business days. Only 76% of system inventory matched the physical count, and the company finally launched a nine-month cloud ERP project.
- At the kickoff, the CEO made it clear: “This time it’s not the IT team’s project, it’s every department head’s.” Six manager-level staff were pulled from purchasing, production, quality, and accounting, and half of them were stationed full-time in the project room.
- The longest task was cleaning up item codes. Reconciling the 12,000 items that each department had been calling by different names, and cutting them to 8,400 through a physical count, took 11 weeks alone, and about 3,000 discontinued items were written off.
- The head of production management held out, saying, 'Our painting process is special, so the screens have to change.' The PMO lead settled it by proposing two months on the standard screens, then a review, and only 9 of 41 customization requests were accepted.
- For the first month after go-live, the old Excel files ran in parallel. When shop-floor foremen skipped barcode entries and inventory drifted, the production manager spent 15 minutes every morning going through the previous day’s missing entries with them, building the habit of entering data.
- One year later, the monthly close dropped from 12 business days to 5, and inventory accuracy rose from 76% to 97%. With delivery-date replies now going out within a day, urgent outsourced machining costs fell by roughly KRW 180 million (≈ US$134,700) a year.