The good thing about OpenText is that we have the mapping specification guideline available, which is not there in a solution like SEEBURGER. Whenever you want to take a decision to move away from OpenText, you have already documented your mapping and what your mapping looks like. So you go to the next provider, provide them with that mapping specification, and it'll be very easy for them to develop a new map instead of just taking the data - input data, output data - and then looking for how the data is getting transformed. So you have the mapping spec level which is a very good feature of OpenText, which we do not have in SEEBURGER. It's very hard to move from SEEBURGER. The solution is easy to implement. It's stable and reliable. They are the industry leaders in the integration space.
