Custom Query (73 matches)

• Many assignedGroups may be added to a task.
• Many assignedPersons may be added to a task.
• A persons tasks would be every task that they are assigned to and every task that any group that they belong to is assigned to and every task where they are lead person.
• Record changes to assigned groups as modifications see ticjet #35
• Allow a targetStartDate for the assigned group? No this would then be better as a sub task.

• The person groups now have the added benefit of acting as a training/qualification record. Since only persons trained/qualified to be in the group are added to that group.

Implemented in r239, r240, r241, r242, r243, r245.

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.

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