Build the first asset hierarchy – quick start

After signing in, Asset Strategy Optimization will always start in the Tree view. This view shows all the folders and asset trees built-up in those folders you are entitled to see based on your user rights.

If you have the rights to create a folder and objects, then a good way to get to know Asset Strategy Optimization is by creating your own folder and start building a first asset tree.

The following steps will help you set up your first asset hierarchy with the web version of Asset Strategy Optimization. The example will use a common place object, such as a bicycle, which contains all the aspects that one can find in FMECA.

To build a tree hierarchy

1. Open the Tree structure screen in the Tree view in Asset Strategy Optimization
   

2. Folder: Create a folder with a clear name, for example Systems.

3. FMECA System: After adding a new folder, the folder can be Create an FMECA system with a clear name, for example Bottling Plant. The System is the starting point to build up a hierarchy of objects available to the user.

4. Serial System: Create one or more levels of serial systems. Use names that yield a logical decomposition of the system, for example a main serial system called Production USA, with subsystems called Production Line A, Production Line, and Production Line C.

   

5. Redundant System: You can also model redundancy by creating one or more levels of redundant systems. In the example above, no redundant system is present.

6. Part: You may now create one or more parts, such as Pumps, Piping, and Ball valves in the example above.

7. Components: Now create components which together make up the part. These are part of the section Components / Failure causes. An example for a pump is Mechanical seal, Electrical circuit, Propeller, Bearings.

8. Failure causes: Define one or more failure causes per component, which is how the component can fail, for example Defect, mechanical seal (because of wear). A failure cause can be Hidden, meaning that it may not be obvious to detect (usually in a situation where there is also a redundant system). There is a probability for it to happen, expressed as MTTF (Mean Time To Failure). Describing the effect of the failure cause on the business objectives is done as part of FMECA step 5.

9. Maintenance: For each failure situation, define the maintenance needed to resolve the failure, for example Repair mechanical seal. Here, the user also defines preventive maintenance actions, meant to prevent the Failure cause from happening, as part of a maintenance strategy.

10. Failure modes. A Failure mode describes the effect on the business objectives when one of the functions of the associated part fails. A failure mode is therefore defined at the level of the part and assigned to one or more failure causes of that part. The effect of the failure mode is then defined for each of the business objectives defined for this system.

    Note: When the field Tag is filled, that description will be included in the name shown in the Asset tree, separated with a dash. For example, a part called Ball valve DM50 may be given a tag called PLBV003. The name displayed on the screen will then be PLBV003 – Ball valve DM50.