The following terms are used in this article:
There are two types of liability: non-contractual liability, which applies whenever you place products on the market. You owe contractual liability to your contractual partners.
For non-contractual liability applies to product liability:
Liable are the management and the board of directors, even after they have relinquished their mandate.
For general liability:
Here (gross negligence and of course intent) everyone is personally liable. Specifically, for example, if someone does not comply with processes and instructions or standards.
Your contracts and the Swiss Code of Obligations (OR) apply here, typically the following types of contract:
The manufacturer is contractually liable on the one hand, but more importantly non-contractually liable for functional safety:
Please note that software, especially embedded software, can/ is also classified as a movable thing and therefore also falls under this liability, including cyber security.
Specifically, this means that the manufacturer's management and board of directors can be held liable if the products they place on the market for end customers ("B2C") are not safe. For employee liability, see "How is the Employee Liable?".
The subcontractor is contractually liable on the one hand, but more importantly non-contractually liable for functional safety:
Please note that software, especially embedded software, can/ is also classified as a movable thing and therefore also falls under this liability, including cyber security.
Specifically, this means that the subcontractor's management and board of directors can be held liable if the products they place on the market are not safe. For employee liability, see "How is the Employee Liable?".
The development service provider is contractually liable on the one hand, but more importantly non-contractually liable for functional safety:
Please note that software, especially embedded software, can/ is also classified as a movable thing and therefore also falls under this liability, including cyber security.
Specifically, this means that the development service providerr's management and board of directors can be held liable if they act negligently. For employee liability, see "How is the Employee Liable?".
The manufacturer is always responsible for quality assurance. He can comply with this responsibility for purchased development services in regulated markets (e.g. medical devices, aviation) in two ways:
The first route is of course much easier for the manufacturer.
In principle, the notified body is contractually liable in the same way as the development service provider, but is more importantly non-contractually liable for functional safety:
The manufacturer is contractually liable on the one hand, but more importantly non-contractually liable for functional safety:
Specifically, this means that the notified body's management and board of directors can be held liable if they act negligently. For employee liability, see "How is the Employee Liable?".
A document from the notified body is therefore mainly a marketing issue and can possibly serve as an argumentation aid in the event of a court case.
Attention: In the "breast implant case" of 2020, a court has ruled that the notified body of the implant manufacturer is liable for the defective silicone oil that was not identified in the audit. According to the judges in Karlsruhe, ensuring the protection of the end customer should not be the sole responsibility of the manufacturer, but also that of the notified body. The notified body has an independent position from its client and serves not only the manufacturer but also the end customer with its testing activities. However, it is still unclear what this case means for Europe-wide jurisdiction.
The employee's is primary liability is non-contractually:
In concrete terms, this means that employees can be held accountable if they act with gross negligence (or worse, intentionally), e.g. if they do not comply with processes or do not carry out a review. They cannot be held accountable for errors, i.e. if they comply with all processes and standards but make a mistake. Otherwise nobody would develop medical devices, airplanes, trains, etc. anymore.
In principle, standards are not legally binding. Their application is therefore voluntary in principle.
However, there are cases where this is not the case:
There is a ruling ("airbag ruling") by the German Federal Court of Justice, which obliges manufacturers to comply with the state of the art in science and technology. Incidentally, the EU directives do the same, although the exact meaning of the term is not defined.
A ruling by the Federal Constitutional Court ("Kalkar ruling") requires that not only standards, but the state of "current human knowledge" be taken as a reference. In concrete terms, this means that more recent and other sources (proposed standards, conferences, papers...) must be consulted when assessing the state of the art in science and technology...
Projects? Ideas? Questions? Let's do a free initial workshop!
No Comments