8 replies
by samuelbrooks
by itdebate
by dlw6
I concur with Mr Brooks.
I worked 18 months in an IT dept where we owned over 100 users, over 100 desktops, and 2 domain controllers but did not own the LAN. We had to call in work orders for any problems or to have ports turned on. It always took longer than if we'd done the work ourselves, and increased the risk of error because of longer lines of communication.
Having said that, it would take a lot of convincing to outsource a LAN -- it's not that complicated and any IT support team can learn to do it.
It is a bit easier to accept outsourcing for a CAN or WAN because of the wider variety of equipment and unique expertise required. You might save time and/or training cost over learning and maintaining the edge equipment yourself.
The fear with outsourcing is security and quality of service. The contract should be specific with respect to the provider's responsibilities and any reparations resulting from failure to meet those responsibilities.
Good fortune,
Don
by itdebate
by itdebate
by mckaytech
I formerly worked for a company that provided remote LAN management services. If understood and implemented properly, these services can be a cost-effective way for SMALL networks to receive maintenance and monitoring that would otherwise not be feasible.
Outsourcing these functions to a reputable company can also provide some stability and insurance against disruption of business in the event of a sudden change of on-site IS personnel. In fact, one of the easiest ways to find customers for these services is to talk with company officials whose networks have been held hostage by a network administrator or where someone has left and taken the passwords with them.
Personally, I would consider outsourcing LAN management either with primary responsibility in the case of a small LAN with no on-site IS presence or with secondary responsibility in a larger LAN with some on-site IS presence.
It is critical, however, to develop a clear understanding of what the service covers and what it does not and that is best accomplished by drafting a rigorously detailed Service Level Agreement that addresses security, response times, roles, responsibilities and a problem clearance procedure.
paul
by itdebate
by itdebate
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending