Environment
The client, a Fortune 500 financial services company, relies heavily on technology to automate a majority of the core financial functions. The IT department consists of 1200+ technical staff developing and supporting over 1400 applications across hundreds of varying server platforms deployed to over ten thousand desktops worldwide. Unplanned systems downtime has a significant impact on the productivity of the company and the capability to execute standard business functions.
The objective of the implementation was to streamline the amount of work required to maintain production system health. This primarily involved change management, service management, and configuration management solutions.
Implementation Components
Change Management: Change Control Committee
| Business Problems |
Initiative Summary |
- Production outages due to unknown changes
- Long outage resolution times due to misguided troubleshooting
- Separate, conflicting production changes
- Limited tracking of system change history
- Technical staff not accountable for alterations to production systems
|
- Defined function and structure of the Change Control members
- Modified existing tracking system to mimic future Remedy functions
- Implemented processes to review and coordinate all production changes each week
- Implemented Remedy solution once processes and organization were adopted
- Developed key metrics to determine effectiveness of change control
|
Change Management: Release Management Process
| Business Problems |
Initiative Summary |
- Unconfirmed completion of development tasks
- Non-standard software distribution and installation processes
- Undocumented maintenance/support procedures
- No owner of release management and control
- Non-standard training of support staff and end-users per release
|
- Performed gap analysis on existing release management processes
- Documented production migration requirements for all teams
- Integrated new processes with existing PMO organization
- Mandated all application migrations perform deployment review
- Defined requirements for overall Release Manager role
- Integrated processes with Change Control committee
|
Service Desk: Remedy Implementation
| Business Problems |
Initiative Summary |
- Various systems for tracking incidents
- Non-standard process for issue escalation
- Limited metrics on support performance
- No integration with planned changes
- Undefined support tiers within organization
|
- Performed gap analysis of all support applications
- Designed Remedy module to accommodate client requirements
- Defined and communicated proper tiered support organization
- Developed standard incident management processes
- Migrated internal help desk initially and subsequent tiers as requested
- Developed standard management reports of key metrics
|
Configuration Management: Hardware and Software Repository
| Business Problems |
Initiative Summary |
- No repository of technical hardware assets
- Limited database of approved desktop software
- No tracking of assets and associated incidents
- Limited availability of real time asset data
- No financial tracking capability for hardware asset lifecycle
- Non-standard training of support staff and end-users per release
|
- Define vision of Configuration Management DB for all assets
- Researched existing platform management tools (e.g. LANDesk)
- Defined and built custom Remedy module for software assets
- Define standard processes for maintaining CMDB data
- Developed routine reports from hardware resellers for hardware data
- Customized Remedy module for desktops, laptops, servers, PDA’s, monitors, and printers lifecycle tracking with routine data updates
- Developed custom reports for lifecycle tracking and maintenance
|