Versions 1.28.x

The method of handling the emission monitoring history form check has been changed. Currently, exceeding the registration deadlines for a given event resulting from the schedule does not affect the possibility of saving history. Instead of blocking the recording, the system displays a message informing about exceeding the deadline.

A list of invoices divided by cost category has been added to the analytical view of leases. This way, the user can analyze lease costs by category. The function and view are only available when the Finance module is enabled.

The way analytical data is displayed in work progress has been changed. Currently logged data is now taken and compared to the total number of supervised items to calculate the percentage progress.

SQL data editor with syntax highlighting has been added. The user has the ability to edit SQL data in a convenient way, with SQL syntax highlighting, which makes it easier to work with SQL queries. SQL integration views have been modified in this way.

In the employee detail view, the employee’s assigned schedules for individual days also appear in the calendar.

The event history has been expanded and most key elements in the system save their change history. Changes can be viewed in the configuration module along with a comparison of the difference in field values between subsequent events.

In the definition of events and schedules, there is now an option to copy them to a new one. Just select the appropriate option from the context menu and the full configuration will be copied to the new object.

For attachments, the file information window displays information about the user who created or uploaded the attachment.

In the event editor, there is a button that displays the available event templates. Templates allow you to easily fill in all the necessary fields in the editor. They make it easier to create events, and also allow you to quickly add an event rule and customize it to your needs.

In the configuration and list of all notifications in the application, a Test button has been added, which allows you to generate a test notification. Such a notification can be seen in the main interface of the application.

Error messages have been modified. Production versions display a general error message, while beta versions display a detailed error message.

In the view of changes available in the application, the ability to display a list of all presented information has been added. After enabling it with the button, a list appears that allows you to go to the information you are interested in without having to go through all the elements in the list of changes.

AMAGE has changed the update method to continuous update within the next major version. Using the information window you can find out the exact release date of the version and detailed configuration information.

The archive instances of the AMAGE system received the appropriate information after logging in to them. Information about the instance working in archive mode appears at the bottom of the screen. Archive mode allows you to view the contents of the instance, but does not allow you to make changes to the data.

An additional context menu for each parameter has appeared in the list of parameters in the resource. It allows you to change the parameter value, but also access the automation module, if it is enabled. The module allows you to define events and schedules dedicated to a given parameter. Events will be performed only for a given parameter (specific object), and not for all resource parameters or all parameters in the system.

The supervision status history importer has received an expanded section for updating existing supervision history. When a history entry is found that matches parameters or identifiers (UUID, ID), the fields in the history record are updated. The parent parameter is also updated accordingly.

In the context menu action of the article for a document in the Register of Legal Obligations module, the ability to add an article above/below an existing article has been added. We select the action "Add above/Add below", which causes new elements to be added not at the end of the list, but in the selected location. Additional actions allow the article to be moved up/down the list.

The REST API system has been extended to include the ability to upload files/attachments to resources, item types, and work orders. To do this, use the appropriate REST API terminals. More information in the REST API documentation in the appropriate section of the AMAGE Academy.

The integration mechanism with GSW weighing systems has been modified to enable handling of product code changes in the GSW system and updating of records in AMAGE. The system automatically corrects records in AMAGE if the product code in the GSW system is changed.

During the definition of additional parameters that are imported from the source XLS file, we have the option of copying the description from the column header from which we are importing data to the parameter name. To do this, click the Copy button.

Importers, when importing a date from an external source (Excel/CSV), try to recognize the date in the YYYY or YYYY-MM format in addition to the standard existing formats. If such a date is recognized, the system automatically fills in the missing fields from the date, e.g. day and month, with the values 01.

The resource importer has been extended. When a record is detected for update, sales fields such as dates, deadlines, etc. are also updated. Previously, they were not included when updating a record.

New importers from CSV/XLS formats have been added, which allow importing contractors and contacts to contractors.

A simplified import view has been provided for all modules that allow data import. This allows data import functionality to be made available to standard users. It is required to predefine data import templates in the system configuration section.

The work order history importer now has an additional option to search for existing work order history records, e.g. to update it by record ID/UUID. This allows for more reliable and precise finding of records for update.

