Overview

eMESA is not a traditional integrated application. Most applications that are “integrated” use the term loosely. eMESA is different. eMESA is a true alternative user interface.

The components that allow eMESA to work its magic are outlined below:

Presentation Layer

The presentation layer of eMESA provides the entire user experience for an eMESA user. In the presentation layer, the user experiences an intuitive Web 2.0 / AJAX experience that is simple, effective, and easy to learn. Use of advanced user interface techniques as well as visual indicators such as effective color schemes and graphical navigation provide the user with the best experience possible. Our team of dedicated engineers works hard to make sure that the user doesn’t have to go through too many tabs, too many clicks, and too many headaches to accomplish simple tasks.

Cache / Search Engine Layer

Certain elements of data that change relatively infrequently in the source system the eMESA system will cache for improved speed. Equipment Master, Material Master, System Table Codes, etc are cached every few hours for greatly improved speed. In addition, eMESA’s internal search technology offers searching that spans multiple tables and multiple fields for relevant, accurate search results.

eMESA Web Service API

The eMESA Web Service API provides an XML Web Service programmable interface that external applications in addition to the eMESA Presentation layer consume to communicate with back-end systems. Completely programmable and standards compliant, the eMESA Web Service API allows any application to transparently communicate with back-end ERP systems.

ERP Integration Layer

The eMESA ERP Integration Layer serves as the connectivity layer between the underlying ERP system and eMESA. Built from the ground up using Service Oriented Architecture (SOA), the eMESA Integration Layer handles the communication with each ERP API. Different technologies are applied given the different interface requirements for the specific ERP applications.

For more technical please see System Architecture and System Requirements.