IWS Release Notes - July 2013

From BriteWiki
Jump to: navigation, search

We strive to keep our products above the industry standard so that your systems remain current and flexible. For that reason, we make continuous improvements to BriteCore's code base. We've been experimenting with a continuous release process, and we'll be shifting to this to better reflect our daily improvements. Rather than waiting for the all-clear of many items to go out in one weekly release, you'll receive continuous updates for code changes going out in the daily release. Items that require full release notes for this month can be found in this section of the BriteWiki.

July 31, 2013

To Be Released: New County Specification Tool

IWS has reworked BriteCore's Business Locations to enable carriers to customize their own county specifications using the County Specification tool located in Settings > System Wide > Business Locations. This release largely affects clients who use BriteCore's Category Type > Location Code (in Lines) to rate policies by county. However, all clients will be able to use this tool to capture county specifications without that specification necessarily affecting rating.

Note: Please contact IWS before making any changes to your Lines.

Purpose

The purpose of the County Specifications tool is to allow carriers to apply more than one rate to a specific county by dividing the county into separate ratable subdivisions. This means companies who write business on the coast and rate by county can sub-divide their counties into areas such as "beach" or "non-beach" in order to apply different rates to the different location types within the county. This gives carriers more flexibility and control over county/area rates.

Summary of Changes

Below is a list of major changes associated with this request.

  • Removed Cities area from Settings - The "Cities" area has been removed from Settings > Business Locations because it was redundant and unnecessary. Cities are now pulled from the BriteCore geography table which is populated according to data files we receive from zip-code.com.
  • Renamed Townships/Municipalities - The "Townships/Municipalities" box located in Settings > Business Locations has been renamed "County Specifications". Carriers can now use this area to customize their own County Specifications.
  • Added Functionality for County Specifications- Counties and County Specifications carry over to the Category Type > Location Code (in Lines) so carriers can use them to custom define rates for counties and/or county specifications.
  • Renamed the Property > Specify Box - The "Specify" drop-down box located in Policies > Revisions > Property has been renamed County Specification. All custom created County Specification(s) associated with the selected county are available for selection from this drop-down box. If no specifications have been made for the selected county, this box will be hidden.

Documentation

View the documentation links below for more information on how to set up and use County Specifications in BriteCore.

Additional Resources

Below are links to the BriteIdeas > County Specifications change request and software requirement specifications.



July 29, 2013

Mortgagee Type > Land Contract Holder

We've added a new option labeled "Land Contract Holder" to the mortgagee Type drop-down box located in Policies > Property > Mortgagee > Type.

When this option is selected from the Property tab in BriteCore or the Risks tab in BriteQuote, the "Land Contract Holder" type is displayed on the mortgagee section of the declaration. Additionally, for those who are using InsVista, the code 'LCH' is sent when a mortgagee is identified as a "Land Contract Holder".

Land Contract Holder.png



July 25, 2013

Update on Data Warehouse

BriteCore's Data Warehouse has been a valuable reporting asset for many clients already. Since it was first released at the beginning of 2012, we've been able to create quick queries that provide all sorts of managerial reporting to BriteCore clients. Now its time for us to take the Data Warehouse to the next level.

New Data Warehouse Development Effort

Beginning in August, a new Data Warehouse development effort will begin. The purpose of this effort is to:

  • Update the underlying Data Warehouse Infrastructure
  • Add Claims, Payment, and Application Data
  • Add a Drag and Drop Interface, to allow clients to easily construct their own simple Ad-Hoc Reports without any knowledge of SQL

These additions to the Data Warehouse will require a large effort and are expected to take many months to get up and running. Additionally, they will require some of our current engineers who work on custom reports, so it's important to be aware that time spent building custom reports means time not spent building these additional features in the Data Warehouse. The take-away is that if you can make do with the reports that you currently have in BriteCore (or the ones that are soon to be released), you will be much better off in the long run.

July 25, 2013

Update on BriteCore Reports

Over the last 6 months, our reporting team has been making huge strides in developing, testing, and refining our core reporting libraries. The largest advance in this arena is a new library that makes it very simple to get accurate transactions from BriteCore policies. What this means for our BriteCore clients are reports that are more cost effective, faster to develop, and extremely accurate.

