Lawson Software

1

iSeries Skip Upgrade External Sales Presentation
September,2005
2
Lawson Commitment

• Lawson is actively pursuing new iSeries clients
  and is planning to grow the Lawson iSeries client
  base
• Lawsons latest applications are now available to
  iSeries clients
• Lawson is providing a very attractive option in
  the form of a 7.2x to 8.1 skip upgrade solution
  to move to the latest Lawson applications

3
Version 8.x Application Releases

• iSeries releases (version 8.03 and version 8.10)
  contain the same application code as that offered
  to Unix/Windows clients
• These are iSeries centric releases. 8.x
  applications are created in RPG IV/ILE language
• Version 8.03 applications on the iSeries have
  been generally available since October 2003.
• Version 8.1 applications were generally available
  on May 12, 2005

4
Significant Value in Upgrading to the Version 8.1
Lawson Applications

• Technology
• Portal
• Design Studio
• Process Flow
• Performance/scalability
• Business Applications
• New products
• Many new features
• Performance and scalability
• Reporting Analytics
• Lawson Reporting Suite
• Smart Notifications
• Web delivered standard reports

5
Decommission Decisions

• Decommission v7.2.x.x for the iSeries platform
  deadline May 31, 2007
• Decommission upgrade path to 8.03 within FY06

6
Key Messages

• With Lawsons newest applications, iSeries
  clients can take advantage of the latest
  enterprise software technology to automate their
  business processes, meet regulatory compliance,
  reduce costs, improve operational efficiency and
  effectiveness, and increase their competitive
  advantage.
• Providing Lawson 8.1 applications shows Lawson is
  listening to its clients and delivering the right
  products at the right time, while presenting them
  with the choices, flexibility and control they
  need in determining how to manage their IT
  investment and systems.

7
Upgrade Goals and Objectives

• Terminology
• Upgrade Is moving data from one release level
  to another where there are major database
  changes.
• Cyclical Fixes, enhancements with no or minor
  database changes.
• Migration Change hardware platform.
• Conversion From non-Lawson to Lawson formats.

8
Upgrade Goals and Objectives
UPGRADE 8.0.3 Environment 7.2.2.4 To 8.1.0 plus
latest MSP Applications
9
KEY TO SUCCESS

• Two Important Facets
• Technology Strategy
• Applications Strategy

10
Upgrade Methodology

• Four Phases
• Planning
• Design
• Construction
• Activation

11
Upgrade Initiation

• Determine objectives
• Assess experience
• Determine resource commitments
• Analyze hardware status
• Set expectations

12
Upgrade Registration

• Complete Skip Upgrade Addendum and send to Client
  Manager
• CM registers with GSC Upgrade Center
• 7.2.2.4 to 8.1 Skip Upgrade Software delivered
• Receive Upgrade Information Packet (UIP)

13
Business Needs Analysis

• Set initial goals objectives
• Document current process flows
• Gather copies of current forms, screens reports
• Determine interface modification needs
• Define/document upper managements expectations

14
Strategy Meeting

• Objectives and Deliverables
• Understanding of the Upgrade Methodology
• Defined project objectives scope
• Chart a safe course from the current state to
  the desired state
• Agree on Lawsons and Clients responsibilities
  commitments
• Define project team structure/commitments
• Identify all modifications which will require
  attention during your upgrade.
• Identify all interfaces which will require
  attention during the upgrade.

15
Strategy Meeting (contd)

• Define project milestones and establish critical
  dates
• Identify project constraints
• Assemble the team and define project
  expectations.
• Determine if there will be any prerequisite
  upgrades required, and if so, include them in the
  Technology Upgrade Plan.
• Provide input to be used in creating the Upgrade
  Project Plan.
• Upgrade Differences Training Schedule
• Initial Project Plan for Upgrade

16
Project Team Training

• Technical
• Knowledge transfer by Technical Consultant
• Running Upgrade Programs
• Pre and Post Upgrade Processes
• Application Training (differences or full
  application)
• New Functionality
• Gain knowledge to make setup and procedural
  decisions
• Upgrade Setup Requirements

17
Application Exploration (AE)

• Obtain better understanding of how software works
• Begin making setup decisions

18
Business Procedure Review (BPR)

• Upgrade Server Technology (environment as
  required) and test
