Effective License Position (ELP) Delivery Template



Effective License Position (ELP) Delivery TemplatePartner Instructions and Usage GuidanceIntroductionAs the Microsoft SAM program expands globally, we constantly look for ways to enable our partners to deliver quality work in an efficient way. The Effective License Position (ELP) Delivery Template is such an enabler. This template, developed in collaboration with Microsoft and multiple SAM partners, may be used to standardize the work products delivered during a customer license review. It is an enabler to help standardize the deliverables and help minimize the time required to format the final client presentation.This ELP template can be used in whole or in part to compile and summarize the license deployment and entitlement figures for the customer. In addition, portions of the presentation could be included or removed based on the scope of the project. This template is provided to our partners as a guideline to teams in delivering consistent quality ponentsThe files associated to the ELP Delivery Template include the following:ELP Delivery Template – ExcelThe Excel file shows the detailed deployment and entitlement data gathered from the customer. A description of each tab is below.ELP – This worksheet shows the license position information, presented in a format designed to be easy to understand for most audiences. This can be used for discussions with the customer to both understand the deployment environment and to communicate the findings to the more technical audience.Software Package Tabs – These tabs list out the machine names and the software installed, organized by software product.The design of the worksheets will assist with your discussions with the customer to help them better understand their current install base. We recognize that there may be environments that are too large to display the information in this manner. For each project, the SAM partner has the discretion to summarize the detailed information as appropriate.Executive Summary – PowerPointThe PowerPoint presentation template is an executive summary to be presented to the customer project sponsors. Utilizing this presentation, either in part or in its entirety, can assist your project team in communicating the results of your review in a non-technical, high-level perspective. A description of each section is below.Introduction (first paragraph). This section is meant to be an introduction to the project. It is addressed to Microsoft, since this report will be delivered to the Microsoft account manager at the conclusion of the engagement. Note that each partner will be required to ensure the disclaimer meets their entity’s verbiage requirements.Background. This section is a generic description of our work. The graphic represents the typical phases in a license review project. Additional detail can be included as necessary.Scope. Describe scope limitations or deployment assumptions made. This section allows the partner to describe any limitations encountered during the project or any assumptions made impacting scope.Entitlement Considerations. This section will help walk the customer through how we assessed the license entitlement and to describe our high-level procedures. In addition, this section will give Microsoft insight into entitlement issues and proof of license procedures performed by the partner.Overview of Customer’s Software Asset Management Findings. This is the section to summarize the findings of the project. This high level overview of the deployment/entitlement gaps is typically the “bottom line” of the findings and may be as detailed as some sponsors wish to discuss.Microsoft Environment Overview. This section includes optional graphs to help the customer better understand their install base. Double click on the charts to enter in the customer-specific information. This section is optional to include in the executive summary.Summary of the Effective License Position. This section brings out the highlights of the findings, organized by major product family. The descriptions should be designed to incorporate multiple detailed findings, as appropriate. Double click on the charts to enter in the customer-specific mon Licensing Issues. In response to the customers questions about licensing best practices, this section, which can serve as an appendix, can aid in your discussion with the customer about what issues may currently exist in the customer’s environment. This discussion typically arises when a significant licensing gap is discovered.Since each customer and each project will be different, the Partner team may expand or reduce this suggested template and add detail based on the needs of the engagement. Although we attempted to ensure the template format, colors, and styles would work well with any Microsoft Office installation, please note that it is the Partner’s responsibility to ensure the colors and fonts appear normal before issuing the report to Microsoft or sharing it with the customer.ELP InstructionsFollowing are suggested instructions for creating the ELP spreadsheet and the associated worksheets in Excel:Required Resources:Entitlement Data:Microsoft Supplied MLS statementReseller Supplied Licensing Records (particularly for OEM and Full Packaged Product (FPP))Customer supplied licensesInstalled Data:Inventory record of customer’s environment (What is installed)Key data components:Machine Name (Unique Identifier)Software TitleSoftware VersionNumber of Processors (for certain server applications)Application access data for determining CAL informationELP Worksheet: The ELP worksheet has been updated so that the SAM consultant can copy and paste the License Product Family, License Version, and Effective Quantity directly to the spreadsheet from the MLS. Specific Column Definitions:Product Family – Title of Application grouped in order of MLSVersion – Product Version. Recommendation: Sorting these in chronological order vs. the MLS supplied alphabetical order creates a more logical upgrade/downgrade explanation for customers.LicensesMLS Volume Licenses: The actual number of licenses as calculated on the MLS statement. Recommendation: Validation of these license counts are key and working to understand how these are calculated helps resolve potential issues in the future.FPP Licenses: Full Packaged Product LicensesFPP Upgrades: Full Packaged Product UpgradesOEM Licenses: Original Equipment Licenses. Note: This total license count cannot be automatically added to the other data columns to determine licensing. Specific licensing analysis needs to be applied to apply this column based on the Product Use Rights (PUR).Preliminary License Entitlements: This is the total of licenses that the customer ownsDeploymentsIdentified by Inventory Discovery Tool: Installed copies of software in the customer environment.Identified Manually: Installations of software and CAL requirements that were not discovered by the inventory tool.Total Software Deployment: Total number of installations of software within the environment which require software licenses Software Deployment vs. License Entitlement – The number of software installations less the number of licenses for a specific software titleLicense Allocation (+/-) Upgrades, Downgrades, etc – Utilizing the licensing contracts, applying applicable upgrade and downgrade rightsActual License Position – The final licensing position for this titleComments – Any background or comments that will help explain the licensing position to the customer and just as importantly in the future.Unresolved LicensesUnresolved Quantity – Any licenses that could not be applied due to issues including lack of underlying licenses.Notes – Any explanation for these license applications or non-application of licensesProduct Worksheets: These worksheets provide machine level information for applications that are installed. This provides detailed information for customer and Microsoft reference.For more information about this ELP template, or if you would like to propose any changes that will improve the usability of the templates, please contact your Microsoft SAM engagement manager. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download