## 4 Discussion: Model for G-QMS in SoS
### G-QMS in SoS, Sturcure
#### 4.3.1 G-QMS in SoS Entities  
In Figure 2, an independent category [8.3] with a Si\({}_{\text{Total}}\) = 9.54 was identified for the QMS entities. These key structural entities are elaborated below, beginning with the internal and continuing with external ones, while Figure 4 presents a graphical view of them. * _SoS G-QMS CORE_: In accordance with base anchor number 1 [1], and the main principles already identified for the model [2], G-QMS in SoS requires a CORE entity, which functions as the headquarters of the G-QMS in SoS. The CORE chief reports to the SoS project chief manager and is a member of the SoS project chief management team. * _SoS-QMS-C&I_ (_QMS\({}_{\text{Integ}}\)_): Refers to the QMS for the integrated SoS engineering function at the C&I stage. This QMS entity is recognized for its paramount importance, with a recognized need for enhancement in its quality management capabilities (Section 4.2.2(d)). It serves as a central hub for multiple interfaces among all the CSs involved in the SoS, necessitating its definition from the project's planning phase. QMS\({}_{\text{Integ}}\) maintains an active interface with the SoS G-QMS CORE. It is recommended that the QMS\({}_{\text{Integ}}\), head has both a _direct_ reporting line to the SoS G-QMS CORE chief and an _indirect_ one to the Integration body head. This structural arrangement underscores the importance of QMS\({}_{\text{Integ}}\), within the SoS project's quality management framework, with its effectiveness contingent upon the professional caliber of the SoS G-QMS CORE entity. * _SoS QMS T&C_: Denotes the quality management functions during the validation stage. The research highlights a strong motivation to enhance the role of quality engineering in the field of tests and experiments, acknowledging that quality engineers, typically in this field, possess specialized knowledge and skills that can greatly contribute to the success of this phase. * _SoS QMS handing over_. Refers to the quality management functions during the handing over phase, which includes a distinct role for quality management. * _QMS entities and other areas_, such as PS and RAMST, need to be integrated under an independent quality management framework specific to the project. Typically, these entities are branches of the QMS entities belonging to the G-QMS of G-org. of SoS model, combined locally in the SoS project management program. The main external QMS entities comprise the following:  
* _QMS Client_: The typical client (or _owner_) of SoS is itself a large and significant organization, sometimes a government or military authority. Similarly to other G-organizations, the client typically establishes a local organization unit specifically tasked with overseeing the SoS project in order to successfully ensure its ordered asset. The client effectively becomes an integral component of the overarching G-organization architecture built for the SoS project. As part of this structure, the client entity also incorporates its own QMS. * _QMS M&C Local\({}_{SoS}\)_. The QMS entity of the M&C Local\({}_{SoS}\) for a specific SoS project (denoted by \(X\)). This M&C Local\({}_{SoS}\) aims to ensure the project's adherence to its scheduled timelines, content delivery, and required quality level. It is composed of expert leadership teams that parallel the main contractor's organizational structure, effectively serving as a \"mirror image\" to monitor and control the project's execution. Within the M&C Local\({}_{SoS}\), there exists a dedicated team focused on quality management, known as the QMS M&C Local\({}_{SoS}\), entity. The broader M&C Local\({}_{SoS}\), encompassing various functional areas _beyond_ just quality management, is _fundamentally_ a quality management function in itself. Its comprehensive monitoring and control mechanisms contribute significantly to the strength of the _control structure_ within the entire global organizational framework established for the SoS project.