The TMO, TMX-O, ISS and IMX Back Office solutions are currently providing solutions for existing customer requirements. IMX have a architecture model for their future applications that effectively will provide .NET solutions to organisations which will integrate with the IMX Back Office and Distribution solutions. IMX are transforming their products and services from an ASP based model.

Our POS applications support multiple currencies, which are user defined.

By utilizing the Active Directory security, users are not required to maintain multiple passwords. Furthermore, security policy established at a corporate level is maintained and not overriden by the application. IMX prefers that Windows security profiles are used and maintained. Wherever possible, IMX tries to maintain all specific enhancements for a client through user exits.

Our systems have been designed for a 24-hour operation. Multiple End of Day (EOD) and Start of Day (SOD) runs can be executed within one physical day to reflect different operational shifts.

The IMX Back Office solutions is a centralised control system for the remote retail sites.

The product can or has already been translated to any language supported by the Microsoft Windows environment including Kanji and simplified Chinese.  

Our POS applications does support multiple tax structures.

IMX arrive to risk management processes jointly, as risks vary from customer to customer. Areas that need to be managed are enhancements, testing and implementation tasks.

All project developments and software implementations undertaken by IMX and their partners, deliver applications using the Microsoft Solutions Framework (MSF) to limit the risk.

IMX uses its online IssueTracker system to track all problems, enhancements and system changes. This information is used and made available to clients. 1. Helpdesk are raised by the Licensee for all problems encountered with the Product. A form may also be used to request enhancements by the Licensee for the Product. Whenever a problem is encountered or an enhancement is required, the Licensee will complete the details on IssueTracker. Priority 1 and 2 calls can be notified to IMX via phone or facsimile, and IMX will enter the problem into their IssueTracker system. On receipt of the details the IMX will act on the details on their request for service system. If an estimate is required the details of changes and costs are completed in the appropriate section of the RFS form and then faxed/emailed to the Licensee for authorisation. On receipt of the RFS the Licensee will review the estimated costs and may approve the changes by completing the relevant details on the bottom of the RFS and faxing/emailing the form back to the IMX where the RFS is then allocated for action according to its priority. Once an RFS has been allocated, IMX will be responsible for correcting/completing the problem, or enhancements which will be included in a new software release or patch and sent to the Licensee.  

Yes. On an agreed contractual arrangement.  

Initially a Request For Service (RFS) is raised by the customer. On receipt of the RFS at IMX will record the details on their internal system. If an estimate is required the details of changes and costs are completed in the appropriate section of the RFS form and then faxed/emailed to the Licensee for authorization. On receipt of the RFS the Licensee will review the estimated costs and may approve the changes by completing the relevant details on the bottom of the RFS and faxing/emailing the form back to the IMX where the RFS is then allocated for action according to its priority.