SRO Data Utility SDU · PDF file • Maximo 22.214.171.124 - Maximo 126.96.36.199 • Maximo 188.8.131.52...
Embed Size (px)
Transcript of SRO Data Utility SDU · PDF file • Maximo 184.108.40.206 - Maximo 220.127.116.11 • Maximo 18.104.22.168...
Maximo Upgrades, Outage, Migration and Change/Risk
SRO Data Utility SDU
Why SRO Data Utility?
• IBM approved global solution
• Reduces downtime
• Mitigates the risk of failure
• Enables testing and training on live data
• Offers a proven and successful approach
+44 (0)845 408 4250
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 capa- bilities allow you to synchronise 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 en- vironments. The SDU captures and syn- chronises the data, so that environments can be kept in sync with a seamless cutover.
TRANSFORM MIGRATE UPGRADE
IBM UPGRADE PROCESS
SRO Data Utility
The SDU upgrade enables an organisation to reduce the overall downtime of a major Maximo upgrade. 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 22.214.171.124
• Maximo 126.96.36.199 - Maximo 188.8.131.52
• Maximo 184.108.40.206 - Maximo 220.127.116.11
• Maximo 4.0.1 - Maximo 18.104.22.168
The SDU will migrate data changes from current production into the future pro- duction system which has been upgraded through the various levels required.
Import Scoped Tables
Data Migration The SDU migration functionality allows an organisation 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 organisation 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-con- figuration data and continue to synchronise delta data changes from current production into the target production system.
Examples: • De-Customization
• New Corporate Configuration
• Large Business Process Changes
SDU usage examples
We are “the zero downtime upgrades
SDU usage examples
Merge Environments The SDU Merge functionality allows an organisation to merge multiple instances of Maximo while reducing down- time impact – an upgrade may also be involved. In this scenario, the target database may have data written from various sources or may already have live users within the system.
• Merging environments
• Consolidating separated instances of Maximo to a corporate
• Combining vendor instances of Maximo
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 system to function.
The SDU will migrate data changes from current production into the target production system which has been re-con- figured with a new release or patched to a later minor level.
• Maximo Table adjustment
• New tables/columns
• Extending fields
• Dropping tables/columns
• Workflow re-configuration
• Screen change
• Integration adjustments
• New interfaces
• Modification of existing interfaces
• Rebuilding interface tables
• Applying a FixPack or HotFix
“Major upgrade with SDU - just happened”
d . -
+44 (0)845 408 4250
Leisure Parks US | Florida • Size of database - 1.7TB • SDU used for production and archive databases
Nuclear UK | Lancashire • Size of database - 35GB+ • No. of users - 300 • Highly customised SDU upgrade process
US | North Carolina • Size of database - 600GB+ • No. of users - 8,000 • SDU used twice 6.2.3 – 7.5 & 7.5 – 7.6
Transportation US | Arkansas • Size of database - 15GB+ • Switched from Oracle to SQL Server • 40 million work orders
Utilities US | Georgia • Size of database - 300GB+ • No. of users - 11,000 • SDU sync lasted less than 15 minutes
Oil & Gas US | California • Size of database - 9GB+ • No. of users - 2,000 • Database distributed globally over 30+ sites
Ports UK | Hampshire • Size of database - 60GB+ • No. of users - 150 • Upgrade process utilised 3 times 6.2 - 7.1 & 7.1 - 7.5 & 7.5 - 7.6