Ema Wla q2 2012 Radarreport CA

EMA Radar for Workload Automation (WLA): Q2 2012
Report Summary & CA Technologies Profile

By Torsten Volk, Senior Analyst Enterprise Management Associates (EMA) June 2012
EMA Radar for Workload Automation (WLA): Q2 2012 Report Summary & CA Technologies Profile
Table of Contents
Introduction ..................................................................................................................................... 1 Research Methodology...................................................................................................................... 1 What Changed Since the Q1 2010 Workload Automation Radar..................................................... 2 State of the Discipline in 2010..................................................................................................... 2 Progress since 2010...................................................................................................................... 3 Customer Perspective: Real Life Workload Automation.................................................................... 5 Shifting WLA Business Requirements............................................................................................... 7 Workload Automation and Cloud..................................................................................................... 7 Core Capabilities in 2012: Its all about the Business Service............................................................. 8 Architecture & Integration........................................................................................................... 8 Architecture.......................................................................................................................... 8 Integration........................................................................................................................... 8 Functionality................................................................................................................................ 9 Deployment & Administration.................................................................................................... 9 Deployment......................................................................................................................... 9 Administration..................................................................................................................... 9 Cost Advantage............................................................................................................................ 9 Vendor Strength........................................................................................................................... 9 Vendors Included in this Report...................................................................................................... 10 Traditional WLA Vendors.......................................................................................................... 10 Challengers................................................................................................................................. 10 Specific Solution Vendors........................................................................................................... 10 Workload Analytics.................................................................................................................... 10 Evaluation Criteria .......................................................................................................................... 10 EMA 2012 Workload Automation Radar Results............................................................................ 11 Key Changes Compared to the 2010 WLA Radar Report......................................................... 11 Value Leader: CA Technologies.................................................................................................. 12 CA Technologies Profile................................................................................................................... 12
I
2012 Enterprise Management Associates, Inc. All Rights Reserved.
Introduction
In todays age of cloud and IT-as-a-Service, the importance of Workload Automation (WLA) as the evolution of job scheduling, and its sister discipline IT Process Automation (ITPA), has grown tremendously. As a new chapter opens in enterprise IT, where business-unaware technology silos no longer count as a valid excuse for SLA violations1, the ENTERPRISE MANAGEMENT ASSOCIATES (EMA) team regards automation WLA and ITPA as the glue that keeps business processes tightly integrated. Operating systems, middleware, databases, applications, and business services are simply technical necessities that must be orchestrated to support and streamline these business processes in the most efficient manner. While this EMA Radar Report is focused on WLA solutions, the integration of these individual software packages with ITPA constitutes an important evaluation criterion, as the separation of both disciplines WLA and ITPA is an artificial one. To truly automate entire business processes, WLA and ITPA have to work together harmonically. a) WLA is commonly considered an activity that takes place deep in the data center, controlled by an inner circle of aging mainframe wizards, also often referred to by business stakeholders as the data center mafia. The data center mafia usually knows very little about the business impact of WLA and is notorious for only contacting business stakeholders to let them know why a certain request cannot be fulfilled in a timely manner. b) ITPA, often also referred to as run book automation, can be described as the automated execution of a set of tasks to address a specific planned or unplanned situation. All the various steps that have to be taken for processes such as staff onboarding, application release management, or weekly backups fall under ITPA. Since the previous EMA Workload Automation Radar Report in 2010, most vendors have recognized the above requirement to integrate WLA and ITPA in order to effectively support business processes.
Research Methodology
The major challenge of this type of market evaluation is to avoid creating a simple feature comparison. EMA is aware that in order to be valuable for the end customer, any analyst report must thoroughly research and consider the client perspective. Enterprise IT is generally about solving actual customer challenges. Therefore, each software feature is only relevant for this report, if it solves a specific and important business problem. To remain entirely objective, this EMA Radar Report is based on a comprehensive survey with over 600 data points that can, for the most part, be measured unambiguously. All survey questions were founded on customer feedback and vendor responses, and thoroughly verified by a sequence of product demonstrations and end customer interviews. EMA acknowledges that in WLA, as well as in most other arenas of enterprise IT, there is no one best solution for every customer. Therefore, EMA has evaluated each product along five dimensions: 1. Functionality 4. Cost 2. Architecture & Integration 5. Vendor Strength 3. Deployment & Administration
1
Service Level Agreement - For more detail on the importance of SLAs, please take a look at the following article: http://www.enterprisemanagement.com/web/ema_ac0312.php
1
Based on these five dimensions, a potential client might select a solution that offers only average scores in terms of functionality, but is easily deployed, requires minimal maintenance, and costs significantly less than some of the functionality leaders. Providing guidance along these five dimensions will enable potential clients to determine which solutions to look at more closely. This can mean narrowing down the field to only three vendors, or it could mean to also include lower cost alternatives into the RFP process. This report will have achieved its purpose, if EMA has provided the potential WLA customer with the background knowledge and guidance necessary to confidently make this pre-selection decision.
What Changed Since the Q1 2010 Workload Automation Radar

