VIDEO
HIGHLIGHT
Log InSign up
Blueprint Two Working Session 1
SummaryTranscriptChat

Blueprint Two Working Session 1

Introduction

The speaker introduces himself and the event, talks about the venue and theme song, thanks attendees for coming, and dispels a rumor he started at a previous event.

Event Introduction

  • The speaker introduces himself and welcomes attendees to the event.
  • He thanks attendees for coming and notes that there is a full house.
  • The speaker dispels a rumor he started at a previous event about prioritizing Blueprint 2 over other transformation initiatives.
  • He jokes about finishing Blueprint 2 before he dies and assures attendees that it will be completed.

Event Details

The speaker discusses the purpose of the event, encourages interaction during breakout sessions, announces future events, and provides an update on the roadmap.

Event Purpose

  • The speaker explains that this event is meant to be more interactive and technical than the previous one in December.
  • He encourages attendees to ask questions during breakout sessions.

Future Events

  • The speaker announces that there will be three more events over the course of the year.

Roadmap Update

  • The speaker confirms that the roadmap presented in December has been confirmed.
  • He notes that sequences one and two are complete and being used by customers.
  • Sequences three, four, and five will require more help from customers.

Lloyd's Building Update

The speaker provides an update on progress made with joint efforts between Lloyd's people, joint venture leadership, and dxc leadership.

Joint Efforts Update

  • The speaker notes that there is a joined-up effort between Lloyd's people, joint venture leadership, and dxc leadership.
  • He explains that the teams are working together to deliver results.

Conclusion

The speaker concludes the event by thanking attendees and encouraging them to become part of ec10 communities.

Event Conclusion

  • The speaker thanks attendees for coming and encourages them to become part of ec10 communities.

Introduction

The speaker introduces the purpose of the meeting and explains the importance of data standardization.

Data Standardization

  • Data standardization is important for compiling data for placement.
  • There will be a variety of sequences over the course of 23.
  • Collaboration and input are key to adoption.

Sequences Overview

The speaker provides an overview of the five sequences that make up the project.

Sequence Breakdown

  • Sequence one is foundation building, including cloud services security messaging.
  • Sequence two is global premium and claims for Singleton business.
  • Sequence three is London Market premium and claims specifics.
  • Sequence four is delegated authority, same as sequence three but for delegated authority.
  • Sequence five is Gateway.

Benefits of Data Standardization

The speaker explains why data standardization is important and how it will benefit customers.

Benefits

  • Better offering for customers using a common set of data to talk to each other in terms of how we place business settled claims which will make it much faster than it is today.
  • It will make it cheaper both in central services and firms in terms of back-office work.
  • Common set of data will lead to new innovation in the marketplace.

Workshops Update

The speaker provides an update on upcoming workshops related to the project.

Workshop Schedule

  • May workshop: update on services provided by joint venture as a result of digitization, deployment strategies, and smaller chunks delivery approach.
  • September workshop: spend more time talking about customer journeys or business processes for open market claims and delegated authority.
  • December workshop: sets up 24 in terms of what's going to be delivered and what we'll need to do as we get ready for next year.

Closing Remarks

The speaker concludes the meeting and thanks attendees.

Conclusion

  • Attendees are encouraged to attend the workshops.
  • Bob and Chris provide a roadmap update.
  • Breakout sessions will follow.

Introduction

The speaker introduces the purpose of the meeting and what services are available today. They discuss how these services can benefit attendees and how they can get involved.

Available Services

  • DXC is available for service in a matter of weeks.
  • Sequence three and four will be available around Q1 of 2024.
  • DXC is looking to cut services into bite-sized chunks for easier adoption.
  • Parts of sequence three and four can be delivered earlier than Q1.

Introducing the CEO

  • The speaker introduces Bob, who has taken over as CEO of DXCJv.
  • Attendees are encouraged to ask Bob any hard questions they may have.

Planning for Adoption

The speaker discusses moving out of build and planning for adoption. They emphasize that this process involves everyone in the room, not just Javen Lloyds. Workshops are designed to help attendees prepare for adoption.

Workshops

  • Workshops are designed to help attendees prepare for adoption.
  • Attendees are encouraged to ask any questions they may have during workshops.

Data Center Move

The speaker discusses the data center move scheduled for February 16th - 23rd. They mention that testing and dress rehearsals have been completed.

Data Center Move

  • The data center move is scheduled for February 16th - 23rd.
  • Testing and dress rehearsals have been completed.

Introduction

