Plato E1ns3

PLATO e1ns 3.0 / SCIO™ 8.
0
New features
PLATO AG Contact Support

Maria-Goeppert-Straße 15 Telephone: +49(0) 451.930986-01
23562 Lübeck - Germany Email: support@plato.de
PLATO e1ns 3.0 / SCIO™ 8.0 1
Content
1 GENERAL INFORMATION ............................................................................................................. 4
1.1 Main features and functions of e1ns 3.0 and SCIO™ 8.0 ................................................................ 4
1.2 Important remarks prior to the installation .................................................................................. 5
1.2.1 Functional Safety, FMEDA, Hazard Analysis – available not until e1ns Version 3.1! ........................5
1.2.2 A new license is required – this applies for updates to e1ns version 2.4.21 ....................................5
1.2.3 A license is required – only applies to updates of SCIO™ version 6.0 or lower ................................5
1.2.4 Company-specific customizations, methods, and interfaces ...........................................................5
1.2.5 Implementation of suggestions for improvement............................................................................5
1.3 Discontinuing SCIO™ version 5.1 .................................................................................................. 5
2 AIAG VDA ALIGNMENT ................................................................................................................ 6

3 E1NS.ACTIONS ............................................................................................................................. 7
3.1 User administration – highlighting of inactive users ...................................................................... 7

3.2 e1ns.newsletter........................................................................................................................... 7
4 E1NS.ARCHITECT.......................................................................................................................... 8
4.1 Creating subsystem elements in the working area ........................................................................ 8

