topbanner
topbanner

Asset Lifecycle Management


Asset Lifecycle Management (ALM) support your maintenance and modification activities.

After completion of a plant you want start fast and smooth whit your production and maintenance processes. It is essential that all ‘As Built’ information is complete and can be consulted. These are documents, tags, parts, and coherence. By changes you want to quickly adapt the ‘As Built’ information based on the future maintenance processes in the new situation of the Plant.

There must be considered from multiple roles, when setting up an efficient information store. In a plant there are playing different types of information a role such as; documents (Drawings, Manuals, etc.), Function Codes (Tags / PPS ’s), lines (items, equipment) and setting conditions. These involve often large data sets, and all information has a consistency. In this network of information everyone has to find his own information within there role and adapt quickly.

An example. For an engineer, who applies a new pump in the production process, the following information important: the related Functie-/Tagcodes in the overall process, functional specifications and descriptive documents (eg CAD drawings). This information should be easy for him to find. Which physical pump (brand and part number) there is chosen is for him hardly relevant.

service engineer will consult other information. He doesn’t need only the specifications of the engineer, but also the instructions of the manufacturer. He also wants to know exactly where the pump will be  more used in the Plant(“Where Used”). This is to make use of  knowledge from the past, or just to prevent a malfunction in other places. It goes without saying that a technician will manage the history of changes, both at the level of adjustment data, old parts and original documentation. If an adjustment provides problems, he wants consultation the data from the old situation.

ALM supports the sets of commands and change processes for both roles, and providing all requested information. ALM is not limited to manage or access documents, but also manages (with the links), tags and parts.

‘Asset-Oriented Information’ requires a PLM system

Experience shows that maintenance employees need oriented asset information management. This means that maintenance workers seek information on the basis of Function Codes (Tags, PPS codes, location codes) and Part data(vendors, part numbers, etc.). A Part of the information belongs directly to the tags and / or components, such as history, data settings, ‘Where Used’, etc.. Employees will also consult related Documents. Classic Document Management Systems (DMS) offers too little functionality and flexibility for this kind of requirements. A Product Lifecycle Management (PLM) system is capable to support all the complex  store and search structures around tags, components and documents, without restriction.

Support for all extensions and amendments from the Plant

The maintenance worker will performing common (small) changes to the ‘As Built’ situation, or has modifications suggestions. In straitALM all these changes and suggestions can easily be processed. Extensive support for changes is present, such as authorizations, ‘Where Used’, impact analysis, redlining and workflow. Colleagues can immediately see what kind of changes to a tag line, carried out or planned in straitALM. Obviously the history before changes will be preserved. For larger changes and improvements to the Plant, the “engineering cockpit” in straitALM will be activated. The engineer simply calls all the necessary information, for example, displayed in a hierarchical Tags Structure with all P & IDs and data sheets. Again all (maintenance) employees see directly which parts changes are planned. The tight integration with many CAD and Office applications is also a unique feature that no other ALM system has.

Links with OBS systems such as Maximo and SAP

If you have an OBS system (such as Maximo,  Ultimo or SAP), then PLM provides an optimal synchronization of the functional (tag) and/or component structures. Tags, components and documents relationships are always complete and up-to-date management. Depending on your needs you can search for information in your OBS or  PLM environment.