|
|
|||||
 Introducing PTWin32 |
Here
is an imagined example of how PTWin32 report writing capabilities can be used to
quickly solve unexpected problems. Your
commissioners have a meeting in which they compare the number of inspectors
on-staff against the number of permits issued. They believe these numbers
justify cutbacks in staffing. In
response you quickly create a PTWin32 Ad Hoc report that compares the number of
inspectors on-staff against the number of inspections performed. This presents a
new picture that reveals the many inspections and re-inspections required for a
single permit. These new workload statistics validate current staffing and
cutbacks are avoided. But
you decide there is more to this issue than clarifying your department’s
activities. In printing your report you have discovered that nearly 20 percent
of your inspection activity is spent re-inspecting building projects that have
failed your code requirements. You
return to PTWin32 to investigate and discover that among the bundle of
pre-defined reports included with PTWin32 there is a report that shows permits
awaiting re-inspection called reinsp.srw. You run the report and discover
that most of your failed inspections are of foundations. You
decide to keep digging and set up a new query on the Define Search page
that sorts failed permit inspections by primary contractor. Just
as you suspected there are a few primary offenders so you decide to layout your
report as a warning letter that lets them know they have been identified as
having failed an inordinate number of inspections. You push the Print Report
button and your letters appear at the printer. You
create a new query using PTWin32’s Scheduling tables and find that the
contractor responsible for most of the failed foundation inspections is
scheduled for a foundation inspection in two days. You use the opportunity to go
out there to talk to them about improving their performance. When
you return you find a request from the Zoning Board. They would like a list of
all parcels that are zoned for commercial use. Once
more you find that PTWin32 has already provided you with a solution. You open
the parczon.srw report and see that it is a listing of all Parcel
records sorted by zoning classification. You
simply add filters to the Zoning field on the existing report to narrow
the results to include only commercially zoned parcels and save your modified
report to another name. The
Board decides to grant a request for the development of a shopping center
provided the developer fund the extra effort required by your department to see
the complex project through. You
use the PTWin32 Time Tracking function to create a log of staff
involvement in the project and discover existing reports and summaries that
provide a detailed accounting of the department’s efforts. These
reports coupled with other existing PTWin32 reports for Plan Review and Inspection
records provide a complete picture of your contribution to the project. But you
go one step further by putting together reports that sort the Time Tracking
records by Staff Member or Work Type so you can study your
department’s workload and streamline operations. And so our fictional case study ends with
you in complete control of your destiny thanks to PTWin32. A little time spent
learning how to make queries and reports has made you the rising star in your
organization. They double your budget and your salary;
They get you a new vehicle and a personal assistant; They put you on a four-day
workweek and extend dental coverage to your pets. And you have only yourself and
PTWin32 to thank. Hey…it could happen.
|
||||
 |
|||||
