Le savoir contenu dans les FMEA (AMDEC)

La dernière version de la suite rationalK, logiciel de gestion de la connaissance pour les pme permet aux utilisateurs de capitaliser le savoir contenu dans les FMEA (ou AMDEC en français).

Les FMEA (process et design) sont un recueil de toutes les lessons apprises par la société. Cela à condition de contourner les problèmes suivants :

  • La FMEA d’un produit est sauvegardé dans un fichier excel perdu au fin fond des sous-dossiers windows.
  • Si la FMEA du produit est mise à jour, le fonctionnement avec fichier excel rend très fastidieux la mise à jour des autres produits similaires

Le module FMEA pour rationalK vous apporte les solutions suivantes :

  • Importez en deux clics vos FMEA de base (aussi appelées FMEA générique ou core FMEA)
  • Les éléments de la FMEA sont sauvegardé dans la base de donnée ce qui vous permet de rechercher à la google à travers les entrées de cette base
  • A partir d’une FMEA générique, vous pouvez en 4 clics, exportez une FMEA spécifique pour un produit particulier en se basant sur les similarités de production et de design

Toutes les informations sur rationalk.ch.
Télécharger rationalK et le module FMEA.

Le logiciel est open-source, donc vos commentaires et contributions sont les bienvenus.

Best practises for knowledge management in the industry

In the industry, more precisely the mechanical industry, the knowledge is everywhere, spread among everyone’s mind and hard drive. The challenge is to capitalise and re-use this knowledge to do better products at better prices.

A few basic principles that help managing knowledge :

  • Write guides (how-tos, users manuals,…). As soon as learn something, it is important to write it down. This document will be not only useful for your colleagues but also for you in case you forget how o do it. If you don’t have time to write a nice documentation, you should still open the manual, add the title and put one or two screenshots. This is enough in the action. Then later in the day, take some time to consolidate your texte and share it to colleagues.
  • Share documents you write. When you write a document of any kind (a procedure, a calculation report, …), share it ! Don’t just let it on your hard drive or inside a mail discussion between your customer and you. I my office, we have a list of document we wrote, as soon as a document is added each collegues get a mail notification that some new knowledge has been created. People can subscribe to document category and field of application to avoid spam.
  • Use follow-up or project logs extensively. Follow-up are important information concerning a project event (a project change, a new risk that pop-up,…). Writting a follow-up should be very quick if you want people to adopt this methodology. I saw in one company, people where using excel list to handle follow-up : people needed to open the windows explorer, find the corrsponding project in the tree view, open the excel file, scroll to the last line, fill in various fields and save the document. This is not the right approach. A powerful alternative would be a mini software or add-in that work like this : when I press Ctrl+F+U a windows pop-up, I type the project number, press enter, type some free text and press enter to finish. This should not take more than 15 seconds. More information on follow-up in rationalK
  • Use core-DFMEA and core-PFMEA. As soon as a risk is discover or a process failure occurs you need to store it somewhere. Even if you don’t have the solution to this new problem now. Core FMEA (or generic FMEA) are your basic template from which you derived new product FMEA. As a consequence they are a great place to store knowledge. As some of your curious customers will ask to get a copy of these documents to handle a different public version of these document with less internal knowledge. We have developed a handy tool to manage your FMEAs
  • Develop software and use databases. One of the best way to capture knowledge and to be sure it will be re-used is to give to your company software an access to it. A software can be as simple as an excel form. If you already have a software in place that use a database. Do not add new product information in a lost word document inside the ERP or your company intranet but add it instead directly into the database so that people can simply select it to re-use it. Keep the knowledge source in a static place and add a link from the database to the source in case someone need to extend this knowledge.
  • Use list of tagged documents. This function is part of any modern document managing system (whether you use rationalK or a windows folder).Try to avoid the folder and subfolder structure to store your document. At some point you will be torn appart because you won’t be able to determine if this document should be in this folder or in this other folder. You will start to duplicate documents. If you don’t know where to store your knowledge, imagine how difficult it will be for your colleagues to find something… Instead, create a list of document with title, link to the document and a tag list. Then since the document is linked inside the list, you can store them anywhere in the disk, it does not matter since you will access them using your list.
  • Convert emails. Emails convey a lot of non-formatted knowledge spread inside discussions. Emails are difficult to access for new project members or occasional project participants. If you cannot avoid to use them, do your best to convert them. The most simple way to convert emails into knowledge is to save them (as pdf or msg format) inside your project folder. A more elaborated way is to store each individual informations at their appropriate place : follow-up, fmea entry, risk register, calculation database, general documentation,…

