DBS 2.3.4 to DBSi 5.0 Environment Strategy

Agenda

• Recommended Reference Information

• Roles & Responsibilities Full vs. Minimal Assistance

• Environment Activities by Phase

•Pre-Planning

•Planning

•Dealer Configuration

•FDC Conversion Test

•Production Conversions

•Mock Cutover / Business Testing

•Production Cutover (Go Live)

Reference Information

• 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 download.

•DBSi 5.0 Infrastructure Architecture Blueprint

•Coda Installation Guide

•Coda Database Backup Procedures

•CODA & 3rd Party Software Integrations Operations Guide

•DBS 2.34 to DBSi 5.0 Coda Conversion Installation Guide*

•DBS 2.34 to DBSi 5.0 Core Installation Guide*

Comparing Full vs. Minimal Deployment Assistance

  Full Assistance Minimal Assistance

Coda Installation Yes (Optional) No

DBS 2.3.4 to DBSi 5.0 System Upgrade Yes (Optional) No

Finance Conversion Package Installation Yes (Optional) No

To clarify below are the environment build related services to expect with full assistance compared to minimal assistance:

NOTE: The dealer is responsible for execution of the upgrade package(s) and will also need to make sure the environments are properly sized prior to executing these packages.

Pre Deployment

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

•Determine if you want to have a separate AS/400 or Coda Financials environment for Development, Mock (Business Testing) and Finance Conversion Testing

• The benefits of having two environments is the testing efforts will not impact the performance of the current production environment

•The drawbacks would include additional expense in hardware and licensing to support a second environment

•Acquire the necessary Intel Servers to support Coda Financials

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

•Download the following software packages: Coda Financials application package, Finance Data Conversion package, DBS Core upgrade package & Service Advisor upgrade package (available on https://www.acndms.com)

Phase TaskFull Assistance   Minimal Assistance

Dealer Shared Dealer SharedPre-Planning Identify Hardware Requirements   X   X         Separate Deployment LPAR X     X         Additional DASD required? X     X    Acquire Intel Servers for CODA X     X    Full System Save (build Test Environment) X     X    Request DBS 2.3.4 to DBSi 5.0 Software Packages X     X  

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 development environment in which would be upgraded using the provided DBS 2.3.4 to DBSi 5.0 Upgrade package

Phase TaskFull Assistance   Minimal Assistance

Dealer Shared Dealer SharedPlanning Install Coda Financials Server Software   X   X    Apply Finance Conversion Package to Test, Prod   X   X    Build DBSi 5.0 Development Environment   X   X  

Dealer Configuration

• Coda Financials configuration is recommended to be done on your FDC instance. This instance is also where the Conversion testing should be done as well as against your 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 FDC/DDC testing should occur against your DBSi 5.0 Development environment

NOTE: Caterpillar Inc. (DDS) will provide Application Service Packs that may need to be reviewed and applied based on where you are in the deployment cycle (not recommended to apply service packs once in Mock testing)

FDC Finance Conversion Testing

• Execute all conversion programs the necessary number of times to finalize your Coda Financials configuration from a test DBS 2.3.4 environment to your FDC instance of Coda Financials

•Testing duration is usually 2 weeks and recommends execution of all master and 1 year’s worth of detail & summary posting conversions.

Production Finance Conversions

• Copy your tested FDC Coda Financials configuration to your Production instance of Coda Financials

•Make sure the updated conversion cross reference spreadsheets are applied to your Finance conversion package in production

•Execute conversions in your production environment updating the production instance of Coda

•Recommended to begin daily backups of your Coda production databases once this phase begins

Phase TaskFull Assistance   Minimal Assistance

Dealer Shared Dealer SharedProduction Conversions Schedule Daily Coda Financials Backups X     X  

Mock Cutover (Business Testing)

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

•Copy the necessary conversion files and cross reference spreadsheets from production to your test DBS 2.3.4 environment

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

•Copy necessary configured Safe source files from your development environment if applicable.

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

Phase TaskFull Assistance   Minimal Assistance

Dealer Shared Dealer SharedMock Cutover / Business Testing Remove DBSi 5.0 Development Environment   X   X    Copy Coda FDC Database to TRN instance X     X    Build DBS 2.3.4 Mock Test Environment X     X    Execute DBSi 5.0 Upgrade (Mock Cutover)   X   X  

Production Cutover

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

•Take a Yearly 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

•Copy Safe source files from Mock testing where applicable

•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 Yearly After Batch save once validation is complete.

Phase TaskFull Assistance   Minimal Assistance

Dealer Shared Dealer Shared

Production Cutover (Go Live) Full System Save (PRD) week prior to Cutover X     X    Yearly After Batch Save (before upgrade) X     X  

 DBS 2.3.4 to 5.0 Upgrade (Production Cutover Plan), Application Service Packs, Hot/High Fixes   X   X  

  Apply FDC/DDC Changes X     X    Yearly After Batch Save (after upgrade) X     X  

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

•Create a DBSi 5.0 Test (FDC) environment for testing future service packs and bug/fixes

•Retire the DBSi 5.0 Development environment (when applicable)

•Retire the DBSi 5.0 Mock environment (when applicable)

•Retire the Coda V4 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)

Phase TaskFull Assistance   Minimal Assistance

Dealer Shared Dealer SharedPost Production Remove Test DBS 2.3.4 (Txxx) environment X     X    Build a Test DBSi 5.0 environment   X   X    Remove Finance Conversion Tools   X   X    Remove CODA V4 Appication/License   X   X    Remove DBSi 5.0 Mock Environment   X   X  

Questions / Comments