Custom Query (73 matches)

With the concept of the maintenance technician entering the task and the production person entering the "fault entry" against that task there needs to be a clear work flow for sharing these task numbers.

One way to do this would be to reserve a number of tasks (say 5) for a technician and provide a report with the task numbers and space to write down the details. The technician could then print the report and hand the reserved numbers out to production as work comes up. Using the printed report to record the details in the space provided for later entering the "work done" into the task number. The production person would then have a task number to enter their "fault entry" against at any time they wish.

Another way to do this would be to make it very easy for the production person to list the "Immediate Callouts" for period and production reference. As these would be the only tasks to which this applies. They would then enter faults against these tasks. The constraint on this would be that all tasks must be entered (with descriptions) before the production person came around to wanting to enter their "fault entries" to produce their production report.

Some CMMS systems require the production person to create the task or work order and provide this number to the technician. This often fails since:

1. Production personnel don't know the correct asset names, technician or planner then often has to correct or adjust the task details.
2. The production person's world is often a busy one where taking time to enter a fault before calling a technician is simply not possible.
3. The technician should be providing a service to the customer.

• Note: This does not apply to "Work Requests" of a low priority where the production person may want to enter the faults or work requests at their leasure, this functionality should still be available.

For production report see ticket #41.

Each cost code or person needs a relationship and way to authorise management and purchase on that cost code (budget or ledger account).

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.