Difference between revisions of "Socio-Technical Features of Systems of Systems"

From SEBoK
Jump to: navigation, search
(References)
(Human and Organizational Considerations in SoS)
Line 2: Line 2:
 
Most [[System of Systems (SoS) (glossary)|systems of systems]] (SoS) are socio-technical systems that are composed of a number of interdependent resources, such as, people, processes, information, and technology that must interact with each other and their [[Environment (glossary)|environment]] in support of a common [[mission (glossary)]] (See also [[Enterprise Systems Engineering]]).
 
Most [[System of Systems (SoS) (glossary)|systems of systems]] (SoS) are socio-technical systems that are composed of a number of interdependent resources, such as, people, processes, information, and technology that must interact with each other and their [[Environment (glossary)|environment]] in support of a common [[mission (glossary)]] (See also [[Enterprise Systems Engineering]]).
  
==Human and Organizational Considerations in SoS==
+
==Socio-Technical Aspects of Systems of Systems Engineering==
Within a SoS, these socio-technical systems are often referred to as [[enterprise (glossary)]] systems (Chen et al. 2008). Examples of emerging ‘soft’ issues that are critical to the [[Design (glossary)|design]] and operation of systems of systems can be identified as follows (Hubbard et al. 2010):
+
Engineering a systems of systems often entails more than simply integrating physical systems but also incorporates integration of the people and processes associated with the constituent systems.  In most SoS cases, each constituent system has its own users and stakeholders with their own operating processes, objectives, motivations and constraints as well as its own technical development processes, funding mechanisms, and lifecycle approaches.  This affects systems engineering for SoS in several ways.
* decision making in SoS, which includes addressing issues involving autonomy, authority, responsibility and [[Ethics (glossary)|ethics]],
+
 
* measures of enterprise SoS performance,
+
First, this means that the SoS systems engineer needs to consider the operating processes of the constituent systems and how these will affect the systems of systems.  This includes considering changes in the operations of systems to meet the needs of the SoS and how these will affect the constituent systems which often continue to support their original users concurrently with the SoS.  In effect in many SoS, SoSE includes engineering operational and social processes as well as the technical systems. Examples of emerging ‘soft’ issues that are critical to the design and operation of systems of systems can be identified as follows (Hubbard et al. 2010) include decision making in SoS, which includes addressing issues involving autonomy, authority, responsibility and ethics, impact of culture and cultural attributes on multinational and multicultural team performance, system of systems ethics, governance, and regulation, and shared/distributed situational awareness.
* impact of [[Culture (glossary)|culture]] and cultural attributes on multinational and multicultural [[Team (glossary)|team]] performance,
+
Many of the issues associated with ‘soft’ or organizational aspects of an SoS often exhibit many of the characteristics of so-called wicked problem (Rittel and Webber 1973), including:
* system of systems ethics, [[Governance (glossary)|governance]], and regulation,
+
 
* system of systems experimentation,
+
* problems are extremely complex and not bounded or stable, * impact of [[Culture (glossary)|culture]] and cultural attributes on multinational and multicultural [[Team (glossary)|team]] performance,
* shared/distributed situational awareness,
+
* they do not have uniquely correct solutions, but rather solutions that are either better or worse than others, and they also do not have a definitive formulation,
* alternative approaches to training, e.g., virtual reality and gaming,
+
* SoS requirements are often volatile with changing constraints and moving targets,
* SoS lead and lag ‘soft’ [[Metric (glossary)|metrics]], e.g., improved mental and physical workload [[Measurement (glossary)|measurement]] techniques,
+
* stakeholders have different views, and  
* enterprise system [[Agility (glossary)|agility]] and [[Resilience (glossary)|resilience]], e.g., dynamic allocation and reallocation of function and the human in the loop, and
+
* understanding the whole context is challenging but critical.  
* enterprise SoS leadership and motivational issues.
 
  
 
