Post‑implementation support

1. Transition from project to operations

The transition is a critical handover. Key elements:

• Knowledge transfer: Project team documents system and trains support team.
• Support tools: Ticketing system, knowledge base, monitoring tools are handed over.
• Defined SLAs: Response and resolution times agreed.
• Hypercare exit: Clear criteria for moving from hypercare to steady‑state support.

2. Support models & tiers

Most organisations use a tiered support model:

Tier	Description	Examples
Tier 0	Self‑service (knowledge base, FAQs, user guides)	User looks up how to create a PO
Tier 1	Service desk – first point of contact for users	Password reset, basic "how to" questions
Tier 2	Functional support – deeper process expertise	Configure a new report, troubleshoot workflow
Tier 3	Technical support / vendor escalation	Bug fix, database issue, customisation

3. Service Level Agreements (SLAs)

SLAs define expected response and resolution times based on priority:

Priority	Definition	Response time	Resolution target
Critical	System down, major business impact	15 minutes	4 hours
High	Major function impaired, workaround exists	2 hours	24 hours
Medium	Minor function issue,不影响核心流程	8 hours	3 days
Low	Cosmetic, enhancement request	2 days	Next release

4. Key support processes

• Incident management: Logging, categorising, prioritising, resolving, and closing issues.
• Problem management: Identifying root causes of recurring incidents.
• Change management: Controlling modifications to the system (patches, enhancements).
• Knowledge management: Building and maintaining a knowledge base for users and support staff.
• User access management: Adding/removing users, roles, and permissions.

5. Support team structure

A typical ERP support team includes:

• Service desk analysts: Handle Tier 1, log all incidents.
• Functional consultants: Deep knowledge of finance, supply chain, etc. (Tier 2).
• Technical team: Developers, DBAs, integration specialists (Tier 3).
• Super‑users: Embedded in business units, first line of help.
• Support manager: Oversees SLAs, reporting, and continuous improvement.

6. System maintenance & updates

Ongoing technical activities:

• Patch management: Applying vendor updates (security, bug fixes).
• Version upgrades: Major releases (more frequent in cloud ERP).
• Backup & recovery: Regular testing of restore procedures.
• Performance monitoring: Identifying and resolving bottlenecks.
• Security management: User access reviews, vulnerability scans.

7. Continuous improvement

The ERP should evolve with the business. Continuous improvement activities:

• User feedback: Surveys, focus groups to identify pain points.
• Adoption metrics: Monitor usage, identify underutilised features.
• Enhancement requests: Formal process for new features or reports.
• Quarterly business reviews: Review support metrics, plan improvements.

8. Common pitfalls

• No clear transition: Project team disappears, support team left without knowledge.
• Understaffed support: Ticket backlog grows, users frustrated.
• Poor knowledge base: Support team answers same questions repeatedly.
• No SLA enforcement: Users don't know when to expect resolution.
• Stopping improvement: System stagnates, business needs change.