Can one Storage serve more than one Site? If not, it seems you have:
Storage >- Sites -< Operations -< JoinTable >- Storage
You didn't say what exactly needs to be tracked here, so the join table might not be strictly necessary - but you are certainly describing a many-to-many relationship between Operations and Storage.
Thanks for the comment.
Fortunately, Storage vessels are limited to the Site on which they're found; a Storage vessel cannot service other Sites.
Can you please describe what happens in a Join Table? I believe this is where the links (in this case) between Storage and Operations are made, but how would I go about doing that? I know the fields would include: Site_ID, Storage_ID, Operation_ID, but how the fields be completed? Manually? Any clarification would be helpful because it just might suit my needs.
I know the fields would include: Site_ID, Storage_ID, Operation_ID
The SiteID field is redundant, since the site is known from the operation record. There would also be fields to describe the unique join (I don't know what they might be - perhaps quantity?).
For a basic demo of a join table, see: