3-Tier Middleware

The software provider and engineer should not lose sight of the overall objective of maintenance management. It is to reduce operational costs while maintaining availability safely.

Engica’s role as a provider is to provide you with the necessary functions to do this at the application level but also to provide you an architecture that offers significant advantages for lower system life cycle costs.

We maximize the user ability to configure, customize and integrate the system. Using efficiency and easy to use techniques to do this safely.

This is achieved with our three-tier technology. The three-tier model keeps data and processing functions separate from the user interface. Front-end user forms can be very light as the architecture uses "thin client" technology. It is also highly flexible, as companies can decide whether the bulk of processing is carried out at the server level or an each individual personal computer including a web browser.

The following highlights provide some of the advantages that you will obtain from the Q4 Power 3-tier architecture

• Extend Q4 Power to add features and details specific to your own business
• Customize Q4 Power by redesigning or replacing user interfaces
• Integrate Q4 Power with other systems, using simple to use and “upgrade-safe” interfaces
• Standard, COM based interfaces place minimal demands on development tools or training requirements
• Free your users from fixed PCs by extending Q4 Power out to web clients by developing your own browser pages
• Program the COM based interfaces through C++, Visual Basic or even Microsoft Office applications
• Build PC-based rich clients and server based browser interfaces to Q4 without worrying about the CMMS functionality
• Select and extract arbitrary data sets for display, manipulation and reporting
• Provide your users with a “digital dashboard”, linked with Q4 and other business systems to give an instant overview
• Integrate easily with other business systems to avoid the costs, errors and irritation of duplicate entry
• Work to a defined and published interface, so that your code survives upgrades and simply “inherits” new or altered CMMS functions