Problem Repairs

Problem Repairs are technically just another type of problem, but they're intended to show the documentation of a something that is no longer a problem.  For example, an overheating breaker that is caused due to a loose connection could have a repair that explains the steps taken to correct the problem and the new temperature readings that demonstrate that the breaker is now operating within normal temperature ranges.  Problem Repairs track who repaired the problem, when it was repaired, and the details of what was done.  Problem Repair Reports look very similar to Work Orders, except that the repair data has been filled out and exists within the customer database.  Problem Repairs are always continuations of existing problems.  That is, you cannot create a problem repair from scratch.  Also, problem repairs must be the very last entry in a chain of problem documentation.  You cannot continue a recurring problem chain after repair documentation has been created.

Problem repairs use the same detail form as regular problems, but most of the time the data filled in to the detail will result in a "Normal" or "Pass" severity to demonstrate the problem doesn't exist any more.  However, it's entirely possible to create a problem repair that shows a reduction in severity, perhaps from critical to minor.

Follow these steps to create a problem repair:

    1. In either location or equipment detail, select the problem you want to create repair documentation for.
    2. Choose "New Repair".
    3. Optionally, choose "Go To Repair" and enter the data for the repair.

A new problem repair will pull all relevant existing data from the problem it is created from, so basically a problem repair starts as a snapshot of the problem.  Then, for an electrical problem for example, you can change the temperature data, amperage readings, risk to production/safety and so on to reflect the new repaired condition.