JOIN ILM2.0

Sponsored By

Consulting Resources & Services

Need help with service management implementation? Do you see the need for professional services in your organization? Talk to the ILM2.0 community of world-wide consultants about your needs through this portal. 
The following is a list of typical Consulting Engagements the ILM2.0 team provides 

Service Management and ILM2.0 Engagements
  • Establishing Collaborative teams 
  • Information Classification - taxonomy, methods, integration
  • Business Requirements and Policy Setting
  • Service Level Objectives and Agreements
  • Service-Level Audits - using the ILM Maturity Model to define status, goals, and metrics
  • Audit Cloud services and Information Governance in the Cloud
  • IT service catalog design and implementation guidance
  • Infrastructure Cost Reduction and Efficiency Optimization
  • "Appropriate Design" focused on selecting appropriate technologies, infrastructure architecture, practices, data services and service catalogs to meet the business requirements





The following are typical Operating Areas to apply service management methods and ILM2.0 based implementation practices

Operational Practice Areas:
  • Business Infrastructure and Services Readiness Assessments and Audits.
  • Developing Cloud-based Services
  • Deploying Cloud Storage
  • Outsourced service/Cloud Quality of Service definitions
  • Information Governance, Compliance, & Litigation Support Preparation through defensible infrastructure practices including eDiscovery
  • Retention Management (retention and deletion practices)
  • Risk Management
  • Long-term Retention and Preservation (digital archive)
  • Data services planning and optimization (data protection, disaster recovery, business continuity, data availability, storage virtualization.)
  • Service readiness audits using the ILM2.0 Maturity Model
















"ITIL v3 doesn't go far enough. 
It doesn't give us a methodology for implementation.  
Service management with ILM2.0 based practices fills that gap. "
                                                                               Source: Bob Rogers, 2010


Comments