We are working with some customers who are doing fuel management, so I would like to use this topic to start to see what the community thinks about tags for Fuel.

Equip would be a tank. Marker tag on a Fuel Tank would be "fuelTank"

The amount of gas in a tank would have the following markers/tags "volume", unit=="gals", point, sensor

The capacity of the gas tank would have the following markers/tags "capacity", unit=="gals",point, sensor

The % filled on a tank would have the following tags: "capacity", unit=="%", "level", "point", "sensor","curLevel"????? (Not sure on what to tag the current level of a tank. We have 2 of these, one current level in inches, and another one current fill level)

premium gas should be a tag called "premium", this tag should go on the equip/fuelTank. For unleaded gas should be a tag called "unleaded". For Diesel gas should be a tag called "diesel".

I'm not an expert in this field, so I'm just throwing out suggestions.

We probably need an expert on fuel tanks to finalize, but I think we can probably come up with pretty good straw man.

I think tank is definitely the equipment, and marker tags might include:

• fuel
• unleaded, premium, diesel

Capacity is really a fixed fact on the tank, not a sensor so I think it would just be a numeric tag on tank measured in gals or liter.

Sensors on tanks probably require some expert input, but from what I've seen:

• volume
• tcVolume (temperature compensated)
• ullage
• water level
• temp

I don't know exactly how volume + ullage + temp compensated volume is typically mapped to sensors vs computed, etc. We need some advice there

There can be more types of "contents" of a tank that just gasoline, and different companies may have very specific labels they want to apply to grades or "products"...

What is in the tank would be termed a "product"..

It could be fuel oil, kerosene, or some grade of gas.

tankNumber = Ordinal Number of Tank on the site (matters for some uses) des = Description of name in customer terms... ex:

tankNumber = 1, des = "Premium" tankNumber = 2, des = "UNL1" tankNumber = 3, des = "UNL2" tankNumber = 4, des = "Diesel"

What can get us into the weeds here is sometimes you can have a partitioned tank, where for the inventory and Product there could be 5 tanks, but for the sensors (below), there are only 3 REAL physical vessels..

Along with inventory, there are also "sensors"... which are probes that measure that everything is "ok" on a site.. some are associated with tanks, others aren't...

sensor des = "Tank 1 STP" sensorNumber = 1 tankNumber = 1 sensorState = Enum State sensorValue = Resistance of Sensor for Diagnosis

sensor des = "Dispenser 1" sensorNumber = 2 dispenserNumber = 1 sensorState = EnumState sensorValue = Resistance of Sensor for Diagnosis

Dan

I think the most important tags to figure out are the terms used for the sensors.

Dan, when there is one physical tank partitioned, is there is just one set of sensors shared? Or do they have sensors in each partition?

Sensors don't associate with tanks all the time..

Ex:

Each "tank" would have.. Fill sump

Interstitial (referred to as brine in trade, area between tank walls filled with salt water)

Sump

Each dispenser would have a sensor in its sump, these sensors would not be associated with ever tank (imagine a container under each fuel pump to catch gas, and detect it for alarm).

So something like this..

equip = Fuel Console (tags = status and alarms about the system itself, paper out, internal faults, status, and so on..) equip = fuel tank1 (tags = points and sensors associated with tank) .. equip = mpd1 (tags = points and sensors associated with tank, right now for us would just be sensors, but in future could be more information, such as performance of dispensers... transactions, flow rates, and the like). I know there is some desire by others to get this type of information in the future.

equip = mpd2

Dan

I'm building this out by hand now to see how it works out.