A systems integration framework for process analysis and improvement

Abstract

Systems Integration (SI) is an important element of Systems Engineering. It involves the integration of hardware, software, products, services, processes, and humans. The ever‐increasing scale of complexity of systems and its impact on the business requires that we revisit the processes involved in the development and integration of a system. This paper proposes a Systems Integration Process Model (SIPM) based on a comprehensive lifecycle view of systems integration. As part of the ongoing SI research at Stevens Institute of Technology, the authors have developed a Systems Integration Framework (SIF) which incorporates the relevant aspects of integration from a lifecycle perspective and sets a foundation to an end‐to‐end approach to SI. Our end‐to‐end approach focuses on how integration issues can be addressed up‐front to minimize integration related complexities and challenges later on in the system engineering process. This paper discusses the merits and benefits of applying the SIPM to evaluate and improve current SI processes in organizations. The paper provides, in addition to an overview of the SI framework, the activities included in the model. The model was pilot tested to evaluate the SI processes at a government agency. The results were used to provide recommendations for SI process reengineering. © 2009 Wiley Periodicals, Inc. Syst Eng

A framework to address the impact of system of systems integration using commercially off the shelf (COTS) technology

“…The process of SI using CBS has been divided into number of life cycle phases: Concept, Design, Development, Testing, Production, and Deployment/Optimisation and integrates the concepts of the spheres of influence. By extending the SIF we define the SI process as a set of phases that transforms the stakeholder requirements into an operational system by unifying the process components and product components into a whole while ensuring compliance to the specified levels of component operations and interoperability (Jain et al, 2010). The scope and objectives of SI for CBS should be clearly identified to ensure that new systems and components (COTS products) are able to integrate seamlessly with the existing systems and components.…”

“…From a process perspective, the SoSI process creates the links within the systems engineering process from requirements collection to V&V and ultimately to implementation of the system (Morisio et al, 2002) ensuring the ability to define systems optimisation strategies that support technology refresh as components change or become obsolete. The SoSI process begins at project inception and continues throughout the entire systems lifecycle (Jain et al, 2010).…”

Feasibility of a rapid systems engineering framework: an exploratory study

“…Systems integration is an important element of SE, which involves the integration of hardware, software, products, services, business processes and human beings (Grady, 1994;Jain, 2007). The systems integration process is a set of activities that transforms the stakeholder's requirements into an operational system by unifying the process components and product components into a whole while ensuring compliance to the specified levels of component operations and interoperability (Jain et al, 2010). The scope and objectives of systems integration should be clearly identified to ensure that new systems and components are able to work with the existing systems and components.…”

Characterizing Design Process Interfaces as Organization Networks: Insights for Engineering Systems Management

“…Problems at any of these interfaces may result in system failures or may add uncertainty to the design process [Maier, Eckert, and Clarkson, 2009a,;Felekoglu, Maier, and Moultrie, 2013]. Consequently, understanding and active management of interfaces is essential for successful execution and for design process improvements, especially in the context of systems engineering [Sheard and Mostashari, 2009;Jain, Chandrasekaran, and Erol, 2010]. This becomes particularly important in the design of large and complex engineering systems, where interdependent design activities covering different subsystems can be distributed across hundreds or thousands of engineers [Browning, 2009;de Weck, Roos, and Magee, 2011;Madni and Sievers, 2014].…”