17
00:01:13.380 --> 00:01:36.030
Sebastian Good: Thanks. Laura, excited to be here this morning to talk a little bit about how we build cutting edge experiences in the Ftc. 3 and open fin ecosystems. I'm excited to have Chris Thomas and Andy join us. they have had a lot of bumps and bruises over the years and built some pretty cool things in this ecosystem. So we're gonna have a little chat with them and hear about how we've made all that stuff work
18
00:01:36.384 --> 00:01:48.065
Sebastian Good: first a few minutes just on our company itself. For over 20 years experiment has been designing and deploying digital solutions with a focus on creating powerful experiences for expert users.
19
00:01:48.755 --> 00:02:13.940
Sebastian Good: We've always found that trained users experts in their field have particular wants and needs that transcend the industries they work in, whether they're managing electric grids for safety or prospecting for hydrocarbon deposits managing pharmaceutical supply chains or managing client assets responsibly. In the wealth world. They do work differently than most users. They explore their data more. They have high levels of expertise, require higher performance from their software.
20
00:02:13.940 --> 00:02:20.470
Sebastian Good: The stakes of their work are much higher, with complex data and their success or failure. Reflecting on the firm itself.
21
00:02:20.792 --> 00:02:47.709
Sebastian Good: the solutions we built for these experts are deeply useful not just pretty and we've built solutions across a bunch of these industries with these demanding requirements. In mind, we do have a digital solutions practice that has built products through what we call a full stack. Everything from product strategy, user experience, design, data, strategy, analytics and AI modernization, which is common thread here in finance and the ability to deploy and so support solutions for our customers.
22
00:02:49.170 --> 00:03:05.870
Sebastian Good: we have a lot of experience working in financial services. It is the majority of our business across wealth asset management and banking and in the context of this conversation. We're proud to have been an open fight sort of open fin certified development partner since since 2,017
44
00:07:05.240 --> 00:07:32.629
Sebastian Good: we work with partners like Morningstar to produce first class decision making experiences for customers of their data. We help with things like fund screening and portfolio analytics. We're excited this week to have closed the deal with another market news and data provider and hope to talk soon about how we're bringing their information to professional desktops as well. Our spiral connected framework is an accelerator that manages data, connectivity, analytics and workflow including in fraud analytics workflows at 3 of the top 10 Us. Banks
45
00:07:32.970 --> 00:07:51.300
Sebastian Good: from Treasury trading solutions to telephony and communications, some of which will show a little bit today. We've built tools that drive meaningful value by bringing useful and beautiful complex data experiences to life. So today we're here to talk to you a bit about how we do that in the Ftc 3 and open fin ecosystems
46
00:07:53.184 --> 00:08:21.119
Sebastian Good: I'll start our conversation with just a few thoughts on the ftc, 3 ecosystem itself. You know, as an open standard, it's easy to get involved with and steer, and a lot of companies have done so over the years from vendors like Dow Jones or flex flex trade to solutions. Implementers like us. A lot of people are designing their solutions to be ftc, 3. Compliant you can join fin o finos itself, and vote on extensions to the standard. But it's also very easy to get involved
47
00:08:21.120 --> 00:08:41.410
Sebastian Good: in the different user groups and conversations around how the standard is advancing and what changes you know, if any improvements may be needed for some of the work that you're doing. What does it mean for us as we think about how we build solutions for our customers. To me one of the biggest things is it? It means we can approach how we go to market differently.
48
00:08:41.718 --> 00:09:01.319
Sebastian Good: You know, if you're a vendor of data or services like an Lms or a market data provider, you can look to this growing ecosystem as a way of quickly meeting your customers where they are, and becoming a native part of the workflows that matter to them, you know. For many years, especially, data vendors found themselves, building their own applications to bundle with their data
49
00:09:01.320 --> 00:09:26.290
Sebastian Good: and sometimes struggling, because that application is really just sort of a small footprint over the full course of everything that's needed. Say, to complete a trade or rebalance portfolio, or talk to a customer about their wealth needs being a point solution can sometimes be difficult when you're 1 point in a hundred point workflow. And one of the great things about this ecosystem is now you can find a way to deliver that key value into that larger workflow without having to try to
50
00:09:26.290 --> 00:09:28.119
Sebastian Good: implement all of it
51
00:09:28.130 --> 00:09:50.749
Sebastian Good: on the flip side. If you're one of the people building those workflows, like many major banks like Jp. Morgan Wells, Fargo, are doing. It means you don't necessarily have to think about buying all of it from one vendor and being stuck with their decisions, you know, even great products have this problem for many of their customers, where, when their customer needs a new feature or a new data integration or a change.
52
00:09:50.860 --> 00:10:18.089
Sebastian Good: They often have to get in line behind all the other customers that are requesting things, and you know, you do end up with a rich, powerful product, but often as a consumer of it, it can be frustrating if it is, too, all encompassing, and becomes difficult to build the workflows and integrations you need. So it it means you don't have to necessarily be beholden to those vendors, and likewise you don't have to think about building it all yourself, which has been a solution. The industry seen a lot over the years, you know, that can come at such a great cost?
53
00:10:18.456 --> 00:10:21.020
Sebastian Good: We think that by embracing this ecosystem
54
00:10:21.220 --> 00:10:38.819
Sebastian Good: it means, you know, you can build and buy to end up with the best of breed solutions. So for me, when I think about how am I most quickly adding value for my customers, I think about leaning on this as an accelerator, not just for development speed, but for go to market speed and higher business value.
55
00:10:38.820 --> 00:10:57.740
Sebastian Good: So with with that in mind. I thought I'd ask Andy, maybe as one of our great Project managers, who always seems to leave his customers happy to talk a little bit about, you know. How does he approach? How do you approach, Andy? You know, planning an open fin or Ftc 3 development project specifically.
56
00:10:59.443 --> 00:11:08.509
Andy Nicholls: Thanks, Sebastian. Well, this kind of integration capability brings interesting ux challenges for the implementation team.
57
00:11:09.080 --> 00:11:16.860
Andy Nicholls: We always promote the the use of ux designers for all our projects. But the most successful ex examples we've seen
58
00:11:16.980 --> 00:11:26.579
Andy Nicholls: of this type of integration have all started with a very focused discovery and design effort prior to the start of any development effort.
59
00:11:27.030 --> 00:11:49.629
Andy Nicholls: So you lay out the used case an obvious one. But and yes, in some instances you may want to have full access to an internal or a third party app that pops up in a new window or a view, but if the intent is to update a let's say, a Crm system with notes from a meeting or a phone call.
60
00:11:49.700 --> 00:12:01.269
Andy Nicholls: Do you just need a notepad to pop up that that can be called, and then that updates the client record in the system in the background without having to launch the the full application.
61
00:12:01.380 --> 00:12:06.089
Andy Nicholls: Or if you want to send an email to the A contact after a phone call
62
00:12:06.571 --> 00:12:12.680
Andy Nicholls: do you need to open outlook or just click and launch directly into a pre-populated email.
63
00:12:12.880 --> 00:12:13.900
Andy Nicholls: Yeah, so
64
00:12:14.190 --> 00:12:24.430
Andy Nicholls: start with something simple and build from that is always a good plan. You can add more complexity and additional workflows so that you get much more familiar with the platform.
65
00:12:24.490 --> 00:12:29.670
Andy Nicholls: And also, as you gather, real and usable feedback from the end users.
66
00:12:30.178 --> 00:12:42.019
Andy Nicholls: We've had, really tremendous success using interactive figma designs working with the product teams and the end users and the sport groups to create much more effective solutions.
67
00:12:43.050 --> 00:12:57.769
Sebastian Good: That makes a ton of sense. You know, one of the questions I always have when we're scoping a project is wh, what could go wrong. Right? If I have a great approach like this, what are the risks I may run into nonetheless blockers? I might I might hit.
68
00:12:59.100 --> 00:13:14.999
Andy Nicholls: Well, one of one of the main blockers which we were, we learned very early on, and one of the key areas to focus on early in the planning is around the Apis. So you have your use case. You've determined what applications you need to integrate with.
69
00:13:15.080 --> 00:13:21.710
Andy Nicholls: It's really critical to review those published and private Api's. Do you plan to use
70
00:13:21.990 --> 00:13:28.209
Andy Nicholls: to make sure that all of the data elements are available for each of the use case or the workflows that you need.
71
00:13:29.047 --> 00:13:39.650
Andy Nicholls: Another thing to consider is it's it's critical to determine this security constraints that may be in place to for you to access those Apis
72
00:13:40.167 --> 00:13:58.920
Andy Nicholls: we've seen significant timeline impacts on some projects over internal concerns around who can access, let's say, sales data or Crm data which you know makes sense. The earlier, you can identify these risks and get the key stakeholders involved
73
00:13:59.030 --> 00:14:03.609
Andy Nicholls: and active on the project the better it is, and the easier it is to address the issues.
74
00:14:04.270 --> 00:14:30.189
Sebastian Good: That makes sense. I I can certainly recall times in our engagements where we've had. Yeah. Engineers fired up ready to code to build some great, you know, like, you say, Crm integration. But it turns out, yeah, some of the infrastructure or privacy or technology concerns around access to say, you know, Salesforce Api, or some internally developed tool haven't been answered yet. So here we are, sitting idle, waiting for that to be done. That's gotta happen earlier makes a ton of sense.
75
00:14:30.558 --> 00:14:36.660
Sebastian Good: What best practices do you bring to to to bear on on these sorts of projects?
76
00:14:38.140 --> 00:14:50.239
Andy Nicholls: Well, I guess. This is a a really a best practice that we bring as experience to any of the projects we run. But it can be on these types of integration projects. It can really be, make or break.
77
00:14:50.530 --> 00:14:57.199
Andy Nicholls: You have to keep a constant focus from the key stakeholder groups at all stages of development.
78
00:14:58.004 --> 00:15:01.090
Andy Nicholls: These, these projects are normally delivering
79
00:15:01.120 --> 00:15:07.620
Andy Nicholls: a pretty impactful change to what are well established workflows and legacy applications.
80
00:15:07.987 --> 00:15:26.740
Andy Nicholls: And although you know, the people using these legacy applications may not necessarily be happy with them. Some, you know, most of the time they've been working with these applications for years and years, and are very comfortable with the limitations and know how to work through their daily work. Workflow. So
81
00:15:26.840 --> 00:15:41.619
Andy Nicholls: you know, adoption of the new application is critical when you've got people so well established in these legacy environments. So, as mentioned earlier, working with the end user, the product teams. The support groups is essential, but maintaining
82
00:15:41.640 --> 00:15:47.699
Andy Nicholls: that commitment from the key stakeholders and getting their input on a continuous basis throughout.
83
00:15:47.820 --> 00:15:50.269
Andy Nicholls: The project is really really important.
84
00:15:51.368 --> 00:16:03.209
Andy Nicholls: It's best to create an environment where the stakeholders can constantly see the work in progress and any changes and provide the development team with instant feedback and approval.
85
00:16:04.980 --> 00:16:15.529
Andy Nicholls: you're gonna find that third party and internal applications are gonna behave differently than expected, or they may not have the exact data elements that you were expecting
86
00:16:15.810 --> 00:16:23.290
Andy Nicholls: this can impact the feature set and actually shape the workflow slightly differently than you originally designed for.
87
00:16:23.640 --> 00:16:38.470
Andy Nicholls: So having an environment that you can show that getting the buy in and validation early and on a regular basis with the key stakeholders will will help to bring success and easy adoption of the final solution.
88
00:16:39.310 --> 00:16:47.660
Sebastian Good: I guess that makes a ton of sense. It's a bit of a 2 edged sword building, a workflow integration. On the one hand, you get a bunch of benefits by bringing all these tools together.
89
00:16:47.820 --> 00:16:58.709
Sebastian Good: On the other hand, as a project manager, by golly, you've got to bring all these projects together, which is more, more cats to herd, more people to coordinate, more stakeholders, to manage right. That makes a ton of sense.
90
00:17:00.340 --> 00:17:21.701
Sebastian Good: So having planned and discovered and assessed or different vendors and internal solutions, and Apis and maybe even agitated with them to improve Ftc. 3. Compliance they may have if they're if they're in the Ecos ecosystem. It's time to actually start designing and building the real new software artifact.
91
00:17:22.339 --> 00:17:34.329
Sebastian Good: why don't I turn now to Chris Hobson, who's led a lot of these sorts of engagements for us. What are some of the most surprising things you've seen about teams that are put together to build ftc. 3 applications.
92
00:17:35.180 --> 00:17:44.589
Chris Hobson: Yeah, sure, thanks, Sebastian. Well, you know, if you think about it. Ftc, 3. And the you know the open fin container, it's actually quite a unique set of technologies. Right?
93
00:17:45.011 --> 00:17:50.970
Chris Hobson: I mean, we're building something that looks and feels very much like a native or a desktop application.
94
00:17:51.000 --> 00:18:13.770
Chris Hobson: But it's still really front end web. Dev, right? Some folks get quite mystified. Even developers can get quite mystified bit by this. You know this concept. So we've even seen other firms out there staff their teams with like Java and.net developers right? Because it's seems like a desktop app. So I mean, even in those situations we've brought in. We've we've actually
95
00:18:14.020 --> 00:18:21.639
Chris Hobson: guided these teams in in general web dev practices, you know, like simple HTML, dom and modern Javascript type stuff like that.
96
00:18:22.470 --> 00:18:39.130
Sebastian Good: That's pretty funny, I mean, I I guess it's easy to have a chuckle about staffing the wrong kind of staff on a project. But actually, in this industry a ton of the work was done earlier than other industries in digitizing the desktop, and there are a lot of Java and.net programmers out there that have made amazing things that
97
00:18:39.130 --> 00:18:53.329
Sebastian Good: yeah. Even in this, the year of our Lord 2024 are transitioning to web technologies. And yeah, no, that I've noticed that that's a significant amount of work that our tech leads often do is not just leading the implementation, but leading the mentoring
98
00:18:53.575 --> 00:19:11.480
Sebastian Good: of a team that's coming up to speed on on kind of modern web development. So what what kind of things do they have to learn then these web developers like, I show up and I'm already I'm a great Javascript developer, and I built web apps before. But now I'm jumping into the Ftc, 3 space like, how is it different? What do? What do I need to learn.
99
00:19:12.160 --> 00:19:14.653
Chris Hobson: Yeah, you know, to be fair. It's it's it's
100
00:19:14.950 --> 00:19:41.349
Chris Hobson: It's really advanced front end stuff. I mean, I might even dare to say it's front end architecture level, I mean, cause if you break a typical front end, project down a typical project you're building for a library like react or view angular. You're sort of in a self contained like guided process. There's a there's a known way to do it, and you're making a a single single page app. That's a single bundle and whatnot. But you know, when you're talking about Ftc, 3 in these containers.
101
00:19:41.360 --> 00:20:07.000
Chris Hobson: you're building really an orchestration across multiple running web contexts that all need to work together. So anything from a splash page that comes up to a modal or a login page, they're all separate little security contexts that you need to be aware of, and they all have to talk to each other. So there's all these implications when it comes to like web security and permissions. Or, you know, chorus issues you might run into, or authentication. You gotta be aware of all that advanced stuff.
102
00:20:07.190 --> 00:20:35.574
Chris Hobson: and you know, not to mention the performance implications. Right? So when you're building an app, a single page, app, you kind of have your own little space to manage, and it runs the way it runs. But when you're in, you know a container like open fin, you got all these separate processes that you need to be aware of, and you gotta make sure that you don't have a giant monolithic app. That's kind of slowing everything down so you could do things like tree shaking. You're basically building separate single purpose apps for different use cases and then ultimately,
103
00:20:36.950 --> 00:20:37.495
Chris Hobson: cut.
104
00:20:38.710 --> 00:20:40.190
Chris Hobson: I was doing so good.
105
00:20:42.250 --> 00:20:43.409
Chris Hobson: Let me take a breath.
106
00:20:45.380 --> 00:20:47.429
Chris Hobson: I've seen a way to close that up.
107
00:20:51.880 --> 00:20:53.540
Chris Hobson: I'm gonna start at performance. Okay.
108
00:20:53.900 --> 00:20:56.989
Sebastian Good: Yeah, do it? I mean, Laura's gonna love this.
109
00:20:59.330 --> 00:21:01.180
Alright. Well, we got it.
110
00:21:03.030 --> 00:21:06.530
Chris Hobson: I don't know, do we? Is it hard to cut these, or did you just do jump cuts? Usually.
111
00:21:07.190 --> 00:21:12.950
Yes, I asked Sarah. She's gonna cut it. She said. It would take not long at all for her to just cut it like.
112
00:21:13.250 --> 00:21:16.219
she said. If it's just a snippet's fine. Okay.
113
00:21:18.590 --> 00:21:37.019
Chris Hobson: And this is not to mention the performance aspects of this right? So if you're building lots of little applications, you gotta make sure that you're you're doing them. It would fully optimize bundles, right? You wanna do tree shaking and ultimately make single use or single purpose little windows that could run in parallel without dragging the whole system down.
114
00:21:37.020 --> 00:21:49.300
Chris Hobson: So there's other things you could do like, maybe sharing queries among multiple windows, using shared workers and things like that. So again, a lot of advanced web technology stuff that you gotta consider in these projects.
115
00:21:49.900 --> 00:22:18.749
Sebastian Good: I think that makes sense. And I've certainly noticed that in our recruiting process for great front end developers. You know, it sounds so simple front end developer, back end developer. But in fact, a front end developer, so called, is really building on an entire huge application. Really, an architecture called browser right? And compared to even just 10 years ago, it's much more complex than just laying out some ui which itself is its own challenge. So really an understanding of how a browser works, and how that multi-threaded multi container experience works
116
00:22:19.190 --> 00:22:21.530
Sebastian Good: is critical that that makes a ton of sense.
117
00:22:22.680 --> 00:22:23.630
Sebastian Good: So
118
00:22:23.650 --> 00:22:40.699
Sebastian Good: I I I guess. I've I've I've queued up my project. I've hired to write developers. They're great web developers, and I have a workflow vision that my stakeholders are excited about. So I'm in the kitchen, and I just sort of shake some Ftc 3 salt onto the project. And all this works right, Thomas. That's been your experience.
119
00:22:40.700 --> 00:23:06.961
Thomas Holmes: Yeah, yeah, certainly. No. I I mean, if only folks that easy. Right? Because, there are certain considerations that you have to do. So ftc, 3 is a spec, and it's implemented by open fin in this like container world. And but there are gaps and decisions that you need to make. So, for example, there's like app discovery. How do you actually search for find apps? Or how does one app know about what a, what other applications are even available for it to talk to.
120
00:23:07.474 --> 00:23:12.410
Thomas Holmes: It's something that you have to consider, you know. There, there's a model for it, but you don't necessarily have to follow that
121
00:23:12.816 --> 00:23:37.993
Thomas Holmes: intent resolution is another one where there's intentionally a gap left there where you know you have a one application, and you wanna view a chart. So you raise an intent. But there are multiple applications that could actually handle that. So you have to figure out a way to resolve that down to what you actually wanna do, you could either present that option to a user or you can make it some kind of default in the background, or you could
122
00:23:38.685 --> 00:23:52.590
Thomas Holmes: make it based off of user settings. The user could choose a default application to handle certain intents. But again, that's up to you as the platform provider to make. You know, to make your experience.
123
00:23:53.115 --> 00:24:05.530
Thomas Holmes: Some other things to consider that aren't necessarily like the most basic cases, but very useful is a context enrichment. So imagine that you have an application that wants to share an instrument.
124
00:24:05.822 --> 00:24:30.360
Thomas Holmes: There are many ways that an instrument could actually be defined, or many properties that can refer to the same instrument. Right? So imagine you have an application that's trying to send. You know, a a ticker symbol for Microsoft. As it comes into your platform, you could actually reach out and enrich that context so you can add other properties to it, whether it's the Q sub the asset, or you know any of the other different ways to actually identify it
125
00:24:30.480 --> 00:24:52.469
Thomas Holmes: before you pass it along to where to all the disparate applications that are listening for it. You could do that, you know, adding it directly to that concept, or you could do it in parallel. You could change that from being just a a a, you know, a symbol that's coming in to. Then figuring out holdings and set a different context in parallel to that along the way. And then, along with
126
00:24:52.470 --> 00:25:16.210
Thomas Holmes: context enrichment. There is also, like custom, intense and context. So there are guidelines for creating custom, intents and context. But as a platform provider, you get to create a spec. That's a standardization across your platform. And it's really important to do that because you're in your platform might have a hundred different applications, and they need to have some kind of common language to actually be able to communicate effectively with each other.
127
00:25:17.600 --> 00:25:39.439
Sebastian Good: Makes sense. I mean that context enrichment is really your example. There is kind of a case of what Andy was talking about coordinating stakeholders. Right? When you start you need to understand. I've got 4, you know, applications serving in your example. Some sort of you know. Maybe pre trade intelligence or market data need. And yeah, one of them talks Q sips. And one of them talks is, and one of them probably talks Bb, ids, and who knows?
128
00:25:39.768 --> 00:25:47.650
Sebastian Good: Unless you have that kind of data availability, you're gonna stumble in building the workflow and then figure out usage and authorization, and
129
00:25:47.730 --> 00:26:03.039
Sebastian Good: where the security master is. You need to have all that straight before you can create a really smooth experience. Yeah. And I, I think the custom. Intense and context are interesting. If you go to the Ftc. The website, you'll see that they have a set of built in intents. But every one of our customers has
130
00:26:03.040 --> 00:26:25.150
Sebastian Good: ended up building some of their own right to express the the native concepts in their platform. You know, if you're in a wealth platform. Some of your key Ids may not even exist in the Ftc. 3 spec. Like an account holder or a household, or you know a group of accounts. Right? How you create that language and how you can implement it across your different applications is is a matter of design. Right.
131
00:26:25.833 --> 00:26:28.729
Thomas Holmes: Yeah, certainly. So like, you need to
132
00:26:28.780 --> 00:26:58.459
Thomas Holmes: choose and think about your workflows carefully right so you're building a platform, so you you can design workflows for your used cases and understand and understand that it's not supposed to be 100 on rails for all the users all the time. It's hard to stop the users from doing anything they want. And you can't necessarily create workflows for every single situation. But as long as you have your base cases set. Then you have a very rich user experience set up for them.
133
00:26:59.063 --> 00:27:04.829
Thomas Holmes: Some things to consider, though, is again, you wanna really think about your workflows and your use cases, because.
134
00:27:04.860 --> 00:27:24.529
Thomas Holmes: as I said, it's a platform. And if you design something poor, or it's not a great experience, it's actually like a compounded mistake, because again, you might have a platform with 100 applications, or more than that in it. And if you're if your platform is a bad experience. You have a bad experience across all of those different applications.
135
00:27:25.088 --> 00:27:27.229
Thomas Holmes: Another thing to consider is.
136
00:27:27.350 --> 00:27:29.550
Thomas Holmes: the apps are what they are.
137
00:27:29.560 --> 00:27:42.829
Thomas Holmes: They might be yours. They might be third party and you can't necessarily control them. You can add little bits and pieces to make them fit into your workflows. But it. It's a lot of work to enforce a strict
138
00:27:43.265 --> 00:27:46.669
Thomas Holmes: workflow to every single application in your platform.
139
00:27:47.030 --> 00:27:50.499
Thomas Holmes: So with with those things in mind, I would say.
140
00:27:50.520 --> 00:27:55.990
Thomas Holmes: keep it simple from the beginning. Get your used cases, and you could always build complexity on top of that.
141
00:27:57.350 --> 00:28:03.199
Andy Nicholls: This is Thomas. This is where our use of the figma designs and the interactive
142
00:28:03.300 --> 00:28:05.940
Andy Nicholls: designs has been really useful and
143
00:28:06.470 --> 00:28:32.700
Andy Nicholls: having a having the ability to be able to demonstrate some of the interactions directly to the key stakeholders as you're in the development process really helps them decide how they want to constrain things, or if they wanna let things be more open, as you say, you can't constrain everything all the features but it that having that ability to reflect those changes and give options
144
00:28:33.309 --> 00:28:37.139
Andy Nicholls: as you're as you're moving through the development cycle is really important.
145
00:28:37.450 --> 00:28:39.030
Thomas Holmes: Yeah, absolutely. It's critical.
146
00:28:40.070 --> 00:29:02.898
Sebastian Good: Yeah, I mean, some of the pictures that are shown here are are some of the templates we bring to bear when thinking about that back to the double edged sword. Analogy. That's great. I have a workspace that users can rearrange to do the work just the way they want. The the thing is in real life. That's a pretty small percentage of users that are tend to be really gifted at putting together highly reusable workspaces
147
00:29:03.514 --> 00:29:18.230
Sebastian Good: many of us, when presented with a build. Your own adventure of windows, build a pretty messy adventure. We're busy doing our actual work. And so there's definitely some thoughtfulness we bring to mind in those workflow considerations in okay, I have
148
00:29:18.230 --> 00:29:28.959
Sebastian Good: 15, 2,000. Whatever many applications that I'm bringing together to orchestrate. What am I doing? Is this an exploratory workflow? Is this a hub that I'm spreading out to? Or am I one of the spokes
149
00:29:28.960 --> 00:29:54.874
Sebastian Good: actually doing something, and in so doing, you know, what applications do I need to bring? And how will they interact? So you're right, Thomas, that you can't keep the user in a box on a platform like this. That's the beauty of it is that they're free to explore. But often it is, it is really important to bring them something that is sort of pre thought to start from so they can. They can do that work more more effectively. So let's think a little bit about
150
00:29:55.690 --> 00:30:12.660
Sebastian Good: Wh where do you go? So so there's those are some of the sort of the bruises and notions around managing projects and and things to think about around the technical side of of Ftc, 3. What are some of the really interesting and powerful things you can do here that are not just web development. Chris.
151
00:30:13.370 --> 00:30:17.549
Chris Hobson: Yeah, so so those are the basic tools. Right? You get the foundation in place.
152
00:30:17.580 --> 00:30:21.000
Chris Hobson: And like, you guys were sort of talking about like, well, what's the next step
153
00:30:21.463 --> 00:30:38.989
Chris Hobson: thinking about building a curated solution, essentially imagining, imagining, like, how you can build an innovative approach to solve this specific problem for your clients for your users. Right? So actually, at this point you mind if I show a little demo that demonstrates some of this stuff.
154
00:30:39.810 --> 00:30:42.719
Sebastian Good: Demo. What more can I ask for? What's the best?
155
00:30:42.860 --> 00:30:44.189
Sebastian Good: Those are the best.
156
00:30:45.600 --> 00:30:46.820
Chris Hobson: Cool. Alright.
157
00:30:47.260 --> 00:31:07.199
Chris Hobson: So yeah, today, I wanna show a little bit about what we've done for Ipc and their one view portfolio. So if you don't know. Ipc is a industry leader in voice trading technology, and we help them reimagine their existing unity, soft client, and built it within an Ftc. 3 container and open fin. Right?
158
00:31:07.570 --> 00:31:11.990
Chris Hobson: So right now, I'm going to simulate a phone call.
159
00:31:15.210 --> 00:31:16.030
Chris Hobson: Pause.
160
00:31:16.650 --> 00:31:18.569
Chris Hobson: Am I showing everything right now?
161
00:31:19.690 --> 00:31:22.520
Sebastian Good: You're showing the whole desktop. Yeah, but it's a virtual desktop.
162
00:31:23.250 --> 00:31:29.080
Chris Hobson: Oh, okay, that's good. I'm seeing the green line, even though I switch to chrome. Usually, that means you're sharing everything. So.
163
00:31:29.080 --> 00:31:30.220
Sebastian Good: Oh, no.
164
00:31:31.355 --> 00:31:35.439
Sebastian Good: you just lost your confidence, because you know someone can pick you up with and edit it with him.
165
00:31:36.230 --> 00:31:37.020
Thomas Holmes: Yeah.
166
00:31:38.810 --> 00:31:40.289
Chris Hobson: It's all good. I'll get it back.
167
00:31:40.550 --> 00:31:43.919
Chris Hobson: Okay, so you're just seeing the PC. Right now, right.
168
00:31:44.050 --> 00:31:44.390
Thomas Holmes: Yes.
169
00:31:44.390 --> 00:31:46.429
Sebastian Good: Yeah. It's a windows 11 with a.
170
00:31:46.430 --> 00:31:47.230
Chris Hobson: Several.
171
00:31:47.360 --> 00:31:48.380
Sebastian Good: Yeah. Desktop.
172
00:31:50.050 --> 00:31:50.790
Chris Hobson: And
173
00:31:59.700 --> 00:32:02.179
Chris Hobson: alright. So right now I have an incoming call.
174
00:32:02.220 --> 00:32:03.739
Chris Hobson: I'm gonna go ahead and answer that
175
00:32:05.970 --> 00:32:10.519
Chris Hobson: alright. So what we've done we have a notification that came in from a caller right
176
00:32:10.620 --> 00:32:32.959
Chris Hobson: by answering that notification fired intent to start call, and it was picked up by the unity, soft client dialer right here. But importantly, what it also brought up was the contact dashboard is what we're calling it. But it's really think like a a super advanced caller. Id, right? So what we're seeing on the left is all the information from our caller.
177
00:32:33.040 --> 00:32:58.539
Chris Hobson: All these in all these little apps, are separate, completely different apps that could come from different systems like Oms or Crm, they're basically they represent different apps that have context or information about our caller. In this case, Hazel Jones. So it's really enrichment, right? Each of these apps responding to the start, call intent. Go out and do a lookup. Find information that's relevant to the caller as you're talking to them.
178
00:32:58.560 --> 00:33:03.410
Chris Hobson: So it's great because you don't have to go when you're you're talking to somebody you don't have to go like hunt and search
179
00:33:03.500 --> 00:33:06.629
Chris Hobson: or information about them. It's all presented to you
180
00:33:06.760 --> 00:33:32.770
Chris Hobson: instantly. Right? And the key thing to remember is this, this window, this contact window is like an inherent context group. So you can actually drag more applications into this window. And they would naturally do that lookup. They they automatically connect to Hazel's context, right? So that's super important. It's convenient. And it just basically gives a great way to gather everything together neatly for the user. Right?
181
00:33:33.100 --> 00:33:34.700
Chris Hobson: So that's one example.
182
00:33:34.750 --> 00:33:37.460
Chris Hobson: But here's something else I can show, too. So
183
00:33:37.500 --> 00:33:56.910
Chris Hobson: thinking about apps and context, right, we're we're going on these say, third party applications or websites. It's important to, you know, to realize that all these existing apps, they have a lot of context already built in like phone numbers, or what websites email addresses things like that.
184
00:33:56.980 --> 00:34:09.740
Chris Hobson: So with intense, we can essentially extend these apps and give them extra power so that I can do things like our click to dial feature where I I click on this phone number. And instantly
185
00:34:10.280 --> 00:34:15.169
Chris Hobson: the intense fired and it starts a phone call with the unity dialer application.
186
00:34:15.380 --> 00:34:26.700
Chris Hobson: So in this way, we're like, we're really extending the the existing behavior of these applications that are in your system by nature, of just being within the open fin container. So it's a super powerful tool.
187
00:34:27.489 --> 00:34:29.179
Sebastian Good: So I can actually
188
00:34:29.259 --> 00:34:47.519
Sebastian Good: extend someone else's website. And that's fun that you've extended our website there. But I assume this would, you know, extend to extending someone else's web application right? Like a I don't know. Like a salesforce view or an oms view, I can go peek into there and do some something interesting.
189
00:34:47.830 --> 00:35:08.390
Chris Hobson: Yeah, yeah, anything's possible. Like, just by being within the open fin container, you can extend essentially extend these, these, these apps and build in extra behavior and connect them to your existing workflows. And it's all connected with, you know, intense intent driven. And you can basically drive new experiences that
190
00:35:08.390 --> 00:35:38.229
Chris Hobson: build sort of a cohesion between all of your existing applications. I like to think of. You could build. Do things like little co-pilots or chat bots things like that. They could be kind of up in the top left corner, whatever. You could basically, you know, have notepads or or things that, you know, even speaking of like generative AI, you could scan the page for important information and build a little summary for users again. You're you're just adding, enhancing, enriching the experience of all the existing apps you might have in your system. So it's a super powerful tool.
191
00:35:38.320 --> 00:35:45.399
Chris Hobson: And again, it's a way to to build that cohesion and and and flow for your users among all the existing apps that might be in your system.
192
00:35:46.260 --> 00:36:01.399
Sebastian Good: Some part of your upfront assessment. You can look at some of these tools that you may not control and figure out what are some low risk ways to use this technique to kind of integrate them more extensively into the into the workflow. So that's pretty cool.
193
00:36:03.340 --> 00:36:04.460
Sebastian Good: So
194
00:36:04.790 --> 00:36:14.030
Sebastian Good: if if we look at that, and you know, think about what is possible with ftc. 3 in. General and an open fin containers.
195
00:36:14.400 --> 00:36:42.530
Sebastian Good: let's talk a little bit about what open fin itself does. Yes, open fin container is a chrome container that lets you do those cool tricks. It is managing the Ftc 3. Implementation as far as intense and context. But one of the great things about them is, they add their own sort of user experience centralization on top of it, right with some of the features that were implied there in your demo notifications home. Maybe talk a little bit about how some of those open fin specific features have been useful to our customers.
196
00:36:42.760 --> 00:36:46.969
Thomas Holmes: Yeah. So home is an example of one of the workspace components.
197
00:36:47.884 --> 00:37:00.259
Thomas Holmes: Where, essentially, it's just a text box and a callback. But the sky's the limit. Realistically, any Api can be integrated and you bring your own content to it. So companies have used it to allow users
198
00:37:00.610 --> 00:37:09.299
Thomas Holmes: in one user face to search for customers. Contact securities, quotes, applications, workflows to launch.
199
00:37:09.550 --> 00:37:33.180
Thomas Holmes: And you know, you can create your own commands that go along with that. So you could make. You know your own kind of language where you type slash trade and symbol, and that would actually execute some kind of command in the background as opposed to just searching for something some bit of information. So it it's really powerful. And what you're allowed to do
200
00:37:33.587 --> 00:37:45.712
Thomas Holmes: and like, I said, you bring your own content to it. And W. One of the important things that allow you to make like a really smooth experience is, if you let's say there are 10 different backend services. Do you actually, wanna pull information from
201
00:37:45.970 --> 00:38:09.040
Thomas Holmes: you can load the information into home and update the results progressively. So it's not some you know, some giant. Wait where you're waiting for the slowest call to come back. You can actually progressively show stuff which leads to a smooth experience, and with that said, I would say, one little tip is to use d bounce right, because you don't need to be slamming your services on every single input that the user does.
202
00:38:10.840 --> 00:38:18.620
Sebastian Good: This. Yeah, I've seen a lot of interesting uses of home where I can look up everything from yeah securities to quotes to to contacts, and
203
00:38:18.780 --> 00:38:34.479
Sebastian Good: that could be very powerful or very overwhelming. So it's a similar sort of double edged sword. Think about the experience you're trying to give to your customers. What else, Chris? Any thoughts on open Fin Workspace? You know features that you find interesting.
204
00:38:35.080 --> 00:38:47.520
Chris Hobson: Well as in the demo I gave, you know. It started off with the the notification that came up and notification centers. It's very popular. It's huge. It's a you gotta remember, it's kind of always on in the background, right? So it's
205
00:38:48.088 --> 00:39:09.279
Chris Hobson: it's a way to to a single location to surface multiple events or notifications that can fire from any app that you have in your system at once. That's not just like simple toast messages. I mean, what you can do with notifications are pretty elaborate. You can have input boxes or dialog fields, you can, you know, basically get responses from people. So there's a little bit of a workflow going on there
206
00:39:09.310 --> 00:39:10.160
Chris Hobson: right?
207
00:39:10.240 --> 00:39:17.230
Chris Hobson: But the key thing to focus on is that you know it's it's it's a display surface right?
208
00:39:17.540 --> 00:39:36.270
Chris Hobson: What a lot of people want is, you know, stuff that requires real time, alerting, triggering, and sort of the back end service to handle your your, your alerts and a tasks through the throughout the day. So let's say you, you know you show up in the morning. You basically want a to do list of things. Oh, who do I got a call today? Right?
209
00:39:36.270 --> 00:40:00.649
Chris Hobson: So a lot of those systems still need to be in place. A lot of those services need to be built in order to to be the to basically invoke those notifications. And then, Re, you know, get that input back from when your users actually submit stuff from notifications. So there's you think of notification center kind of the tip of the iceberg. And you need to have that orchestration layer below it which we've helped a lot of teams do, by the way, so.
210
00:40:03.670 --> 00:40:28.720
Sebastian Good: That makes sense, I mean, we run into this like in our fraud investigations. Right? I I find an alert that suggests a potential bad behavior or bad account opening. And I wanna pass that on to someone, and they need to look at it. They've got a high graded list of things they're looking at. They may pass it back to me. And that notification center is a great place to do that work. But someone has to be on in the back end of it orchestrating that, and and communicating with it.
211
00:40:29.178 --> 00:40:36.180
Sebastian Good: What kind of gotchas do we run into when we deploy this in into an enterprise situation.
212
00:40:36.600 --> 00:40:41.290
Thomas Holmes: Yeah. So the biggest one that happens a lot is
213
00:40:41.680 --> 00:40:52.239
Thomas Holmes: openfin is built on chromium and chromium is not chrome. So the the classic is, it works? It works in chrome. Why isn't it work in open fin?
214
00:40:52.240 --> 00:41:16.049
Thomas Holmes: So it's not exactly the same thing. Open fin deals with chromium and updating the Runtime, and making sure it's up to date with security. But the features aren't necessarily implemented the same way. So it's important to be aware that your firm can configure security options like allowed Urls or web Apis or audio and video recording permissions. But if you have policies for existing browsers.
215
00:41:16.050 --> 00:41:22.770
Thomas Holmes: it's not necessarily going to be applied. Actually, it won't be applied to your open fin chrome instance
216
00:41:22.770 --> 00:41:48.949
Thomas Holmes: or chromium instance. So things like defaults for auto complete might function differently. Opening windows and closing windows might be a little bit different within open fin. There's no your address, bar. There's no forward and back buttons, but that's because it's building a desktop experience where your websites are actually applications, right? Those things could be turned on or added, or that experience could be massaged into it. But that is a little something extra that you need to do.
217
00:41:49.250 --> 00:42:13.910
Sebastian Good: That makes sense. I know open fin spends a lot of time making sure that the version of chromium they ship is up to date from a features and security perspective. In fact, that's one of the best things about using it is that you are getting an extremely secure environment. But, indeed, from a from a policy perspective, right? An auto complete that works in one place and not in the other place, might be really surprising. To some customers right so from an enterprise perspective, you have to make sure you.
218
00:42:13.910 --> 00:42:21.969
Sebastian Good: the people who are managing the open fin deployment are on board with those enterprise policies. That makes a lot of sense. Chris, how about you.
219
00:42:22.680 --> 00:42:27.105
Chris Hobson: Yeah, well, this sort of goes back to stuff that that Andy was talking about.
220
00:42:27.720 --> 00:42:49.670
Chris Hobson: you know, like a lot of what we do is just total integration. Right? So like you're, you might be integrating 5, or, as we see in the screenshot here, like, you know, 4 different sources of information of data. And these are all Apis that need access right? And so sometimes it's hard to gain that access from a third party. Api, especially if it the that Api is managed by a third party team or a vendor. So
221
00:42:49.670 --> 00:42:57.730
Chris Hobson: you like, Andy said, getting that upfront, knowing that we need to do. Get this access, you know, starting that access early is generally the best way to solve that.
222
00:42:57.840 --> 00:42:58.530
Chris Hobson: But.
223
00:43:00.020 --> 00:43:03.291
Sebastian Good: Excellent. And now I'm gonna demand another
224
00:43:04.110 --> 00:43:12.869
Sebastian Good: break, because for some reason, my, what's coming next slide was not finished. I don't know what asshole didn't finish it in time. Who thought he had. So give me a
225
00:43:13.010 --> 00:43:14.950
Sebastian Good: me 1 min to finish this
226
00:43:15.160 --> 00:43:19.049
Sebastian Good: one of the things we're talking about here. We've got open fin anywhere, right?
227
00:43:19.310 --> 00:43:21.789
Sebastian Good: Is it called Interop anywhere or open fin anywhere?
228
00:43:22.050 --> 00:43:22.770
Chris Hobson: Interrupt.
229
00:43:22.770 --> 00:43:24.030
Thomas Holmes: Interrupt anywhere.
230
00:43:25.980 --> 00:43:28.269
Sebastian Good: Interrupt. It used to be called Open fin anywhere.
231
00:43:29.490 --> 00:43:34.659
Thomas Holmes: Yeah, they have a bunch of different terms that are all kind of the same thing.
232
00:43:35.410 --> 00:43:36.630
Sebastian Good: Else that's cool.
233
00:43:36.890 --> 00:43:37.580
Thomas Holmes: Yeah.
234
00:43:41.040 --> 00:43:42.110
Sebastian Good: Anywhere.
235
00:43:43.980 --> 00:43:45.963
Chris Hobson: As we're talking here, Laura.
236
00:43:47.020 --> 00:43:50.090
Chris Hobson: I might want to try re-recording my whole demo thing. I'll do that. But.
237
00:43:50.090 --> 00:43:52.660
Sebastian Good: Oh, it was fantastic! You don't have to re-record it.
238
00:43:52.660 --> 00:43:55.539
Chris Hobson: I wanna do another one, and you guys can then decide what's better.
239
00:43:56.400 --> 00:43:57.940
Sebastian Good: I thought you did. Great.
240
00:43:58.180 --> 00:44:02.369
Chris Hobson: Yeah, well, I'll just do another one quick after we get off this call, and I'll send it to you guys.
241
00:44:03.805 --> 00:44:04.220
'kay.
242
00:44:04.220 --> 00:44:07.220
Chris Hobson: It's easy to do right, cause there's no there was no interaction or anything.
243
00:44:07.780 --> 00:44:09.979
Thomas Holmes: Yeah, you just run through it. There's no back and forth.
244
00:44:13.920 --> 00:44:18.239
Sebastian Good: Okay. So let's return to this.
245
00:44:18.670 --> 00:44:21.199
Sebastian Good: That's a beautiful thing about doing ahead of time.
246
00:44:25.570 --> 00:44:27.350
Sebastian Good: Gone video
247
00:44:27.670 --> 00:44:29.110
Sebastian Good: videos.
248
00:44:32.090 --> 00:44:36.559
Sebastian Good: What if you just can't? I've had multiple videos playing back at the same time.
249
00:44:37.530 --> 00:44:40.369
Sebastian Good: Really, unclear, why, it's not showing 20, months.
250
00:44:41.090 --> 00:44:42.139
Sebastian Good: Give me a minute.
251
00:44:46.610 --> 00:44:57.380
Thomas Holmes: I mean, the interrupt anywhere is not really a video that needs to be played. There's nothing to. It's just marketing like arrows drawing to each other. Right? So, wanted, yeah.
252
00:44:57.380 --> 00:45:02.030
Sebastian Good: Welcome to a demonstration. How explosing I explore. Jet pack.
253
00:45:02.470 --> 00:45:03.590
Sebastian Good: Oh, my God!
254
00:45:03.800 --> 00:45:06.765
Sebastian Good: Some AI generated voice. That's awful.
255
00:45:08.950 --> 00:45:10.660
Sebastian Good: center view.
256
00:45:18.970 --> 00:45:22.460
Sebastian Good: Okay, that is showing, okay, that works good enough.
257
00:45:27.210 --> 00:45:28.290
Sebastian Good: Share it.
258
00:45:43.500 --> 00:45:44.350
Sebastian Good: Alright.
259
00:45:45.670 --> 00:45:53.480
Sebastian Good: So with that, let's talk a little bit about what is coming next into that ecosystem. Chris, any thoughts on some of the features that are coming soon.
260
00:45:53.900 --> 00:46:05.120
Chris Hobson: Yeah, so interrupt anywhere is super exciting. And it's, you know, it's really a web socket web. Rtc type solution, where you can basically do the same. Ftc. 3 stuff, but not
261
00:46:05.150 --> 00:46:19.789
Chris Hobson: restricted to being in an open fin container. So, of course, that means like your device or your your turrets on your desk, but it also just means like being in the web like a standard browser. You could use the same Apis to communicate among all these devices
262
00:46:20.087 --> 00:46:39.100
Chris Hobson: different places. Not only different device, your devices, but potentially other team members across. You know the world right? So I think of things just like in in my demo like, Oh, you could actually make a phone call, and then on your you know your desktop. You could see all your the contact information of the person you're talking to. Pop up.
263
00:46:39.333 --> 00:46:55.689
Chris Hobson: You know, again, things like you. You're working in a team, and you need to manage a task together, and you could see, oh, like so and so updated the status of this task. And it they sent it over to me with through all through the Ftc 3 spec. Which is very standardized. So again, interrupt anywhere, I'm pretty excited about what we're gonna see coming out of that.
264
00:46:57.305 --> 00:46:59.619
Sebastian Good: Thomas? How about open Fin Cloud?
265
00:47:00.260 --> 00:47:05.339
Thomas Holmes: Yeah, so open fin is building and hosting their own workspace. And
266
00:47:05.640 --> 00:47:14.949
Thomas Holmes: it essentially, you'll be able to, Bill, you know. Use it as your own with some configuration. But what we're excited about is the fact that
267
00:47:15.010 --> 00:47:39.339
Thomas Holmes: normally, when we build a workspace platform or anything with open fin, there's like a large lot of. There's a large amount of boilerplate that we have to run through every time, and that's gonna be abstracted away, and they're gonna be hosting that and maintaining it, which is nice because it's gonna be standardized. And then it's going to allow us to really focus on the unique and interesting problems that are specific to our clients and the workflows that they wanna solve for.
268
00:47:41.470 --> 00:48:07.630
Sebastian Good: That makes sense. Yeah, I mean a lot of the reason for that historically, was security, right? Having everything on premise at the bank and as embrace the cloud. You know the ability for a vendor like open fent to have sort of a cloud standard vetted, secure offering. Yeah, it's just take the chunk of money you were gonna spend on that and spend it on something interesting instead. I'm I'm super excited about this as well. I'm excited about the interop anywhere, too. Just because.
269
00:48:07.913 --> 00:48:32.620
Sebastian Good: we've so far been focusing on productivity on a single desktop, which is huge. But you know, a lot of important flows in this industry are are between multiple users, between a portfolio manager and a trader or a a wealth advisor and and an analyst that's helping implement. So I'm excited to see where that's gonna go. I know one thing I wanted to mention that we're certainly working on is the ability for AI assistance to participate on the desktop.
270
00:48:32.948 --> 00:49:00.530
Sebastian Good: I think an environment like open fin is uniquely useful there in that. You can have an AI assistant not just having a conversation with you and potentially helping you browse ideas and data, but actually orchestrating workspaces so that we can accomplish certain tasks right? Some tasks that you don't execute very often, or that are highly complex are difficult to make effective as users require training, or, you know, don't do it often enough to remember how it works.
271
00:49:00.530 --> 00:49:12.840
Sebastian Good: and an assistant that can bring together, say, 4 or 5 applications required to do a complex, you know, transfer or rebalancing operation, or something, and wealth, as you might imagine, could be very powerful. Hoping to talk about that
272
00:49:13.454 --> 00:49:23.295
Sebastian Good: in our next webinar. So what I wanna say guys is, thanks everyone for the great tour of bumps and bruises and opportunities.
273
00:49:24.100 --> 00:49:47.920
Sebastian Good: wanna close out with just some closing thoughts. I guess I'll offer one of my own, which is that this presentation has been a great reminder to consider the growing power of that ecosystem itself everywhere. You heard us say, you could integrate this or integrate that, or augment this so all components that are potentially available. Not just inside your firm, but across a pretty large vendor community. Like, I said, you can join finos
274
00:49:47.920 --> 00:50:00.140
Sebastian Good: to affect the future of Ftc, 3 and actually open fin themselves are a great corporate partner at creating movement in that ecosystem, and working tirelessly to get more and more vendors. Big vendors on board with that each passing month.
275
00:50:00.460 --> 00:50:04.630
Sebastian Good: But let's just closing thoughts go around the table here. Thomas.
276
00:50:05.050 --> 00:50:06.130
Thomas Holmes: Sure. So
277
00:50:06.290 --> 00:50:30.450
Thomas Holmes: ftc, 3 and open are very powerful tools. You need to be thoughtful and intentional when planning your platform, because you can make a sluggish platform with a terrible user experience that at that gets 0 adoption. Or you can make a game changing application for your firm with beautiful workflows that empower users, where people will complain that they're actually not on the first wave of the rollout.
278
00:50:30.670 --> 00:50:34.100
Thomas Holmes: So the power is in your hands. But you need to know what you're doing.
279
00:50:35.220 --> 00:50:37.860
Sebastian Good: And love it. Wow! Humbling Chris.
280
00:50:38.840 --> 00:50:51.859
Chris Hobson: Yeah. Well, I'd say there's a lot of power here in the notion of you. Don't have to throw everything out all at once right? I mean, if you want to modernize your systems, start where you're at, you know you can
281
00:50:52.204 --> 00:51:05.419
Chris Hobson: use openfin and ftc, 3 as a migration path. To take legacy applications into the future. Keep what you got, add new stuff to it, and together. Between all of that, you can build a great experience for your users.
282
00:51:07.075 --> 00:51:07.559
Sebastian Good: Andy!
283
00:51:08.260 --> 00:51:16.699
Andy Nicholls: Yeah, kinda reinforcing what Thomas and Chris is saying really is, stop, start simple plan ahead of time.
284
00:51:16.780 --> 00:51:23.769
Andy Nicholls: and especially spend invest that time upfront to understand your data sources and access
285
00:51:23.810 --> 00:51:27.529
Andy Nicholls: and what you're gonna need to use. I think that's absolutely critical.
286
00:51:28.770 --> 00:51:52.499
Sebastian Good: Awesome. Well, cool. Thanks, everyone for joining today. And thank you guys for your contributions. Looking forward to seeing more people next month at our next event, where we'll get a little deeper into some of those future developments, including, on how we think generative. AI plays a role inside the complex decision experiences. We're we're putting together in these markets. Thanks again.
