
ServiceNow投資からさらに運用価値を引き出すには――BigPanda CEO アサフ・レズニック氏が語る
How IT Leaders Get More Operational Value From Their ServiceNow Investment - with Assaf Resnick of BigPanda

ServiceNow投資からさらに運用価値を引き出すには――BigPanda CEO アサフ・レズニック氏が語る
The AI in Business Podcast
要約
BigPandaのCEOアサフ・レズニック氏が、導入済みのServiceNowの上にコンテキストと相関分析の層を加え、ITオペレーションの価値を高める方法を語った。大量のアラートを少数のインシデントに集約し、AIエージェントが原因特定や対応まで担うことで、対応時間や誤エスカレーションが減ると述べている。進め方としては、全面刷新ではなくレベル1運用などの小さな成功から始めることを勧めている。
この回のポイント
- ●レズニック氏は、AIエージェントの性能は与えられるコンテキストの質で決まると述べ、Slack、Jira、Confluence、監視ツールなど多数のシステムの情報をServiceNowに集約するとしている。
- ●文書化されていない「暗黙知」も、優秀な担当者の行動や会話を観察することで取り込み、組織の知識にできるという。
- ●監視ツールのアラートの洪水をAIと機械学習で相関させ、例えば2万件のチケットではなく20件の本質的な問題にまとめられると説明した。
- ●自律度は「ダイヤル」であり、サーバー再起動のような安全な修正は自動化し、ロールバックなどは人間に推奨して実行させるといった使い分けを提案している。
- ●品質は再エスカレーション率や平均インシデント継続時間で測れると述べ、優先度1の障害が平均3日から5時間に短縮できる例を挙げた。
- ●導入は大規模な計画から始めず、外注L1運用、サービスデスク、AI SREなど痛みの大きい領域で短期の成果を出すことを勧めている。
章立て
ServiceNowを使い切るための文脈
AIエージェントにはコンテキストが重要であり、複数システムの情報と暗黙知をServiceNowに集約するというBigPandaの役割が語られる。
アラートの洪水を相関で整理
監視ツールが生む大量のアラートをAIで少数の問題に集約し、人手の対応負荷を減らす考え方を説明する。
価値向上の兆候と状況把握の速さ
オペレーター増員が続くことが兆候だと指摘し、状況把握を数時間から数秒に短縮できると述べる。
大規模障害とエージェントの群れ
数百人が参加するブリッジコールの代わりに、専門家エージェントが原因と直近の変更を特定する構想を語る。
自律度の調整と再発防止
自律度をダイヤルとして調整する考え方と、インシデントから学んで再発を防ぐ点を説明する。
品質とROIの測り方
再エスカレーション率やインシデント継続時間など、品質を測る指標を紹介する。
段階的な導入と最初の90日
L1運用などから小さく始める進め方と、最初の90日で期待される変化を語る。
解説記事
BigPandaの創業者兼CEO、アサフ・レズニック氏が、The AI in Business Podcastで、ServiceNowを導入済みの企業がAIによってさらに運用価値を引き出す方法を語った。ServiceNowを置き換えるのではなく、その上にコンテキストと相関分析の層を加えるという考え方が軸になっている。なお、同氏はBigPandaの立場から語っており、以下は同氏の主張である。
AIエージェントの鍵はコンテキスト
レズニック氏は、ServiceNowの業務の多くがAIエージェントによって担われつつあるなか、エージェントの知能は与えられるコンテキストの質に左右されると述べる。BigPandaはITナレッジグラフを用い、ServiceNow内の記録に加え、Slack、Jira、Confluence、監視ツールなど多数のシステムに散らばる情報を集めてServiceNowに取り込むという。
もう一つの柱が暗黙知である。大企業の重要な知識の半分は文書化されず、優秀な担当者の頭の中にあると同氏は言う。エージェントは「設定される」のではなく「インターンとして育てる」ものであり、過去のチャットやブリッジコールで誰が何をしたかを観察させることで、組織の知識に変えていくという説明だった。
アラートの洪水を少数のインシデントへ
銀行や航空会社のサービスは、サーバー、ネットワーク、マイクロサービスなど数万の要素で成り立ち、それぞれに監視ツールがある。その出力は人間が追いきれない「津波」になっていると同氏は述べる。BigPandaはAIと機械学習でこのノイズを相関させ、たとえば2万件のチケットを、本当に重要な20件ほどの問題に集約できるとする。2,000人のオペレーターが対応する代わりに、少数の優秀な担当者が重要な問題に集中できるという主張である。
価値向上の兆候としては、技術基盤が複雑化するにつれ、サービスデスク、NOC、インシデントマネージャー、SREの増員が止まらない状況を挙げた。人手で対応を続ける限界に来ていれば、導入を検討する合図だとしている。
状況把握の高速化と「エージェントの群れ」
見た目が同じアラートでも、軽微なものと大規模障害の前兆があり得る。これを見分けるには、同じクラスターの他のサーバーの状態、影響するサービスの重要度、顧客や売上への影響などを確認する必要がある。SLAでは15分が理想だが、現実には数時間から数日かかることもあると同氏は述べる。AIならこれを数秒で行え、対応や適切な担当者へのエスカレーションまで示せるという。
大規模障害では、数百人の専門家が参加するブリッジコールが開かれがちである。BigPandaは、優秀な担当者を模した専門家エージェントが群れとして調査し、7時間ではなく7分で済ませる構想を示した。症状から根本原因と下流の影響を切り分け、影響範囲と震源を特定し、直近の変更(例として2週間で2万件)の中から原因となった変更まで突き止められるとしている。
自律度は「ダイヤル」
どこまで自動で解決させるかについて、同氏は自律性は一律ではなくダイヤルだと説明する。サーバーやサービスの再起動のような安全な修正は完全自動にし、コードのデプロイやセキュリティパッチのロールバックのようにリスクのある修正は、エージェントが推奨し人間が実行する、といった設定が可能という。
さらに、インシデントごとに学習し、危険な変更が再び試みられた際に警告を出すことで、事後対応型から予防型へ運用の姿勢を変えられるとも述べた。
品質の測り方と導入の進め方
品質は再エスカレーション率で測れるという。外注のL1 NOCでは、約40%が誤った担当者にエスカレーションされ、正しい担当者に届くまで6〜7回回ることもあると同氏は述べる。また、人手中心の運用では優先度1の障害が平均3日続くとし、これを5時間に短縮できるかが指標になるとした。
導入については、2〜3年かかる大型プロジェクトを避け、一つか二つの明確な成果から始めることを勧めている。候補は、離職の多い外注に頼るL1運用、サービスデスク、ブリッジコールを代替するAI SREなどである。クラウド移行が少数のワークロードから進んだ例にたとえ、最初の90日で、インシデント数の減少、継続時間の短縮、質の低いエスカレーションの減少が見込めると語った。
まとめ
この回の主張は、ServiceNowを作り替えるのではなく、文脈とアラート相関の層を足すことで運用負荷を下げるというものだ。数値は同氏の発言であり、ベンダーの立場からの主張として受け止める必要がある。それでも、再エスカレーション率やインシデント継続時間といった指標で効果を測り、痛みの大きい領域から小さく始めるという進め方は、ServiceNowを使う日本の企業にも参考になるだろう。
文字起こし(英語・自動生成)
Welcome, everyone, to the Emerge AI in Business podcast. Today's guest is Asab Resnik, founder and CEO at Big Panda. Big Panda is an authentic IT operations platform and an elite-built partner with ServiceNow, running as a certified app natively inside the ServiceNow ITSM workflow. In this episode, a staff discusses how enterprise IT teams can get more operational value from a ServiceNow deployment that they've already booked, using AI to pull context from across the organization's systems and prior knowledge into a single actionable view. He explains how correlating alerts into fewer, clearer incidents changes what operations teams actually do when something breaks and what a realistic incremental path to this kind of modernization looks like for a ServiceNow heavy enterprise. Today's episode is sponsored by Big Panda. In this episode, we cover how enterprise IT leaders can get more value from a ServiceNow investment they've already made.
To go deeper on this topic and learn how to evaluate AI vendors by assessing leadership expertise and why funding benchmarks can signal product maturity and stability, download our free PDF report, Five Ways to Select the Right AI Vendor at Emerge.com.aiz1. That's Emerge.com.aiz1 to download your copy. Now the conversation with the staff. welcome back to the podcast thanks for having me back good to be here yeah always interesting conversations and a very different one than what we've had before. I think every enterprise IT leader we talk to has already put real budget behind ServiceDial.
It's the system that most of them run their operations through and a lot of thought has gone into it. But getting a platform in place and getting the full value out of it is not always the same thing. And sometimes it requires a bit more of conversation. And that's a genuinely interesting territory. So I want us to kind of dissect that part first and ask you that for a team that's already invested, what is the difference between simply running ServiceNow and actually getting the most out of it look like in practice? So good to be back, by the way. Thank you. So ServiceNow is obviously this critically strategic platform for enterprises where work gets done. Now, you know, a lot of that work these days is being done by agents. But when you have agents that were powered by AI, intelligence today is really only as good as the context that you can feed those agents. And so where we come in for large enterprises and where we play really, really nicely and serendipitously with ServiceNow is we have an IT knowledge graph that says,
hey, how do we get as much context as we can out of two buckets? One is all of the systems that a large enterprise has. So, of course, there's a lot of ServiceNow as a system of record. There's a lot in there. But there's a lot of other context in a lot of other systems as well. There's context in Slack and in observability streams. There's context in whatever you may have in your knowledge articles in JIRA or Confluence. There's confluence in 57 different systems. And what we're really good at is getting all that context out of those different systems and putting that into ServiceNow so all of the humans and the agents that need to do that work can have that context. That's bucket number one context. The other bucket is tribal knowledge. If you're a large enterprise, half of the critical knowledge you need, it's not written down anywhere. It's in the heads of your best people.
And so what we're really, really, really good at is if you think of how agents come online, agents aren't configured. They're interned. And how do you intern an agent? By letting the agent observe. What do your best people do when they're in action? Who did what? Was there a chat six months ago where someone said something? Was there a bridge call three weeks ago when an escalation path became clear of who actually owns something? And being able to get those breadcrumbs out of the heads of your best people and turning that into institutional knowledge, that's an invaluable source of context, both for humans and for Asians. And so that's what we do really, really well, and we pair that with ServiceNow to make sure that everything someone needs, whether it's a human or an agent, has all the context they need to do their job. Can you take us through the observability part? Exactly how does that happen?
How do we make sure that that happens? Sure. So obviously one important piece of context is all of the observability tools that are telling you, hey, what's happening right now with my critical infrastructure that's powering my digital services? So for a customer to go to a bank or go to an airline and reserve a ticket or withdraw money from their ATM, there's a lot of different technology pieces that have to work together. There's servers, there's networks, there's applications, there's microservices, tens of thousands of moving parts. Each one of those moving parts has an observability tool that is observing the critical performance metrics of that piece. Now, it's at a point, though, where the scale of those machines is such that a human being just can't possibly keep up. So there was a day not so long ago where you had a bunch of human operators in a room looking at 57 different screens of all my networks and databases and clouds.
But the complexity of modern enterprise is such that there's just way too many moving parts and they're moving way too fast. And so all of the observability of those moving parts has turned into a tsunami that people just cannot keep up with. unless you know how to read the matrix, which most people don't, it's very hard to keep up with what's going on. And so that's where we come in. One of the things we do is to say, hey, feed us that fire hose of observability. We are really really good at taking all that signal all that noise and using AI and machine learning to correlate that into the handful of signals that you really really need to know And so that can make the difference between having 20,000 tickets in service now about a bunch of different systems or, hey, we've correlated that, all that noise into signal about what's really going on. And
What you really have is 20 issues with lots and lots of symptoms, and those should turn into 20 tickets in ServiceNow. And so you don't need 2,000 different operators handling and responding to 2,000 different tickets. You need a handful of your best people working on the 20 things that really matter most. Yeah. Okay, that makes a lot of sense. And I want to also fix that a bit on the word symptoms. And I think, you know, the IT leaders that we've been talking to, they're very happy with ServiceNow. So they'll see this as an opportunity to look to get even more value out of it. What are the symptoms to knowing that, oh, there's an opportunity for more value? How do they know that they can do better from context and from the observability? Yeah. So it's really around, you know, the story is not about improving ServiceNow. ServiceNow is a wonderful platform. The story is, how do you take a tsunami of data and context and turn that into either insight for a human being to react to or full autonomy that doesn't require a human being at all?
And so what are the symptoms? Well, they're not hard to see. Are you spending more and more budget to hire more and more operators to keep your tech stack running? Do you have to hire more and more folks into your service desk? Do you have to hire more and more folks into your network operations center? Do you have to hire more and more incident managers? Do you have to hire more and more SREs? Because as your tech stack rows in complexity and scale and velocity, which generally are good things because they let you innovate faster, for the folks who have to operate, it's a huge challenge because there's just more and more moving parts. And so for any CIO or any technology leader that says, hey, I can't keep throwing human workflows at this tech stack that's just expanding well beyond the limits of human scalability, well, that's a pretty good indicator that you need someone like a big panda to come in and say, hey, we can actually do the hard work of taking all that data, turning it into insights and turning that insight into action.
And all of that gets done on top of and inside of ServiceNow. Do you want your humans parsing through all that information and connecting the dots? Or can you have agents doing that, doing it faster, doing it more accurately, and taking fast action instead of humans? And connecting the dots, obviously, that's going to be very reliant on the context that we have available. So let's dive into that part of the conversation and look at, you know, if two alerts can almost look identical on a screen, right? So same error code, same server name or whatever. And yet one turns out to be something that we can fix in two minutes and the other becomes the start of a major outage. So they look the same going in, but it actually tells your team different things. How exactly does that happen? What actually tells your team the difference between something that's going to be a quick fix and something that's going to be or will require more effort? A lot of it is, you know, when you are a human and you get an alert that says you're an IT operations specialist
and you get an alert that says, hey, server number 123 is having high disk utilization. That in and of itself isn't enough information to say, hey, something's going on. What you need to know is there's a whole lot of secondary questions that you need to know to tell you, hey, is this a real issue or is this just a noise that will go away? Because ultimately what you want to know is, is this going to impact my customers? Is this going to impact my revenue? Right? And so for server number one, two, three, you need to know, hey, how critical of an issue is this? Are there other servers in the cluster that are having a bad day? Does this server cluster serve some kind of mission-critical microservice that is part of a larger service that is mission-critical? Or do they power some kind of service that's not really important? You want to know which customers of mine depend on this service.
You want to know, hey, what is the impact to my customer if this service goes down? What is the impact to my revenue if this service goes down? So all of those questions can take you hours to answer just to be able to answer the question, hey, should I respond to this one issue about server number 123? And so you can see why you have to throw armies of humans at all of these questions. Typically, you want these questions answered in an SLA of 15 minutes. In the reality, it takes humans hours and sometimes days. And so that lets critical problems fester. So with AI, we can say, hey, all of those questions I just asked that you need in order to get situational awareness, We can do that in five seconds, not five hours. And because AI can see the entire matrix and connect the dots and humans can't, you can typically get answers that are much more accurate, much faster.
And with AI, at least with Big Panda, you can actually take action and resolve those issues really, really quickly. So it's the difference between saying, hey, it's going to take me five hours just to get situational awareness about, is this an issue I need to respond to, to that answer comes to you within seconds, plus clarity about what actions should I take to either resolve this issue or escalate it to just the right person. And so if we're thinking of something that, let's say there's a company-wide outage, obviously loads of tickets coming in for the same thing, how is context going to change the way that the system groups those alerts? Is that even something that would be relevant to this part? Yeah, absolutely. So, you know, when you have today a really big outage, okay, you are an airline and your fleet is grounded and you have angry passengers stuck in the airport. You know, there's a very special place in hell for airlines that keep their passengers stuck in the airport.
At that point you have a bridge call and you calling in all of your experts right Because these really really big issues are never isolated to one thing just the network or just the application layer just the database, because they tend to have started somewhere and then they spread out, spread out, spread out, and you see symptoms everywhere. So a lot of our customers, they end up having these bridge calls from hell with 400 experts on the line, each one with access to just a deep but very siloed part of the infrastructure. Everyone's typing away to look at what systems they own and what is the health of those systems and when did things start to deteriorate. And those can take hours, if not days, to figure out what is actually going on. It's a very reactive way to run your business, and it's also very disruptive because those 400 experts, they have a day job. Their job is not to firefight. Their job is to build the future of your company.
And so what we come in is we say, hey, instead of bringing all your best people, bring our swarm of experts that are fashioned after your best experts. They're watching your best experts in action. And we're actually creating agentic specialists to know and have the same expertise as your best specialists. And they will swarm. And they will have the bridge call. But the bridge call will take seven minutes, not seven hours, and it won't be disruptive for your best people. And then we'll be able to take all of those different systems or symptoms and understand, hey, which of these systems are – these symptoms are a root cause versus a downstream impact. And then we can start to really understand, you know, what is the blast radius of an issue? What is the epicenter of that issue? And let's just dive into the epicenter. Then once we're there, we can say, hey, what changed recently?
You know, I'm a large enterprise. I've had 20,000 changes over the last two weeks of people deploying code and people changing infrastructure, people changing security configurations. any one of those 20,000 issues could have started off this avalanche of an incident. With AI, with our AI, not only can you get to the epicenter of a problem, you can actually get to what changed and is the root cause of that issue. So all that can happen in minutes versus today, which is typically many, many hours with many, many humans. Yeah. So the picture that we're painting for our audience members is kind of like, you know, the experts are already in the room, already brainstorming before you even open the alert. Is that the right picture that we're painting? That's exactly it. The expert agents are there swarming and brainstorming and hypothesizing and throwing ideas at the wall. And another expert comes and stress tested it. They're doing all the work that the humans are doing, but we're doing it agentically. Yeah. And like you said, with a fraction of the time. So what happens then?
Obviously, is there decision making that happens after? Is that way it's handed over to a human, or is there certain types of decisions that we will allow the authentic experts to take? So a few things happen then. So first of all, ultimately you want to resolve the issue, right? And so that's when you get into the conundrum of how much leeway do I give to autonomy to resolve things. And so the answer is it really depends on what the situation is and what the trust level is of customers. Autonomy is a dial. There's no one-size-fits-all. So customers, enterprises can say, hey, for fixes that are very safe, like restarting a server, restarting a service, go ahead, and I want that to be fully autonomous. And if that fixes the problem, great. for fixes that are maybe a little bit more involved, like rolling back a code deployment, rolling back a security patch.
You know what? I want you to recommend an action to a human, but I want that human to actually go do the fix. And so that's kind of, you know, autonomy is a dial, and you can figure out for which use case, For what level of risk tolerance are you willing to give autonomy? And so that's step one. And step two is, hey, how do I prevent this issue from happening in the first place? You know, one of the beautiful things about Agentec ITOps is it can help change the mindset of operations teams from, hey, I'm reactive. I need a bunch of humans sitting in a room waiting for a fire to start so we can go fight the fire. to, hey, how do I prevent this problem from happening in the first place? And so with every incident that we are helping resolve, we're learning from that. We're understanding the symptoms.
We're understanding what are the changes that were made that maybe shouldn't have been made or made in the wrong way, in a very risky way. And how do we make sure those kinds of things never happen again? And when someone tries to do that again, we can raise the flag and say, hey, last time someone tried to do that, it caused a big problem. Here's why it caused that problem. Here's our recommendation for what you should do to prevent that issue from happening again. And that's invaluable. So not only are we helping enterprises respond to those incidents faster, we're dramatically helping them prevent those issues in the future. Yeah, and that's exactly what I wanted to ask you next, Because I know that we have IT leaders listening saying that, you know, it sounds kind of like better together idea. We know that ServiceNow is already wonderful, but it can be even more wonderful. And that's, again, the better together concept. And they're going to ask, okay, but how do I measure quality? Because it's easy to measure speed, knowing that decisions will be made faster or resolutions could happen faster.
But what is the difference between just what they're used to now and the quality improvements that they'll see? How can they measure that? Well, it's actually quite easy to measure quality. So is the system, so there's a few use cases. So whether it's autonomous service desk or autonomous knock, are issues being resolved with accuracy? That's not hard to check. when an issue is being escalated. Is it being escalated to the right person, or do they have to re-escalate it? So think of a typical outsourced L1 knock, right? 40% of the time when that junior person is saying, hey, I don't know what to do, I've got to go escalate it to this expert, 40% of the time they're escalating to the wrong person. And so that person who has a day job has to take time out of their job Say okay well what is this ticket about Huh this isn me Let me go escalate it to that person And those issues typically get escalated six to seven times before it actually hits the person who can do something about it
And so with agentic IT ops, it's very easy to measure, hey, what was the re-escalation rate? And so, yeah, I know you can do it faster, but can you do it better? And the answer is yes, we can do it dramatically better. Get it to the right person, give that person the right context very quickly to do their job. And ultimately it's, hey, did you reduce the average time that an issue lives for? So, hey, with fully human workflows, the average priority one severity incident would last three days. Those are real numbers, three days. Well, can you bring that down to five hours? And if so, well, you know, it's a no-brainer. You can do it with less people, better quality of service, and ultimately happier customers. And easy measurement, because I think that's one thing that leaders struggle. If they need to motivate why something new needs to enter the chat, something must be built upon on top of what they already have,
they're going to be asked questions around ROI. And the ROI is going to be the speed, but not just that, the quality, the accuracy, the escalation. And there's a lot to think about and a lot to show for what you're saying. So last part of this conversation is where we give our leaders some very concrete advice. And we know that we have a lot of leaders sitting on ServiceNow that has already been deployed. They're listening to what we have to say, and they're thinking about, okay, what does the future look like? So for enterprises with ServiceNow already deeply embedded, what is a realistic incremental path to modernizing the workflow? What does that actually look like? So it's a great question. You know, when it comes to doing an agentic transformation of any large enterprise functions, certainly operations, typically my recommendation is don't start with a boil the ocean project that's going to take you two or three years. Start by finding one or two clear wins and get there.
So typically one that is an easy win is level one operations. So a lot of our customers today are outsourcing their operations to global systems integrators. They've been outsourcing to GSIs for the last 20 years. Nobody's happy with that situation. You're paying a lot of money to an outsourcer to run your most mission-critical infrastructure, and the employees of that outsourcer have an average tenure of seven months. It means every seven months, the people that are running your most critical infrastructure are quitting. And so at any given time, you've got someone who's junior, doesn't know your customers, has been there for three months, and doesn't really feel the emotional impact of an outage. That's a really good place to start with really, really fast ROI. We can do the same for service desk. Another great area is AISRE. So, hey, if you're tired of bridge calls from hell that are sucking up the time of your most strategic builders,
bringing in AISRE to do that swarm for you, that's very, very fast value as well. And so, you know, depending on where you have the most pain, dip your toes in the waters, start building out that context graph, and then growing from there, it just becomes easier and easier and easier. And where will our leaders see the changes in the first 90 days? If they have to monitor this, then obviously we've spoken about the measurement, but what will be the clear indicators within the first 90 days of the changes that this will bring? Incidents should go down in volume dramatically. The duration of those incidents should go down dramatically. Poor quality escalations that disrupt your best people when they're not really the end target should improve dramatically. So less incidents, faster resolution, less disruption. Again, a no-brainer. I cannot see anyone arguing with that. I think that's exactly what we all need
to go and look up and start studying after this conversation. I know that we have loads of IT leaders that will listen to this probably more than once to get out of it, to get the insights out of it. Asaf, thank you so much for sharing so much. Is there a final thought that you would love to leave out? Yeah, you know, it's what I said before. If you think of, the thought is just get started and get started small with a fast use case that you can prove out ROI very, very quickly. You know, very much like how people migrated to the cloud 15 years ago. they didn't just say, CIOs didn't just say, hey, let me move everything to the cloud overnight. They said, hey, let me take one or two workloads, put them in the cloud, show ROI, get familiar, and put a handful more. So, you know, with Big Panda and Agentec IT operations, it's very easy. It's not a boil the ocean project. It's pick one environment, let's get a quick win, and let's start the snowball going from there. Absolutely, and I think that's exactly what we leave our audience with today.
Thank you so much. It's been wonderful having you back in the studio. Thank you. Wrapping up today's episode, I think some three key takeaways from our conversation with the staff. First, the friction IT leaders feel often comes from the growing number of monitoring tools feeding alerts into their systems. not from the platform recording those alerts. Second, adding a layer that groups and enriches alerts with context can cut incident duration dramatically and reduce how often issues get escalated to the wrong person. And finally, modernizing operations doesn't require a full rebuild. A focus first step like outsource level one support or a single high friction process can show fast results before scaling further. In this episode, we covered how enterprise IT leaders can get more value from a ServiceNow investment they've already made. on this topic and learn how to evaluate AI vendors by seeking leadership expertise
and why funding benchmarks can signal product maturity and stability, download our free PDF report, 5 Ways to Select the Right AI Vendor at Emerge.com slash AIV1. That's E-M-E-R-J dot com slash AIV1 to download your copy. For further executive level analysis and to join our network of leaders delivering workflow impact with AI, visit Emerge.com. On behalf of the team at Emerge, we'll see you on the next episode. Thank you.
番組の概要欄(原文)
ServiceNow already anchors how large IT operations teams run their work — the opportunity is getting even more value out of that investment. In this episode, Assaf Resnick, CEO at BigPanda, explores how adding a layer of context and correlation on top of ServiceNow helps IT teams capture that additional value without replacing or rebuilding what they've already built. The conversation covers how growing alert volume from connected monitoring tools affects operations teams, what measurable improvements look like, and a realistic first step for scaling that value further. This episode is sponsored by BigPanda Learn how to evaluate AI vendors by assessing leadership expertise, and why funding benchmarks can signal product maturity and stability. Download our free PDF report, "5 Ways to Select the Right AI Vendor," at emerj.com/aiv1
出典・この記事について
- 番組
- The AI in Business Podcast(Daniel Faggella)
- 元の回
- How IT Leaders Get More Operational Value From Their ServiceNow Investment - with Assaf Resnick of BigPanda
- 配信日
- 要約作成日
- 公式サイト
- emerj.com
この要約・解説記事は、元の音声を文字起こしした内容をもとに AI(Claude)が日本語で作成したものです。 固有名詞や数値に誤りを含む場合があるため、正確な内容は元の音声でご確認ください。制作方法について
関連エピソード

マルチクラウドLLMルーティングと、コンテキストを理解するコーディングエージェント
Agentic Conversations (formally mlops.community)

AIネイティブ企業が他社と違う7つのこと
The AI Daily Brief: Artificial Intelligence News and Analysis

【ライブ】パッチは間に合うか?AIが脆弱性を見つける速度が人間の対応を超えつつある
The Neuron: AI Explained

エンタープライズAIはなぜROIを出せないのか|DevRev CTO Ahmed Bashir
Eye On A.I.

暴走するAIボット群が示す「制御喪失」の現実(マックス・テグマーク氏)
Future of Life Institute Podcast

エージェント検索はページを探すのではなく、答えを組み立てる
The Stack Overflow Podcast