ITIL and PMP Framework Similarities

While ITIL addresses how IT organizations as a whole should operate, PMP addresses how individual projects within the organization should be executed. PMP applies to projects throughout the entire organization not just IT. Both frameworks rely heavily on process and the use of tools to enable consistent execution of processes. The ITIL framework and the project management framework support each other in a way that propels services and operations to a greater level of proficiency. Furthermore, both frameworks address the need to manage quality, risk, and accountability. Most importantly, however, both ITIL and PMP consistently help improve efficiency and usefulness within the organization. ITIL describes the ideal end state that an organization would like to achieve. There are those who believe that if the ITIL framework behaves according to the ideal model, all will go according to plan. Unfortunately, this impractical IT end result is not realistic in the business world - and an organization must implement a framework that allows for individual projects to be completed over months’ time in order to get to the desired end result.

Differences between ITIL and PMP

The differences between the ITIL framework and the project management framework are inconsequential when compared to the overall effectiveness of combining the two. Similarities aside, project management is not specific to IT. The PMP framework, focusing on effective execution of projects, can be applied to any area of any organization. Unlike ITIL, the project management framework does not operate on a lifecycle approach, but is organized into nine key knowledge areas: project integration, scope, time, cost, quality, human resources, communications, risk, and procurement management. As previously mentioned, rather than analyzing the breakdown of each project, the ITIL framework examines the whole picture - a key difference. By taking a larger view of services in the organization as a whole via a lifecycle approach, ITIL sets out to examine service strategy, service design, service transition, service operation, and continual service improvement. Take, for example, an organization that is building and deploying an email service - on one level, ITIL will evaluate what is needed; PMP will then take this information and further break it down into easier-to-manage increments.

Data Center Implementation and build

I was bit fortunate when I participated in a presentation on DC Implementation and build.
After the presentation, I was very much excited about the content & knowledge of the presentation which is not available freely & easily over the internet. Thus I decided to put the content here with some of the my understanding. Most of the IT managers look for the deep secretes of building a DATA CENTER, following are the points which are very much important in terms of the building a Data Center.
1st, How many types of Data Centers?        So, there are 4 types of Data Centers (Tier 1–4, details are easily available over the internet). Tier 1 to 4 Data Center is nothing but a standardize methodology used to define uptime of DC. Primarily these are useful for measuring: DC performance, Investment, and ROI.
Tier 4 Data Center is considered to be most robust and less prone to failures (Downtimes). A Data Center is nothing but a(Power + Cooling + Place) where we keep different networked devices. While constructing a data center we should see that, it is scalable, modular, flexible & simple in design.
Which are most important element/s of the any Data Center?    Following are the most important elements during planning & designing for a new Data Center which will direct the course of action....
A. Stakeholders
B. Scope
C. Space
D. Cost
E. Requirement (individual)
F Compliance
What are the precautions we should follow while building a Data Center?        While building a new DC, there are many things which are of lot of importance, we should follow below design guidelines during the course....
A. Label everything (golden rule)
B. Use RLU (rack location unit) costing
C. Be flexible, for future needs
D. Think modular, for future expand plan
E. Worry about weight, as we are aware that most of the DC does not build on ground floor, so we should think properly for weight of the devices.
F. Keep things covered or bundled to avoid dusting
G. Build raised floor tiles at least of 4 feet
Lets look at Data Center build from the perspective of project management (PMI). Once I was a part of the team where we were involved in planning & designing phase of the DC build project. There are many major areas in any Data Center build project, i.e. Civil work, Electrical work, Fire work, Security & Cooling arrangement. I learned most of the stuff in that project only, following are the some golden learning's....
a. A complete Scope, an approved budget, & an experience team (are the keys to build DC successfully)
b. Insurance and local/ state /country building codes
c. Determining the viability of the project
d. Realistic project & full budget
e. Considerable redundancies of power/services/HVAC/UPS
f. Proper management of account (how will be funds distributed)
g. Future modifications, upgrades, changes
h. Factors in running cost, services, and maintenance contract with supplier
i. Are redundant system really necessary
j. How much will be projected failures (downtimes)
k. Separate NOC/command center
l. What is the best time to bring the facility online (schedule management)
m. Physical space and weight capacity for equipment/device
n. Power availability/grid power
o. Cooling system redundancy to increase uptime
p. ISP Bandwidth type & amount
And for above we should have fantastic Support, processes which are....
A. Location of floor & weight of rack
B. Sufficient power to run racks
C. Humidity in Data Center should be between 40-45% & cooling should be between 18–27c
Ok, its not all, we have something bigger to worry. Lets talk about risk in these types of projects. Till now I have identified following major risks....
A. Ambiguity in the scope of work
B. Not having clear contract/sourcing process
C. Queries from vendor, turns out to be additional work
D. Change management
E. Finance
F. No involvement of delivery team/people during planning or design phase
That's all I have, will be posting more in this topic if I learned/discover new things in this regards.