What are you selling?
Oracle database hyper automation consulting services, specializing in JIRA and ServiceNow Oracle integration. The software resides on a small Linux VM you will have to provision, with very modest requirements, between your ticketing system (ServiceNow, JIRA, etc.) and your infrastructure, whether hardware or software.
How Does the Software Work?
Nothing changes from a manager's perspective, except for two aspects:
1) From here on out, you start assigning the work to the automation modules, instead of your administrators. You keep assigning more and more tasks and incidents to the modules you purchased, until all or at least most of your resolutions, installations, provisioning, and maintenance tasks are automated and scheduled.
2) You do this in the same familiar ServiceNow ticketing system. But be careful. The automation modules work hard. They never eat, sleep, or vacation. They don't understand the concept of "good enough". Everything they do will result in the best possible outcome. It will not just be some DBAs' best. It will consistently be the industry's best, thanks to the Best Practices embedded in our automation modules.
How is Your Software Different from Autonomous Databases?
While some current autonomous database software requires less or no maintenance, that "simplification" applies only to one installed instance. True, for a small mom'n'pop shop that plays a significant role. After all, the owners no longer need to maintain their small "Orders" or "Customers" database or be aware of its existence in the Cloud. But in an enterprise with 100,000+ employees, such user-friendliness is of little consequence. To an enterprise, an administrator is the same as a cell to an organism (cells are essential, a cell isn't). On contrary, those autonomous database offering increase the Total Cost of Ownership because of the upgrade, migration and training costs. There are thousands of disparate database systems, hundreds of incompatible technologies from countless vendors, and warring departments, each locked in its own technological and procedural silo. The enterprise is more interested in ensuring that all its diverse personnel, hardware, and software are efficient and flexible to change. That is usually measured by change velocity, governance, and stability. Unfortunately, none of these crucial factors are improved by the current automation offerings. Let's consider an example. Suppose a database administrator completed a given task 10 minutes earlier because of some autonomous feature or an open-loop automated shortcut. Will the admin's manager notice? The answer is a resounding "no". The manager has already been delaying all due dates by a week because his administrators are always busy and need a week to get to them. So, as long as the task is completed within the week, the manager would not notice the 10-minute improvement. But if the same tasks didn't even need to be assigned or opened, the manager will notice. If the work was magically done by itself, 24x7, always under budget and ahead of schedule - that, again, the manager will notice (so will the manager's manager). This is where open-loop automation falls short and closed-loop hyper-automation delivers.
The second factor is organizational: protecting the company from this stubborn technology. Let's keep exploiting the same configuration change script. Let's say the buffer week the manager has given the administrator has passed. Before an employee runs the script, they must attend hours of CAB, JIRA, Agile, Kanban approval meetings. This is another week wasted, on top of the first buffer week. What is worse, it is the same configuration change that is being discussed/approved and executed each time, just a different iteration. This makes as much sense as disassembling your car in your garage after work just to reassemble it again in the morning to drive back to work.
It is an enormous waste of time and effort that could have been used more productively. There is currently no technological solution to this problem of extreme organizational inefficiency (the bigger the company, the worse). We need a method that enables all the disparate departments, teams, technologies, and processes to work in tandem to implement a long-term business strategy. The current Cloud autonomous database offerings don't even begin to scratch the surface of usability there, as they're all open-loop. Asking them to reduce the database software TCO is the same as asking a Burger King restaurant to rid you of your diabetes. They are not set up for that. Selling you a diet salad is the best they can do.