In designing collaborative forecasting, especially in a complex organization like UC with multiple acquisitions and territories, it's crucial to consider the system's performance. When a sales user is assigned to multiple territories, and they work on numerous opportunities, it can significantly impact the system's ability to generate accurate and timely forecasts. Salesforce's own documentation on collaborative forecasting emphasizes the need to carefully manage territory assignments and forecast calculations to maintain system performance and forecast accuracy.
References to these considerations can be found in Salesforce's Release Notes and Administrator Guide, where Salesforce discusses best practices for managing territories and forecasts in complex sales environments.
https://help.salesforce.com/s/articleView?id=000199046&language=en_US&type=1

Platform Events are a Salesforce-native feature that enable apps to communicate inside and outside of Salesforce using an event-driven messaging architecture. An event producer creates an event and adds it onto the event bus, which operates as a queue with a strict chronological order. An event consumer subscribes to an event and gets notified when the event is put onto the event bus.
According to 3, Platform Events can be used to define and manage custom notifications within the Salesforce platform and in external apps. They can also be used to integrate Salesforce with external systems and devices in near real-time.
Therefore, a Solution Architect should suggest utilizing Platform Events based on the devices' state change. This way, UC can connect the data from the smart devices to Salesforce in a scalable and reliable manner, without having to poll or query for changes constantly. UC can also use Platform Events to trigger workflows or actions based on the device status, such as creating a case, sending an email, or ordering a replacement part.
https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro.htm