Part

The part in Asset Strategy Optimization is an object within which failure modes and effects of failures are defined. A part is dependent on a system, a serial or parallel system or a library folder. The levels below are referred to as an obligatory structure. A part always comprises components that in turn comprise one or more failure causes each having one or more maintenance actions per failure cause. No failure cause (failure) can be added at the part level.

The following objects can be created under a Part:

Converting into another object

Should the wrong type of object have been chosen, it is possible to Convert into other object the created object into another object. Note that any data created for the original object will remain available in the database, should the user decide to change the type back into the original type.

Definition of the parts

Depending on the required level of analysis and simulation, it is necessary to define what is considered as a part and what as such is dependent on the FMECA system. Example1 shows that the bicycle system is divided into two parts. If required, you can opt for further itemization by using for example, separate parts for 'front wheel' 'and 'rear wheel'. The components related to traction, such as 'Gear Back', can be an additional components of the part 'rear wheel'.

Part composition- example 1

Part composition - example 2

Tab Part - General

A part has a number of specific properties that play a role in the risk analysis and simulation of the part and system of which the part is an object. These can be entered in the Property Grid. Optionally, by double-clicking on the part, users can open the Properties screen where the properties can be viewed and/or changed, as shown below.

Properties of the Part - tab General