The will still be some time before we have the ability to look into the future by modeling or simulating socio-technical systems or ‘soft’ elements of a system of systems in order to evaluate the [[effectiveness (glossary)|effectiveness]], impact or added value of alternative system configurations, prior to deployment. Such a capability would greatly enhance our ability to dynamically (re)configure appropriate socio-technical systems (people, [[process (glossary)|process]], and technology), to achieve the performance required to produce designated [[capability (glossary)]] in different contexts, and to avoid SoS structures that are susceptible to undesirable emergent behavior (also see emergence).  
 
The will still be some time before we have the ability to look into the future by modeling or simulating socio-technical systems or ‘soft’ elements of a system of systems in order to evaluate the [[effectiveness (glossary)|effectiveness]], impact or added value of alternative system configurations, prior to deployment. Such a capability would greatly enhance our ability to dynamically (re)configure appropriate socio-technical systems (people, [[process (glossary)|process]], and technology), to achieve the performance required to produce designated [[capability (glossary)]] in different contexts, and to avoid SoS structures that are susceptible to undesirable emergent behavior (also see emergence).  
Line 26: Line 25:
 
* An EA framework is an organized collection of ingredients (tools, methodologies, modeling languages, models, etc.) that are necessary to architect or re-architect a part of or an entire enterprise, and
 
* An EA framework is an organized collection of ingredients (tools, methodologies, modeling languages, models, etc.) that are necessary to architect or re-architect a part of or an entire enterprise, and
 
* For a given enterprise, the enterprise architecture describes the work the enterprise does, the information the enterprise uses, and the physical means, human labor, and IT that the enterprise requires.
 
* For a given enterprise, the enterprise architecture describes the work the enterprise does, the information the enterprise uses, and the physical means, human labor, and IT that the enterprise requires.
 
