ERP Implementation Planning Should Prepare You to Run It

A lot of ERP work gets pushed to "after go-live," and then it gets done in a hurry, if at all.

Learning the system, securing it, and deciding who runs it are three items that tend to get pushed out. Ken Foley, Vice President of RPI Consultants' Infor Practice, returns to RPI Tech Connect to argue that ERP implementation planning should cover this work from day one

Drawing on nearly 30 years in the Lawson and Infor space, Ken covers role design across every CloudSuite application, the change control process auditors will eventually ask you to produce, and segregation of duties. Plus, hear why the first few months after go-live are busy enough with support issues that anything postponed gets postponed again.

If you’re considering an ERP project, this conversation is a must-listen before starting!

Not sure who owns your ERP system after go-live? RPI can help. Contact us to learn more about our strategy services before your next project 👉 https://www.rpic.com/project-strategy/ *Chapters:*

00:00 Welcome to RPI Tech Connect

00: 41 How Operational Pain Points Slip Through the Cracks

5:33 A Proactive Approach Reduces Process Firefighting

14:13 Step 1: Application Security & Role Design

19:44 Step 2: Technical Development Lifecycle & Change Control

32:18 Delivering to Run: Nailing the Post-Implementation Handoff

34:42 Step 3: Governance, GRC & Segregation of Duties

39:27 "Think Like a Thief": Stress-Testing Your Own Security

46:54 The Benefits of Planning Ahead: 90 Days Post Go-Live

49:25 Final Thoughts & Takeaways