The system allows for categorization of invoices, e.g. division of invoices into purchase, lease or repair categories. The lease analytical dashboard has been extended with a view of invoices broken down into cost categories. In this view, you can see invoices broken down into cost categories, as well as see the totals of invoices in each category.

Added ability to move items in the tree structure of locations and product groups by selecting an action from the context menu. The existing Drag & Drop move is still available. Moving using the context menu action is especially useful when moving items between different branches of the tree.

After adding a new option "Join with …​" in the context menu in Locations and Product Groups, the user can now connect selected locations or product groups with other locations or product groups. The system will automatically replace the occurrence of the location or product group in the database structure, as well as in related records. Finally, the record that was connected to another record will be deleted from the system.

In the attachment view in the element tabs, e.g. in assets, it is now possible to display attachments from other related objects, e.g. from the Element Type. This allows you to quickly display data for a specific resource in one view, e.g. photos, information about a specific resource, but also display attachments from related objects, e.g. from the Element Type, e.g. catalog cards, user manuals, certificates, etc.

In the mobile view, the ability to display the history of parameters has been added. To do this, go to the detailed view of the resource, then display the parameters and select the chart button for a specific parameter.

If asset’s parameter charts include more than one parameter, a legend describing the chart colors is also displayed.

Applies to mobile view. In the asset’s parameter list, if there are no parameters that do not have any category, then the group displaying these parameters is not presented in the mobile view.

An automation has been added that allows for notification of selected users about the lack of change in parameter values over time or the lack of new parameter values over time. Such an automation allows for detection of lack of communication with selected devices or external systems that should provide information on an ongoing basis. It also allows for a quick response to the lack of data, which can be crucial in the case of monitoring important parameters.

More:

The interface of the work order details view has been slightly modified. The work order history button was moved to the top bar. In addition, all buttons have been made more prominent in the interface. Links to charts and shortcuts/analyses were added to the work order history view. The tasks in the work order history view have been simplified. The work order history table was also modified to display two lines of information in a more condensed manner.

In the contractors list view, a "Join with…​" action has been added to merge selected contractors with another contractor. The merge involves transferring all events, documents, tasks, notes, assignments and tasks ordered from the selected contractors to the contractor they will be merged with. Finally, the source contractor is deleted.

The Change UUID action has appeared in the context menu of parameter settings for the selected resource. This allows you to arbitrarily set the value of the item’s unique identifier. This can be useful, when using the UUID in integration systems between multiple instances or when the aggregator device is to send data to multiple parameters in different instances of the AMAGE system. Then the same UUID is required for all parameters to be handled by the aggregator device.

A Guardian field has been added to the Contractor Contacts module, which allows you to assign a system user to a contractor. This field is available in the Basic Data tab. It allows you to enter data that indicates the contact person for the person from the company’s staff. This data can also come from an external information system, such as a ERP or visitor registration system.

Added the ability to specify the competency of a contractor’s contact from the main competency dictionary. This makes it possible to determine what competencies a person has, e.g., electrical licenses, health and safety training performed, etc.

The ability to define competencies for an employee from the internal employee editor has been added. These competencies are defined in the Competencies tab.

An additional Calendar tab has been added to the assets list view, where expiration/calibration records for assets identified as equipment and warranty dates for all assets appear as calendar entries.

In the history of work orders, the ability to change a specific history entry as invalid has been added. Once it is marked as incorrect, it is withdrawn from analyses and reports. All material consumptions that arise from such a history entry are also marked as incorrect. The status can be restored by changing the status of the history entry to correct.

In the work order detailed progress reporting form, the ability to report work hours for a specified number of employees has been added without selecting them from the system user/employee list. When the number of employees to report work hours is defined in the work order, a field appears in the work order progress detail reporting form where you can enter the number of employees for whom work hours are reported.

The interface for changing the status of a work order has been modified so that for users with the appropriate authorization in the work order, the ability to select the date for changing the status of a work order appears. If the user does not have the authorization to change the date, the date selection field is unavailable. We have the option to specify the date of the event registration.

Two additional types have been added to the question type - date and date+time. This allows in the user interface to use appropriate controls to make it easier to enter the answer to the question. In the system, value data is stored in ISO format.

