iSeries Skip Upgrade External Sales Presentation

September,2005

Lawson Commitment

•Lawson is actively pursuing new iSeries clients and is planning to grow the Lawson iSeries client base

•Lawson’s 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

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

Significant Value in Upgrading to the Version 8.1 Lawson ApplicationsTechnology

• Portal

• Design Studio

• Process Flow

• Performance/scalabilityBusiness Applications

• New products

• Many new features

• Performance and scalabilityReporting & Analytics

• Lawson Reporting Suite

• Smart Notifications

• Web delivered standard reports

Decommission Decisions

•Decommission v7.2.x.x for the iSeries platform deadline May 31, 2007

•Decommission upgrade path to 8.03 within FY06

Key Messages

With Lawson’s 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.

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.

Upgrade Goals and Objectives

UPGRADE

8.0.3 Environment

7.2.2.4 To 8.1.0 plus latest MSP Applications

KEY TO SUCCESS

Two Important Facets

• Technology Strategy

• Applications Strategy

Upgrade Methodology

Four Phases•Planning

•Design

•Construction

•Activation

Upgrade Initiation

•Determine objectives

•Assess experience

•Determine resource commitments

•Analyze hardware status

•Set expectations

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)

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 management’s expectations

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 Lawson’s and Client’s 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.

Strategy Meeting (cont’d)

• 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

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

Application Exploration (AE)

•Obtain better understanding of how software works

•Begin making setup decisions

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

BPR (cont’d)

• 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

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

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

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

System Tests

•Circle back to System Test and Business Strategy Session

•Recommend 2-3 test passes

Readiness Assessment

•Decision regarding go live date

•Develop upgrade activation plan (with timings)

•Develop contingency plans

End User Training

•Train end users on new functionality and procedures

•Roll out as necessary

•Revise procedures, if necessary

Upgrade Activation/Go Live

•Run upgrade in Production

•Verify data accurately converted

•Applications are operational

•Resume normal day to day operations

Post Implementation Review

•Review and recommend for future changes

•Plan for any Phase 2 projects

•Provide feedback on implementation process

iSeries Upgrade Strategy

Upgrade Project Team

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

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

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

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

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

LAWSON SOFTWARE UPGRADE METHODOLOGY

STARTSTARTBusiness Needs

AnalysisProject

Strategy Meeting

Have InitialMeeting WithProject Team

Initial Upgrade Planning

DetermineFirst DraftTime Line

Project Team Training

Project LeadersTrained on New Version of Applications

Application Exploration

Project Leaders‘Play’ In TestEnvironment

Install NewApplication

s

Business Procedures

Review

Project LeadersDecide How ToUse/Setup NewFeatures, Functions,& Reports

Detailed Upgrade Planning

Order/InstallUpgrade Software

Plan ExactlyFor The TestUpgrade

Run Upgrade Tools/Software

Test UpgradeBusiness Strategy Session

Determine HowTest UpgradeWent

Project LeadersTest the System“Mini-Parallel”

System Test

Final Training Of Everyone

End User Training

Project Meeting to Verify Everyone Is Ready

Readiness Assessment

Live UpgradeProductionUpgrade

Verify Reports and that Everything Is OK

Post UpgradeReview

Decide on Project Team

Recycle as oftenas necessary(2-3 test runs

typically)

Option: QuickTest Upgrade

Mini CRP

1st Upgrade Test Pass

Verify data & that procedures meet bus. rqmts.