DM REVOLVE in More Detail


In short DM REVOLVE is

  • DataMC’s ground breaking proprietary data migration toolset
  • Powered by BIDM methodology
  • Developed over decades by industry experts
  • A proprietory toolset used by DataMC on every engagement
  • Clients get to experience the full use of the tools whilst working with DataMC consultants

Here we present a small breakdown of some of the DM REVOLVE tools we use.

TAP – Toolkit Access Portal

The control hub of DM REVOLVE, TAP houses all of our toolsets

  • WOM – Workflow-O-Matic
  • POM – Profile-O-Matic
  • MOM – Map-O-Matic
  • ROM – Report-O-Matic
  • TOM – Translate-O-Matic
  • FOG – File-O-Gen

From here you can access any of the tools you will need for a data migration.

DM REVOLVE front end interface

Workflow-O-Matic (WOM)

WOM is the gatekeeper of DM REVOLVE. Through the WOM interface, every part of our 15 step data migration is

  • Tracked
  • Reported on
  • Updated
  • Signed off

For each of the data objects, it is easy to see

  • What stage in the process they have progressed to
  • If they are on schedule
  • Quality of the data
  • Status
  • Who is responsible for it at that time

Problems can be spotted quickly. Tracking shows the history of objects throughout the project. Relevant parties are informed when objects reach each stage of the process. WOM makes the process transparent, and accountable.

WOM – Workflow-O-Matic – the main admin area of DM REVOLVE – tracking the data objects from start to finish

Profile-O-Matic (POM)

POM – the selection criteria from the legacy source is used to obtain the required data set, this is then used to create the data objects. All relevant information for each object is recorded here, such as

  • The data source
  • Table names
  • The description of the object
  • Any other notes

The SQL Select statements used to Extract data from the legacy sources are recorded. Once the data has been Extracted, the data owner checks it against the expected data set then signs off in order to progress to the next stage.

POM – Profile-O-Matic – Select and Extract the data from the legacy systems

Map-O-Matic (MOM)

MOM takes the completed selection criteria and performs the mapping from

  • Source (legacy) system data fields


  • Target load template fields

This work is performed by the data analyst and subject matter experts (SMEs) from the client. Required translations and Data quality (DQ) checks are identified at this stage along with the severity of any data quality issues.

Once mapping for a data object has been completed it is submitted for

  • Review
  • Approval
    • on to the next stage
  • Refinement
    • goes through the MOM cycle again
MOM – Map-O-Matic – maps fields from the legacy system to the new system

Report-O-Matic (ROM)

The ROM review process shows the results of

  • POM – selection Criteria
  • MOM – Mapping
  • Coding

It is a verification and Data Quality step, here the verification takes place for the

  • Number of records
  • Data quality of the objects

The quality of the extracted data is tracked through ROM. Its traffic light system shows quickly and clearly where any issues are occurring. Each of the data objects is given a thorough breakdown and reports are given for

  • Any errors
  • The number of fields affected
  • The exception encountered and its severity
  • Individual errors for each record
    • Individual fields if needed.

ROM should be reviewed and monitored by both the client’s subject matter experts (SME’s), as well as DataMC Technical Leads, Analysts, and Coders.

ROM – Report-O-Matic – Generates data quality reports
ROM – Report-O-Matic – identifies errors and helps fix them

Translate-O-Matic (TOM)

TOM empowers the client data owners to ensure all translations are completed and correct. This is an important step in improving data quality and ensuring a seamless migration for DataMC and the client.

All the data translations take place in TOM and are tracked and updated here. If you need a legacy field updating from say White to W, Red to R and Blue to B then this is the place to do it. All the results can be exported if needed.

TOM is also the place to perform inflight data duplication cleansing – this could be merging separate accounts into one along with any data associated with them if needed.

TOM – Translate-O-Matic – Translates old values to new, either individually, automatically, or en masse

File-O-Gen (FOG)

File-O-Gen generates load files from stored model tables, these are ready for import into the target system. Once generated the loads can be tested daily, this leads to

  • Fast generation of structured files
  • Repetition of the load
  • Catching and correcting errors
  • Automation and predictability
FOG – File-O-Gen – Generates Load files ready for the new system