The speaker talks about resiliency, speed, and security. He apologizes for being late but is more focused on delivering the next 10 days.

  • Resiliency, speed, and security will take a step change before the end of this month.
  • Apologizes for being late but is more focused on getting the next 10 days out of the way and delivered to you.

Data Center Move

The speaker mentions that they are going to get into sequence two. Martin and Anne will walk through what is available in sequence two.

  • Speaker mentions that he will handle data center move questions.
  • Martin and Anne will walk through what is available in sequence two.

Sequence Two: Global

Martin and Anne talk about Sequence Two: Global. They mention that it's outward-facing and available as a standalone platform. It supports peer-to-peer premium and claim submissions and agreement.

  • Sequence Two or Global is outward-facing.
  • Available as a standalone platform.
  • Supports peer-to-peer premium and claim submissions and agreement.
  • No London Market ISMs in global sequence two.

Interacting with the Platform

Martin explains how you can interact with the platform. There are two ways of interacting with it depending on your digital maturity level: Accord standard interaction through APIs or accessing the platform through a portal.

  • Two ways of interacting with the platform: Accord standard interaction through APIs or accessing the platform through a portal.
  • Creates a flexible solution that doesn't matter if you've got different levels of maturity for different participants who want to access the platform.
  • Common data standards across the platform.

Business Flow for Global Through Platform

Martin puts up a diagram to show the business flow for Global through the platform. He explains that there are a number of different capabilities and engines, such as iros for risk element, IPOs for premiums, and icos for claims.

  • Diagram shows the business flow for Global through the platform.
  • Different capabilities and engines: iros for risk element, IPOs for premiums, and icos for claims.
  • Iros is optional.
  • Either a broker or carrier can submit a record.
  • Soft validation helps with automatic validation further down.

Query Functionality and Claims Flexibility

This section discusses the query functionality and claims flexibility available on the Global digital platform.

Query Functionality

  • The carrier has the option to accept or reject a value that doesn't look quite right.
  • If accepted, payment will be made through a funded account in a maximum of two hours.
  • Real-time query functionality is available within the platform, which cuts down query time.
  • The query functionality looks like an instant messaging chat.

Claims Flexibility

  • There is added flexibility around who can receive claim payments, including brokers, TPAs, and end-insured parties.
  • Reporting is available through dashboards and bespoke reports.

Benefits of the Global Digital Platform

This section outlines the benefits of using the Global digital platform.

Speed

  • Payments are made quickly through a funded account in as little as five to ten minutes for major currencies.
  • Real-time chat functionality speeds up query resolution.

Visibility

  • All data on the platform is auditable and available for MI purposes.
  • A dashboard is available for authorized users to view data.

Quality and Precision

  • Soft validations are in place to ensure quality and precision of data.
  • Centralized document management allows for easy access to uploaded documents by authorized users.
  • Data received via messaging is Accord standard compliant.

Flexibility

  • Different claim payments can be made to different participants.
  • Non-funded accounts allow for batched payments, saving on bank charges.

Security and Performance

  • The platform is resilient and secure due to being cloud-based.

Example Use Cases

This section provides examples of how participants in the market might find benefit from using the Global digital platform.

Carrier with U.S. Brokers

  • A carrier was receiving central settlement messages and payments, but after their business moved to U.S. brokers, they lost this benefit.

Broker with Multiple Carriers

  • A broker had multiple carriers and struggled with the different processes for each one.
  • The Global digital platform provided a standardized process for all carriers.

Introduction to Global Platform

In this section, the speaker introduces the Global Platform and explains how it can benefit businesses that are not digitally mature.

Benefits of Global Platform

  • The platform provides a common standard of data and payments.
  • It allows businesses with disparate processes to have a common platform.
  • It extends the reach of creating a common process and set of data standards.
  • Participants who are not digitally mature can also join the platform.
  • Reporting, self-serve MI, and document storage are available on the platform.

Comparison with Rushicon

In this section, the speaker compares Global Platform with Rushicon and explains why businesses should consider using both platforms.

Benefits for Rushicon Users

  • The Global Platform allows participants who are not at the same level of digital maturity to use the platform.
  • It extends the reach of creating a common process and set of data standards.
  • Aggregation of payment is possible, which reduces bank fees.
  • Flexible payment in terms of claims is available.

Invitation to Explore Global Platform

In this section, the speaker invites attendees to explore Global Platform further by attending demos and workshops.

Invitation to Attend Demos and Workshops

  • Attendees are encouraged to come and speak with representatives about how they can use Global for their benefit.
  • Individual demos will be available upon request.
  • Representatives will be available throughout the afternoon in breakout areas.

What's Next for Global Platform?

In this section, speakers discuss what's next for Global Platform beyond sequence two.

