This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
I got a request today to look into ways a site could document changes to a job plan, so a historical review could be done during an audit to show who made the change/revision, what date/time the change was made, and a description of what was modified. I explained that so we've managed documenting changes via the eaudit tables. After showing a demonstration of the details captured on the eaudit tables the person requesting the change said that was too complicated to show an auditor because of the field comparison.
I'm curious to hear how others are, or if you are, handling job plan revision history?
Jason,
We are using an aftermarket software from Xybion call Compressive Audit Trail (CAT) that ties to the audit tables. It displays as an additional Tab at the end of the module displaying all the changes for that record. There is no need to run a special report. We used it when we were using version 6.2 and successfully upgraded to version 7.5
The contact I have for Xybion is David 'dchiaramonte@xybion.com'
Roy Cline
Phone: (203) 492-8189
Cell: (203) 640-9743
FAX: (203) 492-8462
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, June 02, 2014 12:29 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Job Plan Revision/Versioning in Maximo
I got a request today to look into ways a site could document changes to a job plan, so a historical review could be done during an audit to show who made the change/revision, what date/time the change was made, and a description of what was modified. I explained that so we've managed documenting changes via the eaudit tables. After showing a demonstration of the details captured on the eaudit tables the person requesting the change said that was too complicated to show an auditor because of the field comparison.
I'm curious to hear how others are, or if you are, handling job plan revision history?
Jason, try creating a view with the pertinent information, then add a table to a new tab referencing the new view.
________________________________
From: "jason.verly@yahoo.com [MAXIMO]" <MAXIMO@yahoogroups.com>
To: MAXIMO@yahoogroups.com
Sent: Monday, June 2, 2014 11:29 AM
Subject: [MAXIMO List] Job Plan Revision/Versioning in Maximo
I got a request today to look into ways a site could document changes to a job plan, so a historical review could be done during an audit to show who made the change/revision, what date/time the change was made, and a description of what was modified. I explained that so we've managed documenting changes via the eaudit tables. After showing a demonstration of the details captured on the eaudit tables the person requesting the change said that was too complicated to show an auditor because of the field comparison.
I'm curious to hear how others are, or if you are, handling job plan revision history?
Jason, on second thought,
I am also thinking a simple relationship might also provide the information you need to show in the application.
________________________________
From: "wwilliams@rocketmail.com [MAXIMO]" <MAXIMO@yahoogroups.com>
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Sent: Tuesday, June 3, 2014 6:36 AM
Subject: Re: [MAXIMO List] Job Plan Revision/Versioning in Maximo
Jason, try creating a view with the pertinent information, then add a table to a new tab referencing the new view.
________________________________
From: "jason.verly@yahoo.com [MAXIMO]" <MAXIMO@yahoogroups.com>
To: MAXIMO@yahoogroups.com
Sent: Monday, June 2, 2014 11:29 AM
Subject: [MAXIMO List] Job Plan Revision/Versioning in Maximo
I got a request today to look into ways a site could document changes to a job plan, so a historical review could be done during an audit to show who made the change/revision, what date/time the change was made, and a description of what was modified. I explained that so we've managed documenting changes via the eaudit tables. After showing a demonstration of the details captured on the eaudit tables the person requesting the change said that was too complicated to show an auditor because of the field comparison.
I'm curious to hear how others are, or if you are, handling job plan revision history?
Jason,
There are a couple of serious flaws in Maximo native EAUDIT capability that you should be aware of when trying to use it. First as you've already mentioned, looking at the audit tables for change comparison is complicated. As others have suggested, that can be overcome with a view. I have views sitting on top of all my audit tables that show the old and new values of any audited fields on the same row. Secondly and perhaps more important, Maximo natively logs the NEW(current) value into the audit table. So the first time any record changes after turning on auditing, you will not natively have the old value for comparison or even to see what has changed. We purge our audit tables monthly so this really impacts us. So in order for auditing to be 100% effective, you have to come up with some strategy for seeding values. In our case, I simply augmented the native functionality to write two records to the audit table the first time any record is changed, the native one with the new/current value and one with the old value.
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, June 02, 2014 12:29 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Job Plan Revision/Versioning in Maximo
I got a request today to look into ways a site could document changes to a job plan, so a historical review could be done during an audit to show who made the change/revision, what date/time the change was made, and a description of what was modified. I explained that so we've managed documenting changes via the eaudit tables. After showing a demonstration of the details captured on the eaudit tables the person requesting the change said that was too complicated to show an auditor because of the field comparison.
I'm curious to hear how others are, or if you are, handling job plan revision history?
Jason, what version are you in? JP revision control is available in 7.1.x and up (I believe even in later patches of v6). We were unable to move to electronic Job Plans until we upgraded to a version that has revision control - we're an FDA, CFR Part 11 site. I totally understand not being approved by your org to use the audit tables. It does have some holes as one has mentioned on this site. However, the revision control in v7 is pretty slick. We route new JPs and JP edits through workflow, and provided an additional "revision details" text box with greater text capacity to provide the justification notes. This matches the justification requirements of our former paper process and helped us gain QO approval for this new process. HTH.
Bill Murphy
Grifols Therapeutics