System Integration ITec4162

Chapter 1: Introduction Systems Integration

Systems integration (SI) is a process whereby a cohesive system is created from components that
were not specifically designed to work together. Components of an integrated system are often
systems in their own right.

System Integration is melding existing systems and new technologies to from more capable
systems that are intended to take on additional tasks, exhibit improved performance, and/or
enhance existing systems.

SI is a logical, objective procedure for applying new and/or expanded performance requirements
in an efficient, timely manner to the design, procurement, installation, and operational
configuration consisting of distinct modules (sub systems), each of which may embody inherent
constraints or limitations.

A building management project frequently requires the integration of separate specialized

systems, controllers, and infrastructure technology into a building management system. The
requirement for integration can arise for a number of reasons. Some of those are:
Another vendor’s specialized controller must be added to a system. For example, add a boiler
controller to the building automation system.

Two buildings of a campus may have systems from different vendors. The owner requires
the two systems to be managed from a “single seat.” In other words, a single operator sitting in
front of a single workstation must be able to operate all the systems.
Several stand-alone building systems must be integrated into a single facility management
system in order to enable automatic responses to events. For example,
swiping a badge on the security system card reader must turn on lights and HVAC for an
office floor.

The facility owner’s expectation is for the integration to be cost-effective and the result to be a
single cohesive system.

SI is the combination of processes, software, standards, and hardware resulting in the

seamless integration of two or more enterprise systems allowing them to operate as
one.

“There was no thought whatsoever given to the integration of corporate data. The entire objective
was to replicate manual procedures on the computer.”

These were known as “stovepipe” systems, giving us something like figure

4th Year Information Technology 1

System Integration ITec4162

This “islands of automation” model was not being used or lived gradually for three
reasons:

1. It became increasingly necessary to allow the systems to interact. This meant the existing
systems had to be integrated to provide interoperability – the scale meant that you
couldn’t simply start again!
2. The realization that customer information within the stovepipe system had massive value,
particularly when viewed as a whole. For example, a software vendor may have separate
systems for home, business and government client, and no way to obtaining a global view
of the information.
3. The desire to integrate key systems with vendors and customers.
As integration became more and more important, systems would tend to look
more like figure 2

4th Year Information Technology 2

System Integration ITec4162

Key Concepts
1. API: An Application Programming Interface (API) is a defined and documented software
interface that a software program may use to interact with a system or a specific sub-
system or feature of a system.
2. Integration: Integration is the process of inter-connecting one system with another
system in order to provide a useful exchange of information, data and/or control between
the systems.
3. Interface: An interface is a point where interaction occurs between two systems, devices,
programs, etc. To be useful for integration, an interface must have stable and well-
defined characteristics. A standard interface is one that is defined and documented by a
recognized professional or industry organization. The RS-232 interface is an example of
a standard hardware interface – it is currently managed by the Telecommunications
Industry Association (TIA).
The term “interface” is also used to refer to a hardware or software component that
translates or converts from one interface to another interface.
4. Media: Media is the medium through which data is conveyed. Media has specific
physical properties such as voltage levels, bandwidth and frequency response. A
telephone line is a type of media characterized only by its physical properties.
More complex media may provide a choice of cabling or interconnections with different
sets of physical properties. For example, standard available Ethernet media includes
several specifications for twisted pair wire and fiber optic cables. The common element
among these various types of physical media is the Media Access Control (MAC)
protocol. A MAC protocol manages access to the media for outgoing messages and
manages address recognition of received messages. A MAC protocol is an integral
component of the implementation of sophisticated media such as Ethernet.
When integrating separate devices, determining and achieving a common media is one of
the steps to a successful integration. For popular media such as Ethernet, products are
available that convert from one type of physical media to another.
5. Middleware: Middleware is software used to “glue” together disparate systems without
those systems needing to know anything about each other. Knowledge of both systems is
contained in the middleware.
6. Protocol: A protocol is a set of rules governing the exchange or transmission of data
electronically between devices. A protocol is like a language; both devices must
understand the same language in order to exchange data. A complex system has multiple
levels of interactions. The different levels will likely use different protocols, each
optimized for the nature of the interactions required at that level.
For example, the network level might interact using Ethernet. The operating systems
might interact using TCP/IP. The application programs might interact using OPC.
7. System: A system is a group of hardware and software components that work together in
a cohesive manner to perform a task. A system may be as simple as a single controller or

