Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
best_practices [2019/08/02 17:51]
tmuvee
best_practices [2019/08/05 11:27] (current)
tmuvee
Line 26: Line 26:
         U->>​TSOPS:​ Read connectivity status (to verify succesful installation)         U->>​TSOPS:​ Read connectivity status (to verify succesful installation)
 </​uml>​ </​uml>​
 +
 +===== Build thing identity in Thingsee (instead of customer cloud) =====
 +
 +Thingsee Field Operations services provides a full-set of functionality so that the identity of the usecases, devices, locations and assets can be build and fully managed within Thingsee Operations Cloud. This is a perfect option for customers who don’t have existing customer identity pool or APIs, or want to move to use full Thingsee Field Operations solution to manage their device/​asset fleet.
  
 ===== Do not use gateway identifier (tsmGw) for business logic ===== ===== Do not use gateway identifier (tsmGw) for business logic =====
  
 Do not use tsmGw information within Thingsee messages to identify your installation,​ location or a customer. If your customers A and B are in close proximity, then it is fully possible that some customer B sensors are routing through customer A gateway and vice versa. Therefore you must build your customer identity and inventory based on the sensor'​s tsmTuid information only.  ​ Do not use tsmGw information within Thingsee messages to identify your installation,​ location or a customer. If your customers A and B are in close proximity, then it is fully possible that some customer B sensors are routing through customer A gateway and vice versa. Therefore you must build your customer identity and inventory based on the sensor'​s tsmTuid information only.  ​