Inspections
Overview
Inspections
Overview
SedonaOffice contains functionality within the Service Module to generate Inspection Tickets in bulk. Many installed systems, particularly fire systems, are required by law to be inspected on a periodic basis. The application keeps track of how frequent a System requires an inspection, when the last inspection was performed and when the next inspection is due. Tickets generated for inspections and are viewable in a separate ticket queue which makes scheduling simple and easy to manage.
The application allows for multiple Inspections for a single System. For instance if a particular System requires an annual inspection, but also requires another inspection for the same System on a quarterly basis, multiple inspection records may be set up.
Since an inspection is related to a particular System, the setup of inspection information is input on a special form within the System record. Inspection information may be input after a new System record is manually created or when a new job is created. One of the required fields for an Inspection record is the Problem Code. When an inspection ticket is created, this problem code will automatically be assigned to the ticket. Suggested problem codes are: Annual Fire Inspection, Semi-Annual Fire Inspection, or Security Inspection. Problem codes are created and maintained within the SedonaSetup application.
When setting up an Inspection record, a Service Level may be assigned to the Inspection record that may be different than the Service Level assigned to the System itself. For example, the inspection service may be invoiced from the Cycle Billing process or invoiced to the customer each time an inspection is performed. Make certain the appropriate Service Level is assigned to the inspection so charges are calculated properly on the Inspection invoice.
For information on other Inspection related topics refer to the link below.