24
Engineering Systems Integration
a system of systems results in a set of systems that are both integrated and
interoperable to achieve a set of metasystem functions in which all the component systems participate (to varying degrees). Bringing people together
with a system can be thought of in terms of system of systems integration.
Typical of system of systems integration is a preponderance of highly complex
exchanges of EMMI between systems sometimes coupled with a loss of individual system capability. For example, what is the effective mix of integration and autonomy? Giving up autonomy is another form of loss. In systems
integration, the relation between objects is expressed as connectivity, coupling, and cohesion. However, for system of systems integration, the notion
of autonomy is more germane at the system level. For the system of systems,
what flexibility is sacrificed at the individual system level when an interface
is integrated? The integration of one system with another system (i.e., a
system(s) of systems) brings about challenging issues, such as joint operations, joint interoperability, and the dimensions of distributed command (‘to
direct’*) and control. The systems engineer considers the political, social,
and technical integration of system(s) of systems. The secondary domain of
systems engineering is that of developing the structures and overseeing the
engineering tasks to build objects, and integrating object by object to achieve
functionalities and performances. Beyond functions and performance, integration requires adaptability and flexibility to reach the required degree of
system stability. The intended result of integration is to facilitate the exchange
of EMMI that is required to achieve the system(s) objectives. For every interaction, there results a loss of EMMI. For every integration into a system, there
results a loss of EMMI. For every integration of a system into a system of
systems, there results a loss of EMMI.
Endnote
1. The type of acquisition, the amount of detail in the system design, and the degree
of specificity for the concept of operations are typical considerations for starting
the systems engineering development work. The U.S. government acquisitions
for the Department of Defense often presents a set of general system requirements
(with some degree of specificity for core aspects) and a concept of operations as
the starting point for systems engineering development work. As a consequence
of the acquisition process, which at some point asks potential bidders to propose
their ideas and means for building and integrating a product or service to a set of
requirements, reasonably explicit and detailed descriptions of a system design
and a concept of operations are included in the proposal submission. The systems
engineering work for the U.S. Department of Defense is required by regulation
* Function are designed by single quote marks; whereas processes are designed by double
quote marks.
Engineering Systems Integration
a system of systems results in a set of systems that are both integrated and
interoperable to achieve a set of metasystem functions in which all the component systems participate (to varying degrees). Bringing people together
with a system can be thought of in terms of system of systems integration.
Typical of system of systems integration is a preponderance of highly complex
exchanges of EMMI between systems sometimes coupled with a loss of individual system capability. For example, what is the effective mix of integration and autonomy? Giving up autonomy is another form of loss. In systems
integration, the relation between objects is expressed as connectivity, coupling, and cohesion. However, for system of systems integration, the notion
of autonomy is more germane at the system level. For the system of systems,
what flexibility is sacrificed at the individual system level when an interface
is integrated? The integration of one system with another system (i.e., a
system(s) of systems) brings about challenging issues, such as joint operations, joint interoperability, and the dimensions of distributed command (‘to
direct’*) and control. The systems engineer considers the political, social,
and technical integration of system(s) of systems. The secondary domain of
systems engineering is that of developing the structures and overseeing the
engineering tasks to build objects, and integrating object by object to achieve
functionalities and performances. Beyond functions and performance, integration requires adaptability and flexibility to reach the required degree of
system stability. The intended result of integration is to facilitate the exchange
of EMMI that is required to achieve the system(s) objectives. For every interaction, there results a loss of EMMI. For every integration into a system, there
results a loss of EMMI. For every integration of a system into a system of
systems, there results a loss of EMMI.
Endnote
1. The type of acquisition, the amount of detail in the system design, and the degree
of specificity for the concept of operations are typical considerations for starting
the systems engineering development work. The U.S. government acquisitions
for the Department of Defense often presents a set of general system requirements
(with some degree of specificity for core aspects) and a concept of operations as
the starting point for systems engineering development work. As a consequence
of the acquisition process, which at some point asks potential bidders to propose
their ideas and means for building and integrating a product or service to a set of
requirements, reasonably explicit and detailed descriptions of a system design
and a concept of operations are included in the proposal submission. The systems
engineering work for the U.S. Department of Defense is required by regulation
* Function are designed by single quote marks; whereas processes are designed by double
quote marks.