DBS 2.3.4 to DBSi 5.0 Environment Strategy

Agenda

• Recommended Reference Information

• Roles & Responsibilities

• Environment Activities by Phase

o Pre-Planning

o Planning

o Dealer Configuration

o TEST Conversion Test

o Production Conversions

o Mock Cutover / Business Testing

o Production Cutover (Go Live)

© 2010 Accenture. All rights reserved. 2

Before proceeding with any of the following activities, please be sure to have the following reference documentation available, especially if installing these products without deployment assistance. These documents are available on the https://www.acndms.com website for viewing.

• CODA V11.3 Prerequisites

• CODA Database Backup Procedures

• CODA & 3rd Party Software Integrations Operations Guide * For reference only, most setup will be handled by Accenture

• DBS 2.34 to DBSi 5.0 Coda Conversion Menu Installation Guide

*For reference only Accenture will install – dealer will download script

• DBS 2.34 to DBSi 5.0 Core Installation Guide (DBCI) * For reference only Accenture will install – dealer will download script

Reference Information

© 2010 Accenture. All rights reserved. 3

Environment tasks and responsibilities

Below are the environment build related services to expect:

NOTE: The dealer is responsible for making sure the environments are properly sized prior to executing these packages.

© 2010 Accenture. All rights reserved.

Task Responsibility

Download Coda application Dealer

Install Coda application Accenture

Download Finance Conversion Menu from website

Dealer

Install Finance Conversion Menu Accenture

Download the DBCI Package Dealer

Perform the 5.0 Upgrade (DBCI) Accenture

4

Pre - Planning

• Identify hardware requirements to host a DBSi 5.0 Test environment (see DBSi Infrastructure Architecture Blueprint for detailed specifications)

• CODA test environment will be utilized for the mock conversion

•Acquire the necessary Intel Servers to support Coda Financials

•Review DASD requirements for additional Finance Conversion package and temporary storage

•Download software packages: Coda install, Conversion Menu, and DBCi - details and location will be available on request

Task Responsibility

Identify Hardware Requirements Shared

Separate Deployment LPAR Dealer

Additional DASD required? Dealer

Acquire Intel Servers for CODA Dealer

Full System Save (build Test Environment) Dealer

Request DBS 2.3.4 to DBSi 5.0 Software PackagesDealer

© 2010 Accenture. All rights reserved. 5

Dealer Planning

• Install Coda Finance Application on Intel Servers

• Apply Finance Conversion Package to Production and Test environments (NOTE: Test environment for conversions needs to be at a DBS 2.3.4 level)

• A suggestion to take a recent save of the production DBS environment and use that to build a DBSi 5.0 Test environment in which would be upgraded using the provided DBS 2.3.4 to DBSi 5.0 Upgrade package

Task Responsibility

Install Coda Financials Server SoftwareAccenture

Apply Finance Conversion Package to Test, Prod

Accenture

Build DBSi 5.0 Development EnvironmentAccenture

© 2010 Accenture. All rights reserved. 6

Dealer Configuration

•Coda Financials configuration is recommended to be done on the Coda TEST instance. This instance is also where the Conversion testing should be done as well as against the DBS 2.3.4 test environment

•The dealer is responsible for identifying if any database tuning or indexing requirements on the Coda Financials database are needed to improve performance issues (these can be customized based on dealer configuration)

•DBS configuration and TEST testing should occur against the DBSi 5.0 Development environment

NOTE: Accenture will provide Application Service Packs that may need to be reviewed and applied based on the deployment cycle (not recommended to apply service packs once in Mock testing)

© 2010 Accenture. All rights reserved. 7

Conversion Test

• Coda will help configure the necessary information to the TEST

instance of Coda financials.

• Execute conversion programs from the DBS Conversion Menu that are applicable for the data conversion from IAS to Coda.

•Testing duration is usually 2 weeks and recommends execution of all masters with some converted historical postings.

© 2010 Accenture. All rights reserved. 8

Production Conversions

• Copy final tested TEST Coda Financials configuration to the Production instance of Coda Financials

• Make sure the appropriate cross reference spreadsheets are updated and ready for the 2.3.4 to 5.0 upgrade (DBCI)

• Execute the applicable conversions in the DBS 2.3.4 production environment updating the production instance of Coda

Note: It is recommended to continue daily backups of the Coda test and production databases during this phase

© 2010 Accenture. All rights reserved. 9

Mock Cutover (Business Testing)

• Take a copy of the production Coda Financials database and use it to replace or refresh the information in the TEST instance of Coda

• Copy the necessary conversion files from production to the test DBS 2.3.4 environment

• Execute the DBS 2.3.4 to DBSi 5.0 Upgrade process in the Mock Cutover Plan

• Copy necessary configured Safe source files from the DBSi 5.0 TEST environment if applicable.

• Copy the Mock instance of Coda to the TRN (Training) instance if desired to keep any configuration information not already in production.

Task Responsibility

Refresh DBS 2.3.4 Mock Test EnvironmentDealer

Execute DBSi 5.0 Upgrade (Mock Cutover) Shared

© 2010 Accenture. All rights reserved. 10

Production Cutover

• Execute Month End Close activities (optional – can choose not to convert following a month end)

• Take a full system After Batch save once Month End Close and preparatory activities are completed

• Execute the DBS 2.3.4 to DBSi 5.0 Upgrade using the Production Cutover Plan developed

• Apply Application Service Packs where applicable

• Request application of hot/high fixes where applicable.

• Validate the DBSi 5.0 environment is built/working correctly

• Perform a second full system save once validation is complete.

Task Responsibility

Full system Save (PRD) prior to Cutover Dealer

DBS 2.3.4 to 5.0 Upgrade (Production Cutover Plan) Application Service Pack, Hot/High fixes

Shared

Apply FDC/DDC changes Dealer

Full system Batch Save (after upgrade) Dealer

© 2010 Accenture. All rights reserved. 11

Post Production Cutover

• Revise your current production backup schedule to include new DBSi 5.0 libraries and remove obsolete DBS 2.3.4 libraries where applicable

• Refresh the DBSi 5.0 Test (TEST) environment for testing future service packs and bug/fixes

• Retire the DBSi 5.0 Mock environment (when applicable)

• Retire the IAS Finance application within 6 weeks following Go Live

• Uninstall the Finance Conversion and related temporary files within 6 weeks following Go Live (be sure to save off any files you may want to keep longer term)

Task Responsibility

Refresh Test 5.0 environment from production Dealer

Remove Finance Conversion tools Dealer

Remove IAS Application/License Shared

Remove DBSi Mock (TEST) environment if applicable Dealer

© 2010 Accenture. All rights reserved. 12

Where to Get More Information

• ADMS Website (https://www.acndms.com)• Application Service Packs

• Technical 5.0 Application Service Packs• CODA Help from CODA main menu • Contact your Accenture Deployment Lead• For non-deployment related issues, please continue to contact Accenture Dealer

Management Services (ADMS): support.adms@accenture.com

• ADMS support center:• 309-674-4000 or +54 (11) 4850 3800• support.adms@accenture.com

© 2010 Accenture. All rights reserved. 13

Questions / Comments

© 2010 Accenture. All rights reserved. 14