4th Year Information Technology 3

System Integration ITec4162

as complex as the telephone network. A personal computer with a video card, memory, a
disk drive and an operating system is also a system.
8. System Integration: System integration is a process whereby a cohesive system is created
from components that were not specifically designed to work together. Components of an
integrated system are often systems in their own right.

Integration Rules

A successful integration is one that meets the system owner’s needs in the most cost effective
way. Generally, the most cost effective integration is achieved by making use of existing
capabilities of the systems involved. Performing system integration can be a complex and costly
process. Before proceeding with system integration, be certain it is necessary. The most cost
effective integration is no integration.

Begin a system integration project by evaluating the requirements for integration. Integration
requirements are often open-ended or ambiguous. Project specification documents often state
that integration is required between two systems, but provide no other details. Assess the
project’s requirements:

 Do not make up detailed requirements based on your assumptions – require specification

details be provided
 Understand the intent of the people responsible for the specifications
 Understand the needs of the operational people – these may not agree with the
specification
 Make sure the interested parties resolve their differences
 Before proceeding, be sure integration is the most effective way to meet the needs of the
clients

If integration is required, understand the scope of integration that is needed. A cost effective
integration will use the simplest and most direct approach that meets the objectives of the
integration. For example:

 If the requirement is to have “single-seat” display of alarm messages, a suitable solution

may be as simple as using a commercial terminal emulation program on the primary
workstation, connected to the secondary system, as the display window for alarms from
the secondary system
 If the requirement is to be able to manage two or more systems from a “single-seat,”
simply running the workstation software of two different systems concurrently on the
same computer may be a suitable solution
 If the requirement is to integrate the display of data from different systems, integration
through the workstation may be more practical than a controller level solution

4th Year Information Technology 4

System Integration ITec4162

 If full data exchange between the systems is required and only a custom solution can
achieve it, a workstation based solution may be more cost effective than a controller level
solution

Seek a solution that makes use of the built-in capabilities of the systems involved and/or uses off
the-shelf alternatives that can meet the requirements.

For example:

 When providing controllers to perform specialized functions, select controllers that work
with protocols already supported
 When requirements specify controllers that are not compatible with supported protocols,
look for and propose alternatives that work with a supported protocol
 When non-compatible systems must be integrated, look for commercially available
gateway products that can connect the systems together
 When requirements specify integrating data at the workstation, look first for
commercially available workstation software products such as communications drivers,
OPC servers and middleware that may facilitate the integration

A solution that requires custom hardware or software should be a last resort. A custom solution
brings the following issues:

 The implementation cost is high; it may not be cost effective within the budget of the
project
 The cost of system maintenance is increased; changes or updates made to the integrated
systems may require updates to the custom solution
 Limited warranties and support
 Unproven solutions have an increased risk of failure
 Maintenance may be difficult to arrange.

Generally: Systems integration is a complex topic with many factors to consider. Execution of a successful
integration will require knowledge and understanding of the requirements weighed against a careful
balance of compromises.

Systems Integration Life-cycle Phases

An organized approach to SI is to view the program from the perspective of a systems
development life cycle. The seven phase life cycle that is most commonly used in SI programs is
as follows:

1. Requirements Definition and Specifications

The goal for requirements definition and specification is to completely define and correctly
interpret the client's real needs. It sometimes surprises the systems integrator when the client
appears not to understand completely the system requirements being proposed.

4th Year Information Technology 5

System Integration ITec4162

2. Feasibility analysis

It is necessary to establish complete and consistent system performance criteria to determine

feasibility as well as assess the risk potential. The criteria must be developed on a functional
basis and not by reference to existing commercial configurations. Assessment of risk potential
based on performance and technical characteristics constitutes one of the major activities during
feasibility analysis.

3. System Architecture Development

Specify required technical capabilities Just as in the instance with feasibility analysis concerning
performance, it is necessary to specify the system architecture and to establish the required
technical capabilities for the system to be deployed. This is an especially critical activity for SI in
that the architecture selected will most certainly determine the ease or difficulty with which the
ensuing system may be put together and made operational. Good systems architecture can also
provide significant cost savings, especially during maintenance activities, as well as greatly
increased system flexibility.

4. Management Plan: Program and Project Plan

