OHO - search engine for sustainable open hardware projects - User contributions [en]

White Rabbit

2022-09-23T12:36:07Z

Robert: Created page with "{{Projekt |subcat=Metrology##Frequency meters |projectname=White Rabbit |projectnameES=White Rabbit |projectnameDE=White Rabbit |firstin=https://ohwr.org/project/white-rabbit |trans_status=WT |desc=White Rabbit is a fully deterministic Ethernet-based network for general purpose data transfer and synchronization. It can synchronize over 1000 nodes with sub-ns accuracy over fiber lengths of up to 10 km. Commercially available. More info at the Wiki page |licence=CCBY40 |ty..."

{{Projekt
|subcat=Metrology##Frequency meters
|projectname=White Rabbit
|projectnameES=White Rabbit
|projectnameDE=White Rabbit
|firstin=https://ohwr.org/project/white-rabbit
|trans_status=WT
|desc=White Rabbit is a fully deterministic Ethernet-based network for general purpose data transfer and synchronization. It can synchronize over 1000 nodes with sub-ns accuracy over fiber lengths of up to 10 km. Commercially available. More info at the Wiki page
|licence=CCBY40
|typeproject=TUBerlin
|organization=CERN
|project_status=active
|maturity=PFP
|design_files_pub=yes
|cad_link=https://ohwr.org/project/wr-switch-hw-v4/tree/enclosure-v1.0
|cad_files_editable=yes
|cad_format=DWG
|mechanical_licence=COHL
|electronic_files_pub=yes
|electronic_link=https://ohwr.org/project/wr-switch-hw-v4/wikis/wrs-v4-main-board-schematics#design-files
|electronic_files_editable=yes
|electronic_license=COHL
|software_files_pub=yes
|assembly_inst_pub=yes
|assembly_instructions_editable=yes
|bill_materials_pub=yes
|bill_materials_link=https://ohwr.org/project/wr-switch-hw-v4/wikis/uploads/8b7ac7b5fc18b7ae2e7783e6b23fbef9/EDA-xxxx_pcb-mat_V1.0.xls
|bill_materials_editable=yes
|contributing_guide_pub=no
|issue_management_system=yes
|issue_management_system_link=https://ohwr.org/project/wr-switch-hw-v4/issues
|versioning_system=yes
|versioning_system_link=https://ohwr.org/project/wr-switch-hw-v4/tree/master
|contains_pdf_drawings=yes
|certificate_requested=No
}}

About Open Hardware

2021-02-26T13:33:39Z

Robert: /* Was sind die Probleme von Open Source Hardware? */

== What is Do it Yourself, Open Hardware and Open Source Hardware? ==
[[File:solar3.png|thumb|'''Do it Yourself refers to the handmade production of products by private individuals or small groups, usually without a commercial background.''']]
[[File:crane5.png|thumb|'''The term "Open (Source) Hardware" borrows from the term "Open (Source) Software" and refers to technical developments and inventions that are not protected by companies through patents or other property rights.''']]
Do it Yourself refers to the handicraft production of products by private individuals or smaller groups, usually without a commercial background.

The term "open (source) hardware" is based on the term "open (source) software" and refers to technical developments and inventions that are not protected by companies through patents or other protective rights. The developers are often individuals, non-profit organizations, or small businesses who make their knowledge freely available to others.

Open hardware and open-source hardware are often used as synonyms, although open-source hardware usually uses stricter criteria. According to the Open Source Hardware Association (OSHWA) definition, open-source hardware (OSH) is "hardware whose blueprints have been made publicly available so that anyone can study, modify, redistribute, and make and sell it and hardware based on it".

The four essential requirements for open-source hardware are:
* Use: Anyone can use it
* Understand: All the important information to be able to understand it must be available.
* Distribute: Anyone can distribute it
* Improve: Anyone can improve it

In order to fulfill these requirements, complete technical documentation is necessary, because without it, points 2-4 cannot be fulfilled. The technical documentation usually consists of:
* CAD files
* Technical drawings, e.g. in PDF format
* Parts lists
* Optional: Documentation of electrical and electronic components
* Optional: software

== Open source hardware compared to open source software ==

In open-source software projects, the product and the documentation are identical: the program code is both the end product and the common international language for documentation and communication between developers. The documentation requires only a minor additional investment of time. This is why a large worldwide community has developed in a relatively short time and why open source software is also very successful from an economic point of view.

In open-source hardware projects, product and documentation are two different things: The realization of an open-source hardware project requires craftsmanship, material input, and a workshop. The documentation of an open-source hardware project requires a CAD workstation as well as knowledge and experience in CAD systems. However, only a small proportion of OSH developers have the knowledge and experience of the latter, even these often cannot afford the relatively high additional workload for clean documentation.

This is an important reason why open-source hardware, in contrast to open source software, does not (yet) play a really relevant role socially and economically.

=== Significance of open source software ===
Open-source software now dominates many market segments, such as:
* Apache for web servers
* Linux with its distributions as server operating systems
* WordPress as CMS and for blogs
* The CMS classics Typo3, Drupal, and Joomla
* PHP as a programming language for web servers
* etc. etc.
=== Significance of open source hardware ===
In contrast, open-source hardware has only a few "lighthouse projects", which have virtually no influence on society as a whole, for example
* Arduino
* 3D printers such as RepRap
* Laser Cutter Lasersaur
* Tabby OSVehicle
* Prosthetic Hands by OpenBionics'
* Wikihouse

There are a few important reasons for this.

