Quick start SKILL FMEA PRO - Skill Software€¦ · Quick start SKILL FMEA PRO ... 4.2 Product nomenclature _____30 4.3 Creation / modification of the ... the software is adapted

SKILL SOFTWARE – ZAC des Portes du Dauphiné – 55 chemin de Mure – 69780 Saint Pierre de Chandieu – FRANCE

+33 (0)472.48.24.80 - +33(0)472.48.24.89 - www.skillsoftware.com

Page 1

Quick start

SKILL FMEA PRO

V7.0



Page 2

Table of content 1 ADMINISTRATOR ________________________________________________________4

1.1.1 Delete password ______________________________________________________________ 4 1.1.2 Delete password in transversal audit _______________________________________________ 5 1.1.3 Site _________________________________________________________________________ 5 1.1.4 Profile _______________________________________________________________________ 5 1.1.5 Profile _______________________________________________________________________ 6 1.1.6 Application language ___________________________________________________________ 7 1.1.7 SMTP server _________________________________________________________________ 7 1.1.8 Colours management___________________________________________________________ 7 1.1.9 Access configuration ___________________________________________________________ 8 1.1.10 Registration __________________________________________________________________ 8

2 MANAGER _____________________________________________________________9 2.1.1 Glossary _____________________________________________________________________ 9 2.1.2 Evaluation grid _______________________________________________________________ 14 2.1.3 Multiple RPN scale____________________________________________________________ 15 2.1.4. Matrix scale creation _____________________________________________________________ 15 2.1.4 List ________________________________________________________________________ 17 2.1.5 Catalogues / principles_________________________________________________________ 19 2.1.6 Responsible _________________________________________________________________ 22 2.1.7 Report name ________________________________________________________________ 23 2.1.8 SCC _______________________________________________________________________ 23

3 USER DESIGN – PROCESS - MACHINE _____________________________________24

3.1 General interface _______________________________________________________24

3.2 Information, general attributes ____________________________________________24

3.3 Meeting management ___________________________________________________27

4 QUICK START - DESIGN FMEA ____________________________________________29

4.1 Functional analyses _____________________________________________________29 4.1.1 Life situation _________________________________________________________________ 29 4.1.2 Functions ___________________________________________________________________ 29 4.1.3 Criterion ____________________________________________________________________ 29

4.2 Product nomenclature ___________________________________________________30

4.3 Creation / modification of the nomenclature _________________________________31

4.4 Import of components ___________________________________________________32

4.5 Functions / components matrix in design FMEA ______________________________33

4.6 Function / component matrix in preliminary analysis __________________________33

4.7 Design FMEA analysis ___________________________________________________34 4.7.1 Design FMEA vocabulary ______________________________________________________ 34 4.7.2 Failures in design FMEA _______________________________________________________ 35

5 CREATION OF ACTIONS _________________________________________________36

5.1 Link actions ___________________________________________________________37

5.2 Actions plan follow up ___________________________________________________38

6 QUICK START PROCESS FMEA ___________________________________________44

6.1 Manufacturing diagram __________________________________________________44

6.2 Process FMEA analysis __________________________________________________46 6.2.1 Vocabulary __________________________________________________________________ 46 6.2.2 Operations partitioning _________________________________________________________ 46

6.3 Operations / components matrix in process FMEA ____________________________47

6.4 Type of display in process FMEA __________________________________________47



Page 3

6.4.1 Operation > Mode > Characteristic _______________________________________________ 48 6.4.2 Operation > Characteristics > Mode ______________________________________________ 50 6.4.3 Operation > process parameter __________________________________________________ 51

7 CONTROL PLAN _______________________________________________________52 7.1.1 Multiple monitoring ____________________________________________________________ 54 7.1.2 Duplication of monitoring or control plan ___________________________________________ 56 7.1.3 Levels of Control plan AIAG ____________________________________________________ 58

7.2 Printout & reports ______________________________________________________61

8 FMEA FILES HANDLING _________________________________________________63

8.1 Specific FMEA _________________________________________________________63

8.2 Global handling on an FMEA _____________________________________________65 8.2.1 Delete action ________________________________________________________________ 65 8.2.2 Reset action _________________________________________________________________ 65 8.2.3 Set evaluation to maximum _____________________________________________________ 65 8.2.4 List of rejected / archived actions ________________________________________________ 65 8.2.5 Reallocate actions ____________________________________________________________ 66 8.2.6 Delete control plan ____________________________________________________________ 66 8.2.7 Protect with password _________________________________________________________ 66 8.2.8 Display confidentially __________________________________________________________ 67 8.2.9 Statistics ____________________________________________________________________ 67

8.3 Generic and specific FMEA _______________________________________________68 8.3.1 Creation of a generic FMEA ____________________________________________________ 69 8.3.2 Capitalization Generic > Specific _________________________________________________ 70 8.3.3 Call generic > Specific _________________________________________________________ 72 8.3.4 Automatic capitalization ________________________________________________________ 73 8.3.5 Send an alarm to the specific FMEA pilot for updating ________________________________ 74 8.3.6 Automatic synchronization of a specific FMEA from a generic __________________________ 75 8.3.7 Generic / Template / Specific ____________________________________________________ 77

8.4 FMEA translation _______________________________________________________79 8.4.1 Translation inside the FMEA ____________________________________________________ 79 8.4.2 Translation into the catalogue ___________________________________________________ 79

9 TRANSVERSE AUDIT ____________________________________________________80

9.1 Functionnalities _____________________________________ Erreur ! Signet non défini. 9.1.1 Add, Edit, Delete a query _______________________________________________________ 80 9.1.2 Execute a query / question _____________________________________________________ 82

10 COPY/PASTE INTO AN FMEA _____________________________________________83

10.1 Drag & Drop simple _____________________________________________________83

10.2 Drag & Drop double _____________________________________________________84

11 ADVANCED FUNCTIONNALITIES __________________________________________85

11.1 Design risk ____________________________________________________________86

11.2 Manufacture risk _______________________________________________________86

11.3 Risk control plan _______________________________________________________86



Page 4

1 ADMINISTRATOR All users must be not connected

The administrator connection allows you to define some technical parameters of Skill FMEA Pro. It is a « computer specialist profile »

Login Admin Password (default is no password)

The Parameters menu groups the entire accessible functions in the administrator mode.

1.1.1 Delete password

All folders protected by a password are displayed in the list. To delete a password, select a folder and press the button « delete »



Page 5

1.1.2 Delete password in transversal audit

All queries protected by a password are displayed in the list To delete a password, select a query and press the button « delete »

1.1.3 Site

At least one site must be created. Replace the default site of “Lyon”, by your site description. The company logo will be printed on all reports generated by the software. If the multi sites option, has been activated in your decoding licence key, you can created several sites

1.1.4 Profile The cell 1 to 10 correspond to a software screen If a cell is checked, the user profile will allows modifications is that screen. A user is linked to a user profile.



Page 6

1.1.5 Profile

The user list is displayed Double click to modify a user, or button Add to create a new user.