The development and utilization of a management plan is the key to success for the SI program.
Architectural and configuration alternatives must be examined and explicit program and project
plans developed. One of the most important activities for the success of development of large,
complex engineered systems is the identification and assessment of risk factors and the
development of a successful risk management strategy. This development includes assessment of
technical and nonfunctional risk factors and the development of a risk management plan.

5. Systems Design: Logical and Physical Design

A major activity is to define and explore all options that could meet the performance criteria
established earlier.

6. Implementation: Design Implementation, System Tests, and Operational

Deployment

Select and deploy the preferred option(s). Included in this step are such widely diverse matters as
ensuring that non-operating questions such as operator training, systems shakedown, and client
acceptance bench marking are addressed, and in addition, ensuring lifetime system
maintainability.

7. Evaluation: System Review and Plans for Replacement/retirement

Conduct various system performance tests and evaluate the outcomes in light of the client
requirements. Once the system has been deployed and is operational, it is necessary to conduct

4th Year Information Technology 6

System Integration ITec4162

total SI tests and evaluate the outcomes to ascertain that the functional and performance
requirements have been met. The phases in the system life cycle are interactive and iterative
throughout the program development activity. Depending on the state of development and
understanding of a specific project, it is possible to initiate the life cycle at anyone of the specific
phases.
However, it is recommended that the life cycle be used from the beginning of the program and
followed through until completion.

Benefits and Limitations of System Integration

Benefits Limitations

Increased Revenue and Growth High Initial Set-up Costs

Leveling the Competitive Environment Power and Interdepartmental Conflicts (due to

the sharing of information)

Enhanced Information Visibility Long-term and Intangible ROI (Usually

several years)

Increased Standardization Creativity Limitations (Restricts Creativity and

Independence)

Enterprise Recourse Planning (ERP) and Systems Integration

 ERP systems thus make the process of systems integration easier, but they are expensive
and often require organizations to start from scratch.

 Enterprise Resource Planning (ERP) systems are integrated, multi-module application

software packages designed to serve and support several business functions across an
organization.

4th Year Information Technology 7

System Integration ITec4162

 ERP systems are typically commercial software packages that facilitate collection and
integration of information related to various areas of an organization.

 ERP systems enable the organization to standardize and improve its business processes to
implement best practices for its industry.

 Before installing the ERP system, an organization may have to upgrade or install
middleware or get rid of their legacy system’s hardware and software.

 Integration is also required at the Data level, Client level, and at the Application level.

 A good ERP implementation improves operational efficiency with better business

processes that focuses on organizational goals rather than on individual departmental
goals.

 Improved efficiency with a paperless flow and electronic data interchange (EDI) or
business-to-business (B2B) commerce environment with partners.

ERP Project and Time

 Real transformational ERP efforts will usually run between 1 to 3 years, on average.
 Short implementations (3 to 6 months):
→ small companies,
→ implementation limited to a small area of the company, or
→ The company only used the financial pieces of the ERP system.
 The important thing is not to focus on how long it will take but to understand why you
need ERP and how you will use it to improve your business.
Hidden cost of ERP
 Training  Replacing best and brightest staff
 Integration and testing after implementation
 Data conversion  Implementation teams can never stop
 Data analysis  Waiting for ROI (return on
 Consultants investment)
 Post-ERP depression
Potential Benefits of ERP
 Internal Benefits

• Integration of a single source • Reduced operating costs

of data • Improved internal
• Common data definition communication
• A real-time system • Foundation for future
• Increased productivity improvement

4th Year Information Technology 8

System Integration ITec4162

 External Benefits
• Improved customer service and order fulfillment
• Improved communication with suppliers and customers
• Enhanced competitive position
• Increased sales and profits
ERP implementation Approaches
→ The big bang – install a single ERP system across the entire organization
→ Franchising – Independent ERP systems are installed in different units linked by common
processes, e.g., bookkeeping.
→ Slam dunk – install one or several ERP modules for phased implementation of key
business processes.
Major Challenges to ERP implementation
→ Limitations of ERP technical capabilities
→ Inconsistency with existing business processes
→ Costs - implementation (hardware, software, training, consulting) and maintenance
→ Impact on organizational structure (front office vs. back office, product lines, etc.)
→ Changes in employee responsibilities
→ Flexibility of software system upgrades
→ Implementation timelines
→ Availability of internal technical knowledge and resources
→ Education and training
→ Implementation strategy and execution
→ Resistance to change

4th Year Information Technology 9