Software deployment is the process of realizing value from purchased software. It is the process of putting software and software solutions into place to ultimately drive business success. These and other perspectives have a common theme: that software is an investment; one that can only be measured in terms of cost until it is successfully deployed and used.
IBM engages our clients to assist them in deployment monitoring , tracking and planning. Our goal is to improve our client’s experiences in deployment and adoption of IBM software and streamline the touch points in the process (One IBM).
Deployment engagement with our clients drives:
- Identify opportunities for the alignment of IBM software in their overall technology solution
- Facilitate the successful deployment of IBM software by coordinating the extended IBM team
- Identify and help realize the intended business value of the solution
Typical deployment challenges - Realization of value
Experience in deploying software reveals that many company’s are not taking the necessary steps to achieve business value, for example:
- A deployment strategy was not mapped out
- Early projects were not identified, and the scope and schedule of software implementation were not considered
- The transition plan from the purchasing team to the implementation team did not clearly articulate expectations, roles, and responsibilities
- Identified deployment projects did not occur on schedule
- Software deployment is inherently complex. It involves multiple components and organizations
- reactive project management resulted in delayed implementation due to challenges that arose late in the deployment process
The lack of focus in these areas has resulted in less than optimal deployment performance. It has also spawned situations where multiple projects are run in parallel with inadequate infrastructure or mechanics to leverage common components, tasks, resources, lessons, and so forth.
Addressing challenges for successful software deployment
These experiences suggest that successful software deployment, both in the actual deployment and the identification of opportunities, does not just happen. It requires proactive focus and attention in the following areas:
- Qualifying the initial demand (projects)
- Identifying the core team, both IBM and client, that will coordinate the overall software deployment process
- Developing a deployment strategy
- Defining additional projects that can help the company overcome new challenges using purchased software
- Proactive monitoring and tracking of deployment against schedule and goals
Many components go into creating successful software deployment. In general, software deployment is influenced by a combination of the following:
- The companies business and IT requirements
- The contracted offerings (what is/is not included)
- Commitment from all parties (planning, trust, openness, product awareness, skills, etc)
- Managing expectations, including time lines, skills available, contract value, commitments
- Using the structure and discipline of the methods within the Software Deployment Process
- Education and skills building
The purpose and value of effective monitoring and tracking
Effective monitoring and tracking of software deployment is important for multiple company stakeholders.
Procurement and supply chain teams benefit because it will provide them with:
- Consistency for overall software procurement and burn down
- The ease of assuring the distribution of the software procured, which could be via a download, or a simple e-mail template, an electronic ordering system, etc.
- Consistency of a face-to-face relationship with vendors; product queries and easier access to the many teams across vendor companies
- Access to the broad range of software
- Targeted access to necessary vendor skills and subject matter experts
The procurement perspective is a simple view: the software contract is an instrument for the ease of acquiring software and managing costs. Therefore, the more software they deploy the higher the value they derive from the contract.
Software deployment is critical to the CTO/CIO to maximize the availability of IT solutions to the organization. Successful deployment of software procured provides “value and functionality” to the organization, and therefore success for the CTO/CIO.
The value of license tracking
If the software licenses are not used, it becomes difficult to show “value” and the deployment may not be seen to be successful. The CTO/CIO will utilize the deployment knowledge for the following:
- To build IT strategies around preferred vendor offerings
- To provide consistency of pricing for budget and ongoing planning purposes
- To understand and contain overall costs of software
- To deliver on their service level agreements (SLAs) to their line of business (LOB) user community
- For reassurance that the vendor will “make it right”
It is important that the company thinks about the concept of license tracking and management for both limited and unlimited licenses. Most of our clients do not know, or do not want to report, which products are deployed and in use in their environments. This makes calculating return on investment (ROI) difficult and compliance management nearly impossible.
Tracking for license management involves identifying:
- The licenses that are installed
- The licenses that are active
- The number of licenses that are forecasted to be deployed
A license tracking solution
Since there is no automated process today, spreadsheets are presently used to identify deployed software on every endpoint and to establish a baseline. Tivoli has a tool called Tivoli License Manager (TLM) that became available in November 2002.
IBM Enterprise Software Management Tool (ESMT) is an innovative Web solution designed to help you manage large, complex software license deployments more efficiently and more effectively. ESMT is a secure, online self-service tool that is readily adaptable to a variety of internal business processes. As it is fully scalable, it is also flexible enough to keep up with rapid changes in business.
How partnering with IBM can address deployment planning, monitoring, and tracking challenges
External links:
Additional contributors: DavidGrimm