Objective We have a long-term client who has been undergoing a time of significant change. This change was bringing in new software systems, as well as modified business processes. As part of the implementation of the new software, Senior Management wanted to avoid manual integration. They also wanted to allow for software systems to easily talk to each other, where …
Parent Company Reporting – 3 clients, 3 needs, 3 ways
Objectives Our clients often have challenges meeting Parent company or Head Office reporting requirements. And the challenge increases if they’re using ERP software, or financial software, which is different to the rest of the Group. It’s common for a business to go down the path of getting staff to manually piece the data together – their justification is that it’s …
Solving Out Of The Box API limitations
Objective Our client had an existing, simple integration in place between their ERP and a Field Service software package. They wanted to expand on this integration, but the integration methods provided by the Field Service software had changed. Instead of “pushing” data changes to the ERP, they now only provided Webhook subscriptions. The client’s ERP software was unable to manage …
Rectify and Expand simPRO to ERP Integration
Objective Our Construction-industry client had a pre-existing integration built between simPRO and their ERP system. This integration had been built by their ERP vendor for them and was reliant on having IBM middleware in place, hosted by their ERP vendor. We had been involved in the original work to develop process and data translation for the integration and at the …