Activities recorded in Ewida Standard

In addition to keeping records of objects themselves, Ewida Standard also lets you record activities carried out on equipment and other items stored in the system. This makes it possible to keep not only records of what the company owns, but also a history of work performed on specific objects.

If you prefer a web-based solution for record-keeping and asset management instead of a Windows desktop application, also take a look at Codenica ITSM + ITAM.

In Ewida Standard, you can record four main types of activities:

  • repairs,
  • services,
  • upgrades,
  • maintenance.

Scope of individual activity types

Repair records apply to sets, devices, and consumables. The other activity types, namely services, upgrades, and maintenance, can be used more broadly across different object types, except for the user object.

It is up to the program user to decide how to classify events that occur in a given company and which category to assign them to. This makes it possible to adapt the working model to internal procedures. The wizards for each activity type have a similar structure, but they include fields specific to the type of event being recorded.

It is worth adopting consistent rules from the start so that similar events are recorded in the same way. This makes it easier later to filter data, analyze costs, and prepare reports.

Repairs and changes to object status

Of all recorded activities, it is the repair that can affect an object’s status. This makes practical sense, because an item being repaired may be temporarily taken out of use or sent for service. A status change then makes it immediately clear that a given piece of equipment is not currently available in its usual place of use.

The rules for status changes can be configured independently. This is worth keeping in mind especially when a company wants to clearly distinguish between active objects, retired ones, items under repair, or items waiting to be returned.

It is also important that before recording another repair for the same object, the previous one must be closed. The program does not allow two active repairs for the same item at the same time, which helps keep the event history consistent.

How activity recording works

All four wizard types have a similar layout. They mainly differ in the activity description and the set of fields that can be filled in. The overall workflow, however, is similar.

First, you select the objects to which the activity applies. Then you enter the event data. The left side of the form is usually used for identification data, while the right side is used for the description of the process itself, for example a fault, scope of work, maintenance, or upgrade.

If needed, you can add or remove objects covered by a given activity using the appropriate buttons. The program also allows different descriptions for different objects, which is useful when one operation covers several items but requires individual notes for each of them.

Updating data and printing a report

After entering the activity data, you can move on to updating selected object properties. This is especially useful for upgrades, when after the work is completed, things such as the software version, technical condition, or other important parameters change. You only need to remember that the selected properties must be added to the list of changes with the add icon button.

The final step is printing a report for the completed activity. This step can be skipped, but in many companies, printing or saving the report is an important part of the documentation. The program lets you choose your own print template and also decide whether several objects should be included in one report or whether each should receive a separate document.

Thanks to this, repair, service, upgrade, and maintenance records in Ewida Standard are not limited to a simple entry in the history. They can become full documentation of the work carried out on company equipment.