Universal Conversion Technologies
Phone: (972) 717-5690
1701 W. Northwest Hwy, Suite 100 Grapevine, TX 76051
Mail UCT at: P.O. Box 141478
Irving, TX 75014

UCT's Release Upgrades Solution

Typical Policy Administration Release Upgrade puzzle

Migrating from one version of a vendor system (starting version) to another (ending version) is an often trivialized task. Here are some of the complexities involved:

  1. Data migration isn't the most complex task in release upgrades - The most complex task that takes the most time and effort is the code retrofit (the integration of new release enhancements with the existing version of the customer's system).
  2. System vendors usually provide tools to help upgrade a system from one release to the very next release
  3. Vendor tools don't handle customer functional modifications and the version upgrade effort often becomes a programming effort
  4. Not all new functionality in a new release is used and customers spend considerable effort analyzing each one against the business functions and products they need
  5. Data migrations are very complicated when there are many releases between the "starting version" and the "ending version", the result is:
    1. Each release between the "starting version" up to the "ending version" is successively applied to the system
    2. The vendor's tools get difficult to use because after each version is applied, the system needs to be tested to make sure it was applied correctly
    3. The application of each version includes "customization" of the vendor's tools to accommodate the customer modifications from the "starting version"
    4. Both 5b and 5c are highly redundant, prone to errors, and cause additional expense and delay

Wouldn't it be better if you could migrate data directly from the "starting version" to the "ending version" without incrementally applying each version in between?

Jump the versions in between with UCT's approach to version upgrades

In a typical release upgrade, we believe that as much as 70% of the "analysis" and programming related specifically to data migration is automated by the Data Conversion Architect (DCA)

  1. UCT experts lead or support our customers in the analysis of the collective enhancements to determine which should be integrated into the "ending version" of the system.
  2. UCT experts support our customers in the retrofit of selected enhancements to the "starting version" of the system.
  3. UCT experts use the Data Conversion Architect (DCA) to migrate data from the "starting version" to the "ending version" - skipping the versions in between:
    1. Import the data model of the "starting version" into DCA
    2. Import the data model of "ending version" into DCA
    3. Use DCA to automatically build the maps that move values from the "starting version" fields to the "ending version" fields. The maps include the logic necessary to complete the move. DCA will... DCA provides automated tools to support release upgrades from one application version to any other version
      • Produce maps for each segment - includes field details: name, format, length, and valid values.
      • Compare the "starting version" of segment fields to the "ending version". When a field match is found, DCA automatically adds the appropriate logic to the map to move the data and a notation to the business expert that no additional logic is required.
      • Alert the business expert to missing fields in the "ending version". Analysis will typically identify this as a result of a customer modification to the original vendor release that needs to be added to the data model of the "ending version".
      • Alert the business expert to changed fields in the "ending version", tell them what changed, and suggest logic to accommodate the change.
      • Alerts the business expert to new fields in the "ending version" and add logic that initializes the new fields based on their data definition
      • Generate a complete program to convert the "starting version" segment/record data to the "ending version" format. These compile without error.
      • Analyze the data in the "starting version" of the system data and produce reports that identify the field values used or other types of useful information.
    4. In addition, DCA can easily be used to provide production-level test data as needed for the code retrofit tasks. Usually, the compilation of test data is a manual effort so due to the substantial time and effort required, complex conditions don't get tested.

Call UCT to see how we can help

If you are moving to a newer version of your product you will benefit from UCT expertise and techniques. For more information, contact Rae Albertini at (972) 717-5690 or submit our online information request form.

Home | Services | Data Migration Tools | About Us | Contact Us