@Joshua Roberto this is AMAZING!! I was thoroughly STUMPED and you make it look so easy π
Thank you for taking the time to help me out with a very thorough suggestion, super appreciate the video! I went ahead and configured to your suggestion and this is exactly what I was trying to achieve.
The use case is to replicate MaaS billing which relates to the 4HRA of consumption. I took your steps to arrive at minutes by hours 0-23. Then added a MIPS PER MINUTE field = (MIPS/INTERVAL LENGTH)*MINUTES to arrive at a directionally correct evaluation of MIPS consumption relative to the running time within each hour.β I say directionally correct because running time isn't = to running load but it's the only metric we have to leverage.
Then I grouped by ARTIFACT, DATE, and WHICH HOUR? to arrive at: XREF to pull in the PROUDCT and SYSID after grouping the 1MM rows into 30K

My MF folks want to see MIPS consumption by hours 00-23 of each day to identify the 4HRA and which ARTIFACTs are generating that peak. The 2nd bit is then to flush the Maas cost through the applications that own those artifacts since the billing is relative to only the peak and not the full population of MIPS.
#TBMStudio