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
Tidal by Redwood
Score 6.8 out of 10
N/A
Tidal Automation, from Redwood Software since the early 2023 acquisition, is an enterprise workload automation platform for automating and orchestrating cross-application, cross-platform workloads – in on-prem, cloud or hybrid environments – from one central point of control. Tidal is used to optimize mission-critical business processes, manage…
N/A
Pricing
ignio AIOps
Tidal by Redwood
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
ignio AIOps
Tidal by Redwood
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
ignio AIOps
Tidal by Redwood
Features
ignio AIOps
Tidal by Redwood
Workload Automation
Comparison of Workload Automation features of Product A and Product B
-Autonomous alert and incident management related to infrastructure, NW, and applications. -Excellent fit to handle CPU, memory, and disk space alert management - proactive and predictive. -Several automation features (self-healing) - CPU/Memory modifications; disk extensions; patch management -Provisioning of user access and infrastructure servers, etc.
1. Tidal Automation is a super robust application for Regular SQL tasks or other file maintenance which in-turn can help employee's to free up their time which they spend on working on repetitive tasks. 2.This has significantly reduced the time and effort required for setting up and managing workflows, ultimately increasing productivity. 3. Although we faced few problems while integrating the software with existing systems and was time consuming.
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.
Still a bit slow when navigating. If you close a job you have to wait a few seconds to open another one. Even when you made no changes.
When viewing a job and make no changes, the "ok" button changes the last modified date as if you made a change. No big deal, but wastes time when troubleshooting a problem and looking into what jobs were changed last.
You can see the parameters column in the "job activity", but not in "Job definitions".
Can't search the parameters field in the filter.
Changing a variable name does not change it on the job. It still works because Tidal Automation uses the ID number. It just causes confusion when you see a variable on a job and can't find the variable under "Variables". On top of that, Tidal Automation does not show the ID column under "Variables" making it even more difficult to find the variable.
We are on the fence. The increased pricing for renewals is staggering. With new automation options like Microsoft's Power Automate and Event Driven Ansible on the field, there are other options now available.
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.
Having provided consulting services for years on Tidal by Redwood, I recommend going with a solutions partner or consultant to deploy it. I believe there are sizing and tuning guidelines that should be followed for environments of scale. I believe they are not critical when first lighting up the product, but if you are not aware of them you will encounter performance degradation after a few thousand job objects are added.
Tidal by Redwood excels at performing complex workflows, event-driven automation, and compliance-focused procedures in big companies with varied IT infrastructures. This includes claims, policy, and billing processes are included in this. The sending of our documents and checks to our printers for automatic printing has also been automated with TA. The majority of our regular file transfers to and from our company are done utilizing TA and SFTP. Key characteristics:- Control over access and security. Resource management and error correction. Tools for reporting and observing. Capacity for extensive automation and job scheduling. Scalability for large enterprises. Orchestration of workflow for intricate operations. Uses:- A good fit for big businesses with complicated IT environments. Ideal for managing dependencies and automating complex operations. effective at organizing cross-platform and system functions. strong support for governance and compliance.
It has a positive impact on factors like increase in productivity, easy to implement as there some options pre-built in it which automates and perform.
It also reduces human error mostly as it involve less manual performance and tool is time saving in this perspective.
It also has negative impacts like cost of the tool as its expensive and if it's not properly utilized it may lead huge revenue loss as all will be scheduled per plan.
We have to continually monitor its effectiveness to ensure a positive return on investment.