For each user, different level of access can be adjusted. - Each user belongs to a profile, and a site. The user can validate action (recommended) Send E-mail actions: (recommended) Modification of labels: (recommended, to advanced user) If a label is modified, it affects all FMEA folders using it. Final RPN modifications, during the action follow up, if that matches your organization. …

Options:

In the users list, the Option Button allows to define a mandatory password, with a defined length



Page 7

1.1.6 Application language

You can define 5 simultaneous languages for the software, among the available languages During the modification of a language, a reset of the glossary is done.

1.1.7 SMTP server

Define the address of the server to be used for action follow up, and meeting scheduling. Each different site, can be connected to its own SMTP server. Please contact our technical support for more detail

1.1.8 Colours management For each area of the screens, a

specific colour can be defined The colour assigned are the

same for all users connected afterward

To reduce the data flow with Citrix, Win TSE, it is recommended to use a set of pure colour.



Page 8

1.1.9 Access configuration

Display the path of the database. The compact button, only activated for an Access database, is used to compact the size of the database

1.1.10 Registration Contact our technical support to obtain a decoding corresponding to your order.



Page 9

2 MANAGER All users must be not connected The Manager connection allows parameterisation of functional options and features of the software. It is a « quality profile » Login Manager Pass word (no password by default)

The parameters menu groups all functions available in the Manager mode.

2.1.1 Glossary It groups the vocabulary used by the software, and adjusts some functional parameters.



Page 10

« General »

- Definition of vocabulary - Criticality class The steps of the RPN limits are defined for the graphic analysis. The « product » section is used for the design and process FMEA. The « Machine » section is used for the means/machine FMEA.

« Design/manufacture » »

- Global vocabulary used by the design and process FMEA



Page 11

« Component / Machine FMEA » -Global vocabulary used for component. The components exist into the design/process FMEA, and into the Machine FMEA too.

« Failure » Action status The level of action is defined for each company, The validation level is the trigger for changing colours of the failure screen. (A) AIAG

The new release of the AIAG requires printing a message when no action is declared on a failure.

(A) The administrator can give a user, the right to select that validation level inside the action plan follow up.



Page 12

« Monitoring plan » - The header of column is defined for the Skill FMEA Pro monitoring plan format. (Non AIAG)

« Headers » - Definition of the Skill Norm header. - The 4 left cell are printed en vertical size (portrait) - All cells are printed on an horizontal size (landscape)

« Occurrence » Frequencies or occurrences are used for the maintenance plan scheduling, linked to the components inside the design FMEA or inside the machine FMEA



Page 13

« Parameters » Some software adjustment to match your FMEA approach…

VDA

If that cell is checked, the software is adapted to the VDA requirements. The impacts are located on functions, operations, initial date of creation of a cause, in addition, for each action, you have the possibility to declare a final Occurrence, and Detection. In that case, the software keeps the lowest quotation declared Traceability

If that cell is checked, when you close the FMEA folder, it is proposes a revision date and index Allow update of dates/milestones in action plan follow up

You can authorize the modification of the start / end date of an action. Otherwise, they are defined into the MEA folder. Update of all specific folder from a generic

You can authorize the massive update of the specifics linked to a generic. It has to be used with caution. Expand/collapse

