Activities/Tasks and Events/Work Orders
- Last UpdatedJan 10, 2025
- 3 minute read
Activities/Tasks and Events/Work orders summary views has the same structure as Tags and Documents ones. However, they are detailed in their own section due to their differences.
-
Task & Event ID and its classification.
-
Populated from Name & CLassID of the EIWM XML file.
-
Attributes appear under different sub heads in the attributes section due to attribute grouping in ISM.
-
Is a part of site association is used for building the breakdown structure for Tasks and Events.
-
Is a task on Tags is an association used to populate the Activities/Tasks section on the Tag summary view. Since this association is used, the Activities/Tasks section is populated on the tag summary view because of the other side of the association created between Tags and Tasks has task.
-
Event Tags populated thanks to the is an event on association. Since this association is used, the Events section is populated on the tag summary view because of the other side of the association created between Tags and Tasks has event.
Register configuration
-
Association for forming the breakdowns – Task is a part of plant and association for forming the breakdowns – Event is a part of Plant.
-
Association for populating the Activities/Tasks Section on the Tag Summary view – Task is a task on GEN_ROOT_FUNCTIONAL and association for populating the Events Section on the Tag Summary view – Event is an event on GEN_ROOT_FUNCTIONAL.
ISM Configuration
Permissibility for associations related to Activities/Tasks and Events/Work orders needs to be added.
Association between Site and Task is not present by default in AIM-A. So, its permissibility needs to be added. Define permissibility for is a part of associations related to Task objects and add visibility = false for the ACTIVITY class such that the Activity class node doesn’t appear in the AIM-A dashboard (optional).
Association between Site and Event is not present by default in AIM-A. So, its permissibility needs to be added. Define permissibility for associations related to event objects is a part of and add visibility = false for EVENT class such that the Event class node doesn’t appear in the AIM-A dashboard (optional).
