Socio-Technical Features of Systems of Systems

From SEBoK
Jump to navigation Jump to search

Human and Organizational Nature of SoS

system of systems (sos) (SoS) contain many types of systems among which are, what are often termed, enterprise Systems (Chen et. al. 2008). There are many different definitions of enterprise: within a SoS environment an enterprise system could be described as a complex , socio-technical system that comprises interdependent resources of people, information, and technology that must interact with each other and their environment in support of a common mission (See also Enterprise Systems Engineering. Emerging ‘soft’ issues critical to the design and operation of Systems of Systems can be identified as follows (see Hubbard et. al. 2010),

  • Decision making in SoS, including issues in autonomy, authority, responsibility and ethics
  • Measures of Enterprise SoS performance
  • Impact of culture and cultural attributes on multinational and multicultural team performance
  • System of Systems ethics, governance, and regulation
  • System of Systems experimentation
  • Shared/distributed situational awareness
  • Alternative approaches to training, e.g., virtual reality, gaming
  • SoS lead and lag ‘soft’ metrics, e.g., improved mental and physical workload measurement techniques
  • Enterprise System agility and resilience, e.g., dynamic allocation and reallocation of function, the human in the loop
  • Enterprise SoS leadership and motivational issues

The holy grail of being able to look into the future by evaluating the effectiveness , impact or added value of alternative enterprise system configurations, prior to deployment, is still a long way off. Such a capability would greatly enhance an enterprise’s ability to dynamically (re-)configure appropriate systems (people, process , and technology) to achieve the performance required to produce designated capability in different contexts and to avoid enterprise structures that are susceptible to undesirable emergent behaviour (See also Emergence) including adverse circumstances such as accidents, disasters. Enterprise System models not only provide the means to visualize, represent, and analyse the inner workings of an Enterprise SoS, but can also constitute the building blocks of an Enterprise SoS Architecture (EA).

An EA is an architecture of an organization that supports strategy, analysis, and planning by stakeholders to determine how the organization can most effectively achieve its current and future objectives. (1) An EA Framework provides a methodology to describe how an EA is organized, structured, and operates in terms of people, processes, product , information technology (IT) and resources in order to achieve its goal.(1A) 1 + 1A = tiger team document (replace with appropriate description)

Existing models and enterprise system architectures and Frameworks (e.g. Zachman, CIMOSA, GERAM, VERAM, ToVE , PERA DoDAF, MODAF) tend to deal with enterprise elements such as Resources, Information Flows and Functions well, but a) within a process framework and b) they do not show a sufficient capability to include soft enterprise characteristics such as policies, culture, competencies, decision making structures, etc. within dynamic models. Hence, changes in one or more of these characteristics are not shown in overall organizational system performance. The following points can be made with reference to EAs:

  • Architecture is foundational for managing modern enterprises and planning enterprise integration.
  • An EA framework is an organized collection of ingredients (tools, methodologies, modeling languages, models, etc.) necessary to architect or re-architect whole or part of an enterprise.
  • For a given enterprise, the enterprise architecture describes the relationships among the mission assigned to the enterprise, the work the enterprise does, the information the enterprise uses, and the physical means, human labor, and IT that the enterprise needs.

The prime advantage of an EA is to provide a common view (in the form of models) of what is going on in the enterprise to relevant actors or stakeholders of the enterprise. The second decisive advantage of an EA is that it provides a sound basis for the management of change that occurs throughout the life cycle of the enterprise. Vernadat (1996) combines the two methodologies of enterprise modeling and enterprise integration and advocates a systematic engineering approach called Enterprise Engineering, for modeling, analysing, designing and implementing integrated enterprise systems.

Enterprise modelling (EM) is concerned with the representation and specification of the various aspects of enterprise operations; namely, functional aspects to describe what are the things to be done and in which order; informational aspects to describe which objects are used or processed; resource aspects to describe what or who performs things and according to which policy; and organizational aspects to describe the organizational structure and the responsibility frame within which things are being done. These Enterprise System models can be combined within an EA framework to provide a dynamic overview of the enterprise system.

Although there are several models available to assess the structure and performance of organizations (e.g. Castka 2001; Curtis et. al. 2001; Tannenbaum et. al. 1996), few if any of these models provide quantitative and qualitative measures of performance and none are truly able to provide a direct multi-point, measurable cause and effect link between the various soft attributes of an enterprise system and its performance. It is clear, though, that success factors from a human perspective do center upon the structure of communication (stakeholder management) and decision making processes and systems within the overall System of Systems

