WO2007030633A2 - Procede et systeme de surveillance et de gestion a distance de reseaux informatiques - Google Patents

Procede et systeme de surveillance et de gestion a distance de reseaux informatiques Download PDF

Info

Publication number
WO2007030633A2
WO2007030633A2 PCT/US2006/034878 US2006034878W WO2007030633A2 WO 2007030633 A2 WO2007030633 A2 WO 2007030633A2 US 2006034878 W US2006034878 W US 2006034878W WO 2007030633 A2 WO2007030633 A2 WO 2007030633A2
Authority
WO
WIPO (PCT)
Prior art keywords
managed services
customer
services
solution provider
managed
Prior art date
Application number
PCT/US2006/034878
Other languages
English (en)
Other versions
WO2007030633A3 (fr
Inventor
Mark E. Bakken
Ed Luck
Shannon Schroeder
Jeff Oler
Jennifer Dickert
John Bandy
Original Assignee
Bedrock Managed Services & Consulting
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bedrock Managed Services & Consulting filed Critical Bedrock Managed Services & Consulting
Publication of WO2007030633A2 publication Critical patent/WO2007030633A2/fr
Publication of WO2007030633A3 publication Critical patent/WO2007030633A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising

Definitions

  • the present invention is directed to monitoring and managing a computer network, and more particularly to providing a managed services architecture to monitor and maintain a client's computer network.
  • Small or medium sized businesses face unique IT challenges. These businesses may have the same infrastructure needs as larger companies, but they cannot justify hiring full-time support. In addition, the capital expenses for necessary server and infrastructure hardware have a greater impact on small businesses.
  • small or medium sized businesses hire freelance or consultant IT support for system installation, but fail to spend money on maintenance and patching. Because consulting fees are calculated according to billable hours, the cost of employing consultants can be very high and unpredictable, making it difficult to budget or to plan. Also, because these businesses only use IT professionals or. specialists for special projects or installations, day-to-day support is usually provided by someone with other business responsibilities, so IT support is not always available to end-users.
  • the choice of IT consultants for each project is motivated by cost; therefore, the consultants may vary from project to project, leading to the implementation of different, and potentially inconsistent, approaches and methodologies at a single customer site.
  • the present invention provides a comprehensive managed services model that allows a third-party information technology (IT) service company to assume responsibility for monitoring, administering, and maintaining a business' IT infrastructure, hi addition, the cost of a comprehensive managed services model is predictable and lower than the cost of handling the same monitoring, administration, and maintenance tasks through an internal, or in-house, IT staff. Meanwhile, the comprehensive managed services model provides the third-party IT service company with a long-term predictable revenue stream.
  • IT information technology
  • the third-party IT service company offers various packages of managed services, and the customer is charged according to a subscription-based pricing scheme. While the packages may contain a predefined set of services, the managed services model also permits selection of individual services in a-la-carte fashion to create a customized solution that exactly fits the customer's needs and requirements. The managed services model also allows the third-party IT service company to partner with affiliate IT companies to deliver the services. The combination of automated IT services and a flexible, yet predictable, pricing scheme reduces IT costs while maintaining the stability and performance of the customer's IT infrastructure.
  • FIG. 1 illustrates an exemplary system architecture that provides a managed services solution.
  • FIG. 2 illustrates an exemplary process for implementing a managed services solution.
  • FIG. 3 illustrates exemplary process for implementing a managed services solution from the perspective of the third-party IT solution provider.
  • FIG. 4 illustrates another exemplary process for implementing a managed services solution from the perspective of the third-party IT solution provider.
  • FIG. 5 illustrates the steps for building a comprehensive managed services offering.
  • FIG. 6 illustrates the steps for developing an operations process for a comprehensive managed services offering.
  • FIG. 7 illustrates the steps for developing a comprehensive managed services marketing plan.
  • FIG. 8 illustrates the steps for selling the comprehensive managed services solution.
  • FIG. 9 illustrates the steps for building the comprehensive managed, services process.
  • FIG. 10 illustrates the steps for providing comprehensive managed services support.
  • FIG. 11 illustrates an example flowchart that summarizes how the sales, engineering, and operations teams work together to sell and implement a managed services offering.
  • the present invention provides a comprehensive managed services model, or solution, which a third-party information technology (IT) service company can implement to improve management of a' client's IT infrastructure while lowering the cost of system maintenance and administration for the client.
  • the comprehensive managed services solution reduces administrative overhead and improves operational efficiencies for customers, while providing an up-to-date, stable, secure, and optimally tuned IT infrastructure.
  • the present invention enables customers to outsource information technology functions and simplify the management of their IT infrastructure. By assuming system management and security responsibilities from the customer and by providing end-user support services, the managed services solution permits the customer to focus on the long-
  • FIG. 1 illustrates an exemplary system architecture 100 that provides a comprehensive suite of managed services to a customer at client site 120.
  • Managed services provide benefits in three notable areas: system monitoring and event notification, server and desktop management, and local-area-network (LAN)/wide-area-network (WAN) management.
  • the managed services may include, but are not limited to, system monitoring, IT help desk services, patch management, backup management, e-mail services, file/print services, faxing services, telephone and voicemail system management, anti-virus protection, spam filtering, vulnerability assessments, digital rights management, as well as IT staff and end-user training.
  • the system architecture 100 has a data center 110 which is located remotely from the client site 120 and is managed by the solution provider.
  • solution provider refers to any third-party IT service company that implements the comprehensive managed services model according to the present invention. Such companies may include, but are not limited to, IT consulting companies, IT contractors, IT support companies, or computer software or hardware vendors.
  • the system architecture 100 may employ remote management of customer systems, the solution provider's services may include on-site visits or even continuous on-site presence.
  • the data center 110 includes a systems management/update server 111, a server management system 112, an anti-spam server 113, and an anti- virus server 114. It is understood, however, that the data center 100 may include additional systems necessary to provide the managed services desired by customers.
  • the servers can be located at a remote location, e.g. through a hosting service, it may be preferable that servers are located locally at the client site
  • the system management/update server 111 facilitates server and desktop management by automating deployment of operating system and application patches and upgrades to end-user systems, e.g. workstations. The release of patches and upgrades are controlled from a central administration console, which ensures that computing environments are standardized throughout the enterprise.
  • the system management/update server 111 allows sophisticated, monitoring, analysis, testing, deployment, reporting, and enforcement of software updates from the data center 110.
  • SLA service level agreement
  • This SLA may govern how patches and upgrades are deployed.
  • Software updates may be prioritized according to a severity rating system.
  • the SLA may set out deadlines for the deployment of the software updates according to the severity rating system.
  • the rating system may categorize software updates, such as patches, as: critical, important, moderate, and low.
  • a "critical" patch for example, may address a security threat that can spread easily and quickly, such as an Internet worm.
  • An "important" patch for example, may address a security vulnerability that that does not spread easily.
  • a patch of "moderate” or “low” severity may involve deployment of service packs, BIOS updates, or firmware that address problems with a moderate or low impact.
  • an SLA may require "critical” updates to be deployed within three days, important updates within two weeks, and moderate or low updates within three months.
  • other software updates can be categorized as functionality upgrades or major version updates. In these cases, for instance, the SLA may require functionality upgrades to be rolled out within six months and major version updates within one year.
  • the server management system 112 facilitates the central administration of many servers from the data center 110.
  • operating systems and applications can be automatically installed on dozens or even hundreds of bare metal systems across large, scaled-out installations.
  • the servers have consistent configurations.
  • the anti-spam server 113 provides centrally-managed intelligent spam filtering for enterprise- wide mail and messaging . systems. Meanwhile, the anti-virus server 114 provides centrally-managed protection from computer viruses for all servers and end-user computers.
  • the customer may be required to have broadband Internet access and to maintain software maintenance agreements with the software vendors and hardware maintenance/spare plans with the hardware vendors.
  • the system architecture 100 also includes a remote monitoring system 130, a remote backup system 150, and a remote web services system 150.
  • remote systems demonstrate that any number of the managed services offered by the third-party solution provider can be provided from other sites managed by other parties who have partnered with the solution provider. It is understood, however, that the managed services can be provided entirely by a single solution provider.
  • the remote monitoring system 130 may employ a monitoring agent for the customer's servers, workstations, and network devices at client site 120. Monitoring agents may also be used with temperature and humidity probes to ensure a proper operating environment for servers and other devices.
  • the solution provider is automatically notified of any equipment failure or performance problems, and most issues are resolved by the solution provider before the customer becomes aware of them. In general, the monitoring system 130 provides advanced problem notification to promote faster problem resolution and to minimize downtime.
  • the monitoring system 130 may provide automatic alerting and escalation based on customizable thresholds, which may correspond with an SLA between the customer and the solution provider.
  • the monitoring system 130 may provide the customer with periodic health reports on each server, including information on alerts received from the server and actions taken, as well as metrics, such as disk, memory, and processor usage.
  • the remote backup system 140 may provide remote backup over a standard broadband connection onto on tape, optical device, disk, or other storage media.
  • the backup strategy and retention periods for the backups generally depend on the customer.
  • the backup strategy may also correspond to a disaster recovery plan.
  • the backup system 140 may permit a convenient way for the customer to initiate small-scale data restorations.
  • the remote web services system 150 includes website hosting 151 and DNS hosting 152, which allows the customer to maintain a public website.
  • the present invention permits managed services to be provided according a variety of pricing schemes.
  • the system architecture such as the exemplary embodiment illustrated in FIG. 1, provides the efficiencies of automation.
  • the solution provider benefits from economies of scale.
  • the solution provider can offer a flexible, yet predictable, pricing plan.
  • Offerings based on the comprehensive managed services model may include, without limitation:
  • Time-and-materials billing In some cases, the solution provide? may offer a fixed fee charge for the initial configuration of the environment (assessment, standardization, and upgrades), but the customer pays for all ongoing administration for monitoring, maintenance and site visits entirely on a time and materials basis.
  • the initial configuration can also be provided on a time and materials basis.
  • the fixed-fee, per-device support offerings above are examples of subscription- based pricing arrangements. It is understood that subscription-based payments can be made per-employee or per-service, rather than per-device. Moreover, subscription-based arrangements are not limited to payment according to monthly interval.
  • the solution provider may offer a subscription-based pricing scheme, where the fixed-fee is based on the selection of managed services selected by the customer. The business can select a managed services solution that more closely fits its needs.
  • a subscription-based pricing scheme involves low up-front investment costs and requires no long-term commitments. However, the length of agreements between the solution provider and customers preferably last at least twelve months from the date of system installation.
  • the managed services model also permits selection of individual services in a-la- carte fashion to create a customized solution that exactly fits the customer's needs and requirements.
  • the solution provider may charge fees for initial setup activities.
  • the solution provider may charge a fee for a pre-deployment assessment of the customer's existing IT systems.
  • the assessment fee accounts for travel requirements, pre-assessment discovery, analysis of the customer's server network and supporting infrastructure, as well as creation of a report.
  • the assessment fee also depends on the type, size, and location(s) of the customer's infrastructure.
  • the solution provider may charge the customer a one-time setup fee or amortize the setup costs over the customer's periodic subscription payments.
  • FIG. 2 illustrates basic steps in an exemplary implementation of a managed services solution.
  • the information gathering phase takes place in the first step 210.
  • the solution provider may conduct pre-assessment meetings with key management and functional area representatives on the client side.
  • the solution provider may also collect any relevant documentation on the customer's current infrastructure. After gathering the necessary information .from step 210, the solution provider should understand the customer's organizational needs, critical issues and systems, system boundaries, and the managed services that the customer wants to receive.
  • the information may be incorporated into a document that formally outlines the scope of the implementation project. The document ⁇ should finalize the systems and services that are within the scope of the project.
  • the document may also describe the expected outcomes as well as final acceptance procedures.
  • the analysis and planning phase take place in the second step 220.
  • the solution provider assesses the customer's current infrastructure and identifies deficiencies, or gaps, in the current system. To complete the assessment, the solution provider may find it necessary to conduct site visits and interview IT staff and end-users to validate existing documentation and processes. In addition, the solution provider may conduct performance monitoring and usage analysis of existing systems. Such information may be useful, for instance, in determining whether existing systems can be consolidated. During this step, the solution provider may create documentation to supplement the existing documentation.
  • An architecture design is developed according to the operational efficiencies and opportunities that the solution provider has identified during the assessment of the customer's infrastructure.
  • the analysis and , planning phase of step 220 also includes transformation planning.
  • the transformation plan identifies risks and required resources, creates a budget, and outlines a deployment timeframe with expected outcomes.
  • the solution provider may conduct a detailed cost- benefit analysis, which may include a total-cost-of-ownership (TCO) and/or a return-on- investment study.
  • TCO total-cost-of-ownership
  • the transformation phase takes place during step 230.
  • Dedicated teams implement the transformation plan developed during the analysis and planning phase in step
  • step 230 creates an up-to-date, secure, and financially viable foundation for IT operations.
  • the system is first lab tested and a pilot implementation is evaluated. A follow-up is conducted for each risk identified in the transformation plan.
  • step 230 all decisions have been made and tested so that everything is ready for the rapid and trouble free deployment and operation in step 240.
  • step 240 functionality is verified and customer accepts by signing off. The operation of the system is then transitioned, or handed off, to the solution provider.
  • the solution provider assumes responsibility for the managed services and devices outlined in the contract between the customer and solution provider.
  • the managed services solution is integrated with the customer's existing operations environment.
  • the solution provider employs a comprehensive operations plan, which incorporates best practices.
  • users are also trained to use new features of the new IT solution, streamline business processes, and realize business value. In addition, all documentation is finalized and turned over to the customer.
  • Managed services offerings expand a solution provider's ability to address customer needs and fill gaps left by traditional consulting companies.
  • the comprehensive, yet flexible, managed services model allows a solution provider to build a foundation for long-term revenue generation for its organization. By creating customized solutions based on the comprehensive managed services model, the solution provider increases both short-term business opportunities and long-term revenue stream.
  • a business based on the comprehensive managed services model is both proactive and predictable, enabling the solution provider to increase its revenue and improve its employee retention. Applying the comprehensive managed services model helps the solution provider create long-term business relationships both internally among its teams and externally with its customers.
  • FIG. 3 illustrates an exemplary process for implementing a managed services solution from the perspective of the third-party IT solution provider. From a high level, the process includes a sale step 310, a transformation- step 320, an on-site installation step 330, and a maintenance step 340. Aspects of these steps are described in further detail herein. [0062] To implement a comprehensive managed service offering, the solution provider considers the requirements of implementing the infrastructure and services offerings for both its organization and its customers. Before its organization offers managed services to its customers, the solution provider creates an infrastructure capable of providing those services. After its internal infrastructure is prepared, the solution provider then prepares the necessary infrastructure for each new customer.
  • the major phases of creating a comprehensive managed services infrastructure include deciding which services to include, developing internal processes for handling management tasks, and developing and documenting technical procedures.
  • the first phase in creating a managed services infrastructure is to determine the services that should be provided.
  • the solution provider is planning to provide remote management services, it might find many components of its proposed offering duplicates services that is has already been performing. In this case, once the solution provider begins offering comprehensive managed services, it can benefit from the core competencies it already has, but may partner with other organizations and solution providers to cover services outside of those core competencies. However, the solution provider's areas of core competence grow as its organization's skills, experience, and confidence grow under the managed service model. > ⁇
  • the solution provider must have a strong technical infrastructure and associated internal services.
  • the solution provider may take either a centralized or decentralized approach to establishing the infrastructure components required to provide managed services. Depending on the solution provider's goals and core strengths, its infrastructure approach may be more or less centralized. For a centralized system, the solution provider adds the required functionality to its existing infrastructure. ⁇
  • a solution provider can create a virtual data center through a combination of centralized services and strategic relationships with third-party affiliates who specialize in a specific area.
  • an affiliate is another third party that is contracted to provide components of the managed services offering that 1 are beyond the solution provider's resources or goals. Through affiliates, the solution provider can gain the benefits of economies of scale, lower the operations costs, and reduce liability.
  • FIG. 4 illustrates exemplary phases which enable a third party IT solution provider to develop a managed services business.
  • the phases include: building a comprehensive managed services offering (step 500), developing an operations process for a comprehensive managed services offering (step 600), developing a comprehensive managed services marketing plan (step 700), selling the comprehensive managed services solution (step 800), building the comprehensive managed services process (step 900), and providing comprehensive managed services support (step 1000).
  • FIG. 5 illustrates exemplary steps for building a managed services offering 500.
  • the step 510 involves identifying business opportunities.
  • a solution provider first identifies potential clients and the demand for a potential managed services offering.
  • Business opportunities may include chances to provide customers with: a cost-effective monitoring, management, protection, and support solution; infrastructure technology; solutions based on enhanced knowledge of customer needs and an in-depth understanding of their current environment; or customer expansion services (e.g. remote offices and secure VPN access).
  • Other opportunities that might arise include: selling and configuring core infrastructure hardware; licensing and deploying core infrastructure software; or providing supporting technology solutions like VoIP, intrusion detection systems, or thin clients.
  • the greatest opportunity for selling comprehensive managed services to small and medium-sized businesses may occur when the business:
  • a comprehensive managed services solution may compliment the enterprise customer's internal staff.
  • the in-house IT staff can focus on being system architects, strategists and project managers, while the solution provider's staff handles day- to-day IT operations and assists with implementing the latest technologies.
  • An opportunity to sell a managed services solution to an enterprise oustomer may arise after the solution provider has helped the customer with an upgrade or the roll-out of a new technology.
  • the solution provider may attempt to sell a managed services package that maintains the new system.
  • Enterprise customers rriay also be likely to subscribe to a managed services package when members of the in-house IT staff leave, when the company grows, or when the IT work load is increasing.
  • step 520 involves the creation of a business plan.
  • a good business plan focuses on three major areas: selling and marketing managed services to customers; creating a cost effective technical managed services solution for the customers; and providing operations and ongoing support for managed services.
  • a general business plan may include the following sections:
  • another step 530 in building a managed services offering is determining whether adding a comprehensive managed services offering is right.
  • the solution provider assesses whether it has the core skills needed to build a comprehensive managed services offering.
  • a solution provider in step 530, assesses requirements for infrastructure, administration and staff, facilities, marketing, and training.
  • the solution provider needs a solid, reliable infrastructure.
  • the solution provider's organization must be able to provide remote management, notification, and reporting capabilities for the customer environment. This does not necessarily mean that a large investment is required, as the solution provider may already have many of the necessary infrastructure components in
  • a solution provider may provide comprehensive managed services in several ways:
  • Remote access to customer sites Remote access dramatically improves response time.
  • the solution provider can establish remote access through VPN tunnels. Whatever technology is selected, using a single access method is preferred, to improve operational efficiency.
  • Call center capability The solution provider must be able to receive customer calls or e-mail requests properly, log the issue presented, and track the issue through to resolution.
  • step 530 requires assessing administrative and staffing requirements and costs. Establishing a successful managed service offering requires coordinated sales, technical, and administrative teams to provide tailored solutions to each
  • the solution provider already provides infrastructure solutions, the roles necessary for the new managed services offering can be easily added to existing staff responsibilities. As . the managed services client base grows, specific staff may need to be dedicated to each of these roles.
  • the solution provider might need legal help to review customer contracts and affiliate agreements and accounting staff to track managed services revenue and costs. Accounting staff might also need to address credit checks, credit card payments, and invoicing in advance.
  • the solution provider may create a website to enable internal employees and customers to view reports, track .changes, open incidents, and make change requests. Staffing and administration costs depend completely on how quickly the solution provider wants to expand its managed services business.
  • staff should grow as business dictates instead of hiring many people with the hope business will come.
  • step 530 the solution provider also assesses marketing requirements and costs.
  • the solution provider needs to develop marketing materials to help sell a comprehensive managed services offering. These materials may include:
  • the solution provider may also want to consider developing:
  • the solution provider assesses training requirements and costs. Training that covers the managed service model is generally required for staff. The technical staff is instructed to follow best practices documentation, including how to set up, configure, optimize and maintain each type of server on a daily, weekly, monthly, and quarterly basis.
  • step 530 requires an assessment of facilities requirements and costs. Providing comprehensive managed services does not require a network center. If the solution provider already has such facilities, it may choose to leverage that investment for the managed services offering. However, as discussed previously, the solution provider can implement comprehensive managed services without data center facilities if customers choose to keep their servers in their own facilities.
  • the solution provider may rent rack space from a suitable data center provider.
  • the cost to rent rack space is typically pay-as-you-go.
  • the solution provider may either resell it or let the customer purchase it in the customer's name.
  • a cost-effective way to start offering comprehensive managed services without investing in any facility is to use affiliates to provide monitoring, patching, and end-reporting services.
  • the solution provider may choose to have a small office for administrative staff, meeting space, Internet connectivity, and access to a color printer and marketing materials, or if the solution provider offers repair services, hardware and software resale, or training services.
  • the step 540 requires identifying the organizational impact of adding a comprehensive managed services offering.
  • it is necessary to understand the impact on technical staff, operations, and sales and marketing.
  • it may be necessary to communicate the vision of this new model to employees.
  • the reasons for adopting this business model may need to be communicated to ensure that the staff understands the benefits to both the customers and the solution provider's organization.
  • the framework of the comprehensive managed services offering should be explained, stressing the benefits to the company.
  • technical staff When moving to a comprehensive managed services offering, technical staff will be required to be on call 24 hours a day, seven days a week.
  • operations staff will need to:
  • step 550 requires designing the business model architecture for the comprehensive managed services .offering.
  • a comprehensive managed services offering requires the following core building blocks:
  • Steps 610-680 of FIG. 6 illustrate the steps required for developing an operations process for a comprehensive managed services offering.
  • Step 610 requires defining personnel requirements for operations support, which includes defining personnel requirements and descriptions and defining compensation plans.
  • the current size of the solution provider's organization and the skill levels of its operations staff are major factors in how the solution provider applies the comprehensive managed services model.
  • the staff must be able to handle the increased technical and administrative workload.
  • the solution provider may combine some positions or split others up among part-time staff. Regardless of how the staff roles are defined, the staff must be able to meet the customer needs generated by the solution provider's managed services offerings.
  • the solution provider already maintains a consulting practice with technical and support staff. Thus, it may already have all the necessary staff members in place, and all that is necessary is to adjust their key responsibilities to support the managed service offerings.
  • the following position descriptions illustrate the personnel that may be required for providing comprehensive managed services. The positions are not presented as requirements. ,
  • the billing administrator performs tasks that apply standard accounting principles, procedures, and techniques.
  • the primary objectives of the billing administrator are to support staff by administrating accurate and timely accounting, to improve efficiency, and to enhance customer service.
  • the financial analyst is responsible for developing and maintaining highly complex financial information, plans, and projections by applying knowledge of advanced financial theory and understanding of both the solution provider's organization and the customer. Financial analysts are assigned to complex projects that require return on investment (ROI) or cost analysis breakdowns.
  • ROI return on investment
  • the contract specialist provides assistance and oversight in the preparation and negotiation of contracts and subcontracts.
  • the contract specialist serves as the liaison between the solution provider and other vendors and service companies, as well as with customers.
  • the contract specialist also ensures that all contractual revisions are mutually accepted, communicated, and documented according to the specified change control process.
  • the operations manager must balance costs and value while providing general oversight, including responsibility for personnel management, solution development, revenue growth, customer satisfaction, profitability, and business coordination.
  • the operations manager should have an excellent understanding of sales processes, competitors' strategies, technology and industry trends, financial implications of technology decisions, and legal and regulatory requirements.
  • the systems engineer provides infrastructure analysis and recommendations and is responsible for monitoring internal and customer systems from both a technical and financial perspective. The systems engineer must stay current with technology
  • the project manager ensures that the project is delivered on time, does not exceed its budget, and meets the customer's needs by maintaining a cooperative, motivated, and successful project team and ensuring that any affiliates involved in a project meet or exceed delivery expectations.
  • the staff coordinator provides leadership and overall management of all technical staff and must be able to respond staff allocation conflicts and requests expeditiously.
  • a sales and customer liaison is a customer's primary point of contact and essential to ensuring that solutions are aligned with customer needs.
  • step 620 of FIG. 6 the solution provider creates comprehensive managed services architecture designs. This step involves choosing the degree of centralization, designing vendor affiliations, organizing the internal architecture, and creating standard customer architecture designs.
  • the basic design for the managed services infrastructure should be transparent to customers, but the degree of centralization of the infrastructure is important within the solution provider's organization. Before the solution provider plans and implements its managed services infrastructure, it carefully evaluates the organization's immediate business needs, as well as its long-term plans for providing comprehensive managed services. [0100] As described above, taking a decentralized approach enables, the solution provider to deliver the same capabilities without requiring a large capital investment in a physical data center. The decentralized approach leverages data and communication technology to provide a virtual network operations center at a much lower cost than a traditional operations center. Due to advances in firewall and other security technologies, the influence of geography on how the solution provider organizes its staff and other resources is minimized.
  • the solution provider can integrate standard phone systems, e-mail systems, and voice-over-IP (VoIP) technology with remote desktop and remote assistance software to provide routine management and user support.
  • VoIP voice-over-IP
  • Customers can place a call or send a message for support and receive the same prompt response they would receive from a traditional operations center.
  • a support call in a decentralized system can involve a user in one location, a support call worker at a different site, and a technician at yet another sijte.
  • the solution provider plans how to provide comprehensive managed services, it might determine that it can provide some services with minimal retooling or change of focus with respect to its core competencies. However, other services, though critical to a comprehensive offering, might be outside the solution provider's current areas of expertise and would require substantial investment. In such cases, the solution provider may decide to offer these services through a strategic affiliation with another third party rather than by developing the ability to provide them internally.
  • the first step in selecting affiliates is to determine which elements of the managed service offering are provided internally and which are outsourced. In making this decision, ' the solution provider considers what services fall within a core competency of the solution provider and what services would require substantial investment in training, equipment, and staff. In addition, the solution provider considers whether it would take on additional liability by offering a service.
  • remote backup service One example of a service that may be outsourced is remote backup service.
  • a solution provider would have to make a large investment in Internet connectivity and mass storage.
  • Anti-spam filtering and anti-virus protection may also be outsourced by managed services providers.
  • this core component of comprehensive service packages may also be outsourced to an affiliate.
  • the solution provider identifies and selects affiliates to provide those services.
  • Factors that enter into affiliate selection include technical competency, contract and licensing flexibility, responsiveness, and company culture.
  • the solution provider is responsible to the customer, so all services are provided in such a way that the customer cannot distinguish between the services that are provided internally and those that are provided by affiliates.
  • affiliates must support the customer offerings effectively. Because any outsourcing is transparent to the customer, all branding and licensing agreements reflect this requirement. Preferably, the selected affiliates see the mutual benefits of working together and are flexible enough to structure an agreement to meet both parties' needs. affiliates with a core focus in the required area are preferably selected, rather than a company with a broad focus and potentially competing managed services offerings.
  • affiliates are also evaluated for their willingness to satisfy requests for technical development or support. affiliates are preferably also flexible enough to expend development effort to accommodate the solution needs.
  • the capacity of the remote management infrastructure is a significant factor in successfully offering managed services.
  • the solution provider supplies monitoring, detection, response, and maintenance services for both its internal environment and for the facilities, equipment, and software that support customers.
  • the solution provider's organization is a virtual operations center that provides on-demand, professional, and courteous support. The design of the virtual operations center depends on many factors, including customer requirements, the solution provider's capital investment, and the breadth of services it provides.
  • the infrastructure supports the processes and procedures needed to record communications with customers properly and to respond to both planned and unplanned customer needs.
  • a standard customer architecture design may require that the customer have: maintenance contracts with software vendors for all software covered under the managed services agreement; warranty coverage and/or a hot spare plan on all hardware covered under the managed services agreement; broadband Internet access; and remote access to customer systems, hi a particular, high-speed Internet access ensures that remote support can be
  • remote access to customer systems enables monitoring, management, and support from any location.
  • remote access and other customer architecture requirements are defined in the customer agreement.
  • Required improvements to the existing infrastructure may also be required as part of the transition process or as a separate consulting project before the managed services agreement takes effect.
  • Step 630 in developing an operations process involves defining service level agreements and internal service policies.
  • Step 630 may include: defining affiliate service level agreements, defining customer service level agreements, defining internal service level responsibilities, and defining effective compensation schemes.
  • a solution provider In addition to having a strong technical infrastructure, a solution provider also employs an effective set of service level agreements for affiliates and customers. Moreover, the solution provider also has clear internal policies that define the roles and responsibilities for staff members supporting the managed services offerings. . '
  • the agreements ensure that the affiliates provide products and services flexibly, and in compliance with the solution provider's branding needs.
  • the affiliate agreements require that affiliates bill the solution provider directly and that all materials they deliver have the solution provider's branding or no branding at all.
  • the SLA between the solution provider and the customer defines the parameters of the services provided by the solution provider.
  • the contents should include a specified level of service(s), support options, enforcement or penalty provisions for services not provided, a guaranteed level of system performance as relates to downtime or uptime, a specified level of customer support, and a detailed inventory of hardware and software
  • a customer service level agreements may cover: incident management, problem management, configuration management, change management, release management, automated updating and patching, e-mail anti-virus and anti-spam, desktop and server anti-virus, backup services, remote monitoring and alerting, web hosting and DNS services.
  • Customer SLA's may also address the following areas: telephony integration, voice mail, faxing, voice over IP, web filtering and monitoring, intrusion detection and prevention, vulnerability assessment and remediation, digital rights management (DRM), secure e-mail, portal integration services, application web services, policies and procedures, inter-network device management (router, firewall, switches), web site hosting and DNS services, help desk services, and managed desktops and printers.
  • DRM digital rights management
  • the solution provider After the solution provider signs an agreement with a customer, it is responsible for supporting the covered services established in the agreement.
  • the solution provider has the staff and infrastructure to respond to any needs or service requests covered by the SLA.
  • the solution provider may need to adjust its internal compensation schemes to retain the staff required to deliver the promised services.
  • Step 640 in FIG. 6 involves establishing scope of work standards, which addresses setting contract terms, determining invoicing parameters, establishing assessment fees, setting pricing options, writing service level agreements, providing customer reports, and setting cancellation fees.
  • Scope of work standards outline the topics and issues that should be addressed when defining what the solution provider and the customer expect from an engagement.
  • scope of work standards When the scope of work standards are used for a statement of work or a service level agreement, the essential project parameters are documented in a logical and consistent format.
  • the scope of work standards minimize miscommunication and confusion, and help develop sound customer expectations and a collaborative consensus between the solution provider and the customer; Scope of work standards address all procedures and processes involved in fulfilling customer agreements, including cost information and any deliverables that customers receive.
  • scope of work standards may be organized according to
  • Contract terms define standards and requirements for customers before the solution provider deploys and provides managed services.
  • Well-defined contract terms for managed services may include provisions to address the following: ownership of custom software, e.g. software licenses, termination of licenses, and third party interests; warranties; limitation of remedies and liabilities; and indemnification of customer and the solution provider.
  • the solution provider typically pays its affiliates a monthly fee in advance of receiving services
  • the solution provider preferably invoices its customers in advance for services to be provided in an upcoming period, e.g. the upcoming month.
  • the solution provider preferably requires all new customers to pay their first month's invoice, in addition to an initial set-up fee, before beginning deployment or enabling their services.
  • the solution provider's pricing options address the needs and concerns of the customers. To ensure the sales staff have flexibility in offering services, the solution provider establishes several pricing plans and variations as discussed previously.
  • the solution provider When the solution provider begins a managed services relationship, it assesses and documents every element in the customer's current environment that might affect the migration to a managed services environment. A thorough assessment can uncover organizational problems that might affect the shift to managed services. The doc ⁇ mentation generated by an assessment can help shape the service level agreement, while also providing a starting point for the migration plan and helping to estimate the cost of the customer transition. The solution provider may charge a fee for this assessment.
  • the assessment fee accounts for travel requirements, pre-assessment discovery, analysis of the customer's server network and supporting infrastructure, as well as creation of a report. The assessment fee also depends on the type, size, and location(s) of the customer's infrastructure.
  • the solution provider At the end of each month, or a specified period, the solution provider provides customers with a report on the health of each of their covered systems, any alerts received, and the actions taken to address each alert.
  • the solution provider's customer support team
  • the SLA may deliver these reports and review them with appropriate customer staff. These periodic reviews of system health reports provide customers the opportunity to ask questions, further identify their needs, and appreciate the value of the. solution provider's services. [0129] To protect the solution provider, the SLA also addresses occasions when a customer wants to cancel managed services entirely or remove specified devices or services from the original agreement. For instance, the standard SLA may require the customer to pay a charge for service cancellations or reductions. In addition, the customer may be responsible for liquidated damages due to the difficulty of determining actual costs, losses, and liabilities associated with an early termination.
  • Step 650 illustrates the creation of a cost analysis and return pn investment template.
  • the solution provider needs a thorough understanding of its organization's costs. Armed with knowledge of its own costs, a solution provider achieves an understanding of the fees it can charge its customers. Thus, the solution provider can communicate how much it can reduce a customer's IT spending and increase its ROI by moving them to managed services.
  • the solution provider may establish a cost review process that verifies all costs before delivering a managed services proposal to a customer.
  • the solution provider's accounting staff may conduct consistent cost reviews of each proposal before the sales team presents it to customers.
  • a thorough cost analysis breaks down all relevant components of the proposed managed services offering, which may include:
  • affiliate costs monitoring, anti-virus, spam filtering, back-ups, etc.
  • the solution provider may also track costs in the following categories:
  • Managed services setup cost The cost associated with making a device ready to be managed. It should include all billable time for an upgrade, applying patches, or installing remote monitoring and management software.
  • the amount of time to complete a managed services task depends on the type and number of managed devices. For a customer with the same type of server at multiple locations, it might take a few hours to test a patch folly, but the test results will be valid for multiple servers.
  • the solution provider's technical staff estimates how many hours per month each task will take for each device and then calculates the total number of hours for all devices per customer. This total is then multiplied by the hourly rates for the technicians involved to determine the internal support costs. The total should account for any free support hours provided under the managed services agreement.
  • the tasks to consider may include:
  • the solution provider's cost review process also accounts for all internal costs associated with each specific managed services offering.
  • the solution provider decides how much to mark up each specific piece of the offering. For example, the solution provider may add 10% to the cost of hardware, 15%-20% to the cost of software, 20-25% to the cost of vendor affiliate services, and 40-50% to internal staff costs.
  • the solution provider then totals the markups and costs and divides that total by the number of devices being managed to get a per-device monthly fee for the customer.
  • the solution provider may create a return on investment (ROI) template.
  • ROI return on investment
  • the solution provider needs to understand its internal cost structure and its customer's current IT cost structure. Direct costs that may require consideration include: • ' Internal staff costs
  • the solution provider may analyze this information to see which of these costs can be reduced or avoided by using managed services. In some cases, the biggest potential for cost savings may be realized by convincing the customer to delay hiring another internal IT support person. By avoiding the hiring of more IT staff and using comprehensive managed services, customers will not only save money, the customer will get a more stable and secure IT foundation for their work.
  • the ROI template should make it easy to compare a customer's current costs to the anticipated monthly fee.
  • Indirect costs are those that cannot be easily and accurately identified with a specific project.
  • a customer might undervalue the potential savings gained by minimizing these costs, but the savings are real and should be taken into consideration when deriving the return on their investment.
  • Some of the potential indirect savings include:
  • step 660 involves creating internal support processes, which includes creating a response process, creating an escalation process, creating an incident management process, and establishing communication standards.
  • Strong internal support processes are important to keeping customers satisfied.
  • the solution provider establishes how its organization provides effective incident response, resolution, and follow-through. Without strong internal processes, the solution provider risks vague, ineffective incident responses and haphazard work by support' staff.
  • the solution provider sets the specific areas of responsibility for each of the staff roles. Using well-defined internal support processes, support staff work consistently, independently, and effectively.
  • Some basic elements that may be a part of the internal support process design include: response; escalation, incident reporting, resolution reporting, closure reporting, and communication flow. An incident is an event that has interrupted or diminished the quality of services for a customer.
  • the solution provider also defines level ofresponse by categorizing events.
  • the categories indicate the severity and required response time for an incident. For example, events may be categorized according to the following levels:
  • An escalation process determines who to contact and what steps to take when an initial response fails to resolve a problem. If the solution provider provides some services through affiliates, it ensures that the escalation process addresses problem resolution with those 1 affiliates.
  • the escalation process may identify initial contacts, technical and core service specialists, management contacts, and executive contacts.
  • the solution provider establishes standards to guide its support staff to a successful and timely resolution.
  • the complexity of the incident processes depends on the type and importance of the solution provider's services, service level agreements (SLAs), and the relationship between the solution provider and its customers.
  • SLAs service level agreements
  • a larger client base may call for a more sophisticated incident management system to handle the workload.
  • Incidents are recorded in a timely and accurate manner.
  • the incident reporting process may include the following components:
  • Creating effective communication standards can help strengthen relationships among the solution provider's staff and between the solution provider and its affiliates and customers.
  • the solution provider's communication standards may require that written communication be used as much as possible to minimize misunderstandings often associated with oral communication.
  • the standards promote clear and concise communication, and promote collaboration.
  • the solution provider continuously reviews and revises communication standards.
  • step 670 involves creating call processes to support managed services customers. Specifically, this step addresses receiving support requests, responding to support requests, escalating support requests, reporting support requests, closing support requests, and documenting support requests.
  • the support process is as simple as possible for customers.
  • the solution provider may establish multiple ways for customers to initiate a support request. For instance, communication > via telephone and e-mail are typically available to customers. Regardless of how a support request is submitted, however, the procedures followed should be the same.
  • the solution provider establishes a dedicated support channel for support requests from its customers.
  • the nature of this support channel will depend on the number of customers and the volume of calls expected. For instance, if the solution provider's customer base is small, responsibility for support calls can be incorporated into the job of several staff roles. On the other hand, as the managed services customer base grows, the solution provider may enlist a staff fully dedicated to handling support requests.
  • the solution provider ensures that a specific person or team is always responsible for incoming support requests. For instance, the solution provider avoid strategies such as a shared e-mail address or telephone number that forwards a request to a group mailbox or a voicemail box, respectively.
  • Responsibility for a support request is assigned immediately upon receipt of the call, and any subsequent transfer of responsibility for the request is formally recorded.
  • the solution provider When the solution provider receives a request, it must gather certain information about the issue to route and assign it properly. As such, the information recorded according to support request procedures may include the following:
  • the support request process includes steps to acknowledge the request from the customer and prioritize the request.
  • the priority assigned to the request may also have a corresponding response time. Regardless of how the request is received, the solution
  • the priorities may include the following:
  • request information is collected and a priority is assigned to the request, the request is assigned to an available technical resource, e.g. technician or engineer. After this assignment, the priority and the terms of the customer SLA determine if the support requests takes precedence over existing calls. For instance, a request with a very high priority may take precedence over an older lower priority request.
  • an available technical resource e.g. technician or engineer.
  • the responding technical resource begins troubleshooting the support request.
  • the responding technical resource is also responsible for meeting any additional terms of the SLA, which may dictate escalation and status reporting requirements.
  • the responding technical resource is aware of the terms of the SLA that are in effect for each request in order to make an appropriate response.
  • the responding technical resource is also aware of any limitations to the SLA for each request. For example, if a support request is determined to be related to a hardware failure, the request may need to be immediately referred back to the customer if the SLA does not cover hardware issues.
  • the terms of the SLA dictates that some types of response or troubleshooting are billable, the responding technical resource may need to obtain customer permission before proceeding.
  • Escalating a support request transfers responsibility for the request to another person inside the solution provider's organization or possibly to an affiliate.
  • the solution provider may divide escalation into two categories: technical and administrative.
  • Administrative escalation is a separate process designed to ensure that all support requests are resolved according to the customer's SLA by setting thresholds for resolution.
  • the threshold for administrative escalation may be a percentage of the time limit for resolution of a request required by the SLA. If the request remains open past, the threshold, the request is transferred to a service manager or similar staff member for a higher level of attention. This attention might include assigning additional staff to the request, escalating to a more experienced technician or engineer, or contacting the customer to discuss alternative solutions.
  • Administrative escalation typically requires an automated process to function optimally, which may entail a comprehensive helpdesk or support application. Multiple levels of administrative escalation are possible, and may involve continued escalation to higher levels of responsibility within the company.
  • SLA SLA
  • the terms of SLA also dictate the requirements for communicating status to the customer.
  • a SLA may require periodic status reports to the customer to verify that the request is being addressed.
  • the responding technical resource is aware of any reporting requirements so that the customer receives the communication according to the requirements of the SLA.
  • the form of status updates to the customer may also be dictated in the SLA. For instance, status updates may be communicated through by telephone, manually composed e- mail, or automated messaging using support software.
  • Support requests typically fall into one of the following status categories:
  • Hold for resolution a support request that is either awaiting additional information requested from the client, or that has been resolved and is awaiting confirmation from the customer.
  • Pending, fix identified a support request for which a potential resolution has been identified, but is awaiting customer approval to deploy.
  • RPC submitted a support request for which a formal change approval process has been initiated, and which has not yet been approved.
  • a technician believes that a support request has been resolved, he or she may set the request to status "Hold for resolution.” The technician or another staff member then contacts the customer to confirm that the issue is resolved. If the customer indicates that the issue has not been resolved, the technician maintains responsibility for the support request and troubleshooting continues. If the customer indicates that the issue is resolved, the date and time are noted on the support request, and the technician begins work on the next highest priority request.
  • the step 680 involves designing a centralized customer data repository, which includes, developing a comprehensive managed services marketing plan. Having an internal customer data repository in place to organize documentation helps to ensure the efficiency, continuity, and consistency of the managed services.
  • Data repositories are a collection of resources that organize customer information and documentation in one central location. Data repositories also control how the information and documentation is distributed. Repositories often consist of several databases tied together by a common search engine. A properly designed repository can help enforce configuration management standards for all customers. Other benefits of customer data repositories include:
  • the data repository is kept organized. Effort is made in creating, developing, and maintaining the repository structure. Maintenance duties are assigned to customer
  • the repository is based on a stable and scalable platform that is backed up daily. To secure customer data internally within the organization, access to the repository is based on job function.
  • policies, procedures, guidelines, and management are established.
  • the policies, procedures, and guidelines of each of the components of the customer data repository are established and defined.
  • the data repository is easy to use. A focus group may be created with likely users in order to assess and guide the software acquisition and configuration choices for the repository.
  • Invoicing conditions may differ among the solution provider's customers. Each customer's requirements or preferences are documented accordingly within the customer centralized repository. Maintaining an accurate record of invoicing terms, pricing conditions, and SLAs ensures accuracy in monthly invoicing.
  • customer inventory repositories should include:
  • Asset management can be a time-consuming and complex task. Effective control of the solution provider's and customers' assets enables the solution provider to obtain the highest use and return on each of its investments.
  • the solution provider may also employ a customer communication site to ensure that communications with customers are consistent, timely, and secure. Such a site also enables the solution provider and its customers to find relevant information quickly and easily.
  • the customer communication site can be the cornerstone of the customer data repository. It empowers customers by giving them accurate and up-to-date information accessible at all times. When used effectively, a customer communication site can enhance task flow and decision-making for all customers.
  • the centralized repository also reflects the scope of work (SOW) standards for managed services customers.
  • SOW scope of work
  • the SOW documents specify service commitments to customers. Embedding the scope of work standards into the design of the customer data repository provides a consistent and clear reference point for the solution provider and its customers.
  • Every managed services relationship begins with a contract between the solution provider and the customer.
  • This original contract provides a foundation for all subsequent contracts and addendums and is easily accessible as a quick reference point.
  • the solution provider can streamline the process of establishing a managed services customer by signing a master contract with the customer before it develops a scope of work document and service
  • Including the master contract in the data repository can provide a foundation for relevant staff to use when SOW documents and SLAs are finalized.
  • HIPA Health Organization
  • Sarbanes-Oxley are affecting the way some businesses must track and protect information. Because of this, the customer data repository must be secure and designed to support customers' regulatory compliance needs.
  • the solution provider In the event of a major service interruption or disaster, the solution provider must expedite the restoration of the customer's operations. To help build the customer's confidence and trust, the solution provider must provide a solid, reliable, and proven disaster recovery plan, which may be incorporated with data within the customer repository.
  • FIG. 7 illustrates the steps that are involved in developing a comprehensive managed services marketing plan 700.
  • the steps may include: developing the comprehensive managed service offerings; providing a four-tiered comprehensive managed service offering; understanding customer challenges and communicating solutions; developing sales and marketing materials; and developing internal training.
  • the solution provider already has a customer base, it might already know a great deal about the marketplace and business needs.
  • the solution provider may be able to quickly and easily propose and sell a comprehensive managed services solution to existing clients. Converting existing customers to comprehensive managed services clients can then
  • the solution provider first creates and analyzes a high-level list of all potential customers in its market. Factors to consider include size, location(s), and market sector of the businesses. To remain competitive within the market place, the solution provider also analyzes each competitor's value proposition and pricing strategy.
  • the step 710 involves developing comprehensive managed service offerings.
  • business opportunities arise from providing a comprehensive managed service offering.
  • the primary and secondary, opportunities presented by offering comprehensive managed services may include:
  • the solution provider's marketing plans should emphasize that the solution provider has the ability to enhance other aspects of the customer's environment while providing the comprehensive managed services. Moreover, the marketing plans also explain that the solution provider has the flexibility and customization options to suit each customer's needs and goals.
  • Step 720 in FIG. 7 involves providing a four-tiered comprehensive managed service offering, though the pricing schemes according to the present invention are not limited to this type of offering. How the solution provider structures the services it offers and
  • Flex hours can be saved and used later for either tech support or on-site project work (must be used in four-hour increments). Flex hours expire at the end of the calendar year.
  • the Bronze level of service is designed for large customers. Large customers are likely to be able to take advantage of a multiple server discount when they choose one of the managed services components like monitoring and patching. In these environments, IT staff is already present, but by relieving them of after- hours support necessities and daily requirements, the solution provider presents its organization as an asset that helps them meet their strategic needs.
  • the Silver level of service is designed for any customer who wants to add major platform upgrades included to the basic service provided in the bronze level offering. These customers probably will have multiple servers and be able to take advantage of a multiple server discount.
  • the Silver service level may be more applicable to small and medium-sized organizations that maintain IT staff but do not have the time to invest in routine maintenance of configuration standards and security, hi most cases, major platform releases occur every 18 to 24 months.
  • the additional monthly per-server charge enables the solution provider to bank $250.00 per contract month to help offset the labor costs associated with performing the upgrade.
  • the services included in the future upgrade of operating systems include design, research and development, and deployment of the upgrade.
  • the Gold level of service is designed for any customer who needs to have major platform upgrades and broad 24x7 support provided to them at no additional charge.
  • the Gold service level is designed primarily for small organizations that need to outsource their overall IT support, but some medium-sized organization might also be interested.
  • the Gold service level enables customers to outsource their all their IT services.
  • AU customer servers are set up to a standard configuration and the solution provider assumes full responsibility for management and support. With this level of service, the solution provider is again able to bank and additional $250.00 per contract, per month to assist in offsetting the labor costs associated in providing remote phone support, 24x7x365 onsite support where required, and the necessary operating upgrades to ensure the managed service customer is always on the most recent and updated version.
  • Add-on (“a-la-carte”) services may include:
  • A-la-carte services are designed for customers who have needs that do not map exactly to the standard packages.
  • A-la-carte options enable sales and technical staff to customize solutions for the customer while maintaining the advantages gained from economies of scale.
  • the solution provider gains the most from its affiliates through a Ia carte options. For example, the customer might choose a gold level agreement, but in addition would like the solution provider to host an e-mail or Web server.
  • the associated pricing for the a-la-carte options usually are handled in a cost-plus pricing model, but as a flexible managed service provider, those costs must be incorporated into the customer's monthly bill.
  • a systems engineer should be consulted when a-la-carte options are designed and offered. All technologies included in comprehensive managed services solution are both compatible and operationally efficient for the customer.
  • the Bronze, Silver, and Gold service levels in TABLE 1» are designed to cover a base foundation for most of the customer's needs. Meanwhile, a-la-carte options help the solution provider to easily and effectively supplement its standard offerings so that it meets nearly any customer needs.
  • Step 730 in FIG. 7 involves understanding customer challenges and communicating solutions.
  • the solution provider must understand the issues and challenges its customer is facing, so that it can position its comprehensive managed services offering to address their needs.
  • Some of the customer goals that the solution provider emphasizes when marketing its solutions may include:
  • IT management can be an increasing part of an organization's costs.
  • Comprehensive managed services can enable small and medium-sized organizations to predict and manage IT costs more accurately and successfully. Guaranteed system-wide software and hardware compatibility can simplify decisions about future directions for the organization.
  • Automated update management can greatly simplify system maintenance by making it much easier to apply critical security fixes quickly and consistently, thereby minimizing the risk of virus attacks and other security breaches.
  • Standardization and routine maintenance helps to ensure .reliability and consistency throughout an organization. This can enable improved problem identification and resolution, enhance employee productivity, and lower employee stress.
  • step 740 in FIG. 7 developing sales and marketing material is an important part of developing a comprehensive managed services marketing plan.
  • the solution provider :
  • Brochures are an affordable and familiar way to get a message to a target market. Brochures can provide a high-level overview of a solution provider's comprehensive managed services offerings which makes customers interested.
  • the solution provider incorporates brochures in its marketing strategies by using a them as a follow up to cold- calling a prospective customer, including them in a direct-mail campaign, and distributing them at events.
  • Case studies present examples of real deployments. Case studies enable the solution provider to show concrete results and benefits of transitioni ⁇ g to comprehensive managed services.
  • the solution provider creates case studies to chronicle events that take place in a customer's environment during the transition to managed services. When the solution provider begins offering comprehensive managed services, it works with a satisfied customer to build an effective case study that it can use in its sales and marketing efforts.
  • the solution provider can offer its customer a discounted rate for receiving managed services
  • Web sites can help the solution provider's business with marketing and customer service. External web sites are generally accessible all the time and can promote the solution provider's company to a global audience. The solution provider can update Web content quickly and easily, and reduces the need to print materials. When the solution provider design a customer-facing Web site, it may consider the following goals:
  • Company awareness Provide a single portal to the company's missions, culture, vision, and goals.
  • an intranet Web site enables the solution provider to provide employees and authorized affiliates quick access to material required to complete their work. If the solution provider takes a virtual data center approach to offering managed services, its support staff may be in many different locations. In such cases, a strong intranet Web site can help ensure all staff members have ready access to the most up-to-date information while keeping that information secure through role-based access control. In addition to keeping employees well connected, an intranet site can help reduce operating costs for printing and document distribution, improve collaboration, enhance individual productivity, support information management policies, and protect confidential information while keeping it accessible to appropriate staff.
  • the intranet Web site design is task-oriented. It provides straightforward navigation and enables easy content updates.
  • Content for an intranet Web site may include:
  • Sales templates may provide a framework that includes:
  • the solution provider's staff may use sell sheets to communicate marketing information to customers. Creating and maintaining accurate sell sheets keeps staff members and customers informed about the solution provider's latest services and the value that each of the services provides. The sell sheers may also be distributed directly through the mail, e- mail, or an external Web site to new or existing customers as part of a marketing outreach. Sell sheets for external distribution may include:
  • the solution provider may also use a pricing guide, which is an internal tool that provides a clearly organized description of the pricing model and options for managed services.
  • the set of available pricing model options may be broad and flexible. Pricing options may include include:
  • the solution provider may also itemize its a-la-carte offerings to enable its sales team to sell an individual component and add it to an existing agreement.
  • the pricing guide is simply used as a starting point, and final pricing may vary.
  • the solution provider may prepare a Frequently Asked Questions
  • Guidelines for customer presentations may include:
  • Step 750 of FIG. 7 illustrates that developing internal training is also a component of developing a comprehensive managed services marketing plan.
  • a comprehensive managed service offering introduces new knowledge requirements for the solution provider's staff.
  • a training plan provides the staff with skills essential to implement, operate, manage, and sell managed service offerings.
  • An internal training strategy also helps manage the organizational and cultural changes brought about by offering comprehensive managed services.
  • the solution provider provides internal training and support to facilitate effective incident response.
  • the organization develops in-house training and manuals that detail the overall process, roles and responsibilities, as well as system specifications.
  • training focuses on both soft and technical skills. Failure to set aside time to build, maintain, and foster this knowledge limits the solution provider's efficiency and market success.
  • Target market and trends Provide current market trends and analysis on managed services to build awareness and understanding of the position of managed services.
  • Adopting the industry-standard Information Technology Infrastructure Library (ITIL) framework can help the solution provider systematically apply best practices to keep its customers' IT assets performing at peak efficiency.
  • ITIL Information Technology Infrastructure Library
  • the ITIL approach focuses on two main areas of providing managed services: service support and service delivery. Service support practices are focused on operational goals while service delivery components are tactically oriented.
  • Configuration management defines standards for recording configuration items (CIs) and specifying relationships between CIs.
  • Incident management processes handle events that are not part of the standard operation and which cause or might cause a service disruption or reduce quality of service.
  • Release management controls the introduction of approved changes such as deploying a new service or application to address a customer challenge.
  • Service level management maintains quality of service through continuous monitoring and analysis and defines steps to take when service quality problems are identified.
  • Capacity management monitors and analyzes the performance of all managed services and facilitates both internal and external reporting.
  • Availability management optimizes IT infrastructure to deliver a cost-effective and sustained level of availability.
  • Continuity management identifies the minimum requirements to support the customer, determines how much the customer might lose because of a disaster or other service interruption, and defines escalation processes based on the identified loss.
  • the solution provider adapts ITIL standards to its needs to improve its customer communications and operational efficiency. To benefit from applying ITIL standards, the solution provider plans carefully and ensures its organization is committed to the, change. The solution provider ensures that its executive staff is committed to these new practices. If the organization implements ITIL, or any other industry standard, full internal support is required. Executive staff needs to believe in the process and convey the value to the entire organization to ensure successful adoption.
  • the sales staff pfays a role in positioning the solution provider's offerings in the market, so they also know the customers' needs and challenges. By addressing customer challenges in the sales training, the solution provider gives the sales staff a tool for improving performance. The sales staff understands that closing deals depends on offering a customized solution with clear benefits and quantifying the return on investment that customers can gain through managed services.
  • Customer liaisons are responsible for providing high-level relationship management with customers as advocates for the comprehensive managed services offerings. Because customer liaisons are senior sales staff, their training should include all material offered to the general sales staff. Because customer liaisons work with customers to ensure that managed services engagements are successful, their training emphasizes soft skills such as presenting solution strategies and persuading customers that proactive systems management is a valuable investment.
  • System engineers provide solution recommendations based on an analysis of customer needs. They are responsible for monitoring the strategic direction and growth of solutions from both a technical and financial perspective. They stay current with both technology changes and the competitive marketplace. They also assist in defining, planning, and overseeing technical and operational solutions and requirements for the organization and customer. Because their work affects all other aspects of offering comprehensive managed services, system engineer training provides overviews of ITIL, project management, and sales best practices.
  • Project managers ensure that projects are delivered on time, do not exceed the budget, and meet both internal quality standards and the customer's needs. Project managers work closely with staff coordinators to ensure that the technical staff is informed of best practices related to each customer engagement and that a cooperative, motivated, and successful project team is assembled for every engagement.
  • the project manager's role spans all managed services functions. Thus, their training includes overviews of all personnel responsibilities and associated training. The training plan for project managers also should include extensive study of ITIL standards.
  • the call center may be the primary point of communications for customers with problems or requests. In this case, the call center staff provides professional and timely customer service. Furthermore, the call center staff is trained in the following areas:
  • Staff coordinators are ultimately responsible for the overall management of the technical personnel, managing and supporting their daily activities. Staff coordinators also provide instruction and guidance to all personnel. Coordinators understand the technical competencies of each of member of the technical staff so they can assign the right people to the right job. Therefore, training for staff coordinators may include the following topics:
  • FIG. 8 illustrates the components of selling the comprehensive managed services solution, which includes targeting potential managed services customers, understanding managed services customization options, positioning comprehensive managed services solutions, and defining and customizing the scope of work.
  • Step 810 in FIG. 8 involves targeting potential managed services customers. Any organization with an IT infrastructure can benefit from implementing comprehensive
  • Medium-sized organizations may have 3-50 servers and 50-500 workstations.
  • the solution provider can start by focusing on a single system and identifying a critical system that currently is performing erratically and disrupting the customer's work. The solution provider can then offer a managed services solution to address the problem. Completing a consulting job to address the single problematic system demonstrates the value of a managed services solution to the customer and may provide an opportunity to sell a comprehensive managed services solution.
  • the solution provider can find potential managed services customers in a variety of ways. As discussed above, the solution provider may search the existing customer base for organizations matching the criteria outlined above. Other methods exist, however, to find businesses that may be interested in a managed services solution. For instance, the solution provider may find potential customers by looking through, the job postings to identify seeking IT staff.
  • the solution provider may employ cold calling to find customer.
  • the solution provider researches small and medium-sized organizations in the geographic service area. After obtaining a general understanding of the organizational background for each prospect, the solution provider directly calls the prospect using a sales script which delivers a short message focusing on the cost savings and security benefits of a managed services solution.
  • the solution provider may also schedule an onsite meeting to educate a prospective customer about the solution provider's organization and. the benefits of the managed services offering.
  • the discussion with the prospective customer may begin with a series of open-ended questions, which may encourage the prospective customer to consider a comprehensive managed services solution more closely:
  • the solution provider may also use web seminars as a convenient forum to find interested customers.
  • a web seminar requires customers to dial into a conference call while simultaneously logging onto a web site to view a presentation.
  • This method can provide many of the benefits of in-person discussion without the demands of travel.
  • Web seminars can shorten the sales cycle and save money on facilities, travel, promotional materials, refreshments, and employees' time.
  • a Web seminar should last 30-60 minutes and the major components may include:
  • a traditional live seminar can be used in place of the web seminar.
  • the presentation at a live seminar may be organized like the web seminar.
  • live seminars enable customers to meet the solution provider's staff and encourage networking among attendees.
  • the solution provider may employ a marketing campaign, which may include any of the following:
  • step 820 Another component in selling the comprehensive managed services solution is shown in step 820 as understanding managed services customization options.
  • the solution provider's success in selling managed services depends on the sales team's ability to align the solution provider's offerings with customer needs. Both the sales and technical teams must be well versed in the details of the solution provider's offerings and able to identify each customer's challenges.
  • step 830 another aspect of selling the comprehensive managed services solution is positioning comprehensive managed services solutions. This step involves identifying customer needs, tailoring solutions to meet customer needs, selling comprehensive managed services benefits, and identifying and positioning additional opportunities.
  • the solution provider When the solution provider first engages a prospect customer to sell a comprehensive managed services solution, the solution provider provides an in-depth overview of what the comprehensive managed services solution has to offer and how it will benefit the prospective customer's specific challenges and needs. As the solution provider interacts with a prospective customer, it identifies the prospective customer's needs, tailors a solution to meet those needs, positions the benefits of managed services, and identifies additional opportunities.
  • the solution provider may take a partnering approach, .rather than a sales approach, to let the prospect know that it understands the devices on their network, etc.
  • the solution provider may recommend an assessment that can provide a further understanding of the transition to a comprehensive managed services environment.
  • the solution provider may recommend a phased approach instead of an immediate transition to comprehensive management, especially if the prospect is not an existing customer.
  • the solution provider can ease the customer's concerns about adverse effects on the customer's organization, while also demonstrating that the comprehensive managed services solution can prove improve the customer's IT environment.
  • a phased approach may involve using a specific server or group of servers within the customer's infrastructure for pilot implementation.
  • the solution provider may identify a system that is problematic or one that is essential to the customer's needs.
  • the solution provider may perform the pilot work on a time-and-materials basis before moving the customer to a subscription-based managed services solution. Doing so may demonstrate to the customer that solution provider is willing to customize its services and pricing scheme to address the customer's concerns.
  • the solution provider may propose additional managed service components. These additional components may also be provided in a phased approach. For instance, the solution provider first provides monitoring, alerting, and reporting only. After a period of time, the solution provider then adds patching services. After yet more time, the solution provider manages, analyzes, and optimizes systems, in addition to the first two sets of services. Finally, full administration
  • the solution provider can add components to a customer's solution any time a new need is identified. Below is a list of additional services that may be offered through affiliates or the solution provider itself:
  • Mobile device support e.g. Blackberry, SmartPhone
  • Step 840 shows that defining and customizing the scope of work is another component of selling the comprehensive managed services solution. Every managed services engagement begins as a partnership between the solution provider and its customer. One of the first steps in establishing this partnership is defining and customizing the scope of work that will be provided to the customer. Defining the scope of work minimizes any misunderstanding about what is included in, or excluded from, a managed services engagement. The scope of work defines the services being provided, the duration of time to perform the services, staff roles and responsibilities, and the costs to provide these services. [0264] To create effective scope of work documents, the solution provider defines the customer's needs, customizes the managed service solution, defines service level agreements, and provides financial justification.
  • the solution provider documents the expectations for the solution provider and the customer and define the elements essential to establishing harmonious managed services relationship. [0265] To align managed service offerings effectively with customer needs, the solution provider attains a solid understanding of the customer's environment as well as its organizational culture. The solution provider may understand what the customer requires from its IT environment by collecting information about the following aspects of the customer's environment:
  • the solution provider By documenting the customer's IT requirements and expectations, the solution provider establishes a map for customizing a managed services solution for the customer. This alignment between the solution and customer expectations permits the solution provider to assess and respond to a customer's critical needs. Identifying the customer's needs accurately and understanding how they can benefit from comprehensive managed services enables the solution provider to substantiate and articulate the value to the customer. [0267] Pricing is an important tool the solution provider has to customize solutions to meet the needs of particular customers. Pricing is typically the primary driver behind the type of service solution customers choose. Thus, the pricing is based on the objectives of the customer and created to satisfy their expressed needs.
  • the solution provider may create custom service offerings to address customer requirements that cannot be addressed through a pre-packaged solution.
  • the pre-packaged solution offerings include a complete packaged solution, a per- device solution, and a fee-based solution.
  • a complete packaged solution suits smaller customers that might already have internal IT support.
  • the focus of this solution is to provide remote management and security services to enable the internal IT staff to focus on strategic projects.
  • a per-device solution suits organizations that have an internal IT department or have already made a significant investment in hardware.
  • the solution provider may provide managed services for specific servers without providing the licensing and hardware. This pricing model gives customers the ability to outsource specific aspects of their environment and enables them to focus on strategic IT projects.
  • a fee-based solution suits customers whose infrastructure already includes hardware and software that meet the solution standards or for those customers who are more comfortable with a time-and-materials approach.
  • the solution provider may provide a complete solution including hardware, software, and services. This type of solution provides everything a small organization needs at a low monthly cost.
  • the standard package may include a server, firewall, switch, and UPS device. The customer may decide to own or lease the hardware,
  • Service level agreements specify the quality, capacity, and timeliness of the service expected by customers.
  • An SLA can be a highly effective tool for helping the solution provider and its customers manage expectations, clarify responsibilities, and objectively assess service effectiveness.
  • An SLA defines the boundaries of the engagement in terms of the functions and services that the solution provider provides to its customers.
  • a well-defined service level agreement correctly sets expectations for both the solution provider and the customer, and provides targets for accurately measuring those objectives.
  • a service level agreement improves the delivery of managed services in accordance with the customer's needs and helps sustain customer relationships by setting achievable and realistic expectations and benchmarks.
  • a service level agreement may act as:
  • a communications tool • A communications tool. A service level agreement assists in achieving a mutual understanding and opens up communications to build stronger relationships.
  • a conflict prevention tool A service level agreement helps to avoid and manage disputes by providing a shared understanding of needs and priorities. If conflicts occur, they can be resolved more expeditiously because expectations are documented.
  • the managed services organization should set a predetermined frequency both internally and with customers to review and assess the services being provided, and negotiate any required revisions.
  • the solution provider helps the customer justify the cost of the employing the model.
  • the solution provider may perform both a cost analysis and return on investment analysis for the recommended solution. Because customers are concerned about the value
  • the solution provider may emphasize, -particularly in a scope of work document, the following efficiencies of a comprehensive managed services solution:
  • FIG. 9 illustrates the steps for building the comprehensive managed services process. The steps include developing a managed services transition plan, developing internal communication processes, and developing external communication processes. [0281] As shown in step 910, developing a managed services transition plan involves documenting a site survey process, documenting a managed services technical design
  • the solution provider determines the scope of the managed services solution as described above, the solution provider performs a site survey and documents the existing environment. This documentation forms the basis for the migration plan, the support agreement, and the cost estimate.
  • the level of detail and scope of the site survey depends on the managed services the solution provider deploys for the customer. Managing a single IT asset requires a detailed understanding of only a few specific aspects of the customer infrastructure, and has little or no interaction with other aspects of the customer network infrastructure. For instance, an offering to manage e-mail spam filtering requires a detailed understanding of the domain names the customer has registered, which ISPs host Msolution provider records, and internal and external mail flow, but is not concerned with other aspects of the customer's network, such as which servers host terminal services or what operating system the customer's workstations are running.
  • managed services offerings generally require detailed and complete information about the customer's existing infrastructure.
  • a managed services offering that includes outsourced management of several existing servers require a great deal of information about the services those servers provide, how the servers are currently configured, and how the servers are currently managed and
  • the site survey includes information about customer practices that affect the covered device.
  • a managed services offering that is based on the implementation of new software also requires a site survey to determine what interaction the new software will have with existing systems, and how any existing work processes (e.g. disaster recovery or backup) will be affected by the implementation.
  • the design of each customer's managed services environment may be a unique solution created by a joint effort between the solution provider and the customer. Factors that might affect solution design includes the customer's current level of sophistication, its internal IT support capacity, and its organizational needs.
  • the solution provider may recommend a standard core offering of services with a few modifications to meet the customer's needs.
  • Standard core offering may be preferable, because it enables the solution provider to develop a large base of standardized customer environments that can be support easily with a small staff.
  • the overall solution may involve more customization, and as such, may be designed by a team of experts in their respective fields. For many customers, the design might require a senior-level network architect with several years of; experience.
  • Building the comprehensive managed services process may include documenting the process as a flowchart. As described above, implementing comprehensive managed services solution may consist consists of the following phases.
  • FIG. 11 illustrates an example of a flowchart that summarizes how the sales, engineering, and operations teams work together to sell and implement a managed services offering.
  • the migration plan is a step-by-step plan to move the customer fram its current environment to the managed services environment.
  • the migration plan can be as simple as installing a firewall or as complex as a complete network re-design that requires formal project planning and a large deployment team.
  • the migration plan should be written by the staff member who develops the solution design, and should include enough specific information for the customer to plan ahead for downtime and any necessary training for end users.
  • a managed services migration plan is different from a typical consulting engagement.
  • consultants are hired to produce a specific result dictated by the customer, or consultants might perform a needs assessment and develop some general recommendations.
  • the end-state of the migration plan is not defined by the customer, but rather is defined by both parties during the creation of the managed services agreement. Another way of looking at the managed services migration plan is that the end-state is the point where the requirements of the customer agreement can be met and the managed services support team takes over control of the covered devices.
  • a pilot implementation may be advantageous, but is required only if the scope of the change is large or the sensitivity of the customer is high.
  • the solution provider and the customer decide whether to deploy a pilot implementation.
  • An important factor in making this decision is risk. For instance, if there is a risk of significant downtime or data loss, the solution provider may test the solution either in a lab environment or with a limited group of users in a pilot implementation. The solution provider explains the risks of an enterprise-wide implementation and the time and resources required to conduct a pilot test, so the customer has the necessary information to decide on a pilot implementation.
  • the solution provider After the solution provider implements a managed services environment, the customer must formally agree that the deployment meets the requirements set forth in the SLA. Functionality acceptance, is an important step, because it provides an opportunity for the customer to test the deployment, verify that the managed services meets requirements, and raise any concerns about functionality. By accepting functionality, the customer is agreeing that the solution has been implemented as planned. This provides important documentatiqn in the event of a disagreement later in the relationship. [0297] After the customer has accepted functionality, the solution provider begins ongoing operation of the managed services environment and assumes control of the systems and services covered by the SLA. At this point, change management processes and both parties' responsibilities under the SLA are enforced. Billing may also begin on the date the client formally accepts functionality.
  • Functionality acceptance also serves as the final checkpoint for the solution provider to verify that the new configuration meets technical requirements for ongoing support and management.
  • the solution provider's managed services team tests all remote management, monitoring, and support components to ensure proper installation, configuration, and functionality before the solution provider accepts functionality. After the customer and the solution provider's managed services team have accepted functionality, the solution provider becomes responsible for meeting the requirements of the SLA. [0299] Regardless of the level of service desired, each customer expects the solution provider to have a comprehensive recovery plan in the event of a hardware failure or other emergency.
  • Redundancy may be employed to minimize hardware failure or unavailability due to a power spike or outage.
  • Redundancy is analyzed for cost benefit, but basic forms of hardware-based redundancy are generally cost-effective. For. example, a simple hard drive failure in a server might require a new hard drive to be ordered. The new drive may not arrive for several days, and once available, a technician is required to perform the replacement (potentially pulling them from a billable engagement elsewhere). Even if hardware is under warranty, the cost of dispatching a technician likely outweighs the cost of the spare drive, not to mention the risk to the customer relationship posed by the downtime. [0301] . Redundancy can also be incorporated into offerings with no hardware components.
  • support processes with redundant parallel paths can be employed.
  • a managed service to monitor a server and troubleshoot errors remotely must have some way, such as e-mail or a text message to a pager or mobile phone, to notify support staff in the event of an error.
  • the solution provider may set up a redundant path to alert support staff via both paths to ensure receipt, or to notify via pager with a follow-up alert via e-mail if the alert is not acknowledged in a set amount of time.
  • the solution provider may design systems to escalate automatically to a backup staff member if an alert is not resolved in a set amount of time by the person on duty.
  • the solution provider also designs each offering with a recovery plan in case of total failure.
  • a recovery plan applies typically to hardware, such as a firewall that will not boot after a lightning strike or other catastrophic failure.
  • Standardization and effective change management are the keys to quick recovery in this event.
  • employing firewalls with a standard configuration means that the solution provider can build a replacement quickly using assets already on hand. Therefore, recovering from a failed firewall involves retrieving a standard hardware configuration from inventory, following the standard build process, and then referring to the change management logs to reconfigure whatever minimal changes were applied after the firewall was initially placed on the customer site. While downtime is sometimes unavoidable, recovery is much quicker and easier if disaster recovery plans exist.
  • step 930 involves developing internal communication processes, which may include documenting an external change management process, documenting an external configuration management process, documenting an external release management process, documenting an external incident management process, and documenting an external problem management process.
  • the solution provider bases a communication management strategy on five major processes: change management, configuration management, release management, incident management, and problem management. Organizing communication management strategies around these five processes allows the solution provider to accommodate a wide variety of customers with differing needs while maintaining consistency that promotes internal efficiency and enhances customers' sense of the solution provider's professionalism.
  • IT systems are dynamic and always changing. Providing effective managed services means that change must be handled smoothly and continuously.
  • a formal change management process ensures that the solution provider tests all changes against formal standards and methods and provides a record of changes.
  • a well-designed change management process also schedules changes in a timely and non-disruptive manner.
  • a simple internal change management process allows the solution provider to be more flexible in accommodating customer needs and requirements.
  • a simple but effective process may be designed with three components: change requests, administrative authorization, and final review.
  • Change requests can by initiated by the solution provider's internal staff or by customers. Most internal change requests involve proactive maintenance, such as operating
  • the change request process begins with a request for change (RFC).
  • the solution provider establishes a standard format for RFCs that record all pertinent information regarding the proposed change.
  • a standard RFC includes a unique identifier, an identification of the problem or need, a description of the desired result, parties potentially impacted by the change, the process for making the change, and a proposed deadline for the application, of the change.
  • a standard RFC also includes the service continuity plan in case of failure, the cost of making the change, the budget amount for approval and sign-off, and the priority for the proposed change.
  • the RFC contains sufficient information to enable a change manager or review committee to assess the change for authorization.
  • Each new RFC is screened by a change manager who can provide administrative authorization for further work.
  • the solution provider establishes permanent, full-time change managers or assigns the role to technicians with skills pertinent to each RFC.
  • change managers who discover incomplete or inaccurate information contact the originator of the RFC to find the full and correct information. Change managers also review the priority assigned to the RFC and change it if appropriate.
  • the last step of administrative authorization is to approve or reject an RFC. Depending on both the impact of the change and the standards set at the client's site, an RFC may be released immediately after administrative authorization. If the request for change is rejected, it is considered closed. Upon receipt of rejection, the RFC originator decides to withdraw the request or submit a new RFC for review.
  • the solution provider may also require additional authorization by a review committee when the RFC poses a potentially high impact on a customer organization.
  • Review committee members should have strong experience with the context of the RFC so they can provide accurate projections of the results. Ensuring that proposed changes are scrutinized thoroughly is crucial before releasing a change to a production environment. .
  • the pace and volume of configuration changes will vary from customer to customer, and managing those changes effectively is essential to the solution provider's long- term success.
  • the configuration management process identifies, controls, and tracks all
  • Effective configuration management can ensure that only authorized components are used in the IT environment and that all changes are recorded and tracked. Effective configuration management requires proper organization of change records for easy future reference.
  • the solution provider may base a configuration management strategy on formal records called configuration items (CIs) that isolate and define the various components of both customer systems and internal systems that are being used to serve that customer.
  • CI configuration items
  • a CI is any element of an IT system (hardware, software, or documented process) that is formally defined and managed. CIs may be very simple, such as a brand of monitor tp purchase, or something much more complex, such as an operating system. A common challenge that many organizations face is maintaining hardware and software standards among their various departments.
  • the solution provider can record every system element, from server hardware to system backup procedures, as a CI to improve overall management.
  • CMDB configuration management database
  • a CMDB provides a concrete tool that enables management to oversee infrastructure and maintain standards. When pertinent information for each CI is clearly present, revealing patterns in how CIs interact may be discovered.
  • a CMDB can help standardize platforms and avoid implementing redundant processes and applications. For example, if a server needs to be imaged, a technician can access the CMDB to check for documentation on the standard imaging process.
  • Release management is employed to handle deployment of changes after they are authorized, developed, tested, and packaged. The release management process ensures that all changes are deployed successfully into the production environment with minimal service interruptions.
  • the release management process may be handled, at least in part, by the change manager. After all submitted changes have been prioritized and particular change teams created, the release process is documented and implemented.
  • Incident management is an important process that provides the solution provider with the ability to identify, record, and resolve the issue to minimize any negative business impact. The process also provides. management with detailed and accurate information on the incidents that are consistently affecting the organization. The incident management process ensures that the solution provider's support resources are focused on issues that have the highest level of urgency and potentially the greatest impact on business.
  • Past incidents recorded in the centralized repository or CMDB may provide information to help resolve a current incident, thus saving significant time in troubleshooting and returning the system to normal operation more rapidly.
  • incident records can be used to identify network trends and problem areas, so that the solution provider's staff can be proactive and prevent serious issues from developing and interrupting business.
  • Methodical problem management helps the solution provider to determine the root causes of many incidents and address problems by making changes to internal processes, procedures, or the solution provider's infrastructure. To resolve a pattern of related, problems, the solution provider may reevaluate and change configuration standards or user practices. As such, problem and change management work side by side. [0322] Because no two organizations are alike, the solution provider may engage with some customers who maintain comprehensive formal processes, some who have partially formalized their processes, and some who have no methodical approach to IT at all.
  • Step 930 includes documenting an external change management process, documenting an external configuration management process, documenting an external release management process, documenting an external incident management process, and documenting an external problem management process.
  • the solution provider establishes a seamless bridge between its internal and external communication processes.
  • Requests for change (RFCs) and incident reporting between the two sides are based on the same standards and duplicated as configuration items (CIs) for each of the central repositories. If the solution provider is hired to develop its customer's processes from the ground up, it establishes full parity between internal and external communication processes with relative ease.
  • RRCs Requests for change
  • CIs configuration items
  • the solution provider may offer communication management solutions that align the customer's communications processes with the solution provider's processes.
  • the goal of the change management process is to ensure that all changes for hardware, software, and processes are reviewed, approved, and documented in a way that facilitates analysis of the information.
  • Configuration management is the process of identifying, controlling, and tracking all versions of hardware, software, documentation, processes, procedures, and all other components of the IT infrastructure. Configuration management ensures that only authorized components are used in the IT environment and that all changes are recorded and tracked. Whether the solution provider only uses its own CMDB, establishes a unique CMDB for a customer, or links its CMDB to the customer's existing repository for CIs, effective external configuration management maximizes efficiency by strengthening the solution provider's understanding of each customer's environment and standardizing ongoing CI reviews.
  • External release management are an important aspect of external communications processes. Much like the other core management processes, some customers might already have an internal release management process. This redundancy might seem a tedious burden, but it can create a powerful mechanism to promote communication and understanding between the solution provider and the customer by ensuring that released changes meet prerequisites and standards.
  • the external incident management processes need to cover both customers and any affiliates.
  • Proactive monitoring and maintenance are essential to successful comprehensive managed services offerings.
  • the solution provider needs to be able to protect the integrity of its customers' systems and assess usage patterns to anticipate their changing needs.
  • incident reporting might be recorded only in the solution provider's repository or by both the solution provider and the customer.
  • the solution provider ensures that the records are consistent in both systems.
  • FIG. 10 illustrates the steps for providing comprehensive managed services support, which includes establishing managed services expectations, initiating comprehensive managed services, and maintaining comprehensive managed services.
  • establishing managed services expectations is an important aspect of providing comprehensive managed services support. Establishing proper expectations with the customer is critical to a successful managed services engagement, Although the solution provider formally establishes expectations with the customer in a managed services level agreement, expectations may change throughout the duration ' of the relationship between the parties.
  • Comprehensive managed services includes a centrally managed anti-virus solution, and the solution provider specifies the risk points that it scans, which may include e- mail servers, web servers, and workstations.
  • the solution provider informs its customers that the anti-virus software and virus definition files are updated automatically. If a customer uses e-mail, the solution provider that the customer understands that the firewall may be configured to remove specific types of incoming attachments that are commonly associated with viruses.
  • the solution provider updates customers on all aspects of its server hardening, practices which will affect end users, including strong password policies and off-hours limits to certain network resources.
  • the solution provider also has a defined procedure to ensure that security updates are applied promptly and consistently.
  • the solution provider ensures that customers understand that although patches and updates are released often and on no particular schedule, centralized management from the solution provider's organization will
  • the solution provider follows formal change management and configuration management procedures for testing and applying each update. As discussed previously, the customer may also have change management processes with which the solution provider must also work.
  • the solution provider performs regular maintenance on managed devices to ensure optimal performance.
  • Remote monitoring may be the primary method of ensuring that the covered devices are functioning correctly.
  • the solution provider can perform remote monitoring using a variety of methods. Regardless of the monitoring method, however, the solution provider must define and use critical metrics for determining actions.
  • Some basic metrics may include: processor utilization, disk space available (system), disk space available (data), memory utilization, critical or warning alert in event logs, backup failures, UPS alert, threshold critical or warning alerts, virus detection, and firewall attacks.
  • the solution provider's response to an alert may involve remote troubleshooting from its operations center and possibly dispatching an engineer. Another important part of ensuring optimal performance is regular analysis of managed devices.
  • step 1020 involves initiating comprehensive managed services.
  • the solution provider need to begin providing regular services.
  • the solution provider may provide a health check, implement patching, and implement management processes for configuration changes,
  • the first step after initially deploying a managed services environment is to run a basic systems health check to ensure that there are no patches or updates that should be applied.
  • vendor web sites might detect available patches, vendors might send e-mail announcing updates, or they might provide scanning tools that will tell the solution provider when patches are available.
  • the solution provider After checking system health for the customer, the solution provider is ready to implement the patching policies that are defined in the SLA.
  • the solution provider will patch systems frequently for its customers. Timely application of a given patch is the optimal goal, but it is imperative to exercise caution when releasing a patch to the production environment.
  • a single patch can have adverse effects on an entire network, but customers might not always appreciate the risks and can become concerned if they know a patch is available but is still being tested before deployment.
  • the solution provider's communication management process provides an, efficient solution to these potential conflicts.
  • an RFC needs to be created and sent for an administrative and technical review.
  • the RFC will need all pertinent information that applies to the patch. Items covered in an RFC for a patch may include:
  • RFCs must be sent to the designated change manager for review. Before approving the change, the change manager will decide what release requirements are necessary and whether or not the requirements have been met.
  • the solution provider should save all RPCs in its configuration item (CI) repository for future reference. Change managers may want to review past RFCs involving similar patches. To understand which users might be affected by the change, the change, or maintenance, windows applicable to given devices, or whether or not a given system has the resources to accommodate a change, the solution provider may access its configuration management database for assessment sheets.
  • the RFC is archived in the solution provider's configuration item repository.
  • the outcome of the RFC will be included as well so that as future incidents or needs arise, operations will be enhanced with an updated knowledge base of CIs and procedures already encountered or that might affect release of the change.
  • the release manager completes a final review of the testing process and grants a release approval.
  • incident management is intertwined with the request to patch from beginning to end.
  • An integrated incident management process first detected the need for a patch. In the case of a critical patch, it is crucial to determine the need for it as soon after release as possible.
  • the incident management process monitors system resources and reviews error logs. Anything detected by the monitoring tools and procedures is noted. Even if release management decides there are no significant errors detected during the test, any alert is noted and can be referenced after patch deployment.
  • RFC submission Include as much detail as possible without providing unnecessary information. The fewer times an RFC needs to be returned for updates or clarification the quicker the change can be processed.
  • Configuration items Standardizing CIs will improve the efficiency in which they are created and understood.
  • CMDB Configuration Management Database
  • Test environment Setting strict guidelines for the test environment is crucial for successful change deployment. Ensure that the customer's production environment is properly represented in the test lab.
  • Monitoring Establish a monitoring solution that provides reliable alerting. The more variables the monitoring solution can track, the more effectively proactive care can be provided to customers' systems.
  • step 1030 of FIG. 10 another component of providing comprehensive managed services support involves maintaining comprehensive managed services, which includes reviewing monthly reports, findings, and recommendations.
  • Reviewing monthly reports helps the solution provider improve internal processes. Moreover, reviewing reports together with customers promotes the customer's appreciation of the value provided by the solution provider's solution.
  • Monthly reports keep customers aware of the actions the solution provider takes and provide a proactive view of network activity and needs. The information included in monthly reports depends on reporting capabilities and the needs of each customer. Preferably, information that is pertinent to the service level agreement is presented. Information such as the monthly incident reports, including incident resolutions and the status of any current RFCs, are also preferable. These reports should provide an attractive, user-friendly presentation of data that can facilitate proactive decisions about network resources. In addition to any technical data, an executive summary that clearly describes the technical data presented in plain language is also preferable.

Landscapes

  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

Un modèle complet de services gérés permet à une entreprise de services de technologie de l'information tierce (IT) de prendre en charge le contrôle, l'administration et la maintenance d'une infrastructure IT commerciale. Le coût de la solution est prévisible et inférieur au coût de maintenance des mêmes tâches de contrôle, d'administration et de maintenance par du personnel IT interne. Le modèle fournit à l'entreprise de services IT une source de revenus prévisible à long terme. Dans un système donné en exemple, l'entreprise de services IT tierce offre différents forfaits de services gérés, et l'on facture le client selon un programme de fixation des prix lié à l'abonnement. Alors que les forfaits peuvent contenir un ensemble prédéfini de services, le modèle de services gérés permet également de sélectionner des services individuels à la carte pour créer une solution personnalisée qui répond exactement aux besoins et aux exigences du client. Le modèle de services gérés permet également à une entreprise de services IT tierce de faire un partenariat avec des entreprises IT pour fournir ces services.
PCT/US2006/034878 2005-09-07 2006-09-07 Procede et systeme de surveillance et de gestion a distance de reseaux informatiques WO2007030633A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US71433605P 2005-09-07 2005-09-07
US60/714,336 2005-09-07

Publications (2)

Publication Number Publication Date
WO2007030633A2 true WO2007030633A2 (fr) 2007-03-15
WO2007030633A3 WO2007030633A3 (fr) 2009-04-16

Family

ID=37836471

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/034878 WO2007030633A2 (fr) 2005-09-07 2006-09-07 Procede et systeme de surveillance et de gestion a distance de reseaux informatiques

Country Status (1)

Country Link
WO (1) WO2007030633A2 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120136810A1 (en) * 2010-11-30 2012-05-31 Ranvir Singh Systems and methods for locally outsourcing work
WO2013070178A1 (fr) * 2011-11-08 2013-05-16 Bellini Alejandro A Logiciel de téléphone cellulaire personnalisé permettant de contrôler un ordinateur avec connexion internet pour des jeux interactifs
US20140195288A1 (en) * 2010-11-30 2014-07-10 Ranvir Singh Systems and methods for locally outsourcing work
US8943464B2 (en) 2013-03-05 2015-01-27 International Business Machines Corporation Continuous updating of technical debt status
US9262145B2 (en) 2011-10-31 2016-02-16 Hewlett Packard Enterprise Development Lp Remote software deployment across a network
US11513817B2 (en) 2020-03-04 2022-11-29 Kyndryl, Inc. Preventing disruption within information technology environments
US11776176B2 (en) 2019-04-19 2023-10-03 Microsoft Technology Licensing, Llc Visual representation of directional correlation of service health

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020042731A1 (en) * 2000-10-06 2002-04-11 King Joseph A. Method, system and tools for performing business-related planning

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020042731A1 (en) * 2000-10-06 2002-04-11 King Joseph A. Method, system and tools for performing business-related planning

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120136810A1 (en) * 2010-11-30 2012-05-31 Ranvir Singh Systems and methods for locally outsourcing work
US20140195288A1 (en) * 2010-11-30 2014-07-10 Ranvir Singh Systems and methods for locally outsourcing work
US9262145B2 (en) 2011-10-31 2016-02-16 Hewlett Packard Enterprise Development Lp Remote software deployment across a network
WO2013070178A1 (fr) * 2011-11-08 2013-05-16 Bellini Alejandro A Logiciel de téléphone cellulaire personnalisé permettant de contrôler un ordinateur avec connexion internet pour des jeux interactifs
US8943464B2 (en) 2013-03-05 2015-01-27 International Business Machines Corporation Continuous updating of technical debt status
US8954921B2 (en) 2013-03-05 2015-02-10 International Business Machines Corporation Continuous updating of technical debt status
US11776176B2 (en) 2019-04-19 2023-10-03 Microsoft Technology Licensing, Llc Visual representation of directional correlation of service health
US11513817B2 (en) 2020-03-04 2022-11-29 Kyndryl, Inc. Preventing disruption within information technology environments

Also Published As

Publication number Publication date
WO2007030633A3 (fr) 2009-04-16

Similar Documents

Publication Publication Date Title
US20060161444A1 (en) Methods for standards management
US20060161879A1 (en) Methods for managing standards
US8200527B1 (en) Method for prioritizing and presenting recommendations regarding organizaion's customer care capabilities
US20070276674A1 (en) Defining and sizing feasible approaches to business needs within an integrated development process
CA2386788A1 (fr) Organisation de fonctions de technologie de l'information
US20070073572A1 (en) Data collection and distribution system
US20110106569A1 (en) System and method for automated risk management appraisal
WO2007030633A2 (fr) Procede et systeme de surveillance et de gestion a distance de reseaux informatiques
Thejendra Practical IT Service Management: A concise guide for busy executives
Bowen et al. Sp 800-100. information security handbook: A guide for managers
Park et al. Case study on estimating the financial impact of IT process alignment
Spencer et al. Technology best practices
Spasic et al. Information and Communication Technology Unit Service Management in a Non-Profit Organization Using ITIL Standards.
WO2001008004A2 (fr) Systeme, procede et article manufacture pour determiner les niveaux de capacite d'une zone de processus de surveillance a des fins d'evaluation de processus dans une etude de maturite operationnelle
Rae A guide to SLAs
McDowell introduction to “
Van Bon ITIL® 2011 Edition-A Pocket Guide
Korfage Improvement of the current Service Level Agreement of Denko-ICT
Herold The shortcut guide to improving IT service support through ITIL
GONZALEZ PROJECT MANAGEMENT PLAN FOR THE HELP DESK IMPLEMENTATION IN SECRETARIAT OF EDUCATION DISTRICT OF BOGOTÁ, COLOMBIA
ALBULESCU et al. Service operation management in it domain. comparing two it companies processes, flow and results
Freitas Applying Robotic Process Automation to Improve Customer Operations at Vodafone Portugal
WO2001008035A2 (fr) Systeme, procede et article manufacture de verification d'un processus a maturite operationnelle par determination du niveau d'aptitude dans un domaine de processus traitement d'administration utilisateur
Herold The shortcut guide to IT service management and automation
Hyder et al. eSourcing Capability Model (escmSM) for IT-enabled Service Providers v1.

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06814283

Country of ref document: EP

Kind code of ref document: A2