Skip navigation
Previous Next

Tech Talk

August 2011
0

CA Workload Automation AE (formerly AutoSys) is used by hundreds of companies across the world to manage their critical distributed platform jobs.  For operations teams keeping an eye on these business critical activities, any jobs that stall or fail require immediate action.  CA Workload Automation AE provides two modes for monitoring jobs – eyes on glass using the dashboard, or email alerts when something goes wrong.  The challenge with the first approach is that it is people intensive and wasteful.  The second approach typically blasts out an email notification to a list of people who then have to connect back to the console from wherever they are to address the issue…..and all of this typically happens at 2am  when everyone is fast asleep (or at least shouldn't be focusing on their batch jobs).

 

Sound like a process that could be optimized?  It is.  Turns out that within the bounds of our existing partnership with CA Technologies we've already been addressing this very issue with other CA products – Spectrum, and Service Desk Manager.  xMatters relevance engines are designed to take critical events and get them into the right people's hands so that they can take corrective actions from wherever they are.  It directs alerts about events to people using knowledge of on call schedules, escalation rules, technicians' expertise, location, severity of issue, and more.  The alerts are all interactive and delivered via email, phone calls, SMS text messages, smartphones, and tablets.

 

So what does all that mean if you use CA Workload Automation AE?  You can now deploy a xMatters (IT) engine for CA Workload Automation AE (formerly Autosys) that brings these capabilities to bear when managing your critical jobs.  If a job fails in the middle of the night, Autosys can automatically pick up the phone, call the technical expert or application programmer who is responsible for that job, speak to them in any of 12 different languages, and give them the ability using touchtones to restart it.  The tech could do the same thing using SMS text messages, or with their tablet or smartphone without the need to drive into the operations center or power up a VPN connection.  No eyes needed to watch the console 24x7, no email blasts to people who can't do anything about the issue, no waking up the wrong person in the middle of the night.  As an added bonus, the relevance engine can also automagically provide a heads up to the key business stakeholders that an issue occurred AND that it had already been handled.  No more early morning calls starting with "Why didn't anyone tell me about ______?"

 

Now that's how you take down a zombie job plague before it gets out of control.

 

Abbas Haider Ali.

 

UPDATE: Check out the press release after the jump.

0

I'm based out in Washington DC and have lived on the east coast for a long time and as such have no experience with what an earthquake actually feels like.  That statement was true until yesterday afternoon at about 1:53pm EDT when I felt and heard a rumbling sound that was just a little too intense to be a passing truck.  It took me the first 5 seconds just to clue into what was actually going on.

 

Immediately after that, I realized that I actually have no idea about what I'm actually supposed to do during an earthquake.  My wife yelled at me to get into a doorway and I yelled back "I think we're supposed to go to the bathtub."  For the record, according to FEMA, here is what you're actually supposed to do.

 

Working with our clients all over the world, I get to hear about the varying experiences that they've had dealing with nature's display of its powers, at varying scales.  There was minimal damage from the quake itself, but I did get to experience first hand the communication threads that start up following any widespread event.

 

Before the shaking even fully stopped, my first status update of "Was that an earthquake that I just felt in DC?" was out on Facebook and Twitter (don't judge me).  It was quickly commented on and retweeted as confirmations started to come in from my friends/followers all across the east coast.  Within 5 minutes, all that I could see on Facebook were references to the earthquake.  Some providing details as they learned them, including images from the USGS website showing the intensity and epicenter of the earthquake.  Others were letting everyone know that they were OK.

 

In parallel, I texted family members to let them know that we were OK to preempt the inbound calls that would start as soon as the news got out.  I had to use text messaging, because I couldn't get a call through to anyone.  Lines were all jammed up and continued to be in that state on and off for another 2 hours.

 

Turns out that they never got my texts. And of course I had no idea that they had not heard from me. Luckily,while they were trying to reach me, my brother had seen the updates on Facebook and let them know that all was well.

 

What I learned from the experience simply backs up the strategy that I recommend to all of our clients.  Don't rely on a single, or even a couple of communications channels.  In the event of an emergency, prioritize and use all the channels at your disposal to ensure that the  right message gets out to the people that need it using the mechanism that they are likely to receive it through.  Every channel has its own reach and should be to dessiminate information into the right circles taking advantage of network effects to pass it along as needed.

 

What was your communication experience during the earthquake?  And yes, for all those on the west coast, we easties are very soft when it comes to the ground shaking beneath our feet.

 

Abbas.

0

If you're just joining in on the discussion of combining the rich deposits of personal data and social history that we're creating every day with technology for more effective communication, you might want to take a look at some of my earlier posts:

Part 1: Introduction

Part 2: Location

Part 3: Location privacy

 

What exactly is a social graph?  It's essentially a digital representation of all the relationships that we have online, explicit or implicit. What makes the social graph truly powerful though is that it's not just a repository of connections. In the most mature deployments, it's something that includes other information about all the interconnected people and can be queried by other systems.

 

What does all that mean? A version of your social graph cobbled together from all the services that you use would reveal family relationships, friendships, professional connections, shared interests, places where you get together with friends, birthdays, favorite movies, what time you're likely to be online, what products you like, and lots more.

 

If you're not yet convinced, consider the 3 largest sets of social graphs and what they might reveal about you: Facebook (750 million users), LinkedIn (100 million users), and email services (2 billion users).

 

Social clusters

 

 

Like most things, this powerful information can be used to provide innovative new services that individuals would want and gain benefit from, or they can be used badly to annoy, violate our privacy, and in ways that are just plain wrong.  If you're interested in the negative responses to growing use of social graphs, just search for "<company name> privacy controversy" and you'll find lots to work with.

 

For the purposes of this post, we'll try to stay focused on the good side of all of this information and go through a couple of use cases where social graph represents critical information about a person that allows them to receive and be a part of relevant communications.

 

Emergency Management

With earthquakes, fires, tornados, typhoons, and heat waves in headlines all over the world, there has been no shortage of disasters to put emergency management and communication to the test.  Where social graphs can be invaluable in communicating under these circumstances are the links that they provide between people.  If one of my coworkers evacuates a building safely with me, and we can provide that update into our social graphs, the natural clustering effect in our relationships will ensure that most people who would want to know that we are OK, will get that information.  Our professional graph through LinkedIn or an Enterprise 2.0 system knows about other coworkers & managers; through common Facebook connections our friends and family can be updated.

 

And that's for the simplest cases.  If you don't know someone's name who has been injured, the social graph can first help with identification.  Do you know where they work? Where they live?  What school they attend?  All of those are starting points to query a broader set of graphs to first identify the person and then notify the people who would want to know their status.

 

The social graph could also be a means of authenticating and determining who can see what information about me.  In the event of an emergency, I would be OK with providing transparent updates to my Facebook friends, it would be great to share some basic information with my LinkedIn connections, and may be share tagged updates with my Twitter and Google+ followers.

 

 

Customer Communications

Outside of targeted advertising (which is always a lightning rod for controversy), once you've done business with a company a few times, it might actually make sense to share limited access to your social graph with them.  Why?  The assumption here is that once you've done business with them you might want to trust them with more information about you so that they can help you make better decisions for the products & services that they offer.

 

Here's a personal example: I am terrible at remembering birthdays, anniversaries, and just about any other important dates in my life and those of my friends and colleagues.   I do however have all this information close at hand IF i remember to go looking for it - in Facebook, Plaxo, LinkedIn, Email threads lies all the information that I can never remember myself.  As an Amazon Prime customer, I buy lots of stuff there.  They also have a great recommendation engine.

 

Combining those things together, I would love to have a service delivered by a combination of Amazon & my social graphs that tells me when a special occasion is coming up and also based on that person's published interests/likes/dislikes/recent activity, what I might want to get for them.  The system would have to be tune itself based on my feedback of course for things like who gets a card, an actual present, an email, a FB wall post with a virtual present, and so on. 

 

It's a win-win situation.  Amazon gets me to buy more products, and I don't get in trouble for forgetting things. 

 

Other use cases

There is certainly no shortage of innovative services that crop up every week looking to take advantage of this wealth of information.  Whether it's advertising, movie recommendations, discovering new music, finding the next career opportunity, personalizing news content, picking classes in college, looking for help with homework, getting your writing proof read, reporters looking for sources, finding the hot new restaurant, picking up on style trends, just about any service you can think of benefits from a little social flavor.

 

A word of caution though, if you really want to make sure that you're exposed to new things, social graphs have to be diverse enough to avoid the dreaded Filter Bubble.

 

Stay tuned for the next post in the series as we continue exploring the impact (both good and bad) that personal data & social history have on our quest to better target communications.

 

And on a final note, if you'd like to join any of my social graphs, here's where to find me on a few services:

Twitter

LinkedIn

Google+ (click here if you need an invite)

I sign up for pretty much everything to try it out and consistently use "abbashaiderali" as my username.

 

Abbas Haider Ali.

 

 

image credit: SWAT Labs