Cost of change

Well it is time for my second blog entry. This time around, I have chosen to discuss some of the hidden costs of changing from one product to another that pretty much delivers the same functionality and results.

Firstly a cost of change analogy:

If we take a simple home scenario of changing a car to help understand some of the hidden costs we do not always think about.

So you decide that you want to trade in your large gas guzzler for a more economical car, no harm in that. So you start by determining if the numbers add up, if you bought a smaller car that has a manual transmission instead of an automatic transmission, which is more economical than a larger car. You chose the Manual transmission because it should be more economical. The figures will add up as follows:

  • Lower monthly car instalments
  • Lower monthly fuel bills
  • Lower insurance premiums
  • Based on financial analysis you go ahead and change your car.

    Now the hidden costs start showing their ugly head, your wife, your son and your daughter need to go for additional driving lessons as they have only ever driven automatic transmission cars and do not know how to drive a manual transmission car. Then there are a few mishaps that result in damage to the car but no one is injured. This means claims against your insurance, which means you loose your no claim discount. Then because you have made claims your premiums go up. While your family is learning to drive properly with the manual transmission they actually use more fuel than your old automatic transmission car did. Then along comes your first family holiday with the new car and you find that because the car is smaller you can not fit all the luggage into the car. So you either need to buy a trailer or rent one, again additional cost that would not have been incurred with the old larger car.

    Net result, after a year your new cheaper, more economical car has actually cost you more.

    Now lets move on to the technology related discussion.

    Decisions of which technology is deployed to solve a particular problem is always taken at a higher level. The biggest contributing factor is always cost, and ROI. The cost of ownership and ROI is very often presented by the vendor and although fairly accurate, omit a couple of factors. Here are some factors often overlooked when migrating from one technology to another. These are factor that either myself or friends of mine have witnessed, this list is by no means exhaustive or complete.

  • One of the the most commonly overlooked factors is the cost of retraining the users on the new technology.
  • On a regular basis all the peripheral scripts and tools that have been developed around the existing technology.
  • If we focus on Workload automation, very often some of the batch streams need to be redesigned because the new technology does something differently.
  • More often than not there is a great deal of work that needs to be redone with regards integrating the new technology into other areas of IT.
  • All of the above points can be quantifiable in turns of cost to the organisation in monetary terms with regards to time and loss of productivity.

    There are also some soft losses when switching technologies, and these include:

  • Relationships that have been built with the existing vendor. This sometimes results in additional benefits such as discounts or even early access to new releases.
  • The support staff going from experts to novices.
  • Familiarity moving to apprehension or uncertainty.
  • In conclusion, I am in no way saying that we should not change technology. I am just wanting to ensure that we see the entire picture and know the true cost of the change. There are times when the newer technology is the better option even if it costs slightly more to change. I guess my ultimate goal is that we make informed decisions based on factual data and not make decisions based on emotions.

    19 Responses to “Cost of change”

    1. Nice post. Lots of good points. Found your car analogy very entertaining!

      Working with your car theme, one problem with Autosys r11.0 is that the lack of FTP/SFTP integration is like not having electric windows when all your friends have had them for years. Could the lack of scalability in WCC also be likened to squeezing a bus-load of passengers into a Fiat 500 (or a Mini).

      The AutoSys r11 Administration radically changed between AutoSys 4.5 and AutoSys r11. Riffing on the same car theme, managing the new r11.0 infrastructure is like progressing from driving a scooter to driving a bendy-bus. Clearly it’s not impossible to progress from one to another but there’s a lot to learn (and some cyclists may be crushed). Hand on heart how long has your latest r11 project taken to take into production. 6 months, 12 months, 18 months? I think that all AutoSys r11 implementations are big projects where we have to learn the products from the ground up.

      I disagree about your point about a soft loss “the support staff going from experts to novices”. his point doesn’t work for Admins in my opinion, as an AutoSys 4.5 expert is only r11 novice. (Although I agree that for end users this is not the case but retraining end users from scheduling product A to scheduling product B isn’t that difficult).

    2. Martin Says:

      Ha! This post is a good attempt at explaining the issues via fable but I would contend that my wife, daughter and son (Infra Manager, Autosys Admin US and Autosys Admin UK) are more than capable of upscaling from automatic to stick shift gearbox but they were left somewhat dazed and confused when placed in the cockpit of the space-shuttle (Autosys r11).

      Yes CA had Astronauts (some really great Autosys gurus) they sent to help us get off the ground but no it’s not a simple step.

      If the previous comment is saying an Autosys 4.5 expert is only a Autosys r11 novice I think I would agree.

      Keep posting

    3. Jonathan Says:

      I think the difference here is how you administrate AutoSys. We don’t use the GUI’s for administration. The command line is much more powerful and quicker than using the Windows Admin GUI or the 4.5 Web Interface (which has it’s own scalability issues).
      The admin processes will not change from 4.5 to r11.*

      In terms of time taken on the actual upgrade I reckon it’s taken 1 FTE, 6 Months work to Plan the upgrade from 4.5 to r11 (we’re also changing hardware so this includes builds etc). Which for a large enterprise isn’t too excessive. ALL of the extra time has been spent remediating the issues we’ve had with r11.

      I guess I miss spoke in my earlier comment when I said the issues were specific to us, they’re obviously not. However, the issues only have to be fixed once for everyone to benefit.

      regards
      Jon

      *The process is changing as we’re automating more with other tool sets, but they dont have to change as part of the upgrade.

    4. Hi Hendry – Very amusing and some good points.

      I don’t think we should overlook another hidden cost of changing tools by way of Admin Team headcount. Some tools that I’ve worked with do not allow end users to carry out even the simplest task on their schedules in any environment, leading to an increase in the headcount required to manage the schedules. This is a BIG plus for Autosys in that you can quite safely “distribute the management”. From personal experience I’ve seen another tool with comparable workload requiring 6 people against 2 for Autosys.

      I’m a bit puzzled by what seems like some peoples “fear” of r11 – yes it’s got a new architecture, but basically it’s the same.

    5. I guess that iXp is the spoiler (for faster performance) and iDash the parking sensor (warning me of impending impact). JAWS is an equally nice sensor but you’ve got to buy it from the main dealer.

      Or maybe iXp is the new paint job that convinced the Mrs and kids to be seen using the car? Is Alchemy is the furry dice?

    6. Further to Martin’s comments for “Astronauts” training try the Cevallos Consulting courses (http://cevallosconsulting.com/). They have partners delivering the courses in the US (e.g. Robert Mark) and Europe (e.g. Extra Technology). More AutoSys r11 training available from these guys than from CA at the moment.

    7. More AutoSys r11 training available from these guys than from CA at the moment.

      Not entirely true, CA now have about 4 training course for Autosys R11 which includes WCC R11. I have personally presented them on behalf of CA a few times already.

      Hendry

    8. Hi AcidDragon

      Just my thoughts but the 4 existing Cevallos Courses seem to be more comprehensive than the CA courses (CA’s WAC112 for example is only a 4 hour course and shouldn’t really count). Obviously I understand that CA will offer more courses later. CA typically have nicer training facilities too.

      Obviously each candidate must weigh-up both options. Just my 5 cents!

      Thanks

      Andy

    9. | Not entirely true, CA now have about 4 training course for Autosys R11
      | which includes WCC R11.

      Hendry – I confirm that the Cevallos Courses seem more comprehensive than their CA equivalents.

      | I’ve seen another tool with comparable workload requiring 6 people
      | against 2 for Autosys.

      RH – Can you say which tool that was? Last year I visited a UC4 reference site (Financial company) who claimed a similar reduction when moving from AutoSys to UC4.

      | I guess that iXp is the spoiler (for faster performance)

      Andy – Is iXp faster than WCC? I thought it’s main features were improved scalability and single-sign-on/security?

    10. I don’t understand Andy’s comment from 2 March: “JAWS is an equally nice sensor but you’ve got to buy it from the main dealer.” Who’s the “main dealer”? JAWS is available from CA, who resell the product. It is also available directly from us, Terma Software Labs, the vendor which develops and also sells the product directly.

    11. CA r11 Courses:

      03AUT20011: CA AutoSys® r11: Installation 200 3 days
      03AUT20021: CA AutoSys® Workload Automation r11: Foundations 200 3 days
      03AUT30011: CA AutoSys r11: Security Implementation 300 2 days
      03WCC20010: CA WCC r11: Workload Automation and Reporting 200 0.5 (web-based training) days

      Cevallos Consulting r11 Courses:

      CC111: CA AutoSys Workload Automation r11 Fundamentals 2/3 days
      CC211: CA AutoSys Workload Automation r11 Advanced Topics 2/3 days
      CC311: CA AutoSys Workload Automation Administrator 2 days
      CC411: CA AutoSys Workload Automation Security 2 days

    12. Re: Andy’s comment and Walters reply.

      I may have been misdirected or (more likely) misunderstood my CA rep but isn’t it the case that very large (international corporations) AutoSys sites can only buy JAWS from CA (not go directly to Terma Software Labs) due to stipulations set in CA’s resell agreement with Terma?

      In ideal world it only makes sense to buy a product indirectly if the reseller adds value but it’s not clear to me where CA adds value to a JAWS sale. Is the perceived benefit that the customer has access to CA Technical Support? Or perhaps that CA have JAWS certified consultants in their Solutions division?

      As a side issue – apart from CA Solutions are there any other services companies qualified/certified to work with JAWS outside of the United States?

    13. Mike,

      We are not certified, but Tayori Limited do do quite a bit of work with Terma here in the UK, I even presented with Walter at the last CA world.

      Hendry

    14. Hi Mike

      Extra Technology Ltd has 4 UK-based consultants trained in JAWS. We were trained at Terma Software Labs’ offices in Boulder by the Lab’s JAWS Experts. There is no formal certification as such (to my knowledge).

      We are happy to work with JAWS customers worldwide.

      Mark

    15. Thanks Hendry.

      Out of interest, how many JAWS/AutoSys consultants does Tayori Limited employ? Is Tayori Limited a CA Partner?

      Has your company taken a JAWS project from proof-of-concept, thru deployment and to the point where SLA alerts are automatically being sent to application teams?

      Has your company any experience of replacing a 24/7 IT Operations department with fully automated dark-site Operations?

      Mike

    16. Apologies to Walter if I caused any offence. I had been led to believe that JAWS has to be purchased through CA if you are a large corporation. Depicting JAWS and iDash as parking sensors was just following the original poster’s automobile analogy. Sadly with the recession, purchasing from anybody is highly unlikely anyway!
      Thanks for clarifying.

    17. I am not surprised that a good CA rep would imply that a “large corporation” can only buy the product through CA. 😉 However, that is simply NOT the case. In fact, the largest JAWS deal ever, period, was sold directly by Terma, not by CA. No offense taken, but it’s important to set the record straight.

      There are no stipulations in our contract with CA which require corporations to buy JAWS from CA. In fact, while some customers have chosen to buy at the 11th hour from CA for whatever reasons their purchasing departments have deemed important, it is also true that at least one (very large) JAWS customer who originally purchased from CA is now shifting their maintenance to Terma directly.

      Without making any further comments, perhaps Mike that might shed some light on your questions from 18 March above…

      As for formal certifications…true…we don’t hand out certificates (maybe we should), but there are a small handful of folks out there who know JAWS well enough for us to be comfortable recommending their services. That’s certainly the case for Hendry, as well as Mark and posse.

      There are a few options here Stateside as well, of course.

      Cheers all and thanks – you can see I don’t troll the boards that often – no time usually. You’re all welcome to email me directly at any point, and I promise to be responsive.

      Walter-
      walter@termalabs.com

    18. Hello all,

      I’m coming to this blog a bit late and I have only read the first two sections. This leaves me quite condused.

      We are a small Autosys user (1000 objects) and I hear about huge problems installing, no tools to convert existing workload and training needs.
      Is there a site where we can find a little more about what the problems actually are, how much the training costs and what tools exist to assist in the workload conversion (ex. does JIL actually work). The CA support site doesn’t seem to recognize our site since they converted it.

      Thanks
      RayB

    19. Simply want to say your article is as astonishing. The clarity to
      your put up is simply spectacular and i could assume you’re
      a professional on this subject. Well with your permission let me to take
      hold of your feed to stay updated with imminent post. Thank you one million and please keep up the enjoyable work.

    Leave a comment