📇 feature: Electrical consumers

[ken-mellem]

Summary

Do due diligence and build up potential issues we will need.

Issues

• [Electrical consumers] Custom electrical network view #510
• [Electrical consumers] Grid endpoint (Backend) #511
• [Electrical consumers] Filter endpoint (Backend) #544
• [Electrical consumers] Join consumers from STID with FAM data (Backend) #545
• [Electrical consumers] Join isolated, disconnected from scope change api (Backend) #512
• [Electrical consumers] Create app frontend #513

Dependency

• Heat Trace: Circuit Diagram (Frontend) #482

Related

• 👑 Epic: Implement Heat Trace app #520
• equinor/lighthouse#372
• 👑 Epic: Implement Pipetest app #519

[ken-mellem]

Aman has requested data from STID to FAM.

[Gustav-Eikaas]

Current status:
FAM does not contain OGP data for electrical networks. They are informed that this is important to us and will work on getting the data. This data will come from STID. It is possible to go directly to STID to aqcuire the data but it will need to be joined with FAM/PCS data (checklists).

Going directly to STID

For main view (Table)

1. Query stidapitest.equinor.com/portal//ele-consumers
2. Filter tagcategory; 7 Main Equipment, 8 Electrical field equipment, 11 Heat tracing cable.
3. Query from every facility on projectmaster.
4. Add property to distinguish tags belonging to PM (Requires PCS data)
5. Join in disconnected status from local db

Should be cached for ~1 hr

For elenetwork

1. Query Query stidapitest.equinor.com/portal//ele-net-consumer?tagNo=
2. Join with checklist status using data from FAM

[Gustav-Eikaas]

Current status:
App is in a usable state(mvp). Data is fetched from STID and joined with fam information. Circuit diagram renders correctly in sidesheet.

[ken-mellem]

Setting back to Refinement - we need to find a way to get data - and a priority on this. @atlewee

[atlewee]

Get data:
I think we should be able to get this data purely from ProCoSys/FAM, and not require STID at all.
We can do that by traversing CompletionTagDetails (cables) fromTag/toTag from bottom until circuit/switchboard
Probably easier in code than SQL.
This connections (fromtag/toTag) change infrequently so running a process every 24h that builds a simpler table to further join data into could be a solution if direct sql is not possible.

Priority:
The user requesting and pushing for this has left his job, so no more pressure from him.
But this data is also used in Piping, HeatTrace + ReleaseControl. So we need this data anyway.

[ken-mellem]

Had a chat with Atle - I understand that we have the data but not in the model we need for the apps in question. @BenSvend can assist and assess if this is something we want to do in a view or if we should opt to calculate this on-demand on backend.

[Gustav-Eikaas]

App didnt make the cut