A number of navigation and user interface improvements have been made to the LOTO (Lock Out Tag Out) module. Changes include:

The ability to generate a report for individual LOTO points and a summary report of a list of LOTO points has been added. The reports are available in PDF format and contain information about LOTO points.

The ability to filter the view in the IFC viewer with the upgrade of the display engine to the latest version.

IFC model viewer available as a local display system with linkage to the resource structure in AMAGE.

Moved all functionality from existing static dashboards to the new definable dashboard engine. New controls have been added to visualize data from the AMAGE system, allowing all available static dashboards to be visualized with the new solution.

In multi-charts view, the ability to copy a parameter to display from an already defined one has been added. This makes it easier to create new summary charts using already defined parameters.

An automaton that allows the transformation of the value of one parameter to another parameter or to production data. The automaton allows, for example, to rewrite data from a parameter continuously collected from some device (energy meter value) or data from external IT systems stored in parameter settings to production data at the end of the month using additional actions and aggregation.

More:

Production data is exported to XLS format with the accuracy of decimal places according to the settings in the system. Previously, they were always exported with 2 decimal places.

Production parameter data that has a value set that the data is the average value for a given period is displayed in the summary in the date range list in direct form. However, the summary of the period’s value for these data correctly displays the average of the period instead of the sum of the data (as for other data).

The data aggregator application in its statistical data sent periodically (heartbeat) to the AMAGE main server also includes information about the available disk space on the server. This allows for possible diagnostics and reaction to a situation in which the server is approaching exhaustion of available disk space.

In the employee schedule view, the ability to call up hour statistics for selected employees has been added. After selecting an option from the menu, a window appears indicating a summary of the number of hours for a specific schedule type for each employee and pie charts for all selected employees, and for the currently selected one.

In the attendance report, data generation has been improved, translations have been supplemented, information on registration time and an hourly summary have been added. The report is a supplement to the attendance module, which allows for the registration of attendance within the AMAGE system or importing information from systems such as Work Time Registration. This data allows for the verification of employee attendance during the performance of activities and comparison of information with data registered in other modules, e.g. work orders or supervision over performance.

The attachment API has been expanded.

More:

In the integration of external systems, character strings are used to recognize the target account/warehouse. From now on, if the character string starts with the character of the beginning of the regular expression text, i.e. ^, the system will recognize accounts/warehouses according to the given regular expression pattern. Otherwise, the text will be searched for inside the information in the integrated document as a regular text search.

In the warehouse document view, the unit price of the material in the document has been colored (red) if this price is different from the catalog price entered in the element type. This allows you to detect a price change in the warehouse document in relation to the catalog price/agreed during contract execution. The function is identical to the existing function for the order details view.

In the mobile events view, event type icons have been added, as well as an expanded filter that allows you to display events assigned to a user and events reported by the user.

New features have been added to the AMAGE REST API for the Work Orders and Supervision modules. They allow you to:

The AMAGE REST API documentation has been updated with new features.

For more information, see the sections:

Virtual inspections have been renamed to bulk inspections. This change is intended to better understand the functionality of virtual inspections, which are bulk and apply to multiple objects at once.

Major expansion of the inspection module. Virtual inspections have been renamed to bulk inspections to better reflect their nature. The ability to create inspection plans for bulk inspections has been added. Bulk inspections are dedicated to a specific location. They can group resources and as part of such an inspection, the devices will be checked and their parameters will be updated according to the reported data.

All sections of the system take into account the scheduling, execution and reporting of single as well as bulk inspections.

In addition to the text filter, three buttons have been added to the main toolbar to quickly display service events:

Added the ability to download supervision history record data via REST API.

For more information, see the sections:

A new REST API interface has been added that allows for resource operations. First, methods have appeared that allow for modifying parameter setting values. We can get parameter setting properties and add a new parameter history record.

For more information, see the sections:

The standard login form has gained the ability to show the entered password using the Show password button. This allows the user to check the correctness of the entered password.

The user list context menu (configuration section) has been expanded with two additional actions allowing for mass assignment/removal of a selected permission profile from the list of selected users.

