Objective Our client, a multi-discipline infrastructure services partner, had recently been through a Field Service Mobility Selection process. They wanted to develop a bespoke Field Service Mobility solution. This was their third attempt at implementing this type of software. The last two attempts had failed, based on their lack of functional and technical design requirements. This project ended up being …
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 …