Summary of user interviews

We summarized the feedback of the user interviews for TypeDesigner and AutoDoc. The statements are based from our notes during the interview.

Statements with a number behind were mentioned more than once. Statements without a number behind were mentioned only once.

TypeDesigner

Some things wasn't clear enough without explanation (Types, Types References, Path). (3)
Fear that it can get to messy with a lot of elements in the column and to scroll a lot. (2)

Unsure, when the plugin is needed in the engineering process. (2)
Use cases of usage of types are unclear.
Plugin would be rather not used.
Plugin would be more for experts, which understand IEC 61850.
Plugin could be to generic that it would be used. It must be clear what to specify.
Curious to give it a try.

...mechanism to identify or find types again. (2)
... to search types in each columns. (2)
...a visual identification to identify that the types, are the same element in the different column.
...to sort Substation, Voltage Level and Bay in one section and IED, LD, and LN in another section.
...layout of columns and blocks should be responsiv and compact.
...to change button label of "add" button. (2)
...mechanism to see in both ways what happens when a type is changed and where it is used. (2)
...to lock types when they are "ready" and should be not changeable anymore.
...more visual design like single line diagram designer. (2)

What Details can be seen from LNs? Can the details of LNs also be edited?
Do we want to do that on functional level OR use bay and function separate?
It is possible to group by "function", a group of logical nodes?
Can you set additional attributes? IEDs have a lot of attributes.
How do you manage versions of types? (2)
How would a user know when a type is used/instantiated?
Will you use the 90-30?
IEDs and Bays don't have a Child/Parent connection. Instead, IEDs are referenced. How to handle that?

Could help as a transition solution to digitalization.
Substation area, many people still want paper on site (especially in DE).
There is need to generate documentation as a backup.
Interested in using AutoDoc.
Digital documentation is more useful.
The SCD file itself would be digital documentation. PDF/Print is not needed. (2)

...add column like "author" and "target audience".
...a static preview to see whats in side of a template.
...header and footer definitions to display something on every page.
...personal templates, that not everyone can edit. Different templates for different user groups.
...rename button from "Export" to "Generate".
...functionality to add a variable inside a heading/text element to reference data from the project.
...would be good to be as flexible as possible in the creation of a template.
...rename Button from "add element" to "add content".