[c-nsp] Change Management

[Serge Vondandamo]

Hello Brian,

I don't know about any open source product but I my company we do use
Mercury ITG solution (IT Governance)
http://www.mercury.com/us/products/it-governance-center/change-management/

The application runs IT like a business and it has the following
functionalities (I think, each module can be purchased separately):

Demand Management
Portfolio Management
Program Management
Project Management
Financial Management
Resource Management
Change Management
Time Management
IT Governance Foundation
IT Governance Center Services

It works great since it integrates your IT infrastructure and fully
automated using your messaging platforms.

Regards
Serge
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Justin M. Streiner
Sent: vendredi 14 janvier 2005 22:20
Cc: 'cisco-nsp'
Subject: Re: [c-nsp] Change Management

On Fri, 14 Jan 2005, Brian Feeny wrote:

> Can some of you all share how you handle Change Management on your
networks?
> Everything from serious changes to something mundane like changing a
customer 
> IP address.

Where I worked before, large service-affecting changes (code upgrade on 
routers/switches, circuit re-grooms and the like) were discussed in a 
semi-weekly change management meeting.  The change was approved or not 
approved by management and normally the engineer who scheduled the change 
was the one who did the change.  The standard maintenance window was 1 to 
5 AM regardless of the day.

Smaller changes like new customer circuit turn-ups, static routes, 
customer BGP changes, etc could be done on the fly in many cases.

As for the software, we has a homegrown app we wrote in PHP originally, 
then the change management functionality was rolled into our existing 
trouble ticket/case management system.

jms

> I would hope there is some good open source tools for this purpose.
>
> BTW, we already use "configuration management" tools like RANCID, but I am

> needing something that
> people can use to log a change, who did it, why, when, etc, so its
accounted 
> for BEFORE it happens.
>
> Thanks,
>
> Brian
>
> ------------------------------------------------------------------------ 
> ------
> Brian Feeny, CCIE #8036, CISSP    	e: signal at shreve.net
> Network Engineer           			p: 318.213.4709
> ShreveNet Inc.             			f: 318.221.6612
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/