Sensors are referred to as Tags across the Platform. There can be a wide variety of Sensors used in a plant. There could be heat sensors, pressure sensors, voltage, frequency, vibration, speed, load, pressure deviation, and so on. Each sensor in the plant is given a unique identifier called "dataTagId" along with information such as instrument properties, its location in the plant, the property it measures, etc. All this information is added to a record called "tag meta" in the Database.
Let us, at the outset, know the hierarchical asset structure within a Plant.
Every Plant has a number of systems, for example, Boilers, Cooling systems, Fuel Supply, Generators, Transformers, Turbines, and many more. The system, therefore, is a collection of equipment that performs a specific function. The system is, thus, broken down at the first level into a set of Equipment or Assets.
The equipment/assets are usually self-sufficient machinery that contribute to a specific aspect of a system’s functioning. For example, Preheater is an equipment and is a part of the Boiler system.
Components and/or Sub-Components are the logical breakdown of equipment like Economizers, Main Steam Lines, Supply Systems, Fans, Steam Pressure Controllers, Storage Tanks, Air Coolers, Furnaces and Bearings cases of sub-components, and others.
Relevant Sensors (Tags) are attached to each Component or Sub-Component to record/monitor respective measure properties. The Measure Property is the medium or base property of the system that is being monitored. Depending on the type of plant (Power Generating, Cement), these measure properties could be, Secondary Air, Metal, Power, Main Steam, Feed Water, Cooling Water, Flue Gas, Oxygen, Furnace, and others to measure Differential Pressure, Current, Voltage, Frequency, Flow, Run Hours, Pressure Deviations, etc in terms of respective measure units like KG/Cm2, Kv, Mm/Sec, Tph, Hours, MTs, RPM, Kj/Kg, kW, Kva etc (measure types).
The Tag Mapper feature of Pulse Platform allows users to map or assign the Sensors (Tags) to Equipment/Assets, Components, and/or Sub-Components, Measure Property, Measure Type, Measure Units, and Measure Location (the location at which the sensor is placed). For example, Inlet, Outlet, etc. all these sensors when onboarded remain Unassigned until you assign them to the relevant System, Equipment/Asset, Component, or Sub-Component.
Warning: Do not attempt to assign the Sensors unless you are well-versed with the Systems/Equipment/Assets and their measuring parameters. Assigning incorrect information will result in irrelevant tagmeta.
Use the link below to go to tag mapper page of Pulse
https://data.exactspace.co/pulse-tag-mapper-ng/#/tagmapper
or
Enter the URL https://data.exactspace.co/pulse-login/
Within the Tag Mapper interface, you'll find a list of tags categorized into two sections: "Assigned" and "Unassigned." Your task involves assigning equipment with the appropriate tags by navigating through various fields. Initially, the Equipment section will be selected by default. Proceed to assign further fields such as Components, Subcomponents, Measure Property, Measure Type, Measure Unit, Measure Location, Bad Direction, and Anomaly by selecting each tag individually. Components and subcomponents may or may not be assigned for certain tags, but it's essential to assign the remaining properties for comprehensive metadata organization.
There's a common option for all fields labeled "Select All" and "Unselect All," which function uniformly across the board.
For example
In the figure below, there exists a list of unassigned tags without an accompanying equipment list. Notably, the equipment list is absent, as it is typically accessible through APIs rather than being visually presented. In such instances, queries are directed towards APIs and aren't tied to any specific unit. However, when it comes to assigning equipment to tags, a distinct equipment list becomes essential. This list serves as a reference point for associating equipment with respective tags, ensuring accurate assignment, and facilitating seamless management of equipment-tag relationships.
Upload the system and equipment information in Asset Hierarchy and Equipments by clicking on “Create an asset” or through “Import Plant template” or by “Uploading metadata” through an Excel sheet. Refer to section 2.2.1 to “Create an asset” 2.2.2 for Import plant template and section 2.1 to upload metadata through Excel of this user guide for detailed information on this topic.
It's important to avoid assigning all tags to the same equipment. Instead, utilize keyword searches to individually assign each tag to the appropriate equipment based on specific requirements.
Note :Ensure you have accurate information regarding the number of equipment units you need to assign tags to, especially when dealing with specific equipment types. For example, you should be aware of whether you have one or two PA fans, enabling you to conduct targeted searches and make appropriate assignments accordingly. This clarity facilitates efficient and precise tagging, optimizing your metadata management process.
Steps to assign equipment to tags -
Note: Occasional delays may occur for display of preferred option on right side for respective fields due to backend service issues, requiring a brief wait for the display. Additionally, it's crucial not to blindly rely on the recommendations; they serve as assistance rather than definitive solutions
The assigned tags will now be displayed under the "Assigned" section. For example, if the assigned tags previously showed 2, they should now show 4 after the recent assignments have been made.
This change reflects the updated status of tagged equipment, providing a clear indication of the number of assignments made. Please refer to the figure below for visual confirmation.
Similarly Assign other tags
Example for – BL2FDFan2 assign to Afbc2 SA fanB
Proceed systematically to assign metadata to the remaining tags
To add a component to the Tag
For example:
For the bearing Fan, we assign “motor” as the motor is related to the bearing fan. So select motor on the right side and bearing fan temp on the left side for all those tags you want to assign “motor” as “component”. Click on “Assign”.
Add component “-” to the tag where you do not find any compatible component.
How to add subcomponents to tags
To assign a subcomponent to tags, follow similar steps as mentioned for equipment assignment.
For example, in the case of FAN AMPFeedback, the option of “-” is recommended.
Through tags it's understandable what subcomponent can be assigned to it.
Like
Measure property refers to how you measure tags
Steps to add Measure Property to tags
To assign a measure property to tags, follow similar steps as mentioned for equipment assignment.
For example,
To check measure property take some common keyword from the list of assigned tags. Sometimes it's not clear which measure property should be assigned.
For example-
FAN SPEED Feedback can be assigned power. But it has two properties: “rotor speed” or “motor speed”. In such case you can refer the base unit and check the measure property form Configure asset of Pulse interface
How to check “measureProperty” through base unit
Steps-
https://cpp.utclconnect.com/pulse-ui-v3/#/login
Another way to check is
After you check this select rotor for speed feedback tag and click on Assign
Similarly, if you check for Bearing Temp-DE. Type “bearing’ in Tags with measure properties on the left side. On the right side, you get the option of metal which is its measure property. Select all bearing temperatures you want to assign metal as a measure property. Click on “Assign”
Measure type- how you measure sensors like amp (current) for a fan.
To assign a Measure Type to tags, follow similar steps as mentioned for equipment assignment.
For example
Bearing TEMP-DE -
Example3.
FD FAN Speed Feedback- In this you get measure type “Speed” which can be assigned to this tag.
in this way you assign measure property for all the list of tags.
To add Measure Unit to Tag
Do we need to explain the same steps again?
Steps to add Measure Location to Tag
The system is configured to facilitate issue identification. For instance, consider "Bearing temperature." In temperature-related scenarios, high temperatures often trigger issues, while low temperatures are typically acceptable. Given that issues arise primarily at the high end, assign the "high" designation to a set of temperature tags accordingly.
Example “Current B phase” will raise an issue if its current value goes “high”. Refer figure below
Note: If you assign “-” here for any tag, this means you want alarms for both sides high as well as low.
If you set an anomaly to “True”, you need an alert for that tag. Towards which side (Low or high or both) you want that anomaly to be raised is decided by a bad direction.
In case you do not want an anomaly to be raised for a particular tag, set the anomaly value to “False” for that tag.
This feature is primarily intended for creating alarms and is not directly related to metadata. Therefore, all tags are displayed as assigned, as it's crucial for all tags to trigger alarms in the event of value changes beyond specified limits. “Unassign” tags which cannot raise an anomaly i.e. if a particular tag is not needed in fault tree or to raise a concern, assign that tag as “false” in anomaly, then alarm will not be triggered from there.