Janus ERP integration services

ERP Janus client API

Have you noticed that e-mail, which until quite recently seemed very convenient and modern, now seems to be a washed-up form of communication? Not long ago, it felt fast and convenient to receive a file you needed by e-mail. But now, what to do with that mountain of messages and their various attachments? How will you find the thread containing the information you need?

When you’re using web services, the idea of needing to make a preliminary phone call to specify what information you need seems anachronistic, while the response  “Tell me what information you require and I’ll send it to you by e-mail” is enough to make anyone cringe.

Janus always tries to keep up with the times, and recently, the company’s R&D department created a software interface that allows our clients to obtain information about the cost of the projects they are working on with Janus.

This development aimed to resolve a couple of issues for the client:

•             Obtaining cost information (estimates) automatically, without having to go through a manager;

•             Getting the information soon after placing a project order.

The R&D department created a service that integrates MemoQ with ERP Janus, the company’s information system, and developed a client API where the customer receives project cost information at the right time once an order has been placed.

A pilot of these new services was successfully completed in January, and the additional customer requests that inevitably emerged along with the more advanced system were fulfilled.

The services are universally designed and the ability to receive estimates only via the ERP API is conditioned by a specific client’s wishes rather than by the capabilities of the API service. In principle, it is possible, by agreement, for customers to receive extended information about the projects placed with us through this service. All client expectations can therefore be fulfilled, and our database is ready.

I should also add that the primary goal of R&D is to develop such useful services. This fits well with the global trend towards microservice architecture. In simple terms: there is a certain monolith in such architecture, for example, a company-wide information system that affects all departments, which means it is vital that changes are made quickly. It’s like an existing multi-story building: often hard to rebuild. And that’s where small, individual programs – services that allow you to take the elevator up to any floor of the building – come to the rescue, as they are easier and faster to write or change as required.

R&D tracks global trends and tries to be guided by them in its work.