Analogy with Triathlon

  • The speaker draws an analogy between triathlons and what's next for Global Platform beyond sequence two.

What's Next for Global Platform?

  • Speakers discuss what's next for Global Platform beyond sequence two.
  • They will talk about sequences three, four, and five in the future.

Triathlon and Sequence Overview

The speaker uses a triathlon analogy to describe the program's current state, having completed the first milestone and transitioning into the next phase. They introduce sequence three, which involves premium and claims processing for open market business, and explain how it fits into the overall plan.

Transitioning to Sequence Three

  • The program is in transition from the swim to the bike leg of a triathlon.
  • Sequence three involves premium and claims processing for open market business.
  • The team has learned lessons from previous phases and is shifting focus to sequence three.
  • A replan was done to come up with a more confident plan on how they will progress.

Delivering Sequence Three

  • Experts will explain what open market business is.
  • Help is needed from everyone to deliver sequence three successfully.
  • Sequence five will be delivered in parallel as it is essential for delivering the program successfully.

Program Design

  • The program was intentionally designed to deliver value first before layering on complexity, de-risking the overall program.
  • This approach gives teams experience and confidence before adding additional complexity.

Challenges in Open Market Business

Steve discusses some of the challenges faced by open market businesses such as improving failure rates, moving away from documents, and achieving faster, better, cheaper solutions.

Challenges Faced by Open Market Businesses

  • Open market businesses face challenges such as improving failure rates, moving away from documents, and achieving faster, better, cheaper solutions.

Introduction to Blueprint 2

In this section, Steve and the speaker discuss the problems that Blueprint 2 aims to solve. They also provide an overview of the different streams of work that Blueprint 2 is focusing on.

Streams of Work

  • The first stream of work is focused on data standards and reducing processing times for transactions.
  • The second stream of work is focused on engaging with the community to show them how the system can interact better for them from a CDR, premiums, and claims perspective.
  • The third stream of work is focused on building new services and technology that will be consumed by users. This includes Gateway or iros, iposite icos, premium service, claim service, API portal Accord.
  • The fourth stream of work is focused on transition. This includes Legacy messaging, digitizing subscriptions, and getting Legacy data into the new system.

Supporting Services

  • Supporting services are critical to the success of Blueprint 2. These include Settlement Services, reporting Services document management notification parties.

Conclusion

In this section, the speaker briefly mentions that Sean Ed and Jay will take attendees through what's next in breakout sessions.

What's Next?

  • Attendees will learn more about what's next in breakout sessions led by Sean Ed and Jay.

Introduction

The speaker introduces the topic and mentions that they are building a product that will allow them to report on what they do. They credit their build team and key partners for their success.

Building the Product

  • The speaker mentions that they are building a product that will allow them to report on what they do.
  • They credit their build team, which is 400 strong and based in three main locations: UK, Egypt, and India.
  • At peak, there will be 23 different teams tackling this project.
  • Several key partners play a pivotal role in the success of this project: AWS, ASG, Datum, and Vertese.

Dicing Up the Project

The speaker explains how they are dicing up the project into horizontals and verticals. They also discuss how they are going to logically build from left to right.

Dicing Up Horizontals and Verticals

  • The speaker explains how they are dicing up the project into horizontals (settlement messaging and MI) and verticals (risk product, premium product, claims product).
  • Settlement messaging and MI fall in the supporting services space but are also products in their own right.

Logical Build from Left to Right

  • They go about logically building from left to right so as not to take too long.
  • They parallelize as much of the work as possible along both horizontal and vertical lines.

Conclusion

The speaker concludes by encouraging the audience to ask questions and get involved in the project.

Getting Involved

  • The speaker encourages the audience to ask questions and get involved in the project.
  • They mention that Steve will be talking more about the placement side of things.

Roles and Responsibilities in Data Assembly

This section covers the consultation process for roles and responsibilities in data assembly. It is a crucial part of agreeing on who will be doing what in the data assembly process.

Submission Points

  • The consultation covers submission points, which are important for getting more data earlier in the process.
  • The consultation also covers at what point the full CDR needs to be complete and what stages are in between.
  • Soft calls and enrichment are discussed, as well as how errors will be managed and who will be responsible for correcting which data items.

Importance of Getting Involved

  • It is urged that everyone gets involved in this consultation to ensure that teams know what they need to do and how they need to operate to collect the necessary data.
  • Getting this right is critical because it will define what is needed for brokers, carriers, and their teams to drive automated premium and claims processes.

Other Processes

  • There are other bits around ebot and ECOT as we move through the premium and claims processes respectively.