NIMM and ECAL Frequently Asked Questions
One way the NIMM is being used is to help measure an organisations readiness to deploy and benefit from the Microsoft Enterprise Licenses avaliable under the Enterprise Agreement. This process is intended to be simple and straightforward with help along the way from Microsoft, your Microsoft Large Account Reseller and NHS Connecting for Health.
Here are the two most common questions I get asked with respect to the NIMM and how to apply for ECALS.
HOW DO I USE THE NIMM TO APPLY FOR MICROSOFT ENTERPRISE LICENSES?
Your first point of contact should be your Microsoft Large Account Reseller (LAR); currently this will be either Bytes, Computacenter or Trustmarque (this is determined by your location).
IMPORTANT: Please make sure that you actually need Enterprise Licenses (ECALS), the core licenses which are available by default to the NHS will provide sufficient functionality for most NHS IT needs, if in doubt please contact your LAR or Microsoft Account Manager.
When requesting Microsoft Enterprise software you will have to provide a self assessment to your LAR showing a NIMM maturity level 4 for Software Asset Management and Collaboration Technology. Capability Maturity Documents are available as part of the NIMM which describe the KPI’s needed to achieve Level 4 in these capabilities.
Once the LAR has your NIMM self assessment for these two capabilities and any backup documents they feel are necessary, they will make an ECAL referral to NHS Connecting for Health for approval before issuing the Enterprise Licenses.
I NEED TO USE MICROSOFT ENTERPRISE SOFTWARE BUT I DON’T UNDERSTAND HOW TO ACHIEVE LEVEL 4 IN COLLABORATION MATURITY
The key things that NHS Connecting for Health are looking for when considering a request for ECALS are Software Asset Management Maturity to NIMM level 4 AND either a Collaboration Strategy, or a sound Business Case that justifies the use of Enterprise Licenses.
The Collaboration Strategy should include a description of the following:
- Business Drivers for Collaboration
- A High Level Solution Design and the links back to the Business Drivers
- The Technical Architecture
- How collaboration technology will change or enhance processes, the way people work and the initiatives being taken to prepare for and facilitate this change
The Business Case should include a description of the following:
- Who the senior business areas sponsors are
- Vision & plan for collaboration in the organisation
- A description of the business needs for collaboration
- A description of the collaboration initiatives that address the business needs
- Estimated costs and deployment times scales
- Desired outcomes
- Desired benefits and return on investment
- Benefit measures