• Compare existing and standard reports
• Review current business flows, map changes
• Determine setup parameters for all modules
• Obtain approval on setup decisions

19
BPR (contd)

• Document setup parameters
• Document and prioritize interfaces
• Document and prioritize modifications
• Develop test scenarios and test data
• Document new business issues
• Begin prep of User Procedure Manuals

20
Mini Conference Room Pilot (CRP)

• Prove/disprove procedures meet business needs
• Identify any procedures to rework
• Confirm need for modifications
• Confirm interface requirements
• Revise Issue List

21
System Test(s)

• Run upgrade
• Track timing of upgrade process
• Execute test scripts
• Review Reports from Source data to Target data
• Identify any problems plans to correct
• Stress test to simulate live conditions

22
Business Strategy Session

• Evaluate test upgrade
• Revise procedures or setup based on test results
• Develop/revise system test plans
• Write/revise User Procedure Manuals
• Develop end user training strategy/materials

23
System Tests

• Circle back to System Test and Business Strategy
  Session
• Recommend 2-3 test passes

24
Readiness Assessment

• Decision regarding go live date
• Develop upgrade activation plan (with timings)
• Develop contingency plans

25
End User Training

• Train end users on new functionality and
  procedures
• Roll out as necessary
• Revise procedures, if necessary

26
Upgrade Activation/Go Live

• Run upgrade in Production
• Verify data accurately converted
• Applications are operational
• Resume normal day to day operations

27
Post Implementation Review

• Review and recommend for future changes
• Plan for any Phase 2 projects
• Provide feedback on implementation process

28
iSeries Upgrade Strategy

• Upgrade Project Team

29
UPGRADE PROJECT TEAM

• Project Manager
• Oversees all upgrade activities
• Documents and resolves issues, sets priorities
• Application Owners (MM, GL, AP, HR, PR)
• Application strategic needs, setups, testing and
  end user training
• Make tactical decisions

30
UPGRADE PROJECT TEAM

• Application Work Team Members
• Document system setups
• Test system setup and parameters, processes,
  reports and security
• Lawson Application Consultants
• Product specialists, setup and procedures
• IS Work Team Members
• Support system and applications
• Upgrade data files, security, run upgrade
  programs, interfaces, modifications and custom
  reports

31
UPGRADE PROJECT TEAM

• Lawson Client Manager
• Activates upgrade registration and licenses
• Orders software, upgrade programs
• Lawson Practice Manager
• Initial Upgrade Strategy Planning
• Consulting Services Proposal and Agreement

32
UPGRADE PROJECT TEAM

• Lawson Project Manager
• Schedules Lawson activities, detailed project
  planning, manages issues, coordinates consulting
  resources (application and technical consultants)
• Lawson Technical Manager
• Sets technical strategy, provides detailed
  technical project planning, manages technical
  issues, and coordinates technical consultants
• Lawson Technical Consultant(s)
• Technology specialists, upgrade programs, and
  security

33
Upgrade Next Steps

• Complete an Upgrade Client Profile
• Schedule a Planning Session with Lawson Services
• Complete detailed planning session and develop
  project plan and timeline
• Define Project Team
• Develop Team Training Plan

34
LAWSON SOFTWARE UPGRADE METHODOLOGY
Business Needs Analysis
Project Strategy Meeting
Have Initial Meeting With Project Team
START
Decide on Project Team
Initial Upgrade Planning
Determine First Draft Time Line
Post Upgrade Review
Verify Reports and that Everything Is OK
Project Leaders Trained on New Version of
Applications
Production Upgrade
Project Team Training
Live Upgrade
Install New Applications
Option Quick Test Upgrade
Application Exploration
Readiness Assessment
Project Leaders Play In Test Environment
Project Meeting to Verify Everyone Is Ready
Project Leaders Decide How To Use/Setup
New Features, Functions, Reports
Business Procedures Review
Final Training Of Everyone
End User Training
Order/Install Upgrade Software
Recycle as often as necessary (2-3 test runs
typically)
Verify data that procedures meet bus. rqmts.
Project Leaders Test the System Mini-Parallel
System Test
Mini CRP 1st Upgrade Test Pass
Determine How Test Upgrade Went
Detailed Upgrade Planning
Test Upgrade
Plan Exactly For The Test Upgrade
Business Strategy Session
Run Upgrade Tools/Software