The real-time data exchange will be available for the following collections:

  • points
  • schedules
  • alarms
  • references

Only some specific fields will be updated, they are detailed below.


Point update

There are two possible changes that can trigger an update of the Mongo document:


There are multiple options that can be activated by the MSI for the point update:

  • A point update can be forced every x minutes/hours so you're sure that you get the same value that is currently in the BOS. Ask your MSI, it's an easy option to activate.
  • A minimum time between two updates so you don't capture too many changes. A point value can change every second in the BOS and then trigger changes in the Mongo document every second. Again, ask your MSI if it's not acceptable for you.
  • A minimum value change for Numeric Point only. For example, if a temperature doesn't change by at least 0.1, then no update is triggered. You can combine it with the other options.



Schedule update

There are multiple possible changes with a Schedule Data asset to trigger a document update:

  • A single event is created/updated/deleted by a user or by a third party
  • A regular event is created/updated/deleted by a user or by a third party
  • Time is flowing, the schedule output changes so is the next event as well



Alarm update

There are three possible changes with an Alarm asset:

  • The alarm event is generated. The document is generated in the "alarms" collection.
  • The point value returns to its normal state, then the existing document is updated.
  • The alarm event is acknowledged by a user or a third party

Please note that alarm acknowledgment can happen before the return to normal.




Reference update

Every time there is a modification on a Reference, all its fields are updated in the Mongo database.