== What are the problems of Open Source Hardware? ==
[[File:crowd3.png|thumb|'''Most open-source hardware or DIY projects are not documented at all or only incompletely.'']
There are several reasons for the lack of importance of open source hardware:

=== Problem 1: Documentation ===
Most open-source hardware or DIY projects are not documented at all or documented incompletely. A complete documentation of a technical solution includes e.g. CAD files, technical drawings, parts lists etc. The creation of these documents is time-consuming and sometimes also requires specialised knowledge, for example in CAD systems. Therefore, it is often neglected in non-commercial projects. However, a lack of documentation means that the projects can neither be used by others, nor copied, nor further developed. There are no synergy effects, the different developments cannot be networked or build on each other.

=== Problem 2: Licensing and copyright ===
The number of Do it Yourself projects exceeds the number of Open Hardware projects many fold.
Many good projects are not published under free licenses that allow other people to use and develop the projects freely.

=== Problem 3: Publicity: ===
OSH and DIY projects are often published on small unknown websites in only one language. For those interested in searching in other languages, those projects are untraceable, also because sometimes inappropriate search terms are used. As a result, they are often only found by a small part of the potentially interested network.

About Open Hardware

2021-02-26T13:26:34Z

Robert: /* Open Source Hardware im Vergleich zu Open Source Software */

== What is Do it Yourself, Open Hardware and Open Source Hardware? ==
[[File:solar3.png|thumb|'''Do it Yourself refers to the handmade production of products by private individuals or small groups, usually without a commercial background.''']]
[[File:crane5.png|thumb|'''The term "Open (Source) Hardware" borrows from the term "Open (Source) Software" and refers to technical developments and inventions that are not protected by companies through patents or other property rights.''']]
Do it Yourself refers to the handicraft production of products by private individuals or smaller groups, usually without a commercial background.

The term "open (source) hardware" is based on the term "open (source) software" and refers to technical developments and inventions that are not protected by companies through patents or other protective rights. The developers are often individuals, non-profit organizations, or small businesses who make their knowledge freely available to others.

Open hardware and open-source hardware are often used as synonyms, although open-source hardware usually uses stricter criteria. According to the Open Source Hardware Association (OSHWA) definition, open-source hardware (OSH) is "hardware whose blueprints have been made publicly available so that anyone can study, modify, redistribute, and make and sell it and hardware based on it".

The four essential requirements for open-source hardware are:
* Use: Anyone can use it
* Understand: All the important information to be able to understand it must be available.
* Distribute: Anyone can distribute it
* Improve: Anyone can improve it

In order to fulfill these requirements, complete technical documentation is necessary, because without it, points 2-4 cannot be fulfilled. The technical documentation usually consists of:
* CAD files
* Technical drawings, e.g. in PDF format
* Parts lists
* Optional: Documentation of electrical and electronic components
* Optional: software

== Open source hardware compared to open source software ==

In open-source software projects, the product and the documentation are identical: the program code is both the end product and the common international language for documentation and communication between developers. The documentation requires only a minor additional investment of time. This is why a large worldwide community has developed in a relatively short time and why open source software is also very successful from an economic point of view.

In open-source hardware projects, product and documentation are two different things: The realization of an open-source hardware project requires craftsmanship, material input, and a workshop. The documentation of an open-source hardware project requires a CAD workstation as well as knowledge and experience in CAD systems. However, only a small proportion of OSH developers have the knowledge and experience of the latter, even these often cannot afford the relatively high additional workload for clean documentation.

This is an important reason why open-source hardware, in contrast to open source software, does not (yet) play a really relevant role socially and economically.

=== Significance of open source software ===
Open-source software now dominates many market segments, such as:
* Apache for web servers
* Linux with its distributions as server operating systems
* WordPress as CMS and for blogs
* The CMS classics Typo3, Drupal, and Joomla
* PHP as a programming language for web servers
* etc. etc.
=== Significance of open source hardware ===
In contrast, open-source hardware has only a few "lighthouse projects", which have virtually no influence on society as a whole, for example
* Arduino
* 3D printers such as RepRap
* Laser Cutter Lasersaur
* Tabby OSVehicle
* Prosthetic Hands by OpenBionics'
* Wikihouse

There are a few important reasons for this.

== Was sind die Probleme von Open Source Hardware? ==
[[File:crowd3.png|thumb|'''Die meisten Open Source Hardware oder DIY-Projekte sind gar nicht oder nur unvollständig dokumentiert.''']]
Für die fehlende Bedeutung von Open Source Hardware gibt es mehrere Gründe:

=== Problem 1: Dokumentation ===
Die meisten Open Source Hardware oder DIY-Projekte sind gar nicht oder nur unvollständig dokumentiert. Eine vollständige Dokumentation einer technischen Lösung umfasst z.B. CAD-Dateien, technische Zeichnungen, Stücklisten etc. Die Erstellung dieser Unterlagen ist zeitaufwändig und erfordert teilweise auch Spezialkenntnisse, zum Beispiel in CAD-Systemen. Deshalb wird sie in nicht kommerziellen Projekten häufig vernachlässigt. Eine fehlende Dokumentation bewirkt jedoch, dass die Projekte von anderen Menschen weder genutzt, noch nachgebaut, noch weiterentwickelt werden können. Es entstehen keine Synergie-Effekte, die unterschiedlichen Entwicklungen können nicht einander vernetzt werden oder aufeinander aufbauen.

=== Problem 2: Lizenzierung und Urheberrecht ===
Die Anzahl an Do it Yourself Projekten übersteigt die Anzahl an Open Hardware Projekten um ein Vielfaches.
Viele gute Projekte sind nicht unter freien Lizenzen veröffentlicht, die es anderen Menschen ermöglichen die Projekte frei zu nutzen und weiter zu entwickeln.

=== Problem 3: Bekanntmachung: ===
OSH- und DIY-Projekte werden häufig auf kleinen unbekannten Websites in nur einer Sprache veröffentlicht. Für Interessenten, die in anderen Sprachen suchen, sind sie unauffindbar, auch weil bisweilen wenig treffende Suchbegriffe verwendet werden. Dadurch werden sie häufig nur von einem kleinen Teil der potentiellen Interessnet gefunden.

About Open Hardware

2021-02-26T12:26:49Z

Robert: /* Was ist Do it Yourself, Open Hardware und Open Source Hardware? */

== What is Do it Yourself, Open Hardware and Open Source Hardware? ==
[[File:solar3.png|thumb|'''Do it Yourself refers to the handmade production of products by private individuals or small groups, usually without a commercial background.''']]
[[File:crane5.png|thumb|'''The term "Open (Source) Hardware" borrows from the term "Open (Source) Software" and refers to technical developments and inventions that are not protected by companies through patents or other property rights.''']]
Do it Yourself refers to the handicraft production of products by private individuals or smaller groups, usually without a commercial background.

The term "open (source) hardware" is based on the term "open (source) software" and refers to technical developments and inventions that are not protected by companies through patents or other protective rights. The developers are often individuals, non-profit organizations, or small businesses who make their knowledge freely available to others.

Open hardware and open-source hardware are often used as synonyms, although open-source hardware usually uses stricter criteria. According to the Open Source Hardware Association (OSHWA) definition, open-source hardware (OSH) is "hardware whose blueprints have been made publicly available so that anyone can study, modify, redistribute, and make and sell it and hardware based on it".

The four essential requirements for open-source hardware are:
* Use: Anyone can use it
* Understand: All the important information to be able to understand it must be available.
* Distribute: Anyone can distribute it
* Improve: Anyone can improve it

In order to fulfill these requirements, complete technical documentation is necessary, because without it, points 2-4 cannot be fulfilled. The technical documentation usually consists of:
* CAD files
* Technical drawings, e.g. in PDF format
* Parts lists
* Optional: Documentation of electrical and electronic components
* Optional: software

== Open Source Hardware im Vergleich zu Open Source Software ==

Bei Open Source Software Projekten sind das Produkt und die Dokumentation identisch: Der Programmcode ist gleichzeitig das Endprodukt und die gemeinsame internationale Sprache für Dokumentation und Kommunikation zwischen den Entwicklern. Die Dokumentation erfordert nur einen geringen zusätzlichen Zeitaufwand. Deshalb hat sich in relativ kurzer Zeit eine große weltweite Community entwickelt und deshalb ist Open Source Software auch aus wirtschaftlicher Sicht sehr erfolgreich.

Bei Open Source Hardware Projekten sind Produkt und Dokumentation zwei unterschiedliche Dinge: Die Realisierung eines Open Source Hardware Projektes erfordert handwerkliche Fähigkeiten, Materialeinsatz und eine Werkstatt. Die Dokumentation eines Open Source Hardware Projektes erfordert eine CAD-Arbeitsstation sowie Kenntnisse und Erfahrung in CAD-Systemen. Über letzteres verfügt jedoch nur ein geringer Teil der OSH-Entwickler. Und selbst diese können den relativ hohen zusätzlichen Arbeitsaufwand für eine saubere Dokumentation häufig nicht leisten.

Dies ist ein wichtiger Grund, dass Open Source Hardware im Gegensatz zu Open Source Software gesellschaftlich und ökonomisch (noch) keine wirklich relevante Rolle spielt.

=== Bedeutung von Open Source Software ===
Open Source Software dominiert mittlerweile viele Marktsegmente, wie zum Beispiel:
* Apache für Web-Server
* Linux mit seinen Distributionen als Server-Betriebssysteme
* Wordpress als CMS und für Blogs
* die CMS-Klassiker Typo3, Drupal, und Joomla
* PHP als Programmiersprache für Webserver
* usw. usw.

=== Bedeutung von Open Source Hardware ===
Demgegenüber kann Open Source Hardware nur wenige „Leuchtturmprojekte“ vorweisen, welche gesamtgesellschaftlich jedoch so gut wie keinen Einfluss haben, wie zum Beispiel
* Arduino
* 3D printers such as RepRa
* Laser Cutter Lasersaur
* Tabby OSVehicle
* Prosthetic Hands von OpenBionics’
* Wikihouse

Hierfür gibt es einige wichtige Gründe.

== Was sind die Probleme von Open Source Hardware? ==
[[File:crowd3.png|thumb|'''Die meisten Open Source Hardware oder DIY-Projekte sind gar nicht oder nur unvollständig dokumentiert.''']]
Für die fehlende Bedeutung von Open Source Hardware gibt es mehrere Gründe:

=== Problem 1: Dokumentation ===
Die meisten Open Source Hardware oder DIY-Projekte sind gar nicht oder nur unvollständig dokumentiert. Eine vollständige Dokumentation einer technischen Lösung umfasst z.B. CAD-Dateien, technische Zeichnungen, Stücklisten etc. Die Erstellung dieser Unterlagen ist zeitaufwändig und erfordert teilweise auch Spezialkenntnisse, zum Beispiel in CAD-Systemen. Deshalb wird sie in nicht kommerziellen Projekten häufig vernachlässigt. Eine fehlende Dokumentation bewirkt jedoch, dass die Projekte von anderen Menschen weder genutzt, noch nachgebaut, noch weiterentwickelt werden können. Es entstehen keine Synergie-Effekte, die unterschiedlichen Entwicklungen können nicht einander vernetzt werden oder aufeinander aufbauen.

=== Problem 2: Lizenzierung und Urheberrecht ===
Die Anzahl an Do it Yourself Projekten übersteigt die Anzahl an Open Hardware Projekten um ein Vielfaches.
Viele gute Projekte sind nicht unter freien Lizenzen veröffentlicht, die es anderen Menschen ermöglichen die Projekte frei zu nutzen und weiter zu entwickeln.

=== Problem 3: Bekanntmachung: ===
OSH- und DIY-Projekte werden häufig auf kleinen unbekannten Websites in nur einer Sprache veröffentlicht. Für Interessenten, die in anderen Sprachen suchen, sind sie unauffindbar, auch weil bisweilen wenig treffende Suchbegriffe verwendet werden. Dadurch werden sie häufig nur von einem kleinen Teil der potentiellen Interessnet gefunden.

About OHO Open Hardware Observatory

2021-02-26T12:14:26Z

Robert: /* Zielgruppen */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

* Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
* Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
* Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
* Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
* Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==What happens next?==
====Projects====
We are currently in the process of documenting and certifying the first reference projects. By the end of 2021, we will put as many well-documented open hardware projects as possible online on OHO. One focus will be the area of renewable energies.
====Community====
We will lay the foundation for the OHO community, and try to get as many hardware developers as possible to publish their projects cleanly documented under free licenses.
====Publication of projects====
An important goal is that as many people as possible have access to the information on OHO. To this end, we will cooperate with a number of other organizations, such as Wikipedia. Furthermore, we will set up various social media channels that will allow us to connect directly with the developers and users of Open Hardware.

==The vision==
Our vision is to create an international community of people that - similar to Wikipedia - builds and develops a knowledge platform for free sustainable technical knowledge. And that this platform in the same way as Wikipedia is available to all people worldwide in many languages and thus contributes to making technical and economic development on our planet more sustainable.

==The key objectives of OHO are:==
* Find sustainable Do It Yourself and Open Hardware projects (> OHO Search Engine)
* Create CAD files, blueprints and parts lists of selected projects (> OHO CAD Center)
* Certify selected projects and make them known worldwide (> OHO Certification Center)
* Connect project developers with users and supporters (> OHO Community)

==Target groups==
====Individuals who====
*would like to replicate projects for their own use
*would like to develop projects further
====Start-ups, small or medium-sized enterprises who====
*want to replicate and market projects
*want to further develop existing products
====Organisations from the fields of====
*Open Source Hardware, Do it Yourself, FabLab etc.
*Sustainable development
*Development cooperation, Development aid

About OHO Open Hardware Observatory

2021-02-26T12:12:11Z

Robert: /* The key objectives of OHO are: */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

* Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
* Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
* Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
* Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
* Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==What happens next?==
====Projects====
We are currently in the process of documenting and certifying the first reference projects. By the end of 2021, we will put as many well-documented open hardware projects as possible online on OHO. One focus will be the area of renewable energies.
====Community====
We will lay the foundation for the OHO community, and try to get as many hardware developers as possible to publish their projects cleanly documented under free licenses.
====Publication of projects====
An important goal is that as many people as possible have access to the information on OHO. To this end, we will cooperate with a number of other organizations, such as Wikipedia. Furthermore, we will set up various social media channels that will allow us to connect directly with the developers and users of Open Hardware.

==The vision==
Our vision is to create an international community of people that - similar to Wikipedia - builds and develops a knowledge platform for free sustainable technical knowledge. And that this platform in the same way as Wikipedia is available to all people worldwide in many languages and thus contributes to making technical and economic development on our planet more sustainable.

==The key objectives of OHO are:==
* Find sustainable Do It Yourself and Open Hardware projects (> OHO Search Engine)
* Create CAD files, blueprints and parts lists of selected projects (> OHO CAD Center)
* Certify selected projects and make them known worldwide (> OHO Certification Center)
* Connect project developers with users and supporters (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T12:11:39Z

Robert: /* Die wichtigsten Ziele von OHO sind: */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

* Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
* Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
* Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
* Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
* Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==What happens next?==
====Projects====
We are currently in the process of documenting and certifying the first reference projects. By the end of 2021, we will put as many well-documented open hardware projects as possible online on OHO. One focus will be the area of renewable energies.
====Community====
We will lay the foundation for the OHO community, and try to get as many hardware developers as possible to publish their projects cleanly documented under free licenses.
====Publication of projects====
An important goal is that as many people as possible have access to the information on OHO. To this end, we will cooperate with a number of other organizations, such as Wikipedia. Furthermore, we will set up various social media channels that will allow us to connect directly with the developers and users of Open Hardware.

==The vision==
Our vision is to create an international community of people that - similar to Wikipedia - builds and develops a knowledge platform for free sustainable technical knowledge. And that this platform in the same way as Wikipedia is available to all people worldwide in many languages and thus contributes to making technical and economic development on our planet more sustainable.

==The key objectives of OHO are:==
Find sustainable Do It Yourself and Open Hardware projects (> OHO Search Engine)
Create CAD files, blueprints and parts lists of selected projects (> OHO CAD Center)
Certify selected projects and make them known worldwide (> OHO Certification Center)
Connect project developers with users and supporters (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T12:09:04Z

Robert: /* Die Vision */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

* Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
* Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
* Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
* Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
* Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==What happens next?==
====Projects====
We are currently in the process of documenting and certifying the first reference projects. By the end of 2021, we will put as many well-documented open hardware projects as possible online on OHO. One focus will be the area of renewable energies.
====Community====
We will lay the foundation for the OHO community, and try to get as many hardware developers as possible to publish their projects cleanly documented under free licenses.
====Publication of projects====
An important goal is that as many people as possible have access to the information on OHO. To this end, we will cooperate with a number of other organizations, such as Wikipedia. Furthermore, we will set up various social media channels that will allow us to connect directly with the developers and users of Open Hardware.

==The vision==
Our vision is to create an international community of people that - similar to Wikipedia - builds and develops a knowledge platform for free sustainable technical knowledge. And that this platform in the same way as Wikipedia is available to all people worldwide in many languages and thus contributes to making technical and economic development on our planet more sustainable.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T12:06:21Z

Robert: /* Wie geht es weiter? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

* Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
* Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
* Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
* Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
* Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==What happens next?==
====Projects====
We are currently in the process of documenting and certifying the first reference projects. By the end of 2021, we will put as many well-documented open hardware projects as possible online on OHO. One focus will be the area of renewable energies.
====Community====
We will lay the foundation for the OHO community, and try to get as many hardware developers as possible to publish their projects cleanly documented under free licenses.
====Publication of projects====
An important goal is that as many people as possible have access to the information on OHO. To this end, we will cooperate with a number of other organizations, such as Wikipedia. Furthermore, we will set up various social media channels that will allow us to connect directly with the developers and users of Open Hardware.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T12:00:52Z

Robert: /* What does OHO do? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

* Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
* Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
* Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
* Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
* Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==Wie geht es weiter?==
====Projekte====
Aktuell sind wir dabei, erste Referenzprojekte zu dokumentieren und zu zertifizieren. Bis Ende 2021 werden wir möglichst viele gut dokumentierte Open Hardware Projekte auf OHO online stellen. Ein Schwerpunkt wird u.a. der Bereich Erneuerbare Energien sein.
====Community====
Wir werden den Grundstein für die OHO Community legen, und versuchen möglichst viele Hardware Entwickler dafür zu gewinnen, ihre Projekte sauber dokumentiert unter freien Lizenzen zu veröffentlichen.
====Bekanntmachung der Projekte====
Ein wichtiges Ziel ist es, dass möglichst viele Menschen Zugang zu den Informationen auf OHO haben. Hierzu werden wir mit einer Reihe von anderen Organisationen kooperieren, wie zum Beispiel mit Wikipedia. Außerdem werden wir verschiedene Social Media Kanäle aufbauen, die es uns erlauben, direkt mit den Entwicklern und Nutzern von Open Hardware in Verbindung zu treten.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T12:00:12Z

Robert: /* Was hat OHO bisher erreicht? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

# Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
# Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
# Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
# Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
# Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Achievements of OHO so far?==
The following milestones have been achieved since OHO was founded in 2019:
*Development of the OHO search engine.
*Development of DIN Spec 3105
*Development of the OHO certification platform
*Development of the OHO Standards for Technical Documentation.
*Cooperation with various governmental and private organizations
*Acquisition of first grants
*Establishment of the OHO CAD Centre with several experienced engineers

==Wie geht es weiter?==
====Projekte====
Aktuell sind wir dabei, erste Referenzprojekte zu dokumentieren und zu zertifizieren. Bis Ende 2021 werden wir möglichst viele gut dokumentierte Open Hardware Projekte auf OHO online stellen. Ein Schwerpunkt wird u.a. der Bereich Erneuerbare Energien sein.
====Community====
Wir werden den Grundstein für die OHO Community legen, und versuchen möglichst viele Hardware Entwickler dafür zu gewinnen, ihre Projekte sauber dokumentiert unter freien Lizenzen zu veröffentlichen.
====Bekanntmachung der Projekte====
Ein wichtiges Ziel ist es, dass möglichst viele Menschen Zugang zu den Informationen auf OHO haben. Hierzu werden wir mit einer Reihe von anderen Organisationen kooperieren, wie zum Beispiel mit Wikipedia. Außerdem werden wir verschiedene Social Media Kanäle aufbauen, die es uns erlauben, direkt mit den Entwicklern und Nutzern von Open Hardware in Verbindung zu treten.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T11:57:19Z

Robert: /* What does OHO do? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:

# Development of standards for the documentation and certification of Open Hardware projects e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
# Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
# Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
# Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
# Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Was hat OHO bisher erreicht?==
Folgende Milestones wurden seit der seit der Gründung von OHO im Jahr 2019 erreicht:
*Entwicklung der OHO Suchmaschine
*Entwicklung der DIN Spec 3105
*Entwicklung der OHO Zertifizierungsplattform
*Entwicklung der OHO Standards für die Technische Dokumentation
*Kooperationen mit verschiedenen staatlichen und privaten Organisationen
*Akquisition von ersten Fördergeldern
*Einrichtung des OHO CAD Centers mit mehreren erfahrenen Ingenieuren

==Wie geht es weiter?==
====Projekte====
Aktuell sind wir dabei, erste Referenzprojekte zu dokumentieren und zu zertifizieren. Bis Ende 2021 werden wir möglichst viele gut dokumentierte Open Hardware Projekte auf OHO online stellen. Ein Schwerpunkt wird u.a. der Bereich Erneuerbare Energien sein.
====Community====
Wir werden den Grundstein für die OHO Community legen, und versuchen möglichst viele Hardware Entwickler dafür zu gewinnen, ihre Projekte sauber dokumentiert unter freien Lizenzen zu veröffentlichen.
====Bekanntmachung der Projekte====
Ein wichtiges Ziel ist es, dass möglichst viele Menschen Zugang zu den Informationen auf OHO haben. Hierzu werden wir mit einer Reihe von anderen Organisationen kooperieren, wie zum Beispiel mit Wikipedia. Außerdem werden wir verschiedene Social Media Kanäle aufbauen, die es uns erlauben, direkt mit den Entwicklern und Nutzern von Open Hardware in Verbindung zu treten.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T11:54:00Z

Robert: /* Was macht OHO? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==What does OHO do?==
OHO aims to contribute to this in the following ways:
1. Development of standards for the documentation and certification of Open Hardware projects.
e.g. through the DIN Spec 3105, developed together with the German Institute for Standardisation.
2. Registration and categorization of Open Hardware and Do it Yourself projects through a specially developed search engine.
3. Creation of CAD files, technical drawings, and parts lists of selected Open Hardware projects.
4. Certification of the selected projects, where the projects are checked by experienced designers for safety, quality, robustness, licensing, etc.
5. Promotion and dissemination of the selected projects together with other organizations, such as Wikipedia, etc.

==Was hat OHO bisher erreicht?==
Folgende Milestones wurden seit der seit der Gründung von OHO im Jahr 2019 erreicht:
*Entwicklung der OHO Suchmaschine
*Entwicklung der DIN Spec 3105
*Entwicklung der OHO Zertifizierungsplattform
*Entwicklung der OHO Standards für die Technische Dokumentation
*Kooperationen mit verschiedenen staatlichen und privaten Organisationen
*Akquisition von ersten Fördergeldern
*Einrichtung des OHO CAD Centers mit mehreren erfahrenen Ingenieuren

==Wie geht es weiter?==
====Projekte====
Aktuell sind wir dabei, erste Referenzprojekte zu dokumentieren und zu zertifizieren. Bis Ende 2021 werden wir möglichst viele gut dokumentierte Open Hardware Projekte auf OHO online stellen. Ein Schwerpunkt wird u.a. der Bereich Erneuerbare Energien sein.
====Community====
Wir werden den Grundstein für die OHO Community legen, und versuchen möglichst viele Hardware Entwickler dafür zu gewinnen, ihre Projekte sauber dokumentiert unter freien Lizenzen zu veröffentlichen.
====Bekanntmachung der Projekte====
Ein wichtiges Ziel ist es, dass möglichst viele Menschen Zugang zu den Informationen auf OHO haben. Hierzu werden wir mit einer Reihe von anderen Organisationen kooperieren, wie zum Beispiel mit Wikipedia. Außerdem werden wir verschiedene Social Media Kanäle aufbauen, die es uns erlauben, direkt mit den Entwicklern und Nutzern von Open Hardware in Verbindung zu treten.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T11:51:52Z

Robert: /* Warum gibt es OHO? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Why does OHO exist?==
The starting point of OHO is the fact that there are thousands of Do it Yourself and Open Hardware projects worldwide. However, more than 95% of these projects are poorly documented or not documented at all. This means that there are no construction plans and parts lists. They can therefore only be rebuilt, modified, or further developed with great effort. In addition, many of these projects are on small unknown websites, are only published in one language, and are therefore difficult to find.

On the other hand, there is a huge need for good Open Hardware projects, e.g. in the fields of renewable energies, environmental technologies, technologies for small industries, etc. Here, Open Hardware projects can give important impulses for sustainable economic activity and create millions of new jobs. Especially in developing countries, where access to affordable technologies and product ideas is much more limited than in industrialized countries, Open Hardware can be an effective strategy for technology transfer and sustainable economic growth.

==Was macht OHO?==
OHO will hierzu in folgender Weise beitragen:
1. Entwicklung von Standards für die Dokumentation und Zertifizierung von Open Hardware Projekten
z.B. durch die gemeinsam mit dem Deutschen Instititut für Normung entwickelten DIN Spec 3105
2. Erfassung und Kategorisierung von Open Hardware und Do it Yourself Projekten durch eine speziell hierfür entwickelte Suchmaschine.
3. Erstellung von CAD-Dateien, technischen Zeichnungen und Stücklisten ausgewählter Open Hardware Projekte.
4. Zertifizierung der ausgewählten Projekte, hierbei werden die Projekte von erfahrenen Konstrukteuren auf Sicherheit, Qualität, Robustheit, Lizensierung etc. überprüft.
5. Bekanntmachung und Verbreitung der ausgewählten Projekte gemeinsam mit anderen Organisationen, wie zum Beispiel Wikipedia u.a.

==Was hat OHO bisher erreicht?==
Folgende Milestones wurden seit der seit der Gründung von OHO im Jahr 2019 erreicht:
*Entwicklung der OHO Suchmaschine
*Entwicklung der DIN Spec 3105
*Entwicklung der OHO Zertifizierungsplattform
*Entwicklung der OHO Standards für die Technische Dokumentation
*Kooperationen mit verschiedenen staatlichen und privaten Organisationen
*Akquisition von ersten Fördergeldern
*Einrichtung des OHO CAD Centers mit mehreren erfahrenen Ingenieuren

==Wie geht es weiter?==
====Projekte====
Aktuell sind wir dabei, erste Referenzprojekte zu dokumentieren und zu zertifizieren. Bis Ende 2021 werden wir möglichst viele gut dokumentierte Open Hardware Projekte auf OHO online stellen. Ein Schwerpunkt wird u.a. der Bereich Erneuerbare Energien sein.
====Community====
Wir werden den Grundstein für die OHO Community legen, und versuchen möglichst viele Hardware Entwickler dafür zu gewinnen, ihre Projekte sauber dokumentiert unter freien Lizenzen zu veröffentlichen.
====Bekanntmachung der Projekte====
Ein wichtiges Ziel ist es, dass möglichst viele Menschen Zugang zu den Informationen auf OHO haben. Hierzu werden wir mit einer Reihe von anderen Organisationen kooperieren, wie zum Beispiel mit Wikipedia. Außerdem werden wir verschiedene Social Media Kanäle aufbauen, die es uns erlauben, direkt mit den Entwicklern und Nutzern von Open Hardware in Verbindung zu treten.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About OHO Open Hardware Observatory

2021-02-26T11:47:12Z

Robert: /* Was ist OHO? */

==What is OHO?==
www.oho.wiki (OHO) is a platform that supports, improves and publicises sustainable Open Hardware projects. Open Hardware refers to technologies and products whose documentation (plans, parts lists, etc.) are freely available so that individuals and companies can replicate and further develop them. OHO was founded with the support of the Technische Universität Berlin (TU Berlin) and is a spin-off of the non-profit organisation Source Ecology Germany e.V.

==Warum gibt es OHO?==
Ausgangspunkt von OHO ist die Tatsache, dass es weltweit viele Tausende Do it Yourself und Open Hardware Projekte gibt. Mehr als 95% dieser Projekte sind jedoch nur unzureichend oder gar nicht dokumentiert. Das bedeutet, dass es keine Baupläne und Stücklisten gibt. Sie können also nur mit hohem Aufwand nachgebaut, geändert oder weiterentwickelt werden. Außerdem stehen viele dieser Projekte auf kleinen unbekannten Websites, sind nur in einer Sprache veröffentlicht und sind deswegen nur schwierig zu finden.

Andererseits existiert ein riesiger Bedarf an guten Open Hardware Projekten, z.B. in den Bereichen Erneuerbare Energien, Umwelttechnologien, Technologien für Kleinindustrien etc. Hier können Open Hardware Projekte wichtige Impulse für nachhaltiges Wirtschaften geben und Millionen neuer Arbeitsplätze schaffen. Besonders in ärmeren Ländern, wo der Zugang zu bezahlbaren Technologien und Produktideen, viel begrenzter ist als in Industrieländern, kann Open Hardware eine wirkungsvolle Strategie für den Technologietransfer und nachhaltiges Wirtschaftswachstum werden.

==Was macht OHO?==
OHO will hierzu in folgender Weise beitragen:
1. Entwicklung von Standards für die Dokumentation und Zertifizierung von Open Hardware Projekten
z.B. durch die gemeinsam mit dem Deutschen Instititut für Normung entwickelten DIN Spec 3105
2. Erfassung und Kategorisierung von Open Hardware und Do it Yourself Projekten durch eine speziell hierfür entwickelte Suchmaschine.
3. Erstellung von CAD-Dateien, technischen Zeichnungen und Stücklisten ausgewählter Open Hardware Projekte.
4. Zertifizierung der ausgewählten Projekte, hierbei werden die Projekte von erfahrenen Konstrukteuren auf Sicherheit, Qualität, Robustheit, Lizensierung etc. überprüft.
5. Bekanntmachung und Verbreitung der ausgewählten Projekte gemeinsam mit anderen Organisationen, wie zum Beispiel Wikipedia u.a.

==Was hat OHO bisher erreicht?==
Folgende Milestones wurden seit der seit der Gründung von OHO im Jahr 2019 erreicht:
*Entwicklung der OHO Suchmaschine
*Entwicklung der DIN Spec 3105
*Entwicklung der OHO Zertifizierungsplattform
*Entwicklung der OHO Standards für die Technische Dokumentation
*Kooperationen mit verschiedenen staatlichen und privaten Organisationen
*Akquisition von ersten Fördergeldern
*Einrichtung des OHO CAD Centers mit mehreren erfahrenen Ingenieuren

==Wie geht es weiter?==
====Projekte====
Aktuell sind wir dabei, erste Referenzprojekte zu dokumentieren und zu zertifizieren. Bis Ende 2021 werden wir möglichst viele gut dokumentierte Open Hardware Projekte auf OHO online stellen. Ein Schwerpunkt wird u.a. der Bereich Erneuerbare Energien sein.
====Community====
Wir werden den Grundstein für die OHO Community legen, und versuchen möglichst viele Hardware Entwickler dafür zu gewinnen, ihre Projekte sauber dokumentiert unter freien Lizenzen zu veröffentlichen.
====Bekanntmachung der Projekte====
Ein wichtiges Ziel ist es, dass möglichst viele Menschen Zugang zu den Informationen auf OHO haben. Hierzu werden wir mit einer Reihe von anderen Organisationen kooperieren, wie zum Beispiel mit Wikipedia. Außerdem werden wir verschiedene Social Media Kanäle aufbauen, die es uns erlauben, direkt mit den Entwicklern und Nutzern von Open Hardware in Verbindung zu treten.

==Die Vision==
Unsere Vision ist es, dass eine internationale Community aus Menschen entsteht, die – ähnlich wie Wikipedia - eine Wissensplattform für freies nachhaltiges technisches Wissen aufbaut und weiterentwickelt. Und das diese Plattform - ähnlich wie Wikipedia – allen Menschen weltweit in vielen Sprachen zur Verfügung steht und so dazu beiträgt, die technische und wirtschaftliche Entwicklung auf unserer Erde nachhaltiger zu gestalten.

==Die wichtigsten Ziele von OHO sind:==
Nachhaltige Do It Yourself- und Open Hardware-Projekte finden (> OHO-Suchmaschine)
CAD-Dateien, Baupläne und Stücklisten ausgewählter Projekte erstellen (> OHO CAD Center)
Ausgewählte Projekte zertifizieren und weltweit bekannt machen (> OHO Certificatiopn Center)
Projektentwickler mit Anwendern und Unterstützern verbinden (> OHO Community)

==Zielgruppen==
====Einzelpersonen, die====
*Projekte für den eigenen Bedarf nachbauen möchten
*Projekte weiterentwickeln möchten
====Startups, kleine oder mittlere Unternehmen, die====
*Projekte nachbauen und vermarkten möchten
*existierende Produkte weiterentwickeln möchten
====Organisationen aus den Bereichen====
*Open Source Hardware, Do it Yourself, FabLab etc.
*nachhaltige Entwicklung
*Entwicklungszusammenarbeit, Entwicklungshilfe

About the OHO Community

2021-02-26T11:40:52Z

Robert: /* Jeder Interessierte ist herzlich eingeladen, bei OHO mitzumachen, zum Beispiel: */

====OHO does not develop its own projects, but OHO would like to support hardware developers====
[[File:crane1.png|thumb|'''Is an important concern for us to network developers with each other, as well as to enable mutual exchange and mutual support in their work''']]
[[File:solar1.png|thumb|'''
Students: Internships, Bachelor's and Master's theses are easily possible, by the way''']]

* to undertake better projects,
* to document these projects better,
* and to make these projects better known.

That's why it's important to us to network developers with each other, as well as to enable mutual exchange and mutual support in their work.

====OHO is networked with various organizations from the following areas:====
* Open Source Hardware (OSH) or Open Hardware (OH)
* Open Knowledge
* Do it Yourself (DIY)
* FabLabs or Maker Spaces
* Sustainability
* Development Cooperation (DC)
* so on

====Everyone interested is welcome to join OHO, for example:====

* by uploading interesting projects
* by providing reviews for the certification of projects
* by giving feedback, suggestions, ideas about OHO in general or about specific areas on OHO

Students: By the way, internships, bachelor's and master's theses are easily possible. Through cooperation with universities and research institutes, it is even possible to do a doctorate in this field.

About the OHO Community

2021-02-26T11:38:59Z

Robert: /* OHO ist vernetzt mit verschiedenen Organisationen aus den Bereichen: */

====OHO does not develop its own projects, but OHO would like to support hardware developers====
[[File:crane1.png|thumb|'''Is an important concern for us to network developers with each other, as well as to enable mutual exchange and mutual support in their work''']]
[[File:solar1.png|thumb|'''
Students: Internships, Bachelor's and Master's theses are easily possible, by the way''']]

* to undertake better projects,
* to document these projects better,
* and to make these projects better known.

That's why it's important to us to network developers with each other, as well as to enable mutual exchange and mutual support in their work.

====OHO is networked with various organizations from the following areas:====
* Open Source Hardware (OSH) or Open Hardware (OH)
* Open Knowledge
* Do it Yourself (DIY)
* FabLabs or Maker Spaces
* Sustainability
* Development Cooperation (DC)
* so on

====Jeder Interessierte ist herzlich eingeladen, bei OHO mitzumachen, zum Beispiel:====

* durch das Hochladen von interessanten Projekten
* durch die Realisierung von Reviews bei der Zertifizierung von Projekten
* durch Feedback, Anregungen, Ideen zu OHO allgemein oder zu bestimmten Bereichen auf OHO

Studierende: Praktika, Bachelor- und Masterarbeiten sind übrigens problemlos möglich. Durch die Kooperation mit Universitäten und Forschungsinstituten lässt sich in dem Bereich sogar promovieren.

About the OHO Community

2021-02-26T11:36:43Z

Robert: /* OHO entwickelt keine eigenen Projekte sondern OHO möchte Hardware-Entwickler dabei unterstützen */

====OHO does not develop its own projects, but OHO would like to support hardware developers====
[[File:crane1.png|thumb|'''Is an important concern for us to network developers with each other, as well as to enable mutual exchange and mutual support in their work''']]
[[File:solar1.png|thumb|'''
Students: Internships, Bachelor's and Master's theses are easily possible, by the way''']]

* to undertake better projects,
* to document these projects better,
* and to make these projects better known.

That's why it's important to us to network developers with each other, as well as to enable mutual exchange and mutual support in their work.

====OHO ist vernetzt mit verschiedenen Organisationen aus den Bereichen:====
* Open Source Hardware (OSH) bzw. Open Hardware (OH)
* Open Knowledge
* Do it Yourself (DIY)
* FabLabs bzw. Maker Spaces
* Nachhaltigkeit
* Entwicklungszusammenarbeit (EZ)
* u.a.

====Jeder Interessierte ist herzlich eingeladen, bei OHO mitzumachen, zum Beispiel:====

* durch das Hochladen von interessanten Projekten
* durch die Realisierung von Reviews bei der Zertifizierung von Projekten
* durch Feedback, Anregungen, Ideen zu OHO allgemein oder zu bestimmten Bereichen auf OHO

Studierende: Praktika, Bachelor- und Masterarbeiten sind übrigens problemlos möglich. Durch die Kooperation mit Universitäten und Forschungsinstituten lässt sich in dem Bereich sogar promovieren.

About DIN SPEC 3105

2021-02-26T11:33:07Z

Robert: /* Die Norm besteht aus zwei Teilen: */

__NOTOC__
== What is DIN SPEC 3105 ==
[[File: about Grafik DIN11.jpg|thumb|''' The standard is kept strictly compatible with the OSHWA definition and also cooperates with other standardization projects.'']
DIN SPEC 3105 is the only official standard in the open-source area. There are a lot of free/open standards in the IT segment (internet protocols etc.). In the hardware sector, we are only aware of the generally recognized OSHWA definition cited above (which, however, does not set an actual standard) and the Open-Know-How metadata standard. We cooperate closely with both initiatives.

DIN SPEC 3105-1 describes an unambiguous and workable definition of OSH and breaks it down into objective criteria for assessing the compliance of a piece of hardware with this definition. The document sets requirements for technical documentation. It is designed as a supplement to existing standards for technical documentation (e.g. VDI 4500) and is not intended to replace them. It focuses on those aspects of technical documentation that relate to compliance with the principles of open source.

The document builds on the OSHWA Definition 1.0 and the Open Source Definition. The standard is kept strictly compatible with the OSHWA definition and also cooperates with other such standardization projects as the Open Know-How Initiative, which developed the first metadata standard for open source hardware.

==The standard consists of two parts:==

=== DIN SPEC 3105-1 ===
[https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 DIN SPEC 3105-1] defines the term "open source hardware" and provides the framework for explicit, certifiable, technology-specific requirements for technical documentation.

=== DIN SPEC 3105-2 ===
The principles and definitions of [https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 DIN SPEC 3105-1] form the framework for [https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 DIN SPEC 3105-2], which in turn sets out concrete and practical requirements for the establishment of certification procedures. [https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 DIN SPEC 3105-2] establishes a community-based certification process that builds on the scientific peer-review process. This is intended to create a reliable, transparent certificate and simultaneously exclude concentration of power and corruption as far as possible

About DIN SPEC 3105

2021-02-26T11:28:48Z

Robert: /* Was ist die DIN SPEC 3105 */

__NOTOC__
== What is DIN SPEC 3105 ==
[[File: about Grafik DIN11.jpg|thumb|''' The standard is kept strictly compatible with the OSHWA definition and also cooperates with other standardization projects.'']
DIN SPEC 3105 is the only official standard in the open-source area. There are a lot of free/open standards in the IT segment (internet protocols etc.). In the hardware sector, we are only aware of the generally recognized OSHWA definition cited above (which, however, does not set an actual standard) and the Open-Know-How metadata standard. We cooperate closely with both initiatives.

DIN SPEC 3105-1 describes an unambiguous and workable definition of OSH and breaks it down into objective criteria for assessing the compliance of a piece of hardware with this definition. The document sets requirements for technical documentation. It is designed as a supplement to existing standards for technical documentation (e.g. VDI 4500) and is not intended to replace them. It focuses on those aspects of technical documentation that relate to compliance with the principles of open source.

The document builds on the OSHWA Definition 1.0 and the Open Source Definition. The standard is kept strictly compatible with the OSHWA definition and also cooperates with other such standardization projects as the Open Know-How Initiative, which developed the first metadata standard for open source hardware.

==Die Norm besteht aus zwei Teilen:==

=== DIN SPEC 3105-1 ===
[https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 DIN SPEC 3105-1] definiert den Begriff “Open-Source-Hardware” und stellt den Rahmen für eindeutige, zertifizierbare, technologiespezifische Anforderungen an die technische Dokumentation.

=== DIN SPEC 3105-2 ===
Die Grundsätze und Definitionen der [https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 DIN SPEC 3105-1] bilden den Rahmen für die [https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 DIN SPEC 3105-2], die wiederum konkrete und praxisnahe Anforderungen an die Einrichtung von Zertifizierungsverfahren stellt.[https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 DIN SPEC 3105-2] legt einen community-basierten Zertifizierungsprozess fest, der auf dem wissenschaftlichen Peer-Review-Prozess aufbaut. Das soll ein verlässliches, transparentes Zertifikat schaffen und gleichzeitig Machtkonzentration und Korruption, soweit möglich, ausschließen.

About the OHO Certification-center

2021-02-26T11:17:35Z

Robert: /* DIN Spec 3501 - 100% Open Source Hardware */

== Why does the OHO Certification Center exist ==
[[File:lathe9.png|thumb|'''The OHO certificate is a precursor to the DIN Spec 3501 certificate'']]
Previously, there were no generally accepted standards for the development and technical documentation of Open Hardware projects. This makes it difficult to replicate and further develop the projects. To solve this problem, OHO is pursuing two approaches:

* The OHO Certificate
* The DIN Spec 3501 Attestation

== The OHO certificate - rebuilding is possible ==
A prerequisite for the granting of the OHO certificate is that all documents required for the reproduction, such as construction plans and parts lists, are complete and correct. Non-standard documentation is also accepted, e.g. technical drawings made by hand, photos with dimensions, etc. The OHO certificate is only issued if the documentation is complete and correct. The OHO certificate is a preliminary stage for the DIN Spec 3501 certificate. The examination is carried out by an examiner who can prove the necessary qualification and experience.

== True open-source hardware according to the OSHWA definition ==
This is: "Open source hardware is hardware whose blueprints have been made publicly available so that anyone can study, modify, redistribute, and make and sell it and hardware based on it".
The four essential requirements for open-source hardware are:
* Use: Anyone can use it
* Understand: All the important information to be able to understand you must be present
* Distribute: Anyone can distribute it
* Improve: Anyone can improve it

Further requirements are:

=== Documentation ===
The hardware must be published with documentation that includes all source files and allows editing and redistribution of the source files.

=== Required software ===
If the licensed hardware requires software to function properly and perform its essential tasks, it must be under an open-source license recognized by the OSI (Open Source Initiative).

=== Modified works and redistribution ===
The license must permit the making, use, sale, redistribution, modification and derivative works. These must be redistributed under the same license conditions as the original work.

== DIN Spec 3501 - 100% Open Source Hardware ==
[[File:DIN-Logo.png|thumb|'''[https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History German Institute for Standardization Article DIN''']]
=== Weblinks ===
* DIN Spec 3105-1 ([https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 hweiter])
* DIN Spec 3105-2 ([https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 more])

=== Abstract ===
A prerequisite for issuing an attestation according to DIN Spec 3501 is that the projects are documented completely and (as far as possible) in accordance with the standard. Another important requirement is that they fulfill the definition of the Open Source Hardware Association (OSHWA) for Open Hardware (see above).

Based on these requirements, DIN-Spec 3105 was developed together with the German Institute for Standardisation (DIN) and a competence network of almost 40 organizations and specialists. This is the world's only internationally valid standard developed specifically for the development and technical documentation of Open Hardware projects. [https://journalopenhw.medium.com/din-spec-3105-explained-2cce6134c207 more]

=== Peer reviews ===
The peer-review procedure is applied during the audit. This means that the audit is carried out by at least three auditors with sufficient qualifications and experience who examine all components and parts of the project in detail. They examine the project for completeness of documentation and for obvious or hidden defects.

A technical clarification with the project developer as well as subsequent improvements (with corresponding updating of the technical documentation) is explicitly provided. This ensures that the know-how of the auditors can contribute to improving the quality of the project.

The approach is that, starting from the parts list of the project, each component and assembly is examined individually for possible defects. Any ambiguity is documented on the project page. For technical clarification, graphics, videos, calculations, etc. can be uploaded as evidence. Furthermore, each inspector must individually assign the status "successfully inspected" (approved) to all components and all assemblies.
Only then will the complete project be approved as validated. At least two of the inspectors must evaluate the project positively so that the certificate according to DIN Spec 3501 can be issued.

The entire testing process, including the technical clarification, is published so that all decisions made are transparent and comprehensible.

== Die OHO- Zertifizierungsplattform ==

Die Umsetzung der DIN Spec 3105 erfolgt definitionsgemäß über eine Zertifizierungsplattform, auf der die Review Prozesse transparent und für jeden sichtbar realisiert werden.

Die Software für die Zertifizierungsplattform wurde vom OHO Team mit Unterstützung der Technischen Universität Berlin entwickelt. Im Rahmen einer Masterarbeit wurden die erforderlichen Zertifizierungsprozesse geprüft sowie teilweise mitentworfen:

=== Zusammenfassung der Abläufe ===
[[File:about sl1 a.jpg|1080px]]
[[File:about sl1 b.jpg|1080px]]
=== User Registrierung ===
[[File:about sl2 a.jpg|1080px]]
[[File:about sl2 b.jpg|1080px]]
=== Projekt anlegen ===
[[File:about sl3 a.jpg|1080px]]
=== Zertifizierung beantragen ===
[[File:about s4 a.jpg|1080px]]
=== Review ===
[[File:about sl5 a.jpg|1080px]]

Nach einer detaillierten Analyse verschiedener Software-Alternativen, die ebenfalls für die Zertifizierungsplattform hätten verwendet werden können, entschieden wir uns, die Wiki-Software Mediawiki als Basisplattform einzusetzen. Ausschlaggebenden Gründe waren unter anderem:
* MediaWiki ist eine kollaborative Software, die es ermöglicht, dass viele Personen gleichzeitig an den Inhalten der Plattform arbeiten können.
* der Quellcode MediaWiki ist unter freien Lizenzen veröffentlicht und kann entsprechend den speziellen Anforderungen des Projektes angepasst werden
* es gibt eine Vielzahl von Extensions, mit denen wichtige Funktionen, über welche die Basisversion nicht verfüg, hinzugefügt werden können
* MediaWiki hat für jede Seite eine Versionsgeschichte, was bedeutet, dass alle Änderungen lückenlos dokumentiert werden
* Media Wiki wird erfolgreich in Projekten mit hohen Userund Besucherzahlen eingesetzt, das sind keine Stabilität Probleme bekannt.

About the OHO Certification-center

2021-02-26T11:05:16Z

Robert: /* Echte Open Source Hardware nach der OSHWA Definition */

== Why does the OHO Certification Center exist ==
[[File:lathe9.png|thumb|'''The OHO certificate is a precursor to the DIN Spec 3501 certificate'']]
Previously, there were no generally accepted standards for the development and technical documentation of Open Hardware projects. This makes it difficult to replicate and further develop the projects. To solve this problem, OHO is pursuing two approaches:

* The OHO Certificate
* The DIN Spec 3501 Attestation

== The OHO certificate - rebuilding is possible ==
A prerequisite for the granting of the OHO certificate is that all documents required for the reproduction, such as construction plans and parts lists, are complete and correct. Non-standard documentation is also accepted, e.g. technical drawings made by hand, photos with dimensions, etc. The OHO certificate is only issued if the documentation is complete and correct. The OHO certificate is a preliminary stage for the DIN Spec 3501 certificate. The examination is carried out by an examiner who can prove the necessary qualification and experience.

== True open-source hardware according to the OSHWA definition ==
This is: "Open source hardware is hardware whose blueprints have been made publicly available so that anyone can study, modify, redistribute, and make and sell it and hardware based on it".
The four essential requirements for open-source hardware are:
* Use: Anyone can use it
* Understand: All the important information to be able to understand you must be present
* Distribute: Anyone can distribute it
* Improve: Anyone can improve it

Further requirements are:

=== Documentation ===
The hardware must be published with documentation that includes all source files and allows editing and redistribution of the source files.

=== Required software ===
If the licensed hardware requires software to function properly and perform its essential tasks, it must be under an open-source license recognized by the OSI (Open Source Initiative).

=== Modified works and redistribution ===
The license must permit the making, use, sale, redistribution, modification and derivative works. These must be redistributed under the same license conditions as the original work.

== DIN Spec 3501 - 100% Open Source Hardware ==
[[File:DIN-Logo.png|thumb|'''[https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History Deutsches Institut für Normung Artikel DIN''']]]
=== Weblinks ===
* DIN Spec 3105-1 ([https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 hweiter])
* DIN Spec 3105-2 ([https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 weiter])

=== Kurzbeschreibung ===
Voraussetzung für die Erteilung eines Attestats nach DIN Spec 3501 ist, dass die Projekte vollständig und (möglichst) normgerecht dokumentiert sind. Eine weitere wichtige Voraussetzung ist, dass sie die Definition der Open Source Hardware Association (OSHWA) für Open Hardware erfüllen (s.o).

Ausgehend von diesen Anforderungen wurde gemeinsam mit dem Deutschen Institut für Normung DIN und einem Kompentenznetzwerk aus knapp 40 Organisationen und Spezialisten die DIN-Spec 3105 entwickelt. Es handelt sich hierbei um den weltweit bisher einzigen, speziell für Entwicklung und technische Dokumentation von Open Hardware Projekten entwickelten international gültigen Standard. [https://journalopenhw.medium.com/din-spec-3105-explained-2cce6134c207 mehr]

=== Peer Reviews ===
Bei der Prüfung wird das Verfahren der Peer Reviews angewendet. Das bedeutet, dass die Prüfung durch mindestens drei Prüfer mit ausreichender Qualifikation und Erfahrung erfolgt, die alle Komponenten und Bauteile des Projektes detailliert prüfen. Sie untersuchen das Projekt auf Vollständigkeit der Unterlagen sowie auf offensichtliche oder versteckte Mängel.

Eine technische Klärung mit dem Projektentwickler sowie Nachbesserungen (mit entsprechender Aktualisierung der technischen Dokumentation) ist explizit vorgesehen. Hierdurch wird erreicht, dass das Know-how der Prüfer zur Qualitätsverbesserung des Projektes beitragen kann.

Hierbei wird so vorgegangen, dass ausgehend von der Stückliste des Projektes jedes Bauteil und jede Baugruppe individuell auf mögliche Mängel untersucht werden. Jede Unklarheit wird auf der Projektseite dokumentiert. Zur technischen Klärung können Grafiken, Videos, Berechnungen etc. als Nachweise hochgeladen werden. Des weiteren muss jeder Prüfer allen Bauteilen und allen Baugruppen individuell den Status “erfolgreich geprüft” (approved) zuweisen.
Erst danach wird das komplette Projekt als erfolgreich geprüft freizugeben. Mindestens zwei der Prüfer müssen das Projekt positiv bewerten, damit das Attestat nach DIN Spec 3501 erteilt werden kann.

Die gesamte Prüfprozess inklusive der technischen Klärung wird veröffentlicht, so dass alle getroffenen Entscheidungen transparent und nachvollziehbar sind.

== Die OHO- Zertifizierungsplattform ==

Die Umsetzung der DIN Spec 3105 erfolgt definitionsgemäß über eine Zertifizierungsplattform, auf der die Review Prozesse transparent und für jeden sichtbar realisiert werden.

Die Software für die Zertifizierungsplattform wurde vom OHO Team mit Unterstützung der Technischen Universität Berlin entwickelt. Im Rahmen einer Masterarbeit wurden die erforderlichen Zertifizierungsprozesse geprüft sowie teilweise mitentworfen:

=== Zusammenfassung der Abläufe ===
[[File:about sl1 a.jpg|1080px]]
[[File:about sl1 b.jpg|1080px]]
=== User Registrierung ===
[[File:about sl2 a.jpg|1080px]]
[[File:about sl2 b.jpg|1080px]]
=== Projekt anlegen ===
[[File:about sl3 a.jpg|1080px]]
=== Zertifizierung beantragen ===
[[File:about s4 a.jpg|1080px]]
=== Review ===
[[File:about sl5 a.jpg|1080px]]

Nach einer detaillierten Analyse verschiedener Software-Alternativen, die ebenfalls für die Zertifizierungsplattform hätten verwendet werden können, entschieden wir uns, die Wiki-Software Mediawiki als Basisplattform einzusetzen. Ausschlaggebenden Gründe waren unter anderem:
* MediaWiki ist eine kollaborative Software, die es ermöglicht, dass viele Personen gleichzeitig an den Inhalten der Plattform arbeiten können.
* der Quellcode MediaWiki ist unter freien Lizenzen veröffentlicht und kann entsprechend den speziellen Anforderungen des Projektes angepasst werden
* es gibt eine Vielzahl von Extensions, mit denen wichtige Funktionen, über welche die Basisversion nicht verfüg, hinzugefügt werden können
* MediaWiki hat für jede Seite eine Versionsgeschichte, was bedeutet, dass alle Änderungen lückenlos dokumentiert werden
* Media Wiki wird erfolgreich in Projekten mit hohen Userund Besucherzahlen eingesetzt, das sind keine Stabilität Probleme bekannt.

About the OHO Certification-center

2021-02-26T10:56:57Z

Robert: /* Das OHO Zertifkat – Nachbau ist möglich */

== Why does the OHO Certification Center exist ==
[[File:lathe9.png|thumb|'''The OHO certificate is a precursor to the DIN Spec 3501 certificate'']]
Previously, there were no generally accepted standards for the development and technical documentation of Open Hardware projects. This makes it difficult to replicate and further develop the projects. To solve this problem, OHO is pursuing two approaches:

* The OHO Certificate
* The DIN Spec 3501 Attestation

== The OHO certificate - rebuilding is possible ==
A prerequisite for the granting of the OHO certificate is that all documents required for the reproduction, such as construction plans and parts lists, are complete and correct. Non-standard documentation is also accepted, e.g. technical drawings made by hand, photos with dimensions, etc. The OHO certificate is only issued if the documentation is complete and correct. The OHO certificate is a preliminary stage for the DIN Spec 3501 certificate. The examination is carried out by an examiner who can prove the necessary qualification and experience.

== Echte Open Source Hardware nach der OSHWA Definition ==
Diese lautet: “Open-Source-Hardware ist Hardware, deren Baupläne öffentlich zugänglich gemacht wurden, so dass alle sie studieren, verändern, weiterverbreiten und sie sowie darauf basierende Hardware herstellen und verkaufen können”.
Die vier wesentlichen Anforderungen an Open Source Hardware sind:
* Verwenden: Jeder darf sie verwenden
* Verstehen: Alle wichtigen Informationen um Sie verstehen zu können müssen vorhanden sein
* Verbreiten: Jeder darf sie verbreiten
* Verbessern: Jeder darf sie verbessern

Weitere Anforderungen sind:

=== Dokumentation ===
Die Hardware muss mit einer alle Quelldateien einschließenden Dokumentation veröffentlicht werden und die Bearbeitung und Weiterverbreitung der Quelldateien erlauben.

=== Notwendige Software ===
Erfordert die lizenzierte Hardware Software, um richtig zu funktionieren und ihre wesentlichen Aufgaben zu erfüllen diese unter einer von der OSI (Open Source Initiative) anerkannten Open-Source-Lizenz stehen.

=== Abgewandelte Werke und Weiterverbreitung ===
Die Lizenz muss die Herstellung, die Nutzung, den Verkauf, die Weiterverbreitung sowie Veränderungen und abgewandelte Werke zulassen. Diese müssen unter den gleichen Lizenzbedingungen wie das Originalwerk weitergegeben werden.

== DIN Spec 3501 - 100% Open Source Hardware ==
[[File:DIN-Logo.png|thumb|'''[https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History Deutsches Institut für Normung Artikel DIN''']]]
=== Weblinks ===
* DIN Spec 3105-1 ([https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 hweiter])
* DIN Spec 3105-2 ([https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 weiter])

=== Kurzbeschreibung ===
Voraussetzung für die Erteilung eines Attestats nach DIN Spec 3501 ist, dass die Projekte vollständig und (möglichst) normgerecht dokumentiert sind. Eine weitere wichtige Voraussetzung ist, dass sie die Definition der Open Source Hardware Association (OSHWA) für Open Hardware erfüllen (s.o).

Ausgehend von diesen Anforderungen wurde gemeinsam mit dem Deutschen Institut für Normung DIN und einem Kompentenznetzwerk aus knapp 40 Organisationen und Spezialisten die DIN-Spec 3105 entwickelt. Es handelt sich hierbei um den weltweit bisher einzigen, speziell für Entwicklung und technische Dokumentation von Open Hardware Projekten entwickelten international gültigen Standard. [https://journalopenhw.medium.com/din-spec-3105-explained-2cce6134c207 mehr]

=== Peer Reviews ===
Bei der Prüfung wird das Verfahren der Peer Reviews angewendet. Das bedeutet, dass die Prüfung durch mindestens drei Prüfer mit ausreichender Qualifikation und Erfahrung erfolgt, die alle Komponenten und Bauteile des Projektes detailliert prüfen. Sie untersuchen das Projekt auf Vollständigkeit der Unterlagen sowie auf offensichtliche oder versteckte Mängel.

Eine technische Klärung mit dem Projektentwickler sowie Nachbesserungen (mit entsprechender Aktualisierung der technischen Dokumentation) ist explizit vorgesehen. Hierdurch wird erreicht, dass das Know-how der Prüfer zur Qualitätsverbesserung des Projektes beitragen kann.

Hierbei wird so vorgegangen, dass ausgehend von der Stückliste des Projektes jedes Bauteil und jede Baugruppe individuell auf mögliche Mängel untersucht werden. Jede Unklarheit wird auf der Projektseite dokumentiert. Zur technischen Klärung können Grafiken, Videos, Berechnungen etc. als Nachweise hochgeladen werden. Des weiteren muss jeder Prüfer allen Bauteilen und allen Baugruppen individuell den Status “erfolgreich geprüft” (approved) zuweisen.
Erst danach wird das komplette Projekt als erfolgreich geprüft freizugeben. Mindestens zwei der Prüfer müssen das Projekt positiv bewerten, damit das Attestat nach DIN Spec 3501 erteilt werden kann.

Die gesamte Prüfprozess inklusive der technischen Klärung wird veröffentlicht, so dass alle getroffenen Entscheidungen transparent und nachvollziehbar sind.

== Die OHO- Zertifizierungsplattform ==

Die Umsetzung der DIN Spec 3105 erfolgt definitionsgemäß über eine Zertifizierungsplattform, auf der die Review Prozesse transparent und für jeden sichtbar realisiert werden.

Die Software für die Zertifizierungsplattform wurde vom OHO Team mit Unterstützung der Technischen Universität Berlin entwickelt. Im Rahmen einer Masterarbeit wurden die erforderlichen Zertifizierungsprozesse geprüft sowie teilweise mitentworfen:

=== Zusammenfassung der Abläufe ===
[[File:about sl1 a.jpg|1080px]]
[[File:about sl1 b.jpg|1080px]]
=== User Registrierung ===
[[File:about sl2 a.jpg|1080px]]
[[File:about sl2 b.jpg|1080px]]
=== Projekt anlegen ===
[[File:about sl3 a.jpg|1080px]]
=== Zertifizierung beantragen ===
[[File:about s4 a.jpg|1080px]]
=== Review ===
[[File:about sl5 a.jpg|1080px]]

Nach einer detaillierten Analyse verschiedener Software-Alternativen, die ebenfalls für die Zertifizierungsplattform hätten verwendet werden können, entschieden wir uns, die Wiki-Software Mediawiki als Basisplattform einzusetzen. Ausschlaggebenden Gründe waren unter anderem:
* MediaWiki ist eine kollaborative Software, die es ermöglicht, dass viele Personen gleichzeitig an den Inhalten der Plattform arbeiten können.
* der Quellcode MediaWiki ist unter freien Lizenzen veröffentlicht und kann entsprechend den speziellen Anforderungen des Projektes angepasst werden
* es gibt eine Vielzahl von Extensions, mit denen wichtige Funktionen, über welche die Basisversion nicht verfüg, hinzugefügt werden können
* MediaWiki hat für jede Seite eine Versionsgeschichte, was bedeutet, dass alle Änderungen lückenlos dokumentiert werden
* Media Wiki wird erfolgreich in Projekten mit hohen Userund Besucherzahlen eingesetzt, das sind keine Stabilität Probleme bekannt.

About the OHO Certification-center

2021-02-26T10:52:42Z

Robert: /* Warum gibt es das OHO Certification Center */

== Why does the OHO Certification Center exist ==
[[File:lathe9.png|thumb|'''The OHO certificate is a precursor to the DIN Spec 3501 certificate'']]
Previously, there were no generally accepted standards for the development and technical documentation of Open Hardware projects. This makes it difficult to replicate and further develop the projects. To solve this problem, OHO is pursuing two approaches:

* The OHO Certificate
* The DIN Spec 3501 Attestation

== Das OHO Zertifkat – Nachbau ist möglich ==
Voraussetzung für die Erteilung de OHO Zertifikats ist, dass alle für den Nachbau erforderlichen Unterlagen wie Baupläne und Stücklisten vollständig und korrekt vorliegen. Hierbei werden auch nicht normgerechte Dokumentationen akzeptiert, also zum Beispiel per Hand gefertigte technische Zeichnungen, Fotos mit Bemaßung etc. Das OHO Zertifkat ist eine Vorstufe für das DIN Spec 3501 Attestat. Die Prüfung erfolgt durch einen Prüfer, der die notwendige Qualifikation und Erfahrung nachweisen kann.

== Echte Open Source Hardware nach der OSHWA Definition ==
Diese lautet: “Open-Source-Hardware ist Hardware, deren Baupläne öffentlich zugänglich gemacht wurden, so dass alle sie studieren, verändern, weiterverbreiten und sie sowie darauf basierende Hardware herstellen und verkaufen können”.
Die vier wesentlichen Anforderungen an Open Source Hardware sind:
* Verwenden: Jeder darf sie verwenden
* Verstehen: Alle wichtigen Informationen um Sie verstehen zu können müssen vorhanden sein
* Verbreiten: Jeder darf sie verbreiten
* Verbessern: Jeder darf sie verbessern

Weitere Anforderungen sind:

=== Dokumentation ===
Die Hardware muss mit einer alle Quelldateien einschließenden Dokumentation veröffentlicht werden und die Bearbeitung und Weiterverbreitung der Quelldateien erlauben.

=== Notwendige Software ===
Erfordert die lizenzierte Hardware Software, um richtig zu funktionieren und ihre wesentlichen Aufgaben zu erfüllen diese unter einer von der OSI (Open Source Initiative) anerkannten Open-Source-Lizenz stehen.

=== Abgewandelte Werke und Weiterverbreitung ===
Die Lizenz muss die Herstellung, die Nutzung, den Verkauf, die Weiterverbreitung sowie Veränderungen und abgewandelte Werke zulassen. Diese müssen unter den gleichen Lizenzbedingungen wie das Originalwerk weitergegeben werden.

== DIN Spec 3501 - 100% Open Source Hardware ==
[[File:DIN-Logo.png|thumb|'''[https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History Deutsches Institut für Normung Artikel DIN''']]]
=== Weblinks ===
* DIN Spec 3105-1 ([https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 hweiter])
* DIN Spec 3105-2 ([https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 weiter])

=== Kurzbeschreibung ===
Voraussetzung für die Erteilung eines Attestats nach DIN Spec 3501 ist, dass die Projekte vollständig und (möglichst) normgerecht dokumentiert sind. Eine weitere wichtige Voraussetzung ist, dass sie die Definition der Open Source Hardware Association (OSHWA) für Open Hardware erfüllen (s.o).

Ausgehend von diesen Anforderungen wurde gemeinsam mit dem Deutschen Institut für Normung DIN und einem Kompentenznetzwerk aus knapp 40 Organisationen und Spezialisten die DIN-Spec 3105 entwickelt. Es handelt sich hierbei um den weltweit bisher einzigen, speziell für Entwicklung und technische Dokumentation von Open Hardware Projekten entwickelten international gültigen Standard. [https://journalopenhw.medium.com/din-spec-3105-explained-2cce6134c207 mehr]

=== Peer Reviews ===
Bei der Prüfung wird das Verfahren der Peer Reviews angewendet. Das bedeutet, dass die Prüfung durch mindestens drei Prüfer mit ausreichender Qualifikation und Erfahrung erfolgt, die alle Komponenten und Bauteile des Projektes detailliert prüfen. Sie untersuchen das Projekt auf Vollständigkeit der Unterlagen sowie auf offensichtliche oder versteckte Mängel.

Eine technische Klärung mit dem Projektentwickler sowie Nachbesserungen (mit entsprechender Aktualisierung der technischen Dokumentation) ist explizit vorgesehen. Hierdurch wird erreicht, dass das Know-how der Prüfer zur Qualitätsverbesserung des Projektes beitragen kann.

Hierbei wird so vorgegangen, dass ausgehend von der Stückliste des Projektes jedes Bauteil und jede Baugruppe individuell auf mögliche Mängel untersucht werden. Jede Unklarheit wird auf der Projektseite dokumentiert. Zur technischen Klärung können Grafiken, Videos, Berechnungen etc. als Nachweise hochgeladen werden. Des weiteren muss jeder Prüfer allen Bauteilen und allen Baugruppen individuell den Status “erfolgreich geprüft” (approved) zuweisen.
Erst danach wird das komplette Projekt als erfolgreich geprüft freizugeben. Mindestens zwei der Prüfer müssen das Projekt positiv bewerten, damit das Attestat nach DIN Spec 3501 erteilt werden kann.

Die gesamte Prüfprozess inklusive der technischen Klärung wird veröffentlicht, so dass alle getroffenen Entscheidungen transparent und nachvollziehbar sind.

== Die OHO- Zertifizierungsplattform ==

Die Umsetzung der DIN Spec 3105 erfolgt definitionsgemäß über eine Zertifizierungsplattform, auf der die Review Prozesse transparent und für jeden sichtbar realisiert werden.

Die Software für die Zertifizierungsplattform wurde vom OHO Team mit Unterstützung der Technischen Universität Berlin entwickelt. Im Rahmen einer Masterarbeit wurden die erforderlichen Zertifizierungsprozesse geprüft sowie teilweise mitentworfen:

=== Zusammenfassung der Abläufe ===
[[File:about sl1 a.jpg|1080px]]
[[File:about sl1 b.jpg|1080px]]
=== User Registrierung ===
[[File:about sl2 a.jpg|1080px]]
[[File:about sl2 b.jpg|1080px]]
=== Projekt anlegen ===
[[File:about sl3 a.jpg|1080px]]
=== Zertifizierung beantragen ===
[[File:about s4 a.jpg|1080px]]
=== Review ===
[[File:about sl5 a.jpg|1080px]]

Nach einer detaillierten Analyse verschiedener Software-Alternativen, die ebenfalls für die Zertifizierungsplattform hätten verwendet werden können, entschieden wir uns, die Wiki-Software Mediawiki als Basisplattform einzusetzen. Ausschlaggebenden Gründe waren unter anderem:
* MediaWiki ist eine kollaborative Software, die es ermöglicht, dass viele Personen gleichzeitig an den Inhalten der Plattform arbeiten können.
* der Quellcode MediaWiki ist unter freien Lizenzen veröffentlicht und kann entsprechend den speziellen Anforderungen des Projektes angepasst werden
* es gibt eine Vielzahl von Extensions, mit denen wichtige Funktionen, über welche die Basisversion nicht verfüg, hinzugefügt werden können
* MediaWiki hat für jede Seite eine Versionsgeschichte, was bedeutet, dass alle Änderungen lückenlos dokumentiert werden
* Media Wiki wird erfolgreich in Projekten mit hohen Userund Besucherzahlen eingesetzt, das sind keine Stabilität Probleme bekannt.

Request certification for your project

2021-02-26T10:48:51Z

Robert: /* OHO Certification Application Form = */

== OHO Certification Application Form ===
The certification of a Project must be requested by the [[Certification platform#applicant|applicant]] of the Project, through the following steps:
[[File:Applicant project certificate-request.JPG|thumb|'''Certification request''']]
After uploading the [[Technical documentation|Technical documentation]], as explained in [[Certification_instructions#applicant|Instructions for certification]], go to the "Certificate" tab of the current Project and follow the indications shown:

* The following information must be present in the user profile:
** Name
** e-mail address
** City
** Country
** About (the user)
** Occupation
** Telephone
** Company or organization.
* You must have the basic data of the Project:
** Name of the project
** Description
** Open Hardware License
* You must also have entered the information corresponding to the [[Parts list]].
Finally, the [[Certification platform#applicant|applicant]] must activate the ''Request Certification'' checkbox, starting the [[Certification processes]], so you will be contacted promptly.

Request certification for your project

2021-02-26T10:47:49Z

Robert: /* Formulario para Solicitud de certificación en OHO */

== OHO Certification Application Form ===
The certification of a Project must be requested by the [[Certification platform#applicant|applicant]] of the Project, through the following steps:
[[File:Applicant project certificate-request.JPG|thumb|'''Certification request''']]]]
After uploading the [[Technical documentation|Technical documentation]], as explained in [[Certification_instructions#applicant|Instructions for certification]], go to the "Certificate" tab of the current Project and follow the indications shown:

* The following information must be present in the user profile:
** Name
** e-mail address
** City
** Country
** About (the user)
** Occupation
** Telephone
** Company or organization.
* You must have the basic data of the Project:
** Name of the project
** Description
** Open Hardware License
* You must also have entered the information corresponding to the [[Parts list]].
Finally, the [[Certification platform#applicant|applicant]] must activate the ''Request Certification'' checkbox, starting the [[Certification processes]], so you will be contacted promptly.

About the OHO CAD Center

2021-02-26T10:39:02Z

Robert: /* Was ist der Nutzen des CAD Centers? */

[[File:Crowd2.png|thumb]]
__TOC__
== Why does the CAD Centre exist ==

There are thousands of great sustainable technology projects on the web. However, if you want to copy them, you almost always find that the documentation is insufficient, i.e. there are no or only incomplete plans or parts lists.

There is a simple reason for this: the developers of the projects either do not have enough time or do not have enough knowledge to document them properly. The creation of these documents is time-consuming and requires specialized knowledge of CAD systems.

Interested users have no possibility of rebuilding the projects, or if they do try, there is a great risk that errors will creep in during the recreation.

== How the CAD Centre works ==
[[File:Planes2.png|thumb]]

=== Step 1 ===

Either the project developers apply for certification of their projects on their own or the OHO team selects Do it Yourself or Open Hardware projects.
=== Step 2 ===

In the next step, the projects are checked to see whether they meet the requirements for certification, e.g.
* whether the solutions correspond to the current state of technology
* whether they have specific weak points or risks
* whether special materials, components or processes are required for their manufacture
* Including other criteria

=== Step 3 ===

After a positive preliminary check, it is examined whether the existing project documents (construction plans, parts lists) are sufficient to reproduce or further develop them without any problems. If this is not the case, the engineers of the OHO team use modern CAD systems to create all the files and documents required for standard-compliant technical documentation. The project developers are closely involved in this process to ensure correct documentation of the projects.

== What is the benefit of the CAD Centre? ==

* Projects are closely reviewed by experienced specialists.
* Projects with weak points are either improved or sorted out.
* The selected projects receive technical documentation in accordance with international standards.
* They can be rebuilt or further developed worldwide.

About the OHO CAD Center

2021-02-26T10:37:06Z

Robert: /* Was macht das CAD Center */

[[File:Crowd2.png|thumb]]
__TOC__
== Why does the CAD Centre exist ==

There are thousands of great sustainable technology projects on the web. However, if you want to copy them, you almost always find that the documentation is insufficient, i.e. there are no or only incomplete plans or parts lists.

There is a simple reason for this: the developers of the projects either do not have enough time or do not have enough knowledge to document them properly. The creation of these documents is time-consuming and requires specialized knowledge of CAD systems.

Interested users have no possibility of rebuilding the projects, or if they do try, there is a great risk that errors will creep in during the recreation.

== How the CAD Centre works ==
[[File:Planes2.png|thumb]]

=== Step 1 ===

Either the project developers apply for certification of their projects on their own or the OHO team selects Do it Yourself or Open Hardware projects.
=== Step 2 ===

In the next step, the projects are checked to see whether they meet the requirements for certification, e.g.
* whether the solutions correspond to the current state of technology
* whether they have specific weak points or risks
* whether special materials, components or processes are required for their manufacture
* Including other criteria

=== Step 3 ===

After a positive preliminary check, it is examined whether the existing project documents (construction plans, parts lists) are sufficient to reproduce or further develop them without any problems. If this is not the case, the engineers of the OHO team use modern CAD systems to create all the files and documents required for standard-compliant technical documentation. The project developers are closely involved in this process to ensure correct documentation of the projects.

== Was ist der Nutzen des CAD Centers? ==

* Die Projekte werden durch erfahrene Spezialisten genau überprüft.
* Projekte mit Schwachstellen werden entweder verbessert oder aussortiert.
* Die ausgewählten Projekte erhalten eine den internationalen Standards entsprechende technische Dokumentation.
* Sie können weltweit nachgebaut oder weiterentwickelt werden.

About the OHO CAD Center

2021-02-26T10:27:36Z

Robert: /* Warum gibt es das CAD Center */

[[File:Crowd2.png|thumb]]
__TOC__
== Why does the CAD Centre exist ==

There are thousands of great sustainable technology projects on the web. However, if you want to copy them, you almost always find that the documentation is insufficient, i.e. there are no or only incomplete plans or parts lists.

There is a simple reason for this: the developers of the projects either do not have enough time or do not have enough knowledge to document them properly. The creation of these documents is time-consuming and requires specialized knowledge of CAD systems.

Interested users have no possibility of rebuilding the projects, or if they do try, there is a great risk that errors will creep in during the recreation.

== Was macht das CAD Center ==
[[File:Planes2.png|thumb]]

=== Schritt 1 ===

Entweder die Projektentwickler beantragen von sich aus die Zertifizierung ihrer Projekte. Oder das OHO Team wählt Do it Yourself oder Open Hardware Projekte aus.

=== Schritt 2 ===

Im nächsten Schritt werden die Projekte daraufhin überprüft, ob sie die Voraussetzungen für die Zertifizierung erfüllen, z.B.
* ob es sich um Lösungen handelt, die dem aktuellen Stand der Technik entsprechen
* ob sie bestimmte Schwachstellen oder Risiken aufweisen
* ob zur Herstellung Spezialmaterialien, -komponenten oder -verfahren benötigt werden
* u.a. Kriterien

=== Schritt 3 ===

Nach positiver Vorprüfung wird untersucht, ob die vorhandenen Projektunterlagen (Baupläne, Stücklisten) ausreichend sind, um sie problemlos nachzubauen oder weiter zu entwickeln. Wen dies nicht der Fall ist, erstellen die Ingenieure des OHO Teams mit modernen CAD Systemen alle für eine normgerechte technische Dokumentation erforderlichen Dateien und Unterlagen. Bei diesem Prozess sind die Projektentwickler eng mit einbezogen, um eine korrekte Dokumentation der Projekte zu gewährleisten.

== Was ist der Nutzen des CAD Centers? ==

* Die Projekte werden durch erfahrene Spezialisten genau überprüft.
* Projekte mit Schwachstellen werden entweder verbessert oder aussortiert.
* Die ausgewählten Projekte erhalten eine den internationalen Standards entsprechende technische Dokumentation.
* Sie können weltweit nachgebaut oder weiterentwickelt werden.

Request cad plans for your project

2021-02-26T10:22:28Z

Robert: /* OHO Community */

== Request CAD plans for your project ==

[[File:planes1.png|thumb|'''We create your CAD drawings'']]

More than 95% of all Do it Yourself or Open Hardware projects are published without blueprints and parts lists. Interested persons cannot rebuild or develop them at all or can be done with great difficulties only.
Therefore OHO offers project developers in the field of sustainable development to create standardized CAD files, construction plans, and parts lists for their projects.
Do you have an interesting Open Hardware or Do it Yourself project in the field of sustainable development?
 
 
 
 
 
 

== OHO Community ==

A community whose goal is to help other people to rebuild, develop or modify their projects?
Would you like to create a community of open hardware developers, similar to open-source software, who exchange ideas and cooperate, and together achieve many times what individual developers could ever achieve alone?

=== Then OHO is the right place for you - become a member of the OHO community and receive exciting benefits ===

* Free creation of CAD files and PDF plans
* Free creation of videos with 3D animations
* Free certification of your projects

=== Registration at OHO! ===

Due to a high number of spam registrations, please send us a short mail with your desired alias and we will create your user account: [[info@oho.wiki]]

Request cad plans for your project

2021-02-26T10:12:24Z

Robert: /* Beantrage CAD-Pläne für dein Projekt */

== Request CAD plans for your project ==

[[File:planes1.png|thumb|'''We create your CAD drawings'']]

More than 95% of all Do it Yourself or Open Hardware projects are published without blueprints and parts lists. Interested persons cannot rebuild or develop them at all or can be done with great difficulties only.
Therefore OHO offers project developers in the field of sustainable development to create standardized CAD files, construction plans, and parts lists for their projects.
Do you have an interesting Open Hardware or Do it Yourself project in the field of sustainable development?
 
 
 
 
 
 

== OHO Community ==

Möchtest anderen Menschen dabei helfen, deine Projekte nachzubauen, sie weiterzuentwickeln oder sie zu verändern?

Möchtest du, dass ähnlich wie bei Open Source Software eine Community aus Open Hardware Entwicklern entsteht, die sich austauscht und kooperiert, und gemeinsam ein Vielfaches von dem erreicht, was einzelne Entwickler jemals alleine erreichen könnten?

=== Dann bist du richtig bei OHO - werde Mitglied der OHO Community und erhalte spannende Vorteile ===

* Kostenfreie Erstellung von CAD-Dateien und PDF-Plänen
* Kostenfreie Erstellung von Videos mit 3D Animationen
* Kostenfreie Zertifizierung deiner Projekte

=== Registriere dich auf OHO! ===

Aufgrund einer hohen Anzahl von Spam-Registrierungen, sende uns bitte eine kurze Mail mit deinem gewünschten Alias und wir werden dein Benutzerkonto anlegen: [[info@oho.wiki]]

Upload your project

2021-02-26T09:52:56Z

Robert: /* Would you like to upload your project to OHO? */

[[File:Lathe3.jpg|thumb|]]
== Would you like to register on OHO? ==
Only registered users can upload their projects. Due to a high number of spam registrations, please send us a short mail with your desired username and we will create your user account: [[info@oho.wiki]].

== Would you like to upload your project to OHO? ==
The following two options are available for uploading your project to OHO:
* Go to https://en.oho.wiki/wiki/Special:FormEdit/Project and enter your project data.
* Send us your project data and project files and it will be uploaded for you: [[info@oho.wiki]].

Upload your project

2021-02-26T09:52:00Z

Robert: /* Would you like to register on OHO? */

[[File:Lathe3.jpg|thumb|]]
== Would you like to register on OHO? ==
Only registered users can upload their projects. Due to a high number of spam registrations, please send us a short mail with your desired username and we will create your user account: [[info@oho.wiki]].

== Would you like to upload your project to OHO? ==
The following two options are available for uploading your project to OHO:
* Go to https://en.oho.wiki/wiki/Special:FormEdit/Project and enter your project data.
* Email us your project data and project files and it will be uploaded for you: [[info@oho.wiki]].

Upload your project

2021-02-26T09:50:32Z

Robert: /* Would you like to register on OHO? */

[[File:Lathe3.jpg|thumb|]]
== Would you like to register on OHO? ==
Only registered users can upload their projects. Due to a high number of spam registrations, please send us a short mail with your desired username and we will create your user account: [info@oho.wiki].

== Would you like to upload your project to OHO? ==
The following two options are available for uploading your project to OHO:
* Go to https://en.oho.wiki/wiki/Special:FormEdit/Project and enter your project data.
* Email us your project data and project files and it will be uploaded for you: [[info@oho.wiki]].

Upload your project

2021-02-26T09:50:08Z

Robert: /* Möchtest du dein Projekt auf OHO hochladen? */

[[File:Lathe3.jpg|thumb|]]
== Would you like to register on OHO? ==
Only registered users can upload their projects. Due to a high number of spam registrations, please send us a short mail with your desired username and we will create your user account: [[info@oho.wiki]].

== Would you like to upload your project to OHO? ==
The following two options are available for uploading your project to OHO:
* Go to https://en.oho.wiki/wiki/Special:FormEdit/Project and enter your project data.
* Email us your project data and project files and it will be uploaded for you: [[info@oho.wiki]].

Upload your project

2021-02-26T09:47:34Z

Robert: /* Möchtest du dich auf OHO registrieren? */

[[File:Lathe3.jpg|thumb|]]
== Would you like to register on OHO? ==
Only registered users can upload their projects. Due to a high number of spam registrations, please send us a short mail with your desired username and we will create your user account: [[info@oho.wiki]].

== Möchtest du dein Projekt auf OHO hochladen? ==
Es gibt zwei Möglichkeiten, dein Projekt auf OHO hochzuladen:
* Gehe auf https://en.oho.wiki/wiki/Special:FormEdit/Project und gebe deine Projektdaten ein.
* Sende uns deine Projektdaten und Projektdateien und wir werden laden sie für dich hoch: [[info@oho.wiki]].

About the OHO Search Engine

2021-02-26T09:45:09Z

Robert: /* Was ist der Nutzen der OHO Search Engine? */

==Why the OHO search engine exists==

Open Hardware and Do it Yourself projects are huge treasures of valuable technical knowledge. Hundreds of thousands of people worldwide have successfully developed technical solutions for a wide range of applications, and more are being created every day. Most of these are technical solutions that can be produced with relatively simple technical resources in small workshops.

Potentially, this technical knowledge is free because it is hardly protected by patents or other regulations. However, the vast majority of this knowledge is not or insufficiently documented. In almost all cases, there are no plans, parts lists, etc., which are necessary for rebuilding or further developing a project. There are many publications, especially on the internet, but these publications are often on small and anonymous websites and are only available in a single language.

This technical knowledge could have a huge impact, especially on small businesses, start-ups and individuals. It could enable a more localized and regional kind of technical and economic development. It could enable sustainable development from an ecological, social, and economic point of view. With OHO, we would like to contribute to this.

==What does the OHO Search Engine do==

The OHO Search Engine crawls, an entire web for a variety of search keywords and their combinations and is thus able to find even small "hidden" websites. It searches specifically for Do it Yourself and Open Hardware projects.
In the current beta version, the search engine is available in three languages: English, German and Spanish. Further language versions are in preparation.
In addition, developers can upload their projects directly to OHO. (more) <link to https://en.oho.wiki/wiki/Upload_your_project>

The search results found go through a partly automatic and partly manual quality control. They are listed, classified, arranged in categories, and displayed with thumbnails and short descriptions. Currently, search results from the following main categories can be found on OHO
* Computers
* Electronics
* Renewable Energies
* Health care
* Trade
* Industry
* Agriculture
* Forestry
* Mobility
* Logistics
* Environmental technology

==What is the benefit of the OHO Search Engine?==

OHO Search Engine is the only multilingual search engine specialized in sustainable Open Hardware and Do it Yourself projects. The visitor can browse through the categories and can also search for results with specific properties (for example "has blueprints" or "is published under free licenses" etc.). Currently, the OHO Search Engine offers about 12,000 search results in more than 500 categories.

About the OHO Search Engine

2021-02-26T09:40:01Z

Robert: /* Was macht die OHO Suchmaschine */

==Why the OHO search engine exists==

Open Hardware and Do it Yourself projects are huge treasures of valuable technical knowledge. Hundreds of thousands of people worldwide have successfully developed technical solutions for a wide range of applications, and more are being created every day. Most of these are technical solutions that can be produced with relatively simple technical resources in small workshops.

Potentially, this technical knowledge is free because it is hardly protected by patents or other regulations. However, the vast majority of this knowledge is not or insufficiently documented. In almost all cases, there are no plans, parts lists, etc., which are necessary for rebuilding or further developing a project. There are many publications, especially on the internet, but these publications are often on small and anonymous websites and are only available in a single language.

This technical knowledge could have a huge impact, especially on small businesses, start-ups and individuals. It could enable a more localized and regional kind of technical and economic development. It could enable sustainable development from an ecological, social, and economic point of view. With OHO, we would like to contribute to this.

==What does the OHO Search Engine do==

The OHO Search Engine crawls, an entire web for a variety of search keywords and their combinations and is thus able to find even small "hidden" websites. It searches specifically for Do it Yourself and Open Hardware projects.
In the current beta version, the search engine is available in three languages: English, German and Spanish. Further language versions are in preparation.
In addition, developers can upload their projects directly to OHO. (more) <link to https://en.oho.wiki/wiki/Upload_your_project>

The search results found go through a partly automatic and partly manual quality control. They are listed, classified, arranged in categories, and displayed with thumbnails and short descriptions. Currently, search results from the following main categories can be found on OHO
* Computers
* Electronics
* Renewable Energies
* Health care
* Trade
* Industry
* Agriculture
* Forestry
* Mobility
* Logistics
* Environmental technology

==Was ist der Nutzen der OHO Search Engine?==

OHO Search Engine ist die einzige mehrsprachige Suchmaschine, welche auf nachhaltige Open Hardware und Do it Yourself Projekte spezialisiert ist. Der Besucher hat die Möglichkeit nach Suchbegriffen zu suchen, sich durch die Kategorien durchzuklicken oder Ergebnisse mit bestimmten Eigenschaften zu suchen (zum Beispiel „verfügt über Baupläne“ oder „ist unter freien Lizenzen veröffentlicht“ etc.). Aktuell bietet die OHO Search Engine ca. 12.000 Suchergebnisse in mehr als 500 Kategorien.

About the OHO Search Engine

2021-02-26T09:31:52Z

Robert: /* Warum gibt es die OHO Suchmaschine */

==Why the OHO search engine exists==

Open Hardware and Do it Yourself projects are huge treasures of valuable technical knowledge. Hundreds of thousands of people worldwide have successfully developed technical solutions for a wide range of applications, and more are being created every day. Most of these are technical solutions that can be produced with relatively simple technical resources in small workshops.

Potentially, this technical knowledge is free because it is hardly protected by patents or other regulations. However, the vast majority of this knowledge is not or insufficiently documented. In almost all cases, there are no plans, parts lists, etc., which are necessary for rebuilding or further developing a project. There are many publications, especially on the internet, but these publications are often on small and anonymous websites and are only available in a single language.

This technical knowledge could have a huge impact, especially on small businesses, start-ups and individuals. It could enable a more localized and regional kind of technical and economic development. It could enable sustainable development from an ecological, social, and economic point of view. With OHO, we would like to contribute to this.

==Was macht die OHO Suchmaschine==

Die OHO Search Engine crawlt das komplette Web nach einer Vielzahl von Suchbegriffen und Kombinationen aus Suchbegriffen und ist so in der Lage auch kleine „versteckte“ Websites zu finden. Hierbei wird gezielt nach Do it Yourself und Open Hardware Projekten gesucht.
In der aktuellen Beta-Version ist die Suchmaschine in drei Sprachen verfügbar: Englisch, Deutsch und Spanisch. Weitere Sprachversionen sind in Vorbereitung.
Außerdem können Entwickler ihre Projekte direkt auf OHO hochladen. (weiter) <link to https://en.oho.wiki/wiki/Upload_your_project>

Die gefundenen Suchergebnisse durchlaufen eine teils automatische und teils manuelle Qualitätskontrolle. Sie werden indiziert, klassifiziert, in Kategorien eingeteilt und mit Vorschaubildern und Kurzbeschreibungen angezeigt. Aktuell befinden sich Suchergebnisse aus folgenden Hauptkategorien auf OHO
* Computer, Elektronik
* Erneuerbare Energien‎
* Gesundheit‎
* Gewerbe, Industrie
* Landwirtschaft, Forst
* Mobilität, Logistik
* Umwelttechnik ‎

==Was ist der Nutzen der OHO Search Engine?==

OHO Search Engine ist die einzige mehrsprachige Suchmaschine, welche auf nachhaltige Open Hardware und Do it Yourself Projekte spezialisiert ist. Der Besucher hat die Möglichkeit nach Suchbegriffen zu suchen, sich durch die Kategorien durchzuklicken oder Ergebnisse mit bestimmten Eigenschaften zu suchen (zum Beispiel „verfügt über Baupläne“ oder „ist unter freien Lizenzen veröffentlicht“ etc.). Aktuell bietet die OHO Search Engine ca. 12.000 Suchergebnisse in mehr als 500 Kategorien.

Certification instructions

2021-02-23T14:52:25Z

Robert: /* Designation of the Conformity Assessment Body (CAB) */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designation of the Conformity Assessment Body (CAB) ===
[[File:user rights6.jpg|thumb|'''Assignment of Assessor role to a user''']]
The [[Certifcation platform#cab-team|CAB-team]] must be designated and activated, once the [[Certifcation platform#applicant|Applicant]] performs the [[Request certification for your project]] of the Project, as this team must participate, among others, in the designation of the [[Certifcation platform#reviewers|Reviewers]].

For each member of the [[Certifcation platform#cab-team|CAB-team]], the following must be fulfilled:
*If the [[Certifcation platform#cab-team|Evaluator]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Enter the user's name and access their role information, under ''Load user groups''.
** Activate the ''certification_body'' checkbox.
** Save the changes in ''Save user groups''.
* The [[Certifcation platform#coordinator|Coordinator]] must contact each member of the [[Certifcation platform#cab-team|CAB-team]], to notify them about their responsibilities as Assessor and thus give continuity to the certification.

<div id="reviewers-designation"></div>

=== Designation of Reviewers ===
[[File:user_rights2.jpg|thumb|'''Assigning a Reviewer role to a user''']]
[[File:Certification manager.JPG|thumb|'''Designation of Reviewer to the Project''']]
* If the [[Certifcation platform#reviewers|Reviewers|Reviewer]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights]]
** Enter the user's name and access their role information, under ''Load user groups''.
Activate the checkbox ''certification_reviewer'' ** Save the changes in ''Save user groups''.
Save the changes in ''Save user groups'' ** Save the changes in ''Save user groups''.
* Go to the [[#project_page|Project page]], action ''Edit'', tab ''Certification Manager''.
* In the ''Reviewer 1 to 3'' fields, select the user that will be [[Certifcation platform#reviewers|Reviewer]].
** Save the changes in ''Save page''.
 
 
 
 
 
 
 
 
 
 
 

=== Approval of the Certification Document ===
After the [[Certifcation platform#cab-team|CAB-team]], has issued the [[Certification processes#obs|Certification Document]], the [[Certifcation platform#coordinator|Coordinator]] must carry out the respective steps for the approval of this document, which includes:
* Approval and signature of Authorities by OHO.
* Approval and signature of Authorities by the external certification body for validation according to [[DIN Spec 3105]].

== Reviewers ==
The [[Certifcation platform#reviewers|Reviewers]] have the task to technically analyse all the Project documentation, for which, they must have gone through the [[#sing-up|registration process]] in the same way as for the [[Certifcation platform#applicant|Applicant]]. It must also have the role of ''certificarion_reviewer'', as indicated in [[#reviewers-designation|Reviewer designation]].

Each [[Certifcation platform#reviewers|Reviewer]] must comply with the aspects mentioned below:

=== Analysis of Technical Documentation ===
* Enter the [[#project_page|project page]].
* Analyse all available information, especially the assembly instructions, which includes:
** Correct references between parts in the [[Technical drawings]] and the [[Parts list]] .
** Well explained manufacturing processes for special parts or joining means.
** Consistency in the information shown, it must make sense in technical and [[https://es.wikipedia.org/wiki/Hardware_libre Open Hardware]] terms.

=== Release of non-conformities ===
[[File:Project comments.JPG|thumb|'''Comments in a project''']]
[[File:Project action required.JPG|thumb|'''Item marked as ''Action required''''']]
On the [[#project_page|project page]], comments on technical aspects can be made, these comments are the channel in which non-conformities are issued.

A comment or non-conformity must be issued in the following cases:

* Information is missing in order to be able to classify or recognise a part or assembly.
* Information about a supplier is missing (links to websites tend to be modified).
* Missing information on a purchased part, in order to be able to locate it in current markets.
* Missing measurements or other specifications in the [[Technical drawings]].
* Lack of coherence in the specifications, with respect to the assembly of the parts.
* Missing fields in the [[#part_list|Parts list]].
* Depending on the type of assembly:
** There must exist for each part, a [[Technical drawings|plan in PDF]] and its respective [[CAD files|CAD file]] (the latter, with the purpose of being able to review the 3D information in other CAD systems different from the one that has generated the parts).
** The 3D printing parts must be accompanied by their STL file, in addition to their [[Technical drawings|PDF drawing]] and their [[CAD files|CAD file]].
** For printed circuit boards (PCB), the addresses of their components must be included.
* In case of confusing information or obvious mistakes, a friendly comment should be left, pointing out the mistake in the corresponding item.
* In case of problems regarding the Project in general, there is an extra field in the [[#part_list|Parts list]], where comments can be added
* Those items that require some correction by the [[Certifcation platform#applicant|Applicant]], must be marked as ''Action required'', in the [[#project_page|Project page]], action ''Edit'', tab ''Part list''.
* This process can be repeated as long as there are comments or non-conformities with corrections to be made and not all the items of the [[#part_list|Part list]] are approved, through which, communication with the [[Certifcation platform#applicant|Applicant]] must always be maintained.
=== Project Approval ===
[[File:Project aproved.JPG|thumb|'''Item marked as ''Approved''''']]
After all non-conformities have been resolved, you should:
* Mark each item in the [[#part_list|Part list]] as ''Approved'', on the [[#project_page|Project page]], action ''Edit'', tab ''Part list''.
* Add a final comment including ''OK, FINISHED''.
* Notify the [[Certifcation platform#coordinator|Coordinator|Coordinator]], about the Project Approval.

== Conformity Assessment Board (CAB Team) ==
The [[Certifcation platform#cab-team|CAB-team]] has access to the contact details of the [[Certifcation platform#reviewers|Reviewers]] and the [[Certifcation platform#applicant|Applicant]], and can always intervene in the resolution of non-conformities and obtain direct information for the issuing of the [[Certification processes#obs|Certification document]].
=== Validation of Applicant and Reviewers information ===
Some of the activities of the [[Certifcation platform#cab-team|CAB-team]], include:
* Verify some formalities of the Project.
* In conjunction with the [[Certifcation platform#coordinator|Coordinator]], it opens the [[Certification processes]] as it participates in the [[#reviewers-designation|Reviewers-designation]].
=== Issuance of the Certification Document ===
Once the [[Certifcation platform#applicant|Applicant]] has entered all [[#docs-upload|Technical documentation]], at least twice, the [[Certifcation platform#cab-team|CAB-team]] can issue a certification validating compliance with [[DIN Spec 3105]]. This completes the review process, which may be opened if:
* Any person complains to the [[Certifcation platform#cab-team|CAB-team]] about:
** The publication of the documentation is no longer accessible in whole or in part.
** The license terms have been modified and no longer comply with the requirements of [[DIN Spec 3105]].
** Any relevant information has been altered or removed from the [[Certifcation platform]].
* Taking into account the importance of the submitted complaints, the [[Certifcation platform#cab-team|CAB-team]] can cancel the ongoing certification and reopen the [[Certification processes]] a new revision of the [[Technical documentation]].
* The [[Certifcation platform#applicant|Applicant]] can upload again documentation that has already been certified and approved, in this case, it does not need to be reviewed again.

Certification instructions

2021-02-23T14:52:04Z

Robert: /* Equipo de evaluación de conformidad (CAB) */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designation of the Conformity Assessment Body (CAB) ===
[[File:user rights6.jpg|thumb|'''Assignment of Assessor role to a user''']]]]
The [[Certifcation platform#cab-team|CAB-team]] must be designated and activated, once the [[Certifcation platform#applicant|Applicant]] performs the [[Request certification for your project]] of the Project, as this team must participate, among others, in the designation of the [[Certifcation platform#reviewers|Reviewers]].

For each member of the [[Certifcation platform#cab-team|CAB-team]], the following must be fulfilled:
*If the [[Certifcation platform#cab-team|Evaluator]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Enter the user's name and access their role information, under ''Load user groups''.
** Activate the ''certification_body'' checkbox.
** Save the changes in ''Save user groups''.
* The [[Certifcation platform#coordinator|Coordinator]] must contact each member of the [[Certifcation platform#cab-team|CAB-team]], to notify them about their responsibilities as Assessor and thus give continuity to the certification.

<div id="reviewers-designation"></div>

=== Designation of Reviewers ===
[[File:user_rights2.jpg|thumb|'''Assigning a Reviewer role to a user''']]
[[File:Certification manager.JPG|thumb|'''Designation of Reviewer to the Project''']]
* If the [[Certifcation platform#reviewers|Reviewers|Reviewer]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights]]
** Enter the user's name and access their role information, under ''Load user groups''.
Activate the checkbox ''certification_reviewer'' ** Save the changes in ''Save user groups''.
Save the changes in ''Save user groups'' ** Save the changes in ''Save user groups''.
* Go to the [[#project_page|Project page]], action ''Edit'', tab ''Certification Manager''.
* In the ''Reviewer 1 to 3'' fields, select the user that will be [[Certifcation platform#reviewers|Reviewer]].
** Save the changes in ''Save page''.
 
 
 
 
 
 
 
 
 
 
 

=== Approval of the Certification Document ===
After the [[Certifcation platform#cab-team|CAB-team]], has issued the [[Certification processes#obs|Certification Document]], the [[Certifcation platform#coordinator|Coordinator]] must carry out the respective steps for the approval of this document, which includes:
* Approval and signature of Authorities by OHO.
* Approval and signature of Authorities by the external certification body for validation according to [[DIN Spec 3105]].

== Reviewers ==
The [[Certifcation platform#reviewers|Reviewers]] have the task to technically analyse all the Project documentation, for which, they must have gone through the [[#sing-up|registration process]] in the same way as for the [[Certifcation platform#applicant|Applicant]]. It must also have the role of ''certificarion_reviewer'', as indicated in [[#reviewers-designation|Reviewer designation]].

Each [[Certifcation platform#reviewers|Reviewer]] must comply with the aspects mentioned below:

=== Analysis of Technical Documentation ===
* Enter the [[#project_page|project page]].
* Analyse all available information, especially the assembly instructions, which includes:
** Correct references between parts in the [[Technical drawings]] and the [[Parts list]] .
** Well explained manufacturing processes for special parts or joining means.
** Consistency in the information shown, it must make sense in technical and [[https://es.wikipedia.org/wiki/Hardware_libre Open Hardware]] terms.

=== Release of non-conformities ===
[[File:Project comments.JPG|thumb|'''Comments in a project''']]
[[File:Project action required.JPG|thumb|'''Item marked as ''Action required''''']]
On the [[#project_page|project page]], comments on technical aspects can be made, these comments are the channel in which non-conformities are issued.

A comment or non-conformity must be issued in the following cases:

* Information is missing in order to be able to classify or recognise a part or assembly.
* Information about a supplier is missing (links to websites tend to be modified).
* Missing information on a purchased part, in order to be able to locate it in current markets.
* Missing measurements or other specifications in the [[Technical drawings]].
* Lack of coherence in the specifications, with respect to the assembly of the parts.
* Missing fields in the [[#part_list|Parts list]].
* Depending on the type of assembly:
** There must exist for each part, a [[Technical drawings|plan in PDF]] and its respective [[CAD files|CAD file]] (the latter, with the purpose of being able to review the 3D information in other CAD systems different from the one that has generated the parts).
** The 3D printing parts must be accompanied by their STL file, in addition to their [[Technical drawings|PDF drawing]] and their [[CAD files|CAD file]].
** For printed circuit boards (PCB), the addresses of their components must be included.
* In case of confusing information or obvious mistakes, a friendly comment should be left, pointing out the mistake in the corresponding item.
* In case of problems regarding the Project in general, there is an extra field in the [[#part_list|Parts list]], where comments can be added
* Those items that require some correction by the [[Certifcation platform#applicant|Applicant]], must be marked as ''Action required'', in the [[#project_page|Project page]], action ''Edit'', tab ''Part list''.
* This process can be repeated as long as there are comments or non-conformities with corrections to be made and not all the items of the [[#part_list|Part list]] are approved, through which, communication with the [[Certifcation platform#applicant|Applicant]] must always be maintained.
=== Project Approval ===
[[File:Project aproved.JPG|thumb|'''Item marked as ''Approved''''']]
After all non-conformities have been resolved, you should:
* Mark each item in the [[#part_list|Part list]] as ''Approved'', on the [[#project_page|Project page]], action ''Edit'', tab ''Part list''.
* Add a final comment including ''OK, FINISHED''.
* Notify the [[Certifcation platform#coordinator|Coordinator|Coordinator]], about the Project Approval.

== Conformity Assessment Board (CAB Team) ==
The [[Certifcation platform#cab-team|CAB-team]] has access to the contact details of the [[Certifcation platform#reviewers|Reviewers]] and the [[Certifcation platform#applicant|Applicant]], and can always intervene in the resolution of non-conformities and obtain direct information for the issuing of the [[Certification processes#obs|Certification document]].
=== Validation of Applicant and Reviewers information ===
Some of the activities of the [[Certifcation platform#cab-team|CAB-team]], include:
* Verify some formalities of the Project.
* In conjunction with the [[Certifcation platform#coordinator|Coordinator]], it opens the [[Certification processes]] as it participates in the [[#reviewers-designation|Reviewers-designation]].
=== Issuance of the Certification Document ===
Once the [[Certifcation platform#applicant|Applicant]] has entered all [[#docs-upload|Technical documentation]], at least twice, the [[Certifcation platform#cab-team|CAB-team]] can issue a certification validating compliance with [[DIN Spec 3105]]. This completes the review process, which may be opened if:
* Any person complains to the [[Certifcation platform#cab-team|CAB-team]] about:
** The publication of the documentation is no longer accessible in whole or in part.
** The license terms have been modified and no longer comply with the requirements of [[DIN Spec 3105]].
** Any relevant information has been altered or removed from the [[Certifcation platform]].
* Taking into account the importance of the submitted complaints, the [[Certifcation platform#cab-team|CAB-team]] can cancel the ongoing certification and reopen the [[Certification processes]] a new revision of the [[Technical documentation]].
* The [[Certifcation platform#applicant|Applicant]] can upload again documentation that has already been certified and approved, in this case, it does not need to be reviewed again.

Certification instructions

2021-02-23T14:48:10Z

Robert: /* Revisores */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designation of the Conformity Assessment Body (CAB) ===
[[File:user rights6.jpg|thumb|'''Assignment of Assessor role to a user''']]]]
The [[Certifcation platform#cab-team|CAB-team]] must be designated and activated, once the [[Certifcation platform#applicant|Applicant]] performs the [[Request certification for your project]] of the Project, as this team must participate, among others, in the designation of the [[Certifcation platform#reviewers|Reviewers]].

For each member of the [[Certifcation platform#cab-team|CAB-team]], the following must be fulfilled:
*If the [[Certifcation platform#cab-team|Evaluator]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Enter the user's name and access their role information, under ''Load user groups''.
** Activate the ''certification_body'' checkbox.
** Save the changes in ''Save user groups''.
* The [[Certifcation platform#coordinator|Coordinator]] must contact each member of the [[Certifcation platform#cab-team|CAB-team]], to notify them about their responsibilities as Assessor and thus give continuity to the certification.

<div id="reviewers-designation"></div>

=== Designation of Reviewers ===
[[File:user_rights2.jpg|thumb|'''Assigning a Reviewer role to a user''']]
[[File:Certification manager.JPG|thumb|'''Designation of Reviewer to the Project''']]
* If the [[Certifcation platform#reviewers|Reviewers|Reviewer]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights]]
** Enter the user's name and access their role information, under ''Load user groups''.
Activate the checkbox ''certification_reviewer'' ** Save the changes in ''Save user groups''.
Save the changes in ''Save user groups'' ** Save the changes in ''Save user groups''.
* Go to the [[#project_page|Project page]], action ''Edit'', tab ''Certification Manager''.
* In the ''Reviewer 1 to 3'' fields, select the user that will be [[Certifcation platform#reviewers|Reviewer]].
** Save the changes in ''Save page''.
 
 
 
 
 
 
 
 
 
 
 

=== Approval of the Certification Document ===
After the [[Certifcation platform#cab-team|CAB-team]], has issued the [[Certification processes#obs|Certification Document]], the [[Certifcation platform#coordinator|Coordinator]] must carry out the respective steps for the approval of this document, which includes:
* Approval and signature of Authorities by OHO.
* Approval and signature of Authorities by the external certification body for validation according to [[DIN Spec 3105]].

== Reviewers ==
The [[Certifcation platform#reviewers|Reviewers]] have the task to technically analyse all the Project documentation, for which, they must have gone through the [[#sing-up|registration process]] in the same way as for the [[Certifcation platform#applicant|Applicant]]. It must also have the role of ''certificarion_reviewer'', as indicated in [[#reviewers-designation|Reviewer designation]].

Each [[Certifcation platform#reviewers|Reviewer]] must comply with the aspects mentioned below:

=== Analysis of Technical Documentation ===
* Enter the [[#project_page|project page]].
* Analyse all available information, especially the assembly instructions, which includes:
** Correct references between parts in the [[Technical drawings]] and the [[Parts list]] .
** Well explained manufacturing processes for special parts or joining means.
** Consistency in the information shown, it must make sense in technical and [[https://es.wikipedia.org/wiki/Hardware_libre Open Hardware]] terms.

=== Release of non-conformities ===
[[File:Project comments.JPG|thumb|'''Comments in a project''']]
[[File:Project action required.JPG|thumb|'''Item marked as ''Action required''''']]
On the [[#project_page|project page]], comments on technical aspects can be made, these comments are the channel in which non-conformities are issued.

A comment or non-conformity must be issued in the following cases:

* Information is missing in order to be able to classify or recognise a part or assembly.
* Information about a supplier is missing (links to websites tend to be modified).
* Missing information on a purchased part, in order to be able to locate it in current markets.
* Missing measurements or other specifications in the [[Technical drawings]].
* Lack of coherence in the specifications, with respect to the assembly of the parts.
* Missing fields in the [[#part_list|Parts list]].
* Depending on the type of assembly:
** There must exist for each part, a [[Technical drawings|plan in PDF]] and its respective [[CAD files|CAD file]] (the latter, with the purpose of being able to review the 3D information in other CAD systems different from the one that has generated the parts).
** The 3D printing parts must be accompanied by their STL file, in addition to their [[Technical drawings|PDF drawing]] and their [[CAD files|CAD file]].
** For printed circuit boards (PCB), the addresses of their components must be included.
* In case of confusing information or obvious mistakes, a friendly comment should be left, pointing out the mistake in the corresponding item.
* In case of problems regarding the Project in general, there is an extra field in the [[#part_list|Parts list]], where comments can be added
* Those items that require some correction by the [[Certifcation platform#applicant|Applicant]], must be marked as ''Action required'', in the [[#project_page|Project page]], action ''Edit'', tab ''Part list''.
* This process can be repeated as long as there are comments or non-conformities with corrections to be made and not all the items of the [[#part_list|Part list]] are approved, through which, communication with the [[Certifcation platform#applicant|Applicant]] must always be maintained.
=== Project Approval ===
[[File:Project aproved.JPG|thumb|'''Item marked as ''Approved''''']]
After all non-conformities have been resolved, you should:
* Mark each item in the [[#part_list|Part list]] as ''Approved'', on the [[#project_page|Project page]], action ''Edit'', tab ''Part list''.
* Add a final comment including ''OK, FINISHED''.
* Notify the [[Certifcation platform#coordinator|Coordinator|Coordinator]], about the Project Approval.

== Equipo de evaluación de conformidad (CAB) ==
El [[Certifcation platform#cab-team|Equipo CAB]] tiene acceso los datos de contacto de los [[Certifcation platform#reviewers|Revisores]] y del [[Certifcation platform#applicant|Aplicante]], pudiendo siempre intervenir en la resolución de no coformidades y obteniendo información directa para la emisión del [[Certification processes#obs|Documento de Certificación]].
=== Validación de información del Aplicante y los Revisores ===
Entre algunas de las actividades del [[Certifcation platform#cab-team|Equipo CAB]], se tiene:
* Verifica algunas formalidades del Proyecto.
* En conjunto con el [[Certifcation platform#coordinator|Coordinador]] Apertura el [[Certification processes]] ya que participa en la [[#reviewers-designation|Designación de Revisores]].
=== Emisión del Documento de Certificación ===
Una vez que el [[Certifcation platform#applicant|Aplicante]] haya ingresado toda la [[#docs-upload|Documentación técnica]], al menos dos veces, el [[Certifcation platform#cab-team|Equipo CAB]] puede emitir una certificación donde se valide el cumplimiento de la [[DIN Spec 3105]]. Esto culmina el proceso de revisión, el cual pudiera ser abierto si:
* Alguna persona presenta quejas ante el [[Certifcation platform#cab-team|Equipo CAB]] por:
** La publicación de la documentación ya no es accesible total o parcialmente.
** Los términos de la licencia se han modificado y ya no cumplen con los requisitos de la norma [[DIN Spec 3105]].
** Cualquier información relevante ha sido alterada o eliminada de la [[Certifcation platform]].
* Teniendo en cuenta la importancia de las quejas presentadas, el [[Certifcation platform#cab-team|Equipo CAB]] puede anular la certificación en curso y volver a abrir el [[Certification processes]] una nueva revisión de la [[Technical documentation]].
* El [[Certifcation platform#applicant|Aplicante]] puede subir nuevamente documentación que ya ha sido certificada y aprobada, en este caso, la misma no requiere ser revisada otra vez.

Certification instructions

2021-02-23T14:37:16Z

Robert: /* Aprobación del Documento de certificación */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designation of the Conformity Assessment Body (CAB) ===
[[File:user rights6.jpg|thumb|'''Assignment of Assessor role to a user''']]]]
The [[Certifcation platform#cab-team|CAB-team]] must be designated and activated, once the [[Certifcation platform#applicant|Applicant]] performs the [[Request certification for your project]] of the Project, as this team must participate, among others, in the designation of the [[Certifcation platform#reviewers|Reviewers]].

For each member of the [[Certifcation platform#cab-team|CAB-team]], the following must be fulfilled:
*If the [[Certifcation platform#cab-team|Evaluator]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Enter the user's name and access their role information, under ''Load user groups''.
** Activate the ''certification_body'' checkbox.
** Save the changes in ''Save user groups''.
* The [[Certifcation platform#coordinator|Coordinator]] must contact each member of the [[Certifcation platform#cab-team|CAB-team]], to notify them about their responsibilities as Assessor and thus give continuity to the certification.

<div id="reviewers-designation"></div>

=== Designation of Reviewers ===
[[File:user_rights2.jpg|thumb|'''Assigning a Reviewer role to a user''']]
[[File:Certification manager.JPG|thumb|'''Designation of Reviewer to the Project''']]
* If the [[Certifcation platform#reviewers|Reviewers|Reviewer]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights]]
** Enter the user's name and access their role information, under ''Load user groups''.
Activate the checkbox ''certification_reviewer'' ** Save the changes in ''Save user groups''.
Save the changes in ''Save user groups'' ** Save the changes in ''Save user groups''.
* Go to the [[#project_page|Project page]], action ''Edit'', tab ''Certification Manager''.
* In the ''Reviewer 1 to 3'' fields, select the user that will be [[Certifcation platform#reviewers|Reviewer]].
** Save the changes in ''Save page''.
 
 
 
 
 
 
 
 
 
 
 

=== Approval of the Certification Document ===
After the [[Certifcation platform#cab-team|CAB-team]], has issued the [[Certification processes#obs|Certification Document]], the [[Certifcation platform#coordinator|Coordinator]] must carry out the respective steps for the approval of this document, which includes:
* Approval and signature of Authorities by OHO.
* Approval and signature of Authorities by the external certification body for validation according to [[DIN Spec 3105]].

== Revisores ==
Los [[Certifcation platform#reviewers|Revisores]] tienen la tarea de analizar técnicamenbte toda la documentación del Proyecto, para lo cual, deben haber pasado por el [[#sing-up|proceso de registro]] de la misma manera que en el caso del [[Certifcation platform#applicant|Aplicante]]. También debe contar con el rol de ''certificarion_reviewer'', como se indicó en [[#reviewers-designation|Designación de Revisores]].

Cada [[Certifcation platform#reviewers|Revisor]] debe cumplir con los aspectos mencionados a continuación:

=== Análisis de la Documentación Técnica ===
* Ingresar a la [[#project_page|página del Proyecto]].
* Analizar toda la información disponible, especialmente, las instrucciones de ensamblaje, lo cual incluye:
** Referencias correctas entre las partes de los [[Technical drawings]] y la [[Parts list]] .
** Procesos de fabricación para piezas especiales o medios de union bien explicados.
** Coherencia en la información mostrada, debe tener sentido en términos técnicos y de [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].

=== Emisión de no conformidades ===
[[File:Project comments.JPG|thumb|'''Comentarios en un proyecto''']]
[[File:Project action required.JPG|thumb|'''Item marcado como ''Action required''''']]
En la [[#project_page|página del Proyecto]], se pueden realizar comentarios sobre aspectos técnicos, estos comentarios son la canal en el que se emiten las no conformidades.

Se debe emitir un comentario o no conformidad en los siguientes casos:

* Falta información para poder clasificar o reconnocer alguna pieza o conjunto.
* Falta información sobre algún proveedor (los enlaces a sitios web tienden a ser modificados).
* Falta información sobre alguna pieza comprada, para poder ubicarla en los mercados actuales.
* Faltan medidas u otras especificaciones en los [[Technical drawings]].
* Falta de coherencia en las especificaciones, con respecto al ensamblaje de las piezas.
* Faltan campos en la [[#part_list|Lista de piezas]].
* Dependiendo del tipo de ensamblaje:
** Debe existir para cada pieza, un [[Technical drawings|plano en PDF]] y su respectivo [[CAD files|Archivo CAD]]. (esto último, con la finalidad de que se pueda revisar la información 3D en otoros sistemas CAD distintos del que haya generado las piezas).
** Las piezas de impresión 3D, deben estar acompañadas de su archivo STL, además de su [[Technical drawings|plano en PDF]] y su [[CAD files|Archivo CAD]].
** Para circuitos impresos (PCB), se debe incluir las direcciones de sus componentes.
* En caso de información confusa o errores evidentes, se debe dejar un comentario amigable, señalando la equivocación en el item que corresponda.
* En caso de problemas con respecto al Proyecto en general, hay un campo extra en la [[#part_list|Lista de piezas]], donde se pueden agregar comentarios.
* Aquellos items que requieran alguna corrección por parte del [[Certifcation platform#applicant|Aplicante]], deben ser marcados como ''Action required'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''
* Este proceso se puede repetir mientras existan comentarios o no conformidades con correcciones por realizar y no esten aprobados todos los items de la [[#part_list|Lista de piezas]], a través de la cual, siempre se debe mantener comunicación con el [[Certifcation platform#applicant|Aplicante]].
=== Aprobación del Proyecto ===
[[File:Project aproved.JPG|thumb|'''Item marcado como ''Approved''''']]
Luego de que se han resuelto, todas las no conformidades, se debe:
* Marcar cada uno de los item en la [[#part_list|Lista de piezas]] como ''Approved'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''.
* Agregar un comentario final que incluya 'OK, FINISHED'.
* Notificar al [[Certifcation platform#coordinator|Coordinador]], sobre la Aprobación del Proyecto.
== Equipo de evaluación de conformidad (CAB) ==
El [[Certifcation platform#cab-team|Equipo CAB]] tiene acceso los datos de contacto de los [[Certifcation platform#reviewers|Revisores]] y del [[Certifcation platform#applicant|Aplicante]], pudiendo siempre intervenir en la resolución de no coformidades y obteniendo información directa para la emisión del [[Certification processes#obs|Documento de Certificación]].
=== Validación de información del Aplicante y los Revisores ===
Entre algunas de las actividades del [[Certifcation platform#cab-team|Equipo CAB]], se tiene:
* Verifica algunas formalidades del Proyecto.
* En conjunto con el [[Certifcation platform#coordinator|Coordinador]] Apertura el [[Certification processes]] ya que participa en la [[#reviewers-designation|Designación de Revisores]].
=== Emisión del Documento de Certificación ===
Una vez que el [[Certifcation platform#applicant|Aplicante]] haya ingresado toda la [[#docs-upload|Documentación técnica]], al menos dos veces, el [[Certifcation platform#cab-team|Equipo CAB]] puede emitir una certificación donde se valide el cumplimiento de la [[DIN Spec 3105]]. Esto culmina el proceso de revisión, el cual pudiera ser abierto si:
* Alguna persona presenta quejas ante el [[Certifcation platform#cab-team|Equipo CAB]] por:
** La publicación de la documentación ya no es accesible total o parcialmente.
** Los términos de la licencia se han modificado y ya no cumplen con los requisitos de la norma [[DIN Spec 3105]].
** Cualquier información relevante ha sido alterada o eliminada de la [[Certifcation platform]].
* Teniendo en cuenta la importancia de las quejas presentadas, el [[Certifcation platform#cab-team|Equipo CAB]] puede anular la certificación en curso y volver a abrir el [[Certification processes]] una nueva revisión de la [[Technical documentation]].
* El [[Certifcation platform#applicant|Aplicante]] puede subir nuevamente documentación que ya ha sido certificada y aprobada, en este caso, la misma no requiere ser revisada otra vez.

Certification instructions

2021-02-23T14:36:03Z

Robert: /* Designación de Revisores */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designation of the Conformity Assessment Body (CAB) ===
[[File:user rights6.jpg|thumb|'''Assignment of Assessor role to a user''']]]]
The [[Certifcation platform#cab-team|CAB-team]] must be designated and activated, once the [[Certifcation platform#applicant|Applicant]] performs the [[Request certification for your project]] of the Project, as this team must participate, among others, in the designation of the [[Certifcation platform#reviewers|Reviewers]].

For each member of the [[Certifcation platform#cab-team|CAB-team]], the following must be fulfilled:
*If the [[Certifcation platform#cab-team|Evaluator]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Enter the user's name and access their role information, under ''Load user groups''.
** Activate the ''certification_body'' checkbox.
** Save the changes in ''Save user groups''.
* The [[Certifcation platform#coordinator|Coordinator]] must contact each member of the [[Certifcation platform#cab-team|CAB-team]], to notify them about their responsibilities as Assessor and thus give continuity to the certification.

<div id="reviewers-designation"></div>

=== Designation of Reviewers ===
[[File:user_rights2.jpg|thumb|'''Assigning a Reviewer role to a user''']]
[[File:Certification manager.JPG|thumb|'''Designation of Reviewer to the Project''']]
* If the [[Certifcation platform#reviewers|Reviewers|Reviewer]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights]]
** Enter the user's name and access their role information, under ''Load user groups''.
Activate the checkbox ''certification_reviewer'' ** Save the changes in ''Save user groups''.
Save the changes in ''Save user groups'' ** Save the changes in ''Save user groups''.
* Go to the [[#project_page|Project page]], action ''Edit'', tab ''Certification Manager''.
* In the ''Reviewer 1 to 3'' fields, select the user that will be [[Certifcation platform#reviewers|Reviewer]].
** Save the changes in ''Save page''.
 
 
 
 
 
 
 
 
 
 
 

=== Aprobación del Documento de certificación ===
Luego de que el [[Certifcation platform#cab-team|Equipo CAB]], ha realizado la emisión del [[Certification processes#obs|Documento de Certificación]], el [[Certifcation platform#coordinator|Coordinador]] debe realizar los trámites respectivos para la aprobación de dicho documento, lo cual incluye:
* Visto bueno y firma de Autoridades por parte de OHO.
* Visto bueno y firma de Autoridades por parte de ente certificador externo para la validación según [[DIN Spec 3105]].

== Revisores ==
Los [[Certifcation platform#reviewers|Revisores]] tienen la tarea de analizar técnicamenbte toda la documentación del Proyecto, para lo cual, deben haber pasado por el [[#sing-up|proceso de registro]] de la misma manera que en el caso del [[Certifcation platform#applicant|Aplicante]]. También debe contar con el rol de ''certificarion_reviewer'', como se indicó en [[#reviewers-designation|Designación de Revisores]].

Cada [[Certifcation platform#reviewers|Revisor]] debe cumplir con los aspectos mencionados a continuación:

=== Análisis de la Documentación Técnica ===
* Ingresar a la [[#project_page|página del Proyecto]].
* Analizar toda la información disponible, especialmente, las instrucciones de ensamblaje, lo cual incluye:
** Referencias correctas entre las partes de los [[Technical drawings]] y la [[Parts list]] .
** Procesos de fabricación para piezas especiales o medios de union bien explicados.
** Coherencia en la información mostrada, debe tener sentido en términos técnicos y de [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].

=== Emisión de no conformidades ===
[[File:Project comments.JPG|thumb|'''Comentarios en un proyecto''']]
[[File:Project action required.JPG|thumb|'''Item marcado como ''Action required''''']]
En la [[#project_page|página del Proyecto]], se pueden realizar comentarios sobre aspectos técnicos, estos comentarios son la canal en el que se emiten las no conformidades.

Se debe emitir un comentario o no conformidad en los siguientes casos:

* Falta información para poder clasificar o reconnocer alguna pieza o conjunto.
* Falta información sobre algún proveedor (los enlaces a sitios web tienden a ser modificados).
* Falta información sobre alguna pieza comprada, para poder ubicarla en los mercados actuales.
* Faltan medidas u otras especificaciones en los [[Technical drawings]].
* Falta de coherencia en las especificaciones, con respecto al ensamblaje de las piezas.
* Faltan campos en la [[#part_list|Lista de piezas]].
* Dependiendo del tipo de ensamblaje:
** Debe existir para cada pieza, un [[Technical drawings|plano en PDF]] y su respectivo [[CAD files|Archivo CAD]]. (esto último, con la finalidad de que se pueda revisar la información 3D en otoros sistemas CAD distintos del que haya generado las piezas).
** Las piezas de impresión 3D, deben estar acompañadas de su archivo STL, además de su [[Technical drawings|plano en PDF]] y su [[CAD files|Archivo CAD]].
** Para circuitos impresos (PCB), se debe incluir las direcciones de sus componentes.
* En caso de información confusa o errores evidentes, se debe dejar un comentario amigable, señalando la equivocación en el item que corresponda.
* En caso de problemas con respecto al Proyecto en general, hay un campo extra en la [[#part_list|Lista de piezas]], donde se pueden agregar comentarios.
* Aquellos items que requieran alguna corrección por parte del [[Certifcation platform#applicant|Aplicante]], deben ser marcados como ''Action required'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''
* Este proceso se puede repetir mientras existan comentarios o no conformidades con correcciones por realizar y no esten aprobados todos los items de la [[#part_list|Lista de piezas]], a través de la cual, siempre se debe mantener comunicación con el [[Certifcation platform#applicant|Aplicante]].
=== Aprobación del Proyecto ===
[[File:Project aproved.JPG|thumb|'''Item marcado como ''Approved''''']]
Luego de que se han resuelto, todas las no conformidades, se debe:
* Marcar cada uno de los item en la [[#part_list|Lista de piezas]] como ''Approved'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''.
* Agregar un comentario final que incluya 'OK, FINISHED'.
* Notificar al [[Certifcation platform#coordinator|Coordinador]], sobre la Aprobación del Proyecto.
== Equipo de evaluación de conformidad (CAB) ==
El [[Certifcation platform#cab-team|Equipo CAB]] tiene acceso los datos de contacto de los [[Certifcation platform#reviewers|Revisores]] y del [[Certifcation platform#applicant|Aplicante]], pudiendo siempre intervenir en la resolución de no coformidades y obteniendo información directa para la emisión del [[Certification processes#obs|Documento de Certificación]].
=== Validación de información del Aplicante y los Revisores ===
Entre algunas de las actividades del [[Certifcation platform#cab-team|Equipo CAB]], se tiene:
* Verifica algunas formalidades del Proyecto.
* En conjunto con el [[Certifcation platform#coordinator|Coordinador]] Apertura el [[Certification processes]] ya que participa en la [[#reviewers-designation|Designación de Revisores]].
=== Emisión del Documento de Certificación ===
Una vez que el [[Certifcation platform#applicant|Aplicante]] haya ingresado toda la [[#docs-upload|Documentación técnica]], al menos dos veces, el [[Certifcation platform#cab-team|Equipo CAB]] puede emitir una certificación donde se valide el cumplimiento de la [[DIN Spec 3105]]. Esto culmina el proceso de revisión, el cual pudiera ser abierto si:
* Alguna persona presenta quejas ante el [[Certifcation platform#cab-team|Equipo CAB]] por:
** La publicación de la documentación ya no es accesible total o parcialmente.
** Los términos de la licencia se han modificado y ya no cumplen con los requisitos de la norma [[DIN Spec 3105]].
** Cualquier información relevante ha sido alterada o eliminada de la [[Certifcation platform]].
* Teniendo en cuenta la importancia de las quejas presentadas, el [[Certifcation platform#cab-team|Equipo CAB]] puede anular la certificación en curso y volver a abrir el [[Certification processes]] una nueva revisión de la [[Technical documentation]].
* El [[Certifcation platform#applicant|Aplicante]] puede subir nuevamente documentación que ya ha sido certificada y aprobada, en este caso, la misma no requiere ser revisada otra vez.

Certification instructions

2021-02-23T14:34:21Z

Robert: /* Designación del Equipo de evaluación de conformidad (CAB) */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designation of the Conformity Assessment Body (CAB) ===
[[File:user rights6.jpg|thumb|'''Assignment of Assessor role to a user''']]]]
The [[Certifcation platform#cab-team|CAB-team]] must be designated and activated, once the [[Certifcation platform#applicant|Applicant]] performs the [[Request certification for your project]] of the Project, as this team must participate, among others, in the designation of the [[Certifcation platform#reviewers|Reviewers]].

For each member of the [[Certifcation platform#cab-team|CAB-team]], the following must be fulfilled:
*If the [[Certifcation platform#cab-team|Evaluator]] user does not have the required role:
** Login to the special page [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Enter the user's name and access their role information, under ''Load user groups''.
** Activate the ''certification_body'' checkbox.
** Save the changes in ''Save user groups''.
* The [[Certifcation platform#coordinator|Coordinator]] must contact each member of the [[Certifcation platform#cab-team|CAB-team]], to notify them about their responsibilities as Assessor and thus give continuity to the certification.

<div id="reviewers-designation"></div>

=== Designación de Revisores ===
[[File:user_rights2.jpg|thumb|'''Asignación de rol de Revisor a un usuario''']]
[[File:Certification manager.JPG|thumb|'''Designación de Revisor al Proyecto''']]
* Si el usuario del [[Certifcation platform#reviewers|Revisor]] no tiene el rol requerido:
** Ingresar a la página especial [https://en.oho.wiki/wiki/Special:UserRights User Rights]
** Escribir el nombre del usuario y acceder a su información de rol, en ''Load user groups''
** Activar la casilla ''certification_reviewer''
** Guardar los cambios en ''Save user groups''
* Ir a la [[#project_page|página del Proyecto]], acción ''Edit'', pestaña ''Certification Manager''
* En los campos ''Reviewer 1 a 3'', seleccionar el usuario que será [[Certifcation platform#reviewers|Revisor]].
** Guardar los cambios en ''Save page''
 
 
 
 
 
 
 
 
 
 
 

=== Aprobación del Documento de certificación ===
Luego de que el [[Certifcation platform#cab-team|Equipo CAB]], ha realizado la emisión del [[Certification processes#obs|Documento de Certificación]], el [[Certifcation platform#coordinator|Coordinador]] debe realizar los trámites respectivos para la aprobación de dicho documento, lo cual incluye:
* Visto bueno y firma de Autoridades por parte de OHO.
* Visto bueno y firma de Autoridades por parte de ente certificador externo para la validación según [[DIN Spec 3105]].

== Revisores ==
Los [[Certifcation platform#reviewers|Revisores]] tienen la tarea de analizar técnicamenbte toda la documentación del Proyecto, para lo cual, deben haber pasado por el [[#sing-up|proceso de registro]] de la misma manera que en el caso del [[Certifcation platform#applicant|Aplicante]]. También debe contar con el rol de ''certificarion_reviewer'', como se indicó en [[#reviewers-designation|Designación de Revisores]].

Cada [[Certifcation platform#reviewers|Revisor]] debe cumplir con los aspectos mencionados a continuación:

=== Análisis de la Documentación Técnica ===
* Ingresar a la [[#project_page|página del Proyecto]].
* Analizar toda la información disponible, especialmente, las instrucciones de ensamblaje, lo cual incluye:
** Referencias correctas entre las partes de los [[Technical drawings]] y la [[Parts list]] .
** Procesos de fabricación para piezas especiales o medios de union bien explicados.
** Coherencia en la información mostrada, debe tener sentido en términos técnicos y de [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].

=== Emisión de no conformidades ===
[[File:Project comments.JPG|thumb|'''Comentarios en un proyecto''']]
[[File:Project action required.JPG|thumb|'''Item marcado como ''Action required''''']]
En la [[#project_page|página del Proyecto]], se pueden realizar comentarios sobre aspectos técnicos, estos comentarios son la canal en el que se emiten las no conformidades.

Se debe emitir un comentario o no conformidad en los siguientes casos:

* Falta información para poder clasificar o reconnocer alguna pieza o conjunto.
* Falta información sobre algún proveedor (los enlaces a sitios web tienden a ser modificados).
* Falta información sobre alguna pieza comprada, para poder ubicarla en los mercados actuales.
* Faltan medidas u otras especificaciones en los [[Technical drawings]].
* Falta de coherencia en las especificaciones, con respecto al ensamblaje de las piezas.
* Faltan campos en la [[#part_list|Lista de piezas]].
* Dependiendo del tipo de ensamblaje:
** Debe existir para cada pieza, un [[Technical drawings|plano en PDF]] y su respectivo [[CAD files|Archivo CAD]]. (esto último, con la finalidad de que se pueda revisar la información 3D en otoros sistemas CAD distintos del que haya generado las piezas).
** Las piezas de impresión 3D, deben estar acompañadas de su archivo STL, además de su [[Technical drawings|plano en PDF]] y su [[CAD files|Archivo CAD]].
** Para circuitos impresos (PCB), se debe incluir las direcciones de sus componentes.
* En caso de información confusa o errores evidentes, se debe dejar un comentario amigable, señalando la equivocación en el item que corresponda.
* En caso de problemas con respecto al Proyecto en general, hay un campo extra en la [[#part_list|Lista de piezas]], donde se pueden agregar comentarios.
* Aquellos items que requieran alguna corrección por parte del [[Certifcation platform#applicant|Aplicante]], deben ser marcados como ''Action required'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''
* Este proceso se puede repetir mientras existan comentarios o no conformidades con correcciones por realizar y no esten aprobados todos los items de la [[#part_list|Lista de piezas]], a través de la cual, siempre se debe mantener comunicación con el [[Certifcation platform#applicant|Aplicante]].
=== Aprobación del Proyecto ===
[[File:Project aproved.JPG|thumb|'''Item marcado como ''Approved''''']]
Luego de que se han resuelto, todas las no conformidades, se debe:
* Marcar cada uno de los item en la [[#part_list|Lista de piezas]] como ''Approved'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''.
* Agregar un comentario final que incluya 'OK, FINISHED'.
* Notificar al [[Certifcation platform#coordinator|Coordinador]], sobre la Aprobación del Proyecto.
== Equipo de evaluación de conformidad (CAB) ==
El [[Certifcation platform#cab-team|Equipo CAB]] tiene acceso los datos de contacto de los [[Certifcation platform#reviewers|Revisores]] y del [[Certifcation platform#applicant|Aplicante]], pudiendo siempre intervenir en la resolución de no coformidades y obteniendo información directa para la emisión del [[Certification processes#obs|Documento de Certificación]].
=== Validación de información del Aplicante y los Revisores ===
Entre algunas de las actividades del [[Certifcation platform#cab-team|Equipo CAB]], se tiene:
* Verifica algunas formalidades del Proyecto.
* En conjunto con el [[Certifcation platform#coordinator|Coordinador]] Apertura el [[Certification processes]] ya que participa en la [[#reviewers-designation|Designación de Revisores]].
=== Emisión del Documento de Certificación ===
Una vez que el [[Certifcation platform#applicant|Aplicante]] haya ingresado toda la [[#docs-upload|Documentación técnica]], al menos dos veces, el [[Certifcation platform#cab-team|Equipo CAB]] puede emitir una certificación donde se valide el cumplimiento de la [[DIN Spec 3105]]. Esto culmina el proceso de revisión, el cual pudiera ser abierto si:
* Alguna persona presenta quejas ante el [[Certifcation platform#cab-team|Equipo CAB]] por:
** La publicación de la documentación ya no es accesible total o parcialmente.
** Los términos de la licencia se han modificado y ya no cumplen con los requisitos de la norma [[DIN Spec 3105]].
** Cualquier información relevante ha sido alterada o eliminada de la [[Certifcation platform]].
* Teniendo en cuenta la importancia de las quejas presentadas, el [[Certifcation platform#cab-team|Equipo CAB]] puede anular la certificación en curso y volver a abrir el [[Certification processes]] una nueva revisión de la [[Technical documentation]].
* El [[Certifcation platform#applicant|Aplicante]] puede subir nuevamente documentación que ya ha sido certificada y aprobada, en este caso, la misma no requiere ser revisada otra vez.

Certification instructions

2021-02-23T14:28:55Z

Robert: /* Aplicante */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Applicant ==
The [[Certifcation platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
[[File:Applicant account new.JPG|thumb|'''User account creation''']]
<div id="sing-up"></div>
=== Registration on the Certification Platform ===
The [[Certifcation platform#applicant|applicant|Applicant]] must be registered with OHO, via: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Project data upload ====
[[File:Applicant project basic.JPG|thumb|''Basic data'']]
For the project to exist in the platform, you must start by uploading its basic information and then the rest of the documentation. This is done by logging in at: https://en.oho.wiki/wiki/Special:FormEdit/Project .
Here the user must upload the following information:
* Basic data - The following information must be entered:
** Project name in three languages.
** Project Category - select from the levels offered by the system.
** One or more images of the project:
** They must be clear images, which can be understood.
*** Without distortions.
*** With a suitable resolution, preferably around 600 to 800 pixels wide.
** Keywords:
*** Must not contain redundancies.
*** They must be related to technical aspects of the project.
*** At least five keywords.
** URL (first publication): Web address from which the information on the project was obtained, if available.
** Status of the translation - Select from the options:
*** No translation.
*** Automatic translation.
*** In process.
*** Manual.
** Description of the project:
*** Briefly explain what it consists of.
*** Technologies used.
*** Some important materials
** Highlight advantages such as cost, innovation, efficiency, etc.
* Additional fields - These are initially optional fields, consisting mainly of the following aspects. [[File:Applicant project fields.JPG|thumb|''Additional fields'']]
** Licence.
** Source.
** Organisation.
** Project Status.
** Project Maturity.
** Contains Mechanical Hardware.
** Licence for mechanical hardware.
** Contains electronic hardware.
** Contains original software.
** Published assembly instructions.
** BOM published.
** Conflict management system in place.
** Versioning system in place.
** Contains PDF drawings.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Technology Readiness Level (TRL)].
<div id="project_page"></div>
* When this information is saved, a page is created in OHO with the name of the Project that has been entered.
[[File:Applicant project part-list.JPG|thumb|'''Part List Fields''']]

<div id="docs-upload"></div>
=== Uploading technical documentation ===
<div id="part_list"></div>
* [[Parts list]]: It is important to enter each part and assembly correctly, with the right information and in the right order. The [[Parts list]] is loaded in the ''Part List'' tab. 
 
 
 

** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|'''CSV file''']] 
 
 
 

** The Part list can also be uploaded by accessing the ''Import from CSV'' option, through which the already defined [[Parts list#guidelines|CSV file]] can be uploaded. ''' 

* [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|'''Technical documentation entry''']]
** Upload a PDF file containing the Project drawings, already defined in [[Technical drawings]].
** Upload the compressed folder with the files, already defined in [[CAD files]].
** Similarly, upload the compressed folder with the exchange files, also defined in [[CAD files]].
** Upload also each technical document of importance for the development of the Project.
** When uploading this information, an image or view representing the set of plans or documents being uploaded must be included in the same form, this can be one of the images previously uploaded as indicated in [[#data_upload|Basic data]].
 
 
 
 
 
 

=== Request certification for the Project ===
After uploading the [[Technical documentation]] of the Project, the [[Certifcation platform#applicant|Applicant]] must make the [[Request certification for your project]] of the Project, which will then be contacted by OHO to formalise the process, the following is highlighted:
* The [[#sing-up|user]] assigned to the [[Certifcation platform#applicant|Applicant]] must have all the required information in order to be contacted and verified.
* The Project must have all the fields corresponding to [[#data_upload|Basic data]] entered.
* The [[Parts list]] must have been entered [[#docs-upload|correctly]].

=== Project Corrections ===
[[File:Project comments.JPG|thumb|'''Comments on a project''']]
If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certifcation platform#applicant|applicant|Applicant]] must proceed to make the necessary corrections and edit the project information in the same way the information was entered.
* The communication channel to receive the non-conformities is the same [[#project_page|Project page]], in which the [[Certifcation platform#applicant|Applicant]] must log in regularly, these are displayed as comments superimposed on the [[Parts list]].
* Non-conformities on those items marked as ''Action Required'' must be addressed by the [[Certifcation platform#reviewers|Reviewers]].
* Corrections must be made in a timely manner, in order to expedite the certification process.
* The [[Certifcation platform#applicant|Applicant]], may comment on the ''Reviews'' or add further comments in order to communicate any issue resolution issues.

=== Receipt of the Certification Document ===
The final step of the [[Certification processes]], is the reception by the [[Certifcation platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
* The [[Certifcation platform#applicant|applicant]] must read in detail the document to be received.
* The [[Certifcation platform#applicant|applicant]] must accept the terms of the document.
* Finally, the [[Certifcation platform#applicant|applicant]], is directed to a page where he/she can download the document and fill in some fields about his/her experience during the [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designación del Equipo de evaluación de conformidad (CAB) ===
[[File:user rights6.jpg|thumb|'''Asignación de rol de Evaluador a un usuario''']]
El [[Certifcation platform#cab-team|Equipo CAB]] se debe designar y activar, una vez que el [[Certifcation platform#applicant|Aplicante]] realiza la [[Request certification for your project]] del Proyecto, ya que dicho equipo debe participar, entre otros, en la designación de los [[Certifcation platform#reviewers|Revisores]].

Para cada integrante del [[Certifcation platform#cab-team|Equipo CAB]], se debe cumplir:
*Si el usuario del [[Certifcation platform#cab-team|Evaluador]] no tiene el rol requerido:
** Ingresar a la página especial [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Escribir el nombre del usuario y acceder a su información de rol, en ''Load user groups''.
** Activar la casilla ''certification_body''.
** Guardar los cambios en ''Save user groups''.
* El [[Certifcation platform#coordinator|Coordinador]] debe contactar a cada miembro del [[Certifcation platform#cab-team|Equipo CAB]], para notificar sobre sus responsabilidades como Evaluador y así dar continuidad a la certificación.

<div id="reviewers-designation"></div>

=== Designación de Revisores ===
[[File:user_rights2.jpg|thumb|'''Asignación de rol de Revisor a un usuario''']]
[[File:Certification manager.JPG|thumb|'''Designación de Revisor al Proyecto''']]
* Si el usuario del [[Certifcation platform#reviewers|Revisor]] no tiene el rol requerido:
** Ingresar a la página especial [https://en.oho.wiki/wiki/Special:UserRights User Rights]
** Escribir el nombre del usuario y acceder a su información de rol, en ''Load user groups''
** Activar la casilla ''certification_reviewer''
** Guardar los cambios en ''Save user groups''
* Ir a la [[#project_page|página del Proyecto]], acción ''Edit'', pestaña ''Certification Manager''
* En los campos ''Reviewer 1 a 3'', seleccionar el usuario que será [[Certifcation platform#reviewers|Revisor]].
** Guardar los cambios en ''Save page''
 
 
 
 
 
 
 
 
 
 
 

=== Aprobación del Documento de certificación ===
Luego de que el [[Certifcation platform#cab-team|Equipo CAB]], ha realizado la emisión del [[Certification processes#obs|Documento de Certificación]], el [[Certifcation platform#coordinator|Coordinador]] debe realizar los trámites respectivos para la aprobación de dicho documento, lo cual incluye:
* Visto bueno y firma de Autoridades por parte de OHO.
* Visto bueno y firma de Autoridades por parte de ente certificador externo para la validación según [[DIN Spec 3105]].

== Revisores ==
Los [[Certifcation platform#reviewers|Revisores]] tienen la tarea de analizar técnicamenbte toda la documentación del Proyecto, para lo cual, deben haber pasado por el [[#sing-up|proceso de registro]] de la misma manera que en el caso del [[Certifcation platform#applicant|Aplicante]]. También debe contar con el rol de ''certificarion_reviewer'', como se indicó en [[#reviewers-designation|Designación de Revisores]].

Cada [[Certifcation platform#reviewers|Revisor]] debe cumplir con los aspectos mencionados a continuación:

=== Análisis de la Documentación Técnica ===
* Ingresar a la [[#project_page|página del Proyecto]].
* Analizar toda la información disponible, especialmente, las instrucciones de ensamblaje, lo cual incluye:
** Referencias correctas entre las partes de los [[Technical drawings]] y la [[Parts list]] .
** Procesos de fabricación para piezas especiales o medios de union bien explicados.
** Coherencia en la información mostrada, debe tener sentido en términos técnicos y de [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].

=== Emisión de no conformidades ===
[[File:Project comments.JPG|thumb|'''Comentarios en un proyecto''']]
[[File:Project action required.JPG|thumb|'''Item marcado como ''Action required''''']]
En la [[#project_page|página del Proyecto]], se pueden realizar comentarios sobre aspectos técnicos, estos comentarios son la canal en el que se emiten las no conformidades.

Se debe emitir un comentario o no conformidad en los siguientes casos:

* Falta información para poder clasificar o reconnocer alguna pieza o conjunto.
* Falta información sobre algún proveedor (los enlaces a sitios web tienden a ser modificados).
* Falta información sobre alguna pieza comprada, para poder ubicarla en los mercados actuales.
* Faltan medidas u otras especificaciones en los [[Technical drawings]].
* Falta de coherencia en las especificaciones, con respecto al ensamblaje de las piezas.
* Faltan campos en la [[#part_list|Lista de piezas]].
* Dependiendo del tipo de ensamblaje:
** Debe existir para cada pieza, un [[Technical drawings|plano en PDF]] y su respectivo [[CAD files|Archivo CAD]]. (esto último, con la finalidad de que se pueda revisar la información 3D en otoros sistemas CAD distintos del que haya generado las piezas).
** Las piezas de impresión 3D, deben estar acompañadas de su archivo STL, además de su [[Technical drawings|plano en PDF]] y su [[CAD files|Archivo CAD]].
** Para circuitos impresos (PCB), se debe incluir las direcciones de sus componentes.
* En caso de información confusa o errores evidentes, se debe dejar un comentario amigable, señalando la equivocación en el item que corresponda.
* En caso de problemas con respecto al Proyecto en general, hay un campo extra en la [[#part_list|Lista de piezas]], donde se pueden agregar comentarios.
* Aquellos items que requieran alguna corrección por parte del [[Certifcation platform#applicant|Aplicante]], deben ser marcados como ''Action required'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''
* Este proceso se puede repetir mientras existan comentarios o no conformidades con correcciones por realizar y no esten aprobados todos los items de la [[#part_list|Lista de piezas]], a través de la cual, siempre se debe mantener comunicación con el [[Certifcation platform#applicant|Aplicante]].
=== Aprobación del Proyecto ===
[[File:Project aproved.JPG|thumb|'''Item marcado como ''Approved''''']]
Luego de que se han resuelto, todas las no conformidades, se debe:
* Marcar cada uno de los item en la [[#part_list|Lista de piezas]] como ''Approved'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''.
* Agregar un comentario final que incluya 'OK, FINISHED'.
* Notificar al [[Certifcation platform#coordinator|Coordinador]], sobre la Aprobación del Proyecto.
== Equipo de evaluación de conformidad (CAB) ==
El [[Certifcation platform#cab-team|Equipo CAB]] tiene acceso los datos de contacto de los [[Certifcation platform#reviewers|Revisores]] y del [[Certifcation platform#applicant|Aplicante]], pudiendo siempre intervenir en la resolución de no coformidades y obteniendo información directa para la emisión del [[Certification processes#obs|Documento de Certificación]].
=== Validación de información del Aplicante y los Revisores ===
Entre algunas de las actividades del [[Certifcation platform#cab-team|Equipo CAB]], se tiene:
* Verifica algunas formalidades del Proyecto.
* En conjunto con el [[Certifcation platform#coordinator|Coordinador]] Apertura el [[Certification processes]] ya que participa en la [[#reviewers-designation|Designación de Revisores]].
=== Emisión del Documento de Certificación ===
Una vez que el [[Certifcation platform#applicant|Aplicante]] haya ingresado toda la [[#docs-upload|Documentación técnica]], al menos dos veces, el [[Certifcation platform#cab-team|Equipo CAB]] puede emitir una certificación donde se valide el cumplimiento de la [[DIN Spec 3105]]. Esto culmina el proceso de revisión, el cual pudiera ser abierto si:
* Alguna persona presenta quejas ante el [[Certifcation platform#cab-team|Equipo CAB]] por:
** La publicación de la documentación ya no es accesible total o parcialmente.
** Los términos de la licencia se han modificado y ya no cumplen con los requisitos de la norma [[DIN Spec 3105]].
** Cualquier información relevante ha sido alterada o eliminada de la [[Certifcation platform]].
* Teniendo en cuenta la importancia de las quejas presentadas, el [[Certifcation platform#cab-team|Equipo CAB]] puede anular la certificación en curso y volver a abrir el [[Certification processes]] una nueva revisión de la [[Technical documentation]].
* El [[Certifcation platform#applicant|Aplicante]] puede subir nuevamente documentación que ya ha sido certificada y aprobada, en este caso, la misma no requiere ser revisada otra vez.

Certification instructions

2021-02-23T13:27:44Z

Robert: /* Compendio de instrucciones de acuerdo al rol en OHO */

== Overview of instructions according to the role in the OHO ==
The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process.

Here are the specific procedures for each role in the certification of a project:

<div id="applicant"></div>

== Aplicante ==
El [[Certifcation platform#applicant|Aplicante]] inicia y finaliza el [[Certification processes]], para lo cual debe cumplir con los procedimientos que se indican a continuación:
[[File:Applicant account new.JPG|thumb|'''Creación de cuenta de usuario''']]
<div id="sing-up"></div>
=== Registro en la Plataforma de certificación ===
El [[Certifcation platform#applicant|Aplicante]] debe estar registrado en OHO, a través de: 
https://en.oho.wiki/wiki/Special:CreateAccount 
 
 
 
 
 

<div id="data_upload"></div>
==== Carga de datos del Proyecto ====
[[File:Applicant project basic.JPG|thumb|'''Datos básicos''']]
Para que el proyecto exista en la plataforma, se debe comenzar cargando su información básica y luego el resto de su documentación. Esto se realiza, ingresando en: https://en.oho.wiki/wiki/Special:FormEdit/Project 
Aquí el usuario debe subir la siguiente información:
* Datos básicos - Se debe ingresar la siguiente información:
** Nombre del proyecto en tres idiomas.
** Categoría del Proyecto - seleccionar entre los niveles que ofrece el sistema.
** Una ó más imágenes del Proyecto:
** Deben ser imágenes claras, que se entiendan.
*** Sin distorsiones.
*** Con una resolución adecuada, preferiblemente de unos 600 a 800 pixeles de ancho.
** Palabras clave (Keywords):
*** No deben contener redundancias.
*** Deben guardar relación con aspectos técnicos del proyecto.
*** Mínimo unas cinco palabras clave.
** URL (primera publication): Dirección web de donde se obtuvo la información del proyecto, en caso de existir.
** Estatus de la traducción - Seleccionar enttre las opciones:
*** Sin traducción.
*** Traducción automática.
*** En proceso.
*** Manual.
** Descripción del Proyecto:
*** Explicar brevemente en qué consiste.
*** Las tecnologías usadas.
*** Algunos materiales importantes
** Destacar ventajas como costo, innovación, eficiencia, entre otros.
* Campos adicionales - Se trata de campos inicialmente opcionales, constan principalmente de los siguientes aspectos. [[File:Applicant project fields.JPG|thumb|'''Campos adicionales''']]
** Licencia.
** Fuente.
** Organización.
** Estatus del Proyecto.
** Maduréz del Proyecto.
** Contiene Hardware mecánico.
** Licencia para Hardware mecánico.
** Contiene Hardware electrónico.
** Contiene software original.
** Instrcciones de ensamblaje publicadas.
** Lista de materiales publicada.
** Se cuenta con sistema de gestion de conflictos.
** Se cuenta con sistema de versiones.
** Contiene dibujos en PDF.
** [https://es.wikipedia.org/wiki/Nivel_de_madurez_tecnol%C3%B3gica Nivel de preparación tecnológica (TRL)].
<div id="project_page"></div>
* Al guardar esta información, se crea en OHO una página con el nombre del Proyecto que se haya ingresado. 
[[File:Applicant project part-list.JPG|thumb|'''Campos de Part List''']]

<div id="docs-upload"></div>
=== Carga de la Documentación técnica ===
<div id="part_list"></div>
* [[Parts list]]: Es importante ingresar cada pieza y ensamblaje de manera correcta, con la información adecuada y en el orden establecido. La [[Parts list]] se carga en la pestaña ''Part List''. 
** Puede ser ingresada manualmente llenando cada campo de información para cada item de la lista. [[File:Partlist-structured.jpg|thumb|'''Archivo CSV''']]
** También se puede cargar el Part list, accediendo a la opción ''Import from CSV'', mediante la cual se puede subir el [[Parts list#guidelines|archivo CSV]] ya definido. 
* [[CAD files]], [[Technical drawings]] y Otros documentos: [[File:Applicant project docs.JPG|thumb|'''Ingreso de documentación técnica''']]
** Subir un archivo PDF que reuna los planos del Proyecto, ya definidos en [[Technical drawings]].
** Subir la carpeta comprimida con los archivos, ya definida en [[CAD files]].
** De igual manera, subir la carpeta comprimida con los archivos de intercambios, también definida en [[CAD files]].
** Subir también cada documento técnico de importancia para el desarrollo del Proyecto.
** Al cargar esta información se debe incluir en el mismo formulario, una imagen o vista que represente al conjunto de planos o documentos que se estén subiendo, esta puede ser una de las imágenes previamente cargadas como se indicó en [[#data_upload|Datos básicos]]
 
 
 
 
 
 

=== Solicitud de certificación del Proyecto ===
Luego de cargar la [[Technical documentation]] del Proyecto, el [[Certifcation platform#applicant|Aplicante]] debe realizar la [[Request certification for your project]] del Proyecto, con lo que este luego será contactado por OHO para formalizar el proceso, se destaca lo siguiente:
* El [[#sing-up|usuario]] asignado al [[Certifcation platform#applicant|Aplicante]] debe contar con toda la información requerida para poder ser contactado y verificado.
* El Proyecto debe tener ingresados todos los campos correspondientes a [[#data_upload|Datos básicos]].
* La [[Parts list]] debe haber sido ingresada [[#docs-upload|correctamente]].

=== Correcciones del Proyecto ===
[[File:Project comments.JPG|thumb|'''Comentarios en un proyecto''']]
Si durante la revisión de la documentación del Proyecto, el equipo de Revisores emite alguna no conformidad (''Reviews''), el [[Certifcation platform#applicant|Aplicante]] debe proceder a realizar los correctivos necesarios y editar la información del proyectos de la misma manera en que fue ingresada la información.
* El canal de comunicación para recibir las no conformidades es la misma [[#project_page|página del Proyecto]], en la cual el [[Certifcation platform#applicant|Aplicante]] debe iniciar sesión regularmente, estas se visualizan en forma de comentarios superpuestos sobre la [[Parts list]].
* Deben ser atendidas las no conformidades en aquellos items marcados como ''Action Required'', por parte de los [[Certifcation platform#reviewers|Revisores]].
* Se deben realizar las correcciones de manera oportuna, a fin de agilizar el proceso de certificación.
* El [[Certifcation platform#applicant|Aplicante]], puede comentar los ''Reviews'' o agregar más comentarios a fin de comunicar por esa vía cualquier aspecto sobre la resolución de problemas.

=== Recepción del Documento de certificación ===
El paso final del [[Certification processes]], es la recepción por parte del [[Certifcation platform#applicant|Aplicante]], del [[Certification processes#obs|Documento de Certificación]], para lo cual es contactado por los [[#project_page|canales establecidos]].
* El [[Certifcation platform#applicant|Aplicante]] debe leer detalladamente el documento a recibir.
* El [[Certifcation platform#applicant|Aplicante]] debe aceptar los términos del documento.
* Finalmente, el [[Certifcation platform#applicant|Aplicante]], es dirigido a una página en donde puede descargar el documento y llenar algunos campos sobre su experiencia durante el [[Certification processes]].

== Coordinador ==
El [[Certifcation platform#coordinator|Coordinador]], como ente rector por parte de OHO, es responsable del [[Certification processes]] ya que monitorea, habilita e impulsa todas las etpas. Sus principales actividades son:
=== Designación del Equipo de evaluación de conformidad (CAB) ===
[[File:user rights6.jpg|thumb|'''Asignación de rol de Evaluador a un usuario''']]
El [[Certifcation platform#cab-team|Equipo CAB]] se debe designar y activar, una vez que el [[Certifcation platform#applicant|Aplicante]] realiza la [[Request certification for your project]] del Proyecto, ya que dicho equipo debe participar, entre otros, en la designación de los [[Certifcation platform#reviewers|Revisores]].

Para cada integrante del [[Certifcation platform#cab-team|Equipo CAB]], se debe cumplir:
*Si el usuario del [[Certifcation platform#cab-team|Evaluador]] no tiene el rol requerido:
** Ingresar a la página especial [https://en.oho.wiki/wiki/Special:UserRights User Rights].
** Escribir el nombre del usuario y acceder a su información de rol, en ''Load user groups''.
** Activar la casilla ''certification_body''.
** Guardar los cambios en ''Save user groups''.
* El [[Certifcation platform#coordinator|Coordinador]] debe contactar a cada miembro del [[Certifcation platform#cab-team|Equipo CAB]], para notificar sobre sus responsabilidades como Evaluador y así dar continuidad a la certificación.

<div id="reviewers-designation"></div>

=== Designación de Revisores ===
[[File:user_rights2.jpg|thumb|'''Asignación de rol de Revisor a un usuario''']]
[[File:Certification manager.JPG|thumb|'''Designación de Revisor al Proyecto''']]
* Si el usuario del [[Certifcation platform#reviewers|Revisor]] no tiene el rol requerido:
** Ingresar a la página especial [https://en.oho.wiki/wiki/Special:UserRights User Rights]
** Escribir el nombre del usuario y acceder a su información de rol, en ''Load user groups''
** Activar la casilla ''certification_reviewer''
** Guardar los cambios en ''Save user groups''
* Ir a la [[#project_page|página del Proyecto]], acción ''Edit'', pestaña ''Certification Manager''
* En los campos ''Reviewer 1 a 3'', seleccionar el usuario que será [[Certifcation platform#reviewers|Revisor]].
** Guardar los cambios en ''Save page''
 
 
 
 
 
 
 
 
 
 
 

=== Aprobación del Documento de certificación ===
Luego de que el [[Certifcation platform#cab-team|Equipo CAB]], ha realizado la emisión del [[Certification processes#obs|Documento de Certificación]], el [[Certifcation platform#coordinator|Coordinador]] debe realizar los trámites respectivos para la aprobación de dicho documento, lo cual incluye:
* Visto bueno y firma de Autoridades por parte de OHO.
* Visto bueno y firma de Autoridades por parte de ente certificador externo para la validación según [[DIN Spec 3105]].

== Revisores ==
Los [[Certifcation platform#reviewers|Revisores]] tienen la tarea de analizar técnicamenbte toda la documentación del Proyecto, para lo cual, deben haber pasado por el [[#sing-up|proceso de registro]] de la misma manera que en el caso del [[Certifcation platform#applicant|Aplicante]]. También debe contar con el rol de ''certificarion_reviewer'', como se indicó en [[#reviewers-designation|Designación de Revisores]].

Cada [[Certifcation platform#reviewers|Revisor]] debe cumplir con los aspectos mencionados a continuación:

=== Análisis de la Documentación Técnica ===
* Ingresar a la [[#project_page|página del Proyecto]].
* Analizar toda la información disponible, especialmente, las instrucciones de ensamblaje, lo cual incluye:
** Referencias correctas entre las partes de los [[Technical drawings]] y la [[Parts list]] .
** Procesos de fabricación para piezas especiales o medios de union bien explicados.
** Coherencia en la información mostrada, debe tener sentido en términos técnicos y de [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].

=== Emisión de no conformidades ===
[[File:Project comments.JPG|thumb|'''Comentarios en un proyecto''']]
[[File:Project action required.JPG|thumb|'''Item marcado como ''Action required''''']]
En la [[#project_page|página del Proyecto]], se pueden realizar comentarios sobre aspectos técnicos, estos comentarios son la canal en el que se emiten las no conformidades.

Se debe emitir un comentario o no conformidad en los siguientes casos:

* Falta información para poder clasificar o reconnocer alguna pieza o conjunto.
* Falta información sobre algún proveedor (los enlaces a sitios web tienden a ser modificados).
* Falta información sobre alguna pieza comprada, para poder ubicarla en los mercados actuales.
* Faltan medidas u otras especificaciones en los [[Technical drawings]].
* Falta de coherencia en las especificaciones, con respecto al ensamblaje de las piezas.
* Faltan campos en la [[#part_list|Lista de piezas]].
* Dependiendo del tipo de ensamblaje:
** Debe existir para cada pieza, un [[Technical drawings|plano en PDF]] y su respectivo [[CAD files|Archivo CAD]]. (esto último, con la finalidad de que se pueda revisar la información 3D en otoros sistemas CAD distintos del que haya generado las piezas).
** Las piezas de impresión 3D, deben estar acompañadas de su archivo STL, además de su [[Technical drawings|plano en PDF]] y su [[CAD files|Archivo CAD]].
** Para circuitos impresos (PCB), se debe incluir las direcciones de sus componentes.
* En caso de información confusa o errores evidentes, se debe dejar un comentario amigable, señalando la equivocación en el item que corresponda.
* En caso de problemas con respecto al Proyecto en general, hay un campo extra en la [[#part_list|Lista de piezas]], donde se pueden agregar comentarios.
* Aquellos items que requieran alguna corrección por parte del [[Certifcation platform#applicant|Aplicante]], deben ser marcados como ''Action required'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''
* Este proceso se puede repetir mientras existan comentarios o no conformidades con correcciones por realizar y no esten aprobados todos los items de la [[#part_list|Lista de piezas]], a través de la cual, siempre se debe mantener comunicación con el [[Certifcation platform#applicant|Aplicante]].
=== Aprobación del Proyecto ===
[[File:Project aproved.JPG|thumb|'''Item marcado como ''Approved''''']]
Luego de que se han resuelto, todas las no conformidades, se debe:
* Marcar cada uno de los item en la [[#part_list|Lista de piezas]] como ''Approved'', en la [[#project_page|Página del proyecto]], acción ''Edit'', pestaña ''Part list''.
* Agregar un comentario final que incluya 'OK, FINISHED'.
* Notificar al [[Certifcation platform#coordinator|Coordinador]], sobre la Aprobación del Proyecto.
== Equipo de evaluación de conformidad (CAB) ==
El [[Certifcation platform#cab-team|Equipo CAB]] tiene acceso los datos de contacto de los [[Certifcation platform#reviewers|Revisores]] y del [[Certifcation platform#applicant|Aplicante]], pudiendo siempre intervenir en la resolución de no coformidades y obteniendo información directa para la emisión del [[Certification processes#obs|Documento de Certificación]].
=== Validación de información del Aplicante y los Revisores ===
Entre algunas de las actividades del [[Certifcation platform#cab-team|Equipo CAB]], se tiene:
* Verifica algunas formalidades del Proyecto.
* En conjunto con el [[Certifcation platform#coordinator|Coordinador]] Apertura el [[Certification processes]] ya que participa en la [[#reviewers-designation|Designación de Revisores]].
=== Emisión del Documento de Certificación ===
Una vez que el [[Certifcation platform#applicant|Aplicante]] haya ingresado toda la [[#docs-upload|Documentación técnica]], al menos dos veces, el [[Certifcation platform#cab-team|Equipo CAB]] puede emitir una certificación donde se valide el cumplimiento de la [[DIN Spec 3105]]. Esto culmina el proceso de revisión, el cual pudiera ser abierto si:
* Alguna persona presenta quejas ante el [[Certifcation platform#cab-team|Equipo CAB]] por:
** La publicación de la documentación ya no es accesible total o parcialmente.
** Los términos de la licencia se han modificado y ya no cumplen con los requisitos de la norma [[DIN Spec 3105]].
** Cualquier información relevante ha sido alterada o eliminada de la [[Certifcation platform]].
* Teniendo en cuenta la importancia de las quejas presentadas, el [[Certifcation platform#cab-team|Equipo CAB]] puede anular la certificación en curso y volver a abrir el [[Certification processes]] una nueva revisión de la [[Technical documentation]].
* El [[Certifcation platform#applicant|Aplicante]] puede subir nuevamente documentación que ya ha sido certificada y aprobada, en este caso, la misma no requiere ser revisada otra vez.

DIN Spec 3105

2021-02-23T13:24:05Z

Robert: /* Referencias */

== Aspects of the DIN 3105 Standard ==
[[File:DIN-Logo.png|thumb|'''Article of the [https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History German Institute for Standardisation DIN''']]]
In general terms, DIN 3105 provides very generic requirements for the contents of the documentation, which give flexibility to develop and define a product as [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware]
Moreover, it is the first standard that has been adopted by a standardization body, such as [https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History DIN (German Institute for Standardisation)]. This adoption has been through an open-source license, which means that the standard can be accessed, copied and distributed free of charge and, after a registration process, subsequent versions of this standard can be developed in open processes in an innovative and democratic way.

This standard is structured in two parts:

=== DIN Spec 3105-1 - Requirements for the technical documentation ===
* Provides an explicit and workable definition of the definition of [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].
* Sets out the requirements that the documentation of a piece of hardware must meet in order to be legitimately classified as Open Source Hardware.
* Defines the minimum set of information that developers must share so that "anyone can study, modify, distribute, manufacture and sell" their hardware, as required by the [https://www.oshwa.org/ OSHWA] definition.

=== DIN Spec 3105-2 - Community based certification ===
* Defines an innovative community-based certification procedure that offers a middle way between self-certification and third-party certification.
* Certifications are not granted by a central body, but by the community itself [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].
** Developers or manufacturers of hardware [[Certifcation platform#applicant|Applicant]] can submit their Project documentation to a neutral body, in this case OHO.
** OHO appoints members of the community ([[Certifcation platform#reviewers|Reviewers]] and [[Certifcation platform#cab-team|Conformance assessors]]) to perform reviews of the Project.
** Based on the reviews, a [[Certification processes#obs|Certification document]] is issued.

== References ==
Both parts of DIN 3105 can be found in the following links:
* [[https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 DIN Spec 3105-1]]
* [[https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 DIN Spec 3105-2]]

DIN Spec 3105

2021-02-23T13:23:03Z

Robert: /* Aspectos de la Norma DIN 3105 */

== Aspects of the DIN 3105 Standard ==
[[File:DIN-Logo.png|thumb|'''Article of the [https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History German Institute for Standardisation DIN''']]]
In general terms, DIN 3105 provides very generic requirements for the contents of the documentation, which give flexibility to develop and define a product as [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware]
Moreover, it is the first standard that has been adopted by a standardization body, such as [https://en.wikipedia.org/wiki/Deutsches_Institut_f%C3%BCr_Normung#History DIN (German Institute for Standardisation)]. This adoption has been through an open-source license, which means that the standard can be accessed, copied and distributed free of charge and, after a registration process, subsequent versions of this standard can be developed in open processes in an innovative and democratic way.

This standard is structured in two parts:

=== DIN Spec 3105-1 - Requirements for the technical documentation ===
* Provides an explicit and workable definition of the definition of [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].
* Sets out the requirements that the documentation of a piece of hardware must meet in order to be legitimately classified as Open Source Hardware.
* Defines the minimum set of information that developers must share so that "anyone can study, modify, distribute, manufacture and sell" their hardware, as required by the [https://www.oshwa.org/ OSHWA] definition.

=== DIN Spec 3105-2 - Community based certification ===
* Defines an innovative community-based certification procedure that offers a middle way between self-certification and third-party certification.
* Certifications are not granted by a central body, but by the community itself [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].
** Developers or manufacturers of hardware [[Certifcation platform#applicant|Applicant]] can submit their Project documentation to a neutral body, in this case OHO.
** OHO appoints members of the community ([[Certifcation platform#reviewers|Reviewers]] and [[Certifcation platform#cab-team|Conformance assessors]]) to perform reviews of the Project.
** Based on the reviews, a [[Certification processes#obs|Certification document]] is issued.

== Referencias ==
Ambas partes de Norma DIN 3105 se pueden encontrar en los siguientes enlaces:
* [[https://www.beuth.de/en/technical-rule/din-spec-3105-1/324805763 DIN Spec 3105-1]]
* [[https://www.beuth.de/en/technical-rule/din-spec-3105-2/324805750 DIN Spec 3105-2]]

Certification platform

2021-02-23T12:29:17Z

Robert: /* Beneficios */

== Description ==
[[File:OHO info home1.JPG|thumb|''''[https://oho.wiki/wiki/ Home Page]''']]
OHO has a certification process, through which it is possible to formalize the documentation of each project, this provides technical and administrative support to the quality of the work done, through the application of internationally recognized standards, such as [[DIN Spec 3105]].

When a project is certified, it undergoes a review process and, after a positive examination, a document is issued that certifies or validates the information contained in it.

== Participants ==
For the certification process to be carried out, the action of the following entities, all active users of the OHO platform, is necessary:

<div id="applicant"></div>
=== Applicant ===
This is the person or organization interested in certifying their project.
* Must present a Project [https://es.wikipedia.org/wiki/Hardware_libre Open Hardware].
* Must provide the technical information of the Project, necessary for its realization.
* Must have the [[Technical drawings]] of the Project, which will be submitted for review.
* In case the Applicant does not have the [[Technical drawings]], OHO can provide the [[#benefits|CAD design service]].

<div id="reviewers"></div>
=== Reviewers ===
It is a group of people, accredited by OHO, who are in charge of examining in detail the Project documentation, especially the [[Technical drawings]], in order to indicate to the [[#applicant|Applicant]], which aspects must be corrected in the project.
* They must have a ''certification_reviewer'' role on the OHO platform.
* They must have general or specific knowledge about the project to be reviewed.
* The number of reviewers depends on the length and complexity of the project, a minimum of three (03) is established.

<div id="coordinator"></div>
=== Coordinator ===
Is the person or authority in OHO, in charge of activating, monitoring and controlling the certification process.
* Must have an ''administrator'' role in the OHO platform.

<div id="cab-team"></div>
=== Conformity assessment team (CAB) ===
It is a group of people, accredited by OHO, who are in charge of validating the information of the [[#applicant|Applicant]] and the [[#reviewers|Reviewers]], as well as issuing the certification document.
* They must have a ''certification_body'' role on the OHO platform.
* They must have general knowledge about the project to be reviewed.
* The number of conformity assessors depends on the extension and complexity of the project, a minimum of one (01) is established.
*

== Start of the process ==
The certification process starts with:
* The request of the [[#applicant|Applicant]] of the Project who must fill in the [[Request certification for your project]] form, and then proceed with the [[#reviewers|Reviewers]] and the [[#cab_team|Compliance assessment team]].
* Designation of the [[#reviewers|Reviewers]] and the [[#cab_team|Conformity Assessment Team (CAB)]] by the [[#Coordinator|Coordinator]].
* From this starts the [[Certification processes]]

<div id="benefits"></div>

== Benefits ==
Many projects with great potential lack good technical documentation and even more so a document that provides international validation.

In this sense, the OHO platform offers any developer the possibility to certify or validate his project under the [[DIN Spec 3105]] standard, bringing with it the following benefits:
* A certified Open Hardware project can be clearly differentiated from other initiatives that do not lead to real solutions, which increases the chances of being found by the internet public.
* Certification according to [[DIN Spec 3105]] makes it possible to know the requirements necessary to designate a project as Open Hardware and to update its documentation.
* The certification of more and more projects defines and clarifies a frame of reference for the Open Hardware community about the concept and trends in this type of projects, a frame of reference backed by a globally recognised authority.
* Both the certification process and the CAD design service and technical documentation, provided by OHO, are completely free of charge.
* A certified project has greater possibilities of networking in different groups of the Open Hardware community, which generates opportunities to scale the project and access possible sources of funding.