rationalK et les documents associés

Il vous est maintenant possible d’associer un ou plusieurs documents à un document.

Avantages :

  • Grâce à cette fonction vous ne perdez aucune information
  • Pas de duplication de contenu
  • Plus de questionnement sans fin sur le lieu où vous devez enregistrer l’information
  • L’impact de modification d’un document sur les autres documents de votre base de savoir se mesure facilement

Si l’information que vous cherchez ne se trouve pas dans le document renvoyé par le moteur de recherche de rationalK vous avez la possibilité de naviguer dans les documents liés (documents associés).

Un exemple concret : il parait intéressant de lier le document intitulé : Matrice de choix des matériaux aux documents : Liste des matières plastiques et Liste des fournisseurs de matériaux.

Documents liés
Documents liés

Requirements Management & Compliance Matrix

A template for a Matrix of Compliance using excel.

Matrix of Compliance

Improvement possibilities :

  • There is no change tracking system in Microsoft Excel
  • If the customer send the specification document in pdf or word, the amount of work for the conversion into xls can be quite important.
  • There is (yet) no easy way to reuse knowledge from one product development to another

Going Paperless

This idea was going through my head for a couple of months and I am now determine to give it a try : Going Paperless. I would like to stop using notebooks at the office.

Motivations :

  • It’s green
  • It will probably contribute to a better management of my project notes
  • I could travel lighter
  • My paper book has a lack of functionalities :
    • I cannot use Ctrl+F to find in my paper notebook !
    • I can tag my notes but I cannot rearrange them by tags!
    • It is difficult to share my notes with colleagues.
    • I cannot paste pictures within my notebook.
    • If I lost my notebook in the train, I lost everything !
    • I have to retype everything when I am at my desk in front of my computer

What I think I need :

  • An ipad with sim card
  • The Evernote suite : Evernote, Penultimate, Skitch
  • A stylus
  • A keyboard for ipad
  • An Ipad case that can hold the keyboard and the stylus

I will start in september and keep you posted about how it goes and if I am missing the paper. Please if you have any suggestions feel free to post a comment below.


Une liste de mes brunchs et restaurants préférés à Lausanne.


  1. La Couronne d’Or
  2. L’Hermitage
  3. Le Café de Grancy
  4. Tom Café, au Musée Olympique
  5. Le café des Avenues
  6. La Café Saint Pierre


  1. Nadanam
  2. Brasserie du Palace
  3. L’Eléphant Blanc
  4. L’Orchidée
  5. Fratel e Napule


  1. Café des artisans
  2. Bar Tabac


  1. Le Café Saint Pierre
  2. Midi 20

Les prochains sur la liste à essayer :

  • L’Antica Trattoria
  • Le petit boeuf
  • Le Tramway

Pour d’autres adresses, visitez mon profil tripadvisor.

Bon Appétit.

Workflow for document approval

This post describes a simple workflow for document approval.

In a company, most of the time, documents need to be approved before sending to a customer or even before distributing it to colleagues.

The first things to do is to define roles :

  • A writer
  • A reviewer
  • An approver

The writer submit a document using the standard dms (document managing system)
During the upload he is asked to choose, among a list of person, a reviewer.

The list of reviewer should be based on the type of document and the content of document. The list should propose a list of expert users. This means that the list should be constructed in advance.

The document is uploaded with metadata :

  • date of submission
  • writer username
  • proposed reviewer username

The proposed reviewed is notified by email or in the dms dashboard that a document is pending for review.

Two options:

  1. The reviewer can review the document
  2. The review cannot review the document (for time reason or because he think that he is not the most suitable expert in this field)

In the first case, the reviewer has the following options :

  • Mark the document as ok for approval
  • Correct the document, upload the corrected version and mark as ok for approval
  • Ask the writer to modify the document and gives him his comments and mark the document as awaiting writers corrections

to be continued