State of the Discipline in 2010
The previous EMA Workload Automation Radar Report was released in the first quarter of 2010 based on data gathered throughout Q4 of 2009 and revealed the following key findings:
Many vendors had achieved excellent job scheduling capabilities, but only few were able to offer even basic ITPA and business integration capabilities.2 No vendor was able to include advanced SLA-capabilities that were driven by predictive analytics algorithms and able to autonomously manage the critical path (see Figure 1).
2
Business integration is referred to as the ability to link IT services to business requirements (Business Impact Analysis).
2
Figure 1: 2010 WLA Radar Findings
As Figure 1 shows, WLA in 2010 was still a long way away from being able to truly automate entire processes. Technology silos, a lack of awareness of a workloads business impact, and a lack of predictive analytics capabilities did not allow customers to achieve their ultimate goal of resource optimization and agile IT services delivery.
Progress since 2010
When reevaluating the marketplace over two years later, significant progress can be seen compared to the 2010 WLA Radar Report (see Figure 2). Cloud and the concept of service-driven IT were the main catalysts for this progress. Resource optimization: It is the main goal of any organization to receive the best possible ROI from its IT investments. To realize this ROI, each physical resource has to be utilized to its optimal degree and waste has to be eliminated. To achieve optimal usage, all storage, network, compute, and software resources have to be pooled. Through pooling, these resources are abstracted from their underlying physical infrastructure and therefore can be dynamically assigned to users almost in real time. This ability to rapidly distribute enterprise IT resources based on near real-time requirements brings the data center one important step closer to resource optimization. IT Process Automation: Automatically provisioning, managing, and decommissioning hardware and software resources, based on end user requests issued through a service portal ensures the ultimate degree of IT agility. This agility allows the organization to turn IT into a true business differentiator, by enabling end users to proactively utilize IT resources to the companys advantage.
3
Business Integration: Since the 2010 Radar, there has been significant progress in terms of integrating WLA products with the overall business management environment. Most vendors now offer connectors for service management solutions, CMDBs, BI & Big Data packages, systems management software, as well as for VMware vSphere and for the Amazon EC2 cloud. WLA has come a long way from being an isolated discipline to becoming a good citizen that is well integrated with its neighbors in the data center and in the cloud. Predictive Analytics: The fact that five out of this years six Value Leaders either offer their own predictive analytics engine or integrate with Terma Software Labs JAWS3 analytics solution shows the tremendous progress that was made in workload analytics since the last Radar Report. Vendors have recognized that offering predictive analytics is a true differentiator for their products, as it is a critical precondition for making WLA business process-aware. Job Scheduling: Job scheduling already was mature at the time of the previous Radar Report. However, EMA can still report minor improvements in terms of job triggers, alerting, and API comprehensiveness this time around.
Figure 2: WLA Maturity in 2012
See page 14 for more detail on JAWS.
4
Customer Perspective: Real Life Workload Automation
There often is a significant gap between what analysts and vendors claim is important in WLA and what customers actually ask for. During the course of creating this research report, EMA has talked to countless vendor representatives, but even more importantly, to numerous actual customers. The gap between where customers currently are in their IT evolution and where analysts and vendors think they should be, is best described by taking a brief look at EMAs maturity model for WLA (see Figure 3).
Figure 3: EMA WLA Maturity Model
Most of todays enterprise customers have achieved a state of consolidated job scheduling where most or all batch jobs are centrally managed, dynamically triggered based on various types of events, and able to manage the transfer of files. Faced with user demand for IT-as-a-Service, more and more businesses are starting the journey to a more proactive and connected approach, also referred to as journey to the cloud. This journey
5
includes the addition of ITPA components, a business portal (dashboard), the ability to prioritize WLA issues based on their business impact4, intelligent event correlation to identify events that are relevant to a specific problem, and finally, some form of CMDB.5 Dynamic Automation (heuristic thresholds, SOA, ease-of-use) and Resource Optimization (Resource Pools, Automated Provisioning, Load Balancing) at the very top of the maturity model, can be considered as the ultimate goals of workload automation and enterprise IT in general. The growing education around and adoption of cloud has contributed to a rapidly rising awareness of the importance of data center automation and resource optimization. When talking to WLA customers, EMA has found that there is no such thing as a general homogenous state of the discipline. In many cases, even some of the largest WLA deployments have not even considered the adoption of any advanced WLA technologies that go beyond simple batch scheduler consolidation. In other instances, EMA found that advanced analytical capabilities are deployed and end users are able to monitor relevant workflows through a business portal. Due to this heterogeneity of user requirements, there can be no one best WLA solution for everyone. EMA encourages readers to keep in mind their organizations workload history, maturity, and specific requirements, when looking at the various evaluation charts and vendor profiles that are featured in this report (see Figure 4).
Figure 4: Formula for WLA Requirements Profile
The sobering fact that a majority of organizations still refers to WLA as job scheduling demonstrates the importance of considering this formula, before committing significant funds to acquiring a WLA package.
4 5
Business Impact Analysis EMA is aware of the controversy around the term CMDB; however, in order to effectively manage change within a large enterprise IT environment, there must be a system in place that automatically tracks these changes and issues alerts, when vital dependencies are in the process of being violated.
6
Shifting WLA Business Requirements
The reasons for many organizations to move up the WLA maturity model described in the previous paragraph result from increased business stakeholder demands: Shorter batch windows: As most IT organizations are required to provide 24x7 access to real-time data-driven enterprise applications, batch windows are constantly decreasing. It is no longer acceptable to restrict access to entire business applications during off-peak hours, while the necessary background processing happens. Immediate processing requests: In the early mainframe days, batch jobs were often only processed once per week, month, or even quarter. In modern enterprise IT environments, users often expect instant or near instant results, when they submit service requests. Transparency: Today, it is often no longer acceptable for business stakeholders to learn of workload problems when business critical applications fail, due to a lack of input from the WLA system. In many organizations business service management (BSM) dashboards still turn a blind eye toward WLA. This often leads to unanticipated application failures, as missed job processing windows are not monitored. Service Level Management: When SLAs are missed, there mostly is a direct cost to the organization, as well as an opportunity cost. The direct cost can usually be translated into a dollar value, while the opportunity cost is often expressed in terms of customer dissatisfaction. Regulatory requirements: PCI DSS 6, HIPAA 7, and SOX8 are three common types of regulations that modern organizations are routinely audited for. Therefore, it is essential for WLA solutions to provide comprehensive audit trails of all job streams. Documentation: In reality and despite all the talk about true WLA as opposed to job scheduling, scripts Perl, Cron, Windows and application and operating system specific schedulers are still around in most companies. This often leads to documentation nightmares, resulting in serious business challenges when staff members leave the organization. These business demands all go in line with todays trend toward IT-as-a-Service or cloud, where resources are available instantaneously, for example through Amazon EC2 or Salesforce.com.
Workload Automation and Cloud
The term cloud can be described as a new IT paradigm, making data center resources available to developers and business users, in a near real-time manner. This almost instantaneous availability of resources and applications allows business stakeholders to harness IT to quickly implement solutions that translate into strategic differentiators for the organization. In order to implement a private or hybrid cloud, the following core components are needed: a) Virtualization b) ITPA and WLA c) Self-service portal
Payment Card Industry Data Security Standards Health Insurance Portability and Accountability Act of 1996 8 Sarbanes-Oxley Act of 2002
6 7
7
A virtualization layer is introduced to pool the data centers compute, network, storage, and software resources. Pooling these resources makes them granular and portable, so that they can be easily combined and provisioned based on specific end-user requests. In a nutshell, introducing the cloud to the organization results in the elimination of technical and technological excuses for why a business critical IT project may not be feasible. Considering the criticality of many of these IT projects within todays business environment, eliminating project barriers often has a direct impact on the corporate bottom line. The corporate cloud consists of numerous point solutions service catalog, charge back, provisioning, monitoring, lifecycle management, patch management, asset management, configuration management, compliance management that are tied together into one consistent self-service offering by WLA and its sister discipline ITPA. In the ideal case, most end-user requests can be fulfilled in a self-service manner and in near real-time.
Core Capabilities in 2012: Its all about the Business Service
During this years WLA Radar research, EMA has determined a balance between current WLA requirements as they are perceived by end users and requirements guided by recent developments in enterprise IT, such as the rise of the cloud and advanced business service management. Please keep in mind that these categories were weighed differently, depending on their importance to a businessdriven WLA solution.
Architecture & Integration

