Computed attribute dependent on another computed attribute

I know that it's not good idea, but!

I receiving temperature attribute io11 and create computed attribute which calibrate io11, tempCalculated.

The problem is, when powerCut appears, io11 change its value to 2_000_000, which impact very much temperature report.

Is it possible to rewrite io11:

io11
io11 ? io11 < 2000000 ? io11 : null : null
number
And
tempCalculated
io11 ? io11 < 2000000 ? ((io11 <= 200.00) && (io11 >= -100)) ? io11 - 4 : io11 : null : null
number

You can't have dependencies between computed attributes because the order is not guaranteed.

Is that so important?

What if received io11 as position attribute?

case 1, not processed io11 as Computed attribute.
tempCalculated found 2000000 and skip this value.
case 2 processed io11
tempCalculated found null and skip

Is that correct?

I'm retard. I have deviceTemp for this report where deviceTemp is computed attribute from io11.
tempCalculated from io11 and powerCut alarm from io11.

Sorry about this topic.