Blueprint Two Q&A
Blueprint Two is a major technology initiative aimed at rebuilding and moving the London Market’s core platform systems from mainframe environments to the cloud to facilitate full digital placement of risks and electronic messaging.
DOCOsoft’s Involvement in Blueprint Two
- How has DOCOsoft contributed to the development of Blueprint Two?
DOCOsoft has been closely involved in Blueprint Two, providing influential feedback, constructive suggestions, and practical insights at every stage of the project.
- What is DOCOsoft’s role in the digital transformation of the Lloyd’s and London markets?
DOCOsoft is the leading provider of claims software solutions to the London (re)insurance market and is deeply involved in Blueprint Two, contributing feedback, suggestions, and practical insights throughout its development.
- What percentage of the Lloyd’s market does DOCOsoft’s customer base represent?
DOCOsoft’s customers collectively account for 30% of the Lloyd’s market. - How does DOCOsoft engage with market events and announcements related to Blueprint Two?
DOCOsoft actively engages with every market event, announcement and release of specifications or documentation, ensuring it understands the implications and can represent its clients’ interests. - What process does DOCOsoft follow before, during, and after these events?
DOCOsoft prepares by analysing materials and preparing questions, takes detailed notes during events, and follows up with reports, escalations, and action points shared with its clients. - How does DOCOsoft ensure that Blueprint Two documentation and specifications are up-to-date?
DOCOsoft’s expert team continually reviews all published documentation to ensure that all functional and technical messaging specifications reflect the current project scope and requirements.
- What aspects of the documentation does DOCOsoft review?
DOCOsoft validates assumptions across Writeback claim notification, retrieval and response, claims workflow triggers (CWTs), the ACORD document repository interface (DRI), data dictionaries, and change requests (CRs). - What is Writeback, and what role does DOCOsoft play in relation to it?
The Writeback system is involved in claims notification, retrieval, and response. DOCOsoft is performing a detailed technical-impact analysis to understand how changes to Writeback affect its clients systems and to identify necessary adaptations.
- How does DOCOsoft handle project security protocols and technical impact analysis?
DOCOsoft reviews project security protocols to ensure alignment with current and anticipated requirements – as well as conducting thorough technical impact analyses for all proposed changes. - What support does DOCOsoft provide for Blueprint Two user acceptance testing (UAT)?
DOCOsoft prepares on-boarding documentation, helps clients register for testing, develops customised deployment plans, makes configuration changes for testing, performs connectivity testing, and provides business analysis support. - How does DOCOsoft assist clients in relation to testing and connectivity with Velonetic?
DOCOsoft ensures that two-way messaging flows correctly between clients and Velonetic’s systems, supports issue review and triage during UAT, and adds value through detailed analysis and testing support.
- What does the cutover process for Blueprint Two go-live involve?
The cutover process involves DOCOsoft creating customised DevOps pipelines, providing bespoke deployment plans, ensuring production registration, conducting connectivity testing, and planning rollback scenarios for its clients.
- How will DOCOsoft ensure a smooth transition and manage potential issues during cutover?
DOCOsoft’s dedicated cutover team will ensure that all systems and infrastructure are prepared, liaise with Velonetic, make comprehensive backups, and provide remote access support during cutover.
- What is DOCOsoft’s hypercare support, and what does it entail?
DOCOsoft’s hypercare support service provides dedicated rapid-response troubleshooting during the first three months after Blueprint Two go-live, including daily meetings with client teams, active issue resolution, and system performance monitoring. - How will DOCOsoft monitor and support Blueprint Two system performance post-go-live?
DOCOsoft will conduct ongoing performance analysis against pre-launch benchmarks, meet regularly with Velonetic to discuss issues and resolutions, and plan for the transition from hypercare to standard support.
- Why is Blueprint Two crucial for the London market?
Blueprint Two will have a transformational impact, enhancing London’s ability to maintain its pivotal role in the global (re)insurance ecosystem. A smooth transition is essential to avoid potential damage to London’s global reputation. - What challenges has Blueprint Two faced?
Blueprint Two has encountered an array of delays and challenges – as can often happen with large ambitious projects – but these are being managed with a focus on practical steps to ensure preparedness.
- How is DOCOsoft ensuring its clients are prepared for Blueprint Two?
DOCOsoft is fully committed to preparing its clients by addressing potential pitfalls in advance, smoothing their path to Blueprint Two implementation based on thorough market engagement, documentation review, and proactive support provision.
- What are the phases of Blueprint Two?
Phase 1 involves replacing legacy systems and moving to a new cloud-hosted digital platform. Phase 2 will enable fully digital placement of risks and comprehensive digital messaging. - What are the key systems and processes involved in Phase 1 and Phase 2?
Phase 1 covers the International Premium Orchestration (IPOS) and International Claims Orchestration (ICOS) services, and the re-platforming of the Insurers’ Market Repository (IMR). Phase 2 includes developing a new Core Data Record (CDR) and a Digital Gateway.
- What systems are being replaced in Phase 1?
IPOS will replace LIDS and POSH systems for premiums, and ICOS will replace CLASS and ECF for claims.
- What are IPOS and ICOS?
IPOS is the International Premium Orchestration service that replaces existing premium systems. ICOS is the International Claims Orchestration service, which replaces current claims systems. - How will the Insurers’ Market Repository (IMR) be re-platformed?
The IMR will be moved from a legacy system to the cloud. This involves transferring around 80 million documents. - What is the Core Data Record (CDR), and how will it be used in Phase 2?
The CDR standard will be used to receive, validate, augment, and store data and documentation in the new Digital Gateway. This will minimise errors and reduce re-keying and duplicated effort.