## 4 Discussion: Model for G-QMS in SoS
### G-QMS in SoS, Sturcure
#### 4.3.2 G-QMS in SoS Interfaces
Moreover, this transdisciplinary quality management activity needs to be manifested across the three quality dimensions identified in the G-QMS in SoS concept (Section 4.1.3). For example, the capability to coordinate and combine is particularly crucial when dealing with the diversity and volume of the CSs, which includes establishing coordination and combination mechanisms in accordance with the class (type) definitions of the CSs (see Section 4.4.2). The motivation of the G-QMS in SoS is to rely on the QMS\({}_{\text{CS}}\) as much as possible, and by this classification, delineating clear responsibilities among the various organizations involved and reducing the use of management resources. 3. **Interface structure among the local G-organizations**  
The G-QMS in SoS framework is structured to include a network of interfaces that connects the various local G-organizations involved in the SoS project, each with specific responsibilities. This is a quality management structure based on a _chain-down of control and reporting levels_, starting from the client through the structure levels and reaching down to each CS. Figure 5 gives a graphical illustration of this structure. This chained interface structure includes a main quality management interface structure, connecting the client and the project's main contractor, facilitated through one or more M&C local G-organizations. The client delineates quality requirements and ensures their enforcement via a contractual agreement with the project's main contractor and establishing a _control and reporting_ interface throughout all the project stages. The M&C local G-organization details the client's quality demands and allocates resources to operate control and reporting tasks across the project's lifecycle. The SoS G-QMS CORE is responsible for implementation, adhering to the stipulated reporting obligations towards both the client and the M&C local G-organizations representing the client. For this purpose, SoS G-QMS CORE is tasked with setting the quality requirements for the internal QMS entities within the G-QMS in SoS framework and ensuring these are met throughout the project, providing balanced feedback. This setup exemplifies a Causal Loop Diagram (CLD), one of the primary structural tools of Systems Thinking [58; 77; 78; 79]. In particular, the SoS G-QMS CORE chains down a level of control and reporting vis-a-vis QMS\({}_{\text{CS}}\) and other subcontractors. From the QMS\({}_{\text{CS}}\) perspective, it must meet both the requirements of the SoS G-QMS CORE (typically its \"customer\") and of its own organizational QMS. _Main quality management interface structure: \"If we are not with each other, we will not be able to work with each other. And here in the project, we are with each other, and this is  
Figure 5: Interface structure of local G-organizations QMSs based on a chain-down of control and reporting levels. a point of success--an advantage in the project\"_ (research respondent). The G-QMS in SoS, in accordance with the SoS project, features an actively participating client who outlines contractual requirements and takes an active part in project management. This is a pivotal factor in the quality management for the SoS project, leading to the formation of the main quality management interface structure, which includes the following key components: First, _a dual interface structure for QMS M&C Local\({}_{SoS_{x}}\)_ embedded in the G-organizational layout structure of the SoS project, which acts as \"_a bridge between East and West_\". The dual interface behavior of the QMS M&C Local\({}_{SoS_{x}}\) is founded on a couple of main principles. Firstly, it aims to ensure that the project aligns with contractual obligations and adheres to professional standards, reflecting the primary objective of its operation. Secondly, its nature is influenced significantly by the \"project's DNA\" or the organizational culture of the specific SoS project.