In this blog, I would like to touch base on key things(a few) that have come along with version 2005.
- Feature: Data Protection and Privacy
Export to Excel feature for asset central foundation objects
- Feature: Documents
Search Criteria based on document category/New versions can be created other than image & VDS documents/Multiple languages for each file, based on the log-on language one can view it
- Feature: Equipment
Unique Id field has been added to while creating equipment, helps in search criteria
- Feature: Failure Modes
New fields added to have default values of “Category” and “Type” for each failure mode
- Feature: Topology
Until the 2002 release, the system must have a model assigned which is based on a model template and inherits from the subclass, now user can create a topology for any type of system
- Feature: Default Indicators
A user with an administrator role can select indicators and set them as default indicators on a model level for all users. A variant Default Indicators is available to display the indicators marked as default at model and equipment level. The variant can be selected by the user in the Indicators section of Equipment or Model
- Feature: Sharing
Until 2002 release, for a given authorization group, you can add your own objects to share. While sharing, you can provide read or write access privilege for objects owned by you. For objects that are not owned by you, you can provide only read access privilege. In 2005, this functionality has been enhanced such that the organization sharing the object can provide a grant flag for their own objects by enabling the Grant to the Share button. Grant must be disabled for foreign dependent objects.
Now let us look at them in detail…
- Data Protection and Privacy:
Personal data like e-mail address, first name, last name, and user ID and the objects that one was created or modified can be exported to excel under Core and Others.
The option “Add New Version” is available by selecting the document and choose Edit. Select a file and choose Add New Version. The file uploaded is stored with a new version. The highest document version is displayed in the equipment, model, and location object pages. Multiple languages are supported for a single file. More than one language can be set for a document and based on the logon language, it displays the document in the relevant language.
Note: Even if we upload with the same language of the initial document, the system will hit an error message
Once we complete the document creation, same can be assigned to Equipment/Locations/Models/ Spare Parts/Instruction Steps/System
- Equipment with UID
As of 2002 release, equipment had many IDs to be identified by, but not a unique ID that could be used to identify the equipment in any system. Unique ID (UID) field has been added as a new field when creating equipment and also is displayed in the equipment information. UID must be in the following format: <Unique company identifier>/<Model-ID>/ <Serial No>.
- Failure Modes:
while creating “Failure Mode”, by default system assigns the ” Others” in Category field and “3-Non Critical Failures” in the Type field, so one should change them accordingly.
- Viewing Topology for “SYSTEM”
The system topology displays the network of equipment and subsystems, and how these are connected within this specific system. This mainly helps the reliability team to understand the interconnectivity of the digital assets and can be drill down to individual equipment/subsystem to get detailed information as well and also to have visual identification of newly added/removed equipment in the existing structure.
What is “Topology” ?… before we set up this in IAM-AIN, one should understand the definition and objective of topology…this may vary from process to process…
In Plant Maintenance terminology, Topology is a representation of laying various technical objects in a specific network(multi-equipment network) with certain links between each technical object.
The main advantage to have this topology network is to understand the failure of local equipment system, which halts the neighboring equipment operations or operations of other objects having a dependency on it and causes the whole system breakdown, whereas, with this topology concept, reliability team can understand the relationship of individual equipment failure and analyze the impact of node failure in a network system. This mainly helps to perform a vulnerability analysis of the equipment system.
For example: If a motor of auxiliary cooling tower breaks down, air compressor system will get impacted as there will not be any water circulation to the intercooler and aftercooler of the air compressor system, so the air compressor interlocks will get activated to stop the whole system, as the air temperature at both LP and HP cylinders are not maintained due to failure of cooling tower motor
- Default Indicators
Default indicators can be set at Model level & Equipment level
Automatic sharing has been enhanced such that the changes made by the service provider or business partners on the shared objects are also automatically reshared with the object owner
The system enables to share Objects viz, Equipment/Model/Spare Parts/ Documents/ Instructions/ Announcements/Assessments etc.,
In sharing patterns, you can only configure read or write privileges with which an object can be shared. This has been enhanced with Grant to Share flag so that the organizations with whom these objects are shared will get to reshare these objects.
I hope this document may bring some level of understanding about the things that version 2005 has brought…