|
|
| (5 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| == Overview of instructions according to the role in the OHO ==
| | [[de:Anleitungen_zur_Zertifizierung]] |
| | [[es:Instrucciones_para_la_certificación]] |
| The instructions to follow for the [[Certification processes]], will depend on the participant and his role in the process. | | 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: | | Here are the specific procedures for each role in the certification of a project: |
| | | <div id="inst-app"></div> |
| <div id="applicant"></div> | | * [[Instructions for Applicant]] |
| | | ** [[Instructions for Applicant#Registration on the Certification Platform|Registration on the Certification Platform]] |
| == Applicant ==
| | ** [[Instructions for Applicant#Uploading technical documentation|Uploading technical documentation]] |
| The [[Certification platform#applicant|Applicant]] initiates and terminates the [[Certification processes]], for which it must comply with the following procedures:
| | ** [[Instructions for Applicant#Request certification for the Project|Request certification for the Project]] |
| [[File:Applicant account new.JPG|thumb|<small>'''User account creation'''</small>]]
| | ** [[Instructions for Applicant#Project Corrections|Project Corrections]] |
| <div id="sing-up"></div>
| | ** [[Instructions for Applicant#Receipt of the Certification Document|Receipt of the Certification Document]] |
| === Registration on the Certification Platform ===
| | <div id="inst-rev"></div> |
| The [[Certification platform#applicant|Applicant]] must be registered with OHO, via: <br>
| | * [[Instructions for Reviewers]] |
| https://en.oho.wiki/wiki/Special:CreateAccount <br>
| | ** [[Instructions for Reviewers#Analysis of Technical Documentation|Analysis of Technical Documentation]] |
| <br>
| | ** [[Instructions for Reviewers#Release of non-conformities|Release of non-conformities]] |
| <br>
| | ** [[Instructions for Reviewers#Project Approval|Project Approval]] |
| <br>
| | <div id="inst-cab"></div> |
| <br>
| | * [[Instructions for CAB Team]] |
| <br>
| | ** [[Instructions for CAB Team#Validation of Applicant and Reviewers information|Validation of Applicant and Reviewers information]] |
| | | ** [[Instructions for CAB Team#Issuance of the Certification Document|Issuance of the Certification Document]] |
| <div id="data_upload"></div>
| |
| ==== Project data upload ====
| |
| [[File:Applicant project basic.JPG|thumb|<small>'''Basic data'''</small>]]
| |
| 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<br>.
| |
| 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|<small>'''Additional fields'''</small>]]
| |
| ** 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|<small>'''Part List Fields'''</small>]] | |
| | |
| <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.<br><br><br><br>
| |
| ** It can be entered manually by filling in each information field for each item in the list.[[File:Partlist-structured.jpg|thumb|<small>'''CSV file'''</small>]]<br><br><br><br><br><br><br><br>
| |
| ** 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. '''<br><br><br><br><br><br><br><br><br><br><br><br><br><br>
| |
| * [[CAD files]], [[Technical drawings]] and Other documents: [[File:Applicant project docs.JPG|thumb|<small>'''Technical documentation entry'''</small>]]
| |
| ** 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]].
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| | |
| | |
| === Request certification for the Project ===
| |
| After uploading the [[Technical documentation]] of the Project, the [[Certification 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 [[Certification 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|<small>'''Comments on a project'''</small>]]
| |
| If during the review of the Project documentation, the Reviewers team issues any non-conformities (''Reviews''), the [[Certification platform#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 [[Certification 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 [[Certification platform#reviewers|Reviewers]].
| |
| * Corrections must be made in a timely manner, in order to expedite the certification process.
| |
| * The [[Certification 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 [[Certification platform#applicant|Applicant]], of the [[Certification processes#obs|Certification Document]], for which it is contacted by the [[#project_page|established channels]].
| |
| * The [[Certification platform#applicant|applicant]] must read in detail the document to be received.
| |
| * The [[Certification platform#applicant|applicant]] must accept the terms of the document.
| |
| * Finally, the [[Certification 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 [[Certification 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|<small>'''Assignment of Assessor role to a user'''</small>]]
| |
| The [[Certification platform#cab-team|CAB-team]] must be designated and activated, once the [[Certification 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 [[Certification platform#reviewers|Reviewers]].
| |
| | |
| For each member of the [[Certification platform#cab-team|CAB-team]], the following must be fulfilled:
| |
| *If the [[Certification 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 [[Certification platform#coordinator|Coordinator]] must contact each member of the [[Certification 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|<small>'''Assigning a Reviewer role to a user'''</small>]]
| |
| [[File:Certification manager.JPG|thumb|<small>'''Designation of Reviewer to the Project'''</small>]]
| |
| * If the [[Certification platform#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 [[Certification platform#reviewers|Reviewer]].
| |
| ** Save the changes in ''Save page''.
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| <br>
| |
| | |
| === Approval of the Certification Document ===
| |
| After the [[Certification platform#cab-team|CAB-team]], has issued the [[Certification processes#obs|Certification Document]], the [[Certification 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 [[Certification 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 [[Certification platform#applicant|Applicant]]. It must also have the role of ''certificarion_reviewer'', as indicated in [[#reviewers-designation|Reviewer designation]].
| |
| | |
| Each [[Certification 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|<small>'''Comments in a project'''</small>]]
| |
| [[File:Project action required.JPG|thumb|<small>'''Item marked as ''Action required'''''</small>]]
| |
| 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 [[Certification 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 [[Certification platform#applicant|Applicant]] must always be maintained.
| |
| === Project Approval ===
| |
| [[File:Project aproved.JPG|thumb|<small>'''Item marked as ''Approved'''''</small>]]
| |
| 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 [[Certification platform#coordinator|Coordinator]], about the Project Approval. | |
| | |
| == Conformity Assessment Board (CAB Team) ==
| |
| The [[Certification platform#cab-team|CAB-team]] has access to the contact details of the [[Certification platform#reviewers|Reviewers]] and the [[Certification 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 [[Certification platform#cab-team|CAB-team]], include:
| |
| * Verify some formalities of the Project. | |
| * In conjunction with the [[Certification platform#coordinator|Coordinator]], it opens the [[Certification processes]] as it participates in the [[#reviewers-designation|Reviewers-designation]]. | |
| === Issuance of the Certification Document ===
| |
| Once the [[Certification platform#applicant|Applicant]] has entered all [[#docs-upload|Technical documentation]], at least twice, the [[Certification 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 [[Certification 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 [[Certification platform]].
| |
| * Taking into account the importance of the submitted complaints, the [[Certification platform#cab-team|CAB-team]] can cancel the ongoing certification and reopen the [[Certification processes]] a new revision of the [[Technical documentation]].
| |
| * The [[Certification 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.
| |
