Systems engineering as a part of network development

A systems engineering process (SEP) has been used in complex engineering problems having various properties. It involves multidisciplinary expertise and is especially applied in solv-ing increassolv-ingly complex technological questions. Accordsolv-ing to NASA Systems Engineersolv-ing Handbook (NASA, 2016):

At NASA, “systems engineering” is defined as a methodical, multi-disciplinary approach for the design, realization, technical management, operations, and retirement of a system.

A “system” is the combination of elements that function together to produce the capability required to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed for this purpose; that is, all things required to produce system-level results. The results include system- level qualities, properties, charac-teristics, functions, behavior, and performance. The value added by the system as a whole, beyond that contributed independently by the parts, is primarily created by the relationship among the parts; that is, how they are interconnected.¹It is a way of looking at the “big picture” when making technical decisions. It is a way of achieving stakeholder functional, physical, and operational performance requirements in the intended use environment over the planned life of the system within cost, schedule, and other constraints. It is a methodol-ogy that supports the containment of the life cycle cost of a system. In other words, systems engineering is a logical way of thinking.(NASA, 2016). Citenote¹: (Rechtin, 1999)

Other definitions exist for instance in standards (ISO/IEC/IEEE, 2015), (EIA/IS-632, 2015), and (IEEE, 2005). Figure 5.4 illustrates the process (Department of Defence, Systems Management College, 2001). In addition, (Forsberg and Mooz, 1994) provides extensive illustrations of the project cycle.

80 5 LVDC as part of the network development

5.1.1 Systems engineering as a part of network development

A systems engineering process (SEP) has been used in complex engineering problems having various properties. It involves multidisciplinary expertise and is especially applied in solv-ing increassolv-ingly complex technological questions. Accordsolv-ing to NASA Systems Engineersolv-ing Handbook (NASA, 2016):

At NASA, “systems engineering” is defined as a methodical, multi-disciplinary approach for the design, realization, technical management, operations, and retirement of a system.

A “system” is the combination of elements that function together to produce the capability required to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed for this purpose; that is, all things required to produce system-level results. The results include system- level qualities, properties, charac-teristics, functions, behavior, and performance. The value added by the system as a whole, beyond that contributed independently by the parts, is primarily created by the relationship among the parts; that is, how they are interconnected.¹It is a way of looking at the “big picture” when making technical decisions. It is a way of achieving stakeholder functional, physical, and operational performance requirements in the intended use environment over the planned life of the system within cost, schedule, and other constraints. It is a methodol-ogy that supports the containment of the life cycle cost of a system. In other words, systems engineering is a logical way of thinking.(NASA, 2016). Citenote¹: (Rechtin, 1999)

Other definitions exist for instance in standards (ISO/IEC/IEEE, 2015), (EIA/IS-632, 2015), and (IEEE, 2005). Figure 5.4 illustrates the process (Department of Defence, Systems Management College, 2001). In addition, (Forsberg and Mooz, 1994) provides extensive illustrations of the project cycle.

5.1 Network development 81

Figure 5.4:Systems engineering (Department of Defence, Systems Management College, 2001).

A systems engineering process has many useful elements that can also be applied to LVDC systems, especially in the early stage as there are no established practices for the application of the process. What is often highlighted is the need for early-stage attention as the consequences of design choices done at the very beginning are manifold, and therefore, manipulating parts of the system in a later phase may be problematic and costly. Figures of estimates can be found for instance in (NASA, 2016), where it can be seen how the percentage of costs develops in time, or vice versa, how the ”cost savings” can be obtained at the beginning.

V-cycles have been provided by many authors and stakeholders depending on the specific needs of a particular field of practice and projects. A V-cycle is a graphical illustration of the im-plementation of SEP in consecutive steps. Analysis of its different variants is provided in (Graessler et al., 2018). A general example created for the purpose of this work is given in Figure 5.5.

5.1 Network development 81

Figure 5.4:Systems engineering (Department of Defence, Systems Management College, 2001).

A systems engineering process has many useful elements that can also be applied to LVDC systems, especially in the early stage as there are no established practices for the application of the process. What is often highlighted is the need for early-stage attention as the consequences of design choices done at the very beginning are manifold, and therefore, manipulating parts of the system in a later phase may be problematic and costly. Figures of estimates can be found for instance in (NASA, 2016), where it can be seen how the percentage of costs develops in time, or vice versa, how the ”cost savings” can be obtained at the beginning.

V-cycles have been provided by many authors and stakeholders depending on the specific needs of a particular field of practice and projects. A V-cycle is a graphical illustration of the im-plementation of SEP in consecutive steps. Analysis of its different variants is provided in (Graessler et al., 2018). A general example created for the purpose of this work is given in Figure 5.5.

82 5 LVDC as part of the network development

Figure 5.5:Example of the V-model in the LVDC case.

For the time being, as there are no markets, the manufacturers do not have products for this kind of application. Simultaneously, the DSOs do not have a reference for instance for the actual cost of the converters, technical performance, or reliability. The result of this work can help DSOs to understand what is needed for the successful implementation of LVDC systems. It is likely that without consultancy or collaboration, a DSO is not able to start the LVDC assessment and utilization process.

The V-model presented here represents a process involving a DSO and a manufacturer, at the very beginning. When DSOs seek novel solutions, they often start by testing a technology with a limited number of application targets, which is understandable considering the nature of the business. It is about both gathering experiences and verifying the technology and providing a showcase for the parties involved in the business and operation. In that sense, the process depicted in Figure 5.5 is not permanent, considering the future implementations, but rather a way to get started. Table 5.1 goes through the details that are important in different phases in the V-model, assuming that it is now applied to the LVDC distribution.

82 5 LVDC as part of the network development

Customer

Figure 5.5:Example of the V-model in the LVDC case.

For the time being, as there are no markets, the manufacturers do not have products for this kind of application. Simultaneously, the DSOs do not have a reference for instance for the actual cost of the converters, technical performance, or reliability. The result of this work can help DSOs to understand what is needed for the successful implementation of LVDC systems. It is likely that without consultancy or collaboration, a DSO is not able to start the LVDC assessment and utilization process.

The V-model presented here represents a process involving a DSO and a manufacturer, at the very beginning. When DSOs seek novel solutions, they often start by testing a technology with a limited number of application targets, which is understandable considering the nature of the business. It is about both gathering experiences and verifying the technology and providing a showcase for the parties involved in the business and operation. In that sense, the process depicted in Figure 5.5 is not permanent, considering the future implementations, but rather a way to get started. Table 5.1 goes through the details that are important in different phases in the V-model, assuming that it is now applied to the LVDC distribution.