Most of today's companies operating in the field of system integration have
entered the sector of production and sales of hardware transferring its
business culture and customs laterally from the sector to sector. Such a
transfer of a business culture, a special business processes, has led to a
series of problems that arose system integrators meet these expanding
portfolio. The main problem wich reflected in the approach to problems and
while the companies that were initially created as system integrators or
originate from software sector focus on processes and material flows and
documentation, system integrators, which are primarily operated in the sector
hardware sales primarily focus on the cost of the project. This approach
inevitably leads to a predefine selection decisions to be taken in view of the
financial rank of prices by solutions rather than on meeting key functionality
that requires the user by the required solution. Another important drawback of
this approach is the notion of an infrastructure problem. The one who came out
of the sale and production of hardware is more likely from someone who comes
from the software industry that over-emphasizes the importance of
infrastructure in certain projects and even extreme functionality subordinate
"backbone system". On the other hand, the emergence of the mass usage
of system virtualization is a growing gap that is created between the software
- which is now liberated and de facto independent of the hardware and the
hardware that should be a basic infrastructure on which the software is
located.
On the issue of the audit of system can clearly see the difference between
these two kinds of system integrators, as long as one is trying to using the
predefined questionnaires and/or strictly defined procedures record the current
state of the user, others are too focused on the future status and all what is
necessary to the same is reached. Although, the recommendation of all academic
institutions and professionals in the field to design the system starts from
the end and the design goes back, the dominant business paradigm prevents
system engineers in companies that were previously sold hardware to think this
way. Also in the sector hardware pronounced by authorities and individual work
on problems and is less likely application brainstorming or similar
collaborative methods. Also, the more
pronounced the need for greater security and a higher degree of flexibility of
the system - that is, the excess of resources is often justified on the way to
the end users of the system assigned to provide convenience in operation
although the time resources do not just throw more and irreversibly consume the
already solved elements of the system while at the same time not maintain
accounts or ignored by those elements of system not covered by the system
solution.
The next major problem of system integration stems from the fact that a
good part of the engineering and management staff working in these companies
never listened systems theory does not fully understand all the theoretical
elements and setting the system's integration. This particularly applies to two
areas of theory system which in addition to its theoretical level almost never
happiness as an example in practice or that significantly affect the design of
the system and its future potential for scalable growth or cascade. The system
examines the theory and concepts of "Nothing" and "Unknown"
and takes them into account as unknown quantities when creating a model of the
real world, that is, in the present case of the real business processes.
Ignoring these two values can be easily replaced subsequent reconfiguration
or by adding another layer of business logic when it comes to the software
until it is almost impossible in the case of hardware so this is an additional
reason why a particular system integrators so much focus on infrastructure.
One of the problems is the fact that the majority of system integrators in
the selection and implementation of new solutions tends to merge some of its
previously already established a solution and/or best practices, and
recommendations of leading world manufacturers of equipment and/or systems integrator.
In this way, attempts to access the "top" make the end-user solutions
to the needs solutions that alter their business processes and procedures and
to adapt to the offered solution. In this, of course, is ignored the specifics
of the end user, a specific system settings, especially in the manufacturing
and marketing force to force the procedures that do not have to necessarily be
the best solution for a specific problem.
Generally speaking, a large number of implemented solutions that ultimately
they do not come, or are rejected by end-users or have not reached their market
validation experience that fate just because it is before the implementation of
the decision has not been done properly recording and analysis of the business
process of admission, respectively, did not perform optimization and
standardization of business before the implementation of the system while the
system is expected to correct and propagated
business logic and culture.
Another thing system integrators often do not pay enough attention to the
analysis of material that should be done before the choice and implementation of system solutions, is insufficient number of layers
taken into account in the analysis of the business model. A sufficient number
of layers and adequate model allow an adequate system model that can be to
shift the hardware and software components respectively defined as a systemic
solution that should the system integrator to deliver to the end user.
