# Schema design best practice, storing equipment measurements

**URL:** <https://community.influxdata.com/t/schema-design-best-practice-storing-equipment-measurements/6730>\
**Category:** Store\
**Tags:** influxdb\
**Created:** [September 25, 2018, 3:10am UTC](https://community.influxdata.com/t/schema-design-best-practice-storing-equipment-measurements/6730 "2018-09-25T03:10:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bnjroos](https://avatars.discourse-cdn.com/v4/letter/b/e9a140/32.png) [@bnjroos](https://community.influxdata.com/u/bnjroos)\
**Post date:** [September 25, 2018, 3:10am UTC](https://community.influxdata.com/t/schema-design-best-practice-storing-equipment-measurements/6730/1 "2018-09-25T03:10:10Z")

</div>

Hi,

I am new to influxdb and wondering what would be the best schema design for a system I want to implement. I have about 80 power meters and want to store data from each of them such as: load on each phase, total kvar, total kWh…

What would be the best practice to implement such system :

1. 1 measurement per power meter then fields with measured parameters ?
2. 1 measurement per measured parameters then using tags for power meter location and id ?

Thank you in advance,

Bnj