The data structure looks good, but with 1 to 1 relationships you always have to ask yourself whether you really need it (the same goes for *-* relationships, by the way). Personally I think that these relationships should be 1-* so that the organization can occur through multiple customers, for example, but this depends on your business case.
I think I would remove the empty (the ones without attributes) entities and make a direct association with the organization, by applying good naming to the associations you can distinguish these relationships.
So for example an association between MotherAsset and Organization with the association name "MotherAsset_Organisation". This already makes clear what that organization is in relation to the MotherAsset.
I recommend that you just start building the pages and focus on the functionality you need to build. Thinking about a domain model causes a "builder's block" for many starting developers. By implementing the functionality you will automatically notice and discover whether the domain model fits your solution!
Thank you for the help!