Check whether HAZOP's empty cells are evaluated

Question

Dear medini users,

I would like to share a customization to help you distinguish whether empty cells in HAZOP (Guideword) analysis have been evaluated or not.

If you have evaluated a cell in the guideword analysis, and the result is none of malfunctions for it. You will keep the cell empty.

But medini doesn't have a native way to tell the difference between the evaluated blanks and unevaluated blank.

With this customization, you can select the guidewords which have been evaluated but the analysis result is keeping them empty. See the column `Reviewed guideword blanks` in the screenshot.

If any cells are empty but their guidewords are not selected in `Reviewed guideword blanks`, you will get a red bar in the row to remind you that you haven't evaluated some guidewords.

Validation rules (Dynamic constraints) are also provided.

Note that if you need trigger the script to update the color by pressing `F5` after you put malfuctions for guidewords.

medini_1056584416 · Answer

Thanks Ka-lip for sharing this, really interesting and useful.

I've refined your OCL validation rule for checking blank key cells, offering a bit more flexibility.

The original rule required the list of blank keys to be exactly equal to the list of reviewed keys to show a "green light."
This meant if a key was reviewed but no longer blank (e.g., a malfunction was created for it), the rule would flag it.

My updated rule takes a different approach: it checks that all currently blank keys are contained within the list of reviewed keys.

This means that if you create a malfunction for a specific key (so no blank anymore), but that key was previously reviewed (so still in reviewed list), it won't trigger a red light anymore (despite the fact the lists are different)
The rule recognizes it's still "fine" because it has been addressed or acknowledged.

This provides a valuable alternative to our existing rule, and I believe it offers a more nuanced validation, especially when keys transition from being blank to having associated malfunctions.
Both logic variations remain valid, and our customer can test whichever best suits their HAZOP approach.

OCL rule attached:

inv:
self.user_reviewed_blank->asSet()->includesAll(
 (self.mediniGetOpposites('entries').oclAsType(hazop::HazopAnalysisModel).guidewords->asSet()
 - self.guidewordToFailures.key->asSet()
 ).name->asSet()
)

I hope this can be of use to someone.

Michele

medini_1024169437 · Answer

Nice example from practice Ka-lip, Thanks for that.

Jan