In IT Operations we are all about successfully delivering our Service Level Agreements (SLAs) to the business. At the same time we need to be able to make changes to our production schedules, today it can be difficult to understand the impact of those changes to the delivery times of our jobs before they are in production and potentially causing us problems.
We obviously test, we may have test systems available to run them before going to production, but often we don’t have the same scale of data for it to be representative. Some of our processing is very long and when testing we need to wait for it to complete before knowing the impact. So, sometimes we do more minor checks and make a call as to what impact it will have and we don’t always get that call right.
Also, our schedules are often complex, because our business is complex, so unforeseen consequences come and bite us and we end up firefighting another issue and negatively impacting the business and what the business thinks of Operations.
That is where the simulation facilities of Automic Automation Intelligence comes to our aide. It allows us to simulate the schedule changes using data from our production environments without ever making the changes in the AutoSys environment. It’s easy, quick and allows us to drill into the detail of what happened so that we can confirm the change or improve further. This means we can model and plan additions or improvements to our schedules without the guess work.
In the user interface you simply select “run a new simulation”, you choose the dates and times you want to simulate. Then you simply provide the JIL changes that you want to apply, remember they will never be loaded into AutoSys, so there is no danger of accidental execution, the JIL changes can be typed into the UI or more commonly supplied as a file.
This is standard JIL text, you can provide a comment for any changes to run time for both new and existing jobs this will be reflected in the simulation. You can set overrides to any global states, such as assume success instead of failure from the source execution data within AutoSys, then you simply submit the simulation.
The JIL you supply is validated, so any syntax errors or missing dependencies from the production system would be highlighted– so what you provide is known to be valid for the production environment.
Accurate Predictions on the Impact of Proposed Changes
The simulation then calculates the results, this typically will complete in seconds, for very large changes it might take a minute but you will receive a notification that the simulation has completed.
Now you can see the impact of those changes on the delivery of processing, how it impacts any associated SLA. You can even do a side-by-side comparison of an existing execution against the new simulation to see in detail, step by step what impacted the execution delivery.
You can make changes to your AutoSys workloads with the confidence you fully understand the impact on what IT Operations will deliver to the business. You do not have to wait for the elapsed time of the processing or need a test system or live data to run it.
Remember, this is a simulation, none of the job changes were ever presented to AutoSys, so you can keep making these changes until you get to the result you want and once happy, release them to AutoSys confident in the outcome for the business.
Click here to see a 12 minute demonstration of this in action.