In the long run, this approach can simplify IT operations and lower costs. Defined services can help keep IT focused on important tasks and let the tech group devote more time to critical operations. Standard deliverables mean no one has to reinvent similar wheels for different customers.
But there are risks as well. Anyone who's ever had an online order lost or delayed with no explanation will think twice about using that vendor again. The same goes for IT services. Each service offered must be described in detail in the service catalog, and specific performance indicators and other metrics have to be applied.
A catalog approach can be extremely difficult to implement if your organization has multiple engineering teams supporting services that are unique for specific customers. Few such teams follow a standard process to document or track nonstandard services, and they tend to fall off the operational radar screen. Changes to these nonstandard services can break them and cause performance outages, SLA violations, and other performance issues.
In larger organizations, just tracking down custom-built services can be a major battle--especially if the engineers responsible for them are no longer around.

(click image for larger view)
Page 2:
Keep It Simple
![]()
1
|
2
|
3
Next Page »
Stay connected and informed by visiting our Enterprise IT Community!

Become a member today for instant access to free InformationWeek research, expert advice, peer perspectives, and more on the following topics:
- Application Performance Management (APM)
- Security Management
- Mainframe 2.0
- IT Automation
- Service Assurance
Also, visit our Government, Retail and Financial Services groups to see how these technologies apply specifically to those industries.
NOTE: Offer valid for U.S., U.S. possessions, & Canada only.