adempiere/enterpriseassetmaintenance

ADempiere Enterprise Asset Maintenance

ADempiere Enterprise Asset Management

Enterprise asset management (EAM) is the optimal lifecycle management of the physical assets of an organization. It covers subjects including the design, construction, commissioning, operations, maintenance and decommissioning/replacement of plant, equipment and facilities.

Getting Started

• Download and install ADempiere last versión from https://github.com/adempiere/adempiere/releases
• Download adempiereEAM project using git user git clone https://github.com/adempiere/adempiereEAM
• use gradle for build
• Run it

License

This project have License GNU/GPLv2 or later.

enterpriseassetmaintenance's Issues

Improve the prognosis process

Currently the prognosis is based on preventive maintenance which are linked between parents and children, therefore for example if I have a maintenance at 20,000 km, the 40,000 km maintenance is the father of the 20.000 km, but then the 40,000 is the son of the 80,000.
Therefore the maintenance of 80.000 km is the father of the 40.000 km maintenance and also is grandfather of the 20.000 km.

It is for this reason that the relationship of father and children in maintenance must be modified and the process of prognosis must also be modified to correctly handle the relationships between maintenance.

Regards

Alberto Abudinen
OFB Consulting

Suggestion for change table name

Currently exist many tables with long name, i propose change the name for a better definition:

• AM_AssetMeter_Log -> AM_AssetMeterLog
• AM_MaintenancePattern -> AM_Pattern
• AM_MaintenancePattern_Task -> AM_PatternTask
• AM_MaintPattern_Resource -> AM_PatternResource
• AM_Maintenance_Task -> AM_MaintenanceTask
• AM_Maintenance_Resource - > AM_MaintenanceResource
• AM_ServiceOrder_Request -> AM_ServiceRequest
• AM_ServiceOrder_Task -> AM_ServiceOrderTask
• AM_ServiceOrder_Resource -> AM_ServiceOrderResource

The new table definition is more readable.

Generate Internal Use Inventory from Work Order.

It is very necessary that at the moment of having clarity of the work order, the person in charge of carrying out the maintenance, make the request to collect all the products (spare parts) needed for maintenance from the warehouse.

Therefore the ideal is that from a work order, ADempiere generate an inventory internal use to the warehouse. The idea is to have a button that generates inventory internal use from the work order and then the Warehouse clerk can validate the location of each product.

Regards

Alberto Abudinen

Error when trying to run the migrate scripts (XML files)

I have some errors when I run the migratio script (./RUN_MigrateXML.sh).
These are the steps to reproduce this error:

1. Sincronize last version of adempiere380 hotfix 2 branch
2. Import seed data base
3. RUN migration for upgrade data base to last version (380lts-release folder)
4. At this point, everything is ok
5. Delete all files from Adempiere/migration/380lts-release
6. Copy migration files of adempiereEAM on Adempiere/migration/380lts-release
7. Run migration script again, and then these errors happens:

11:46:30.359 MMigrationStep.rollback: Migration 10 - 01 PM Asset Maintenance Module - null (D) ; Step: 10; Type: AD. successfully rolled back [1]
11:46:30.359 MMigrationStep.rollback: Migration 10 - 01 PM Asset Maintenance Module - null (D) ; Step: 10; Type: AD. successfully rolled back [1]
11:46:30.360 GridField.loadLookup: (AccessLevel) [1]
11:46:30.360 GridField.loadLookup: (AccessLevel) [1]
11:46:30.360 GridField.loadLookup: (ReplicationType) [1]
11:46:30.360 GridField.loadLookup: (ReplicationType) [1]
11:46:30.363 MMigration.syncColumn: Synchronizing column: MColumn[0-null] in table: MTable[0-null] [1]
11:46:30.363 MMigration.syncColumn: Synchronizing column: MColumn[0-null] in table: MTable[0-null] [1]
11:46:30.363 GridField.loadLookup: (AccessLevel) [1]
11:46:30.363 GridField.loadLookup: (AccessLevel) [1]
11:46:30.363 GridField.loadLookup: (ReplicationType) [1]
11:46:30.363 GridField.loadLookup: (ReplicationType) [1]
-----------> MMigration.apply: @NotFound@ @AD_Table_ID@ 0 [1]
-----------> MMigration.apply: @NotFound@ @AD_Table_ID@ 0 [1]
11:46:30.392 MMigration.updateStatus: Migration 10 - 01 PM Asset Maintenance Module - null (D) ---> Unapplied (U) [1]
11:46:30.392 MMigration.updateStatus: Migration 10 - 01 PM Asset Maintenance Module - null (D) ---> Unapplied (U) [1]
11:46:30.408 MMigration.updateStatus: Migration 10 - 01 PM Asset Maintenance Module - null (D) ---> Unapplied (U) [1]
11:46:30.408 MMigration.updateStatus: Migration 10 - 01 PM Asset Maintenance Module - null (D) ---> Unapplied (U) [1]
11:46:30.409 MigrationApply.addLog: 0 - null - null - @NotFound@ @AD_Table_ID@ 0 [1]
11:46:30.409 MigrationApply.addLog: 0 - null - null - @NotFound@ @AD_Table_ID@ 0 [1]
11:46:30.413 Msg.initMsg: Records=1429 - en_US [1]
11:46:30.413 Msg.initMsg: Records=1429 - en_US [1]
===========> MigrationApply.process: * Not found * Table 0 [1]
org.adempiere.exceptions.AdempiereException: * Not found * Table 0

