top curve
Oracle licensing consultants

Archive for December, 2008

Microsoft Select 3-Tier Licensing Agreements

Dec 29 2008: Published by ScottR under Uncategorized

For Select licensing programs, there are three separate components: Microsoft Business and Services Agreement (MBSA), Select License Agreement, and Select License enrollment.  The 3-tier agreement structure was created to allow organizations with multiple affiliates or geographies to have more flexibility.

  • Microsoft Business and Services Agreement (MBSA) is required for any and all Select purchases. This is the master agreement that outlines contract terms common to Microsoft licensing, service, and support agreements and needs to be signed only once with or prior to the Select License Agreement.
  • Select License Agreement establishes the details of an organization’s software needs, including forecasts and product pools. This covers affiliate companies, which will lead to further volume discounts.
  • Select License Enrollment supplies the basic information for affiliates to acquire software product licenses under the Select License Agreement.
  • We get a lot of questions on this 3-tier licensing agreement.  We hope that this clarifies that the three agreements work together.

    Post to Twitter

    Service Provider License Agreement Program Requirements

    Dec 29 2008: Published by ScottR under Uncategorized

    Like the ISV licensing requirements, there are certain requirements that need to be met to qualify for cost savings found in the Service Provider License Agreement (SPLA) Program.

    1-      Your organization must be enrolled in the Microsoft Partner Program as a Certified Partner for a Registered Member in the Hosting Program.

    2-      You must also comply with the Services Provider Use Rights and export requirements.  In addition, as an ISV, you must provide technical support for licensed products delivered to customers.

    3-      Monthly reports on licenses are expected, regardless of activity.

    Licenses acquired under the SPLA are monthly, non-perpetual licenses that can be used during the term of the agreement and is available through two models:

  • Subscriber Access License (SAL). A Subscriber Access License (SAL) is required for each unique individual user or device that is authorized to access or otherwise use the licensed products. With the SAL option, you don’t need a separate Server License.
  • Per Processor License. Each Processor License allows an unlimited number of users to access the software that is installed on that processor for products licensed through a per processor model.
  • The complexity of Microsoft licensing models - or any other software vendor for that matter - is constantly in flux.  However, some truths remain the same: licensing rules are complex and constantly changing.

    Post to Twitter

    Criteria for Microsoft ISV Royalty Licensing Program

    Dec 19 2008: Published by ScottR under Uncategorized

      Independent software vendors who participate in Microsoft’s ISV Royalty program should be aware of the criteria:

  • ISV must develop a value-added solution using Microsoft’s products and distribute it as one solution.
  • It is expected that a Certified II or Gold II membership is maintained in the Microsoft Partner Program or your organization can purchase prepaid support options from MS or a Gold Certified Support Partner.
  • There is a commitment of $15,000 in royalties over a three-year agreement term.
  • Technical support for customers on licensed products is required along with monthly reports, even during times of inactivity.
  • One thing to be hyper aware of in terms of compliance is the Microsoft requirement to incorporate all license terms into your customer agreements.  This means if your customers are using your licensing improperly, you are in danger of being out of compliance.  Be sure to very clearly state their usage rights!

      This seems like a lot to ask - but the ISV licensing program can save you up to 50% on licensing costs. Microsoft provides a lot of information on the benefits of the ISV Royalty Program.

    Post to Twitter

    Forecasting, Pools and Points

    Dec 17 2008: Published by ScottR under Uncategorized

    With the Microsoft Select licensing programs, the terms forecasting, pools and points are heard frequently.  The three items are a means of creating license estimates and determining discounts.  We’re often asked how this is done and what it all means.

    Forecasting gives organizations the ability to estimate the total number of points per product pool needed over the standard 3-year licensing agreement period, which gives a licensing forecast.  The forecasted points determine an organization’s price level qualification with the biggest discount going to those projecting greatest usage of Microsoft programs, servers, etc.  But, as we always caution, it’s not always about the discounts.

    The different price levels are listed below (Note: the minimum point requirement is 1,500 to qualify).  The four point minimums for a 3-year forecast per pool starts at 1,500; 12,000; 30,000; and 75,000.

    Software products are categorized into three distinct product pools: applications, systems, and servers. Examples of software products in each pool are:

  • Applications: Microsoft Office, Microsoft Office Excel, and Microsoft Office Project
  • Systems: Windows desktop PC operating system upgrade such as Windows Vista.
  • Server pool: Windows Server and associated Client Access Licenses (CALs).
  • To give you a better idea as to where you fall into these programs - a complete list of point values can be found at Microsoft Volume Licensing.  Not all organizations will need or be able to forecast using this model.  But, Microsoft Select offers flexibility for organizations that have changing business needs and may require varying numbers of licensing over its licensing agreement term.

    Post to Twitter

    Microsoft ISV versus SPLA Comparison Chart

    Dec 16 2008: Published by ScottR under Uncategorized

    For those of you that like charts and diagrams to make these confusing programs more understandable - enjoy! ISV = Independent Software Vendor and SPLA = Service Provider License Agreement.

    Post to Twitter

    Microsoft Service Provider License Agreement

    Dec 11 2008: Published by ScottR under Uncategorized

    The Service Provider License Agreement (SPLA) is much more flexible than the ISV program. It allows you to license MS products on a monthly subscription basis, during a 3-year term, while enabling your organization to use the products to provide software services to customers.

    The following scenarios would make the SPLA program the best suited for you:

  • You distribute Microsoft licensed products as part of a unified solution, not as stand-alone products.
  • You do not lease or rent Microsoft licensed products without a separate agreement with Microsoft.
  • You integrate Microsoft licensed products with your unified solution and include the entire product, not just a portion of the product.
  • You insert help files contained in a Microsoft licensed product that may not be modified.
  • You do not disable any features so that customers receive fully functional licensed products.
  • Some of these scenarios will qualify you for both the ISV and SPLA programs, therefore you will need to look at each licensing program and choose which will benefit your individual business needs the most.

    Post to Twitter

    Flexibility of Microsoft Open Value Subscription

    Dec 09 2008: Published by ScottR under Uncategorized

    Microsoft Open Value Subscription is by far the most flexible licensing model and requires the lowest up-front costs for businesses that may have limited budgets and changing needs. An example of a business that could benefit from an Open Value Subscription is a forestry organization, where there is a fluctuation of personnel based on the season. Due to a constantly changing workforce - at times from hundreds during the busy season to only a few administrative employees in the off-season - this licensing plan allows for a forestry organization to only pay for the licenses it needs, at the time they are needed.  This model allows companies to easily increase or decrease licenses without having to re-negotiate SLAs every six months.

    Microsoft published an interesting case study about C. Rokas SA’s realization regarding its licensing issues and move to Open Value Subscription, which has proven very successful for them. C. Rokas SA is a leader in renewable energy sources and electromechanical projects with 250 employees and 70 desktop systems. With a number of PCs and servers running different versions of applications, the IT team was faced with compatibility and security issues. Open Value Subscription enables the company to upgrade and unify its system with a single license key.

    Post to Twitter

    Microsoft Select: 3 Key Benefits You Should Know

    Dec 03 2008: Published by ScottR under Uncategorized

    The Microsoft Select License program was designed specifically for medium and large organizations with 250 or more PCs that have mixed software requirements and require the use of multiple vendors, operating across multiple networks or platforms. For example, this program would work well for a global advertising agency with multiple employees and offices; some working on PCs with standard Office applications while others using Mac OS and related design programs. For organizations that meet these requirements and are looking for a “pay as you go” type program, this is the one.  There are three key benefits to Microsoft Select:

    1.         Incentive-based Pricing, which is based on forecasted purchasing volume and reduces overall procurement costs based on volume of purchase. In other words, the more you buy, the more you save.  Obviously, you only save if you’re buying right. Don’t just do volume purchases for the savings as it invariably leads to shelfware.

    2.         Purchasing Options is apay as you go” model. You don’t have to pay for unused apps and only pay for those you use. Well, duh.

    3.        Accelerated Deployment offers access to media kits to ease evaluation of the applications before procurement and training of employees post-deployment.

    Post to Twitter

    Understand, Review and Manage Your Software Assets

    Dec 01 2008: Published by ScottR under Uncategorized

    New compliance and accounting regulations are forcing organizations to rethink how they view software. The emphasis on governance is changing the way companies think about software as an asset and how they account for it with their auditors. Unlicensed or mis-licensed software is a liability. There are 6 simple, basic steps for understanding and managing your software assets:

    1. Create a repository. But, remember that electronic key codes are not enough “proof” for most software vendors. You need to keep the proof of purchase, receipt or invoice and the Terms & Conditions during the initial purchase. In addition, if you have Oracle apps, you’ll need the following information in case of an audit: application name, version, executable file date, department unit and users, and whether it was an individual or suite installation.

    2. Projection of employee numbers and IT requirements to plan for the short-term future.

    3. Review your annual support spend at least twice a year to determine changes in usage that can possibly result in changes within support options.

    4. Understand your organizations vulnerabilities - in the case of licensing, it’s really about liability.

    5. Implement a discovery tool.

    6. Execute a thorough analysis to validate if buying more than you need will lead to additional discounts and results in a long-term, positive return on investment.

    It’s ironic that the amount of resources - financial and human - go into IT organizations, yet many (I would say the majority) have trouble tracking assets - anywhere from hardware to software. I can think of one instance when the FBI could not account for all their laptops. You know. The ones with all the super-duper top secret information. They went “missing.” And, software asset management is a struggle for any organization.

    Post to Twitter

    bottom curve