Custom Query (73 matches)
Results (1 - 3 of 73)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #38 | fixed | A way to assess and record the condition severity of an asset when performing a preventative maintenance task | ||
| Description |
When 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. In the current configuration a task is the smallest unit that can hold this information. class ConditionSeverity {
String code
String recommendation
}
Base data: Code-Recommendation A - Normal Monitoring B - Increase Monitoring C - Replace 2-6 weeks D - Replace 1-2 weeks Possibly a 'recorded condition' domain class could be created and used: class ConditionRecord {
MaintenanceAction maintenanceAction
Date dateRecorded
ConditionSeverity conditionSeverity
}
Recording 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 is supplied by TaskProcedureRevisions. 'Work Performed', 'Part Changed' and 'Part Repaired' are separate conditions that will be indicated by an inventory item used on the task. |
|||
| #72 | wontfix | Add resource numbers to assigned group | ||
| #35 | fixed | Adding or removing assigned groups should trigger a modification to be recorded. | ||
| Description |
A task modification should be recorded for the above. |
|||
