A QueryPlus user wanted to run reports on only ‘brand-new’ Customers, but there isn’t any field in the AMS/AFW databases that indicates this status. So the Daily Querier created a field called:

            Customer Prior Policy Count 

This field returns one of 3 results:

            Blank:              Customer has no policies and never has

            Zero(0):           Customer has no previous policies and is ‘brand-new’

            Positive #:       The number of previous policies this Customer has had

Note that the term ‘prior’ or ‘previous’ Policy refers ONLY to policies written through the AMS interface – it does not include any prior policies from other carriers/agents that were manually entered as prior policies.

With this field, the AMS user can create a query to return all brand-new Customers, not-brand-new Customers, Customers who never bought a policy at all…. The possibilities are many.

Add another existing field:

            Customer Open Policy Count

And there are even more possibilities.

The first 5 fields in the listing below have been added to be able to create a Policy Transaction level report showing premium and commission. Use the last 2 (existing) fields for Premium data.

Policy Total Commission fields have been added to QueryPlus version 3.2. The new fields are:

These fields are useful in policy-level report, especially when combined with the Policy Total Premium and Non-Premium fields.

QueryPlus version 3.2 contains a new set of fields – both Premium and Non-Premium – which are summed at the Policy level. They are useful in creating queries/reports that need policy-level totals.

In AMS360, the new fields are:

The Policy Total Cost of Insurance is the sum of Policy Total Premium and Policy Total Non-Premium.

In AFW, the new fields are:

There is no Un-Billed Non-Premium, since Non-Premium is added in the billing process.

The last 3 fields were added because of some concern about the ‘Don’t Bill’ flag in the AFW interface:

These 3 fields total all Premium without regard to the ‘Don’t Bill’ flag. Use either set of fields as desired to return the correct data for your particular query/report.

We are doing several upgrades a day, and if you haven’t been contacted yet, you will be soon.

The Daily Querier is thrilled to be able to respond to QueryPlus users’ requests for new connectivity, fields and queries effectively in real-time….. I think I mentioned that before, but it bears repeating!

Technical Bulletin #11, available on the Knowledge Base, contains a discussion of how to get information on Auto policy limits – both Personal Lines and Business Auto.

These techniques are also applicable to a wide variety of queries.

The first test of the automatic updater by a ‘real’ QueryPlus user (as opposed to internal QualCorp tests) was conducted today….. and it was a success!

Once you are upgraded to QueryPlus version 3.2, we can offer essentially real-time support for query/report development, because if you need a new ‘join’ or field, we can design it and put it into your database immediately.

And, as everybody either knows already or is finding out, the AMS databases are extremely complex and getting data out of them often requires new joins and/or fields.

Now we can assist you in real-time. This is probably the greatest leap forward for QueryPlus since we first got it to work!

The Daily Querier is grinning from ear to ear!

A QueryPlus user is being upgraded to AMS360 2.5, and was concerned because AMS requires that all traces of other applications, as well as SQL Server 2005 Express & Management Studio Express, be removed from the server before the AMS upgrade can be started.

While we have no direct or specific information from AMS about their requirements, we were able to assist that QueryPlus user in ‘scrubbing’ their server so that the AMS upgrade could be performed.

So if you are getting the AMS360 2.5 upgrade (or any other upgrade), please contact QueryPlus Technical Support as early in the process as possible. We will assist you in meeting AMS requirements prior to your upgrade date, then, once the AMS upgrade is completed, we will get QueryPlus back up and running.

And, of course, there will be no additional charge for this service.

Testing has been completed, the bugs have been worked out, and version 3.2 is ready.

We’ll be contacting all users shortly, but as a special offer to Daily Querier readers, call or e-mail QueryPlus Tech Support and we’ll put you right at the top of the list.