New Reports Tool Set

Based on the experience we've gained over the last several months, we've been able to expand our tool set in such a way as to make it possible to create reports that are:

  • Print-ready PDFs
  • Excel Templates (where you design the template, and we fill in the data)
  • Regular Excel Reports
  • Flat Text Files

Beyond work on the core foundation of BriteCore reports, we've also been writing and releasing a large number of custom reports for clients that request them through BriteIdeas. Many of these reports are niche reports that help BriteCore provide exactly the type of data that a particular client needs, based on their setup of Settings and Lines. We have been able to create every report that has been requested thus far. The take-away for you, our client, is that if you have a custom report that you need, the only question is one of cost effectiveness. And as stated above, we're working very fast to make custom reports more and more cost effective.

Finally, there are four large "All Clients" Reports that should start being released in the coming months. They are:

  • Agency Experience Report
  • Premium Payoff Report
  • Reinsurance CAT Modeling Report
  • Reinsurance Limit Profile Report



July 22, 2013

InsVista Interface Changes (Effective 07/25/2013)

We've recently redesigned the portion of BriteCore's interface that allows users to review and rebuild InsVista files prior to sending them to InsVista. When you open the InsVista processing screen located inside BritecCore > Policies > Processing > InsVista, you'll notice a couple minor changes that help make the tool run faster and more efficiently in BriteCore. The changes also help eliminate unwanted proxy errors clients are experiencing when using the InsVista tool to send files.

Interface Changes

1. The "Transaction Type / Due" code now shows the actual reason code ('BG', 'CP', 'CX', 'DM') rather than the BG or HO description ('premium change', 'mortgagee deleted', 'billing statement issued') that way users know exactly what is being sent to InsVista.

2. The "Transaction Type / Due" amount now displays the amount listed in the InsVista file rather than the "Currently Due" amount displayed on the policy's AR screen. This amount more accurately reflects the data being sent to InsVista.

InsVista Tool OLD.png InsVista Tool NEW.png

Additional Resources



July 15, 2013

Payments Received Report (Fix)

It has been brought to our attention that payments received on inactive policies have been missing from the Payments Received report in BriteCore. We've updated this report so that starting tomorrow, clients can view all payments received––including payments received on inactive policies––when they run the Payments Received report in BriteCore.

Click here to view the full Payments Received Report article on the BriteWiki.

PR Report.png

July 8, 2013

Amended Invoices Now Look Like Installment Invoices

As discussed on the BriteWIki forum, we've decided to remove the section labeled Check the Box Next to a Plan and Pay the Corresponding Amount from all BriteCore Amended Billing Statements. These statements now look like the Installment Billing Statements produced by the system.

View the side-by-side comparison screenshot of the old and new Amended Billing Statements listed below. Notice that the section labeled Check the Box Next to a Plan and Pay the Corresponding Amount is present on the old copy of the deliverable but removed from the new copy of the deliverable. From this point forward, the system will start producing the new deliverable.

Old Amended Billing Statement.png Amended Billing Statement.png

July 2, 2013

Travelers Bordereau

There's a new custom report in BriteCore called Travelers Bordereau that assists clients who have an established relationship with Travelers for Equipment Breakdown coverage. When set up properly using BriteCore vendor tags, this report allows clients to retrieve specific line item limit and premium information in an Excel spreadsheet which can then be submitted to Travelers along with payment.

If you'd like to use this report in Britecore, please contact IWS via the OOPS! button to request access and begin the initial set up process.

Vendor Tagging

Once you've contacted IWS for the initial set up of the report, you'll need to tag all applicable items in all Effective Dates inside BriteCore > Vendors > Vendor Tags > Code Source > Equipment Breakdown. Items properly tagged under the Equipment Breakdown code source will be reported on the Travelers Bordereau report.

Click here to view step-by-step instructions on the BriteWiki.

Running the Report

When you've finished tagging reportable items in BriteCore, you can run the Travelers Bordereau from within Reports > Report List > Custom Reports. Once the report has finished building, you'll be able to view specific line item limit and premium information in an Excel spreadsheet. This spreadsheet, or the information within, can be submitted to Travelers along with payment.

Click here to view the full Travelers Bordereau article on the BriteWiki.