Changes between Version 4 and Version 5 of Ticket #38


Ignore:
Timestamp:
Feb 9, 2011, 5:50:03 PM (14 years ago)
Author:
Gavin
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #38

    • Property Summary changed from A way to assess and record condition/severity of an asset when doing a preventative maintenance task to A way to assess and record the condition severity of an asset when performing a preventative maintenance task

  • Ticket #38 – Description

    v4 v5  
    1 When doing a preventative maintenance task that has a procedure, it would be nice to be able to record partial completion of the maintenance actions and/or the assessed condition of the asset/assembly/component specified in each maintenance action.
     1When performing a preventative maintenance task that has a procedure, it would be nice to be able to record the assessed condition of the asset/assembly/component specified in each maintenance action.
    22
    3 In the current configuration a task is the smallest unit that can hold this information. So a maintenance task and procedure are either completed on time or missed and therefore the KPI for all asset/assembly/component's listed in the procedure is either achieved or not.
     3In the current configuration a task is the smallest unit that can hold this information.
     4
     5{{{
     6class Condition {
     7    String severity
     8    String recommendation
     9}
     10}}}
     11
     12Base data:
     13{{{
     14Code Recommendation.
     15A  - Repair Urgently
     16B  - Repair Soon
     17C  - Monitor
     18D  - No Action
     19}}}
    420
    521Possibly a 'recorded condition' domain class could be created and used:
    … …  
    824    MaintenanceAction maintenanceAction
    925    Date dateRecorded
    10     Condition condition (or)
    11     Integer rating (1-10 or 1-100?)
    12 }
    13 class Condition {
    14     String name (excellent, good, bad, very bad)
    15     String comment
     26    ConditionSeverity conditionSeverity
    1627}
    1728}}}
    1829
    19 The other option:
    20 {{{
    21 Severity.   Recommendation.
    22 A-Severe    Repair Now
    23 B-Medium    Repair Soon
    24 C-Low       Monitor
    25 D-Normal    No Action
    26 }}}
     30Recording the condition of each maintenanceAction in the database has been decided against, for now, in favour of recording the worst condition severity against the task. Printing the taskProcedure out and keeping the paper copy will suffice as report and audit trail.
     31
     32'Work Performed', 'Part Changed' and 'Part Repaired' are separate conditions that will be indicated by an inventory item used on the task.