Follow Us   
Follow REMEDI on Twitter
 
 

GENTRAN™ SERVER FOR UNIX



FOOD SUPPLY CHAIN SERVICES

PROJECT NAME

Gentran Server UNIX v6.1 Visual Map conversion to Sterling Integrator (GENTRAN Integration Suite) UNIX v4.2 Maps - Using X-Link Conversion Engine

CLIENT PROFILE

Client is a supply chain services company providing supply chain solutions to foodservice and grocery chains of all types throughout the world.

  • Industry: Supply Chain Services
  • Location: Southwestern United States
  • Products: Food and foodservice related procurement, distribution, and sales support
  • Technical Environment:
      • Hardware(and OS): Unix
      • Software(and version): Gentran Server for Unix 6.1, Sterling Integrator (GIS) v4.2
      • Relevant to the project...
        • Number of Maps: 127 total maps, 10 vendor and 117 customer maps

BUSINESS CASE

  • To get maps converted to fully utilize Sterling Integrator
  • To retire the instance of GENTRAN Unix
  • To eliminate the cost of operating the two integration environments

SITUATION

  • Client needed to rewrite a block of 127 maps in Sterling Integrator's mapper
  • The source of the maps was GENTRAN Server UNIX Visual maps
  • Sterling Integrator maps tend to take 16 to 24 hours a piece, on average and in most instances, for analysis, mapping, unit testing, and end to end testing
  • Client required rapid development of maps, testing, and implementation due to internal objectives

SOLUTION / DELIVERABLES

  • REMEDI utilized the X-Link Conversion Engine to perform a proof of concept conversion on 4 maps of varying complexity for client
  • Client elected to perform the finalization of the converted maps internally completing map logic for functions in the Visual Mapper not supported in the Sterling Integrator mapper, updating Sterling Integrator code lists, and testing to ensure maps produced similar results as Visual Maps
  • Upon successful completion of the proof of concept, client authorized REMEDI to utilize the X-Link Conversion Engine to convert the remaining 123 maps
  • Client performed the finalization on the remaining maps

OUTCOME

  • Proof of concept completed successfully with client technical resources
  • Balance of maps were converted successfully
  • Using the automated conversion tool the client delivery, conversion, and return of maps to client took less than one business day
  • Maps were finalized by client personnel on their calendar timeline, but with total average finalization time running 2-4 hours per map in most instances

ACCOLADES

  • Client was very pleased with the speed, quality, and success of the project