Architecture
Disaster protection Process automation capabilities Workload virtualization and distribution System interfaces: GUI, web service, mobile application, command line, Windows client Scalability, performance and reliability
Integration
Platform support BI and Big Data support Cloud support Enterprise application integration Comprehensive API Cloud and virtualization platform integration Managed file transfer
8
Functionality
Critical path monitoring Predictive analytics and forecasting Service level management and business awareness Self-service portal Triggering and conditional logic Alerting Security model What-if scenarios Auto remediation Logging and auditability Ease-of-use Mobile device support Help resources Root cause analysis
Deployment & Administration

Deployment
Ease-of-implementation Conversion tools Job stream discovery Training requirements
Administration
Console ease-of-use Upgrade process Lifecycle management Automation of management
Cost Advantage
Flexibility of cost model Transparency of cost model Cost for various scenarios Administration cost Implementation cost Integration cost Vision Strategy Financial strength Research and development Channel and partnerships Market credibility
Vendor Strength
9
Vendors Included in this Report
Traditional WLA Vendors
Todays WLA marketplace can be divided into three major segments:
These vendors conceived their WLA products during the mainframe days in the 1970s and 1980s. Over time, each one of them acquired capabilities to provide WLA for distributed environments. All traditional WLA vendors also offer a full portfolio of business service management solutions. At the time of EMAs evaluation, numerous critical updates to the IBM Tivoli Workload Scheduler were pending release. As the platform was still evolving, IBM declined to participate in the product comparison. Members of this group: ASG, BMC, CA Technologies
Challengers
These are newer solutions that lack the deep experience and massive legacy deployments of the four traditional vendors, but often bring disruptive new elements to the table, such as lifecycle management, advanced analytics, easy-to-use Web-based user interfaces, or agents that can be combined with multiple scheduling servers. Members of this group: ASCI, Cisco, MVP, ORSYP, Stonebranch, UC4
Specific Solution Vendors
Members of this group offer attractively priced solutions that apply to more specific problem sets, such as Windows-only scheduling, advanced file transfer, and advanced business workflows. Members of this group: Arcana, Flux, Network Automation
Workload Analytics
Terma Software Labs (Terma) plays a distinct role within this EMA Radar, as Termas software provides real-time predictive analytics and service level monitoring for three of the above vendors: CA Technologies, Cisco, and Stonebranch. Terma JAWS can be seen as an add-on, transforming these three WLA solutions, into truly business aware automation tools.
Evaluation Criteria
Each product feature had to fulfill the following three criteria to be credited with a capability score: General availability: The features needed to be generally available with the solution set at the time of the evaluation. Features that were in beta testing or were scheduled to be included in later releases of the management suite were not eligible for consideration. Included in Cost: All features that were part of the evaluation had to also be priced into the total product cost. For example, if one vendor included connectors for BI and Big Data with the standard product package, while another vendor offered these connectors at an extra cost, EMA added this extra cost to the pricing for this report. Documentation: All reported features had to be clearly documented in publicly available resources, such as user manuals or technical papers, for verification.
10
EMA 2012 Workload Automation Radar Results
The total product value is defined by comparing the overall product strength of each WLA solution (y-axis of Figure 5) with its cost efficiency (x-axis of Figure 5). Product Strength combines evaluation scores for Functionality and Architecture & Integration, Cost Efficiency is calculated from the scores achieved from the Cost Advantage and Deployment & Administration categories. The size of each vendors bubble indicates the vendor strength as identified in the individual reviews.
Figure 5: WLA Bubble Chart
Key Changes Compared to the 2010 WLA Radar Report
When comparing the new chart with the previous one that was compiled in 2010, EMA can make the following observations: This time, EMA included four additional vendors: MVP, Flux, and Network Automation. Stonebranch and Opswise merged. CA Technologies and Cisco are now Value Leaders. ASCI has jumped from its old location close to Selective Value to its new location, bordering the Value Leader category.
11
Value Leader: CA Technologies
CA Technologies: With its vast customer-base, comprising of numerous global organizations across all industries and with a functionality score very close to BMCs, CA Workload Automation is one of the premier products in this field. Due to excellent process automation capabilities, integration with Terma JAWS for workload analytics, solid integration with CA Technologies ITSM portfolio, very good cloud support, and its service oriented architecture that can easily be integrated with the clients existing enterprise IT infrastructure, CA Technologies has obtained the status of a Value Leader in this WLA Radar Report.
CA Technologies Profile
Introduction
CA Technologies was founded in 1976 and changed its name from Computer Associates International, Inc. in 2006. CA Technologies obtained the AutoSys distributed job scheduler through its $3.5 billion acquisition of Platinum Technology International in 1999. AutoSys was originally developed in 1992 by AutoSystems, which was acquired by Platinum in 1995. Today, CA Technologies distributed scheduling solution is called CA Workload Automation. CA Technologies has a deep workload automation portfolio with CA Workload Automation AE for distributed platforms, and CA Workload Automation CA7 Edition, and CA Workload Automation ESP Edition for mainframe environments. All CA Workload products are centrally controlled through CAs Workload Control Center. In the early 1990s, AutoSys was one of the first workload automation products to enable resource pooling (workload virtualization); a long time before the emergence of the cloud. 12
Architecture & Integration
Due to its service-oriented architecture, CA Workload Automation can centrally manage a vast variety of enterprise workflows and integrates with all major applications, databases, and development frameworks. CA Workload Automation is part of CA Technologies broader ITSM framework (see Figure 10), tying together infrastructure components servers, networks, storage, applications, and private and public cloud resources through network, server, and client automation, and configuration management. CA Workload Automation, CA Process Automation, and the AppLogic Cloud Platform are built upon this infrastructure layer, providing the automation and orchestration capabilities required for application and service delivery. Operations Insight delivers dashboards with business relevant IT metrics, while Capacity Management and Analytics offers SLA-driven capacity management for the entire framework.
Figure 10: CA Workload Automation Architecture
CA Workload Automation is able to dynamically place workloads across physical, virtual, and cloud - public or private - environments, based on cost and SLA considerations. Additional resources can be allocated to ensure service level compliance. CA offers five so-called Process Automation Power Packs, allowing workload customers to mechanize common IT process automation tasks Cloud Burst, Lifecycle Management, Remediation, Self Service, and Health Check without adding CA Process Automation to their infrastructure. CA Workload Automation integrates with CA Capacity Manager and CA Virtual Placement Manager to forecast future hardware, network, and storage requirements for processing workloads compliant with corporate SLAs. For advanced service level monitoring, CA Workload Automation works with Terma Software Labs JAWS (JAWS) see company profile on page 14 and for mobile emergency management, integration with the xMatters relevance engine is provided.
13
Functionality
CA Workload Automation features a robust set of job triggers and alerting features, as well as strong auto-remediation capabilities. Designing complex job streams is relatively simple, despite the slightly dated user interface. CA offers a strong security model that allows handing over control to end users, based on transparent policy and governance processes. Providing secure access to business stakeholders, based on consistent policies, can be regarded as a key strength of the CA product. A major reason for CA Workload Automation to be one of the winners of the 2012 Workload Automation Radar Report lies in its integration with Terma JAWS. In combination with JAWS, the CA product is not only robust, versatile, scalable, and well performing, but convincingly ties together workloads with their corresponding business requirements. Providing health and performance information not only to the data center, but also to affected line of business stakeholders, can be considered as the final frontier of workload automation.
Deployment & Administration
CA offers the widest range of legacy software conversion utilities of any vendor, facilitating workload conversion from BMC, IBM, ASG, ORSYP, Redwood, Cisco/Tidal, Stonebranch, and UC4. Similar to its main competitors and due to the comprehensive but fragmented character of the CA solution, the software installation and configuration requires a significant implementation effort. CA Technologies has announced improved implementation times with the upcoming r11.4 release. The Workload Control Center ensures a consistent and coherent user experience across the mainframe and distributed versions of CA Workload Automation. Unlike Cisco Tidal and Stonebranch, CA has at least partially integrated the JAWS workload performance dashboard, instead of relying on a purely external user interface.
Cost Advantage
The licensing cost and implementation timeframe for CA Workload Automation are in line with its main competitors IBM, BMC, and ASG. CAs licensing model is granular and transparent, exclusively based on the number of clients or on the volume of MIPS in case of a mainframe deployment. Per task pricing would be desirable for increased flexibility. Combining CA Workload Automation with the JAWS software can significantly decrease administration cost, due to considerably improved critical path visibility and transparent mapping of jobs to SLA-relevant business goals. JAWS also sends out prioritized alerts, based on SLA goals for more targeted issue resolution.
Vendor Strength
With over 2,500 customers, CA Workload Automation is one of the most popular enterprise workload automation solutions. CA Technologies achieved revenue of $4.4 billion and $827 million of profit in 2011. CAs vision of integrating workload automation with process automation and service management shows that the company has clearly understood the trend toward an agile IT-as-a-Service model. A preview of CA Process Automation 4.0 has provided EMA with a glimpse of what there is to come from CAs end regarding fully integrated and orchestrated business process automation.
14
Strengths & Limitations
Strengths
Vast customer-base: CAs long history in the enterprise scheduling marketplace has translated into a considerable number of very large customer accounts. Global banks, aerospace & defense organizations, and major retailers are only a few examples of CAs impressive customer base and evidence of the high level of trust placed in CAs security model and architecture. Scalability & performance: When talking to CA Workload Automation customers, scalability and performance are often named as some of the key reasons for relying on the CA product. The credibility drawn from its reputation for scalability and reliability is an important asset to CA when it comes to competing for new accounts. Pre-configured process automation power packs: CAs process automation PowerPacks constitute a strong value proposition, by connecting workload automation with critical process automation elements, such as cloud bursting, lifecycle management, problem remediation, self-service, and health checks. Excellent security model: The CA Embedded Entitlements Manager supports Active Directory and LDAP for easy administration and allows the definition of fine-grained security roles. This enables the customer to create and assign precisely scoped user roles for optimal division of duties and to satisfy audit requirements. Service Oriented Architecture: As described in the Architecture & Integration section, CA Workload Automation was designed with a service oriented approach. This ensures the optimal integration of workloads with enterprise applications.
Limitations
User interface in a need of an update: In recent product releases, such as version 4 of CA Process Automation, CA has impressively demonstrated its ability to create modern and easy-to-use graphical interfaces. Along these lines, CA Technologies has announced a significant overhaul of the dated interface of CA Workload Automation with the upcoming version r11.4. Perceived lack of innovation: CA Workload Automation customers sometimes talk about a lack of innovation, when asked for concerns regarding their workload solution. EMA has found that this perceived lack of innovation is often not well founded in reality, as CA Workload Automation offers one of the strongest feature sets in the market place.
15
About Enterprise Management Associates, Inc.

