5. What is Pre-planning?
+ Gathering requirements and Defining Success Criteria for
CloudSuite End-state
- Level of business process redesign, GL/HR Restructure
- New Functionality Targeted
- Migration to Multi-tenant Strategy for any existing Landmark Applications
- Reporting and Integrations Strategies
- Project Phasing & Budget
6. Pre-planning vs Planning
+ Occurs before CloudSuite project
start
- Roadmap: today through five years out
+ Establishes scope and high-level
timeline
+ Expedites project start and reduces
risk
- Not a substitute for Planning
+ Catchphrase: Anything could be
done, but what do you need in wave
one?
+ Occurs as first phase of each
CloudSuite project
- Design phase should follow immediately
after – risk if gap in time
+ Establishes project management
structure and resource leveling
+ Critical to project success
+ Catchphrase: The SOW is not a
Project Charter.
What’s the difference?
7. Why pre-plan for CloudSuite?
+ Reduce risk of project failure
+ Migrating to CloudSuite is a major organizational endeavor
- Both effort & business impact, even if minimal change desired
+ CloudSuite is a Transformational Opportunity
- Leverage 10-20 years of Organizational Know How
- Address organizational pain points with a modern ERP Platform
- Gain advantages of a new implementation at lower cost and easier
transition
+ Capital Budget Planning
- Pre-planning outcomes help inform Capital budget planning and five-year
roadmap
8. Pre-planning objectives
+ #1 – Prepare organization for Project
- Engage Business Teams
- Educate process owners on CloudSuite
- Walk through Cloud Migration project approach and requirements
- Identify Pain Points and process improvement opportunities
- Gain Organizational Buy in
9. Pre-planning Objectives
+ #2 – Project Scoping
- Level of GL, HR Restructure and Business Process Redesign
- New Modules and Functionality
- Workflow, Interfaces, Customizations and Extensions catalog and migration
plan
- Reporting Needs and future state recommendation
- Suggested Project Phasing based on organizational priorities
- Budgetary estimates with internal resource requirements
10. No two migrations are the same!
+ (re)Implemented Lawson
<5 years ago
+ Business Processes,
Software Configuration,
and Data / Reporting
Structure all in Alignment
+ No Major Organizational
Changes
Less intense
+ On Lawson 10+ years
+ Major organizational change
since original design
+ Current GL or HR structures
not representative of reality
+ Mergers/acquisitions brought
into Lawson without
standardization
More intense
11. Some Pre-planning Variations
+ Pre-planning
+ Pre-planning and Module Proof Of Concept
- GL Design is a good example
+ Pre-planning and V10 Assessment
+ Pre-planning and Robotic Process Automation (RPA)
Assessment
13. Pre-planning Engagement
+ Structured Engagement
- Defined Project Scope, Timeline, And Cost
+ Stakeholder Meetings
- Demonstration, Discovery, And Executive Briefing
+ User Workshops
- Reporting Assessment, Interface Development Plan
+ Roadmap
- Timeline, Phasing, Budget
14. Key Deliverables
Deliverable Objective
Project Scope & Approach An outline of the organizational profile, business process redesign requirements, current
and future state modules, conversion requirements and recommended project approach
and phasing
W.I.C.E Inventory A listing of all workflow, interfaces, customizations and extensions currently in place with
estimated migration complexity and recommended approach/remediation
Reporting & Analytics
Assessment
Co-facilitated workshop with key stakeholders to assess opportunities to
leverage leading practices and CloudSuite tools to increase operational reporting
efficiencies
Budgetary Estimates Budgetary and client-resource effort estimates by phase
Executive Summary Presentation summarizing key findings and recommendations
Requirements Traceability
Matrix
Infor Agility tool to confirm CloudSuite fit and highlight business areas with unique
processes
15. Organization Profile & Requirements
+ Discover and document current use of Lawson, targeted at
scoping and architecting a CloudSuite implementation
+ Review of Lawson by module to highlight anything that will
require special effort during the implementation of CloudSuite
- Identify focus areas that may need
extra care during CloudSuite project
- Identify pain points that can be wins
for CloudSuite
+ Width, breath and complexity of
use by module
16. Business Process Requirements
+ Initial high-level evaluation of current business processes
+ Change Hardiness Scale:
- Standard Functionality &
Best Practices
- Configuration Review &
Changes Required
- Customization/Extensions
Required
17. Conversion Strategy
+ Data Strategy has impact on design and project approach
+ Converting 100% of Lawson history not feasible
+ Volume of data, number of subsystem and level of
transformation directly impact effort / cost
+ Based on assessment, provide recommendations for:
- Master Data
- Transactional Data
- Historical Data
18. Infor Data Migration Factory
+ Data migration tool/service for Lawson customers
+ Automates conversion of transactional data
+ Limits extent of data transformed/restructure during
migration
- Can restructure in Lawson or post-conversion
+ Conversion approach is a key design decision:
- Different approach to system design and build
- Different approach to data prep and cleansing
- Additional coordination and planning w/ Infor
19. Catalog Integrations & Extensions
+ Interfaces
- Note connections to systems that may or may not be retired in favor of
CloudSuite functionality
+ Approvals, Workflows & Action Requests
- Gather policy and business requirements
+ Business Justified Customizations
- Strategy is CloudSuite fit/ gap analysis
+ Diagram Processes Crossing System Boundaries
Columns
Business Area
Owner
Object/File Name
Description/Purpose
Existing Tech
Link to Doc
20. Integration & Extension Strategy
For each WICE
object
Need to
develop for
CloudSuite?
Tech/Tool
T-Shirt Size
21. Reporting Assessment
+ Presentation of Value-Based Design concepts and
methodology
+ Reporting Gap Analysis
- Identify any gaps between the delivered reporting and tools and key
reporting requirements
+ Legacy Reporting Analysis
- Identify how legacy reporting artifacts can be consolidated through the
application of a modern reporting and analytics platform.
+ Automation Analysis
- Identify opportunities to increase operational efficiencies through
automation
22. Module / Process Scope & Phasing
Time & Attendance System Upgrade
24. Executive Summary
+ Facilitated overview of discovery & recommendations derived
from the preplanning engagement
- Based on consolidated feedback from Business and IT
+ Summarizes
- The impact CloudSuite Migration will have on business operations
- What the project looks like in terms of timing and effort
- Expected outcomes from a well executed project
+ Opportunity for Executives to ask CloudSuite questions and
gain clarity as it relates specifically to your organization
26. After Pre-Planning
+ Calculation Software license costs
- New Infor SaaS licensing vs software being replaced
+ Review internal resource requirements
- Are they feasible or should the organization plan for staff augmentation to
backfill key resources
+ Determine tech consulting needs
- High level estimate of development work effort & timeline vs organizational
capacity
+ Scope and compare implementation service proposals
+ Submit internal budgets for capital approval
27. Lawson CloudSuite
Peace of Mind
+ Ensure realistic approach for your organization
+ Reduce Risk / Project surprises
+ Coalesce on organization Roadmap
+ Transformation = Road to happiness
28. Be sure to check out our weekly Blog Posts every
Tuesday and our Tech Talks Series every Friday at
noon eastern.
For opportunities to win more prizes, take our
survey by clicking the link in the chat.
blog.rpic.com
29. CloudSuite Pre-planning
Thank You
Richard Leigh Stout
Partner & Director, Infor
Practice
RPI Consultants
rstout@rpic.com
Michael Grace
Tech Pro Unicorn & Director, Strategic
Services
RPI Consultants
mgrace@rpic.com
Editor's Notes
Michael – discuss that in 2019 we were discussing this and folks have actually completed some.
Michael
Michael
Rls – the exercise we go thru before launching a CloudSuite project. Define outcomes, get a handle on what the project is, how big will it be, align teams. Like a more formal version of “budgeting” or “getting ready to go to the board”.
RLS
Michael – surprises around scope get flushed out – creates early engagement, involvement and momentum – sharpen your pencil – everyone of these has resulted in a different plan than we originally were asked for
Michael
Michael – uncover the “we don’t know what we don’t know”
Michael – as individual as a snowflake – most install base in Lawson over 10 years
Michael
Michael – Richard will walk us through
Michael
RLS
RLS
RLS
Standard Functionality and Best Practices: Minimal (if any) changes required from delivered out of the box configuration and testing scripts
Configuration Review and Changes Required: Additional review and/or recommendations in order to meet business objectives
Customization/Extensions Required: Delivered application functionality not sufficient to meet business requirements alone
rls
rls
rls
rls
RLS
Data migration tool/service for existing Lawson customers
Optional and a key conversion design decision.
Capable of converting transactional history (typically two years) across all Lawson subsystems
Limitations to the extent by which data can be transformed/restructured and requirements that must be met for data integrity within Lawson.
rls
RLS
Determine whether development of replacement required in CloudSuite
If Yes then What is future state technology or tool
And assign shirt size
Complexity determined as S, M or L
rls Best practices for accelerating the time-to-value by leveraging Infor’s prebuilt data model and content