digitalb3-ga,
Ill cover here the basic reasons that corporate IT departmentseven
competent onesneed system integrators in certain situations.
One of the main reasons IT Departments call upon system integrators is
when installing/configuring a new system for the first time. Most IT
Departments run the basic day-to-day computer and telephone system
operations for a company, in addition to providing employee and client
technical support for those systems. Oftentimes, setting up and
configuring these systems in the first place requires a more
specialized set of technical skills than does the daily operations.
In other words, all IT jobs are not created equally. A loose analogy
would be that all doctors do not know how to perform brain surgery
(youd be a little nervous if your ear-nose-and-throat specialist was
going to perform gall bladder surgery on you, right?). Someone use to
assigning IP addresses and creating/deleting new voice-mail boxes does
not necessarily know how to select the proper Avaya telephony system,
install and configure it for use in the first place. Theyre used to
working with it once its already there.
Also, getting new equipment to communicate with existing equipment
across different platforms is a highly technical specialty that is not
normal for company IT staffers to routinely deal with. This is
especially true of computer programming tasks involving communications
protocols.
The following quote from rfp handbook.com: [
http://www.rfphandbook.com/RFPResources/siart.htm
] sums it up well:
System integrators fulfill a need when a company does not have the
internal expertise and resources to design and develop a system, and
yet the project needs are far greater than a single vendor can
accomplish. Many vendors depend on integrators to provide the
programming and industry expertise to build basic business
applications and workflows, integrate components that may not be
previously ported to the imaging software such as a high-speed
scanner, and handle integration of third-party software programs such
as faxing, storage management, or optical character recognition.
So, basically system integration is sort of a higher level of IT
that is extremely specialized and often dealt with on a consultancy
basis, since once a system is set up and configured, the companys IT
staff are capable of running it day-to-day. Another excerpt from
[http://www.rfphandbook.com/RFPResources/siart.htm ]:
A system integrator is a company that is capable of making diverse
components work together as a system. While an integrator does not
usually add value to the components purchased, the whole system, when
assembled, represents a purpose-built system that accomplishes
specific work
In addition, the integrator often becomes involved in
such issues as business process reengineering, overall service and
maintenance, disaster recovery planning, backfile conversion
strategies, and the myriad details that are part of any major project.
Todays system integrator is no longer only responsible for making
hardware/software components work together. They are often responsible
for a project from conception to a finished turnkey system.--
A turnkey system that will be operated day-to-day by the regular IT
staff. When some new piece of equipment is introduced, or the
programming needs to be changed to reflect new company policy, the IT
Department will call system integrators again. They are often under
contract when expensive pieces of equipment or software are purchased.
It then becomes the IT Departments job to manage the ongoing
relationship with the system integrator (just as other Departments
manage their respective relationships with "outside world" parties),
calling them when needed and scheduling appointments with them so that
the impact of any disruptions on the companys systems are minimized.
Heres a good summation, also from [
http://www.rfphandbook.com/RFPResources/siart.htm ] :
The value that a system integrator adds to a project is:
1. The resources and capability to objectively select the right
hardware and software for the project
2. The ability to integrate these components into a system that solves
specific work requirements
3. The programming resources and experience for system development
4. The capability to also provide business process reengineering,
system installation, system training, system maintenance, and future
product integration
The above site goes on to address your question in a more direct way:
Why are System Integrators Needed?
The current trend is to break down imaging systems into component
parts such that you can buy the server software from one company,
client software from a second, storage management from a third,
workflow from a fourth, and so on. Companies such as Diamond Head
Software and Watermark provide the basic tools and software libraries
that allow imaging systems to be built from the ground up without
reliance on any imaging vendors systems.
Now, an end-user interested in developing an imaging system needs to
understand imaging technology at a system level, business process
reengineering, cost justifications, workflow to build the application,
and component level programming/integration. Most end-user companies (
a customer) do not have the resources to put this all together and
therefore, the role of the system integrator has become more important
instead of less important.
Read the rest of this page: [
http://www.rfphandbook.com/RFPResources/siart.htm ] for more details
and examples, including how to find a system integrator.
Above are generally the main reasons IT departments sometimes need
system integrators. If you are looking for a more specific example,
you can let me know and Ill address it in a Clarification. I hope
this helps.
Google search strategy:
Keywords,
IT department need system integrators:
://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&q=IT+department+need+system+integrators
,
"system integrators":
://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&q=system+integrators
Sincerely,
omniscientbeing-ga
Google Answers Researcher |