Designing a CAD deployment should never be considered a trivial task. Even a cursory glance through this manual section is enough to show the amount of thought and planning required in order to most efficiently apply the flexibility built into Tickets (or any other CAD system, for that matter). While it is possible to install and deploy Tickets in a very short time, producing a logical, usable and meaningful workflow should always be a high priority for anyone who will administer and operate the installation. The task of CAD deployment design is far beyond the scope of this manual. I highly recommend reading this manual completely and thoroughly before beginning any configuration you intend to place into a production environment. By doing so you will learn what configuration options are available, and therefore can plan to maximize those options in a manner that best suits your needs.

There won’t be a single “right” way to configure each of the described options of Tickets, because each installation will be for a different purpose, in a different area, and with a different focus. Still, the procedure outlined below will give you a good framework for setting up the various options available. I’m going to outline a comparatively simple configuration for use in a fire/EMS environment, and the options I’ve chosen are based on my own personal experience with what managers in my area want recorded and reported. Your setup will likely look only marginally like the examples provided.