A wide range of ProductWriter/RTE consultants can assist you with new initiatives and ongoing maintenance. They may be able to assist you in the following areas:
ProductWriter consultants who can help with the areas above include:
N.B. Polaris does not guarantee the work of consultants. It is advised that references are taken before decisions are made about use of any developer for specific product building requirements
For further information regarding consultancy please do not hesitate to contact us.
Name
Number
Company Links
Broker Direct (BD) have successfully worked with many insurers delivering products to the broker market since 1997, including Polaris products since 2005
Through our Proficient Division, we offer TPA services including:
OUR TEAM – a team of 12 with a combined 75+ years’ experience working with Polaris
Briefly the team comprises:
Our Developers have an insurance background, combined with extensive Polaris programming experience, primarily Motor and Home using standard UK data dictionaries but also in commercial product builds experience using bespoke software including Retailer, Tradesman, Liability, Commercial Combined and Excess of Loss
Our expertise includes:
Name
Number
Company Links
ProductWriter experts with over 12 years of scheme writing experience. Experience of writing products for major Insurers in various lines of business. Experience in testing with various software houses and integrators.
Worked with Productwriter and RTE for both Personal and Commercial lines whilst at CGI, two market leading Insurers and Software House; OpenGi. Covered all aspects of Polaris products.
Expert in imarket including rating systems, product development, testing and driving effective Customer journey’s. Expert in other imarket services such as Live chat and Accounts Reconciliation centre. Past member of the imarket steering group. Managed Software house integrations for both traditional products and specific broker schemes and arrangements.
Knowledge of various lines of business including Private Motor, Home, Pet, SME and large Commercial schemes using the standard Commercial dictionary and also commercial products using Schema based Dictionaries.
Name
Spencer Wade
Have been involved with ProductWriter and the RTE since 2007, initially as a FTE of Nnable Ltd (now part of Aon) and latterly as a freelance subcontractor. Have worked across multiple integrations.
Recent clients include Tesco Underwriting, Inspire Underwriting, Modus Underwriting and Pen Underwriting.
Name
Number
Company Links
DTR-Ltd was formed in 2007 by its founding directors Phil Sankey Dip CII and Lee Dimmock Dip CII.
We have extensive experience of creating and maintaining ProductWriter Polaris products across the market.
Our products are successfully integrated on a number of Insurance Software Houses, Insurer Hosted systems and Broker systems.
We offer extensive Development and Testing resource and can provide a bespoke package tailored to meet your individual requirements.
DTR-Ltd specialises in all aspects of ProductWriter Polaris Product Creation, maintenance and testing across all product lines and Data Dictionaries. So whether you are thinking about using Polaris for the first time, require a new product build or simply find yourself without Polaris resource then DTR-Ltd are able to help.
Our mission is to offer all of our customers an exceptional level of service, flexibility and peace of mind. Please contact us to discuss your requirements further.
Client list includes: Applied Systems, Chaucer, KGM, Markerstudy, Premier Underwriting, Prestige Underwriting Services Ltd, XS Direct, Zenith and many more. Full details of other clients and / or references are available on request.
Name
Number
20yrs industry experience with exposure to both Direct and Intermediated insurers.
ProductWriter, who has built and deployed multiple products within the following disciplines, Motor/Household and Packaged SME products. Familiar with EDI messaging, IS2000/ insurer mainframes, all major SWH data configuration and test engines, Insurer Hosted and Real Time Pricing. Building them, testing them, being the business analyst and more recently the project management activities – including the delivery of a new policy administration system.
Have used standard, extended and XML data dictionaries. Am familiar with the DB2 configuration. Am familiar with mapping APIs to the dictionaries and vice versa.
Asides ProductWriter have broad understanding of the General Insurance arena from Pricing through Underwriting and have worked for the largest insurers as well as MGAs and start-ups. Including a stint in the Lloyds market as a manager of a developer team.
Have built more Motor products than anything else – but aim not to specialise in only one area.
My main selling point is making it easy for not necessarily Tech people to engage and then pitching the content at the appropriate level of understanding.
Name
Number
Company Links
Founded in 2008 eZee provide consultancy and contracting services to the General Insurance Industry on all aspects of electronic and digital trading ranging from system selection, project management, business analysis, product building, testing, and training.
We provide consultancy, assistance and support to…
Further details can be found on our website.
We can provide support for forms and EDI development; we can also assist clients with Polaris RTE implementations and environment testing.
The e-Zee board members have over 150 years industry experience between them, and our team members have all worked for the major insurers, brokers or Software Houses. The team are located throughout the UK and we have the flexibility to provide assistance to meet our client’s requirements working on site or remotely.
Our ProductWriter team all of whom have over 10 years’ experience using ProductWriter have worked for numerous insurers including Aviva, RSA, Zurich, Commercial Union, Allianz.
Our staff have expertise across all Commercial and Personal Lines products utilising both the Polaris standard dictionaries as well as bespoke XML based dictionaries and schemes.
As well as working with and for numerous insurers and MGAs, our team have developed and supported schemes on iMarket and all the major Software Houses and have extensive experience of their integration.
We have provided support to Carriers who use IHP solutions, and we can build products using the private as well as public dictionaries.
We have provided ProductWriter training to insurers at various levels, from basic introduction to the toolset, testing, and right through to full bespoke toolset training.
If required, we are happy to provide CV’s and client testimonials for all team members.
Visit our website for more details
Name
Number
Company Links
With over 20 years’ experience of working with Polaris technologies F1 has built an enviable reputation for creating and maintaining quality products using the Polaris ProductWriter toolset. During this time we have worked with over 25 insurance companies, building Private Motor, Commercial Vehicle and Household products, ranging from the most basic schemes to the very latest complex peril-rated schemes. We have a vast experience of creating products for all the main broker systems including AA, Acturis, Applied, Budget, CDL, Guidewire, Saga, SSP & TGSL and we have a thorough understanding of all the data enrichment techniques used by each system.
In addition to using the ProductWriter toolset, F1 has a high degree of expertise in integrating the Polaris Run Time Environment (RTE, XRTE & WSRTE) into bespoke software solutions, such as our highly acclaimed product testing software, PremierTest.
All our staff are highly skilled software developers who have worked within the insurance industry for the last 30 years providing an unparalleled level of experience within this sector.
Our main area of expertise with ProductWriter is with the Personal Lines data dictionaries with which we are very familiar, although we have also worked with the Commercial and iMarket dictionaries to a lesser extent. We have a thorough knowledge and understanding of all the main broker systems and have undertaken the development of over 80 individual schemes, split roughly equally between the motor and household dictionaries, on behalf of a great many of the Polaris members.
Name
Jonathan Pennell
Company Links
With over 5 years of experience in the insurance industry, I have developed products using a wide variety of software (including ProductWriter, Excel, various analytics driven programs as well as Python) for a wide variety of platforms: CDL, TGSL, OpenGI, SSP, Acturis, Earnix etc.
As a developer first and foremost, I focus on turning pricing/product frameworks into Polaris Product builds with extensive testing. Whether they’re entirely new or already existing products, I can help get them live on target and with peace of mind.
Name
Number
Company Links
IQUO have been working with POLARIS UK and with ProductWriter for over 20 years. We have considerable experience in writing schemes for a range of insurers. In addition, we develop and host insurance applications that integrate ProductWriter schemes supplied to us by insurers. Recently we have integrated our applications into iMarket to provide both a broker front end and also an insurer backend system.
We have a team of 3 experienced ProductWriter developers, each with over 15 years’ experience. In this time, we have advised our customers on their use of ProductWriter and have provided bespoke training on the product to aid definition and testing of the insurance product. As we use ProductWriter schemes in our applications we are well versed in the deployment of the POLARIS RTE and the processes that have to be followed as part of the regular upgrade routines.
Name
Number
Company Links
I am a ProductWriter developer and ISEB accredited test analyst, with over 10 years of experience within the insurance industry. My background in product development and testing, together with my keen understanding of the product launch process, allows me to integrate quickly into the client’s development teams and deliver results. I offer development and testing expertise on a contract basis.
Polaris ProductWriter Development and Testing for all Class of Business’, on all Dictionaries types, across both Personal and Commercial lines.
Name
Number
Company Links
Since 1998 Line Contracts has been serving the insurance industry with IT solutions. Providing both IT and insurance business Knowledge and experience Line Contracts has been able to offer a wholistic and rounded service from specification testing through to software house integration, supporting our clients either long term or through periods of high demand. Having strong software house relationships and a comprehensive working understanding of the Polaris ProductWriter tool set Line Contracts has a history of delivering new products to market on budget and within proscribed time scales, as well as supporting our clients with monthly maintenance contracts.
Specialising in personal lines products, we work predominantly with Private Car, Household and Small Commercial Vehicle lines. Creating bespoke products for our Blue-Chip insurer partners and large brokers, delivering software house Implementations including IHP integrations.
Name
Number
Company Links
Name
Number
Company Links
We have worked in the Polaris arena since its inception more than 20+ years ago. We have worked with most Insurers over this period and have written more than 200+ Schemes in that time. Design, Development & Batch Testing are all functions we are totally familiar with.
We have also been involved with the implementation of the Polaris RTE into Broker\Insurer Systems.
Name
Number
Company Links
Sablistech has nearly a decade of experience in building and integrating products for insurers and brokers. It has worked with all major Software Houses and imarket as well as third party suppliers. Between them the directors of Sablistech have worked for more than 35 years in Electronic Trading for the Insurance Industry working on both traditional waterfall and agile projects.
Please read these terms before using the Polaris.co.uk website (“the Site”).
By using the Site you signify your acceptance of these terms. If you do not agree to these terms please do not use the Site.
The purpose of the Site is for insurers, brokers and members of the software industry to be provided with information about Polaris U.K. Ltd (“Polaris”), our software products and services and information about insurance industry standards. We do not sell any of our software products via the Site, but if you wish to licence such products you can contact Polaris (0207 265 5765) or use our contact us page to arrange a licence. As a licensee you will be able to download the applicable products via the Site. Please note that the Site is not intended for use by the general public.
We have taken every care in the preparation of the Site. However, as certain technical matters may be beyond our control, we cannot guarantee that you will have uninterrupted access to the Site at all times.
The information that is provided on the Site has been included in good faith for general informational purposes only. It should not be relied upon for any specific purpose and no representation or warranty is given as to its accuracy or completeness and you hereby acknowledge that any reliance upon the information on the Site shall be at your own risk.
We reserve the right to amend any of the content of the Site from time to time without notice to you.
We reserve the right to amend these Terms from time to time without notice to you. Any such amendment shall be effective once the revised Terms have been posted on the Site. As these Terms may be updated from time to time, we suggest that you check them whenever you visit the Site. If you do not agree with the amended Terms you must discontinue using the Site.
Links to other websites are not endorsed nor do Polaris take responsibility for the content of other websites, or are responsible for the availability of them and will not be liable in any way for any loss or damage which you may suffer by using those websites. If you decide to access linked websites you do so at your own risk.
imarket, ProductWriter and all brand, product and service names used on the Site are trademarks, trade names or service marks of Polaris unless otherwise stated. You may not distribute products or offer services under or by reference to or otherwise use or reproduce any such trade marks, trade names or service marks without the prior written permission of Polaris or the owner of such trade marks, trade names or service marks.
You may not publish, distribute, extract, re-utilise or reproduce any part of the Site in any material form (including photocopying or storing it on any medium by electronic means) other than in accordance with the limited use licence set out in the Copyright Notice section below or as permitted by the Copyright Designs and Patents Act 1988 or the Copyright and Rights in Databases Regulations 1997 as applicable or any equivalent legislation as may apply in the UK.
7.1. User generated content
7.1.1. Keep it relevant
For everyone’s benefit, please stay on topic. The Community is specifically provided to allow users and customers of ProductWriter to help each other in using our software. Please refrain from discussing personal matters, abusing any company or product, or, in general, from posting in a manner unrelated to ProductWriter.
7.1.2. Keep it courteous
Please refrain from posting anything unlawful, libelous, defamatory, obscene, pornographic, indecent, lewd, harassing, politically sensitive, threatening, harmful, invasive of privacy or publicity rights, abusive, inflammatory, or otherwise objectionable or injurious to third parties[SW1] .
7.1.3. Keep it legal
It is unacceptable to post any material (i) that would infringe on any patent, trademark, trade secret, copyright, or other proprietary rights of any party, (ii) that contains software viruses or any other computer code or files that are designed to disrupt, damage, or limit the functioning of any software or hardware, (iii) that is deemed to be illegal by any local, or international law, rule, or regulation, or (iv) that suggests or encourages illegal activity.
7.1.4. Keep confidential information confidential
You may not use the Community Hub to disseminate or discuss any confidential information or personal data (as defined by the General Data Protection Regulation) about you, your company, Polaris, or any other person or entity. You are solely responsible to ensure that anything you post does not contain information that may be deemed confidential or to be personal data by a third party. This includes any proprietary information, trade secrets, the terms or existence of Polaris related agreements, nondisclosure agreements, sales or service agreements, any data identifying or relating to an individual, or any other information that may be deemed confidential.
7.1.5. Polaris retains the right to remove content and limit user’s access
Polaris retains the right, at its sole discretion, to limit users’ access to the Community Hub and to remove material that, in Polaris’s sole judgment, does not comply with the current Community Usage Guidelines, or that is otherwise inappropriate, harmful, objectionable, or inaccurate. Moderators may take any action they deem necessary in their own judgment to support the Community Usage Guidelines, and, in general, prohibit content that can detract from the experience of other users or the purpose of the support community. Such actions may include editing or deleting material and suspending individual users. Violation of the Community Usage Guidelines or other terms could result in the suspension or termination of your access to these services. If your account is suspended, you will not be able to sign in.
7.1.6. Disclaimer of Warranties and Limitation of Liability
Members like you are providing most of the material in the ProductWriter Community Hub. Such third-party content is the sole responsibility of the person originating the material. Polaris does not control and is not responsible for this third-party material.
Whilst we have taken care in the preparation of the Site and its contents (including virus checking files which are accessible from the Site), the Site and its contents are provided on an “as is” basis and to the fullest extent permitted by law all warranties (whether express or implied) in respect of the Site and its contents and your use of the same are excluded. Except in the case of death or personal injury caused by our negligence we exclude all liability to you (whether in contract or tort (including negligence or breach of statutory duty ) or otherwise) for any losses sustained arising out of or in connection with the use of the Site including without limitation, loss of profits, loss of data or loss of goodwill (in all of these cases whether direct or indirect) nor any indirect, economic, consequential or special loss.
Notwithstanding the above, we recommend that you conduct virus checks on any files you download from the Site.
The contents of these pages are © Polaris U.K. Ltd. Reproduction of part or all of the contents of our Site in any form is prohibited other than in accordance with the following permissions:
9.1 Licence to copy for personal use:
You may make copies of the web pages from our Site as necessary incidental acts during your viewing of it, and you may take a print for your personal use of as much of our Site content as is reasonable for the purpose of your Company’s business (“Company” means either the insurance, broker or software company which authorised you to access the Site).
9.2 Licence to recopy for limited purposes:
Only Polaris licensees (users of this Site who have entered into a licence with Polaris for the use of its software) may recopy content from our Site to individual third parties but only for their personal information, and only if:
This licence to recopy does not permit incorporation of the material or any part of it in any other work or publication, whether in hard copy or electronic or any other form.
No part of our Site may be reproduced on or transmitted to or stored in any other website or other form of electronic retrieval system.
The Site is operated by Polaris U.K. Ltd (registered number 2911441) and whose registered office and contact address is at:
New London House, 6 London Street, London, EC3R 7LP.
If you have any comments or questions regarding the Site, please contact us.
These Terms are governed by and will be construed in accordance with the law of England and Wales. Any dispute arising under or in connection with these Terms shall be subject to the exclusive jurisdiction of the English Courts.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
| rc::a | Session | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on its use. |
| rc::c | Session | This cookie is used to distinguish between humans and bots. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| wp-settings-time | 363 days | Cookie set by the WordPress CMS. Used to customize user’s view of site interface. |
| XSRF-TOKEN | 15 hours | This cookie is set by Wix and is used for security purposes. |
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Third Party ServicesWe use the following third-party services to provide our analytical cookies:
We don't collect or store your personal information (e.g. your name or address) so this information can't be used to identify who you are.
Further information regarding the analytical cookies we use can found here.
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| _ga_8EF0NVDGJH | 2 years | This cookie is installed by Google Analytics. |
| _hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjCachedUserAttributes | Session | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present. |
| _hjClosedSurveyInvites | 1 year | Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. |
| _hjDonePolls | 1 year | Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. |
| _hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
| _hjid | 365 days | Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
| _hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
| _hjKB | 1 year | Records the status of the survey pop-up. |
| _hjLocalStorageTest | Under 100ms | This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. |
| _hjMinimizedPolls | 1 year | Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. |
| _hjRecordingEnabled | never | Hotjar sets this cookie when a Recording starts and is read when the recording module is initialized, to see if the user is already in a recording in a particular session. |
| _hjRecordingLastActivity | never | Hotjar sets this cookie when a user recording starts and when data is sent through the WebSocket. |
| _hjSession{site_id} | 30 minutes | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. |
| _hjSessionRejected | Session | If present, this cookie will be set to ‘1’ for the duration of a user’s session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues. |
| _hjSessionResumed | Session | A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. |
| _hjSessionTooLarge | Session | Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. |
| _hjSessionUser{site_id} | 365 days | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
| _hjUserAttributesHash | Session | User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. |
| _hjViewportId | Session | This stores information about the user viewport such as size and dimensions. |
| hjShownFeedbackMessage | 365 days | Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. |
| pardot | Session | The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking. |
| vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
| Cookie | Duration | Description |
|---|---|---|
| _hjIncludedInSessionSample_2783668 | 2 minutes | Description is currently not available. |
| _hjSession_2783668 | 30 minutes | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. |
| _hjSessionUser_2783668 | 1 year | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| hubaccesstoken | Session | Records a logged in user’s access token via the Hub system. |
| lpv883703 | 30 minutes | This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view. |
| podaccesstoken | Session | Records a logged in user’s access status to the POD system. |
| polaris_session | 15 hours | Cookie set upon initiation of the user’s current session on the Polaris site. |
| visitor_id883703 | 10 years | The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code |
| visitor_id883703-hash | 10 years | The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information. |
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
