e1ns.architectSystem and requirements analysis for building a central structure in product and process development.

A central system architecture forms the basis of the activities of all participants as well as their verification in product and process development. It facilitates teamwork, supports internal workflows, and enables the validation and verification of all requirements.

The methodology of e1ns.architect allows to build a model of the system architecture very quickly and systematically. The requirements on a system and/or the customer needs are analyzed and the components that could be used to fulfill the requirements can be identified.

This reciprocal processbetween the formulation of the requirement and the selection of a component for its implementation, automatically builds a system structure. The division into individual, independent units/elements which can be realized separately is depicted in a hierarchical tree. The analysis also includes the company’s own production processes and the components manufactured by suppliers.

Why e1ns.architect? Your benefits.
System design, requirements, and specifications
  • The combination of systematic analysis (link matrix) and the visualization of relationships (nets) is a method that quickly provides robust results.
  • A discipline- and solution-independent representation of the overall system is used as the basis for all further activities.
  • All areas in product and process development work on the same system design and contribute to its completion by integrating their specific requirements, analyses, and data.
  • Requirements are specified in detail and linked to the elements that are responsible for their implementation. Each requirement is validated (link to the DVP&R).
Functional relations and failure analysis
  • Functional relationships result automatically from the system design and are visualized as nets.
  • The function net shows how the requirements are related to the implementation. It shows, e.g. the influence of a process step on the product functionality.
  • Each function is checked for non-compliance, which leads to the creation of the failure net. During development and in case of complaints, the problem causes need to be identified, and it is possible to see which further problems could arise elsewhere as a consequence.
  • The failure net automatically fills in the corresponding FMEA forms with failures, causes, and effects at all system levels.
  • For potential failures, safety functions are defined and traceably linked.
The central system architecture for projects, documents, and tasks
  • e1ns.architect supplies a central structure for all activities, creates all project and product documentation, and generates all verifications needed in product and process development. Consistency, transparency, currency, and traceability provide security during day-to-day work and during audits.
Application and use for e1ns.architect
  • Customer-oriented product planning
  • Requirements analysis and detailed specifications
  • Configuration of a system design
  • Description of functions and responses
  • Analysis of system crashes, failures, and their effects
  • Visualization of relationships with nets for systems, functions, and failures
  • Networking of product requirements and manufacturing processes
  • Formulation of safety functions (functional safety)
  • System analysis using the QFD (Quality Function Deployment) methodology
  • Operation according to VDA (Vol. 4)
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

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


* 区域为必填区