Deploying, Using, and Sustaining Systems to Solve Problems
This topic is part of the Systems Approach Applied to Engineered Systems knowledge area (KA). It describes knowledge related to the deployment, sustainment, and use of a solution, that may have been developed through the activities described in the Implementing and Proving a Solution topic. Discussion of how a deployed systems fit into commercial and acquisition relationships in Stakeholder Responsibility topic. Any of the activities described below may also need to be considered concurrently with other activities in the systems approach at a particular point in the life of a system-of-interest (SoI).
The activities described below should be considered in the context of the Overview of the Systems Approach topic at the start of this KA. The final topic in this KA, Applying the Systems Approach, considers the dynamic aspects of how these activities are used as part of the systems approach and how this relates in detail to elements of systems engineering (SE).
Part 3, Systems Engineering and Management, of the Guide to the SE Body of Knowledge (SEBoK) provides two additional KAs that address the engineering aspects of these steps of the systems approach. In KA Product and Service Life Management and System Deployment and Use, in Part 3 explain the SE aspects of deployment, operation, maintenance, logistics, service life extension, updates, upgrades, disposal and the retirement of systems.
A systems approach considers the total system and the total life cycle of the system. This includes all aspects of the system and the system throughout its life until the day users depose of the system and the external enterprises complete the handling of the disposed system products. Creation of the system is rarely the step that solves the stakeholders’ problems. It is the use of the system solution that solves the problem. So from this perspective the deployment, use and sustainment of the system are important concepts that must be a part of the systems approach.
Engineered systems are eventually owned by an individual, team, or enterprise. Those who own the system during development may not be the ones who own the system when it is in operation. Moreover, the owners may not be the users; e.g., service systems may be used by the general public but owned by a specific business that is offering the service. The transition of a system from development to operations is often itself a complex task, involving such activities as training those who will operate the system, taking legal actions to complete the transfer, and establishing logistical arrangements so that the operators can keep the system running once the transition is completed.
A complete systems approach must also consider the many enterprises involved in the system from initial conception through the completion of the disposal process. These enterprises are all stakeholders with requirements , which all have interfaces that must be considered as part of a total systems approach.
There is very little in the literature pertaining to the application of the systems approach to these phases of the life cycle. However, a basic premise of this KA is that the systems approach pertains to all phases of a system’s life cycle. Hence, to properly build systems to solve problems or for other uses, it can be inferred that the systems approach pertains to the deployment, use, and the sustainment of the systems. Many of the available references in this topic area are from SE literature rather than from literature associated with the systems approach so the reader should also see Part 3, Systems Engineering and Management, of the SEBoK.
Deployment: The Transition from Development to Operation
Transferring custody of the SoI and responsibility for its support from one organization to another occurs during deployment and is often called transition (INCOSE 2011). Transition of a product system includes the integration of the system into the acquiring organization's infrastructure. Deployment and transition involves the activity of moving the system from the development to the operational locations, along with the support systems necessary to accomplish the relocation.
Transition includes the initial installation of a system and the determination that it is compatible with the wider system and does not cause any significant wider system issues. This process of acceptance and release for use varies between domains and across businesses and enterprises and can be thought of as an initial assessment of the system’s effectiveness (Hitchins 2007). Generally, transition may be considered as having two parts: 1.) ensuring that the new system interoperates with the systems around it and 2.) ensuring the resulting system is safe and possesses other critical operational properties.
It is particularly important to considered emergent properties when a new system is added to the existing organization's system of systems (SoS) network, as well as the complexity of the organization into which the new system is transitioned (see also Complexity). The more complex the receiving organization is the more challenging the transition will be, and the greater the likelihood of unintended interactions and consequences from the new system's insertion. Dealing with the consequences of this complexity starts in transition and continues into operation, maintenance, and disposal.
Transition of a service system is often performed in two stages. First, the service system infrastructure is accepted and released. Second, each realization of the service is accepted and released. There can be significant problems during the second stage if the required responsiveness of the service does not leave sufficient time to ensure that the service meets necessary functional and quality attributes, including interoperability, safety, and security. (See Service Systems Engineering).
Transition and deployment of a system may introduce unique requirements that are not necessary for operation or use. These requirements can influence the design of the system; therefore, must be considered during the initial requirements and design stages. The most common examples are related to the need to transport the system or system elements, which often limits the size and weight of the system elements.
Transition can also require its own enabling systems, each of which can be realized using a systems approach.
Use of the system to help enable delivery of user services is often called “operations” (INCOSE 2011). A system’s effectiveness is normally considered throughout the operational life of a system. For a complex system, emergent behavior should be considered in three ways:
- to identify and plan for emergent properties within the system realization process (See System Realization KA in Part 3, Systems Engineering and Management)
- to incorporate mechanisms for identifying and handling unexpected emergent properties within the system during its use
- to provide necessary procedures for dealing with wider system consequences of unexpected emergent properties in the enterprise (e.g., emergency responses or medical first aid)
Operations require their own enabling systems, each of which can be realized using a systems approach.
System Sustainment and Maintenance
System sustainment requires maintenance of the system throughout its useful life (INCOSE 2011). In system terms, maintenance implements systems that handle entropy and maintaining the SoI in a viable state. Since an open system maintains its existence by continual exchange of energy, information, and materiel with it’s environment, one aspect of its maintenance must be the management of resources in the environment.
Hitchins (Hitchins 2007) describes generic approaches to resource management and viability management based on systems concepts. Resource management identifies the need to consider the acquisition, storage, distribution, conversion, and disposal of resources. Viability management should consider systems to maintain homeostasis and a means for ensuring resilience to environmental disturbance and adaptability to environmental change.
Maintenance will require its own enabling systems, each of which can be realized using a systems approach. Maintenance success is more likely if it is considered as part of the system concept and design well before the system enters service.
A total life cycle systems approach cannot be considered complete without consideration of how disposal of the system will be accomplished. The purpose of disposal is to remove a system element from the operational environment with the intent of permanently terminating its use and remove any hazardous or toxic materials or waste products (INCOSE 2011).
During disposal the entirety of the open system crosses the boundary from the system side to the environment. A complete systems approach must consider how it crosses the boundary and what remains that must be managed by enterprises other than the ones that developed, used or sustained the system. Including disposal in the system approach expands the stakeholders, the enterprises and the external systems that must be considered.
Disposal requires its own enabling systems, each of which can be realized using a systems approach. Some of these may be contained within the system boundaries and others may be external to the system. For the external disposal systems, the interface where the handover occurs must be considered. As with maintenance, a large part of successful disposal requires related issues to have been considered early on in the system’s life cycle.
Hitchins, D. 2007. Systems Engineering: A 21st Century Systems Methodology. Hoboken, NJ, USA: John Wiley and Sons.
INCOSE. 2012. INCOSE Systems Engineering Handbook, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering. INCOSE-TP-2003-002-03.2.2.
INCOSE. 2011. Systems Engineering Handbook, version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering. INCOSE-TP-2003-002-03.2.1.
MITRE. 2011. "Transformation Planning and Organizational Change." . Systems Engineering Guide. Accessed December 4 2014 at MITRE http://www.mitre.org/work/systems_engineering/guide/enterprise_engineering/transformation_planning_org_change/.
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