Cotere’s original product was Access Point a software portal for delivery of public records like vehicle, driver, credit, health or similar. However even in 2004 that industry was crowded and as Cotere found it difficult to compete we were looking for a way to pivot. Since all potential customers commented on our ability to integrate any type of data it was obvious that we needed to productize our proprietary integration architecture.
As the above diagram depicts Relay Point has a virtual data repository at its hub with spokes of objects enabling the connections of various applications and or data streams.A full fledge IDE was created to accompany the architecture. It was build with Business Analysts in mind and required little to no prior programming knowledge to operate. Please note that below screenshots are from an application from 2004, so as you will see it was ahead of its time.
The Universal Data Format Designer (UDF Designer) was made as a simplified XML editor with custom types, making it easy for anyone to use with its point and click approach.
Custom segments could be saved for later use via drag and drop, minimizing time spent on standardized objects like address, phone or email.
Throughout design of a UDF document the user would be alerted to any problems in the document that would require modifications to match the Cotere document standards.
The Database Designer (DB Designer) was a design tool for creating databases that would match the data format set out in the UDF documents.
The advanced user would be able to customize the DB generation while novice users would be guide through the process via colored alerts in the document.
Thousands of lines of SQL would be autogenerated including with tables, views, stored procedures and triggers all in a matter of minuttes.
Data Connection Designer
The Data Connection Designers (DC Designer) purpose was to make it easy to map the individual fields in the UDF document to the .
Most of the mapping happened automatically based on UDF and DB layouts. However the business analyst could at any time modify the mapping for any field.
Stream Import Designer
The Stream Import Designer (SID Designer) enabled the analyst to tell the system how to import any data, whether XML, CSV or flat file.
Several tools had been implemented to assist the user, including lookup tables for mapping data values and active script coding for more complex imports. A vast library of pre-made lookup tables and scripts were included for known values.
One of the great features of this designer was the integrated debugger, which enabled the analyst to step through a file to be imported and see how each individual field got imported.
Process Tree Designer
The Process Tree Designer (PT Designer) brought together all the pieces in one place. Via a diagram (prior to any other tool taking this approach mind you) the analyst could drag and drop elements of the integration into the designer and by setting a few properties complete a full integration with business rules, notifications and database auditing in a fraction of a traditional integration.
Like with any of the Cotere tools the advanced user had access to the code for tweaking if necessary.