Thanks.

Menu entries not displayed in menu tree

XML file 20AssetMaintenance WindowAndMenu.xml creates menu entries for windows of the EAM module like Meter or Meter Log.

After executing the xml file, the menu table contains the entries, but they are not displayed in the tree, as can be seen in the following image.

MaintenancePatternType is necessary?

Currently the AM_Pattern have MaintenancePatternType column but not exist a description about it

Error Executing file 30_AM_Module_Form_View.xml

While executing file 30_AM_Module_Form_View.xml, the following error is encountered:

The log is as follows:
-----------> MMigrationStep.bailout: Migration 30 - 03 AM_Module_Form_View - null (D) ; Step: 3590; Type: AD. Application failed: org.adempiere.exceptions.AdempiereException: ERROR: duplicate key value violates unique constraint "ad_column_name"
Detail: Key (ad_table_id, columnname)=(539, C_Activity_ID) already exists.

Looking into the database, the table A_Asset has already a column named C_Activity, which step 3590 is trying to insert:

Step SeqNo="3590" StepType="AD"
:
PO AD_Table_ID="101" Action="I" Record_ID="80461" Table="AD_Column"
:
Data AD_Column_ID="114" Column="AD_Table_ID">539
Data AD_Column_ID="2608" Column="AD_Element_ID">1005
Data AD_Column_ID="116" Column="ColumnName">C_Activity_ID
Data AD_Column_ID="111" Column="Name">Activity
:
:
/PO
/Step

Upload test database

A database for testing is needed, so it is not necessary to execute all Adempiere xmls in order to test.

This is only for testing reasons and has to be ignored when doing the pull request.

Refactory Project

This issue is for report a refactory of project, and make reference with:

#10
#11
#12
#13
#15
#4

Change Special Forms for Smart Browsers

There are Special Forms inside the Maintenance module.
One example is converting Forecasts into Work Orders.

The problem of special forms is that they have to be programmed from ground on (filter, display, callouts, etc.), and also must exist one for each UI (in our case Swing and ZK).

If instead these forms where implemented as Smart Browsers, the displaying, filtering, etc. would be very easy and also UI-independent. Moreover, the enhancement and bug-fixing would become much more efficient.

Add new Entity Type for Assets Mantenance

It issue is for report a new entity type for asset maintenance

Change column name definition

The column name AM_ProgrammingType of AM_Maintenace will should be ProgrammingType is not good a prefix when exists a table prefix

Remove unnecessary views

Currently exist the follow views:

• AM_Asset_Meter_Log_V
• AM_Assets_V
• AM_Maintenance_Calendar_V
• AM_Maintenance_Meter_V
• AM_MaintenancePattern_V
• AM_Maintenance_V
• AM_ServiceOrder_V

The views are create for PostgreSQL only, i propose remove all and create only necessary view. Also it will should create with RV_ prefix instead _V suffix

Missing windows when defining menu entries

The XML 20_AssetMaintenance_ WindowAndMenu.xml creates windows for this EAM module and -after the windows have been created- it creates menu entries for each window.

Nonetheless, the following windows are missing altogether: Maintenance Forecast, Meter Log and Required Service Order.

They have to be added in to the menu.

Error executing 40_AM_Module_Process.xml

When executing XML file 40_AM_Module_Process.xml there are exceptions thrown.

Create gitflow infrastructure

Create buttons to calculate costs

In windows Maintenance Pattern, Preventive Maintenance, Request Service Order and Work Order, there must be a button to calculate the theoretical costs. These buttons are missing altogether.

See also #7.