To continue with the Project Knowledge Sectors discussion from Project Knowledge Sectors (01). From these Knowledge Sectors we can now derive an understanding of the overall Project Knowledge Model (PKM) and how it "flows" together no matter whether it is the Vehicle or the System.

So if we look at the flow:

• Looking left to right we have - "this requirement is going to be satisfied by these solutions that will be transformed by these processes".
• Looking right to left we have - "these processes will transform these solutions to satisfy these requirements".
• If we go from the centre out, then we have - "these solutions have been designed to satisfy these requirements and will be transformed by these processes" or "these solutions, to be transformed by these processes, when complete will satisfy these requirements".

A point to note with this model - I call the Solution Space for both the Vehicle and System - the "Pivot". It is the Solution Space around which the Requirement and Process pivot.

Now to me, this is easy to understand and to see broadly how the Sectors come together to form a project. Indeed, fill all the Sectors in and you start to see the Project Knowledge Elephant! It is also more of a "flow" and not "blocky" - more of a melody than hip=hop [see A Melody not Hip=Hop (01) and A Melody not Hip=Hop (02)].

But what if we were to decompose these Knowledge Sectors still further? That is what I wish to address next but I first need to explain another fundamental relationship set. It is a relationship set crucial to understanding the Project Knowledge Model (PKM) and it is what I call the Generic Systems Model (GSM).