SedonaSchedule                               SedonaSchedule Designed Functionality                      Generate Inspection Tickets

Generate Inspection Tickets

Inspection Ticket Generation

This topic will briefly describe how Inspection Tickets are generated.  Step by step instruction are found under the SedonaSchedule Processing topic.  The purpose of this topic area is to provide an overview of how the Inspection Ticket generation process is designed.

The Inspection Ticket generation program within SedonaSchedule creates tickets in bulk based upon the information contained in the Inspection Setup records that are attached to a Customer’s System record within the Customer Explorer.  Inspection Tickets and Vendor Inspection Tickets are generated at the same time.  If an Inspection Record is setup with a Service Company that is a Service Provider, then that ticket will be created as a Vendor Inspection ticket.

 Inspection Tickets are typically generated once a month for Inspections due in the next month to allow time to plan for the needed resources.  Typically one staff member is responsible for generating all of the Inspection Tickets for the company.  For companies operating under multiple physical Branch locations, you may place this responsibility with each Branch office.  When selecting which Inspection Tickets to create, you may filter on a particular Service Company.  If you have created unique Service Companies for each Branch office, and the Inspection Records are linked to the appropriate Branch Service Company, then producing Inspection Tickets at the Branch level can be delegated to the Branch offices.

As mentioned earlier in this topic group, processing and completing Inspection Tickets on a timely basis is essential to staying on schedule with the contractual commitment with your customer.  The application will not generate the next Inspection Ticket until the currently open Inspection Ticket has been completed and closed.  When an Inspection Ticket is Closed, the software updates the Next Inspection Date on the Inspection Record setup.  The Inspection Ticket generation program looks at the Next Inspection Date on the Inspection Record to determine which Tickets need to be created.

For example, an inspection is to be performed quarterly beginning in January.  Which means you should be inspecting the system within the quarters beginning in January, April, July and October.  If the January Inspection Ticket is generated but not yet Closed when you generate your Inspection Tickets for April, the inspection will be skipped.  Due diligence on the part of your company is necessary for success when using the automated Inspection Ticket generation process.

                                                                      Page  1  of  4                              Next Page