e1ns.aspectsWork Using a Shared System Representation.

With e1ns.aspects, developers use a visual representation to design a system / product. The intuitive and systematic approach of e1ns.aspects automatically builds the system structure, which is then used as a basis for all further activities in the product development process (PDP).

Different areas can work on a common system representation and extend the system model by adding various aspects. This means the functional, mechanical, electrical, or electronic behavior of the system, for example, are described at a central location that is accessible to everyone.

Transparent development processes, a common understanding of the system, and good cooperation in a network form the basis for fast and economical product development.

  • Different areas work on a common system representation.
  • Up-to-date data is always available.
  • Repeated tasks are avoided, and maintenance is minimized.
Why e1ns.aspects? Your benefits.
Easy to use
  • Simple, intuitive, and in the web browser.
  • The graphic interface displays all elements of a system.
  • Elements are created to build a system or existing elements are simply dragged into the interface and dropped at the desired location.
  • A system can be divided into any number of levels (additional worksheets).
  • Elements are connected if they depend on or have a mutual influence on each other.
  • A connection between elements can have properties (force, signal, ...).
  • Photos and images for the elements are displayed directly.
Aspect-oriented engineering
  • Any view of a system / element can be created to describe its behavior according to various aspects.
  • This means each engineering discipline can have the system representation it needs - mechanical, electronical, etc.
  • The central availability of all aspects simplifies decision processes in development.
  • The common system representation enables and promotes collaboration.
  • A graphic model provides project members with a simple introduction to the architecture of a system.
  • A current standard in systems engineering is used as the working method. SysML (Systems Modeling Language) is a standardized extension of (Unified Modeling Language) for the modeling of complex systems.
  • It can be started immediately, and no training in model development is necessary.
Integration in the product development process (PDP)
  • Modeled structures are automatically converted to a tree view.
  • The directory tree is used as the main product representation to conduct further analyses.
  • The people involved in the project operate based on the structure and provide the specifications (technical / functional specification), risk or hazard analyses, DVP&R's, etc., for example, depending on their area of responsibility.
Ideas become products with PLATO e1ns - 100% web-based
PLATO e1ns - Beyond FMEA

2:13 min

PLATO e1ns - Engineering is so simple

2:23 min

The development of the FollowMe with PLATO e1ns

3:20 min

FMEA connected - Create FMEAs in team work - worldwide and easy.

2:13 min

Marcus Schorn, CTO of PLATO AG, in the interview at the Control 2017

1:38 min

Interlinked with other engineering methods

As a central tool for the development, description, and monitoring of a system in the product development phases, e1ns.aspects is interlinked with the other methods available in the PLATO methods toolbox:

  • Requirements Management
  • QFD (Quality Function Deployment)
  • Functional Safety
  • Risk / Hazard Analysis
  • Design Verification
Individual forms for engineering methodsIndividual forms for engineering methods

e1ns.methods provides individual forms for the implementation of engineering methods and analyses for companies in a web application.

Mehr erfahren
Maik Teschner, Nexperia Germany GmbH

Maik Teschner about the use of the PLATO Risk Management software SCIO™ at Nexperia Germany GmbH.

Holger Handelmann, Lumileds Germany GmbH

Holger Handelmann about the use of PLATO Risk Management Software SCIO™ at Lumileds Germany GmbH.

Jochen Bauhaus, Johann Borgers GmbH

Jochen Bauhaus about the reasons for using the FMEA software from PLATO at Johann Borgers GmbH.

Gerhard Seifert, Tenneco GmbH

Gerhard Seifert about the reasons for using PLATO FMEA software at Tenneco GmbH.

Jürgen Heinzelmann, Mahle Behr GmbH & Co. KG

Jürgen Heinzelmann about the use and the advantages of the template management system from PLATO.

Gary Baker, PhD, Johnson Matthey

Gary Baker, PhD, about the reasons for using the PLATO software at Johnson Matthey.



+49 451 930986-0


* 区域为必填区