Terminology

From Wiki
Jump to: navigation, search

See the NOVUS Walkthrough Guide for general information about the system.


NOVUS and HELIX terminology

Glossary of terms

Business terminology around our relationship with clients

Binder

A global term for a master, however originally the relationship was a binder and off-policy arrangement, where the master contained the only copy of the market structure, preventing any changes to client discount, order % or carrier participation percentages.

Bordereaux

An accounting tool, comprising rows and columns of data that are attributed to the existence of a transactions

Can

The system is able to do this now. May require a feature to be switched on or off or a new module may be required. There may be a cost, there may not be a cost, there may be some training required.

Claims Bordereaux

A one row per section transaction report in the name of the carrier partner for the specific collection criteria such as for a facility. All previously unreported claims transactions will be returned in a booked claims bordereaux and not reported again. All transactions that have outstanding unsettled values will be returned in a claims paid settlement bordereaux

Clauses

Using the CLAUSE program NOVUS holds a list of codes and titles of clauses, conditions, exclusions, endorsements and wordings. These are controlled by policy type and the verbose wording of each is required to be inserted into the Master_conditions.doc document with a bookmark around the element that corresponds with the code in the NOVUS list. Setting the clauses that default for a specific policy type will mean all policies of that type with have these default clauses included, additional clauses can be added for specific polices.

Consultancy

Domain expert time to be used for advice and one to one training, considered advice on how to use the system in the context of addressing a task or action

Could

It would be possible, with development to make the system

Cover note/EMRC

The COV program - evidence of cover, previously referred to as a cover note encompasses a front page inserts the final slip and adds the market breakdown, signature pages and tails. This action contributes to the contract certainty exception reporting.

Declaration

A declaration is a term used to define an attached policy to a binder when the binder is set up as a lineslip in its behavior.

Development

Include business analysis, documenting requirements and specification, and coordinating with developers and testers who then implement the change to the software.

Exposure Reports

A list of all live or all risks on a facility at location level used to assist carriers with the current exposure of the book of business, this is not a bordereaux as it is not an accounting tool.

Facility

