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.4 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…
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.
On coming to well suited experience while error handling and effortless recovery processes are crucial, Tidal performs exceptionally well. It can identify and fix automated issues, reducing downtime and interruptions. A smaller automation solution may be more cost-effective if a business primarily utilizes a single platform or uses a small number of applications that do not require complex integration.
Tidal Automation allows us to automate and schedule/ perform various tasks in a easy and effective manner. It is highly interactive and effective allowing nearly 4k -5k jobs to run a day.
Tidal is designed to be easily shareable and collaborative allowing multiple users to work at a particular time making work effective.
Tidal allows us to ensure that every event which is triggered is exactly when it's supposed to be regardless of other activities which are going as well.
It is user-friendly to generate the reports required of a particular object and allows us to test the codes perfectly well before executing in live environment.
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.
1. Tidal is good at processing large volume pf data and is cost effective. 2. Tidal can automate the scheduling of production objects, ensure that materials are delivered on time 3. Tidal Process large volumes of data which cannot be done everyday by running codes/scripts manually which does it with ease when required.
