How to make an infoblock architecture?

Question

1C-Bitrix

I am making a website for a network of gas boilers.
Every day, the boiler house heats cold water and delivers it to the facility. There are daily statistics on three parameters. Temperature 1, Temperature 2, Gigacalories
Until I came to the conclusion that

• 1 infoblock - Boiler room
  
• 2 infoblock - Object
  
• 3 infoblock - Statistics
  

As I understand it, the element of the infoblock Statistics will be "one day". But the statistics include monthly figures that need to be driven in somewhere. This is the amount in rubles for payment and the amount in rubles received on the account.
Where to shove it - I have no idea.
There was an option to drive 31x3 properties into 1 element of the infoblock and form a monthly element. But somehow this way seems to me not very correct.
How can I make the structure of infoblocks correctly? Which infoblock should be linked to which one? Are sections necessary?

Answer 1

Somehow everything is complicated for you .... There should be a "measurement" infoblock, it contains the fields T1, T2, date, link to the Object, gigacalories.
And in general, this is not necessary! Just bind a highload block with the same fields to your Object! You pull out the object, from it you pull out the records from the highload block for the desired month. It will work very fast.
In other words, you have only two infoblocks Substation and Facility, and one highload block associated with the Facility with results for the required date.
And if you think a little more, you can also transfer the Substation from the infoblock to to the sections of the Object infoblock. Then you will have only one infoblock Object with catalog sections in the form of Substations (a section can also have its own properties and more!), and a highloadblock!
If it's not clear, ask.
PS. What is good about making substations in the form of sections - you can organize them in a tree structure as you like, for example, territorially, and search and measurement results - everything will be logically connected, expandable and without unnecessary entities. Well, for example, you can set access roles for users at the section level to Objects.