1. DBS 2.3.4 to DBSi 5.0 Environment Strategy Quinn March 22, 2011

2. 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)

3. 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 www.acndms.com website for download. www.acndms.com 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*

4. Comparing Full vs. Minimal Deployment Assistance Full AssistanceMinimal Assistance Coda InstallationYes (Optional)No DBS 2.3.4 to DBSi 5.0 System UpgradeYes (Optional)No Finance Conversion Package InstallationYes (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.

5. 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 e-Finance 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 eFinance Review DASD requirements for additional Finance Conversion package and temporary storage Request the following software packages: Coda eFinance application package, Finance Data Conversion package, DBS Core upgrade package & Service Advisor upgrade package (see the following slides for the software distribution process)

6. DBS 2.3.4 to DBSi 5.0 Software Distribution Process  To request DBS 2.3.4 to DBSi 5.0 upgrade software, please contact your upgrade project coordinator. He/she will then create a Siebel ticket to request the software be made available to the dealer on the ACNDMS website.  The project coordinator will also request temporary authority for a specified user to access the files.  When the files are available, the project coordinator will contact the specified user that the files are available for download.  The package will include installation instructions as well as the following: 1) CODA eFinance Install package 2) Finance Data Conversion package 3) DBS Core Upgrade package 4) Service Advisor Upgrade package

7. DBS 2.3.4 to DBSi 5.0 Software Distribution Process  Once available, the 2.3.4 to 5.0 Upgrade Package will be posted on the ACNDMS site and can be found in the link below under DBS 2.3.4 to DBSi 5.0 Upgrade folder: https://www.acndms.com/Technical/DBSi%2050/Forms/AllItems.aspx

8. DBSi 5.0 ASP Software Distribution Process  DBSi 5.0 Application Service Packs (ASP) will also be distributed using www.acndms.com website. www.acndms.com  You will be automatically added to the ASP distribution list once you request DBSi 5.0 upgrade software for your deployment  A week prior to an ASP’s general availability date, the Code Configuration Management Team (CCMT) will notify self-hosted dealers that the ASP will soon be available for download  On the communicated availability date, CCMT will upload the DBSi 5.0 ASP package and installation instructions to the ADMS site, and then notify dealers via e-mail that the files are available for download

9. Dealer Planning Install Coda eFinance 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

10. Dealer Configuration Coda eFinance configuration is recommended to be done on your FDC instance. This instance is also where the Conversion testing should be done as well against your DBS 2.3.4 test environment The dealer is responsible for identifying if any database tuning or indexing requirements on the Coda e-Finance 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: Accenture 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)

11. FDC Finance Conversion Testing Execute all conversion programs the necessary number of times to finalize your Coda eFinance configuration from a test DBS 2.3.4 environment to your FDC instance of Coda eFinance Testing duration is usually 2 weeks and recommends execution of all master and 1 year’s worth of detail & summary posting conversions.

12. Production Finance Conversions Copy your tested FDC Coda eFinance configuration to your Production instance of Coda eFinance 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

13. Mock Cutover (Business Testing) Take a copy of your production Coda eFinance database and use it to replace or refresh the information in your FDC instance of Coda Copy the necessary conversion files 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.

14. 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.

15. 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)

16. Questions / Comments