Governance in SoS

The SoS mindset

SoS problems often exhibit many of the characteristics of so-called wicked problem (Rittel and Webber 1973):

  • Problems are extremely complex and not bounded or stable
  • They do not have unique, right solutions, but rather solutions that are either better or worse than others, and they do not have a definitive formulation
  • SoS requirements are often volatile with changing constraints and moving targets
  • Stakeholders have different views, and
  • Understanding the whole context is difficult and critical.

SoS problems relate to both hard (mechanical, electronic, and software ) and soft (people, organizations, and regulatory) systems considerations. Research must nowadays include mixed methods and approaches (Conklin 2005) that include both quantitative and qualitative techniques, making this a very challenging area intellectually.


Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.


Castka P B. 2001. "Factors Affecting the Successful Implementation of High Performance Teams." Team Performance Management 7 (7/8), 123-134.

Curtis B, Hefley W. E, and Miller S. A. 2009. "People Capability Maturity Model (P-CMM)" Version 2.0, 2nd Ed. Software Engineering Institute. Carnegie Mellon University.

Conklin Jeff. 2005. "Dialogue Mapping: Building Shared Understanding of Wicked Problems." Chichester, West Sussex, England, UK: John Wiley & Sons, Ltd. 1st ed. ISBN 978-0-47001-768-5

Hubbard, E-M., C. E. Siemieniuch, and M. A. Sinclair. Hodgson A. 2010. "Working towards a Holisticorganisational Systems Model." Presented at 5th Int. Conf. Systems of Systems Engineering (SoSE), Loughborough, UK. 22-24 June.

Rittel, H. W. J. and M. M. Webber 1973. Dilemmas in a General Theory of Planning. pp. Policy Sciences, Vol. 4, Elsevier Scientific Publishing Company, Inc., Amsterdam,155–169. (Reprinted in Cross N. (ed.). 1984. Developments in Design Methodology, J. Wiley & Sons, Chichester, pp. 135–144)

Tannenbaum S I, Salas E, and Cannon-Bowers J A. 1996. Promoting Team Effectiveness. In M. A. West, Handbook of Work Group Psychology. Chichester: Wiley.

Vernadat F B. 1996. Enterprise Modeling and Integration Principles and Applications. Chapman and Hall Publishers.

Primary References

Checkland P B. 1981. Systems Thinking, Systems Practice. Wiley.

Hubbard E-M, Siemieniuch C E, Sinclair M A, Hodgson A. 2010. Working towards a Holistic Organisational Systems Model. 5th Int. Conf. Systems of Systems Engineering (SoSE), Loughborough, UK. 22-24 June.

Rittel Horst W J, and Webber Melvin M. 1973. Dilemmas in a General Theory of Planning. pp. Policy Sciences, Vol. 4, Elsevier Scientific Publishing Company, Inc., Amsterdam,155–169. (Reprinted in Cross N. (ed.). 1984. Developments in Design Methodology, J. Wiley & Sons, Chichester, pp. 135–144)

Additional References

Bruesburg A. and Fletcher G. 2008. The Human View Handbook – Systems Engineering & Assessment Ltd.

IFIP-IFAC Task Force. 1999. The Generalised Enterprise Reference Architecture and Methodology, V1.6.3.

ISO 14258:1998. Industrial automation systems -- Concepts and rules for enterprise models. Geneva, Switzerland: International Organization for Standardization;

ISO 19439:2006. Enterprise integration -- Framework for enterprise modelling. Geneva, Switzerland: International Organization for Standardization.

ISO 19440:2007. Enterprise integration -- Constructs for enterprise modelling. Geneva, Switzerland: International Organization for Standardization.

Miller Frederic - P., Vandome Agnes F, and McBrewster John.2009.Enterprise Modelling. VDM Publishing House Ltd. ISBN 6130253370,9786130253370

Article Discussion

(Davidz, 08/22)

  • There should be links from this section to Part 5. The text is not integrated with the material in Part 5.
  • The "Socio-Technical Features of Systems of Systems" goes beyond Enterprise Systems. As an example, different individual competencies (like collaboration and communication) may be even more important for actors in an SoS environment than in a typical SE environment.
  • The text wanders through topics rather than providing a structured and comprehensive discussion.

[Go to discussion page]

<- Previous Article | Parent Article | Next Article ->


--Blawson 20:47, 15 August 2011 (UTC)