This option reduced the display of the data to speed up the program (To be used for importante volume of data FMEA Manufacture

If that cell is checked, the default display for the process FMEA is selected. Knowledge network

The lists are opened according the « knowledge network or experience ». It is recommended to keep it checked to have benefit of that feature. PPM

- This module will be removed, so it is deactivated by default. Dynamic folder

- This module will be removed, so it is deactivated by default.



Page 14

2.1.2 Evaluation grid

Definition on the evaluation grid or scale for design, process, machine FMEA. Two different type of scale exist, the single RPN, or multiple RPN (an RPN is defined for each step of the severity scale. All the scale is centralized. A default scale can be selected, with the button, and it will be automatically proposed at each creation of an FMEA

Single RPN scale: the RPN has a unique value

In that principle, the RPN has only one value, and each axis (severity, concurrency, detection may have its own alarm. If one of the alarms is reached, the information is displayed in red colour.

Generally, in design and process FMEA, no alarm is defined on the severity, because it cannot be reduced at the final quotation.

Single RPN grid The severity, occurrence, detection are defined The can be not continuous, or discontinuous (ex: 3-5-15) An alarm level is defined (value 8 in the example), and will switch the display in red colour in that case

1 2 3 4 5 6 7 8 9 10

Severity

3 5 15

Occurrency

1 4 6 8 12

Detection

36

RPN

1 2 3 4 5 6 7 8 9 10

Severity

3 5 15

Occurrency

1 4 6 8 12

Detection

36

RPN



Page 15

2.1.3 Multiple RPN scale

In that type of scale, a RPN value is defined for each severity value. In that type of scale, there is no alarm on the occurrence and detection axis.

Multiple RPN The principle is to assign a RPN value for each severity value.

2.1.4. Matrix scale creation

In Manager, you can create a new rating scale (Product, Manufacturing or Machine). A new type of grid is added to the mono-and multi-threshold threshold: with criticality matrix.

1 2 3 4 5 6 7 8 9 10Severity

3 5 15

Frequency

1 4 6 8 12

Detection

RPN

10

100

50

1 2 3 4 5 6 7 8 9 10Severity

3 5 15

Frequency

1 4 6 8 12

Detection

RPN

10

100

50



Page 16

As with any new grid, you need to set your rating scales for severity, frequency and detection in the first three tabs Note: the button "Duplicate" allows you to reuse an existing grid and rating scales. The last tab is for the criticality matrix. The two lists to create a mathematical equation representing a criticality "high" and "moderate." The "low" criticality is not described, it represents everything that is not defined in the other two equations. The VDA scale can taken as an example

The mathematical equation is as follows:



Page 17

2.1.4 List

These lists are used within various screens The most important one is the list of technical unit.

Milestone

An action can be planned with dates, or miles stones.

Action type This list is used to define an action. The VDA option has to be activated.

Office model The model and path are defined for printing.



Page 18

Role of participant.

This list is used to define for each attendee, the role during a meeting.

Unit This list is used for the functional criterion, product characteristic and process parameter

Class

This list is used by the machine FMEA module



Page 19

Influencing factor

This list is used for the causes definition when the VDA is activated.

2.1.5 Catalogues / principles 1- when a label/word is created inside an FMEA, it is created inside the catalogue.

2- when a label/word is modified inside the catalogue, all FMEA using it will be modified.

3- a user may have the right to modify dynamically a label/word inside an FMEA; this will affect all others

FMEA using the same word/label (same as principle N°2) (See chapter Administrator / User rights) At the beginning of the use of the software, it is important to bring attention in order to avoid the catalogues “pollution”: e.g., several terms with a different spelling. To correct and maintain the catalogue in a good level of quality, the “Take/merge” feature is available, and the “purge” function allows an automatic cleaning of the unlined word/label.



Page 20

The left part of the screen shows, the various headings: folder, design, process, component, etc… The right part, for each heading, shows the word/label existing inside the catalogue. In that example, the “functions” are displayed inside the “design FMEA” heading: For each language, a column is grouping all the words/labels

Purge

This feature deletes all terms stored in the catalogues, and not used in any folders. A term may not be linked to the catalogue, after a folder deletion, or the cancelling of a cell (operation function, effect, mode, cause) The purge function works depending the level of the selection

- Purge on process FMEA level: all terms non used will be deleted - Purge on the Effect level: all effects non-used will be deleted. - Purge on the « type of effect »: all terms on a sub type of effect are deleted.

Take/Merge

The operation consists of merging several words which are “the same” for the meaning” The first step in the example; select the two words « puisance” and “puissance”, and click on the button A (take) Some term may have been translated or not.



Page 21

The second step: select the word to be the target and click on the button A>B to merge them together. The windows displays all terms with their translation, by checking, you keep the best combination on each language

Area A : to locate all folder using a label Area B: to filter only labels of a folder Area C: to filter label including letter “vib” = “vibration”, or “strong vibration”, or “light vibration”



Page 22

A B C

2.1.6 Responsible

The responsibles are defined for a revision index, an FMEA meeting, and an action. Take / Merge: To

merge 2 same names, with a different spelling Select the 1st name, press Take, select the 2nd name, and press Merge.

List, when the

responsible is no more in activity, it will be not displayed during a choice, but all the history will be kept.



Page 23

Translation

Log in Manager mode, menu Parameter, option Catalogue For each cell, a spreadsheet is displayed with all terms and their existing translation. To limit the terms defined for one folder, you can select the folder you want to work with, and you can give for each term the equivalent in other language.

2.1.7 Report name

The report name/header is defined for - The folders - The dynamic folders - The other reports The user can define a specific name, which will be displayed on the menu, or the printouts. The name of report is modified in all languages handled.

2.1.8 SCC

The logos for special class characteristic are defined here. To add a logo, use the BMP format with a maximum size of 32x32 pixels



Page 24

3 USER DESIGN – PROCESS - MACHINE

3.1 General interface A B C D E F G

A Call a generic FMEA or capitalize into a generic FMEA B Insert cell, above, below, or delete a cell C Move a cell up or down in the graph D Insert or remove an SCC logo E General attributes of the FMEA F Meeting G Component nomenclature description

3.2 Information, general attributes

The user defines the Traceability, it will be printed in all the reports and analysis.



Page 25

If you click on the « evolution » button, the total amount of cause is displayed, and the amount co critical causes (in red colour) is displayed. The percentage is calculated.

The alarm level, for S, O, D can be modified inside the FMEA Limit >: beyond that value, the data is displayed in red colour. Limit <: beyond that value and below the limit >, the data is displayed in orange colour The orange value is a pre-alarm.

See chapter for associated documents



Page 26

Associated document You can link any windows format documents to various places inside the FMEA, on the following cells - Design FMEA: life situation, function, cause, detection, sub-system, component - Process FMEA: process step, operation, cause, detection, sub-system, component - Machine FMEA: sub-system, component, cause - detection

The list of all documents previously linked with an FMEA is displayed To select one or several documents just click on the check box. To add a new document, click on the add button.

This window allows getting with the explorer any document stored on your network.



Page 27

3.3 Meeting management

Click on button to add, edit or delete a meeting For each meeting, a location, start and end time is defined The object of the meeting and a comment are added



Page 28

On the right part the list of responsible is displayed, select the attendees of the meeting within that list, and

click on the blue arrow button, to load the corresponding meeting. To add a new responsible, click on the button “responsible management to add or edit a person.

To invite the attendees, just click on the button, a mail is sent to each person.



Page 29

4 QUICK START - DESIGN FMEA

4.1 Functional analyses A functional analysis should not describe the product characteristics, except for the installation life situation…

4.1.1 Life situation

The life cycle of the product groups all functions required by the client. A usual life cycle groups 5 or 7 life situation like: Example : Production, storage, transport, installation, active exploitation, passive exploitation, maintenance, recycling. You may add some others to adapt the theory to your particular application.

4.1.2 Functions

Functions: Action of a product or one of its components only expressed by the result. Use an infinitive verb to describe a result of a function.

Example function : « Resist to environmental constraints… », or « Transmit a torque… » In general a product is detailed by 25 to 50 functions, within all the life situations.

4.1.3 Criterion Each function is detailed by physical criterion to allow the description of the requirements. Each criterion is explained by a value and limits. Example of criterion: Weight 50 to 60 Kg @ 100%, Temperature de –30°C + 50°C, Storage 2 to 3 years.

- 80 % of criterions are « easy » to explain. - 10 % are complex due to the technology - 10 % are sometimes « subjective » to describe, « to be easy to use… »



Page 30

4.2 Product nomenclature The product nomenclature is shared by the design and the process FMEA. In the theory, the nomenclature is created at the design phase, and then is “produced” at the process phase.

The product nomenclature is accessed from the main screen describing the functions. Click on the button to display.

The product nomenclature is accessed from the main screen describing the operations. Click on the button to display.



Page 31

4.3 Creation / modification of the nomenclature

To create, update or delete, just double click on any line, or click the button.

The product description is defined in three levels. The sub-system, component, and the characteristic. This ultimate level will receive the links coming from the design and the process FMEA.

On each level of the nomenclature, use the button to Add, Edit, or Delete



Page 32

4.4 Import of components To handle the nomenclature, you can import sub systems, components, or characteristics existing inside other FMEAs.

In the example to import directly 2 components

- The first windows allows selecting from which folder, you will import.

- The second windows display all components existing inside the folder, you can select several of them.

By clicking the « select », these two components will be imported, with the entire characteristics



Page 33

4.5 Functions / components matrix in design FMEA Each component fulfils functions, and functions are fulfilled by components. The matrix can be defined during the preliminary analysis. In the example F1 is linked with C1/C2, C2, is linked with F1, F2, F3. During the design FMEA analysis, the key principle, to link a cause with one or several characteristics of components, has to be done The reverse is so determined: a characteristic can have an influence on several function through mode/cause.

4.6 Function / component matrix in preliminary analysis This step consists of linking component which fulfils function.

Function entity

- The life cycle is split into life situations, grouping functions and detailed by functional criterion.

CAUSE

MODE

Cri 3

Cri 2 F3

Cri 1

Cri 3

Cri 2 F2

Cri 1

Cri 3

Cri 2 F1

Cri1

FUNCTIONSCOMPONENTS

CLIENT

C3C2C1

Cha3

Cha2

Cha1

Cha3

Cha2

Cha1

Cha3

Char2

Cha1

CAUSE

MODE

Cri 3

Cri 2 F3

Cri 1

Cri 3

Cri 2 F2

Cri 1

Cri 3

Cri 2 F1

Cri1

FUNCTIONSCOMPONENTS

CLIENTCLIENT

C3C2C1

Cha3

Cha2

Cha1

Cha3

Cha2

Cha1

Cha3

Char2

Cha1



Page 34

Component entity

- The product is split into sub-system, grouping components, and detailed by physical characteristics (dimensions)

Function / Component matrix

- This matrix has to point out the links between component and function in a preliminary step. - A black cross shows the link between the function and the component.

4.7 Design FMEA analysis

4.7.1 Design FMEA vocabulary Mode: The lost of a criterion of a function. A mode is a non-performance sensed by the end user.

Cause: produces the mode (the origin of the mode)

- The cause is coming from one or several characteristics of the component, which fulfil the function. (e.g., the raw material is not adapted, the dimension are undersized..)

- The cause coming from a wrong realization in the process are not analysed during the design FMEA.

- As long as the cause is not explaining a characteristic of a component, the question “which characteristic is impacted” has to be asked.

- The worse cause could be “wrong design….” Effect: The consequence of the mode on the end user. Several effects can be produced by a mode, a

different user of the product. The effect is independent from the cause. Detection/Validation: The existing procedure to « stop » the cause.

- Lab test, calculation, simulator

- O: Occurrence: of the cause, so linked to the cause.

- S: Severity: of the most important effect if several are declared - D: Detection: Efficiency of the preventive measure to block the cause

- RPN i (initial) O x S x D (based on initial value of OSD) RPN f (final) O x S x D (based on final value of OSD)

Another way to establish such a link consists of linking these two entities during te FMEA analysis. The principle of in design FMEA, the cause is coming from one the characteristics of the component acting for a function”

To access the failure definition screen, select a criterion and click on the button as explained on the picture below. The general rule applies: A mode has several effects and the most important is quoted. (S) A mode has several causes, each cause has its own value of Occurrence (O) A cause has several detections and the most efficient is quoted (D) S x O x D give the initial RPN of the failure



Page 35

4.7.2 Failures in design FMEA

The 3 screens sequence allows the handling of the failure and action

- You can select one or several characteristics, to establish the link with the cause. - You can display, only the component linked previously in the matrix, or display the entire nomenclature.



Page 36

Print out, miscellaneous, function and component matrix

The colour of the cross, shows the criticality of the link, by the FMEA analysis. The matrix is dynamically filled during the link cause/characteristics when the FMEA is done.

5 CREATION OF ACTIONS



Page 37

For each cause where the initial RPN, is greater than the level of alarm, actions are taken to reduce the criticality.

An action has to reduce the final Occurrence or Detection (The severity remains the same)

The final RPN is taken into account, when all actions declared for the cause has the « ACT » level, i.e., the colour bleu for the cause is displayed.

5.1 Link actions



Page 38

The link button is clicked when another already existing action declared inside the FMEA, has to be used to reduce the criticality of the cause. A action can be linked to one or several causes in that case. Its status change will affect all causes linked

5.2 Actions plan follow up The action plan follow up is centralized, and accessed from the button on the left column. The drop down lists, or check buttons, allow the definition of the filters

Parameters available for the update of an action. - The Administrator can give a user the right to “close” the action, e.g. the move the status to the ultimate

level “Act…”, and allows the modification of the final quotation. - The Manager can authorize the start and end date modification during the follow up

1

2

3



Page 39

On the top of the screen, two tabs - Filter: define filters for selection - Result: the result of the filtered actions

The simplest way for an action plan follow up consists of

1- Select one FMEA folder (the result will display all actions “Non act” for an FMEA) 2- Select on responsible (the result will display all actions “Non-act”, for a responsible) 3- No filter (the result will display all actions “Non-act” from the database)

Click on the “Find” button to launch the request into the database Remark; the default filters

- “Non-act” status of action - End date is automatically at +7days from the today date.

In the example, an FMEA folder has been filtered, so all actions “Non act” are displayed

To update an action, just double click on the item



Page 40

During the update, only items can be modified Responsible, Action Taken, cost and comment Status can be raised to “Act”, and final quotation, if the Administrator has given the right to the user. Dates, if authorized by the Manager



Page 41

To send an alarm by e-mail, just click on the button, and add a subject

Some analysis available with print button

Action analysis by status



Page 42

Pie chart of quantity of action per statuts

Action analysis per responsible. For each responsible, the quantity of actions, with a color per each statuts

Form the main screen of action plan, the dashboard offers some analysis



Page 43

Performance of responsible This analysis is based on the End date (defined by the FMEA group) Date of the Act status If date of “Act” <= End date = GREEN If date of “Act” > End date = RED Tin the example, the first responsible has completed 75 % of actions within the delay, and 25% out of delay.



Page 44

6 QUICK START PROCESS FMEA

6.1 Manufacturing diagram See chapter 3.1 for the icon explanation This screen is used for the description of the process manufacturing diagram. It consists of post (machine) and operations. An operation obtains characteristics on the product.



Page 45

Principle

Example of a operation in process FMEA : Drilling of the hole « A », by starting with a mechanical drawing. The first step is basically, to start form the drawing, and highlight the characteristics obtained during the operation.

Product characteristics Mode Abs ++ -- NC

Cause

Diameter Non present Broken tool

Error program

Diameter too big ++ Wrong tool

Vibration on machine

Tool mounting

Diameter too small -- Wrong tool

Weared tool

Perpendicular Perpendicular NC Dirty base

Machine setting

Concentricity Concentricity NC Weared tool

Vibration on machine

Surface Surface NC Weared tool

Speed tool too fast

Vertical speed too fast

Dimension X Dimension X ++ Etc..

Dimension X -- Etc..

Dimension Y Dimension Y ++ Etc.

Dimension Y -- Etc..

6 CHARACTERISTICS

12 MODES 2 modes / characteristics

36 CAUSES 3 causes per mode

Y=

60

+/-

0,2

Z= 6

0 +/-

0,2

X= 90 +/- 0,2

Y=

12

+/-

0,1

X= 45 +/- 0,2

Z= 1

8 +/

- 0,2

Z= 1

8 +/-

0,2

Z= 1

8 +/

- 0,2

Y= 12 +/- 0,2

Ø= 8 +/- 0,02, Perp.= 2,

Ra=3, Conc=4

Ø= 8 +/- 0,02, Perp.= 2,

Ra=3,Conc=4

Matière= Acier X50

= Caractéristiques spéciales

A

BC

Y=

60

+/-

0,2

Z= 6

0 +/-

0,2

X= 90 +/- 0,2

Y=

12

+/-

0,1

X= 45 +/- 0,2

Z= 1

8 +/

- 0,2

Z= 1

8 +/-

0,2

Z= 1

8 +/

- 0,2

Y= 12 +/- 0,2

Ø= 8 +/- 0,02, Perp.= 2,

Ra=3, Conc=4

Ø= 8 +/- 0,02, Perp.= 2,

Ra=3,Conc=4

Matière= Acier X50


Y=

60

+/-

0,2

Z= 6

0 +/-

0,2

X= 90 +/- 0,2

Y=

12

+/-

0,1

X= 45 +/- 0,2

Z= 1

8 +/

- 0,2

Z= 1

8 +/-

0,2

Z= 1

8 +/

- 0,2

Y= 12 +/- 0,2

Ø= 8 +/- 0,02, Perp.= 2,

Ra=3, Conc=4

Ø= 8 +/- 0,02, Perp.= 2,

Ra=3,Conc=4

Matière= Acier X50


A

BC



Page 46

6.2 Process FMEA analysis

6.2.1 Vocabulary Mode: The lost of a product characteristic during an operation. The mode can be seen on the product.

Cause: produces the mode (the origin of the mode)

- The cause is generally coming from a process/machine parameters not correctly set. - As long as the cause is not highlighting a process/machine parameter, the question “which

parameter is influencing the default ?” has to be asked. - When the cause has reached the process/machine parameter, the “investigation” is stopped. The

next step would be a Machine FMEA, to determine which component of the machine is faulty. - Warning: “wrong machine setting”, such a global cause cannot help the risk analysis

Effect: The consequence of the mode, (independent of the cause) The concept of effect on the end user is sometimes hard to determine, it could be more analysed during the design FMEA.

Detection: the existing procedure or device to stop the cause (“Cause killer…”)

- Procedure or preventive action, or « Poka Yoke »

6.2.2 Operations partitioning

Two major rules apply during the process FMEA.

1- Each operation has to be analysed without taking into account the previous one., «The incoming piece is good, the out coming piece is good”. The default is created at the operation 2- In certain type of process, it can be impossible to detect the default at the operation for technological reason, but it is perfectly detected at an ulterior operation. In that case at an operation the detection is bad D=10, but it cannot reach the final client, and the detection is interiorly quoted at D=1. Between these two operations, a future scrap may be worked for nothing, that is the limit of the FMEA method.

OPERATION

N-1

OPERATION

N

OPERATION

N+1

PIECE

CorrectPIECE

Correct

PIECE

Correct

PIECE

Correct

D=10 D=1Detection after N step

OPERATION

N-1

OPERATION

N

OPERATION

N+1

PIECE

CorrectPIECE

Correct

PIECE

Correct

PIECE

CorrectOPERATION

N-1

OPERATION

N

OPERATION

N+1

PIECE

CorrectPIECE

Correct

PIECE

Correct

PIECE

Correct

D=10 D=1Detection after N step



Page 47

6.3 Operations / components matrix in process FMEA Rule # 1 An operations obtains one or several product characteristics Rule # 2

A characteristic can be obtained on one or several operation. Rule # 3

The value of the product characteristic is depending on the operation.

As a deduction, the mode is the lost of a product characteristic during an operation. In process FMEA, the mode is linked to one or several product characteristics.

6.4 Type of display in process FMEA Select the menu « view », to change the type of display

Op 3

Op2

Op 1

Par 3

Par 2

Par 1

Par 3

Par 2

Par 1

Par 3

Par 2

Par 1

OPERATIONS

CAUSEMODE

COMPONENTS

C3C2C1

Cha3

Cha2

Cha1

Cha3

Cha2

Cha1

Cha3

Char2

Cha1

Op 3

Op2

Op 1

Par 3

Par 2

Par 1

Par 3

Par 2

Par 1

Par 3

Par 2

Par 1

OPERATIONS

CAUSEMODE

COMPONENTS

C3C2C1

Cha3

Cha2

Cha1

Cha3

Cha2

Cha1

Cha3

Char2

Cha1



Page 48

6.4.1 Operation > Mode > Characteristic

This is an advanced level in FMEA, and applies in the « plastic industries, foundry.. ». The example shows an injection operation, where several characteristics are obtained at the same time, with the same mode.

LINK A MODE TO PRODUCT CARACTERISTICS

In that sequence, it makes sense to define first the mode, and then link the impacted characteristic Example injection « The 4 diameters can be non present due to a broken tool inside the machine”

Ø N° 4

- Broken tool

- Wounded tool

Missing

Ø –Ø N° 3

Ø N° 2

Ø N° 1

Cause Mode Product carac

Ø N° 4

- Broken tool

- Wounded tool

Missing

Ø –Ø N° 3

Ø N° 2

Ø N° 1

Cause Mode Product carac

Ø N° 1

Ø N° 4Ø N° 3

Ø N° 2Ø N° 1

Ø N° 4Ø N° 3

Ø N° 2



Page 49

Remark: A mode linked to a product characteristic is displayed with a yellow background. The link between the mode and the characteristic is not mandatory…



Page 50

6.4.2 Operation > Characteristics > Mode

It is another advanced level of FMEA, used for « mechanical industries », where different characteristics are obtained during an operation

LINK A MODE TO SEVERAL CHARACTERISTICS

In that sequence, after defining the operation, the list of the characteristics obtained is linked to the operation. 1- Create the operation “Drilling”

2- Click the button and select the appropriate characteristic with the check box

Z ++

Z --

Z= 18 +/- 0,2

Y ++

Y --

Y= 12 +/- 0,1

X ++

X --

X= 45 +/- 0,2

Conc NCConc=4

- Tool speed too slow

- Drilling speed too fast

- Wonded tool

- Manque No lubrication

Ra ++

Ra --

Ra=3

Perp NCPerp.= 2,

Missing

Ø ++

Ø --

Ø= 8 +/- 0,02

Cause Mode Product charac.

Z ++

Z --

Z= 18 +/- 0,2

Y ++

Y --

Y= 12 +/- 0,1

X ++

X --

X= 45 +/- 0,2

Conc NCConc=4

- Tool speed too slow

- Drilling speed too fast

- Wonded tool

- Manque No lubrication

Ra ++

Ra --

Ra=3

Perp NCPerp.= 2,

Missing

Ø ++

Ø --

Ø= 8 +/- 0,02

Cause Mode Product charac.

Y=

12

+/-

0,1

X= 45 +/- 0,2

Z= 1

8 +/

- 0,2

Ø= 8 +/- 0,02

Perp.= 2,

Ra=3

Conc=4

A

Y=

12

+/-

0,1

X= 45 +/- 0,2

Z= 1

8 +/

- 0,2

Ø= 8 +/- 0,02

Perp.= 2,

Ra=3

Conc=4

A

Y=

12

+/-

0,1

X= 45 +/- 0,2

Z= 1

8 +/

- 0,2

Ø= 8 +/- 0,02

Perp.= 2,

Ra=3

Conc=4

A



Page 51

3- The characteristic are now, linked with the operation

For each characteristic obtained at the operation, click the button to access to the failure screen, and defined the mode linked to the characteristic.

6.4.3 Operation > process parameter

This type of display is handled to define the process parameter for the operation. These are the setting of the machine like tool speed, pressure, temperature required to obtain a good product characteristics. The process parameters belong to the machine.

Process parameter can be added too, during the control plan definition



Page 52

7 CONTROL PLAN The control plan feature can be accessed at any time by clicking the icon from the main screen of operations. The control plan groups

- The product characteristics previously defined. - The process parameters previously defined.

Nevertheless, during the control plan sequence you can add additional product characteristics or process parameters

A-B: two independent standard to define the control plan, The « Skill » norm is using the header defined in

a manager connection, the AIAG norm is defined inside the software to follow the AIAG. C: To add process parameters on operation D: To link additional product characteristics E : Control sequence definition. To determine the sequence used for control by the operator.

B A

E

C D



Page 53

A Skill norm

The header are defined by the manager. The 2 norms are independent. Note that you can modify the value of the characteristic at the operation.

B Norme AIAG The headers are « hard coded » in the software and cannot be modified. The 2 norms are independent. Note that you can modify the value of the characteristic at the operation.

C Process parameter

You can add a process parameter on the control plan features.



Page 54

D Product

characteristics You can also add other characteristics on that screen if required.

7.1.1 Multiple monitoring

In order to optimize the various referential, this new version allows defining several monitoring on a product characteristic or a process parameter. Example:

- The operator checks the 1st diameter with a plug gauge at the start shift… - The operator checks 100% of the diameters with a caliper during production…

The first monitoring of the diameter at the start shift…



Page 55

The second monitoring of the diameter during production.

As a conclusion, two monitorings/measurements exist for the diameter.

Remark: At an operation level, the value, limit <, limit < and unit, are the same for all monitoring applied to the characteristic, or parameter.



Page 56

7.1.2 Duplication of monitoring or control plan

The new release allows duplicating an existing monitoring on several characteristics. Example: A measurement robot checks N characteristics during the same sequence. The same method is applied to these N characteristics In the screen below, the robot will measure 4 characteristics

The first one is defined on the diameter…

The diameter is selected, (underlined in yellow color), then click on the duplicate button, and select in the check box all characteristics where the monitoring will be applied.



Page 57

After the duplication, all characteristics are independent, so you can modify them if required. Remark: at the left bottom of the screen, the filter can display all operations. The same monitoring is applied to all these characteristics.



Page 58

7.1.3 Levels of Control plan AIAG

The new release 6 allows keeping three levels of control plan, corresponding the Prototype, Pre-launch and Production steps. You can switch from one to another at any time. Filters on screen display, or printout have been implemented to bring more comfort. Example: we start with the « Prototype » level. (Button: Information / Tab: Headers Control Plan.)

Example: the diameter at the finishing operation is selected.



Page 59

The control plan is defined on the « prototype” level. with a 100% of control…

We switch to the “ Pre-launch” level. Information button, tab headers Control Plan.

A message proposes to copy the previously defined monitoring, so to get it to the new level of control plan.



Page 60

At the bottom of the screen, the display filter shows, by default, all levels of control plan. In the example, a double monitoring is obtained as a result on the diameter. On the printout, both monitoring are printed with the information of which level is concerned. After the change of a level of control plan, each monitoring is independent, so can be modified afterward. .

On the AIAG printout, a filter is proposed to select which level has to be printed. The impacted reports are:

AIAG – Control Plan

AIAG – Control Plan with Component

AIAG – Risk Control Plan



Page 61

7.2 Printout & reports All reports are centralized on the printout icon.

The parameter button can select the language of the report or the framework, and define a page footer , printed on all pages Chaining of report: To have a continuous page numbering N° of first page: to define the page number to start.

To select a report, from the “available area” to the “selected area“ or double click

To select a report, form the “selected area” to the “available area“ or double click

To empty the list of reports selected



Page 62

During a preview, you can export the result into various format as acrobat, word



Page 63

8 FMEA FILES HANDLING

8.1 Specific FMEA An FMEA file or folder is an independent entity, it can be protected by a password, duplicated, by experience, it concerns one product manufactured by the company.

Properties

To changer the name of the FMEA folder or to add a comment Switch the specific folder to a generic folder or vice versa. Archive a folder or make it available Hide the process parameters on printout for confidential purpose during an audit.



Page 64

Save as

Duplicate an entire FMEA folder. The check box allows to copy or not either the functions, components linked with the cause the design or process part, operations, and the actions, in the copied FMEA.

Export

Exporting an FMEA consists of putting it into an external container, separated from the database. While it has been exported, it can be imported into another Skill FMEA Pro database. At this step you can replace all names of responsible in order to do not copy them. During that operation, the FMEA folder is exported with its quotation scale. This feature is used to allow the deletion of a folder into the main database by keeping a backup outside.

Import

That is the reverse operation of the export feature. The same rule applies concerning the responsible name and the quotation scale.



Page 65

8.2 Global handling on an FMEA

8.2.1 Delete action This option deletes all action inside the FMEA, in that case, all final assessment are initialized to the initial one.

8.2.2 Reset action

The status of action are reset to the “Proposed” level. The start date are set to the date defined The end date are set to same amount of days initially existing between the start and end date.

8.2.3 Set evaluation to maximum All evaluation of S, O, D, are put to the maximum value of the scale used inside the FMEA.

8.2.4 List of rejected / archived actions This option prints all actions rejected/archived of the FMEA. These action are not displayed over the reports.



Page 66

8.2.5 Reallocate actions

To move action from one responsible to another one.

8.2.6 Delete control plan

This functionality applies to the AIAG norm. To delete all control plan define for a level. Prototype, Production…

8.2.7 Protect with password The protection of an FMEA is done to ensure that the owner of the FMEA update realizes the update and so, guaranties the revision index. The user, for each FMEA, gives the password. Attention, if the password has been forgotten, the Administrator can cancel it, and release the folder

Password in design FMEA Password in process FMEA

The contain of the function/component is protected

The contain of the operation/component is protected

Password in design and process, the components belong to the design FMEA.

1- The « save as » of a protected folder removes the protection on the copied folder. 2- The administrator can delete the password, so release the FMEA



Page 67

8.2.8 Display confidentially

A process parameter value or a product characteristic value may be hidden during printout for internal reason. (Machine setting, or intermediate dimension during the process step.)

If the confidential display is activated, all reports will hide the value . (Control Plan, Job instruction..)

8.2.9 Statistics

Design FMEA

Process FMEA

These statistics allows the analysis of the FMEA, to estimate the level of details on design and process side.



Page 68

8.3 Generic and specific FMEA A specific FMEA is built for a particular product manufactured for a client. A generic FMEA is built to capitalize and centralize the knowledge spread into several specific FMEA. A generic FMEA capitalizes the knowledge, or modifications done inside the specific FMEA. A generic FMEA never deletes information, during the automatic capitalization. A generic FMEA has the same features as a specific FMEA, it just incorporates the knowledge by addition.

The link between a specific and generic FMEA in done: Design FMEA: at the function level Process FMEA: at the operation level Machine FMEA: at the component level

Inside an FMEA folder, these 3 buttons are handling the connection and exchange between an Generic/specific FMEA

Capitalize the modifications added in a specific FMEA into the generic FMEA

Take an element from a generic FMEA to insert it inside a specific FMEA.

Resynchronise the specific FMEA form the generic FMEA, to update it.

Remark: By experience, several scenarios can exist to build up the sequence of the generic/specific FMEA. Start from an empty database, or several specific existing FMEA to be connected with a generic. The key point remains the handling of the characteristics of component, which requires the use of a “template” between the generic and specific. A template could be imagined for a product line, of a family of product.



Page 69

8.3.1 Creation of a generic FMEA

To create a generic FMEA, click in the check box. To change an FMEA from specific to generic, use the Properties button to access to this dialog box.

Rules & principles of capitalization

During the capitalization form a specific to a generic, the following rules are applied. (a label is can a mode, cause, effect, detection)

If a label has been added into the specific it is added into the generic

If a label has been deleted into the specific, it remains unchanged into the generic

If another element (code, value, limit, unit, comment) is modified = no influence

The risk assessment (S, O, D, RPN) : the value into the generic is the first one written



Page 70

8.3.2 Capitalization Generic > Specific

This functionality is used to add into the generic, all new mode, cause, effect, detection from a specific In design, select the life situation where the function will have to be imported, and follow the sequence of buttons.

1 case: First creation into the generic type of button - A link is created between the specific element and a new element into the generic

- All associated defaut (effect, mode, cause, etc..) are copied into the generic



Page 71

2 case: link with an existing generic element, type of button

- A link is created with a generic element The generic element has to be selected with the list Durant the import from a generic, you can include

- The component linked to the function specific - The actions linked, to the cause of failure.

By default, the check boxes are not activated.



Page 72

8.3.3 Call generic > Specific

This is to copy an element form a generic into a specific

In design FMEA, select the “Life situation” and click on the button All generic FMEAs are displayed on the left part, select the item and click on the bleu arrow button, or double click on it, to copy them into the specific FMEA.



Page 73

8.3.4 Automatic capitalization

From a generic FMEA, update all new elements stored in the specific FMEA.

This functionality ensure that the generic FMEA is 100% updated, by all elements added in each specific FMEA connected to it.

From the generic FMEA, click on the « UP » button.

The left part shows all element of the generic FMEA. The right part displays in which specific FMEA the element is connected. The checkbox, allows selection of the specific element which will be used for the automatic update.

Generic FMEA Specific FMEA

Capitalization

Access from generic

UP

Specific X

Specific X

Generic FMEA Specific FMEA

Capitalization

Access from generic

UP

Specific X

Specific X



Page 74

8.3.5 Send an alarm to the specific FMEA pilot for updating

- To show all specifics FMEA to be updated from the generic - To send an alarm to each specific FMEA pilot to update from the generic

From the generic FMEA, click on the “Down” button.

The left part displays the elements contained in the generic FMEA. The right part shows in which specific FMEA the selected elements (yellow) are utilized. If an element is selected on the right part, the corresponding element of the generic is highlighted on the left part. Click on the button, to send an alarm by email.



Page 75

The upper list display the list of FMEA and their corresponding pilot. The checkbox allow to select the mail to be sent. For each FMEA a mail is sent to the pilot.

8.3.6 Automatic synchronization of a specific FMEA from a generic

During the different sequence of capitalization, the specific FMEA are “different” from the generic. ATTENTION: in a theorical approach, this functionality can transform all specific FMEA identical to the generic one. The ultimate update of the specific is done under the user control.

Specific FMEAGeneric FMEA

Mode 1

Mode 2

Mode 3

Capitalization

Access from generic

Mode 1

Mode 2

Mode 2

Mode 3

Mode 1

Mode 2

Mode 3

Mode 1

Mode 2

Mode 3

DOWN

DOWN

Specific X

Specific Y

Specific FMEAGeneric FMEA

Mode 1

Mode 2

Mode 3

Capitalization

Access from generic

Mode 1

Mode 2

Mode 2

Mode 3

Mode 1

Mode 2

Mode 3

Mode 1

Mode 2

Mode 3

DOWN

DOWN

Specific X

Specific Y



Page 76

Open your specific FMEA. To update the specific FMEA, click on the « Down » yellow/green button

If several generic FMEA are connected, select the one you want to update from the list.

The left part shows what can be added from the generic, if the update is launched. The status column gives indication, on what has to be added (bold and yellow highlight) If you don’t want to add an element, click on it, then press on the unselect button



Page 77

8.3.7 Generic / Template / Specific

By experience, the implementation of Skill FMEA Pro must fulfil a global requirement

- Capitalize the company knowledge - Handle product line (approx. a dozen…) - Maintain specific FMEAs for each individual product (approx. several hundred…)

An FMEA can have a design area, a process area, and a control plan area. The handling of the nomenclature of components is the key point in this architecture. Indeed

- Each product has precise and individual dimension - A manufacturing process can have variant (drilling with machine A, or drilling with machine B)

It is recommended to implement your FMEA according the below schema

Remarks:

- The generic FMEA does not have a product nomenclature - The template stores the variant in process - The template has the control plan in process

Sequence to follow

Create the first template for a product line

Link with a generic FMEA (first capitalization)

Create a specific by a save as of the template

Generic Design

FMEA

Generic Process

FMEA

Function Operation

Template FMEA per product line

Function ComponentDiameter = X

Monitoring 1/X

OperationSpeed = Y/min

Monitoring 1/Y

Specific FMEA for each product

Function ComponentDiameter = 8 +- 01 mm

Monitoring 1/10

OperationSpeed = 800 tr/min

Monitoring 1/hour

Save as

Spe

cific

Tem

pla

te

Ge

ne

ric

Generic Design

FMEA

Generic Process

FMEA

Function Operation

Template FMEA per product line

Function ComponentDiameter = X

Monitoring 1/X

OperationSpeed = Y/min

Monitoring 1/Y

Specific FMEA for each product

Function ComponentDiameter = 8 +- 01 mm

Monitoring 1/10

OperationSpeed = 800 tr/min

Monitoring 1/hour

Save as

Spe

cific

Tem

pla

te

Ge

ne

ric



Page 78

Example in design FMEA

Function reusable: Display all element already linked to a generic FMEA

- A- In the upper part of the screen, all functions, which were coming from a generic FMEA, are

displayed. To capitalize or update the generic with all the modifications brought, click on the cheek box.

- B- Delete link, the feature is used to break the link of the function with its generic FMEA. In

general, after deletion of the link, to create a new link with another generic FMEA. Function usable: Display all element not linked to a generic FMEA

- All new functions created inside the specific FMEA area displayed. To capitalize them inside generic FMEA, for each function, select the name of the generic FMEA to be used.

- Remark: it is mandatory to define the life situation of the generic FMEA to store the function at the correct place.

- Type of link

Use for the first capitalization, to create the generic element, the OK button starts he copy.

Use to just, create a link with a generic element. In order to use the automatic capitalization later on. Component / Action “D”

During the capitalization / update of the generic FMEA, you can copy the component and characteristics which are linked to the cause of failure. During the capitalization / update of the generic FMEA, you can copy the action (responsible, and dates)

A B

C

D



Page 79

8.4 FMEA translation

This feature is an option, and must be activated with your licence key. Language of interface (standard): Skill FMEA Pro can run in several language, like the English, German, French, Spanish.. In that case, that is impacting the language used in the screen, button, menu, and printout. Language of data: (option): A central glossary for terms in handled to allow the exploitation of your FMEA in several languages; the user does the translation for each term.

8.4.1 Translation inside the FMEA

The language selected in the example is English. The words are displayed in the selected language. Now, switch to the German language, the words are displayed in German because they have been previously translated in the central glossary.

Now switch in French language, a word has not been found translated in the glossary, so it is displayed with ###. Put the equivalent word in French, and all FMEA will be updated.

8.4.2 Translation into the catalogue

See chapter 2.1.4- Manager / Catalogues



Page 80

9 TRANSVERSE AUDIT

The audit transversal module is an option and must be decoded in your licence key. The objective is to analyse your data (like the SQL language) and to access directly to the database in order to make specific report or queries on the FMEA.

9.1 Functionalities

9.1.1 Add, Edit, Delete a query

click on the button to create, modify or delete a query. Copy: use that button to copy or duplicate en existing query.

Execute: run a query Save order: to define a specific order to display the list of query, use the button “A”, to move up or down a

query in the list Import / export: to send a query to another Skill FMEA Pro user, or to receive a query made by another

user. Password: to protect a query by a password. See Administrator chapter to cancel / remove a protected

query. A query consists of three area,

1- Name and comment 2- List of field to be displayed 3- List of condition to display the result.

The example describes a query: To get the list of all component with a characteristic flagged by a SCC.

A



Page 81

1- Question name

The name of the query / question, is defined, a comment can be added, and the language is selected. 2- List of field to be displayed

The windows has to be defined to select the details of the filed to be added, or modified

FMEA Type: Select the type of FMEA, 3 types are available, design, process, component. Table : This list shows the table available within the FMEA type Field : This list shows the field available within the table inside the FMEA type. width : The width of the column in the print out result. (Minimum width= 2, maximum width is 260. Options: The option to avoid redundancy during the printout



Page 82

The following scheme explains the 3 FMEA types, and the tables inside the FMEA type.

3 Conditions List

A condition can be defined on field, in order to filter the result.

Operator : logical operator between conditions, AND, OR "(" et ")" : To separate the condition like ((X and Y) OR Z) FMEA TYPE : 3 type are existing, design, process, component Table : Table containing fields, inside an FMEA type Field: fields available inside the table of the FMEA type Condition : classical « SQL » conditions like « greater than », « less than, « « is null », “is not null »… Value : The cell « value »is displayed if you have selected contition like « greater than » or « less than »

9.1.2 Execute a query / question

FMEA folder

Life situ.

Function

Criterion

Mode

Cause

ValidationAction

Sub/syst..

Component

Charactéristic

Poste

Operation Parameter

Mode

Cause

Detection Action

Effect Effect

COMPONENTDESIGN FMEA PROCESS FMEA

FMEA folder

Life situ.Life situ.

Function

CriterionCriterion

Mode

CauseCause

ValidationActionAction

Sub/syst..Sub/syst..

Component

Charactéristic

PostePoste

Operation Parameter

Mode

CauseCause

Detection ActionAction

Effect Effect

COMPONENTDESIGN FMEA PROCESS FMEA



Page 83

Click the button « execute », the result is displayed.

10 COPY/PASTE INTO AN FMEA

10.1 Drag & Drop simple

During a « simple » drag & drop, when the selected element is chosen, all information related are copied CTRL, + click to select the element, + move then release on the target element

In the example if you select the function: the function + criterion + mode+ effect + cause + action, will be copied

The same functionality applies on the failures screen. A little specific « detail », to copy a cause, select the « « Occurrence” value, and not the cause…



Page 84

10.2 Drag & Drop double During a double drag & drop, both tree views are copied. In design “function + components”, and in process “operation + component”.

DESIGN FMEA

Function Component

Cause Characteristic

PROCESS FMEA

Operation Component

Mode Characteristic

CTRL, + SHIFT + click to select the element, + move then release on the target element Un « drag and drop » double copie l’arborescence dans laquelle on se trouve, et les liens avec l’arborescence. Fonction/composant ou opération/composant Level notion : Principle : from the selected element, all informations below are copied

FMEA type Level 1 Level 1 Level 1 Level 1 Level 1 Level 1

DESIGN Life situation Function Criterion Mode

Effect

Cause Detection

Action

COMPONENT Sub-system Component Characteristic

PROCESS Process step Operation Parameter

Cause Detection

Action



Page 85

11 ADVANCED FUNCTIONNALITIES

Skill FMEA Pro is built on three main entities, linked together: the functions, the components, the operations.

- In design FMEA, the link is created between the cause of failure and the characteristic of a component.

- In process FMEA the link is created between the mode of failure and the characteristic of a component.

- By deduction, the characteristic of the component is connected with the design and the process. The D, P, M columns - D: Design FMEA (link cause/characteristic) - P: Process FMEA (link mode/characteristic) - M: Monitoring, Control Plan

The RPN limit and alarm on the O, S, D scale are defined for the FMEA study

The colours for column D & P - White/no colour: no link of the characteristic - Bleu: the characteristic is linked to a non critical mode/cause - Orange: the characteristic is linked to a mode/cause, and at least, one is orange - Red: the characteristic is linked to a mode/cause, and at least, one is red

The colour for the column M:

- White/no colour: the characteristic has no control plan - Green : the characteristic has, at least, one control plan

From the main screen of the components, click the icon to access to the « reverse » analysis



Page 86

11.1 Design risk

The target of that feature is to answer the question « How do you justify that tolerance, which function is impacted ?”

11.2 Manufacture risk The target of that feature is to answer the question “On which operation this characteristic is obtained, and what are the risk ? “

11.3 Risk control plan The target of that feature is to answer the question « How and where this characteristic is monitored?” Attention 2 different analysis, based on 2 norms of control plan, Skill and AIAG.



Page 87

Some reports and analysis

The report and analysis are available on the menu print out from the component main screen.

Some more tips… Quelques trucs & atusces

o Command line : Skill FMEA Pro / LANG=X Use this line to start the software with a language Cette ligne de commande permet de choisir la langue de démarrage silencieux

Replace X by :

CS=>Czech

EN=>English

FR=>French

DE=>German

IT=>Italian

ES=>Spanish

o Command line : Skill FMEA Pro / UID=X

Use this line to start the program with a « silent » user Replace X by the login

o Command line: Skill FMEA Pro /PWD=X

Use this line to start the program with a “silent” password

Replace X by the password

o Command line : Skill FMEA Pro /D

Use this line to start the program directly in Design FMEA

o Command line: Skill FMEA Pro /P

Use this line to start the program directly in Process FMEA

o Command line : Skill FMEA Pro /M

Use this line to start the program directly in Machine FMEA

------------------------ thank you for your confidence-----------------------------------

Quick start SKILL FMEA PRO - Skill Software€¦ · Quick start SKILL FMEA PRO ... 4.2 Product nomenclature _____30 4.3 Creation / modification of the ... the software is adapted

Documents