35 Results Found
No matter what book or manual you use to study for the CCNA examination, you will see various protocols and processes referencing an RFC. And, although frequently referenced, the RFCs are seldom actually included in the documentation. So, the logical question becomes...
No matter which IT field you're working in, there are several skills that are useful for every IT professional to know. Here, seven experienced IT professionals working in the networking, programming, project management, and security fields, share what they believe a...
As mentioned in last week’s post, interviews that require ITIL Intermediate level knowledge will most likely be targeted to specific process areas and activities. If I interviewed someone for a job that required ITIL Intermediate level knowledge, in addition to other questions about the specific technical responsibilities of the job, I might ask the following questions:
ITIL describes a service portfolio as a collection of the overall set of services managed by a service provider. A service portfolio describes a service provider’s boundaries and promises across all of the customers and market spaces it serves. I like to think of a service portfolio as describing the past, present, and future collection of services offered by a service provider. The figure below shows a high-level view of a service portfolio.
In a recent post, I gave an overall description of a service portfolio and the key components of a portfolio. Here, I will describe how a cloud services provider might implement an ITIL service portfolio. A cloud services provider will regularly have a set of services under development, a set of service in live operation, and a set of services that are retired.
UFFA, which stands for “Use it, Flag it or Fix it, Add it,” is the responsibility of every support professional in the knowledge management process. It comes from the Knowledge-Centered Support (KCS) methodology where knowledge management is based on collaboration and a shared ownership of the knowledge base. Let’s break it down.
Most organizations quickly realize that knowledge management must be integrated with incident management in order to improve the quality of service and the efficiency of providing assisted service. What is not as quickly recognized is the value of integrating knowledge management with problem management.
Young adults unable to find work, employers unable to fill jobs, a recent GAO study that reported substantial declines in telecommunication expertise — there has been a lot of news about the pervasiveness of skills gaps, their causes, the actual impacts and what to do about them. It’s rather confusing, because the term “skills gaps” has been hijacked to politicize an extremely wide range of issues.
Event management, although theoretically different, is fundamentally what most IT organizations refer to as “monitoring.” Monitoring an organization’s environment to determine whether important assets are in the state they should be, and knowing when that state changes, is a very important activity that many organizations spend significant portions of their budget doing.
A strong event management process that is able to detect changes of state throughout an organization’s IT environment is a key aspect of a complete suite of service management processes. Event management ultimately helps an organization maintain control through an understanding of the state of things, and how the state of those things changes in an IT environment.