4. Bringing the database to life

Once this initial work of inventorying and defining action frequencies has been completed, the database needs to keep pace with events. As we have just seen, some events are periodic (with periodicities that can change over time), while others are one-off events. It's important to record all events, because this information may end up being useful, even if it seems trivial.

For example, a pharmaceutical company looking to optimize the management of its autonomous temperature sensors was able to demonstrate that the main problem with these sensors was the state of their batteries. At the end of their service life, these batteries no longer had enough energy to process the signal obtained by the physical sensor, and the sensor was really talking nonsense (accuracy errors of several tens of degrees). This demonstration was made possible thanks to the information entered...