The eReplicator™ Solution

eReplicator and its definition dictionary have been configured to recognize the patterns of enterprise systems on all levels: from application design and business logic to mundane tasks like validation and presentation.

Garpac can build eReplicator™ systems in a fraction of the time for a fraction of the cost. The patent-pending eReplicator technology provides us with an unprecedented advantage over traditional ERP/SCM vendors. eReplicator systems are not built by writing and compiling traditional code. Instead, Garpac populates eReplicator's definition dictionary, a special database that describes the user interface, the business logic, and the data structures. Based on the definition dictionary entries, or metadata, the engine then presents a completed system to the user in real-time.

The definition dictionary, sometimes called the system database, is separate from the user database that the completed system uses to store business data. In fact, the user database itself is built with definition dictionary entries.

The definition dictionaries are populated using our special proprietary tools, which are optimized for ERP/SCM system development. eReplicator has a tool set, and a set of definition dictionary tables, for all aspects of the system, including:

As functionality is added to the definition dictionary, it is reflected in the runtime system in real time. More importantly, any changes to the system are reflected immediately.

eReplicator is not merely a code generator. The presentation layer (user interface) is interpreted from the definition dictionary at runtime. There are two engines for interpreting the presentation layer: a rich-client (Windows) engine, and a web engine. Both engines fully understand the same entries in the definition dictionary. When Garpac's consultants¹ populate the definition dictionary, Windows and web versions of the system are immediately available. Both versions may run at the same time within an organization.

Also, eReplicator is not merely an interpreted system. When Garpac's consultants build and save data layer and business logic entries, the engine instantly creates and modifies a real database (the user database) with real tables, stored procedures, and triggers. This architecture ensures that the system has maximum performance and reliability, and can still be easily changed, even after installation.

Using traditional methodology, even with available CASE tools, it typically takes 20-40 man-years (40,000-80,000 hours) just to build a base system for an industry vertical. In contrast, the eReplicator definition process allows us to construct a complete industry-vertical ERP system from scratch in only 3-6% of what it takes others, and what it used to take us.

However, an ERP system rarely needs to be constructed from scratch. Once a base model is built for the target industry, additions and modifications can be completed in that same 3-6% of the time required using conventional procedural or object-oriented development techniques.

Garpac can change eReplicator systems quickly, and often instantly. With a traditional ERP system, customization, maintenance, and support costs incurred after system construction are typically 70% of the total cost of ownership.

In contrast, eReplicator's architecture is optimized for change. Modifications only require changing data entries, rather than recoding, recompilation, retesting, and reintegration. Reuse of metadata elements is much simpler and more straightforward than code reuse.

Since all elements of the system are represented in metadata, dependency mangement is easy. In many instances, changes ripple through the parts of the system that they affect. For example: if a field's data type is changed from an integer to a decimal number, all tables, forms, applications, inquiries, and reports that access that field automatically handle the change.

New applications, enhancements and functions can be delivered in about 5% of the time and costs required by traditional software development technology.

eReplicator systems integrate easily with legacy systems. eReplicator has Universal Database Connectivity™. It connects an eReplicator system in real time to any external database, and uses it as if it was part of the native user database. The external database only requires an entry in the definition dictionary, and can then be used as if it was native to eReplicator:

This means that existing legacy systems don't need to be thrown away. Not only can legacy systems be used together with the new eReplicator modules; the power of eReplicator can be applied directly to the legacy system itself. For example, inquiries, reports, and even new applications can be built that consume the old system, but codelessly and at lightning speed. Existing users can keep using any portion of the old system.

For a more detailed description of our technology, select any of the "Technology" items from the menu on the top-left.

¹ Garpac's consultants are different from its programmers. Consultants populate the definition dictionaries to build the ERP/SCM system. They need to be experts in the target industry, but might not necessarily be programmers. Garpac's programmers are highly technical software developers who have built the eReplicator engine without being experts in any target industry. This split in roles allowed us to hire the best people from a wider pool of candidates, since we were no longer beholden to entrenched, rare programmers with target industry experience.