The Enterprise software solution allows us to have one, fully-integrated system. Before using this product, we had multiple systems to handle underwriting, claims, accounting, and billing. Now, this is the only system we use. The team at ISI integrated two separate software products into Enterprise which significantly decreased administrative work.

The Enterprise software solution offers a full range of modules to conduct every business need for underwriting and issuing policies, handling claims, and reinsurance reporting. Their reporting tool is dynamic and allows for a range of information to be queried and displayed in an easy to read format.

Effective policy management system which handles our reinsurance needs adequately.

Customer Support is great. The ISI team is prompt and efficient. Reinsurance calculation works for at least 90% of our situations. Only complicated reinsurance situations require user manipulation. We can do some internal configuration changes ourselves. Once users have been trained, it is reasonably simple to use.

Enterprise is not intuitive for a new user in terms of adding new locations or items. The user interface is clunky for maneuvering to locations, items, and coverages. The inability to move windows is frustrating for users. Slow response for large program policies is a frustration for users. Certain changes which would seem to be easy drop-down option changes (e.g. in Activity Central) are base code changes which means a lot of work to change it. The release management for large changes is complicated (e.g. merging feature branch to QA, then we must regression test after the merge). OOSE transactions are challenging for our large programs in particular. I receive feedback from users that searching is confusing. The problem is that when people search for client number in a policy number field, the (interim) policy number that was generated when a new policy was set up is also return. This is confusing because the client number is not the same as the system generated new business policy number. Although I understand why it happens, the users don't and they think there is a bug in the search function. It would be good to come up with a solution for this. Naming of rating and rule tables is inconsistent.

Broker Module

the new system implementation has brought about many efficiencies for all departments and we continue to realize more efficiencies as we continue to use the system and expand our development opportunities with ISI.

as with any new system implementation, there have been some ups and downs but overall the downside of development and implementation have not been critical. The benefits of the new operating system far outweigh any of the issues that we incurred during development and implementation.

I like the functionality of the software - if there is something I require, ISI has probably thought of it. If they have not thought about it, they are receptive to new ideas.

The current user interface is not great but that's getting an update this year! Otherwise, everything is falling into place. Base reports would be my next 'room for improvement' area.

Commercial packages - automated Letters automatically generated Less room for errors with more controls in place Activity Central - we are not using it to its potential - but will gain even more efficiency once we use it fully

Many increased efficiencies - fully integrated - more data captured - more user controls to prevent errors

Out of Sequence endorsements not working correctly yet - Reports not working correctly - Processing time for searches on large policies - comparability issues with different search engines