Unit 6.6: ERP Implementation Process and Modules (Enrichment)

--:-- --
↓ Scroll for more

Unit 6.6

ERP Implementation Process and Modules

IT 233: Business Information Systems — Enrichment (beyond syllabus)

Learning Objectives 🎯

By the end of this session, you will be able to:

  • ✅ Describe the phases from planning to post-go-live support.
  • ✅ Explain fit-gap analysis and minimum customization.
  • ✅ Compare big bang, phased, parallel and pilot go-live.
  • ✅ Compare on-premise vs cloud (SaaS) ERP.
  • ✅ Apply Nepal VAT, e-billing, CBMS and fiscal-year rules.

Why Implementation Is the Hard Part

  • Software imposes its own logic — Davenport (1998).
  • Decide: change process vs configure vs customize.
  • Markus and Tanis cycle: Chartering → Project → Shakedown → Onward/upward.

9 Phases at a Glance

  1. Planning / chartering — goals, scope, sponsor, budget.
  2. Requirements — as-is → to-be processes.
  3. Fit-gap — fit or gap + close decision.
  4. Design + configuration — CoA, tax, roles, extensions.
  5. Data migration — clean, map, load masters + balances.
  6. Testing — unit, integration, UAT, parallel payroll.
  7. Training — role-based, super-users.
  8. Cutover + go-live — freeze, reconcile, go/no-go.
  9. Post-go-live — hypercare, then improvements.

Fit-Gap: Close Cheapest First

  • 1. Change process to standard.
  • 2. Configure (settings, workflows).
  • 3. Work around (report / small add-on).
  • 4. Customize code — last resort (upgrade cost).

Example: keep standard price lists, drop Excel discount sheet.

Go-Live Approaches

  • Big bang: all at once — fast, risky.
  • Phased: by module/site — lessons carry forward.
  • Parallel: old + new run together — safe, double work.
  • Pilot: one branch first — real-world test.

Combine: pilot → phased rollout + parallel payroll one cycle.

On-Premise vs Cloud (SaaS)

  • Cost: upfront CapEx vs per-user OpEx subscription.
  • Infra: own servers vs provider + reliable internet.
  • Customization: deep but hard upgrades vs config-only.
  • Nepal tip: backup link + offline billing fallback outside main cities.

Core Modules Hand Data to Each Other

  • Finance ← all modules post here.
  • Procure-to-Pay: requisition → PO → goods receipt → 3-way match → payment.
  • Hire-to-Retire: hire → attendance → payroll → GL posting.
  • 3-way match flags qty/price mismatch automatically.

Critical Success Factors

  • Top management + project champion.
  • Clear vision, minimum customization.
  • Clean masters, tested end-to-end processes.
  • Change management: super-users, Nepali guides, retire spreadsheets.
  • TCO: licences + services + data + training + internal time + dip + contingency.

Nepal Rules Your ERP Must Handle

  • VAT 13%, PAN on invoices, VAT registers.
  • IRD-enlisted e-billing only; check ird.gov.np list.
  • CBMS connection if turnover > NPR 20 crore (check latest notice).
  • Fiscal year Shrawan 1 – Ashadh end; BS dates. Go-live on Shrawan 1.

Mini Case: Gandaki Agro Traders

  • 3 sites, stock vs books mismatch, 2-week close.
  • Recommend: pilot Pokhara → phased branches + parallel payroll.
  • Fit-gap: BS dates, VAT/PAN, CBMS, branch transfers, price lists.
  • Cloud + backup link; go-live Shrawan 1 with counted opening stock.

Key Takeaways

  • Process first, customize last.
  • Phased/pilot beats big bang for multi-site.
  • Include data, training and dip in TCO.
  • Full note: ERP Implementation (Enrichment)