Interfacing & Integration Software
We specialise in EDI between contractors and clients where other people fail, or where the end systems have no existing interface capability
Our core philosophy at Epix Systems is to eliminate waste and duplication. For typical repairs we see organisations handling the same item of information many times when processes could be implemented to reduce this. We start eliminating the waste from the very moment the job is reported , through issuing to engineers who are using PDAs, and finishing with an electronic request for payment that can be exchanged or emailed to your customer.
Throughout our products we have integrated as much information as possible to directly achieve the goal of information sharing and process improvement. For example, our call centre directly integrates with the repairs history from job control, whilst also seeing real-time activity from the mobile working solution to directly affect allocation.
All of our products have been made to work with systems from other suppliers using a variety of interface methods – from simple text files, through XML and SOAP interfaces, to direct API calling from within their application.
We have been interfacing to any and all client systems since the early–90s using virtually every mechanism you can imagine. We are still maintaining an interface for a customer using a fixed–field–length format that was first introduced in 1993!
In our experience the remote end of the interface will declare a specific format that it can generate and receive – and we have always been able to fit our end of the interface to these predefined requirements.
Whatever the requirement, we can meet it.
Benefits & Examples of Our Interfaces
Third Party Contractor Integration
Where a contractor is already successfully using a computerised maintenance system, Epix provide additional integration options. Typically, Markus is introduced as a middle layer between the client integration and the existing maintenance solution to provide a translation between the client's formats and the contractor's own system.
The benefits of this include the ability to provide the client with a standardised portal across all contractors, the ability for the contractor to extend their existing solution to integrate with multiple clients in a unified manner, and additional layers of redundancy and checking into the integration process in order to mitigate network or hardware failures with the contractor's legacy system.
When acting as middleware between systems, Markus can be used as little or as much as is necessary to gather and share information between all parties – either running as a headless automated process, or as an integral part of the contractor's day to day workflow.
Epix have a wide range of experience linking disparate system together using a wide variety of techniques - fixed file formats, XML, CSV, SOAP, custom APIs - and can act as either host or client to the transfer folders or web-services needed to link the client with the contractor.