A central solution - the Sebring Software server

By using adapters to handle communication between the desktop and the application the access to the data in the different enterprise data stores and applications become neutral. The advantage of the system is the uniform treatment of business objects, whose individual information components originate from different systems. The common data model is independent of the underlying.

The server product's main purpose is to handle transactions between the desktop client and the application. To do so in a neutral way, the server has mapping functions that understands the application data model and operating sequence. This is the essence of the Sebring Software adapter (to a specific application).

Adapter exist already for the most common PDM/PLM products, and a myriad of MRP products and the platform delivers different standard protocol adaptors such as JDBC and SOAP.

There is even an adapter that deals with legacy data through screen scraping methodology. Where we do not have an adapter, one can easily be "adapted" to a program that we have not dealt with yet.

The Sebring Software server is then the collection of adapters, the configuration center for different user profiles and traffic cop for the different data served to users.

Sebring Software data model structure takes place in different levels of the Sebring Software architecture. Adapters hold the data model information, which is a description of the model and its mapping to application. The server then performs inquiries to the meta file of the adapter when the client does an inquiry. The mapping translates the inquiry into a proper function in the application. It is very advantageous to implement these tasks in a central place. This greatly simplifies managing changes and additions to the system. You only have to make changes in one centralized place.