Enterprises today have applications that cater to back end processes. ERP and CRM systems are established in almost all organizations. The challenge is to ensure that these are used optimally. Mobile devices and telecom networks provide the last mile connectivity to extend the reach of these applications to persons in the field.

However, the infrastructure that supports these enterprise systems is massive and additional mobile users on the existing infrastructure can lead to performance issues, considering that 4 out of 5 workers operate outside their offices.

Therefore there is a need for a mobility infrastructure that can cater to multiple platform devices, multiple networks, rapid development, ease of deployment, extending the reach of enterprise applications with no degradation of performance.

FRED MEAP provides a flexible, open standards based infrastructure which is highly scalable and device and network agnostic.

FRED MEAP is the foundation on which all our mobile enterprise solutions have been built.

Programmers use Eclipse, the internationally accepted IDE, in conjunction with the FRED Designer, a simple table-based tool, to define the user interface and build in business logic, workflow logic and logic for connecting to enterprise systems. The user interface design is built as a client application that is downloaded on to a device or as an HTML that can be invoked by a smartphone browser. The entire logic (business, workflow and enterprise connectivity) is stored in FRED Views which are business objects in XML format.

FRED Views are invoked within the FRED Platform Server which is a high performance transaction engine. The client application or browser application on the mobile device sends a transaction request through the Front-End Controller, which is a messaging layer, to the relevant FRED View running in the FRED Platform Server. If data has to pass from or to a data source or enterprise system, the Component Calling Interface is called, if required.

As the FRED Views embody complete logic of the application, the application can be modified by modifying the FRED Views using the FRED Designer.

The FRED Platform Server can also invoke native components built to perform specific tasks.

This module is used by the system administer FRED applications as well as users and devices.

TOP

BENEFITS OF FRED MEAP

FRED Designer lowers the cost of development by using simple table-driven interactions. Programmers with lower skills & experience are required. Mobile enterprise apps can be built by AccelTree or by any other vendor using AccelTree’s development tool kit.

FRED Views are the foundation of the platform. FRED Views are complete with business logic, workflow logic, data and external interface mapping. This makes transition from one device to another much faster.

Typical MEAPs operate as single point conduits for information to and from an enterprise system. They lack the ability to process data with business logic.

The FRED MEAP, in addition to having the capability to operate as a conduit for information, can also be configured as a complete front-end system for taking the load off an enterprise system.

An example is a loan origination application residing as a set of FRED Views that processes loan application with necessary document workflows and passes it on to the enterprise system only when the loan is approved.

The FRED Platform Server is C++ based and is able to handle very high transaction load with negligible degradation of response times. It can be deployed on a variety of server environments to suit an enterprise.

The platform requires less than 50% of server side hardware/software compared to any other platform.

It is highly scalable to handle the long-term growth plan and any number of applications.

Application deployed on a wide variety of mobile devices ranging from low-end phones to high-end Android phones can work with the FRED MEAP. There is a clear path for future developments in device technologies.

Using the FRED Platform Server’s Component Calling Interface, the platform is capable of interacting with varied data sources and multiple enterprise systems simultaneously.

On phone - Download of client is controlled with single access key, if required. Applications use a thin client hence minimum or no logic on phone. Transactional data is not normally stored on phone. If data is stored for operational reasons, it is embedded in the application and not maintained in a file system. Passwords not stored on phone. First user screen is the password screen. Authentication based on user ID + password + device ID. An application is not accessible if user authentication fails.

During transmission - SSL encryption is possible. Message keys authentication for whole session or for each message is available. Data integrity is maintained by mobile app or FRED Server automatically by resending a message when not received completely.

On the server - Server physically located behind a firewall. Authorized data administrators only have access to it through password controls. FRED Server itself acts as a shield for data stored in the enterprise systems.

TOP

DEVICES & NETWORKS SUPPPORTED

• iPhone, iPad • Android, including tablets • Windows Mobile 7 • BlackBerry • Symbian • BREW • Low-end Java phones

GPRS, Edge, 3G, 4G, CDMA, W-CDMA and even SMS messaging as a data transport layer.

All hardware servers (including all Linux variants) are supported; so are most Web Application Servers and any SQL compliant database.

TOP