{"id":5215,"date":"2023-03-17T12:30:47","date_gmt":"2023-03-17T12:30:47","guid":{"rendered":"https:\/\/emperor-os.com\/?p=5215"},"modified":"2023-03-29T06:06:09","modified_gmt":"2023-03-29T06:06:09","slug":"5-tips-to-equip-your-technical-documentation-for","status":"publish","type":"post","link":"https:\/\/emperor-os.com\/5-tips-to-equip-your-technical-documentation-for.html","title":{"rendered":"5 Tips to equip your “technical documentation” for the worst case scenario"},"content":{"rendered":"
Time and again, customers approach us with the question: How do we best organize our CE documentation in order to be prepared in the event of damage and to have the proverbial "good papers" when dealing with a regulatory authority or in a legal dispute??<\/p>\n
For us, this is not an easy question to answer, because while every product usually goes through a CE process, the documents required can be highly individual and different. Because "machine is equal to machine" or "device is equal to device" is very rarely true.<\/p>\n
Nevertheless, I have tried to find an answer to the question. At the same time, I would be very happy if you share with us and the readers of this blog your experience and perspective on this topic. Simply use the comment function at the bottom of this page to do so.<\/p>\n
Whether it's the Machinery Directive, the Low Voltage Directive or the EMC Directive, all directives require the compilation of so-called "technical documentation". These documents are intended to "prove" that the product complies with relevant regulations and standards. Must be able to be presented to market surveillance upon request. Within the EU, these documents must be kept for at least ten years.<\/p>\n
Technical documentation includes u. a.:<\/p>\n
But simply having these documents is by no means sufficient. It must also be conclusively recognizable how the standards were implemented. This is especially important if, for example, only parts from standards were implemented.<\/p>\n
Let's put ourselves in the shoes of officials in the market regulator's office and imagine being presented with a thrown-together hodgepodge of documents:<\/p>\n
Documents lie scattered unsystematically in folders with no table of contents, date, or validity; documents, such as the risk assessment, are missing; standards referenced appear outdated ..
Immediately, inspectors become suspicious: does the manufacturer even have a functioning CE process in place? Reason enough to drill deeper.<\/p>\n
Of course, setting up the CE process first involves some initial effort. I'd be happy to hear about your experience with building a CE process in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"
Time and again, customers approach us with the question: How do we best organize our CE documentation in order to be prepared in the event of damage and…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"yoast_head":"\n