As the company that provided the first COBOL to COBOL-in-Java compiler, we wanted to emphasize that direction with the name for our new offerings: hence, "C2J".

We also wanted to differentiate between the old PerCOBOL set of products that were used by our customers to do their own conversion then maintenance work from our newer customers that are benefiting from the "C2J Factory", moving them quickly into a converted model of modernization.

Rather than spend days getting a demo together, weeks evaluating whether the tool made sense, weeks procuring the tool, weeks getting your staff trained, then months and months getting the conversion done, the C2J Factory approach cuts that to days and weeks for the entire project.

We can demo today, FastPilot in 3, start your project next week, Deliver next month.

Time, Talent, and Risk can indeed go to zero.

Our architect, Brian Sullivan, took the bold step in 1995 to conclude that the object-oriented profile of Sun's new Java language -- and Sun's backing -- would create the environment needed to move old COBOL applications "seamlessly"... All you had to do was create a translation engine significantly in advance of the introduction of J2EE, most of JVM, most of why you could verify that this was, indeed, an outstanding selection -- not a wild-eyed graduate degree programmer's mistake...

Still, it was 5+ years before Java was close to becoming the standard it is today, needing the release and the beginnings of the acceptance of the J2EE standard in the enterprise before this became a real business...