Resource Library

As the technology industry has advanced, the professional certification industry has grown alongside it. The Global Knowledge 2016 IT Skills and Salary Report revealed that Cisco, Microsoft, IT service management, ITIL and security certifications are the most lucrative to obtain.

AMC’s television series “Halt and Catch Fire” shows North Texas’ rise as the “Silicon Prairie.” In the 1980s and early 1990s, it’s where IBM PC cloning was explored and where first-person shooter games were created. It’s also the site of the first “logic bomb”—the source of my horror story.

The ITIL® event management process defines three event types: informational, warning and exception. In this post, I will discuss the different event types and give real-world examples of each.

The short answer (and a common one in our industry): it depends. When comparing Cisco IOS with Juniper Junos, the decision to choose one over the other is difficult and often boils down to cost. Of course, there are other factors to consider.

A gap analysis is a tool that ITIL recommends organizations use to compare their current state to some future desired state.

Many I&O leaders and customers see little value from investments in ITIL. Not getting the Return on Investment (ROI) you expect normally comes from using ITIL incorrectly. You, your staff, and your customers must share the same goals and understand exactly what to expect from your ITIL investments. The goal of ITIL is not “business and IT alignment” or “competitive advantage from IT investments.” Instead, its first goal is to stabilize service operation. This builds a base for the second goal: increasing value through service optimization. You must have clear-cut, documented, and managed expectations for each activity, and order is vital. Success requires that you stabilize service delivery before trying to optimize. Focusing on the correct goal and linking each ITIL task to that goal is the correct use of ITIL.

ITIL is generally not prescriptive. In reality, the CSI Register at any given organization might look significantly different than the example given in the CSI book. The fields given in this example are important. 

Organizations that plan for and conduct supplier management according to defined processes and boundaries are more likely to receive predictable, high-quality goods and services from their suppliers in a timely manner.

Regardless of your vendor preference or your experience on the Juniper JUNOS CLI, assuming you have a point of reference to another vendor, your first thought when experiencing JUNOS is, “I have been here before.” The CLI is familiar, convenient, and polished. The similarities between JUNOS CLI and another CLI such as Cisco’s IOS are not what I want to focus on here however; it is their differences I want to focus on. But first, when you connect to a JUNOS powered device and access Operational Mode (see Brad Wilson’s blog post Introduction to Juniper Junos), it looks very much like the User EXEC Mode in IOS. In fact, there are a lot of JUNOS commands that are very much like the IOS User EXEC Mode commands.

Previously I discussed service providers and their risks in the example of my involvement with a landscaping company. ITIL clearly states that services, “…deliver value to customers by facilitating outcomes customers want to achieve…” However, sometimes organizations and people focus on outputs as opposed to outcomes, which sacrifices some of the value of the service. This leads to a question, what is the difference between an outcome and an output?