Priority for activities

Seeking to assist users in the prioritization of activities, the possibility of classifying the activity according to the definition of a priority has been made available in the system. The user can create a rule to set the priority that will support the analysis of which activity to perform. The feature can be configured in the standard activity and replicated for the plans and activities.

 

 

 

Kanban for activities under execution

With the objective of allowing a better view of the activities that are to be performed in a certain period of time, a new portal was made available in the system with Kanban structure. The feature enables the company to be aware of the current workload of a team/position, demonstrating the completed activities, running, pending activities and having a vision of who is performing each activity.

The feature still enables the interaction with the cards, allowing users to associate activities for themselves as well as to perform it, directly through the Portal.

The Kanban vision can be configurable by components, view period and teams, which allows greater flexibility on which activities will be presented. The Kanban still makes it possible to have within the same vision the activities of Verification, Maintenance and Calibration in case the user wants to have a view of components.

 

 

 

Storage place presentation in plan view

For assistance in analyzing the plans, it was made available in the list of the plan view menu and also in Analytics the information related to the physical location of the asset associated with that plan. The information is available even for plans that have multiple assets.

 

Improvements in integration between maintenance activities and Workflow, Incident and Problem instances.

For customers who use the Maintenance component integration with a process instance through the Incident, Problem, or Workflow components, the system then copies the priority set on the instance automatically to the Maintenance activity, provided that the two systems have the same evaluation method. With this feature, the user avoids the need to have to reclassify the priority of the maintenance activity.  

Integration also performs the automatic link between the components, allowing the user to view the related information, regardless of the component that is being accessed. The link can be accomplished both from the instance to activity and from the activity to the instance. When creating an activity via webservice, the ability to perform the link between the activity and the instance is also available.

For maintenance activity, the possibility of associating Workflow instances as occurrence associations has also been added.

 

 

Hyperlink for activity data from Analytics

With the objective of broadening the possibilities of analysis, it is now possible through an Analytics view to access the related activity data. With this feature, the user manages to reach the level of details of the activity analyzed, without the need to have to perform a new view of the component.

 

Webservice for programmed maintenance

A new webservice is available for maintenance activity. Now through the webservice it becomes also possible the creation of programmed maintenance activities.

 

Modifications to the activity form report

By generating the activity form report and activity blank form, the user can choose whether to report the cost section information as well as the activity approvers section. For the reports, the information of Priority and of Asset type was also added.