Setting One of Multiple Safety Goals in DC Worksheet

Question

In an attempt to reduce friction and repetitive strain syndrome I would like to be able to programmatically change the "Safety related in this HW analysis" column when I have multiple safety goals.

The below script captures the safety goal from the first item selected, assumed to be chosen correctly by the user, and applies it to the remaining selected items. The script is doing what I'd expect it to.

Running medini in debug mode, I can see that selected items are having their safety goal updated, but the text in the "Safety related in this HW analysis" column is only updating if one and only one of the other safety goals are chosen prior to running the script. If the default of "all SGs" is in that column it will not update after the safety goal is selected.

In the image below the following can be seen:

RED ARROW: first item, containing the safety goal I want applied to all items in the image.

BLUE ARROW: this item had another safety goal (G024) originally applied and it updated when the script ran

ORANGE ARROW: this item was the default, i.e. both safety goals, when the script ran. The text in the column didn't change, but I can see through the debug mode that the element attributes were updated so the safety goal is G017 as desired. Component C158 is also exactly like this; it updated, but the column text did not.

I've tried refreshing as well as closing medini and restarting. Nothing is updating that column text.

Any insight you can provide would be appreciated.

//$EXPERIMENTAL$

// lets check the selection first 
if (!selection) { 
 throw "No or invalid selection!"; 
}

// select parts
if (selection && selection.length) {
	var componentEntries = Global.getFinder(selection).findByType(Metamodel.dc.DCComponentEntry); 
	if (componentEntries.isEmpty()) {
		console.error("No elements to proceed"); 
	} 
	console.log("Found {0} elements", componentEntries.size()); 
}

// get the safetyRelatedFor data from the first item
safetyGoalData = componentEntries.first().safetyRelatedFor;
desiredGoalName = componentEntries.first().safetyRelatedFor[0].identifier;
console.log("Safety Goal of ''{0}'' is {1}
Safety Goal Info: {2}", componentEntries.first().element.name, desiredGoalName, safetyGoalData);

componentEntries.forEach(function reportBlock(componentEntry) { 
	if (componentEntry != componentEntries.first()){
		console.log("Setting goal for ''{0}''", componentEntry.element.name);
		componentEntry.safetyRelatedFor = safetyGoalData;
	}
});

medini_1064792687 · Answer

Eckhardt,

Thanks for your quick reply.

Regarding your question on the number of SGs, the answer is 2. I agree that doing this by hand is easy enough when the component count is low.

But I have some sections that need this applied to ~300 components. The amount of mouse movement and clicking to do this becomes numbing, both mentally and physically. "Copy Analysis…" does not work in this case.

I understand the point of the friction is to ensure that users do not quickly introduce errors in their analysis. Maybe it would be better to derive a new DC Worksheet and split out the SGs for each instead of using the tool's feature of performing the analysis on 2 SGs in a single sheet.

And maybe I'm using the tool wrong and the amount of friction I'm seeing is because of that.

Todd

medini_1023909254 · Answer

Hi Todd,

* At the beginning a warning: Yes, all settings related to DC Worksheets are quite tricky and you need to carefully reviewed that your script is doing the right things (and the user is applying the script in the right way). This holds especially for scripts changing the DC sheet.  Copy&Paste using a script can easily introduce wrong classifications and significantly impact thus the complete metrics calculation!
* A little more details on the different attributes:
safetyRelated == true means that the component is safety related for all SG listed on the DC Sheet cover page
In case only a subset of the SG shall apply to the component you need to set safetyRelated to false and list all SG in safetyRelatedFor
* Note, there are is also a similar attribute which does handle potential variants in the DC sheet - applicableFor. In case you include variants, you will also need to handle this one correctly
* You may need also to check for ports and handle them correctly - the cover page does have a setting to hide ports - depending on this you need or need not set the SG for the ports.
* Also the setting for the analysis depth (all/leaves or fixed level) has an impact on the metrics calculation and needs to be handled correctly

BTW, how many SG to you handle with your DC sheet? Usually it would be a number below 10 (more 3-5) and (de)-selecting the right ones for a component manually should still bean acceptable effort - and would of course also document the brain work required for it.

Eckhardt

medini_1064792687 · Answer

I figure out what I was missing. I've added the code below between lines 24 and 25 from my original code snippet.

componentEntry.safetyRelated = false;

I needed to set this so that it didn't pick up the defaults. safetyRelated = false seems like incorrect, but I understand you're reusing a flag.

Todd