In general, independently where the software is hosted, our web services receive data from the AMS, triggered by the AMS, when the AMS creates a cage card based on a changed cage content or when flashes are requested. The AMS can get feedback from our web service by the return messages for all transactions it triggered. Additionally there are web service methods like, get status of the label, get roaming status, get locations, get inventory and get billing records. It depends of the AMS provider, how deeply these standard methods are integrated.
In some cases, it would really make sense that our web service actively posts data to a web service offered by the AMS offers not triggered by the AMS.
We currently know 2 situations where it would make sense for the AMS to actively offer web services:
a) To update the topical location automatically. E.g. The user moves a cage from one room to another but does not update the AMS with the new location actively. As I told the Pricer Server sends broadcasts to get status and location from a cage label on certain intervals. The location could be automatically updated in the AMS if the AMS offers such a web service.
b) To save alerts, which we record on the base of our buttons in the Warehouse/Cards-database. We are offering colored buttons which signal certain cage states in the animal room manually. With the App a user can message e.g. “Animal found dead “, “Animal sick”, etc. to a receiver (e.g. Animal Welfare officer or Scientist) outside the animal room. When the user, e.g. Animal Welfare officer later enters the animal room, to take care about the cage and animals he was notified, all cages where some work must be done can be flashed. This App uses web services of the Warehouse/Cards-Database but not automatically forwards these alerts to the AMS. To get those alerts also the AMS must offer a web service.