ERP implementation is not just an IT project. Its success is determined by the involvement of the process owner, the quality of the initial data, the design of work rules, and the readiness of users to operate the new system. Use the 20 questions below to assess areas that need attention before the project starts.
A. Business Objective & Scope
- Have the three operational problems to be solved been written down specifically?
- Are there any initial KPIs, such as reconciliation time, stock accuracy, or invoice delays?
- Has the inbound process for the first phase been differentiated from the features for the next phase?
- Have the business owners for sales, purchasing, inventory, and finance been appointed?
B. Master Data & Accounting
- Have the lists of customers, suppliers, and items been reviewed to remove duplicates?
- Have the SKU code, product unit, and conversion rules been agreed upon?
- Can the physical stock be reconciled with the system balance on the cutover date?
- Have the chart of accounts, tax accounts, accounts receivable, and opening balances been validated by Finance?
C. Proses & Integration
- Have the order-to-cash and procure-to-pay flows been mapped end-to-end?
- Have approval and data access per role been agreed upon?
- Is the list of existing applications that must remain operational complete?
- Have data ownership, synchronization direction, and API failure handling been established?
D. People & UAT
- Are users who represent day-to-day operations involved in the system design?
- Do the UAT scenarios include partial deliveries, returns, discounts, and partial payments?
- Do the SOPs and training materials differ according to the user's role?
- Do critical issues and changes in scope have an approval mechanism?
E. Cutover & Post-go-Live
- Have the cutover schedule, owners of each task, and backups been prepared?
- Are the criteria for proceeding, delaying, and rolling back the go-live documented?
- Are the support team and incident escalation channels clear?
- Has the schedule for KPI evaluation and post-go-live adoption been determined?
Bagaimana Menginterpretasikan Hasilnya?
This checklist is a discussion tool, not a certification standard. Focus on questions that do not yet have answers or responsible parties. If the master data is not yet clean or the process has not been agreed upon, adding ERP features usually does not solve the root of the problem.
Priority for fixes: resolve issues that could halt transactions or corrupt data before go-live; defer enhancement needs and non-critical reports to the next phase.
Contoh Agenda Workshop Discovery ERP 90 Menit
| Agenda workshop discovery ERP selama 90 menit | ||
| Durasi | Agenda | |
| 0-20 menit | Business problems, impacts, and desired KPIs | |
| 20-50 menit | Order-to-cash and procure-to-pay mapping | |
| 50-70 menit | Master data, existing systems, and integration needs | |
Understand the basic concepts of panduan aplikasi ERP Techway. Untuk konsultasi implementasi Odoo, kustomisasi, dan integrasi berdasarkan kebutuhan perusahaan, kunjungi layanan ERP Techway.