Within the system a facility is another kind of master, this time the policies that will attach to the facility MAY be shared across one or more facility and open market. It does not prevent a policy attaching (via the market structure) to only one facility (which must have one or more of the sections the policy wishes to place into, but it affords the underwriter the option to make more complex capacity provisions.

Lineslip

Within the system this is a master contract which will share its market structure with its solely attached declarations. The copy of the market is taken by the declaration and whilst no new participants can join the participation, order%, brokerage and client discount can be altered on each declaration. Only sections on the master can be enjoyed by the declarations, but the declaration does not have to take all sections.

Market

The market set up involved, within the system all parties to the contract financials this being client(s)/ceding brokers/retail brokers/cover holders/insurers, carriers, co-brokers.

Partner

NOVUS regards all entities in the contract to be called partners, these have roles, such as clients, carriers, original assureds/policy holders, TPAs, co-brokers each will be set up to have an IBA (insurance broking account) account code with the permitted roles attributed to them.

Policy

Using POLISSUE much like the COV program but inserts the PROFSCHED document and appends any clauses.

Premium Bordereaux

A one row per section transaction report in the name of the carrier partner for the specific collection criteria such as for a specific facility. All previously unreported transactions will be returned in a booked prem bordereaux and not reported again. All transactions that have outstanding unsettled values will be returned for a prem paid or settlement bordereaux.

Producer

Producer is intended to be an internal member of staff of the client company using the system, someone who produces income for the business which may need to be reported on (e.g. a producing broker or sales person). The producer does not need to be a system user, but would need to be set up in the system with role of 'Producer' in their user profile (this is done by Morning Data). A producer cannot also hold the compliance officer role. The Producer can be assigned on the risk record and used for reporting purposes. The PRODSPLIT program can be used to apportion income on a risk between producers.

Product Demo

A product demonstration, or product demo, is a presentation to an existing customer who has already invested in Morning Data products, to show them existing features, capabilities and value of the software products that they may not already be utilising, or to demonstrate new features, capabilities and value of the software products.
Duration: Approx 2 hours

No of attendees: As agreed with client

Pro forma Schedule

As per the slip – it is a pre firm order document that takes data from the system and merges it with a template form the templates folder controlled by policy type. This document is inserted into the policy document dummy.

Program

Within the system there are a number of programs. these are task based elements of the system, and are referred to by Morning Data by using capitisation such as RISKNEW, TRANPT, WHO, and PARTNER. using these short cuts in the shortcut field on the system desktop will fire that program ready for use. Programs are subject to both permissions by means of a program group and an authorisation level, mapped to a user's setting. For example if the program TRANPT is in group "A" and authorisation level 6 (set in the TITLE) program) all users with level 6 or above and have group A in their groups list (set in the WHO program) will be able to access the program.

Query Grids

The system allows for information, previously potentially supplied by means of a report to be provided via the query screens, which can sort, query, filter and group. The output can be downloaded to Excel. The column sorted allows users to select which columns they want to display including additional columns not in the default view, and the layout can be saved as a view per user to suit the user’s requirements.

Quote

A record in the database that carries a quote number – not a policy/risk/UMR number.

Quote Document

As per slip and pro forma schedule these are pre firm order documents based on templates in the templates folders.

REPGEN reports

A library of reports previously requested by clients to their specifications. Morning Data does not warrant these, but make the library available for use in the context of their output, clients are able to buy these from the library having established they meet their needs.

Requirements gathering

A ‘requirements gathering’ session is a consultancy session either with a new client to determine the requirements for the initial implementation, or with an existing client to determine the requirements for bespoke development requests. These sessions may be single standalone sessions for more simple projects, or form part of a larger requirements gathering phase within a more complex project.
Duration: As agreed with client
No of attendees: As agreed with client

Risk

NOVUS regards these terms as interchangeable as far as a record in the system. RISK/POLICY/CONTRACT/MASTER

Risk Bordereaux

In the event additional breakdown is required the same criteria and basis of the records being returned – i.e. due to a transactions within the collection criteria, a risk bordereaux will return the data at a one row per location per section level.

Risk Details

The system is generic to class except for collecting risk level data (RLD). A templated structure is available for a number of classes where data has been identified to relate to locations, depots, insured address, harbour, branch etc. Several of these have been created, clients can discuss further classes as a development project if not already covered, or contribute to existing screens if additional data is required.

Sanctions Checking

All partners are able to be sanction checked when they are set up, whether new capacity providers, clients , TPAs or policy holders. The entire list will be regularly checked, default once a month with failures against the default OFAC/HMT datasets returned to the compliance officer – the party set up in the WHO program as role C.

Sales Demo

A sales demonstration, or sales demo, is a presentation to a prospective customer to show them the features, capabilities, and value of the software products available from Morning Data.
Duration: Approx 2 hours
Max No of attendees: As agreed with prospective client

Section

Each risk record (quote/policy/treaty/master/binder) will require one or more sections. A section is a self-contained pot of monetary activity within a transaction. A new section is required if any of the following situations arise: different London market risk codes – only one risk code per section, different market configuration – including client discount, carrier deductions (brokerage) signed lines, different carriers (Brexit vs London syndicates) order%, note taxes & fees are applied per section.

A multi-section risk is an insurance contract which comprises a number of separately identifiable risks each of which may be reported separately and each of which may be underwritten by different carriers in a subscription market. Each section is a self-contained part of a larger composition. It refers to a grouping of information of a homogenous nature forming part of the insurance contract. Sections may be created to identify different insurable interests (coverage section) or to identify different layers by limit of liability (layer section). A coverage section is a partition of the insurance contract which represents a specific insurable interest, territory and/or peril, for example:
a. Section 1=hull section 2=cargo
b. Section 1=properties situated in the UK Section 2=in the USA
c. Section 1=property damage section 2=liabilities
A layer section is a partition of a commercial insurance programme into various layers by limit of liability, for example:
a. Section 1=primary $10M, section 2=$10M excess of $10M

Slip

Pre firm order document produced from an existing pre firm order risk or quote record.

System Configuration

Changes already coded in the system to cater for this requirement but will require the developers to initiate or set it up for the client company

System reports

Reports run from programs in the system that the system is not considered fit for purpose without AGED, ACCLIST, TRANLIST, TRIBAL. They are warranted to be correct in terms of the data supplied to them, changes are considered to be possible when legislation or general practices change.

Template

Document templates housed in the templates folder used in slips, pro forma schedules and quotes, the selection of which is available is controlled by policy type

Training

A training session is a ‘classroom’ style session for new users of the software products available from Morning Data, or users who may be new to a particular function of the software, to give information and skills to enable the user to effectively use NOVUS in their defined role within their organisation in line with their organisation’s internal procedures, delivered to a pre-agreed agenda. Provided users have already obtained their license and log-in details, then this may be able to be offered as a ‘hands on’ experience.
Duration: Half day 3 hours Full Day 6 hours
Max No of Attendees: 6

Transaction

A financial entry in the system, by means of TRANPT, TRANPTN or the treaty program, each can be for multiple section and can be (via TRANPT) over multiple instalments. Transactions will be set up for a risk/policy or if an FDO/ADJ may be set up against the master contract directly.

WHO

The program used to set up all users, and producing broker when internal staff are required to act as account managers for a risk but not an active user of the system. Active users all require their own licence no licence sharing is permitted.

Wholesale Binder

sometimes referred to as 3rd party binder, a master record with no attaching policies held in the system, this is however regarded as a structure that may not be appropriate going forward where the policies bound by the 3rd party must be absorbed/imported into the system by the wholesale broker and not just passed through.

Workshop

A workshop session is an interactive session in which a group of existing users of the software products available from Morning Data come together not only to enhance their skills and competencies in a particular area, but also to exchange ideas, brainstorm and contribute solutions to meet the pre-agreed objectives.
Duration: Half day 3 hours Full Day 6 hours
Max No of Attendees: 6

Version History

v4.2.0 – Updated to latest version