Capacity Mgmt & Project Mgmt

[SwissTony]

In a push to move to a more pro-active Capacity Mgmt process a stumbling block is within Project Mgmt. We use the SDLC approach, with 5 checkpoint stages, and ultimatley only get a true reflection of requirements at CP3.

There is an overall process of selecting portfolios to be put forward for the coming year - which normally should be completed begining of Q3. However, at that stage there is little to go off interms of forecasting, and budgeting.

My aim now is to push the heads of project management to increase the amount of time that infra get the project requirements and the date it has to be installed.

Possibly not put in the best way, but any suggestions on how to tackle this subject & the Project Mgmt team. As their obvious answer will be that they have to fulfill the requirements of the business as and when they demand.

Any ideas??

[UKVIKING]

SW

What kind of CapMgmt are you doing

telco/ circuits
h/w / network infra
h/w - cpu / memory

the short answer is it depends

I can answer a little better if i have more input
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[SwissTony]

Good point:

Hardware: PCs, Servers, Mainframe, Systems, databases
Network: LAN, WAN, VPN
Periperals: Storage, Printers
Software Licences
& finally human resources - in terms of infrastructure and their capacity to fulfill requirements from the business / projects.

[SwissTony]

& for servers CPU, Memory, Disk Space as basics.

[UKVIKING]

So you are going whole hog

what i did when I had capmgmt - circuits/pointopoint // mpls

1 - establish baseline against b/w for current usage
2 - if circuit is on upgrade for mpls .. get the program mgr to add my data set to the mpls schedule and compare / highlight planned upgrade against current usage
3 - if project was still in dev, get Progmgr to re-calibrate

i used cost as the factor

I worked for the telco which was providing net mgmt service

repeat weekly

for ex

circuit 1 - london to swindon - 2Mb going to MPLS 2Mb / 2 mb physicall /logical.

as the B/w usage was in the 70 % average and increasing every week
the 2 mb / 2mb was too small
the circuit had yet to be order so the order was changed (more money for telco) and scheduled for the next roll out

as there was a 90 -120 lead time this was good
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter