ignio AIOps, from Digitate in Santa Clara, is a solution designed to improve business agility by creating a unified view of the IT estate, connecting business functions to applications and infrastructure. This is combined with behavior profile of systems and applications that is continuously learnt using this blueprint. ignio aims to improve the transparency of complex Enterprise IT landscapes.
N/A
ServiceNow IT Operations Management
Score 8.7 out of 10
N/A
Built on the Now Platform, the ServiceNow IT Operations Management bundle is designed to help users gain visibility across infrastructure and apps, maintain service health, and optimize cloud delivery and spend.
It's good for issue resolution, user access request automation, standard report generation, health checks, executing self-healing as configured in the attributes. Currently not good at real-time monitoring to trigger an action. Health checks have to be on a scheduled basis.
[...] is changing the way our internal support staff (not only in the IT field) work and enhancing the experience for employees seeking IT assistance through ServiceNow IT Operation Management. We have moved the usual and personalized IT tools and functions from [...] service-desk to ServiceNow IT Operations Management. These advancements have sparked innovation in various aspects of our IT support management, such as enhancing accessibility, managing incidents, optimizing IT workflows and procedures, enforcing service level agreements (SLAs), incorporating AI/ML technology, utilizing virtual agents, streamlining automation, and sharing knowledge throughout the support team via data visualization, monitoring, and reporting. In brief, our collaboration with ServiceNow IT Operations Management is enhancing the effectiveness of our internal system and benefiting our shared clients.
In platform expertise and workflows, so we don't allows have to build everything from scratch.
Tight integration within ServiceNow (especially ITSM) but also brings information and data in from other sources, so I don't feel we are stuck in a proprietary hole.
Increased investment in AIOps and automation
Relatively fast time to value with out-of-the-box capabilities and automation.
There is a lot more the desktop tool can do. For example, we need to apply an upgrade to get the tool to talk to our infrastructure while employees are working from home. The tool was initially installed with the assumption that the desktops would be in UserLand. Instead after COVID-19 the desktop/laptops have been used for over a year on people's home networks. As of right now, we have to sync when the devices are connected to VPN. Moving forward with the upgrade, we will be getting this data over TLS when they are connected to the untrusted networks.
The concept of ignio AlOps requires OCM efforts within most operational teams. This isn't necessarily the fault of the tool itself, but when implementing ignio, or any AIOps tool, the team will get a lot of pushback as an outside team is centralizing the operational improvements. The tool should have a centralized intake process that will allow the collection, ranking, and management of automation opportunities. ignio AlOps should then simulate the proposed efficiencies from implementing something within the backlog. Right now a lot of local teams are having a hard time getting on the same page as the enterprise teams, and a common methodology for prioritizing (even if overly simplistic) would go a long way to enterprise planning.
These tools are very new and things get added to them all the time. There should be a way for the product's stakeholders and process owners to understand the additional value ignio AlOps is gaining over time.
ignio AIOps version upgrades were a heavy lift. Having to learn a new language versus an industry standard language took time. More consideration on overall internal long-term support needs to be determined.
We have built a healthy relationship with the vendor support team throughout the implementation phase, all incidents raised were resolved within the SLA without a fail
I am happy with the way team has implemented and shared the product for our organization. However, would like to see it get extended to the other line of business too.
We wanted it integrated with ITSM and ITBM. Prioir to that we used JIRA for agile development and SysAid for ticketing. So we started with converting SysAid. We went live with Vanilla ITSM. Then we could have a basis for ITOM. However, we needed to migrated from JIRA to ITSM. Only then we felt mature enough to examine ITOM, which required quite a lot of resources. You need networking, motoring, IT and Cyber security team members in your project!!
Increased business value: We have managed to eliminate custom solutions and the accompanying infrastructure, lowering the overall cost and effort of managing legacy solutions. Centralizing our service-desk operations within ServiceNow IT Operations Management streamlines licensing and maintenance for increased simplicity and cost savings.
Reduced service-desk management effort: The automation features we have put in place have decreased the amount of work our helpdesk agents need to do, especially for boring or repetitive tasks. AI and machine-learning capabilities have enhanced inherent decision-making, minimized the risk of human error, and allowed our helpdesk agents to dedicate their time to tasks that require their expertise. For instance, our automation accurately routes incidents 80 percent of the time, resulting in significant time and effort saved.
Reduced mean time to resolution: As we incorporate new features and update the agent support experience, we are consistently seeing a decrease in resolving incidents. In our pilot project, ServiceNow IT Operations Management Predictive Intelligence lowered MTTR by over 10 percent, on average. Using this data, we are expanding the use of Predictive Intelligence across a larger scope for Global Helpdesk.
