Do you have Remedy data migration challenges?
...don't worry, Alderstone CMT can help with that!
We're constantly surprised by the things to which our customers want to use Alderstone CMT for, for example, one company may perform an upgrade by building a parallel set of Remedy environments, while another may have infrastructure or financial constraints which mean they have to reuse their existing environments. Alderstone CMT has been designed to support a wide range of use cases to support various business scenarios and constraints.
This section describes the high-level use cases that are supported by Alderstone CMT. Please note that it is not possible to describe each of the variants in a high-level of detail.
Please contact us to discuss your business objectives and constraints, to see how Alderstone CMT can be used to support your business objectives.
The process of upgrading an environment to a later version of BMC Remedy ITSM. This process has a lot of variants, including, but not limited to; parallel systems upgrade, staggered upgrade, incremental upgrade, capacity-constrained upgrade, and multi-source upgrade, to name just a few! CMT is engineered to support a wide range of upgrade scenarios.
Onboarding a customer onto a Remedy ITSM environment. Variants include onboarding customers with existing BMC ITSM systems and customers being onboarded from non-Remedy systems. CMT can greatly accelerate the onboarding of customers from existing Remedy systems and enhances their experience, by allowing any of their historical and live data to be included in the onboarding. Customers from non-Remedy systems are initially loaded from spreadsheets after which CMT is used to promote their data with significant resource and lapsed time savings.
Offboarding is the opposite of onboarding, and is the process of removing an ITSM company from an environment; typically because the customer is leaving the ITSM SaaS platform. CMT can extract all data for the customer to flat file and remove only that customer’s data from the BMC Remedy ITSM systems.
A staggered upgrade can be used to reduce the impact of a upgrade in a multi-tenant Remedy ITSM environment. Rather than upgrade all of the customers using the system at the same time, selected customers can be upgraded to the new version individually or in waves. This approach to upgrades can only be performed using Alderstone CMT which uniquely is able to migrate an ITSM Company and all their data to the new version of ITSM. This approach allows companies running ITSM as a service to reduce risk, and be more responsive to their customers, enabling customers who are very keen on an upgrade to be migrated without forcing everyone else sharing the platform to be migrated at the same time.
Consolidation is the process of merging of one or more BMC Remedy ITSM environments into a single environment. Typically performed to reduce the overheads of running multiple sets of environments. CMT is the only tool capable of merging Remedy data sets in this way, and does not require all environments to be running the same version of ITSM. This action is often combined with an upgrade.
Separation is the process of moving one or more customer(s) currently on a multi-tenancy platform, onto a separate system including all of their live and historical data. This is typically performed due to changes in the customer’s requirements for security or regulatory compliance.
Hub-and-Spoke is a BMC technology designed to support ITSM SaaS operators who have technical resources supporting customers across multiple systems. Underpinned by Remedy DSO, Hub-and-Spoke enables multiple systems to be connected and synchronized. Hub-and-Spoke is straightforward to configure for green field sites, but there are significant challenges when working with historical data due to clashes in unique identifiers. CMT enables you to resolve these clashes to allow systems with existing data to be integrated into the Hub-and-Spoke architecture.
When managing large multi-environment estates of BMC Remedy ITSM systems, some ITSM SaaS operators choose to use a standard set of configurations to reduce administrative overheads and ensure consistent application behavior. CMT can be used to migrate a standard set of baseline configurations between Remedy environments.
Over time, and even with strict change control processes, the non-Production systems (e.g. Development, QA) tend to diverge from the Production data set. Typically this is addressed by replicating the entire database from Production to the non- Production environments. It can be logistically challenging to schedule a full overwrite of the non-Production environments if you have in-flight projects such as a customer onboarding using those environments. Multi-tenant environments in particular are difficult to refresh, using a full overwrite, as some activity is almost always in progress. Using CMT you can execute a full synchronization of your non- Production environments without disruption to ongoing activities.