Transcript
Page 1: Transform | Upgrade | Migrate · • Maximo 7.5.0.8 - Maximo 7.6.0.5 • Maximo 4.0.1 - Maximo 7.6.0.4 The SDU will migrate data changes from current production into the future production

SRO Data UtilityTransform | Upgrade | Migrate

Why SDU?• IBM approved global solution

• Reduces downtime

• Mitigates the risk of failure

• Enables testing and training on

live data

• Offers a proven and successful

approach

• Allows for “offsite” updates

Take advantage of the latest

Maximo Features

Manage your Maximo Upgrades, Outage, Migration and Change/Risk challenges

using our SDU toolkit.SDU

“Major upgrade with SDU ... it just

happened”DP World

The SDU is an ETL toolkit that helps IBM Maximo customers to reduce downtime during the Maximo upgrade and data migration processes.

The SDU’s unique change capture capabilities allow you to synchronize changed data from one environment to another. Each environment may be on a different version, patch or internal change release level.

The SDU can also be used to move data from production to non production environments.

The SDU captures and synchronizes the data, so that environments can be kept in sync with a seamless cutover.

ZERO

DOWNTIME

Page 2: Transform | Upgrade | Migrate · • Maximo 7.5.0.8 - Maximo 7.6.0.5 • Maximo 4.0.1 - Maximo 7.6.0.4 The SDU will migrate data changes from current production into the future production

SDU usage examples SDU

UPGRADE MIGRATION

The SDU upgrade enables an organization to reduce the overall downtime of a major Maximoupgrade. It involves upgrading from one major Maximo version to another. Some examples include Maximo Industry Solutions and add-ons such as Maximo Mobile and Maximo Scheduler.

Examples of completed upgrades:

• Maximo 6.2.6 - Maximo 7.6.0.5

• Maximo 7.1.1.5 - Maximo 7.6.0.2

• Maximo 7.5.0.8 - Maximo 7.6.0.5

• Maximo 4.0.1 - Maximo 7.6.0.4

The SDU will migrate data changes from current production into the future production system which has been upgraded through the various levels required.

The SDU migration functionality allows an organization to reduce downtime when migrating data from legacy systems or from existing Maximo configurations to another - it may also include an upgrade to a later version. It is similar to the upgrade scenario, however, no official IBM Maximo upgrade is performed as the organization may want to move away from the existing configuration or version into a separately configured Maximo environment.

The SDU will first migrate all the non configuration data and continue to synchronize delta data changes from current production into the target production system.

Typical migration scenarios include:

• De-Customization

• New Corporate Configuration Rules

• Re-Implementation

• Large Business Process Changes

Import Scoped Tables

Activate Environment

Complete MappingConfigure

Environment

Decomission

Scope Definition

Re-configure Environment

Syncronize Data

Deactivate Environment

UpgradeMaximo

Migrate Users

srosolutions.net

Page 3: Transform | Upgrade | Migrate · • Maximo 7.5.0.8 - Maximo 7.6.0.5 • Maximo 4.0.1 - Maximo 7.6.0.4 The SDU will migrate data changes from current production into the future production

SDU

Live data Latest data

DATA CHANGES

UPGRADE PROCESS

TRANSFORM MIGRATE UPGRADE

PRODUCTION OUTAGES

The SDU Production Outages facility allows significant downtime reduction or elimination for typical production outages. This scenario requires a temporary or permanent duplicate of the existing production systemto function.

The SDU will migrate data changes from current production into the target production system which has been re-configured with a new release or patched to a later minor level.

Typical outages scenarios may include:• Maximo Table adjustments

• New tables/columns

• Extending fields

• Dropping tables/columns

• Workflow re-configuration

• Screen changes

• Integration adjustments

• New interfaces

• Modification of existing interfaces

• Rebuilding interface tables

• Applying a FixPack or HotFix“The SDU

made complicated data migration

possible, and with minimal impact to end users.”

MERGE ENVIRONMENTS

The SDU Merge functionality allows an organization to merge multiple instances of Maximo together whilst reducing downtime impact – an upgrade may also be involved. In this scenario, the target database may have data written from multiple sources or may already have live users within the system.

Examples:• Merging environments

• Consolidating separated instances of

Maximo to a corporate level configuration

• Consolidating vendor instances of Maximo

srosolutions.net

Page 4: Transform | Upgrade | Migrate · • Maximo 7.5.0.8 - Maximo 7.6.0.5 • Maximo 4.0.1 - Maximo 7.6.0.4 The SDU will migrate data changes from current production into the future production

srosolutions.net

Tel: +44 (0)845 408 4250 E-mail: [email protected]

Implementations:SDU

Ports | UK | Hampshire

• Size of database - 60GB+• No. of users - 150• Upgrade process utilised 3 times (6.2 - 7.1 then 7.1 - 7.5 then 7.5 - 7.6)

Nuclear | UK | Lancashire

• Size of database - 35GB+• No. of users - 300• Highly customised SDU upgrade process

Leisure Parks| US | Florida

• Size of database - 1.7TB • SDU used for production and archive databases

Utilities | US | North Carolina

• Size of database - 600GB+• No. of users - 8,000 • SDU used twice (6.2.3 – 7.5 and later 7.5 – 7.6)

Transportation | US | Arkansas

• Size of database - 15GB+• Switched from Oracle to SQL Server• 40 million work orders

Utilities | US | Texas

• Size of database - 500GB+• Going live SDU Sync lasted less than 10 minutes

Utilities | US | Georgia

• Size of database - 300GB+• No. of users - 11,000 • SDU sync lasted less than 15 minutes

Offshore transportation | US | California• Size of database - 9GB+• No. of users - 2,000• Database distributed globally over 30+ sites

c 2

018

- SRO

Sol

utio

ns Lt

d. -

SDU

bro

chur

e 04

2018

v.1


Recommended