Questions & answers
Our tops are named differently from our partner's. Can we still correlate? Yes. Add both spellings to a lexicon (or use a national lexicon); wells correlate by unit and show one name.
Our database uses its own codes. Do we need a software change? No. A vocabulary file maps your codes; unmapped codes are reported so nothing is guessed.
We use a different barrier standard or revision.
Set barriers.acceptanceReferences (and, if needed, barriers.requiredBarriers) in your environment.
Can different assets use different settings? Yes. Each environment file is independent; a server can serve several customers at once, each with its own environment.
Why is a value not configurable? Physical constants and unit definitions are fixed so a configuration typo cannot change engineering results.
The software says a key is unknown.
It is probably misspelled; the message shows its full path (for example cement.goodBondIndx). The default stays in effect.
Are generated barrier sets final? No. They are templates marked planned; review elements, depths and statuses for each well.