General discussion

Locked

Best Practices for Installing Hardware

By jim.mackley ·
Does anyone have a checklist or best practices for installing IT hardware?
I need information on how people bring
new equipment into a raised floor env.
IMAC(Install, Moves, Adds, Changes)
Lead time, Cables, Power, Install, Removal -
I would like to compare notes and policies to see if we can improve this process?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Best Practices for Installing Hardware

by Shanghai Sam In reply to Best Practices for Instal ...

Jim,
Start by planning ahead. Get representatives from building services, telcomm, involved vendors and IT operations together at least 30-45 days ahead of time. Mostly to create an awareness of your project and identify any schedule conflicts due to prior work commitments. If you need an external carrier to drop in data circuits, give yourself 45 days. Allow 2-3 weeks or more for electrical work depending upon the depth and workload of the staff. Don't forget to plan for data cabling. Allow a week or so for small IMACs and consider a certified wiring contractor for large jobs involving patch panels and multiple runs. Notify network administrators of any IP addressing needs a week in advance. If possible, obtain/create floor diagrams showing electrical and data outlets and current equipment placement on the floor. Know your operational schedule - identify those times when it is least intrusive to your business to perform the installation and any outages necessary to bring the new equipment online. Once you have your schedule, communicate it to upper management, then department managers and finally the end users. If management knows about it, they can be supportive if they get questions from end users. Communicate theoutage schedule, the impact to the organization/users and the benefits of the change. We have a position to coordinate and manage all changes within the IT organization. These are the guidelines we've followed and they've paid off in terms of easier IMACs and better perception of IT within the rest of the company. To go over this in more detail, send me an e-mail. Chris Kilday (chris.kilday@ctg.com)

Collapse -

Best Practices for Installing Hardware

by James_Randy In reply to Best Practices for Instal ...

Just do it.

Collapse -

Best Practices for Installing Hardware

by jim.mackley In reply to Best Practices for Instal ...

The question was auto-closed by TechRepublic

Collapse -

Best Practices for Installing Hardware

by dlw6 In reply to Best Practices for Instal ...

The things you're asking about depend on what you can directly control and what you have to coordinate with others. Having said that, here are some ideas that apply to nearly any situation.

If time permits, start small. Set up a prototype of your new HW, that is one or two systems. Install and connect it, work the bugs out, and keep copious notes on how it went.

After you share these notes and lessons learned among your team, you'll be in a position to make your plan. You can bring in all the new HW and make it work without wasting a lot of time and effort.

Good fortune,
Don

Collapse -

Best Practices for Installing Hardware

by jim.mackley In reply to Best Practices for Instal ...

The question was auto-closed by TechRepublic

Collapse -

Best Practices for Installing Hardware

by jim.mackley In reply to Best Practices for Instal ...

This question was auto closed due to inactivity

Back to IT Employment Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums