WEBVTT
00:00:12.000 --> 00:00:12.960
Welcome everyone.
00:00:13.759 --> 00:00:15.119
So happy to have everybody here today.
00:00:15.199 --> 00:00:19.600
And here at MeshIQ, I wanted to say we focus on the integrity of the messaging backbone.
00:00:19.679 --> 00:00:28.480
And today we are excited for our discussion with IBM, a leader in the broadest portfolio and the deepest expertise in B2B EDI and MFT managed file transfer.
00:00:28.800 --> 00:00:32.560
In this session, we will discuss mastering end-to-end B2B flow intelligence.
00:00:32.640 --> 00:00:36.880
But before we get into it, with our guests and our introductions, I'd like to set the stage for this session.
00:00:37.439 --> 00:00:47.840
Today, modern commerce requires millions of critical business transactions, from purchase purchase orders to invoices to payments and claims to complete seamlessly across your messaging backbone.
00:00:48.719 --> 00:00:59.759
Just as a customer expects real-time tracking for critical delivery, your organization needs guaranteed, verifiable end-to-end assurance that every business event reaches its destination on time and in full.
00:01:00.320 --> 00:01:02.719
So thanks for joining us and let's meet our guests.
00:01:03.359 --> 00:01:08.879
We are thrilled to have Janine Calandra, IBM's product leader for B2B and MFT, joining us from DC.
00:01:08.959 --> 00:01:09.920
Welcome, Janine.
00:01:10.079 --> 00:01:14.879
And joining us from SIQ, all the way from Sao Paulo, Brazil, is Nabdeep Sedou, our CEO.
00:01:15.120 --> 00:01:25.599
Nabdeep brings 15 years of deep B2B and MFT experience, including his time as a product manager for Sterling Integrator and his 12-year tenure with Web Methods, where he launched Active Transfer.
00:01:26.400 --> 00:01:30.480
So now we are firmly in an AI-driven world.
00:01:30.719 --> 00:01:35.680
Today we are exploring how B2B and MFT are evolving to meet these new demands.
00:01:36.159 --> 00:01:37.840
Jamine, I'd like to start with you.
00:01:38.159 --> 00:01:44.799
Can we talk a little bit about how IBM solutions and capabilities and how they enable billions of commerce transactions?
00:01:45.840 --> 00:01:46.560
Absolutely.
00:01:46.719 --> 00:01:53.439
So B2B integration and managed file transfer, I view them as essentially the backbone for global commerce.
00:01:53.680 --> 00:01:56.640
So as you mentioned, billions of transactions.
00:01:56.959 --> 00:02:06.719
We process billions of mission critical documents and files that go through IBM's portfolio of B2B integration and file transfer solutions.
00:02:06.879 --> 00:02:13.039
So these are all different document types, formats, all things that drive business for our customers.
00:02:13.199 --> 00:02:21.520
So think crucial purchase orders, invoices, payments, and IBM is processing these continuously.
00:02:21.680 --> 00:02:29.759
So every hour of every day across various industries, ranging from retail to financial services to healthcare.
00:02:30.000 --> 00:02:36.639
And for our customers, it's not just about the connectivity and the processing, but it's about trust.
00:02:36.800 --> 00:02:43.520
So trust that every transaction is delivered securely, completely, and on time.
00:02:43.759 --> 00:02:49.680
And IBM is an essential part of providing this trusted foundation for our customers.
00:02:49.759 --> 00:02:52.159
So we offer flexible deployment options.
00:02:52.240 --> 00:03:04.479
And whether those customers are on premises, in the cloud, or across both in a hybrid manner, it's all about the speed, the reliability, and the security being the forefront for our solutions.
00:03:06.560 --> 00:03:07.680
Thank you so much, Dean.
00:03:07.759 --> 00:03:08.080
Appreciate it.
00:03:08.159 --> 00:03:09.520
Nancy, over to you though.
00:03:09.759 --> 00:03:15.360
What are you noticing in the B2B, EDI, MFT world from you know Mesh IQ's perspective?
00:03:16.080 --> 00:03:22.240
Yeah, let me start off by saying that IBM has the market leading platforms for B2B and MFT.
00:03:22.319 --> 00:03:28.479
And as Janine said, they are the backbone for EDAI and file transfers for large companies globally.
00:03:29.680 --> 00:03:35.439
And I would say the B2B and the MFT landscape has become more complex.
00:03:35.520 --> 00:03:43.840
And the reason I say that, we have noticed in the last decade or so, the enterprise boundaries now extend to the cloud.
00:03:44.000 --> 00:03:52.159
The file transfers, which used to happen between two partners or between two internal applications, are now extending to the cloud.
00:03:52.319 --> 00:04:02.639
And whether you're moving the files to the S3 buckets or sending data to Snowflake or Databricks, the boundaries have just expanded and the infrastructure has become more complex.
00:04:02.800 --> 00:04:05.599
So similarly, B2B integration has also evolved.
00:04:05.680 --> 00:04:12.000
And now IPaaS platforms like WebMethods Hyber Integration, they're processing EDI documents in the cloud.
00:04:12.240 --> 00:04:22.639
So not only you have the on-prem gateways, you have the IPaaS platforms, you have cloud storage, you have cloud data warehouses, you have data lake houses, in addition to the legacy EDI vans.
00:04:23.120 --> 00:04:40.000
So the transaction boundaries have expanded, and the typical visibility is not able to deliver the transaction flow level intelligence anymore because these flows have become much more complex, and there are too many failure points in those flows.
00:04:41.920 --> 00:04:42.480
Wonderful.
00:04:42.639 --> 00:04:44.800
Thank you so much for your insights there, Dev.
00:04:45.040 --> 00:04:49.839
I'd like to hop over, if we can, to talking about innovation and modernization strategies.
00:04:50.079 --> 00:04:58.879
Jeanine, what are the new or even upcoming innovations for IBM that you'd like to highlight, particularly regarding AI and those cloud native shifts?
00:04:59.519 --> 00:04:59.920
Sure.
00:05:00.160 --> 00:05:14.079
So a couple of things we hear from customers all the time is they need to modernize, they want to modernize, but they don't want to disrupt what's already working, as these environments are just very deeply embedded into their business processes.
00:05:14.399 --> 00:05:19.439
So what we are focused on is modernization for customers without disruption.
00:05:19.600 --> 00:05:25.839
And that's something really our IPHS platform, the Web Methods Hybrid Integration Solution, excels at.
00:05:26.000 --> 00:05:29.360
So there's a couple of key areas where we help here.
00:05:29.519 --> 00:05:31.439
So first, hybrid by design.
00:05:31.519 --> 00:05:38.639
So giving customers like flexibility, that's just not just to run one model, but to run what works for their business.
00:05:38.720 --> 00:05:43.040
So whether that be on-prem, cloud, SaaS, they can evolve at their own pace.
00:05:43.279 --> 00:05:56.079
And bringing together these different integration patterns across capability, so the B2B integration, it's managed file transfer, whether it's app integration, APIs, events, et cetera, into a unified experience.
00:05:56.560 --> 00:06:02.639
Really seeing these as no longer separate domains, but more of a unified platform and solution.
00:06:02.879 --> 00:06:16.720
And as we continue to expand this beyond web methods, IBM has a broad set of really powerful integration solutions ranging from things like IBM API Connect to Sterling to MQ.
00:06:17.040 --> 00:06:23.519
We're really focused on adding these integrations that add value to customers into a more holistic, unified experience.
00:06:23.759 --> 00:06:28.959
So you also mentioned AI, which is critical to our overall mission for this platform.
00:06:29.120 --> 00:06:38.160
And we are the one of the biggest pain points, this like full stop that I hear from our B2B customers or prospects in general, is around onboarding.
00:06:38.399 --> 00:06:43.199
So all the time customers talk about it just takes too long to onboard.
00:06:43.279 --> 00:06:45.519
Now, Deep talked about that complexity.
00:06:45.680 --> 00:07:00.560
And this is really key here because the complexity in this area has just been increasing exponentially because organizations are just doing business with a broader set of partners and they have a broader set of requirements and more integration patterns to support.
00:07:00.800 --> 00:07:04.879
So an area of focus for us is how do we streamline this for customers?
00:07:05.040 --> 00:07:16.240
So we've introduced, for example, a B2B agent as part of the Web Methods B2B solution to speed that process and make it easier for customers to transact with key trading partners more quickly.
00:07:16.399 --> 00:07:19.120
And there's been really positive responses to that.
00:07:19.199 --> 00:07:20.959
So we're going to continue to evolve it.
00:07:21.040 --> 00:07:28.879
So another request we hear around that complexity is with reducing the effort of managing partner certificates and how AI can help in these areas.
00:07:28.959 --> 00:07:31.680
So that's a focus point moving forward for us.
00:07:32.240 --> 00:07:33.040
Very interesting.
00:07:33.199 --> 00:07:34.240
Thank you so much, Janine.
00:07:34.399 --> 00:07:39.279
And Natib, how are you seeing companies modernize their B2B or MFT stacks?
00:07:40.160 --> 00:07:42.879
Yeah, a great question there, Mike.
00:07:43.120 --> 00:07:51.759
The companies across the board, they always take a very careful approach to modernize B2B and MFT infrastructure because it is mission critical.
00:07:51.920 --> 00:07:59.439
And any failure for a minute, for 10 minutes, or even for an hour, it will directly impact the top line and the bottom line.
00:07:59.680 --> 00:08:02.240
In finance, there are clear penalties.
00:08:02.399 --> 00:08:11.519
For example, a bank may pay millions in penalties for delayed SWIFT transactions if the money is not moved across geographies, across borders in time.
00:08:12.079 --> 00:08:20.560
And similarly, a retail company may lose customers' orders if the system cannot apply a customer's coupon while the customer is in the store.
00:08:20.720 --> 00:08:27.680
So the use cases differ across industries, but the fact that B2B and MFT is mission critical stays the same.
00:08:27.920 --> 00:08:40.639
And due to the fact the use cases are different, the modernization strategy is slightly different across the industries, but it is always centered around minimizing impact to the core business processes.
00:08:40.960 --> 00:08:46.399
So financial organizations, for example, they focus on risk reduction and compliance.
00:08:46.639 --> 00:08:55.120
And while the retail organizations they have a laser sharp focus on cost per transaction and they want to scale while staying lean.
00:08:55.440 --> 00:09:02.320
So across the industries, some aspects like auditability and compliance, they apply to every industry.
00:09:02.799 --> 00:09:08.320
But overall, depending upon the industry segment, we see different modernization strategies and goals.
00:09:09.759 --> 00:09:10.240
Interesting.
00:09:10.399 --> 00:09:14.480
Yeah, I can really see that that varies depending on the industry.
00:09:14.720 --> 00:09:20.399
So I think I'd like to move to our last topic for the day and really talk about bridging that visibility gap that we see.
00:09:20.799 --> 00:09:25.200
Janine, IBM has you know has an incredibly vast spectrum of products.
00:09:25.360 --> 00:09:31.360
You know, how does IBM deliver visibility across that that entire spectrum for a business user?
00:09:31.519 --> 00:09:50.879
Um and to follow up, if if an organization realizes today that their current support model is too reactive, waiting for a partner to call and complain, what are the first steps that they should take to build a more proactive governance framework that scales without adding a massive amount of manual overhead to the IT teams there?
00:09:51.519 --> 00:09:52.480
Good question.
00:09:52.639 --> 00:09:55.279
Uh so I echo what you're saying.
00:09:55.440 --> 00:09:59.360
This is a very common customer challenge just around visibility in general.
00:09:59.519 --> 00:10:16.799
So I'll often hear about the need to extend visibility beyond one area, such as beyond like a system-focused type of monitoring type of model, into something more proactive and end-to-end that has uh visibility into business processes.
00:10:17.039 --> 00:10:26.480
Another area I hear often about is empowering line of business users to avoid things like IT bottlenecks that where people are waiting on information.
00:10:26.720 --> 00:10:40.000
So customers really need to understand what's happening across their flows, their partners' transactions, all of those things, and be able to head off issues quickly and optimize their operations.
00:10:40.240 --> 00:10:45.919
So they want to do that, and they also want to empower business users with this information very quickly.
00:10:46.240 --> 00:10:56.080
So a few ways IBM is working on serving and providing this type of visibility within the iPads platform, the Web Methods Hybrid Integration.
00:10:56.240 --> 00:11:01.440
We are continuing to add AI capability there to help with these types of things and evolve it.
00:11:01.600 --> 00:11:07.039
So there's end-to-end visibility across the multiple capabilities of the platform, for example.
00:11:07.279 --> 00:11:11.519
And we now have some built-in observability agents that work cross capabilities.
00:11:11.679 --> 00:11:19.360
So these new agents like aid customers in identifying and resolving issues quickly, regardless of where they are in the flow.
00:11:19.519 --> 00:11:21.840
So a big value out of the platform.
00:11:22.240 --> 00:11:26.960
We've also focused on adding more business user-friendly type of views.
00:11:27.039 --> 00:11:38.480
So everyone doesn't need to speak EDI, so to speak, or be an expert in those types of things by having more easy to understand, say human readable and role-based appropriate access.
00:11:39.440 --> 00:11:46.320
Also, like taking into consideration customers operate in different models, as Navdeep was saying.
00:11:46.399 --> 00:11:53.120
So they can be hybrid, they may have different geos, different deployments, a mix of various solutions within IBM.
00:11:53.200 --> 00:11:56.639
And they really do need holistic views of all of these things.
00:11:56.799 --> 00:12:09.120
So I definitely see strong value in a solution bringing these types of transactions all together in one spot and helping customers proactively identify these types of bottlenecks across their entire ecosystem.
00:12:09.679 --> 00:12:10.879
Makes total sense.
00:12:11.200 --> 00:12:14.240
Nev, you know, before we wrap this up, I'd love to get your read on this.
00:12:14.320 --> 00:12:23.279
You know, how does MeshIQ specifically, you know, B2B in the flow intelligence layer onto this, you know, provide that end-to-end assurance?
00:12:24.320 --> 00:12:30.879
Yeah, so you know, the transaction boundaries keep expanding from partner onboarding to AI agents.
00:12:31.120 --> 00:12:41.519
And as the transaction boundaries have increased for B2B EDI and MFT transactions, um, the flow intelligence into the complete flow has become extremely important.
00:12:41.759 --> 00:13:01.120
And mesh IQ, B2B and Flow Intelligence uh sorry, Mesh IQ, B2B and MFT flow intelligence taps into 40 plus data points like APIs, uh files, MQ, IBM MQ, Kafka, Webhooks, etc., to gather the relevant metrics into the transaction flow.
00:13:01.519 --> 00:13:06.720
So transaction could be stalled, slowing down, or totally failed.
00:13:07.200 --> 00:13:10.960
So our goal from B2B and MFT flow intelligence is very simple.
00:13:11.200 --> 00:13:14.080
Detect bottlenecks before they become outages.
00:13:14.320 --> 00:13:32.240
So we can look across IBM Sterling integrator, Sterling File Gateway, Web Methods Active Transfer, Web Methods Trading Networks, and every other IBM and non-IBM technology which is involved in the overall transaction flow to monitor the complete end-to-end transaction flow.
00:13:32.480 --> 00:13:55.279
And by correlating these transactions and by adding the layering on the proper context on top of these data points, each transaction flow can be analyzed for SLA violations and we can diagnose the slowdowns, whether it could be due to an expiring or expired certificate, uh slowing down network or even storage outages.
00:13:55.360 --> 00:14:04.559
If the storage is full and the MFT transactions are failing, and we can detect issues at the network layer and even at the OS layer.
00:14:04.720 --> 00:14:13.919
So that gives you a complete picture on why these mission critical B2B and MFT transactions are slowing down or failing.
00:14:14.159 --> 00:14:25.600
We deliver the end-to-end visibility across each step in the transaction, not just the visibility on top of the B2B gateway, because most of the problems they happen downstream from the B2B and MFT gateway.
00:14:26.639 --> 00:14:27.279
Makes sense.
00:14:27.519 --> 00:14:27.919
Love it.
00:14:28.000 --> 00:14:29.200
Thank you for the insights, Nev.
00:14:29.279 --> 00:14:32.960
You know, I think we're about to wrap this up, but I'd love to hear your last comments.
00:14:33.120 --> 00:14:39.519
Um, you know, it seems like Mass Fream B2B isn't just an IT project, it's revenue integrity strategy.
00:14:39.759 --> 00:14:44.720
So, you know, Janine, Nev, what are your last insights to share with the team here?
00:14:47.279 --> 00:14:52.480
So I think it's about uh a bit of an evolution in B2B.
00:14:52.639 --> 00:14:58.399
Navdi uh hinted at this as well, as it becoming a bit more prominent in terms of business strategy.
00:14:58.559 --> 00:15:10.240
So I'm seeing a shift from these conversations around picking a B2B and file transfer solution evolving from just IT discussion, I think to a broader business strategy for organizations.
00:15:10.559 --> 00:15:15.919
So acknowledgement that these B2B documents, files, they're all directly tied to revenue.
00:15:16.080 --> 00:15:18.000
So every transaction matters.
00:15:18.159 --> 00:15:27.039
And if something like an order doesn't go through or a payment is delayed or rejected, then that has real monetary and business impact.
00:15:27.279 --> 00:15:36.000
So from that point of view, you know, IBM's goal is definitely to ensure that every business transaction that should generate revenue for customer does so.
00:15:36.080 --> 00:15:40.960
And it does so completely correctly and in an on-time fashion.
00:15:42.320 --> 00:15:43.039
Thank you, Janine.
00:15:43.120 --> 00:15:44.240
Nev, any last thoughts?
00:15:44.480 --> 00:15:45.919
Yeah, I completely agree.
00:15:46.000 --> 00:15:58.320
And I think uh for many industries like manufacturing, retail, finance, and even healthcare, um, I will not hesitate to say that B2B and MFT are the most critical business applications that directly impact revenue and profitability.
00:15:58.720 --> 00:16:08.639
Flow intelligence into IBM sterling and non-IBM technologies uh involved in the overall transaction flow, it should be a very high priority for every CIO.
00:16:08.799 --> 00:16:12.960
Uh and it should be on their agenda to protect and grow revenue.
00:16:13.120 --> 00:16:15.200
So I will end with two thoughts.
00:16:15.440 --> 00:16:17.840
First is modernize your B2B and MFT.
00:16:18.000 --> 00:16:25.759
Look at technologies like WebMethods IPass to process your B2B transactions in the cloud for you know MFT in the cloud.
00:16:26.000 --> 00:16:35.840
And secondly, as you modernize, develop a flow intelligence strategy, we are an IBM partner and we work closely with their teams to deliver B2B and MFT flow intelligence.
00:16:36.159 --> 00:16:38.240
Thank you both so much for the insights today.
00:16:38.399 --> 00:16:41.600
Um, I felt like I learned a lot and I hope that the viewers did as well.
00:16:41.759 --> 00:16:43.600
Um, but thank you again for joining us.
00:16:43.679 --> 00:16:57.200
And for those out there watching, if you have any questions, please reach out, but visit us at at IBM.com and meshIQ.com for more information, and we'll be surely uh be able to track down any answers you have for any questions you have.
00:16:57.360 --> 00:16:58.960
Uh but really appreciate the time.
00:16:59.120 --> 00:17:01.279
Janine, Navdeep, thank you again.
00:17:01.360 --> 00:17:03.360
And until next time, appreciate it.
00:17:03.440 --> 00:17:03.600
Thank you.
00:17:04.079 --> 00:17:04.799
Thank you.
00:00:12.000 --> 00:00:12.960
Welcome everyone.
00:00:13.759 --> 00:00:15.119
So happy to have everybody here today.
00:00:15.199 --> 00:00:19.600
And here at MeshIQ, I wanted to say we focus on the integrity of the messaging backbone.
00:00:19.679 --> 00:00:28.480
And today we are excited for our discussion with IBM, a leader in the broadest portfolio and the deepest expertise in B2B EDI and MFT managed file transfer.
00:00:28.800 --> 00:00:32.560
In this session, we will discuss mastering end-to-end B2B flow intelligence.
00:00:32.640 --> 00:00:36.880
But before we get into it, with our guests and our introductions, I'd like to set the stage for this session.
00:00:37.439 --> 00:00:47.840
Today, modern commerce requires millions of critical business transactions, from purchase purchase orders to invoices to payments and claims to complete seamlessly across your messaging backbone.
00:00:48.719 --> 00:00:59.759
Just as a customer expects real-time tracking for critical delivery, your organization needs guaranteed, verifiable end-to-end assurance that every business event reaches its destination on time and in full.
00:01:00.320 --> 00:01:02.719
So thanks for joining us and let's meet our guests.
00:01:03.359 --> 00:01:08.879
We are thrilled to have Janine Calandra, IBM's product leader for B2B and MFT, joining us from DC.
00:01:08.959 --> 00:01:09.920
Welcome, Janine.
00:01:10.079 --> 00:01:14.879
And joining us from SIQ, all the way from Sao Paulo, Brazil, is Nabdeep Sedou, our CEO.
00:01:15.120 --> 00:01:25.599
Nabdeep brings 15 years of deep B2B and MFT experience, including his time as a product manager for Sterling Integrator and his 12-year tenure with Web Methods, where he launched Active Transfer.
00:01:26.400 --> 00:01:30.480
So now we are firmly in an AI-driven world.
00:01:30.719 --> 00:01:35.680
Today we are exploring how B2B and MFT are evolving to meet these new demands.
00:01:36.159 --> 00:01:37.840
Jamine, I'd like to start with you.
00:01:38.159 --> 00:01:44.799
Can we talk a little bit about how IBM solutions and capabilities and how they enable billions of commerce transactions?
00:01:45.840 --> 00:01:46.560
Absolutely.
00:01:46.719 --> 00:01:53.439
So B2B integration and managed file transfer, I view them as essentially the backbone for global commerce.
00:01:53.680 --> 00:01:56.640
So as you mentioned, billions of transactions.
00:01:56.959 --> 00:02:06.719
We process billions of mission critical documents and files that go through IBM's portfolio of B2B integration and file transfer solutions.
00:02:06.879 --> 00:02:13.039
So these are all different document types, formats, all things that drive business for our customers.
00:02:13.199 --> 00:02:21.520
So think crucial purchase orders, invoices, payments, and IBM is processing these continuously.
00:02:21.680 --> 00:02:29.759
So every hour of every day across various industries, ranging from retail to financial services to healthcare.
00:02:30.000 --> 00:02:36.639
And for our customers, it's not just about the connectivity and the processing, but it's about trust.
00:02:36.800 --> 00:02:43.520
So trust that every transaction is delivered securely, completely, and on time.
00:02:43.759 --> 00:02:49.680
And IBM is an essential part of providing this trusted foundation for our customers.
00:02:49.759 --> 00:02:52.159
So we offer flexible deployment options.
00:02:52.240 --> 00:03:04.479
And whether those customers are on premises, in the cloud, or across both in a hybrid manner, it's all about the speed, the reliability, and the security being the forefront for our solutions.
00:03:06.560 --> 00:03:07.680
Thank you so much, Dean.
00:03:07.759 --> 00:03:08.080
Appreciate it.
00:03:08.159 --> 00:03:09.520
Nancy, over to you though.
00:03:09.759 --> 00:03:15.360
What are you noticing in the B2B, EDI, MFT world from you know Mesh IQ's perspective?
00:03:16.080 --> 00:03:22.240
Yeah, let me start off by saying that IBM has the market leading platforms for B2B and MFT.
00:03:22.319 --> 00:03:28.479
And as Janine said, they are the backbone for EDAI and file transfers for large companies globally.
00:03:29.680 --> 00:03:35.439
And I would say the B2B and the MFT landscape has become more complex.
00:03:35.520 --> 00:03:43.840
And the reason I say that, we have noticed in the last decade or so, the enterprise boundaries now extend to the cloud.
00:03:44.000 --> 00:03:52.159
The file transfers, which used to happen between two partners or between two internal applications, are now extending to the cloud.
00:03:52.319 --> 00:04:02.639
And whether you're moving the files to the S3 buckets or sending data to Snowflake or Databricks, the boundaries have just expanded and the infrastructure has become more complex.
00:04:02.800 --> 00:04:05.599
So similarly, B2B integration has also evolved.
00:04:05.680 --> 00:04:12.000
And now IPaaS platforms like WebMethods Hyber Integration, they're processing EDI documents in the cloud.
00:04:12.240 --> 00:04:22.639
So not only you have the on-prem gateways, you have the IPaaS platforms, you have cloud storage, you have cloud data warehouses, you have data lake houses, in addition to the legacy EDI vans.
00:04:23.120 --> 00:04:40.000
So the transaction boundaries have expanded, and the typical visibility is not able to deliver the transaction flow level intelligence anymore because these flows have become much more complex, and there are too many failure points in those flows.
00:04:41.920 --> 00:04:42.480
Wonderful.
00:04:42.639 --> 00:04:44.800
Thank you so much for your insights there, Dev.
00:04:45.040 --> 00:04:49.839
I'd like to hop over, if we can, to talking about innovation and modernization strategies.
00:04:50.079 --> 00:04:58.879
Jeanine, what are the new or even upcoming innovations for IBM that you'd like to highlight, particularly regarding AI and those cloud native shifts?
00:04:59.519 --> 00:04:59.920
Sure.
00:05:00.160 --> 00:05:14.079
So a couple of things we hear from customers all the time is they need to modernize, they want to modernize, but they don't want to disrupt what's already working, as these environments are just very deeply embedded into their business processes.
00:05:14.399 --> 00:05:19.439
So what we are focused on is modernization for customers without disruption.
00:05:19.600 --> 00:05:25.839
And that's something really our IPHS platform, the Web Methods Hybrid Integration Solution, excels at.
00:05:26.000 --> 00:05:29.360
So there's a couple of key areas where we help here.
00:05:29.519 --> 00:05:31.439
So first, hybrid by design.
00:05:31.519 --> 00:05:38.639
So giving customers like flexibility, that's just not just to run one model, but to run what works for their business.
00:05:38.720 --> 00:05:43.040
So whether that be on-prem, cloud, SaaS, they can evolve at their own pace.
00:05:43.279 --> 00:05:56.079
And bringing together these different integration patterns across capability, so the B2B integration, it's managed file transfer, whether it's app integration, APIs, events, et cetera, into a unified experience.
00:05:56.560 --> 00:06:02.639
Really seeing these as no longer separate domains, but more of a unified platform and solution.
00:06:02.879 --> 00:06:16.720
And as we continue to expand this beyond web methods, IBM has a broad set of really powerful integration solutions ranging from things like IBM API Connect to Sterling to MQ.
00:06:17.040 --> 00:06:23.519
We're really focused on adding these integrations that add value to customers into a more holistic, unified experience.
00:06:23.759 --> 00:06:28.959
So you also mentioned AI, which is critical to our overall mission for this platform.
00:06:29.120 --> 00:06:38.160
And we are the one of the biggest pain points, this like full stop that I hear from our B2B customers or prospects in general, is around onboarding.
00:06:38.399 --> 00:06:43.199
So all the time customers talk about it just takes too long to onboard.
00:06:43.279 --> 00:06:45.519
Now, Deep talked about that complexity.
00:06:45.680 --> 00:07:00.560
And this is really key here because the complexity in this area has just been increasing exponentially because organizations are just doing business with a broader set of partners and they have a broader set of requirements and more integration patterns to support.
00:07:00.800 --> 00:07:04.879
So an area of focus for us is how do we streamline this for customers?
00:07:05.040 --> 00:07:16.240
So we've introduced, for example, a B2B agent as part of the Web Methods B2B solution to speed that process and make it easier for customers to transact with key trading partners more quickly.
00:07:16.399 --> 00:07:19.120
And there's been really positive responses to that.
00:07:19.199 --> 00:07:20.959
So we're going to continue to evolve it.
00:07:21.040 --> 00:07:28.879
So another request we hear around that complexity is with reducing the effort of managing partner certificates and how AI can help in these areas.
00:07:28.959 --> 00:07:31.680
So that's a focus point moving forward for us.
00:07:32.240 --> 00:07:33.040
Very interesting.
00:07:33.199 --> 00:07:34.240
Thank you so much, Janine.
00:07:34.399 --> 00:07:39.279
And Natib, how are you seeing companies modernize their B2B or MFT stacks?
00:07:40.160 --> 00:07:42.879
Yeah, a great question there, Mike.
00:07:43.120 --> 00:07:51.759
The companies across the board, they always take a very careful approach to modernize B2B and MFT infrastructure because it is mission critical.
00:07:51.920 --> 00:07:59.439
And any failure for a minute, for 10 minutes, or even for an hour, it will directly impact the top line and the bottom line.
00:07:59.680 --> 00:08:02.240
In finance, there are clear penalties.
00:08:02.399 --> 00:08:11.519
For example, a bank may pay millions in penalties for delayed SWIFT transactions if the money is not moved across geographies, across borders in time.
00:08:12.079 --> 00:08:20.560
And similarly, a retail company may lose customers' orders if the system cannot apply a customer's coupon while the customer is in the store.
00:08:20.720 --> 00:08:27.680
So the use cases differ across industries, but the fact that B2B and MFT is mission critical stays the same.
00:08:27.920 --> 00:08:40.639
And due to the fact the use cases are different, the modernization strategy is slightly different across the industries, but it is always centered around minimizing impact to the core business processes.
00:08:40.960 --> 00:08:46.399
So financial organizations, for example, they focus on risk reduction and compliance.
00:08:46.639 --> 00:08:55.120
And while the retail organizations they have a laser sharp focus on cost per transaction and they want to scale while staying lean.
00:08:55.440 --> 00:09:02.320
So across the industries, some aspects like auditability and compliance, they apply to every industry.
00:09:02.799 --> 00:09:08.320
But overall, depending upon the industry segment, we see different modernization strategies and goals.
00:09:09.759 --> 00:09:10.240
Interesting.
00:09:10.399 --> 00:09:14.480
Yeah, I can really see that that varies depending on the industry.
00:09:14.720 --> 00:09:20.399
So I think I'd like to move to our last topic for the day and really talk about bridging that visibility gap that we see.
00:09:20.799 --> 00:09:25.200
Janine, IBM has you know has an incredibly vast spectrum of products.
00:09:25.360 --> 00:09:31.360
You know, how does IBM deliver visibility across that that entire spectrum for a business user?
00:09:31.519 --> 00:09:50.879
Um and to follow up, if if an organization realizes today that their current support model is too reactive, waiting for a partner to call and complain, what are the first steps that they should take to build a more proactive governance framework that scales without adding a massive amount of manual overhead to the IT teams there?
00:09:51.519 --> 00:09:52.480
Good question.
00:09:52.639 --> 00:09:55.279
Uh so I echo what you're saying.
00:09:55.440 --> 00:09:59.360
This is a very common customer challenge just around visibility in general.
00:09:59.519 --> 00:10:16.799
So I'll often hear about the need to extend visibility beyond one area, such as beyond like a system-focused type of monitoring type of model, into something more proactive and end-to-end that has uh visibility into business processes.
00:10:17.039 --> 00:10:26.480
Another area I hear often about is empowering line of business users to avoid things like IT bottlenecks that where people are waiting on information.
00:10:26.720 --> 00:10:40.000
So customers really need to understand what's happening across their flows, their partners' transactions, all of those things, and be able to head off issues quickly and optimize their operations.
00:10:40.240 --> 00:10:45.919
So they want to do that, and they also want to empower business users with this information very quickly.
00:10:46.240 --> 00:10:56.080
So a few ways IBM is working on serving and providing this type of visibility within the iPads platform, the Web Methods Hybrid Integration.
00:10:56.240 --> 00:11:01.440
We are continuing to add AI capability there to help with these types of things and evolve it.
00:11:01.600 --> 00:11:07.039
So there's end-to-end visibility across the multiple capabilities of the platform, for example.
00:11:07.279 --> 00:11:11.519
And we now have some built-in observability agents that work cross capabilities.
00:11:11.679 --> 00:11:19.360
So these new agents like aid customers in identifying and resolving issues quickly, regardless of where they are in the flow.
00:11:19.519 --> 00:11:21.840
So a big value out of the platform.
00:11:22.240 --> 00:11:26.960
We've also focused on adding more business user-friendly type of views.
00:11:27.039 --> 00:11:38.480
So everyone doesn't need to speak EDI, so to speak, or be an expert in those types of things by having more easy to understand, say human readable and role-based appropriate access.
00:11:39.440 --> 00:11:46.320
Also, like taking into consideration customers operate in different models, as Navdeep was saying.
00:11:46.399 --> 00:11:53.120
So they can be hybrid, they may have different geos, different deployments, a mix of various solutions within IBM.
00:11:53.200 --> 00:11:56.639
And they really do need holistic views of all of these things.
00:11:56.799 --> 00:12:09.120
So I definitely see strong value in a solution bringing these types of transactions all together in one spot and helping customers proactively identify these types of bottlenecks across their entire ecosystem.
00:12:09.679 --> 00:12:10.879
Makes total sense.
00:12:11.200 --> 00:12:14.240
Nev, you know, before we wrap this up, I'd love to get your read on this.
00:12:14.320 --> 00:12:23.279
You know, how does MeshIQ specifically, you know, B2B in the flow intelligence layer onto this, you know, provide that end-to-end assurance?
00:12:24.320 --> 00:12:30.879
Yeah, so you know, the transaction boundaries keep expanding from partner onboarding to AI agents.
00:12:31.120 --> 00:12:41.519
And as the transaction boundaries have increased for B2B EDI and MFT transactions, um, the flow intelligence into the complete flow has become extremely important.
00:12:41.759 --> 00:13:01.120
And mesh IQ, B2B and Flow Intelligence uh sorry, Mesh IQ, B2B and MFT flow intelligence taps into 40 plus data points like APIs, uh files, MQ, IBM MQ, Kafka, Webhooks, etc., to gather the relevant metrics into the transaction flow.
00:13:01.519 --> 00:13:06.720
So transaction could be stalled, slowing down, or totally failed.
00:13:07.200 --> 00:13:10.960
So our goal from B2B and MFT flow intelligence is very simple.
00:13:11.200 --> 00:13:14.080
Detect bottlenecks before they become outages.
00:13:14.320 --> 00:13:32.240
So we can look across IBM Sterling integrator, Sterling File Gateway, Web Methods Active Transfer, Web Methods Trading Networks, and every other IBM and non-IBM technology which is involved in the overall transaction flow to monitor the complete end-to-end transaction flow.
00:13:32.480 --> 00:13:55.279
And by correlating these transactions and by adding the layering on the proper context on top of these data points, each transaction flow can be analyzed for SLA violations and we can diagnose the slowdowns, whether it could be due to an expiring or expired certificate, uh slowing down network or even storage outages.
00:13:55.360 --> 00:14:04.559
If the storage is full and the MFT transactions are failing, and we can detect issues at the network layer and even at the OS layer.
00:14:04.720 --> 00:14:13.919
So that gives you a complete picture on why these mission critical B2B and MFT transactions are slowing down or failing.
00:14:14.159 --> 00:14:25.600
We deliver the end-to-end visibility across each step in the transaction, not just the visibility on top of the B2B gateway, because most of the problems they happen downstream from the B2B and MFT gateway.
00:14:26.639 --> 00:14:27.279
Makes sense.
00:14:27.519 --> 00:14:27.919
Love it.
00:14:28.000 --> 00:14:29.200
Thank you for the insights, Nev.
00:14:29.279 --> 00:14:32.960
You know, I think we're about to wrap this up, but I'd love to hear your last comments.
00:14:33.120 --> 00:14:39.519
Um, you know, it seems like Mass Fream B2B isn't just an IT project, it's revenue integrity strategy.
00:14:39.759 --> 00:14:44.720
So, you know, Janine, Nev, what are your last insights to share with the team here?
00:14:47.279 --> 00:14:52.480
So I think it's about uh a bit of an evolution in B2B.
00:14:52.639 --> 00:14:58.399
Navdi uh hinted at this as well, as it becoming a bit more prominent in terms of business strategy.
00:14:58.559 --> 00:15:10.240
So I'm seeing a shift from these conversations around picking a B2B and file transfer solution evolving from just IT discussion, I think to a broader business strategy for organizations.
00:15:10.559 --> 00:15:15.919
So acknowledgement that these B2B documents, files, they're all directly tied to revenue.
00:15:16.080 --> 00:15:18.000
So every transaction matters.
00:15:18.159 --> 00:15:27.039
And if something like an order doesn't go through or a payment is delayed or rejected, then that has real monetary and business impact.
00:15:27.279 --> 00:15:36.000
So from that point of view, you know, IBM's goal is definitely to ensure that every business transaction that should generate revenue for customer does so.
00:15:36.080 --> 00:15:40.960
And it does so completely correctly and in an on-time fashion.
00:15:42.320 --> 00:15:43.039
Thank you, Janine.
00:15:43.120 --> 00:15:44.240
Nev, any last thoughts?
00:15:44.480 --> 00:15:45.919
Yeah, I completely agree.
00:15:46.000 --> 00:15:58.320
And I think uh for many industries like manufacturing, retail, finance, and even healthcare, um, I will not hesitate to say that B2B and MFT are the most critical business applications that directly impact revenue and profitability.
00:15:58.720 --> 00:16:08.639
Flow intelligence into IBM sterling and non-IBM technologies uh involved in the overall transaction flow, it should be a very high priority for every CIO.
00:16:08.799 --> 00:16:12.960
Uh and it should be on their agenda to protect and grow revenue.
00:16:13.120 --> 00:16:15.200
So I will end with two thoughts.
00:16:15.440 --> 00:16:17.840
First is modernize your B2B and MFT.
00:16:18.000 --> 00:16:25.759
Look at technologies like WebMethods IPass to process your B2B transactions in the cloud for you know MFT in the cloud.
00:16:26.000 --> 00:16:35.840
And secondly, as you modernize, develop a flow intelligence strategy, we are an IBM partner and we work closely with their teams to deliver B2B and MFT flow intelligence.
00:16:36.159 --> 00:16:38.240
Thank you both so much for the insights today.
00:16:38.399 --> 00:16:41.600
Um, I felt like I learned a lot and I hope that the viewers did as well.
00:16:41.759 --> 00:16:43.600
Um, but thank you again for joining us.
00:16:43.679 --> 00:16:57.200
And for those out there watching, if you have any questions, please reach out, but visit us at at IBM.com and meshIQ.com for more information, and we'll be surely uh be able to track down any answers you have for any questions you have.
00:16:57.360 --> 00:16:58.960
Uh but really appreciate the time.
00:16:59.120 --> 00:17:01.279
Janine, Navdeep, thank you again.
00:17:01.360 --> 00:17:03.360
And until next time, appreciate it.
00:17:03.440 --> 00:17:03.600
Thank you.
00:17:04.079 --> 00:17:04.799
Thank you.
