ClearPath Application Blueprinting is a structured approach to evolving applications from the current (“as-is”) state to their future desired state (‘to-be”) using a Service-Oriented Architecture (SOA) enabling strategy. According to industry consultants like Forrester, mainframe organizations are well advanced in adopting SOA strategies.
So let me clarify our ClearPath strategy and directions: Many clients are in a current state of having large monolithic 3GL applications that are slow and costly to change. Our goal is to take our clients from this current state to an ideal future state by transforming these monolithic applications to modular, business services running on standardized Intel technology. Our plans are to do so in a low risk, evolutionary manner that minimizes client investment. Unisys is investing to port your applications to run on Intel and Unisys has plans to make the transformation of your legacy assets to modular business services both efficient & cost effective.
On the one hand we have the globalisation of business - reduced barriers to market entry, dramatic changes to business models and business processes – has seen enterprise growth arguably becomes the primary objective of company’s management team, but not at the expense of cost containment and control. Bob – you can speak to this slide for ever ….. The point here is to link it to the next slide where in essence the IT challenge is described: On the one hand IT is required to deliver IT service almost like a utility, cheaply and when and where it is needed Whilst on the other IT is being required to deliver sustainable competitive advantage and innovation for the business. This is the original text that came with this slide . Key Point: Business is dictating that IT executives focus in two directions: one on keeping the “lights on” and running IT as a utility service, and the other in terms of looking to IT for innovation and sustainable competitive advantage for the business.
Afraid I wasn’t up on my Greek Mythology – but Janus had to look in two conflicting directions at the same time. Key Point: Business is dictating that IT executives focus in two directions: one on keeping the “lights on” and running IT as a utility service, and the other in terms of looking to IT for innovation and sustainable competitive advantage for the business.
All software in use is legacy—it’s just a matter of degree. Even the 2-year-old Java application you have, that has been since modified a couple dozen times and the original programmers have moved on to greener green fields—that too is legacy. And legacy is not necessarily a bad thing. You can look at your existing software as in important asset to the business. It has value just because it works and supports the business, but more than that, it is usually customized to your needs, is well-tuned, and supports your critical business needs and competitive business practices. But this value comes at a price: The moment an application goes into product, it starts to accumulate liabilities. The technology gets old, and the skills required to maintain it become harder to find. The more an application is modified, the more spaghetti code it has, and it the more brittle it becomes when you try to change it or use it in a new way. It can even pose a problem when you try to replace it, because its roots run too deep--the business has become dependent on facets of the implementation that people have long forgotten exist, and you can’t easily cut over to a new system. In short, legacy software can become, at its worst, a costly barrier to business agility. But to discount the existing value and “throw the baby out with the bathwater” by replacing it without considering its value and the organization knowledge of business rules and process that it contains, can be a costly a foolish mistake. What we need to do is preserve the value of the legacy assets, while eliminating the liabilities, and that is accomplished through what we call architecture-driven modernization, or ADM.
“ Core Systems” can be evolved unless proved otherwise as opposed to Legacy Systems. And 2) We want to be involved in that technical evaluation and systems evolution. The essence of our discussion today is to review the claim that for the first time in our industry’s history we are being told that we should keep what we have and re-use it in combination with other new technologies to provide not only new ranges of functionality, but functionality directly based on the services executed by the business. (i.e. a service based approach to application evolution and modification – SOA is the guiding principle to achieving this).
Pervasive themes Governance and agility are major drivers of new IT initiatives and together generate momentum for both RTI and Open Source. Compliance, Alignment and Optimization Speak to ensuring that the behavior of IT systems and the investment that goes into maintaining them are a reflection of the business priorities and requirements. Often, projects are focused on key IT assets. These projects create the missing links between the business view and IT services Service Based Architectures, Standardization and Modernization Speak to creation of an easy-to-manage, fast-to-react environment to support business needs. Projects are focused in infrastructure elements and the objective is increasing levels of “dynamic” attributes and decreasing levels of manual effort
SaaS = Solution as a Service
The business functionality aspect and technology aspect overlap and SOA facilitates closing the business / IT gaps. 3D-VE allows us to model all elements that could be involved in SOA and close the gaps.
As part of a ClearPath SOA approach ClearPath applications may need to be transformed and improved to bring additional flexibility and shift investment more towards innovation. Using a multi-phase approach, core business applications can be transformed in a progressive and low risk fashion. And Unisys along with its partners has tools and services to help optimize the entire process. Depending on a client’s core competencies and business strategies Unisys and its partners can offer a wide range of options to sustain the new environment.
Unisys has identified five transformation styles that can be put together in various combinations to create the target, or “to be,” application. Discovery of existing assets is almost always required to progress to future transformation opportunities. The transformation styles are: Discovery of knowledge embedded in existing applications Refactoring (or improvement) of code Translation to different languages, platforms, or data models Wrapping of existing transactions or data Replacement by newly designed or packaged software Orchestration of software as part of business processes These styles can be used in various combinations to describe any given transformation effort.
This chart shows how the modernization needs of the client’s various applications may be mapped against the combination of building blocks that may be applied. Each application is dealt with individually only as part of the overall strategy for modernizing the entire application portfolio. This chart shows how a different combination of modernization scenarios may be applied to different applications. The various scenarios have been simplified here into 6 categories: Discovering means to gain understanding of the existing application and discover the knowledge it contains. All other scenarios require some amount of understanding of the existing application, although the type of knowledge that must be discovered varies depending on the which scenario needs the knowledge. I will discuss what that means in a few minutes. Refactoring means modifying or “cleaning up” source code without changing platform, language or its external behavior. That might be the only thing you do to an application if the only problem is that it is hard to maintain or change. But it may also be required to effectively wrap the application as a service and plug it into an orchestration of services. Translating means to convert the code into another language, such as converting COBOL to Java because you don’t have enough COBOL skills to maintain or improve it. There are automated tools to do this, but if you don’t also do refactoring, you will wind up converting spaghetti COBOL into spaghetti Java! Wrapping means to surround existing programs with an interface layer to expose its functionality as a service so it can be reused to easily construct new solutions. Sometimes this can be done without refactoring the existing application and sometimes a lot of refactoring is needed to make this work. Replacement means to eventually decommission an application and replace it with an entirely new solution. Even if the new application represents an entirely new vision of how to run the business, you still need to know something about what the old application does. Think of it this way: In the process of defining the new business vision and processes, the business architect has to interview a lot of people not just about what they want the future to look like, but also about how the business is run now—what is called the “as is” model. The problem is that the application “knows” things about the “as is” operation that people have long forgotten. You have to “interview the application” to get this knowledge, and the way to do that is use tools and methodologies to mine the application. Finally, orchestration means to integrate the SOA enabled legacy applications and/or newly created custom or packaged applications/components/services with the help of the orchestrating business processes implemented utilizing business process enactment and monitoring services. So how do you decide what gets done to which app when? You can’t look at each app in isolation and decide what is best just for that app. You need to look at it in terms of the overall architecture, as part the larger application portfolio management plan. And the question of when you do it is just as big as what you do. You can’t afford to do everything at once, and even if you could, the logistics of migrating the operation incrementally will likely dictate what can be done when.
When a SOA strategy is envisioned, an architectural approach to transforming applications is generally the best approach. For ClearPath clients Unisys is introducing Reference Architecture (RA) models for SOA enablement. The models provide visibility to help clients make clear decisions and insure that their business objectives are accelerated.
The objective of the Unisys 3D Blueprints for ClearPath SOA approach is to move applications forward from their current state (“As-is”) using a structured, best practices methodology to achieve the future state (“To-be”). The ClearPath approach to SOA enablement is comprehensive and integrates services, the newly developed Reference Architecture views, and a deep choice of technologies to insure that business objectives are met.
A Reference Architecture (RA) model is a view of a best practices approach to SOA enablement. There is a complete set for all types of SOA enablement strategies. Flexible choices for Java EE or .NET are available to expose ClearPath applications. Each Reference Architecture document is adjusted to the specific client requirements and then used to choose the appropriate products for implementation. This RA shows an OpenDTP model for Java EE SOA enablement on OS2200.
Using the Unisys approach to application transformation and SOA enablement provides an exclusive set of benefits.
Frameworks for Application Transformation and SOA Enablement ClearPath Core Business Transformation
ClearPath Strategy & Directions ClearPath RoHS Compliant Platform Next Generation Architecture ClearPath OS2200 & MCP NEXT GENERATION Operating Environments CMOS Intel Client Current State Client Future State Client ClearPath Core Systems & Legacy Assets Monolithic 3GL COBOL/ALGOL SOA Re-Factored COBOL/ALGOL/3GL Wrapped J2EE / .Net Services Java ClearPath – all on board to the “Future State”
ClearPath Announcement Focus 2006 Next-Generation Architecture Directional Announcement (Real-Time, Service Oriented Infrastructure) 2007 First Product Deliveries Based on Next-Generation Architecture New Offerings to transform applications based on Industry Best Practices Platform Focus Software Focus plus
A Rapidly Changing Business Environment The Demands on IT are rapidly Evolving Due to Significant changes in Business Models, Business Requirements, and Business Processes *Sources: CBDi
Economics: globalization demands flexibility
Business processes: changing quickly and sometimes outsourced
Growth: at the top of the CEO agenda
Reusable assets: Leverage what you have
Information: greater availability for Decision Making
The business requires technology leaders to anticipate and respond to these market challenges with relevant initiatives in both areas
Commodity Service Basic IT Services Keeping the “Lights On” Offshore / Outsourcing Competitive Advantage Business Agility IT Innovation Emerging Technology Business dictates that IT executives manage IT as both a commodity service and for competitive advantage – two very different requirements! IT’s “ Janus Effect ”: Deliver Basic IT Services AND Competitive Advantage New Solutions must support both of these Business Objectives Simultaneously “ Lower my costs!” “ Deliver new services!”
Re-defining terms…. SOA-Enabled Integrated Enterprise SOA Wrapper SOA Wrapper Enterprise Service Bus SOA Enabled Components Mainframe Client-Server Legacy Systems Mainframes Client - Server
Some Definitions Legacy Systems: “ Software systems become legacy when they begin to resist modification and evolution” Seacord, Plakosh & Lewis “Modernizing Legacy Systems” Addison Wesley 2003 Core Business Systems: “ Ones that support revenue generating transactions or are otherwise strategic in nature” Unisys 2007
‘ Using incremental development and delivery strategies and avoiding big bang investments, organizations can leverage their mainframe legacy assets and achieve strong business value as they evolve from yesterday’s architectures to tomorrow’s SOA-based foundation’.
Key criteria used to determine approach:
How well do existing applications fit future business needs?
Is there on-going support for the platform?
How does the application fit within the overall portfolio?
What are the costs, risks, and elapsed time to replace?
In most cases businesses opted to adapt/evolve applications through SOA technologies rather than replace
Key Themes Driving IT Projects Source: Unisys Corp. $B Operations expenses continue to grow and outpace growth in hardware spend. Compliance Alignment Prioritization SOA Standardization Virtualization Reducing Operation Expenses Strategic Business Restructuring TCO Business and IT Alignment Business Flexibility
Opportunity for provide exactly the business services that best match the business
Highest cost & risk
Buy or Rent a Package (SaaS)
Still may need to create your own service definitions
Even with pre-built service definitions you may not get a match to your business service definitions
Business Process Implementation Technology Implementation (how close to target environment) Rewrite or Replace Modernize Keep Add, Enhance Good Good Poor Schema to help in deciding how to handle an existing system
New & existing components collaborate to deliver required services
Components use mixture of technologies
Application Environments & Languages
Different H/W platforms
Pre-requisite existing systems are adaptable and open to change
Business Process Implementation Technology Implementation (how close to target environment) Rewrite or Replace Modernize Keep Add, Enhance Good Good Poor Schema to help in deciding how to handle an existing system
Seek to also encompass Strategic Business Transformation.
Proponents argue primary objective is about the design of your business.
Secondary result is a framework to better align IT with the Business (BPEL).
Assumption: the key to long term business success is flexibility.
That flexibility in turn is limited by the flexibility of the technology base on which your business runs.
Business Process Implementation Technology Implementation (how close to target environment) Rewrite or Replace Modernize Keep Add, Enhance Good Good Poor Schema to help in deciding how to handle an existing system Adapatable & Open to Change
ClearPath Strategy - An Evolution that Makes Sense
Retain and extend the value of applications to maximize business value
Reduce development costs through reuse
Improve system maintainability
Rapid response to new business challenges
Cost efficiencies in system management
“ As-is” Future Application State “To-be” Building on strengths of the past Transforming core business systems into modern, flexible business applications and processes with SOA Adoption
Business Logic Back Office Business Logic ERP Business Logic CRM Business Logic FINANCE “ Get Portfolio Balance” “ Transfer Funds” “ Execute Trade” “ Authenticate Users” “ Open Account”
Unisys and Service Oriented Architecture Page 3D-Blueprinting provides the visibility to identify and define services at the Business and Technology layers 3D-Blueprinting provides a framework and methods to model services at the Business Process, Application, and Infrastructure layers, creating a robust and aligned SOA implementation across the enterprise
Unisys 3D-Blueprinting EAM Approach Applies Concepts of Traceability and Visibility to Challenge of Modernization As-Is Business Model To-Be Business Model Business Domain IT Domain To-be applications New business needs As-Is Applications
3D Blueprints for ClearPath SOA 5 Step Process: 3D-Blueprinting Experiential Workshop Defined Strategy for Applications in Portfolio –Identify potential SOA candidates 1 Unisys Value-Add Approach End State Step 3D-Blueprinting Experiential Workshop Repeat – Application transformation is an iterative and incremental process; composite application evolution necessary to deliver newly minted services from existing a new applications 5 Next-Generation Server Architecture Implement to Desired End State – Deploy Service Oriented Infrastructure with application solution deployed – maximizing investment (through re-use and portability) and agility 4 ClearPath skills and tools (knowledge mining tools optimized for ClearPath; Agile Business Suite, ePortal) Abstraction – Rules Modeler, Knowledge Modeler Project Plan and Proof of Concept – Discovery and identification of application transformation style to be used (wrap, refactor, etc.) ; detailed plan; design and validation of plan 3 3D-Blueprinting ClearPath Application Workshop ClearPath Reference Architectures SOA Architecture for Highest Priority Application(s) – Create client specific 3D Blueprints for ClearPath SOA using reference architectures 2
Roadmap to SOA Transformation Assess App Hosting App Develop App Planning App Manage Management ClearPath Application Transformation Process Unisys and Partner Services and Solutions Discover Refactor Translate Wrap Replace Orchestrate Transformation Applications Portfolio Assessment Transformation Rationalize Sustain Rationalization Roadmap Rationalized Portfolio
Discover + 5 Transformation Styles “As-is” to ‘To-be” application Rationalize The composite solution using existing and new services (Generally outside of ClearPath) Orchestrate wrapped and newly replaced services 5. Orchestrate Selected new solutions that provide services that integrate with core business applications Replace applications with new custom or packaged solutions 4. Replace Portions of original application turned into components providing services Encapsulate cohesive functionality in a SOA harness 3. Wrap Application in the target language replicates functionality for composite applications Highly automated language-to-language translation 2. Translate Streamlined application with no dead code, no database redundancy, etc. Improve application without changing language or platform 1. Refactor As-Is model at the appropriate level of abstraction. Discovery is the core service for transformation projects Mine knowledge and abstract it to the right level Discover Results Definition Style
3D-Blueprinting Experiential Workshop to input business requirements and focus on a single project
ClearPath Application Assessment
Implementation views of ideal end point states for selected SOA transformation
Leverage Unisys experiences and expertise
Unisys services portfolio for SOA enablement
Unisys Solution Delivery Framework (SDF)
Services Delivery Framework Integrated with Product Choices
Web Services automation
Java EE service
Adapters and connecters for integration
Holistic framework for ClearPath SOA enablement Future Application State Unisys 3D Blueprints for ClearPath SOA ClearPath Reference Architectures (RA) for SOA Enablement Technology Depth and Alignment with RA
ClearPath Reference Architecture Web Services Example (OS2200)
05/06/10 Page The blueprints support a process that allows us to enhance the value of a client’s existing ClearPath applications by creating visibility for how they can integrate into the client’s SOA environment.
Client Benefits -- Core Business Transformation and SOA Enablement
Increase COMPETITIVE AGILITY by supporting new business goals and processes
Ensure UNINTERUPTED OPERATIONS by allowing old and new applications to coexist during an evolutionary transition period
Provide COST REDUCTION for application operations and maintenance
Provide RISK REDUCTION related to loss of legacy skills
Discover and preserve INTELLECTUAL PROPERTY hidden in existing applications and enables its REUSE
Provide a COMPREHENSIVE END-TO-END SOLUTION by leveraging Unisys and its partners’ innovations and skills