Some automations available in the system have been given the System flag, which makes them available only through the system configuration interface for system administrators. This allows you to hide automation work whose task is, for example, integration with external systems from regular system users in their view of the definition of events and automations available for each section of the system.

The ability to synchronize warehouses with Asseco Merit/Xpertis software has been made available in system integrations. The automaton allows synchronization of warehouse documents and updating of the warehouse status in the AMAGE application in accordance with the balances in the ERP system. This facilitates the verification of stock levels of materials in the formal warehouse of the ERP system at the same time allowing for operational management of quantities, e.g. after they have already been released from the parent system for fiscal reasons.

Additional security measures have been implemented throughout the system during record deletion. After selecting the Delete action, an additional record deletion progress window appears. The progress bar updates continuously during record deletion. If the deletion is successful, the window closes automatically. In the case of deletion errors, the window remains visible, and the Info button is enabled, which allows us to display a detailed message about deletion conflicts.

The system checks all the links of the deleted record and stops deleting the given record in case of conflicts. This makes it easier to properly clean the database from all the dependencies.

The service incident report has several sections that show additional information such as comments, attachments, photos. In case these sections are empty, they are not displayed in the report. In case these sections are filled, they are displayed in the report.

You can use a configuration flag to allow a service event state to change without having to add a comment. When the flag is set, the user does not need to enter a comment to change the service event state.

In the service event comment view, the user can change the event type. To do this, select the appropriate event type from the drop-down list. The change is saved in the event and in the comment along with the date and time of the change.

With the new permissions you can manage access to service event types. Permissions can be assigned at the department or user level. Only people indicated by these parameters will be able to create/change a service event type.

With the new permissions, you can manage access to changing service event states. Permissions can be assigned at the department or user level. Only people indicated by these parameters will be able to change the service event state to the specified one.

Thanks to the new functionality, the user can permanently remember the selected service event view. After re-entering the module, the service event view will be the same as the last selected one.

A service module configuration flag has been added that allows you to specify the visibility of specific types of service events and their states depending on the permission definitions for each of these definitions. After enabling the flag:

Standard users (not super-admin!) only have access to tickets where they are described as users or departments with access.

When saving the emission monitoring history, we can enable the option Further steps are not needed. This will allow you to mark subsequent steps as completed and the entire process as completed. This makes it easier to register and view monitoring that does not require, for example, notifications to external organizational/notified units.

The production plan parameter editor has been expanded with an additional action that allows you to check the completeness of parameters and equations in the production plan. This action checks all equations for each month of a given year and verifies the correctness of parameter names. If a parameter does not exist in the system, an error message will be displayed.

W trakcie edycji/tworzenia dokumentu przyjęcia magazynowego możemy zaimportować elementy składowe dokumentu z pliku XLSX. Dodano do formatu importu możliwość importu wg. indeksu magazynowego. W przypadku podania indeksu magazynowego zamiast numeru zamówieniowego system pozwala na wprowadzenie tych danych.

Format danych importu (plik XLSX):

Dodano nowy importer, który pozwala zaimportować ustawienia parametrów z zewnętrznego źródła. Na podstawie danych system automatycznie tworzy odpowiednie parametry i ustawienia parametrów w zasobie.

Dodano możliwość określenia tekstu opisującego działania w planie inspekcji. Tekst ten będzie widoczny w widoku planu inspekcji oraz podczas wykonania inspekcji

Podczas definicji grupy dashboardów mamy możliwość, aby umieścić daną grupę w głównym menu. Od teraz nie musimy podawać już istniejących głównych wpisów np. Struktura, ale możemy wprowadzić dowolną nazwę, która będzie wyświetlana w menu systemowym jako główny element menu.

W przypadku inicjalizacji nadzoru, gdy jest duża ilość obiektów do zainicjalizowania, postęp inicjalizacji jest wyświetlany w tle. Dzięki temu użytkownik nie musi czekać na zakończenie inicjalizacji, a może kontynuować pracę w systemie. Wykorzystano do tego nowe okna dialogowe powstałe w trakcie implementacji mechanizmu usuwania obiektów.