The prime advantage of an EA is to provide a common view (in the form of models) of what is taking place 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 (glossary)]] of the enterprise. Vernadat (1996) combines the two methodologies of enterprise modeling and enterprise integration and advocates a systematic engineering approach, referred to as enterprise engineering, for modeling, analyzing, designing and implementing integrated enterprise systems.
 
 
Enterprise modeling (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 who performs what and according to which policy, and organizational aspects to describe the organizational structure and the timeframe within which things are being done. These enterprise system models constitute the building blocks of an enterprise SoS architecture and 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.
+
These issues relate to both hard (mechanical, electronic, and software) and soft (people, organizations, and regulatory) systems considerations. Research must include mixed methods and approaches (Conklin 2005) that include both quantitative and qualitative techniques, which makes this a very challenging area intellectually.
 +
 
 +
Second, this means that the SoS systems engineering needs to consider the development processes of the systems including their current state of development (e.g. in development, fielded, evolving) and how this affects their ability to change to meet SoS needs.  This can place constraints on the architecture for the SoS as is discussed in the next section. It also can introduce complexity into SoS development since it is often the case that different constituent systems may be on different development schedules making it difficult to synchronize changes across the systems in an SoS. This can lead to challenges in SoS verification, validation and testing (REF) as well as in maintaining operational capability in the face of asynchronous changes in systems where there are interdependencies among the systems. This can be further complicated when the lifecycle approaches of the constituent systems differ (Boehm and Turner, 2004).
 +
 
 +
Finally, as noted above, many SoS are in effect socio-technical systems. Socio-technical systems are composed of a number of interdependent resources, such as, people, processes, information, and technology that must interact with each other and their environment in support of a common mission.  Increasingly, (INCOSE Vision 2025) systems engineering views this class of system as offering an opportunity for a broadened contribution of systems engineering approaches. Since a socio-technical systems are comprised of multiple, independent systems which together provide a new capability, they can be viewed from an SoS perspective.  These socio-technical systems are often referred to as enterprise systems (Rhodes et al. 2009). The relationship between SoS and Enterprise SE approaches to sociotechnical systems is an active topic of discussion.
  
 
==Dealing with Socio-Technical Issues in an SoS==
 
==Dealing with Socio-Technical Issues in an SoS==

Revision as of 18:37, 17 March 2015

Most systems of systems (SoS) are socio-technical systems that are composed of a number of interdependent resources, such as, people, processes, information, and technology that must interact with each other and their environment in support of a common mission (See also Enterprise Systems Engineering).

Socio-Technical Aspects of Systems of Systems Engineering

Engineering a systems of systems often entails more than simply integrating physical systems but also incorporates integration of the people and processes associated with the constituent systems. In most SoS cases, each constituent system has its own users and stakeholders with their own operating processes, objectives, motivations and constraints as well as its own technical development processes, funding mechanisms, and lifecycle approaches. This affects systems engineering for SoS in several ways.

First, this means that the SoS systems engineer needs to consider the operating processes of the constituent systems and how these will affect the systems of systems. This includes considering changes in the operations of systems to meet the needs of the SoS and how these will affect the constituent systems which often continue to support their original users concurrently with the SoS. In effect in many SoS, SoSE includes engineering operational and social processes as well as the technical systems. Examples of emerging ‘soft’ issues that are critical to the design and operation of systems of systems can be identified as follows (Hubbard et al. 2010) include decision making in SoS, which includes addressing issues involving autonomy, authority, responsibility and ethics, impact of culture and cultural attributes on multinational and multicultural team performance, system of systems ethics, governance, and regulation, and shared/distributed situational awareness. Many of the issues associated with ‘soft’ or organizational aspects of an SoS often exhibit many of the characteristics of so-called wicked problem (Rittel and Webber 1973), including:

  • problems are extremely complex and not bounded or stable, * impact of culture and cultural attributes on multinational and multicultural team performance,
  • they do not have uniquely correct solutions, but rather solutions that are either better or worse than others, and they also 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 challenging but critical.

The will still be some time before we have the ability to look into the future by modeling or simulating socio-technical systems or ‘soft’ elements of a system of systems in order to evaluate the effectiveness, impact or added value of alternative system configurations, prior to deployment. Such a capability would greatly enhance our ability to dynamically (re)configure appropriate socio-technical systems (people, process, and technology), to achieve the performance required to produce designated capability in different contexts, and to avoid SoS structures that are susceptible to undesirable emergent behavior (also see emergence).

There are three particular areas that are key to the development of these socio-technical / enterprise systems:

  • An enterprise architecture (EA) is the architecture of an organization that supports the strategy, analysis, and planning by stakeholders and is used to determine how the organization can most effectively achieve its current and future objectives,
  • An enterprise architecture framework (EAF) provides an enabling methodology to is used to describe how an EA must be organized, structured, and operated in terms of people, processes, product, information technology (IT) and resources in order to achieve its goal (Vernadat 1996; Bernus, Nemes et al. 2003; Chen, Doumeingts et al. 2008), and
  • enterprise system models not only provide the means to visualize, represent, and analyze the inner workings of an enterprise SoS, but may also constitute the building blocks of an enterprise SoS architecture (EA).

Existing models and enterprise system architectures and frameworks (e.g. Zachman, Computer Integrated Manufacturing Open System Architecture (CIMOSA), Generalized Enterprise Reference Architecture and Methodology (GERAM), Virtual Enterprise Reference Architecture and Methodology (VERAM), TOronto Virtual Enterprise (TOVE), Purdue Enterprise Reference Architecture (PERA), Department of Defense Architecture Framework (DoDAF), and Ministry of Defence Architecture Framework (MODAF)) tend to deal with enterprise elements such as resources, information flows, and functions, quite well; however, 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.) that are necessary to architect or re-architect a part of or an entire enterprise, and
  • For a given enterprise, the enterprise architecture describes the work the enterprise does, the information the enterprise uses, and the physical means, human labor, and IT that the enterprise requires.

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

Second, this means that the SoS systems engineering needs to consider the development processes of the systems including their current state of development (e.g. in development, fielded, evolving) and how this affects their ability to change to meet SoS needs. This can place constraints on the architecture for the SoS as is discussed in the next section. It also can introduce complexity into SoS development since it is often the case that different constituent systems may be on different development schedules making it difficult to synchronize changes across the systems in an SoS. This can lead to challenges in SoS verification, validation and testing (REF) as well as in maintaining operational capability in the face of asynchronous changes in systems where there are interdependencies among the systems. This can be further complicated when the lifecycle approaches of the constituent systems differ (Boehm and Turner, 2004).

