Srikanth SrinivasanDecoding Global QAD Launches

1

Thirdware Overview

1200+Employees

20 Years Of

Excellence

Our Infrastructure

Partners

2 Delivery Centers6 Global Locations

20% owned by Ford Technology

300+Customers

85% Automotive

Project Executed in

40+ CountriesGeo Partners

NEO, BrazilSIT, MexicoCarutris, FranceKontextE, Germany

2

Our Journey

1995 - 2000ERPImplementationsLargeMNCsandIndianConglomeratesManufacturing(Automotive)FocusIndia/APACFocus

2001 - 2005ExpandTechnology(MultipleERPs,EPM/BI,Java,.Net)FordStrategicInvestment(20%Stake)StrategicClientFocus- Ford,PfizerDeliveryExpansion- ChennaiDeliveryOperations

2006 - 2010USExpansion- MidWest/EastCoastFocusOracleandSAPPartnershipsTechnologyExpansioninStrategicAccountsBI/Analytics- Impetus

2011 - 2015ServicestoSolutionsFocusExSights– ProductStart-upInitiatedBI&Analytics- ExpandBeyondEPMISO–9K,20K&27KCertifications–Ford&PfizerODC

2016-2020Outcome BasedServicesDeliveryModelServicesAutomationandInnovationDigitalandProducts/SolutionsFocus

ERP Wave

Technology Expansion & Strategic Client Focus

US Geography Expansion& BI/Analytics Focus

Services toSolutions

Services Automation

& Digital

Technology:Enterprise Apps.

Vertical:Manufacturing-Auto

Geography:USA

3

Our QAD Implementation Experience

Projects Executed

India

China

Taiwan

Australia & NZ

Japan & Korea

Thailand, Malaysia, Philippines, Vietnam, Indonesia, Singapore

South Africa

USA

Mexico

Brazil & Argentina

Portugal, UK, France, Germany, Spain, Czech Republic, Austria, Hungry, FranceCanada

4

QAD Launches – Key ChallengesDetermining what business wants and what business have.

Data. Data. Data. Data Preparation takes longest lead time and acts as major go-live disruptor.

Launch team launches and site live with the launched system.

5

Launch Readiness Considerations

Pre-Launch Questionnaire

Data Readiness

QAD Orientation

Environment

LAUNCH KICKOFF

• Understand the high-level business scenarios, organization and current system landscape• Review high-level business process gaps and localization needs

• Enable the sites to initiate long lead master data preparation and cleansing activities.• Support sites during data cleansing and data transformation process.

• Provide awareness & engage site management • Engage key users up front with functionality and key concepts in the QAD model to prepare for gap

analysis and enabling business for pre-launch questionnaire

• Preloaded Databases with standard data.• Finalize Sequence Data Loading sheet and corresponding data load file.• Prepare and create environments for data loads, gap analysis and testing activities during launch.

Launch Activities

6

Typical Implementation Approach

Enable Launch Readiness

▪ Detailed Advance Assessment▪ Educate Key Business Users▪ Envisage Requirements▪ Evolve Model▪ Stakeholder buy in for model

Required Tools

▪ Exhaustive Assessment System▪ Representative Models▪ Introduction & Base Product Training

content

Pre-Launch Launch

EnablersMigration Toolkits

Computer Based Training

Standard QAD Setup

Evolved Model

FactoriesData Migration

Application Integration

Configuration

Launch Development

Launch Activities

▪ Confirm Evolved Model▪ Confirm Data Migration Strategy▪ Prepare additional requirements▪ Demonstrate final model▪ User Training and Acceptance▪ Coordinate cutover / launch

Offshore Factories▪ Manage Data Migration▪ Manage Model Configuration and

Testing▪ Development and Testing▪ Environment Setup

Tools

Data Load SequencesPre-defined Data formats

Extract and Cleansing toolsData Loading Tools

Model PresentationsPre-configured Model

EnvironmentSetup / Config document for

Model

7

Data Readiness ApproachQAD Data Readiness Program

Basic setups and data Standard configurations and setup within QAD

Non-transactional reference dataKey master data elements and detailed field review

Transactions and balancesOpen balance review for key transactions

Track 1 Base Data

Track2 Master Data

Track 3

Transaction & Balances

DATA

READINESS

Divided into 3 Tracks

Parallel Execution

Track 1 : Base Data

Track 2 : Master Data

Track 3:Balance Data

8 Base data includes legal entity setup, control files, generalized codes, printers, etc.8 Review existing legal entity structure and define future model

8 Master data includes customers, suppliers, parts, BOMs, prices etc.8 Identify source systems, extract methods, mandatory fields, field mapping, etc.

8 Balance data includes open inventory, A/R, A/P, etc.8 Review and confirm open balances, adjust in source system as necessary

Metrics Measure Data Readiness by site

Monitor overall data readiness progress

Monitor data inputs to launch activities

8

Managing Business DisruptionsOrganization Change Management

Creation of Process Champions & Business Project Team would existing organizational

rolls.

• Budget and plan for backfill as part of ERP program.• Documentation of tribal knowledge & business rules

before transition to backfill with ensure smooth transition and business continuity.

• Gradual transition with current and backfill working in parallel.

Data Owners have day job.

• Data owner training and Data Management process should be finalized during Core Model Build.

• Ongoing Data Readiness validation with process to capture data changes is needed.

• Advance notification for mock data and cutover dates.

Planning & Scheduling

Impact of launch activities to business

• Identify key program launches and audits before commencing planning and scheduling.

• Try to find lean period for End User training and Cutover.

• In case lean period / plant downtime not available, plan for elongated user training and cutover.

Timing of cutover

• Cutover Approach should be finalized during core model definition.

• Cutover process during pilot should be used to determine volume and timing needed.

• Use pre-loaded environments, loading of base data & master data before cutover.

• Discuss and finalize reduction of opening balance volume during cutover.

Post-Launch

Post-Launch Issues causing business disruption

• Identify key transactions (like Shipment, Receipt, Cycle Count etc.) which needs to work perfectly to prevent business disruption.

• Conduct production dry-run of those transactions before releasing the system to users.

• Do not decommission legacy systems till first month-end closure.

• Plan for Process champions and key users from the site spending substantial time for at least 3 months after the launch.

THANK YOU