Have you ever run into a situation where a single value on a device could represent multiple values at the same time? How would you display a nice string representation for all the potential values? I recently saw this problem solved on an Emerson device where a TLP contained multiple values packed into a single byte. The solution used a combination of multiple reference DEIDs and a few associated enumerations.
There’s a new request in town, and it goes by the name “Request New Device Data” (and boy, does it mean business!).
In ye olde tyme Gas Measurement Repository (GMR), there was only one way to get data from the field, and that was by using date-based requests. When using a date-based request, you essentially are asking the devices: “What data do you have from 3 days ago until today?” This approach works for some cases, but isn’t very robust in other scenarios, many which are unforeseeable. Administrators typically need to build safety nets to handle any communication down times so that there is no data left uncollected