Voting List Details
Voting List Details – Core 2005
IUG Ref / Cost Category / Subject / Description / Notes / Raised By / Date336 / C / Amend Flexible Business Extensions so that such items may be attached to claims as well as policies / Claims may be associated with a particular 'business item' added using Flexible business extensions. This change would allow users to associate one or many of the business items on a policy with a claim on that policy / Axis / 25-Apr-00
338 / E / Allow IRIS to be accessed via a web browser / Allow the IRIS GUI functionality to be accessed via a web browser.
Re-design and re-development all IRIS modules to enable full operation via web.
One main advantage of this is that IRIS would not need to be installed on a PC in order for a user to use IRIS (IRIS would be installed on a web server). This would simplify software installation procedures, since IRIS would only require server installation, individual PCs would only require access to the web. / *** Rebus Recommends *** / Everest; Axis; RebusIS; Rosemont Re / 25-Apr-00
359 / B / Allow definition of calculated fields and validation against main policy data in Flexible Business Extensions / Allow users to define rules in Flexible Business Extensions that validate the data entered in the 'Business Items' against the main policy data (e.g. TSI; EPI of the business items should not exceed the EPI or TSI on the policy). / Axis / 22-Aug-00
372 / D / Expand the selection of fields available in Decision Base / Expand the number of fields available in Decision Base so that they include all of those currently available in CBA, Prog stats and Claims analysis (e.g. CAG1 and CAG2)
In addition the new additional policy code fields that are available in the GUI to be included. / XL London; Great Lakes / 25-Sep-00
217 / D / DecisionBase Underwriting Years / Option to Combine U/W years on Decision Base, as well as showing other years separately, e.g. '85 and prior as one amount with subsequent years shown separately. This will consolidate the view of earlier years & reduce the number of U/W years on the report / Great Lakes / 30-Sep-99
310 / E / GUI Based policy/claim review diary / Provide a link between policy/claim review diary dates on the system and a calendar/messaging system (potentially a task list displayed within IRIS when it is started up) so that users are kept informed of important business dates automatically.
This should take the form of a batch job that triggered user defined events using user defined triggers. For example sending an e-mail with a short cut to a policy when some kind of diary date is hit on that policy.
Allow system administrators to define their own triggers and actions (e.g. when a new quote is entered on the system a reminder should be created for an u/w for them to review it). Triggers should be attached to all common actions (e.g. new policy, update policy, create closing etc).
It is to these triggers that the system administrators should be able to attach actions (e.g. send e-mail, add reminder to u/w's diary etc).
Functionality should also allow the actions to be related to the data on which the trigger was fired (e.g. if a policy was entered with U/W code of ABC then the e-mail should be sent to U/W ABC) / *** Rebus Recommends *** / RebusIS: Rosemont Re / 30-Sep-99
334 / C / Add the ability to define a hierarchy within Flexible Business Extns. / Allow users to define 'Flexible Business Extensions' that consists of multiple levels of data. For example in marine business the top level could be defined as a 'Fleet' and a lower level as the individual 'Vessels' / *** Rebus Recommends *** / Axis / 25-Apr-00
381 / C / Extend enquiry filter to allow lists and ranges as per wizard steps / Currently the enquiry filter function only allows the selection of a single item or a single range. Extend this functionality to allow the same functionality as the Custom Filter step in the wizard steps. / Previously voted in on the 2004 list / Axis / 10-Jul-01
384 / B / Allow removal of columns from enquiries from within the enquiry via right click & delete / Currently it is only possible to remove (hide) a column from an enquiry via the menu. This change would add a context (right-click) menu option to allow the user to remove (hide) columns in an enquiry. / XL London; Axis / 06-Jun-00
385 / E / Transaction Enquiry - Drop Down Net of Deductions etc. option / A drop down box should be made available in the transaction enquiry that would allow the figures to be displayed as Gross, Net of Deductions and Deductions. / Previously voted in on the 2003 list / XL London; Axis / 06-Jun-00
387 / C / Distinguishing between multiple level summary totals and hiding details / Currently the user can only define one colour that is applied to all summary sub-totals. What is required is some method by which the user can specify the application of different colours to different levels of sub-total.
In addition when an enquiry is showing sub-totals this enhancement would allow all the detail levels of information to be hidden so that only the sub-total summary along with relevant info is shown. / *** Rebus Recommends *** / Axis / 07-Jun-00
390 / C / Company Involvement Enquiry/Search on narrative, assured, vessel and reassured/Policy List - Assured & Reassured / An enquiry that lists all involvement for a given company is required/Add a new enquiry that allows searches on narrative, assured names, vessel names, reassured names and lists the policies for which a match is found/Produce a combined Reassured/Assured enquiry removing the need to have two separate enquiries. / *** Rebus Recommends ***
Originally voted in on IUG 2002 but put up for voting on again because of budget constraints in the 2002 budget / RebusIS; Axis; Rosemont Re / 07-Jun-00
407 / D / Allow written, earned and unearned premium figures to be recorded and monitored within IRIS / Enhance IRIS to allow it to monitor written, earned and unearned premium figures (e.g. on a monthly basis). This will enable a history of written premium information to be recorded and reported on. This would be a requirement for one year accounting and GAAP reporting. Include triangulated views of the data. Earned/Unearned premium should include cut off rules. / *** Rebus Recommends *** / Rosemont Re; RebusIS / 08-Jun-00
415 / C / Business Items list changes and Freezing of Columns / Modify the business items list so that it remembers the column widths specified by a user (for each business item type) so that when a user revisits the business item screen the column widths are as defined when they last viewed the screen.
These column widths should be stored at the business item level.
Allow the freezing of columns within FBE and for the frozen state to be remembered / Axis; Great Lakes / 17-Jul-00
416 / B / Save column freeze in enquiries / Currently when saving an enquiry which columns were 'frozen' is not saved as part of the enquiry. This change would allow this information to be saved when the enquiry is saved. / Axis / 19-Jul-00
417 / C / When editing highlighting/filters all existing filters and highlights should be shown / When viewing/editing the filter on an enquiries screen, all currently applied filters should be listed so that a user can see at a glance what selections have been applied to the screen.
When viewing the highlighting applied to an enquiry view, all the applied highlighting rules should be listed. In addition it should be possible to apply multiple highlight rules, with the option of applying different highlighting to the different rules. / Faraday; Axis / 31-Aug-01
419 / D / Create a Progression Triangle Enquiry / Create a new enquiry that allows a progression triangle to be viewed for a policy or a group of policies / *** Rebus Recommends *** / Axis; Rosemont Re / 25-Aug-00
426 / C / Business items - Add Policy Ref Type Field / Expand the list of available generic fields in Business items to include a Policy Reference type field. / HIH; Axis / 12-Feb-01
438 / E / Allow users to jump between the wizard steps in enquiries / Currently the users can only go backwards and forwards between the wizard steps. In some cases it may be preferable to jump to the wizard step required. In addition the users should be able to choose to hide any or all wizard steps so that when the enquiry is saved and rerun it will bypass all the wizard steps that they no longer need. There will still be the option of reactivating the wizard steps if required.
The users should be able to choose to see a summary of the selections applied in an enquiry prior to running it so that they can determine whether they want to go through the wizard to change those selections.
All of this will be controlled by a Wizard manager which will be part of the enquiry. / XL London; Faraday; Axis / 05-Mar-01
446 / B / Business Extensions - Copy Business items from one policy to another / Include a facility in IRIS that allows Business Items to be copied from one policy to another from within the business items function. / Liberty Syndicates; Axis / 02-May-01
453 / C / Policy Input-Allow Save of Incomplete Policies / Enhance the system so that it is possible to save incomplete policies allowing the user to return to them later to complete their data input.
Enquiries will need to be modified so that incomplete policies can be listed and then completed.
The entry of transactions (closings, claims etc) should not be allowed against incomplete policies. / RebusIS; Rosemont Re / 01-Jun-01
463 / C / Closing Reversal / Currently to reverse closings, the user right clicks and selects reverse. In addition a reverse closing button should be added.
Transactions that have been reversed already should be flagged as such and greyed in the enquiry. In addition if a transaction has been reversed, the system should prevent a user from reversing it again (N.B. this will need a modification to the system so that if a user deletes a reversal the original transaction is unflagged as having been reversed).The system generated closing should be clearly identifiable.
Add security so that users can be prevented from reversing a reversal closing or undeleting a deleted closing.
Modify how reversal a/c types need to be defined in housekeeping so that the selection list used in GUI closings reversal is simplified. Define a default data area which holds the reversal transaction reference.
Reversal and re-entry of transactions
There is currently a Closings Reversal in IRIS. This creates a reversal of the original entry. The IRIS system maintains a link between the original item and the reversal.
However, in many cases the user needs to manually re-enter a transaction. And after doing this, there is no system link between the original item (A), the reversal (B) and the new re-entry (C)
It would be useful to amend the Closings Reversal, so the user could optionally also create a new closing (the re-entry - C). This item would by default contain the same details as the original transaction (A). It would also be linked to the original item (A) and it's reversal (B). Also the user would be prompted to amend the relevant details of this new entry before it is actually created on the IRIS Closings Logs / Faraday; AXIS; Abacus; Rosemont Re / 18-Jul-01
484 / D / Display Ancillary Policy Information in enquiries / It should be possible to display (read only) the 'ancillary' policy screens (i.e. deductions, accounting terms, locations, perils, business items etc) from within the policy list function without having to call policy input first. This should be accessible via the menu displayed when right clicking on a policy. / *** Rebus Recommends *** / Faraday; Axis; Momentum; Great Lakes / 31-Aug-01
489 / C / Policy History Information / Currently accessing the policy history enquiry from within a policy in policy input requires the user to navigate through a menu. Include direct access to the history enquiry via an additional button or a extra option in the status bar and also via a function key. / *** Rebus Recommends ***
An alternative method for making the history more accessible that is possible within the system now with no program changes required is to have the history enquiry embedded on the policy details form as an additional tab. (IRIS 7.13 or later) / Axis / 05-Sep-01
494 / C / Allow cross-referencing of Assured in the GUI/Multiple Assured/Assured Pseudonym / As well as allowing the user to enter Assured cross-references they should also be able to run an enquiry to pick up policies for an assured via the cross reference/Ability to record multiple assured names against a single policy. Also ability to record assured pseudonyms & aliases. [Standard Enquiries need to take account of this] / *** Rebus Recommends *** / Axis / 05-Sep-01
496 / E / On line analysis enquiry / Develop a standard IRIS datamart and cubes derived from the IRIS data.
Via integration with a third party OLAP tool allow users to view summarised data in the format that they require (e.g. Triangle view). The enquiry will allow users to access summarised business data directly from within IRIS removing the need to use and log on to other applications. The multidimensional nature of the stored data will allow users to 'drill' down through the layers of the data providing useful management information about the business being recorded in IRIS. / RebusIS / 26-Jun-02
497 / C / IRIS Database Changes / Modify policy file structure to enable codes and amounts to be held separately. This will enable additional codes and amount tables to be added to the policy file more quickly and efficiently in future.
A large number of changes have been requested to the IRIS policy file, examples of which are;
1. Add a best order % to the policy file (the policy file currently holds the best line, the usability of which would be dramatically increased if paired with a best order %).
2. Allow additional premiums; I.R.O special acceptances (i.e. in addition to normal M&D) to be recorded on the policy file
3. Make base currency equivalents available for all the new additional amount fields that are currently available in the GUI
4. Allow AP, RP and reinstatement premiums to be recorded in a structured way on a policy.
5. Add additional sub-limits/excesses including related limit qualifiers
6. Implement a drop-down box beside the BASE EPI field to enable entry of a qualifier to indicate on what basis the adjustment will be made e.g. EPI; FCV (Full Contract Value); AGG (Aggregate) etc. Drop-down choices to be configurable by user. Rename field caption "Base" rather than "Base EPI". As requests for such database changes are frequently received, it is suggested that the structure of the policy file be modified so that going forward adding new amounts and codes fields to the file will be much simpler and quicker to apply.
7. Increase the length of the Broker reference throughout the system. / *** Rebus Recommends *** / Gerling; Axis; Everest; Rosemont Re / 30-Sep-99
498 / D / Block Policy Renewals / A function that would allow several policies to be selected to be renewed to skeletons at once. The aim of this additional functionality would be to make renewing policies a faster process. / Previously voted in on 2003 list / XL London / 01-Jul-02
505 / D / Multi-company/syndicate security. Allow security in policy input to be at company level and inwards/outwards level. Allow Product codes to be restrict / Introduce additional security into IRIS at the following levels for users/roles:
1. Ability to restrict access to data via code information. E.g. allows users to only have access to specific company codes (either NONE, READ or UPDATE). If a user doesn't have any access to a specific company's business then the enquiries should automatically exclude data relating to that company from enquiries run by that user. This could equally well be syndicate code or someother coded piece of information on a risk.
2. Ability to restrict the use of product codes (e.g. so a user only sees the product codes that they are allowed to use)
3. Ability to restrict access at the inwards/outwards level (e.g. grant a user update access to inwards policies but only view access of outwards policies)
4. Restrict users so they can get into Skeleton Input, but not into Policy Input (e.g. add security down to the 'Entry Type' and 'Action' level)
5. Restrict Closings authorisation by user. / *** Rebus Recommends *** / Axis; Liberty Syndicates; Great Lakes; XL London; LDG; Rosemont Re / 09-Mar-01
509 / D / Document Production. IRIS GUI Link to Word / Allow users to define a template in Word and then export data from IRIS into Word document template for the production of standard letters/documents. This functionality would be similar to a mail merge, whereby a template with book marks is created by the user. The bookmarks would be associated with IRIS data base field, which the user wishes to populate. The definition could then be saved for future use. From within IRIS it would then be possible to generate a print, or create a word document using pre-defined templates.
Examples of use would to be able for the user to run an enquiry listing all policies for which there are overdue payments and from this selection, generate a letter to all selected brokers chasing payment.: / Previously voted in on the 2003 list / RebusIS / 28-Jun-02
524 / C / Generic risk skeleton / Ability to create a generic skeleton policy and to decide on Product Type at point of making live. / Axis / 19-Jul-02