Samenvatting-IT-as-a-Service.docx

Samenvatting: IT as a Service Introduction IT as a Service is the emerging technique that gives technology leaders the flexibility of providing the right set of services to the business. Chapter 1: Why you need IT as a Service Explaining the Transition of IT Transformations of IT organizations over...

Samenvatting: IT as a Service Introduction IT as a Service is the emerging technique that gives technology leaders the flexibility of providing the right set of services to the business. Chapter 1: Why you need IT as a Service Explaining the Transition of IT Transformations of IT organizations over past five decades: Timesharing: created to allow companies to buy time and capability from large complex systems Looked like cloud, worked well when computing needs were static but this model was too slow, too expensive and too inflexible IT in-house: results were well received, but massive changes in technology Public cloud: changed everything, but lack in agility Emerging companies leverage cloud services to create new product and service offerings TIP: IT leaders are using IT as a Service as a way to build alliances with business leaders so that IT can deliver the right services with the right service level at the right time. Defining IT as a Service IT as a service: an operational delivery model for providing IT services in a variety of consumptions models based on the requirements of the business at that time The Importance of Modular Services Move from a hierarchical computing model to a more flexible services model? requires modularity IT service provider needs to provide a catalog of services that can be linked together these services have to be orchestrated together to create business value Modular service: a clearly defined process that has no dependencies to outside services (includes API’s) The Value of the Hybrid Computing Model Hybrid cloud = the de facto approach for IT organizations that are adopting IT as a Service models allows companies to quickly change processes and compute requirements to keep up with the pace of business change Many approaches to adopting hybrid cloud, not one answer (depends on objectives and needs) Think about: security (customer info) costs (need consistent pricing method to compare options) breaking down barriers between on-premises and cloud-based systems Looking at Different Cloud Delivery Models Infrastructure as a Service (Iaas) The foundational cloud service IaaS provisions compute, storage, and networking services through either a virtualized image or directly on the computer systems Self-service environment: simply use credit card to purchase services (compute, storage, …) charged on amount of resources you consume you lose access to resources when you stop paying private IaaS: environment is controlled directly by company’s IT organization (security, access, …) Emergence of a Software‐Defined Environment (SDE) provides a next generation approach to IaaS goal of IaaS: optimize use of system resources so they can support workloads with maximum efficiency SDE: abstraction layer that unifies the components of virtualization in IaaS (so they can be managed in unified fashion) ! Remember SDE brings together compute, storage, and networking to create a more efficient hybrid cloud environment. It also allows developers to use a variety of types of virtualization within the same environment without the burden of hand‐ coding the linkages between these services. Software as a Service (SaaS) SaaS is an application that’s architected to operate as a cloud service Ease of use Fast delivery User not responsible for updates Platform as a Service (PaaS) PaaS is a cloud development platform that gives developers an underlying level of middleware services that abstract the complexity away from the developer The PaaS environment provides a set of integrated software development tools ! Remember A well‐designed PaaS consists of an orchestrated platform to support the life cycle of both developing and deploying software within the cloud. A PaaS platform is designed to build, manage, and run applications in the hybrid cloud environment. Business Process as a Service TIP: One of the benefits of a hybrid cloud environment is the ability to link business processes from a variety of services and systems in order to satisfy a customer need. Encapsulating business process allows teams to reuse prebuilt and tested processes. Rather than recoding common procedures, development teams can leverage predefined business processes. In an IT as a Service model, making business processes reusable allows development teams to focus on innovation and helps ensure that services will function in a predictable manner. Flexibility is key for companies that want to change a process when the business changes. Types of business processes: Mature and not likely to change (e.g. payment processes) Need to be able to be changed on the fly ! Remember Often customers demand that companies adapt their business processes based on what they see from emerging vendors in the market. As customer expectations rise, businesses must adapt to meet their customers’ expectations. Hybrid computing =/= single environment, but combination of resources Traditional data center Variety of public cloud services (IaaS, SaaS, PaaS, Process as a Service, and Data as a Service) Private services managed for a single company (without its own firewall or in securely managed service) The value of a hybrid computing environment is flexibility TIP: When you leverage an IT as a Service model based on a modular set of services, you have a lot more flexibility to move workloads based on issues, such as performance, security, or costs. Offering this level of flexibility can help transform the reputation of the IT organization. What is DevOps in the Hybrid Cloud? DevOps: a technique that combines the processes of dynamically creating applications in concert with the processing of deploying and managing those applications ! Remember DevOps requires both a technical change in how applications are created and a cultural change in how IT collaborates The focus on innovation Innovation = key to business change and transformation Software development: transformation from silos of deployment to a continuous life cycle model Flexibility at the core Organizations that have implemented DevOps are able to achieve following goals: Continuous innovation Continuous delivery Continuous learning ! Remember The end‐users (whether they’re customers or business users) don’t care how an application is developed, deployed, or monitored. A DevOps approach needs to be complemented with additional business process changes that support innovation and rapid customer feedback cycles The Importance of Automation IT as a Service requires the following automation services: Orchestration services (connecting on-premises systems with public/private clouds) Business policy services (direct users to the right IT service based on business requirements) Catalog services (all components have to be managed in a consistent and predictable manner) Workload balancing services (balance the workload of the systems, so performance is guaranteed) The Value of Brokering Services ! Remember IT as a Service must be a dynamic environment. The environment has to serve a variety of changing business needs. It also has to have the capability to manage and predict costs. The value of brokering is that it begins with a planning process to understand the needs of the business to be proactive combined with the constraints on costs and need for the right level of security and the right level of service. Policy-driven approach Cloud brokering: environment that acts as an intermediary between different cloud services; cloud broker provides self‐service IT across a variety of hybrid cloud environments, managed services, and data center services ! Remember The broker identifies a set of authorized services combined with business process and policy rules. After these services are in place, business units can freely use a self‐service portal to procure the right capabilities with the right service level and security that’s authorized by both IT leadership and the business. A well‐designed brokering environment provides the business with the choice and flexibility to use public, private, or data center services when needed. The environment can streamline the process of discovering, planning, managing, and governing computing services. In essence, this approach is analogous to a supply chain where all the individual elements come together to create a seamless process. The importance of planning Example given of situation where costs are much higher than expected “While it’s imperative to enable business unit leaders to move quickly to innovate, IT services have to be planned and managed so spending can be planned and controlled.” Chapter 2: Explaining the IT Supply Chain “Without an IT supply chain, you have a set of services that aren’t designed to work together in unison” Understanding the Value of a Supply Chain Supply chain: combination of all the resources, people, and activities that come together to bring a product or service to the customer to achieve the desired outcome ! Remember The successful supply chain requires an ecosystem of fully vetted participants. In addition, managers of that ecosystem must coordinate every element of the supply chain, including sourcing, shipping, parts management, manufacturing, and the final distribution of completed goods. The supply chain needs to be tightly coordinated with customer demands and expectation. The manufacturer must find a balance among satisfying customers, keeping manufacturing costs low, and making sure that there’s enough inventory. All the processes have to be in sync so the company is profitable, maintains the right level of quality, and satisfies current and future customer needs. A well‐designed supply chain is a system of organizations, people, activities, information, and resources that work in collaboration to successfully execute a company’s product creation and delivery of products or services. Defining the IT Supply Chain Organization moves to IT as a Service required to create a supply chain of products and services IT as a Service requires that an ecosystem of trusted services comes together and can work across a hybrid computing environment as though it were a single unified system Today’s disconnected silos Today a lot of departments in organizations have their own IT services from different vendors complexity, inefficiency, no economies of scale Shadow IT (common trend in companies where employees leverage technology resources without the approval or knowledge of the internal IT department) No department is an island Many connections between lines of business and partners linkages must be coordinated TIP: The only way to overcome these challenges is to create an IT supply chain that links all the business elements, as well as those of IT, together in a coordinated and predictable manner that supports business change and agility. Creating and Managing the IT Supply Chain IT supply chain made up of various parts from a wide number of vendors IT becomes the manager/broker of IT services to support business goals ! Remember A fundamental element of the supply chain is the constant change in supply and demand. Like a manufacturing supply chain, the IT organization must be able to predict demand in order to keep customers happy. For example, if your organization has initiative to engage customers via mobile applications, you need to make sure that your mobile application development and deployment platforms can scale to accommodate more users. In addition, make sure that your application management and operations platform is up to the task of monitoring more applications and interactions on a variety of devices. This process requires you to acquire the right performance management tools to ensure that the mobile applications are satisfying end‐user expectations. Core Foundations of the IT Supply Chain ! Remember These services aren’t stand-alone technologies; they’re managed and delivered as a set of integrated services. Each organization will have different supply chain elements based on business and customer requirements. Self-service portal IT as a Service =/= traditional IT model users given access to a self‐service portal where they can select the services they require Service orchestration help tie services together in an automated way Business process services allow developers to create new applications based on the way a business has to operate Application services Many applications to solve a wide variety of business problems Existing applications with important, complex business rules (should be left untouched) Applications that can be moved to different platforms (for flexibility and cost saving) Software as a Service Data services Companies want to lever key data sets in order to make better decisions data should be unified ! Remember To be effective, organizations are beginning to create data services that are designed to be able to be used outside of the way that data was created. These data services are designed for use in many different situations. For example, there could be data services that relate to product problem issues. Another data service may contain all the important information about all the products a company sells. These services can be offered as a service to both various divisions in a company or to key business partners in the IT supply chain. The importance of cognitive analytics system collects data of how the components operate this way system can learn and change based on best practices (detect anomalies) Integration and APIs Application Programming Interface (API): most important technique for creating new applications to support business goals in era of modular business services must be designed on standards to enable integration Cloud services IT as a service providing set of foundational cloud services Turning these services into IT supply chain supporting dynamic service catalog that identifies each service and its policies of use (who has access, …) Creating the Path Forward Working with IT as a Service in context of a supply chain means that business has reliable partner in IT IT supply chain does not happen in a vacuum! (collaboration with key business leaders) Chapter 3: Defining the Services Model Supporting a Hybrid Environment Hybrid environment: computing environment that includes a variety of public and private cloud services and a variety of managed services, combined with services from backend systems Begin with planning First understand how your current environment looks like strengths and weaknesses Collaborate with the business units and business strategists (to understand the changes) How a hybrid approach supports change Organizations need to be able to incorporate new cloud services based on changing circumstances A change might be the emergence of a new type of data integration service that will help business units break down silos between their organizations The Underpinnings of IT as a Service Most companies would love to start from scratch and build a modular service in a consistent way but variety of data center applications, departmental systems, private clouds, public clouds, managed services, and Software as a Service (SaaS) applications… = Complex world so road map to move from current state to more flexible future May include creating a “bi-modal” IT operation (combine traditional IT with more agile services) The Journey to IT as a Service You need to abstract complexity to have seamless customer experiences (e.g. self-service portal) ! Remember Keep in mind that not every organization can immediately implement IT as a Service. Effectively leveraging IT as a Service requires changes throughout the organization. The capability to move quickly depends on the level of maturity and modularity of your existing IT infrastructure and the elements you already have in place to support your goals. You also have to consider the changes in business strategy and what services you need to execute your plans. The value of transforming into an IT as a Service model is to make the task of developing applications become a much more industrial model with best practices and underlying technology services Life Cycle Management of IT as a Service ! Remember IT as a Service isn’t a static approach to managing your computing environment. You need to change your thinking about the overall IT environment and begin thinking in terms of life cycle management of services. In order to be successful with IT as a Service, you need to have visibility across the services and have an understanding of how all the pieces fit together. This is important because you are moving away from the traditional approach of managing each application or environment as if it were its own closed system. IT as a Service requires a context that encompasses all different types of services and how they can work together to support user needs. IT as a Service has 4 goals: Transparency: (ability to get available resources Measurability: (requirement to manage workloads and anticipate the future) Accounting: (ability to track which services are being used and how much they cost) Cost management: (ability to understand and compare costs) ! Remember Don’t think of each of these parts of the life cycle management as isolated issues. Instead, understand that they are all related to the best practice of creating an environment that will stand the test of time. If you adhere to these principles, IT becomes a true partner to the business because it addresses visibility and control that is imperative to the way business leaders think. The service catalog Service catalog: identifies and defines the services that are available for developers and users to meet business objectives (defines parameters and characteristics of services) Each service in the catalog must be carefully vetted (identified, tested, include rules, …) Data governance is key! TIP: One of the benefits of the service catalog is that it keeps the details of the service itself abstracted from the user of that service. The actual code is encapsulated into images, containers, or as microservices. The catalog also indicates how and when a service can be altered. Patterns and best practices Pattern: a copy of code or a database or an application service. Each pattern has a specific function that can be repeatedly deployed for a client (e.g. a virtual machine) same pattern can be used over and over again for different clients best practices create patterns Service automation and orchestration Intelligent automation: technique for bringing together the right services and then orchestrating them based on how they’re being implemented automation helps an IT organization keep a system healthy (by executing on service requests and monitoring overall performance) Orchestration = essential requires process management through use of APIs automation and orchestration = tools for linking services Brokering IT services Cloud broker: environment that acts as an intermediary between various cloud services Well-designed cloud broker provides a holistic model Benefit: provide comparisons between a variety of cloud services Service integration Integration of data and process! Integration as a Service: a hybrid integration platform that enables cloud applications or application services to be linked to each other and to on‐premises applications API management API: defined interface to a service/tool that helps develop programs through linking components together can be stored in service catalog There will probably be hundreds/thousands of APIs in the organization management is crucial! API management platform/portal enables centralized administration to make deployment easier and safer Chapter 4: Getting Started with IT as a Service The Business Requirement IT as a Service solution for shadow IT = industrial model for services creating this model starts with strategic alignment Strategic Alignment through a road map: Understanding the current state of the business and the supporting IT assets Coming to terms with what works and what needs to change Understanding how IT can become a set of services built with reusability in mind Focusing on the customer experience and the right key performance indicators (short term/long term) Setting guidelines for best practices, including economic viability, governance security, resilience, and predictable performance Understanding your workloads Make an effort to gain an objective understanding of the nature of your workloads Self-contained or modular? Do you need public cloud, private cloud or a combination? Do you have the computing power you need? ! Remember There are situations where workloads are complex and written as integrated applications tightly integrated with the hardware platform. Also, if your workloads are steady and don’t change frequently, an on‐premises deployment for your workload deployment helps. In this situation, your consumption patterns won’t change often. There is an important cost factor involved as well. It doesn’t make economic sense to simply move workloads to the cloud en masse. If this application works well for the business, there’s no reason to change. The Role of Standardization in Infrastructure TIP: One of the principles of IT as a Service is the ability to standardize through automation. If all your services are one‐off in every situation, you won’t be able to achieve economies of scale of the cloud. Therefore, consider what type of services you’re dealing with. For example, if an application has been optimized to operate in a specific hardware environment, it may not be economical to move that workload to the cloud. In that situation, there’s often a requirement for developers to manually change settings or configurations. Without a level of automation, creating an environment focused on IT as a Service can be difficult. Protecting Your Company Three factors that help you create a well-performing IT as a Service environment: Design security policies and controls as part of the IT as a Service fabric Implement data governance Manage the right service level Thinking beyond the Data Center Think about the customer service. How does your data center/cloud environment support the business? ! Remember When you begin to create an IT as a Service environment, you’re designing for change. What types of new services can you provide to customers that transform the business relation- ship? How can you make it easier for customers and partners to do business with you? Are there new services that will distinguish your products and services from those of your competitors? Can you be ready to disrupt a well‐established market? Creating a Sustainable Model Create service models that can be used repeatedly for different business needs ! Remember You need to perform all these functions each time you bring a set of services together to solve a new business problem. You also need to have a best practices model that helps developers create new reusable services when new ideas are put into practice. This new model differs from the traditional IT model because nothing is created in isolation. All services are a joint effort between the business and IT, so work collaboratively to support change and innovation. Managing for Predictability and Change IT organization = agent of change & true partner to the business Required: understanding of strategic objectives & availability/applicability emerging technologies IT as a Service = economic model that looks at the types of technology that will lead to real change combined with the costs of those technologies The Journey is Just Beginning TIP: Think about business process completely differently in this new model of IT. Business processes are guaranteed to change as the business changes. The most advanced and innovative companies understand that new business processes are the hallmark of innovators. As you look into the future, you’ll see the evolution of the IT organization as the broker of services. This means that IT will not only create or manage services but also make sure that services are designed to work together seamlessly. IT makes sure that its leaders are partners with the business in designing strategies that focus on digital disruption. ! Remember You don’t have to do everything at once. Select tasks and projects that will help prove the value of IT as a Service. Educate your team on the type of services you’re creating and how it can benefit from the agility and productivity of your organization for years to come.