Finally, as noted above, many SoS are in effect socio-technical systems. Socio-technical systems are composed of a number of interdependent resources, such as, people, processes, information, and technology that must interact with each other and their environment in support of a common mission. Increasingly, (INCOSE Vision 2025) systems engineering views this class of system as offering an opportunity for a broadened contribution of systems engineering approaches. Since a socio-technical systems are comprised of multiple, independent systems which together provide a new capability, they can be viewed from an SoS perspective. These socio-technical systems are often referred to as enterprise systems (Rhodes et al. 2009). The relationship between SoS and Enterprise SE approaches to sociotechnical systems is an active topic of discussion.

Dealing with Socio-Technical Issues in an SoS

Many of the issues associated with ‘soft’ or organizational aspects of an SoS often exhibit many of the characteristics of so-called wicked problem (Rittel and Webber 1973), including:

  • problems are extremely complex and not bounded or stable,
  • they do not have uniquely correct solutions, but rather solutions that are either better or worse than others, and they also 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 challenging but critical.

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

References

Works Cited

Bernus, P., L. Nemes, and G. Schmidt. 2003. Handbook on Enterprise Architecture. Heidelberg, Germany: Springer-Verlag.

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

Chena, D., G. Doumeingtsb, F. Vernadatc. 2008. "Architectures for enterprise integration and interoperability: Past, present and future." Computers in Industry. 59 (7): 647-659.

Curtis, B., W.E. Hefley, and S.A. Miller. 2009. People Capability Maturity Model (P-CMM), version 2.0, 2nd ed. Pittsburgh, PA, USA: Software Engineering Institute, Carnegie Mellon University. Available: http://repository.cmu.edu/cgi/viewcontent.cgi?article=1048&context=sei.

Conklin, J. 2005. Dialogue Mapping: Building Shared Understanding of Wicked Problems, 1st ed. Chichester, West Sussex, England, UK: John Wiley & Sons, Ltd.

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

Rittel, H.W.J., and M.M. Webber. 1973. "Dilemmas in a General Theory of Planning." Amsterdam, The Netherlands: Elsevier Scientific Publishing Company, Inc. p. 155–169, in Developments in Design Methodology, edited by N. Cross, 1984. Chichester, West Sussex, England, UK: John Wiley & Sons, Ltd. p. 135–144.

Tannenbaum, S.I., E. Salas, and J.A. Cannon-Bowers. 1996. "Promoting Team Effectiveness," in Handbook of Work Group Psychology, edited by M.A. West. Chichester, West Sussex, England, UK: John Wiley & Sons, Ltd.

Vernadat, F.B. 1996. Enterprise Modeling and Integration: Principles and Applications. London, England, UK: Chapman and Hall Publishers.

Primary References

Checkland, P.B. 1981. Systems Thinking, Systems Practice. Chichester, West Sussex, England, UK: John Wiley & Sons, Ltd.

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

Rittel, H.W.J., and Webber, M.M. 1973. "Dilemmas in a General Theory of Planning," in Policy Sciences 4. Amsterdam, The Netherlands: Elsevier Scientific Publishing Company, Inc. p. 155–169. In Cross, N. 1984. Ed. Developments in Design Methodology. Chichester, West Sussex, England, UK: John Wiley & Sons, Ltd. p. 135–144.

Additional References

Bruesburg, A., and G. Fletcher. 2009. The Human View Handbook for MODAF, draft version 2, second issue. Bristol, England, UK: Systems Engineering & Assessment Ltd. Available: http://www.hfidtc.com/research/process/reports/phase-2/hv-handbook-issue2-draft.pdf.

IFIP-IFAC Task Force. 1999. "The Generalised Enterprise Reference Architecture and Methodology," V1.6.3. Available: http://www.cit.gu.edu.au/~bernus/taskforce/geram/versions/geram1-6-3/v1.6.3.html.

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

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

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

Miller, F.P., A.F. Vandome, and J. McBrewster. 2009. Enterprise Modelling. Mauritius: Alphascript Publishing, VDM Verlag Dr. Müller GmbH & Co. KG.


< Previous Article | Parent Article | Next Article >


SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus