This article describes how to read counters when reporting new counter values.
The alternative is that the counter values are automatically inserted from another system. It can be, for example, a SCADA system. In that case, the user will not need manual readings.
First, open the counter screen.
From the overview screen, check the counters for which you want to enter values.
Then press "READ COUNTERS".
The counter reading box will now open. The focus is on the first counter and the columns in which you can enter data are highlighted.
The first field to consider is the date of the reading. INEXTIA will automatically set today’s date in the date field. If the reading you are reporting is not from today’s date, you can change it in the date field.
The next field is the value. You can report the value that the counter has shown here. INEXTIA shows the unit that the value has and the last reading can be seen in the field to the right.
The last field is a remark field. This field can be used to write a short remark to the reading. Filling out the field is not mandatory.
When finished typing in the values for all counters, click the “SAVE READINGS” button.
The chosen counters will now be updated with the new values.
Errors in Counter readings
An error message will show in INEXTIA if false data is typed in the date or value field when trying to save the reading.
In the example above, a wrong value was typed in the value field. INEXTIA will mark the field with a red exclamation mark, showing which field that contains false values. When placing the mouse over the red exclamation mark, further information will show and explain why the data is invalid.
When typing a value that breaks a rule from the counter type, INEXTIA will show a warning when pressing the “SAVE READINGS” button. Read more about counter types here.
In the example above, a rule of the counter type “hours” could be that there is maximum 24 hours per calendar day. The reading above contains more than 24 hours per calendar day.
When receiving a warning, it is possible to change the value and pressing the green “Approve” button. It is also possible to keep the value that was originally typed by accepting to break the counter’s rule to add the value to the system.
Rules for the different counter types are therefor guidelines to help avoid reporting error readings but does not force the user to report certain values.
Relation to Component
The components that are related to the counter will be affected when the counter gets updated with a new reading.
Since the components are counting from the moment they are related to the counter, they will not necessarily follow the counter.
As an example, if a company car is created in INEXTIA then the odometer of the car will be created as a counter. Certain components will be changed during the car’s lifetime. The car’s brakes could be created as a component. If the brakes are changed when the car has driven 70.000 km, then the new brakes (the component’s) counter value will be 0 km while the odometer’s counter value will be 70.000 km. When the odometer is updated to 70.500 km, 500 km are now added to each component and the brakes counter will there for show 500 km.
Overwrite component counter history
Because the component count from the time it was related to the counter, and does not necessarily follow the counter, you may end up in a situation where you forgot to relate the component to the counter from the beginning. This will result in value of the counter and the value of the component not following each other.
Using the previous example with the company car, the engine of the car could be created as a component but without relating it to its counter. In that case, if the car has driven 70.500 km and therefor the engine has ben running as well, the engine’s counter would still be 0 km, even though it has been running for 70.500 km.
This mistake can be corrected by using the function “OVERWRITE COUNTER HISTORY”.
When using this function, all readings belonging to the counter will be copied to the component (counter history).
If the component has already received some counter readings, meaning that it is connected to the counter, but was connected too late, then those readings will be overwritten with those from the counter. This explains the name of the function. The counter history belonging to the component will therefor always match the counter when using this function.
Delete counter reading
If an incorrect counter reading had been submitted, it should be deleted, since this will affect the connected components and next date on jobs. Read more about this connection here.
Delete a counter reading by clicking the “EDIT” button and checking the box for the reading that is incorrect. Click on delete (trashcan icon) and then click on “SAVE”.
The counter reading will now be removed from the counter and from the components connected to the counter. If any jobs are connected to the components, using a counter frequency, a new next date will be set for the jobs.
Article is closed for comments.