4.2 Selection list offers quick changes during function and failure analysis .......................................... 8
4.3 Focused failure analysis for subsystem elements [Ticket #2550].................................................... 9
4.4 Creating and displaying comments ............................................................................................... 9
4.5 Quick linking with all subelements, functions or failures ............................................................. 10
4.6 Monitoring and system response (MSR) ..................................................................................... 11
5 E1NS.ASPECTS ........................................................................................................................... 13
5.1 Turning connections into functions ............................................................................................ 13

5.2 Assigning aspects to the whole structure .................................................................................... 14
5.3 Blocks also show ASIL values of functions ................................................................................... 14
6 E1NS.FOUNDATION ................................................................................................................... 15
6.1 All master data is completely displayed [Ticket #2108] ............................................................... 15

6.2 Editing master data ................................................................................................................... 15
6.2.1 Editing FMEA specific data ..............................................................................................................15
6.2.2 Editing Control Plan specific data [Ticket #901] .............................................................................15
6.3 Inheriting master data fields version and revision to subsystem elements................................... 15
© PLATO AG 2019
6.4 Master data display extended by “Diagnostic information” ........................................................ 16

6.5 Options for searching in the schedule overview .......................................................................... 16
6.6 New buttons in the net view [Ticket #2750]................................................................................ 16
7 E1NS.METHODS ......................................................................................................................... 17
7.1 Multilingualism in form sheets ................................................................................................... 17

7.2 Attaching documents to cells in form sheets............................................................................... 19
7.2.1 Documents from SCIO™ are shown in e1ns form sheets................................................................19
7.3 New functions in the Process Configurator ................................................................................. 20

7.3.1 Integrating all process steps in one step into the process flow......................................................20
7.3.2 Creating system elements directly for machines and products .....................................................20
7.4 Filtering for origin of system element in form sheets .................................................................. 20

7.5 Functional Safety (ISO 26262) .................................................................................................... 20
7.5.1 Methodical enhancement – ASIL Decomposition...........................................................................21
7.5.2 Displaying the ASIL value in e1ns.aspects .......................................................................................21
7.5.3 Displaying ASIL values in e1ns.architect .........................................................................................21
7.5.4 Displaying ASIL values in failure and function nets ........................................................................22
7.6 Changing equal entries quickly in a column ................................................................................ 22

7.7 Extended functionality for tooltips on comments ....................................................................... 23
7.8 Trace overview displays the system element name [CR-17615] ................................................... 23
7.9 Filtering cells without background color ..................................................................................... 23
8 E1NS.PORTAL ............................................................................................................................ 24
8.1 Displaying recently opened elements ......................................................................................... 24

8.2 Indexing old data ....................................................................................................................... 24
9 E1NS.TEMPLATES....................................................................................................................... 25
9.1 Adding a prefix or suffix to a process from a template ................................................................ 25

9.2 New button <Complete statistics> .............................................................................................. 25
9.3 Publishing templates directly ..................................................................................................... 25
9.4 Audit Trail logs master data changes .......................................................................................... 25
9.5 Buttons for archiving and reopening not available anymore ....................................................... 26
9.6 New buttons in the dialog window for updating from a template ............................................... 26
10 SCIO™ ....................................................................................................................................... 27
10.1 Extended formatting of system element IDs ............................................................................... 27
© PLATO AG 2019
11 MISCELLANEOUS ....................................................................................................................... 28
11.1 Extended menu bar / New function............................................................................................ 28

11.2 New functions available in the user administration .................................................................... 28
11.2.1 Displaying the data base name .......................................................................................................28
11.2.2 Visual identification of the currently logged on user .....................................................................28
11.2.3 Importing user data ........................................................................................................................28
11.2.4 New basic right “User administration” ...........................................................................................34
11.2.5 Changing passwords with limited administration rights ................................................................35
11.3 Variant tree – creating and editing system element families ....................................................... 35
11.4 Search function for user selection available ................................................................................ 36
11.5 Copy and paste for all modules in the tree ................................................................................. 36
11.6 Java component was replaced ................................................................................................... 36
© PLATO AG 2019
1 General information
1.1 Main features and functions of e1ns 3.0 and SCIO™ 8.0
The emphasis in the new version lies on:
All modules AIAG VDA Alignment – two new form sheets are available
• DFMEA AIAG/VDA
• PFMEA AIAG/VDA
User administration
• Importing user data
• IMPORTANT! New basic right “User administration” must be assigned
• Visual identification of the currently logged on user
Miscellaneous
• Extended menu bar / new function “Recently edited elements”
• Variant tree – creating and editing system element families
e1ns.architect • Focused failure analysis for subsystem elements
• Quick linking with all subelements, functions or failures
• Monitoring and system response (MSR)
e1ns.aspects • Turning connections into functions
• Blocks also show ASIL values of functions
e1ns.foundation • All master data is completely displayed
• Editing FMEA and Control Plan specific data
e1ns.methods • Multilingualism in form sheets
• Attaching documents to cells in form sheets
• Integrating all process steps in one go into the process flow
• Filtering for origin of system element in form sheets
• Functional Safety: Methodical enhancement – ASIL Decomposition
e1ns.templates • Adding a prefix or suffix to a process from a template
• Audit Trail logs master data changes
SCIO™ • Extended formatting of system element IDs
© PLATO AG 2019
1.2 Important remarks prior to the installation
1.2.1 Functional Safety, FMEDA, Hazard Analysis – available not until e1ns Version 3.1!
Users who work with Functional Safety, FMEDA, and Hazard Analysis in e1ns.methods should NOT update
to e1ns version 3.0. These methods require a migration as the link of the ASIL value was changed in the
software. An automatic migration will be provided for e1ns version 3.1.
1.2.2 A new license is required – this applies for updates to e1ns version 2.4.21
When updating to e1ns version 2.4.21 obtaining a new license for e1ns.architect and the form sheets
Control Plan and Process Flow is necessary.
1.2.3 A license is required – only applies to updates of SCIO™ version 6.0 or lower
After the update (from SCIO™ version 6.0 or lower) to SCIO™ version 7.3, users will need to license the
following modules: e1ns.methods (SCIO™-Methods), e1ns.dashboard (SCIO™-Dashboard), and
e1ns.foundation (SCIO™-Portal). To license these modules, send your license file (PLV file) by email to
plato@plato.de.
You will then receive a license file for the update including the modules in return.
Information on updating and installing the software can be obtained from your PLATO representative or by
sending an email to info@plato.de.
1.2.4 Company-specific customizations, methods, and interfaces

Individual customer solutions (plugins) that come with a service contract will be provided on request.
Please issue your request to service-plugin@plato.de. For individual customer solutions (plugins) without
service contract we do not guarantee operability after an update.
Please note that it may not be possible to use interfaces to other applications any more that were
specifically developed for a company. They should be tested before each update.
1.2.5 Implementation of suggestions for improvement

The implementation of suggestions for improvement and solutions for problems sent to us in customer
reports are attributed with the message ID/Ticket # in the following list. The Customer Report is available
on the PLATO home page in the Support section (http://www.plato.de/customer-report-223.html).
1.3 Discontinuing SCIO™ version 5.1

Starting in 2012 PLATO has gradually developed the SCIO™ software version 5.1. However, only the
upgrade versions correspond to today’s requirements of technology, security, and functionality. Hence,
optimizations, updates, technical and application-technical support will not be provided anymore for
version 5.1 and all older SCIO™ versions as of January 2019. Users provided with a service contract will
obtain the update to the current SCIO™ version free of charge. We also recommend users of the versions
up to SCIO™ 6.5 to consider updating in order to benefit from its innovations.
© PLATO AG 2019
2 AIAG VDA Alignment

The new standard for FMEAs is released
As of recently, the new standard can be obtained through the AIAG in English and the VDA in German.
Take your time to familiarize with the new rules. The new standard does not require revising FMEAs in
progress or existing FMEAs. Moderators and auditors are not trained yet. Please keep in mind that time is
needed to prepare trainings in order to train users in the new methods.
For a first orientation PLATO already provides two new form sheets in e1ns.methods:
• DFMEA AIAG/VDA
• PFMEA AIAG/VDA
The structure analysis (higher level, focus element, lower level) is displayed in the head area. The form
sheet shows function and failure analysis, risk analysis, optimization and subsequently also the MSR
analysis.
In each case the focus element will be edited. Depending data from other levels will be displayed.
The form sheets will gradually be developed and the provision of further functional enhancements is
intended in the future. The concept of PLATO e1ns is based on plug in technology. This allows developing
updates for form sheets at any time and delivering them independent of software releases.
© PLATO AG 2019
3 e1ns.actions
3.1 User administration – highlighting of inactive users

If the Responsible person and the Manager have the status “inactive” this will be indicated by showing the
user name in orange italics in the e1ns.actions overview as well as in the dialogs of project, action, folder,
and milestone. In the overview and in the text completion fields the localized term “inactive” is added in
square brackets behind the user name. Tooltips are shown in the fields Responsible person and Manager
containing an explaining text for the field as well as a text with explanations for the display of inactive
users.
3.2 e1ns.newsletter
Next to the overdue FMEA actions the e1ns.newsletter now also displays the open FMEA actions whose due
date has not yet been reached. The mentioned categories list taken and recommended actions.
© PLATO AG 2019
4 e1ns.architect
4.1 Creating subsystem elements in the working area

A button in the working area allows adding subsystem elements to system elements in case no sub
elements have existed so far.
Procedure:
• Click on the turquoise colored field “Click here to create a system element”.
The following dialog box opens.
• Enter the name for the new system element and confirm with <OK>.
4.2 Selection list offers quick changes during function and failure analysis
When working with the filters Function analysis and Failure analysis, a selection list now allows jumping
from one function to another.
After performing a function or failure analysis, the selection list will be shown next to the icons above the
matrix. Pressing <Remove filter> removes the list.
Procedure:
• Choose a function in the table header.
• Choose Function analysis or Failure analysis in the context menu.
A selection list appears in the tool bar above the matrix. The list contains all functions shown in the
table header.
• Choose the function you want to jump to.

In the mode function analysis the corresponding function is shown in the table header.
In the mode failure analysis the function plus its failure(s) are shown in the table header.
• Remove the filter by pressing <Remove filter>.
© PLATO AG 2019
4.3 Focused failure analysis for subsystem elements [Ticket #2550]

For subsystem elements in the tree a focused failure analysis can be carried out. Focused are all functions
of the system element with the corresponding failures. In addition, a selection list allows jumping from one
system element to another one on the same level.
Procedure:
• Choose a subsystem element.
• Choose Failure analysis in the context menu.
All functions of the system element with the corresponding failures will be indicated as focused.
A selection list appears in the tool bar above the matrix (see figure). The list contains all system
elements that are on the same level as the selected system element.
• Choose a system element from the list to jump to it.

• Remove the filter by pressing <Remove filter>.
4.4 Creating and displaying comments

Comments can be added to functions, failures, and system elements with the command Add comment in the
context menu. Elements with comments are marked with a red triangle (analog to e1ns.methods). When the
mouse pointer hovers over the triangle, a tooltip shows the actual comment.
Tooltips on comments contain a scrollbar and a button <Edit comment> that allows jumping directly into
the dialog for editing the comment (also see Chapter 6.9).
© PLATO AG 2019
4.5 Quick linking with all subelements, functions or failures

Linking can now be carried out in one step when
• all subsystem elements are required for a function,
• all sub functions are required for a function, or
• all failures of the subsystem elements are causes of the failure.
This action can be carried out in the focus views Structure, Function and Failure with the command Link
with all functions / failures from the context menu.
The following paragraph describes how the procedure is carried out in the focus view Structure with a
function in the table header.
Procedure:
• Activate the focus view Structure.
• Choose a function in the table header.
• Choose Link with all functions / failures in the context menu.

A dialog box “Apply” opens.
• Confirm the action with the button <Yes>.
All boxes for functions and subsystem elements in this column are ticked. This also applies for
filtered and collapsed elements. When the subsystem elements do not yet have a function, only the
subsystem elements are linked (structure link). The net view in the lower screen area is updated.
Effects in the focus view Failure:

All boxes for failures in this column are ticked. This also applies to filtered and collapsed failures. When the
corresponding subsystem elements or functions are not linked yet, no links will be created there – only the
failure link is created.
If the section External causes contains system elements, these failures will not be linked as only few failure
causes arise from external elements.
© PLATO AG 2019
4.6 Monitoring and system response (MSR)

When using a product it is important that a user can detect and respond to problems during the use or
product defects, respectively. Or that the product reacts autonomously in case of a defect and, for
example, switches into an emergency mode. An MSR analysis considers these aspects.
Monitoring and system response extends a design FMEA by analyzing the effectivity of monitoring and
describing the appropriate system response. Potential failures that occur during customer operation and
their effects can be taken into account. The original effect can be mitigated or even prevented.
A new focus view <MSR> is now available for assigning functions for failure detection (monitoring) and
failure management (system response). This focus view is activated by default. For a connection between
function and failure the types (M)onitoring and (R)esponse are available.
The results of the MSR analysis will automatically be applied when using the form sheet FMEA MSR for
VDA/AIAG harmonization.
Procedure:
• Activate the focus view <MSR>.
The drop-down menus appear in the matrix.
• Choose a function in the tree that you want to link with a failure.
• Select (M)onitoring or (R)esponse in the corresponding drop-down menus.
In the example a control unit detects whether voltage is applied to the lighting or current flows to
power the lighting system of the bicycle in order to detect a lack of visibility during the night. If the
lighting fails the system will switch to the emergency battery. This ensures that the failure does not
occur and the driver is seen.
The failure net shows the MSR functions that disrupt the failure net and hence block the occurrence of the
undesirable failure effects.
© PLATO AG 2019
The display in the form sheet AIAG/VDA D-FMEA looks as follows:
The blocking function (system response) is indicated with the addition “Blocked by:” underneath the
failure.
Into the new form sheet AIAG/VDA D-FMEA percentage values for the probable coverage of monitoring and
system response can be entered (see also figure “Failure net”). BC stands for „Best coverage“ (Monitoring)
and BE for „Best effectiveness“ (Response).
© PLATO AG 2019
5 e1ns.aspects
5.1 Turning connections into functions

Connections between aspects can now be created as functions for system elements. The blocks, however,
must be part of the BOM (Bill of Material) for the menu item Create function from connection to be
activated.
The name of the newly created function is put together as follows:
Port type – Name of the connection – Direction (Input / Output) – Name of the system element
Procedure:
• Select a connection.
• Choose Create function from connection in the context menu.
For the system element that is left by the connection (Charger), the following function is created:
ELECTRICAL – VOLTAGE (5 V) - OUTPUT – BATTERY
For the system element to which the connection points (Battery), the following function is created:
ELECTRICAL – VOLTAGE (5 V) – INPUT – CHARGER
In addition, messages are shown in the lower right display area.
• Open a form sheet.

The functions are listed at the end of the column “Function” with the generated name.
Deleting functions in system elements does not affect the display in e1ns.aspects. The connections
will remain in it.
When creating a bidirectional connection, the functions input and output are both created underneath the
every system element.
If a function name already exists, no function will be created. A corresponding error message will be shown
in the lower right display area.
By means of the PLATO plug in technology the default behavior for Create function from connection can be
adapted to specific customer needs. Please approach your PLATO contact person.
© PLATO AG 2019
5.2 Assigning aspects to the whole structure

A new aspect can now be assigned to system element structures with many subsystem elements.
Procedure:
• Select a system element in the tree.
• Open the context menu on an aspect in the header.
• Choose the command Manage aspect….
• With the button <Select all> you tick all system elements in the tree of the dialog which the aspect
should be assigned to.
5.3 Blocks also show ASIL values of functions

The maximum ASIL value of functions of a system element (if available) is now displayed in the upper right
corner of a block. The value also appears in brackets behind the function name in the pop-up menu (see
figure).
© PLATO AG 2019
6 e1ns.foundation
6.1 All master data is completely displayed [Ticket #2108]

The master data dialog now shows all master data in the sections Mandatory data, Additional information,
FMEA specific data, Control-Plan specific data and Review. In e1ns Optional master data and Open points
are implemented with configured master data dialogs. The section Template information is displayed
whenever the system element was imported from a template data base.
6.2 Editing master data

Master data catalogs can now also be used in e1ns with the exception of the master date “Product”. Here
the catalog selection will be provided with one of the following versions.
6.2.1 Editing FMEA specific data

You can edit the following FMEA master data:
• Key date
• Department responsible for FMEA
• Employee responsible for FMEA
• Departments affected by FMEA
• FMEA team
6.2.2 Editing Control Plan specific data [Ticket #901]

You can edit the following master data of the Control Plan:
• Status
• Employee responsible for CP
• Department responsible for CP
• Departments affected by CP
6.3 Inheriting master data fields version and revision to subsystem elements
In the section Additional information the master data fields “Version” and “Revision” can now also be
inherited to subsystem elements.
© PLATO AG 2019
6.4 Master data display extended by “Diagnostic information”

The master data dialog now shows a section Diagnostic information that could be of importance in service
cases. This section shows the following field:
• GUID: “Globally Unique Identifier” is an internal identification number of the currently chosen
system element.
If a system element was created from a template, two additional fields will be shown:
• Template GUID: Identification number of the top system element of a template.
• External template GUID: Identification number of the respective system element in the template.
6.5 Options for searching in the schedule overview

In e1ns.foundation and e1ns.actions the user is now provided with a drop-down menu to allow searching in
the schedule overview. The menu is placed next to the filter for actions.
In the drop-down menu the user can choose between the following two options:
• Starting with: Shows in the hit list the search hits that begin with the search term.
• Arbitrary position: Shows search hits where the search term occurs somewhere in the hit list
6.6 New buttons in the net view [Ticket #2750]

The net view now contains the following new buttons:
• <Save net as file (SVG)…>: The net view will be saved as SVG file (SVG - Scalable Vector Graphics).
The file can be displayed by the supported browsers and is arbitrarily scalable.
• <Print net…>: The net view can be printed. In the print settings the desired scale or paper size may
have to be set.
© PLATO AG 2019
7 e1ns.methods
7.1 Multilingualism in form sheets

This new functionality is provided in a first stage and will continuously be extended with future versions.
Currently, a basic functionality is available. You have the possibility to try the following use cases:
• A form sheet already contains reference language entries that ought to be translated into a foreign
language.
• Reference language entries ought to be revised in and / or added to an already filled form sheet. For
each single cell an entry will then be entered in the reference language and also for the translation.
The following use cases will not be supported:
• The definition of specifications (Editor in a separate window).

• The entry in columns for numbers, severity numbers, date, persons, status, and class. These data can
be entered and edited in the reference language view.
With a new symbol in the e1ns menu bar, form sheets can be switched into a mode for editing entries in a
particular language. The individual translations can directly be entered underneath the reference entry in
form sheet cells. The client decides on a language which should be reference language (e. g. “English” as
corporate language).
Methodology:
Every data base object is represented by an entry in the so-called reference language. This is the
connection between the translations and the unique data object.
Setting languages:
The language setting allows creating arbitrary languages (only available in SCIO™-Client). They need to
consist of a unique language abbreviation and a description (e. g. “en” / “English”). Use the international
abbreviations for languages.
Selecting the language view:

The symbol in the PLATO e1ns menu bar that allows switching into the language editing mode is only
visible in e1ns.methods.
Clicking on the symbol or the language abbreviation opens a drop-down menu for selecting the language:
© PLATO AG 2019
The following two views can be chosen:

• Only reference language: Displaying the form sheet and working in it have not changed. The only
difference is that the user changes into the mode “Reference language”. No language abbreviation is
shown next to the symbol.
• Reference language with translation: Other languages additional to the reference language can be
entered or edited. The symbol is accompanied by the language abbreviation of the currently chosen
language.
Language view:
The language view always shows the reference language and one additional chosen language. The
translation is directly displayed underneath the reference language entry in the same cell.
In the language view a form sheet can only be edited in a separate “translation pane”. The cells of the form
sheet are write-protected. However, navigating in the form sheet is still possible.
New cells can be added with Add new (or CTRL + ENTER) from the context menu. Text input takes place in
the translation pane.
Cells can be deleted in the language view with Delete entry (or DELETE) from the context menu.
Translation pane:
The translation pane always shows the content of the chosen cell separated into reference language and
translation.
Theoretically the user can edit both entries (not recommended). We recommend carrying out a translation
only, if an entry already exists in the reference language.
When entering a translation while no reference language entry exists the translation will be used as reference
language entry. The abbreviation of the language selected is displayed in front of the entry in brackets.
When working in the lower part of the language window the system proposes translation suggestions (if
available).
NOTES!
The user is responsible for conciliating reference language and translation in cases of purely textual
adaptations (e. g. grammatical errors) and content changes. If a reference entry is changed, the previous
translations will be discarded!
The translation feature does not support the Control Plan yet. It will be provided with a following version!
An output with e1ns.output will be provided with a following version!
© PLATO AG 2019
7.2 Attaching documents to cells in form sheets

Detailed information, images, drawings, or further documents can be linked with method form sheets.
According to the configuration of a form sheet, every cell can be linked to documents. e1ns.documents
must be installed to use the function as this application serves for storing, versioning and deleting
documents.
With the command Attach document… in the context menu documents can be attached to cells in form
sheets. Nothing can be attached to an empty cell.
Attachments can be made to the following cells:
• System elements
• Function
• Failure
• Cause
• Deadline action bundle
• Recommended action
Existing attachments are displayed with a clip icon. A tooltip at the clip lists all attachments.
Clicking on the download icon in front of the name of an attachment opens the file. A dialog box offers
options to save or to open the file. Clicking on the file name opens e1ns.documents on a new page.
Editing and versioning documents in e1ns.documents

Attached documents can be edited and versioned in e1ns.documents. Older versions are also displayed in
the form sheet and can be expanded with the plus icon.
e1ns.documents e1ns.methods
Documents can only be deleted in e1ns.documents. The view Metadata was amended by the entry “Origin”.
This entry provides information on where the document linkage was created (e. g. in e1ns.methods).
When deleting a cell with a document attachment in a form sheet, the documents will be moved to
Lost & Found with a time delay. In this part of the system administration they can be reassigned, if
necessary, or finally be deleted. After four weeks elements in Lost & Found will be deleted automatically.
7.2.1 Documents from SCIO™ are shown in e1ns form sheets

From SCIO™ only locally attached documents are shown. They are marked with a label [external].
Documents can only be changed or deleted with SCIO™. If the system cannot access a file path as, for
example, the document has been deleted N/A will be shown instead of the file size.
© PLATO AG 2019
7.3 New functions in the Process Configurator
7.3.1 Integrating all process steps in one step into the process flow
With the command Add all functions /system elements as process elements in the context menu for the
folders Functions and Process step characteristics for SE all process steps (functions / system elements) will
be integrated into the process in one step. If single process steps have already been chosen, these will not
be integrated again but only the missing steps will be amended.
7.3.2 Creating system elements directly for machines and products

With the command Create system element in the context menu for the folders Machines and machine
characteristics and Product characteristics now new system elements of the type “Product” and “Machine”
can directly be created in the tree of the matrix area. These system elements will then be displayed in the
particular depot as they have no structural linkage.
System elements that have been created underneath a top system element under Machines and machine
characteristics and Product characteristics are directly placed underneath the corresponding project in the
directory tree.
7.4 Filtering for origin of system element in form sheets

In an FMEA, causes from different system elements lead to system failures. By filtering by origin the
analysis focus can be set to individual elements. This applies to all form sheets that display information
about the origin. In FMEA form sheets these are the columns Effect and Cause.
The setting “No origin” only displays entries that were directly entered in the FMEA form sheet. They do
not originate from subelements.
Procedure:
• Click on the filter symbol in the table header.
• Choose the command SE origin filter… in the context menu.
A dialog box opens that shows all origins.
• Set one or more checkmarks in front of the origins that you want to filter the system elements for.
The form sheet only displays the causes whose origin was chosen in the filter.
7.5 Functional Safety (ISO 26262)

The method for Functional Safety was extended and an additional form sheet for an ASIL decomposition
was added.
Detailed information on Functional Safety can be obtained from your PLATO representative or by sending
an email to info@plato.de .
© PLATO AG 2019
7.5.1 Methodical enhancement – ASIL Decomposition

The method for Functional Safety now contains the following method form sheets:
• Item Definition
• Hazard Analysis
• ASIL Decomposition
• FMEDA (26262)
The new form sheet for an ASIL decomposition is used for a method to reduce the original ASIL
classification of a component. This method can be carried out when the component requirements can be
spread among several independent components. The decomposition rules of ISO 26262 are applied.
7.5.2 Displaying the ASIL value in e1ns.aspects

A diagram will show the maximum ASIL value in the upper right corner and, in addition, the corresponding
rule if a decomposition was carried out.
The maximum ASIL value of functions of a system element is displayed in the upper right corner of a block.
The value also appears in brackets behind the function name in the pop-up menu.
7.5.3 Displaying ASIL values in e1ns.architect

The ASIL value can be displayed for functions. It requires changing the filtering for the ID or number line
underneath the functions to ASIL.
© PLATO AG 2019
7.5.4 Displaying ASIL values in failure and function nets

The net display of functions also shows the ASIL value and safety functions highlighted in pink.
7.6 Changing equal entries quickly in a column

This function is used to revise or modify many entries in a column. Initially, the terms are filtered in order to
give the user an overview of the occurrence of terms and the consequences of the modification. Afterwards
the term can be replaced in all occurrences by another entry with the new menu item Mass update….
Initially, the user needs to set any column filter. This activates the menu item “Mass update...” which can
then be used for every column with editable cells. Empty form sheet cells can also be replaced.
Procedure:
• Click on the filter symbol in the column for which you want to carry out a mass update.
• Choose the menu item Mass update… in the context menu.
The following dialog box opens. The column name is displayed in brackets.
The selection list contains all filtered entries of the particular column. The number of occurrences of
the cells to be replaced is displayed in a circle.
• Select the elements you wish to replace.
This can happen manually by clicking on the particular box. A checkmark will be added or removed.
With the buttons <Select all> and <Deselect all> either all boxes will be ticked or all checkmarks will
be removed.
© PLATO AG 2019
• Enter a text in the field “Replace with”.
• Confirm your changes with the button <Apply>.

The replacement “Use standard filter” is executed for “[No entry]” in the particular column in the
form sheets.
7.7 Extended functionality for tooltips on comments

Tooltips on comments now contain a scrollbar and a button <Edit comment> that allows jumping directly
into the dialog for editing the comment.
7.8 Trace overview displays the system element name [CR-17615]

The name of the particular system element is now displayed in square brackets behind the linked entries.
7.9 Filtering cells without background color

Form sheets allow filtering for cells without background color with the menu item Color filter….
© PLATO AG 2019
8 e1ns.portal
8.1 Displaying recently opened elements

A list provides recently edited or opened elements, documents, tasks etc. When clicking on the associated
symbol on the e1ns.portal start page, a dialog window with an overview of the recently used e1ns elements
opens (also see Extended menu bar / New function).
8.2 Indexing old data

In order to facilitate changing from SCIO™ to e1ns, a new function provides the indexation of old data. You
will find a detailed description in the installation manual.
Preparation:
• Open the APPPLICATION.INI file of e1ns.
• Add the entry defaultWorksheetList in the section [Index].
• In e1ns follow the path System administration/Tab “Diagnosis”/Section “License info”. Under #
Worksheet ID you will find the form sheet IDs next to the numbering – e. g. “process_configurator”,
“process_flow”.
• Enter the form sheet IDs that ought to be indexed.
• Save the modifications.
• Start all e1ns services again by means of the Configurator.
Indexing profiles in e1ns:

• Follow the path System administration/Tab “Events”/Section “Indexer”.
• Index initially every incomplete profile with the button <Rebuild index>.
On the page <<Document list>> the system element and the form sheets that were added to the
APPPLICATION.INI for the system element are indexed.
When adapting the master data for a system element the entered form sheets will also be updated.
© PLATO AG 2019
9 e1ns.templates
9.1 Adding a prefix or suffix to a process from a template

When importing new processes from a template using the command Create process, the names of the
processes can now be extended by prefix, suffix, or timestamp. The name of the imported process will be
modified automatically, if a process with the same name already exists.
The type of extension can be chosen from a drop-down list on the page for the import (see figure) in the
working data base.
Also if processes are newly created from templates the names can be supplied with a prefix or suffix using
the command Revise process.
9.2 New button <Complete statistics>

A new button <Complete statistics> on the tab <<Overview>> in the Template Manager is available in
addition to the already existing button <<Rebuild statistics>. The buttons are only available for
Administrators [1].
This function allows rebuilding statistics without deleting previously created instances before. A click on the
button starts a process per template utilization in the process overview. Existing statistics of a template will
not be discarded and only created if they do not yet exist. This action does not affect already made
decisions in the template.
9.3 Publishing templates directly

In the Template Manager the button <Publish directly> is only provided for users with administrator rights
[ID 1]. This command releases the selected template immediately without requiring it to go through the
approval process of any of the approvers. Publishing templates directly should only be allowed in special
cases as it would circumvent an orderly approval process.
9.4 Audit Trail logs master data changes

The Audit Trail now logs master data changes for a system element. For obtaining information on content
changes a jump function allows switching directly to the master data form sheet. In a future version, details
of changes will also be displayed in the Audit Trail.
© PLATO AG 2019
9.5 Buttons for archiving and reopening not available anymore

The manual archiving of templates has been omitted. Whenever a new version of a template is created, the
previous version is automatically stored in the archive. The button <Revoke> was removed.
Reopening older template versions from the archive is no longer supported as the update functionality
requires consistent version numbering. The button <Reopen> was removed.
9.6 New buttons in the dialog window for updating from a template
The appearance of buttons in the dialog window for updating from a template was changed. When
hovering over the symbols, tooltips appear describing the function of the button.
Symbol Tooltip
Accept remaining changes
Reject remaining changes
Reset all changes
Form sheet
Split
Audit trail
© PLATO AG 2019
10 SCIO™
10.1 Extended formatting of system element IDs

An extended KeyID.ini offers changing the formatting of system element IDs. If requested the ID can also
be composed of the abbreviation of the system element type and a freely definable contiguous value. This
positive integer value increments with every newly created system element.
The KeyID.ini can be found in the INI directory of the particular SCIO™ data base or can be created in this
directory.
The configuration of the system element IDs also applies to e1ns.
For system element types the following abbreviations are available:

• D - Design
• P - Process
• I - Interface
• S - Software
• R - Requirement
• M – Machine
Note!
Creating a system element ID with the new format works in the SCIO™-Client only when using the
simplified dialog “Create System Element” without opening the complete master data dialog with the link
“Additional master data…”.
© PLATO AG 2019
11 Miscellaneous
11.1 Extended menu bar / New function

The upper e1ns menu bar was amended by a new symbol whose functionality can be called from every
application.
Clock
A list provides recently edited or opened elements, documents, tasks etc. When clicking on the
symbol, a dialog window with an overview of the recently used e1ns elements opens.
The list displays 10 elements at the maximum, sorted by date.
The newest entry always appears at the first position. Older entries are classified into the
categories Yesterday, Last week, or Older.
11.2 New functions available in the user administration
11.2.1 Displaying the data base name

A tooltip when hovering over User administration in the header shows the name of the user and also the
name of the data base profile.
11.2.2 Visual identification of the currently logged on user

In order to facilitate identification of the currently logged on user in the user administration, in the
overview the name as well as the attached data in the user table are now marked in bold.
11.2.3 Importing user data

The user administration now allows importing new users as well as updating or deactivating already
existing users. Before the eventual import takes place, the expected import results will only be displayed. In
a verification step the user can see what the expected result will look like and either decide not to carry out
the import or edit the import data again.
Only a user with administrator rights [1] can carry out the import.
Procedure and preparations:

Take notice of the following points before starting the import!
• Allowed import formats: CSV (semicolon [;] as separator) and Excel (.xlsx)
© PLATO AG 2019
• Notes on import templates: A CSV or Excel import template can be chosen in the selection menu
Options/Downloads. The files already contain the column headings and two exemplary users. The
password column is not included and needs to be added, if necessary.
• Expected characters / character encoding: The input data is expected to be encoded in UTF-8. It
means that “everything” can be entered but must be delivered to the import with the corresponding
character encoding.
An Excel import file is expected to have the workbook format. The name of the workbook has to
contain the name “e1ns-User-Import”. A prefix or suffix can be appended to the name (e. g. a date).
• Column names: The column names are predefined and must not be changed.
• Status values: The status values Inactive, Active, Invisible, and System are predefined. NOTE: Users
with the status “System” are currently skipped and will not be processed during an import.
• Required and optional column names, respectively:
Column names Required Optional
User name ✓
First name ✓
Last name ✓
Telephone ✓
Email ✓
External ID ✓
SSO ID ✓
Department ✓
Status ✓
Rights classes ✓
Password ✓ (when SSO is not used)
• Notes on optional fields: In order to prevent updating and overwriting of existing user data in
optional fields, the fields’ values can be defined to exclusively contain an asterisk symbol [*].
• Note on enumerating rights classes: Enumerations of rights classes in the field “Rights classes” must
be separated by a comma [,].
• Note on the column “User name”: The column “User name” must always be completed with a
unique name.
• Determination of key fields: Depending on the configuration made in the Application.ini, one of the
fields “User name”, “External ID” or “SSO ID” will be used as key field during the import. This
determination allows to uniquely identify existing users during the import process and to determine
whether the import data contains new users or users that ought to be updated.
Detailed information on configuration can be obtained from your PLATO contact person.
© PLATO AG 2019
Procedure when exporting:
• Choose the menu item Export in the selection menu Options.

Already existing user data can be exported in the formats Comma Separated Values (*.csv) or
Excel (*.xlsx).
Procedure when importing:
The import process consists of the successive steps Upload, Verify and Import.
Step Upload:
• Choose the menu item Import in the selection menu Options.
• Drag & Drop the import file in the field “Drag & Drop or click to select file” or click on the symbol
to choose the file from the directory.
• Choose the following import options before uploading the file:
o Add new departments
New departments will be created when the import data contains users with department names
that do not exist in the data base yet.
A new department will be assigned to users for whom the department was entered as value.
o Add new rights classes
New rights classes will be added when the import data contains users with rights classes that
have not existed in the data base so far.
© PLATO AG 2019
A new (empty) rights class will be assigned to users for whom this rights class was entered as
value. Several rights classes can be assigned to each user.
o Add new users
A new user will be added in case no already existing user can be identified by means of the
determined key field.
o Update existing users
An existing user will only be updated if he or she can uniquely be identified by means of the
determined key field.
o Deactivate not-included users
Already existing users will be deactivated when they are not included in the import data. The
status of these users will be set to “inactive”.
o Hide data where import activity is “ignore”
This option causes users that will not be changed by the import to not initially be shown in the
steps “Verify” and “Import” of the result table. It concerns existing users that are actually
available in the import data. As for these users, however, no difference could be identified they
will be ignored.
• Upload the file with the button <Update file>.
When changing to the step “Verify” the import data is extracted from the import file. In doing so it is
checked for certain format specifications (e. g. whether the field status has a valid value, etc.).
If the process identifies errors, they are reported to the user for correction.
If no errors are identified, the import data will be aligned with the existing data set. In the step
“Verify” the result is initially only displayed to the user.
Step Verify:
• Verify the results.

The existing data set has not been changed in the step “Verify”. The user gets an overview of the
forthcoming import activities for verification.
The overview opens with the arrow symbol in front of Check the data to be imported. It shows the
kind (e. g. user, rights classes, etc.) and overall count of data records. And it gives an overview
whether data records were created, updated, or ignored, for example (see figure).
o Create
Data (departments, users, rights classes) marked blue will be created.
o Update
Users marked green will be updated.
o Ignore
Users marked grey will be ignored. No differences to existing users could be determined. Users
that will be ignored are hidden in the overview table by default. With the display filter Ignore
hiding them can be deactivated.
© PLATO AG 2019
New values will be indicated with the symbol . In the example above the users Crown and Bell
would be created with new values. For the user Schmidt the values for the fields first name, last
name, department, and rights class would be amended. When hovering over the symbol, a
tooltip would show the old value, if there used to be one.
o Skip
Data (department, user, rights class) marked red will be skipped.
In the example the user Schmidt would be skipped because the required field “User name” is not
filled out. An explanatory text is indicated with the symbol .
© PLATO AG 2019
In the example the user Schmidt would still be skipped although the field user name is now filled
out. This happens because the import option Update existing users was not ticked.
In this case the explanatory text is indicated with the symbol .
o Deactivate
Users marked orange will be deactivated.
In the example all users from an already existing list that are not part of the import file would be
deactivated (from status active to inactive)! Presupposed, the import option Deactivate non-
included users is ticked.
Changing to the step “Import” is only possible when data can be updated, created, or deactivated.
• With the button <Back> the user always gets back from the step “Verify” to the dialog Import
options, for example, in order to modify the options.
Should changes in the import file be necessary the currently uploaded file can be removed with
and the modified document can then be uploaded again.
© PLATO AG 2019
Step Import:
• Carry out the import with the button <Import…>.

In the step “Import” import data will be processed and the existing data set be changed. The
duration of the import process depends on the quantity of import data to be processed. As long as
the import is in progress, the browser must not be closed.
• Close the dialog with the button <Close> after a successful import.
New or updated data is directly available in the overview and the user table.
Specifics when importing:

• Treatment of passwords and users with the status “Active”, respectively: When import data does
not contain passwords (e. g. no password column available) and Single Sign-on (SSO) is used, a
password is generated when a user is created, regardless of the user status.
When no SSO (not to be confused with SSO ID) is used, a password column has to be used for the
import data.
• Treatment of users with administrator rights [1]: Existing users with administrator rights [1] will not
be changed by an import process.
• Treatment of users with the status “System”: New or existing users with the status “System” will not
be created or changed by the import process.
11.2.4 New basic right “User administration”

All users that have worked or need to work with the user administration must be provided with the new
basic right User administration [128] unless they already have Administrator rights [1].
Calling and using the user administration is possible for the following combinations:
1. The user is an administrator [1]
OR
2. The user is provided with the new basic right User administration [128]
AND
at least, with one of the previously required basic rights that allow limited use (Create new and edit
user [10], Delete user [12], Assign right classes [34], Departments [36], Configure log in [41]).
© PLATO AG 2019
11.2.5 Changing passwords with limited administration rights

Users with limited administration rights can only create the password for another user when the other user
has not had a password so far. A password does not yet exist when the password creation date in the dialog
Edit user is missing.
The dialog can be opened with the symbol in the user table.
A new password can only be created for another user if

• a new user is directly created with the status “active”,
• an existing user does not yet have a password because he or she was created with the status
“inactive”.
Users with limited administration rights can change their own password. However, the current password
also has to be entered.
11.3 Variant tree – creating and editing system element families

The variant tree allows to display all components belonging to a product or all manufacturing steps and
machines belonging to a process in full in a well-organized structure. System element families can now also
be created and edited in e1ns with the command New / SE family in the context menu. So far this could
only be carried out in SCIO™. Each variant in the tree is assigned an SE family and an SE family ID so it can
be uniquely identified.
SE families and the corresponding SE family ID and projects can be edited with Rename in the context
menu or by pressing F2. Two editing windows open – one for editing the title and one for changing the ID.
Variants can be deleted with the command Delete… in the context menu.
The following menu entries were added to the context menu:

• Copy (CTRL + C): Copies an element. With the command Paste in the context menu the element is
pasted at the currently selected place again. The extension “Copy” and a number in brackets (starting
with 1) is automatically appended to the SE family name. System elements can only be copied and
pasted within a family. A number is automatically appended to the system element name of the
copy, starting with "_1".
• Cut (CTRL + X): Cuts an element. With the command Paste in the context menu the element is pasted
at the currently selected place again.
• Paste (CTRL + V): Pastes a copied or cut element.
• Paste link (CTRL + SHIFT + V): Links SE families. The element has to be copied first and can then be
linked at the appropriate place with the command Paste link. Links to system elements and projects
cannot be carried out.
© PLATO AG 2019
11.4 Search function for user selection available

The following modules are now provided with a search function for the user selection:
• e1ns.actions: Projects/All – for the fields “Responsible person”, “Team” and “Manager”
• e1ns.documents: Meta data – for the field “Additional editors”
• e1ns.foundation: Master data – for all fields in which users are available for selection
• e1ns.methods: Column “Responsible person”
NOTE: Depending on the form sheet definition, the selection lists only active users. If an already
saved user status changes in the meantime from "active" to "inactive", the name will be added at the
beginning of the hit list. However, no further information will be displayed for this user.
The selection shows maximum 5 hits. The sorting of the results is as follows:
• by status of the user (first active, then inactive),
• by user name (alphabetic order),
• and by all further configured fields (alphabetic order).
The additional fields initially have to be configured in the application.ini. You will find the description
in the e1ns user manual.
11.5 Copy and paste for all modules in the tree

Copy and paste in the tree is now available for all modules as it has already been for e1ns.actions. Elements
in the tree can be copied and pasted using the context menu on the particular system element.
11.6 Java component was replaced

Until now, the PLATO Software has used the Java component of Oracle for internal processes. This
component was recently replaced to avoid license fees for Java in the long-term run. Java was replaced by
the component OpenJDK 11.
© PLATO AG 2019

Plato E1ns3

Uploaded by

Copyright:

Available Formats

You might also like

Plato E1ns3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Plato E1ns3

Uploaded by

Copyright:

Available Formats

PLATO e1ns 3.0 / SCIO™ 8.

PLATO AG Contact Support

1 GENERAL INFORMATION ............................................................................................................. 4

1.3 Discontinuing SCIO™ version 5.1 .................................................................................................. 5

2 AIAG VDA ALIGNMENT ................................................................................................................ 6

3.1 User administration – highlighting of inactive users ...................................................................... 7

4.1 Creating subsystem elements in the working area ........................................................................ 8

5.1 Turning connections into functions ............................................................................................ 13

6.1 All master data is completely displayed [Ticket #2108] ............................................................... 15

6.4 Master data display extended by “Diagnostic information” ........................................................ 16

7.1 Multilingualism in form sheets ................................................................................................... 17

7.3 New functions in the Process Configurator ................................................................................. 20

7.4 Filtering for origin of system element in form sheets .................................................................. 20

7.6 Changing equal entries quickly in a column ................................................................................ 22

8.1 Displaying recently opened elements ......................................................................................... 24

9.1 Adding a prefix or suffix to a process from a template ................................................................ 25

10.1 Extended formatting of system element IDs ............................................................................... 27

11.1 Extended menu bar / New function............................................................................................ 28

1.2 Important remarks prior to the installation

1.2.4 Company-specific customizations, methods, and interfaces

1.2.5 Implementation of suggestions for improvement

1.3 Discontinuing SCIO™ version 5.1

2 AIAG VDA Alignment

3.1 User administration – highlighting of inactive users

4.1 Creating subsystem elements in the working area

The following dialog box opens.

• Choose the function you want to jump to.

4.3 Focused failure analysis for subsystem elements [Ticket #2550]

• Choose a system element from the list to jump to it.

4.4 Creating and displaying comments

4.5 Quick linking with all subelements, functions or failures

• all failures of the subsystem elements are causes of the failure.

• Choose Link with all functions / failures in the context menu.

Effects in the focus view Failure:

4.6 Monitoring and system response (MSR)

The display in the form sheet AIAG/VDA D-FMEA looks as follows:

5.1 Turning connections into functions

• Open a form sheet.

5.2 Assigning aspects to the whole structure

5.3 Blocks also show ASIL values of functions

6.1 All master data is completely displayed [Ticket #2108]

6.2 Editing master data

6.2.1 Editing FMEA specific data

6.2.2 Editing Control Plan specific data [Ticket #901]

6.4 Master data display extended by “Diagnostic information”

6.5 Options for searching in the schedule overview

6.6 New buttons in the net view [Ticket #2750]

7.1 Multilingualism in form sheets

The following use cases will not be supported:

• The definition of specifications (Editor in a separate window).

Selecting the language view:

The following two views can be chosen:

7.2 Attaching documents to cells in form sheets

Editing and versioning documents in e1ns.documents

7.2.1 Documents from SCIO™ are shown in e1ns form sheets

7.3 New functions in the Process Configurator

7.3.2 Creating system elements directly for machines and products

7.4 Filtering for origin of system element in form sheets