Request for adding data point naming for the landlord systems

[RathishKJ]

Hello,

Please provide concurrence to enable pull requests for the below ontology which are not available in the telemetry fields.

1. supply_water_pressure_sensor--> This is basically for the water tank (to measure the Line Pressure in Main Header in Main common line which is being used for Hydrant and Sprinkler)
2. potable_water_tank_level_status --> this is to measure the water level of the softened water under the base builder systems
3. conditioning_water_tank_level_status--> this is to measure the water level of the treated water under the base builder systems
4. average_voltage_sensor--> This is for measuring the output voltage of the Diesel Electricity generator
5. average_current_sensor--> This is for measuring the output Current of the Diesel Electricity generator
6. battery_voltage_sensor--> This is for measuring the voltage of the batter used in Diesel Electricity generator
7. oil_temperature_sensor--> The oil temperature in Diesel Electricity generator
8. oil_pressure_sensor --> The oil Pressure in Diesel Electricity generator
9. tank_level_status--> The tank level status is being proposed for measuring the level of media in different types of tanks like Fire water Tank, Flushing water tank, Domestic water tank, Raw water tank, Lift Pit Drain Level Monitoring, Storm Tank, and diesel tank in Diesel electricity generator
10. high_speed_status--> To know the high speed status of the Jet Fans
11. low_speed_status--> To know the low speed status of the Jet Fans
12. input_water_tank_level_status--> To measure the level of the raw water tank

regards, Rathish KJ

[tasodorff]

Some comments on the proposed fields above:

Good with these:

• supply_water_pressure_sensor
• oil_temperature_sensor
• oil_pressure_sensor
• high_speed_status: fine with this, assuming it has states of ON and OFF
• low_speed_status: fine with this, assuming it has states of ON and OFF
• battery_voltage_sensor: this is acceptable as long as the battery is modeled as part of the generator; if you are modeling the battery independently (that is, if it will be a stand-alone entity in the building config) this would need to omit the battery subfield and specify the voltage measurement specifics (what it is measuring voltage difference across).

Questions on these:

• potable_water_tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary. See below.
• conditioning_water_tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary. See below. Also, the term conditioning would need to be defined. What are you proposing for a definition here?
• average_voltage_sensor: For voltages, we need to know what the voltage difference is being measured between (e.g. phase1 to neutral). Please specify.
• average_current_sensor: would prefer to indicate this is the output, so average_output_current_sensor seems most appropriate.
• tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary. See below.
• input_water_tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary. See below.

Tank Modeling: If you plan to model the tanks as independent entities, you would not need to include the keyword tank in any of the fields. And, if you have a separate tank for potable and conditioning water, you wouldn't need the keywords for conditioning or potable either -- it would be obvious since the fields would be on the conditioning tank or the potable water tank.

Hope this makes sense. Please let me know if you have other questions.

[RathishKJ]

Good with these:

supply_water_pressure_sensor --> Ok
oil_temperature_sensor --> Ok
oil_pressure_sensor --> Ok
high_speed_status: fine with this, assuming it has states of ON and OFF -->Ok
low_speed_status: fine with this, assuming it has states of ON and OFF--> Ok
battery_voltage_sensor: this is acceptable as long as the battery is modeled as part of the generator; if you are modeling the battery independently (that is, if it will be a stand-alone entity in the building config) this would need to omit the battery subfield and specify the voltage measurement specifics (what it is measuring voltage difference across). --> battery is modeled along with the generator, hence would be including battery in the subfields

Questions on these:

potable_water_tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary.--> **Yes it is the tank and we are measuring the level of the portable water tank. Hence we would be omitting the Portable water tank and the data-point would be just the "level_status"**
conditioning_water_tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary. See below. Also, the term conditioning would need to be defined. What are you proposing for a definition here? --> **level_status. Same as the above**
average_voltage_sensor: For voltages, we need to know what the voltage difference is being measured between (e.g. phase1 to neutral). Please specify. --> 
average_current_sensor: would prefer to indicate this is the output, so average_output_current_sensor seems most appropriate.--. Ok
tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary.  level_status. Same as above
input_water_tank_level_status: Is this on the tank itself? If so, the tank subfield should be unnecessary.  level_status. Same as above

[charbull]

@tasodorff @mschulze17 ping