Widok parametrów zasobów w dashboardzie został wzbogacony o dodatkowe możliwości wizualizacji. W nowej wersji możemy wyświetlić parametry w formie wykresu liniowego i słupkowego. Dodatkowo możemy określić okres, z którego dane są wizualizowane oraz wyświetlić różnice między wartościami z dwóch okresów.

W aplikacji PVD (agregator danych) dodano w protokole MODBUS obsługę formatu danych int32 w rozszerzeniu do uint32. Można wybrać odpowiednią reprezentację danych. Więcej w dokumentacji użytkownika aplikacji PVD.

Więcej informacji o dostawcy PVD - MODBUS

Schedulery systemowe są dostępne tylko w sekcji konfiguracji. Są to schedulery, które są używane przez system i nie powinny być edytowane przez użytkownika w głównym interfejsie. Takie automaty to np. integracje z zewnętrznymi systemami IT. Takie schedulery dostępne są jedynie w sekcji konfiguracji systemu.

Dodano możliwość opisania kroku dla każdego elementu z listy w oknie Obchody. Pozwala to na określenie oprócz standardowych informacji z operacji (pytanie/pomiar/zadanie) dodatkowych informacji dla użytkownika. W przypadku, gdy nie podano tych informacji dla danego elementu, to w oknie Obchody nie będzie wyświetlany opis kroku.

System zapisuje czas rozpoczęcia i zakończenia obchodu. Wprowadzono nowe pola w oknie Obchody. Mechanizm aktywuje czas rozpoczęcia obchodu w momencie jego pierwszego uruchomienia. Zakończenie obchodu następuje z chwilą zamknięcia obchodu poprzez operację Zakończ. Dane te dostępne są w szczegółach obchodu technicznego oraz w raportach.

W trakcie wykonywania obchodu mamy możliwość zapisania dodatkowego komentarza dla każdego kroku obchodu. Pozwala to na zapisanie dodatkowych informacji/obserwacji w trakcie obchodu. Komentarz jest widoczny w szczegółach obchodu technicznego oraz w raporcie.

Zmodyfikowano sposób definicji harmonogramów obchodu dla różnych dni tygodnia. Teraz możliwe jest zdefiniowanie wielu harmonogramów dla różnych dni tygodnia. Definicja dni tygodnia została przesunięta do poszczególnych godzin obchodu. Pozwala to na określenie różnych harmonogramów obchodu np. w dni robocze, weekendy, święta.

Dodano dodatkową możliwość zapisania podczas wykonywanego obchodu dodatkowych czynności, które są powiązane z realizacją obchodu. Słownik czynności Akcji definiujemy w sekcji konfiguracyjnej lub w widoku szablonów obchodu.

DLa akcji w trakcie obchodu można dodać dodatkowy komentarz lub zdjęcie. Formularz został rozszerzony nie tylko o wybór typu akcji, ale również dodatkowy komentarz oraz możliwość dołączenia zdjęcia/załączników.

Rozbudowano raport obchodowy o możliwość grupowania wyników wg. lokalizacji/sekcji/zasobu. Dzięki temu użytkownik może zobaczyć, jakie czynności zostały wykonane w danej lokalizacji/sekcji.

W interfejsie wykonywania obchodu dodano dodatkowy przycisk, który pozwala na wyświetlenie obchodów wykonywanych aktualnie przez innych użytkowników. Możemy za pomocą tej akcji pobrać obchód aktywny od innego użytkownika i go dokończyć.

Dodano możliwość zbiorczego wydrukowania identyfikatorów dla wszystkich urządzeń/lokalizacji, które zostały przypisane do obchodu. Dzięki temu użytkownik może wydrukować identyfikatory i przypisać je fizycznie do urządzeń/lokalizacji za pomocą jednej operacji.

Rozbudowano interfejs API REST dotyczący zleceń pracy. Dodano możliwość operacji na zasobach przypisanych do zlecenia pracy.

Szczegóły:

Dodano nowe API REST dotyczące operacji na typach elementów, parametrach definiujących te typy oraz szablonach parametrów. Za pomocą tych operacji możemy wykonać wszystkie czynności dotyczące tych obiektów.

Szczegóły:

Dodano kilka usprawnień w edytorze obchodów: