Systems Integration Is the Unification

Systems Integration is the unification of all existing subsystems into one system sharing the same user interface. The five-step methodology involved in systems integration is usually accomplished in two engagements. The first two steps involve defining the current nature of the system and creating a blueprint for the first stages of the new architecture. The definition and architecture steps help to uncover all systemic needs and identify all technical considerations as well as provide detailed project specifications. The next engagement phase involves the building, testing and deploying stages. These involve the actual creation of the integrated system, the testing of the system, and the performance deployment of the system, as the project is then executed according to its final scope and budget.

One common myth of systems integration, according to John Stiernberg of Sound and Contractor Magazine is that pre-determined industry standards are always necessary before systems integration can become a reality. The reality is that the lack of a single technical standard, such as Ethernet, CEBus or BACnet, actually validates the role of the systems integrator. Subsystems can be made to work together in a variety of ways. (Stiernberg, 2005) a second myth is that systems integration and automation are the same thing and that systems integration opens up a system to potential weaknesses from outside, such as hacking, because it is on the same automated interface -- but specifically automation refers only to the pre-set scheduling of system events and automation is thus only a subset of systems integration -- also security controls can be integrated with automated components.