Founded in 1996, Enterprise Management Associates (EMA) is a leading industry analyst firm that provides deep insight across the full spectrum of IT and data management technologies. EMA analysts leverage a unique combination of practical experience, insight into industry best practices, and in-depth knowledge of current and planned vendor solutions to help its clients achieve their goals. Learn more about EMA research, analysis, and consulting services for enterprise line of business users, IT professionals and IT vendors at www.enterprisemanagement.com or blogs.enterprisemanagement.com. You can also follow EMA on Twitter or Facebook. This report in whole or in part may not be duplicated, reproduced, stored in a retrieval system or retransmitted without prior written permission of Enterprise Management Associates, Inc. All opinions and estimates herein constitute our judgement as of this date and are subject to change without notice. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies. EMA and Enterprise Management Associates are trademarks of Enterprise Management Associates, Inc. in the United States and other countries. 2012 Enterprise Management Associates, Inc. All Rights Reserved. EMA, ENTERPRISE MANAGEMENT ASSOCIATES, and the mobius symbol are registered trademarks or common-law trademarks of Enterprise Management Associates, Inc. Corporate Headquarters: 5777 Central Avenue, Suite 105 Boulder, CO 80301 Phone: +1 303.543.9500 Fax: +1 303.543.7687 www.enterprisemanagement.com
2480_CA.062712

Ema Wla q2 2012 Radarreport CA

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ema Wla q2 2012 Radarreport CA

Hochgeladen von

Copyright:

Verfügbare Formate

EMA Radar for Workload Automation (WLA): Q2 2012

Report Summary & CA Technologies Profile

What Changed Since the Q1 2010 Workload Automation Radar

Figure 1: 2010 WLA Radar Findings

Progress since 2010

Figure 2: WLA Maturity in 2012

See page 14 for more detail on JAWS.

Figure 3: EMA WLA Maturity Model

Figure 4: Formula for WLA Requirements Profile

Workload Automation and Cloud

Core Capabilities in 2012: Its all about the Business Service

Architecture & Integration

Deployment & Administration

Todays WLA marketplace can be divided into three major segments:

Specific Solution Vendors

Figure 5: WLA Bubble Chart

Key Changes Compared to the 2010 WLA Radar Report

Figure 10: CA Workload Automation Architecture

Deployment & Administration

About Enterprise Management Associates, Inc.

Das könnte Ihnen auch gefallen