@NicholasChanCJ I am using ITFlow across a city and started with separate clients for each of the departments. What I found is I couldn't move anything between departments without re-entering the information.
Before I got very far in, I dropped to two contacts, City Hall and Police Department (because of the separation needed for church and state secrets). For the most part, exporting and importing (combining) worked.
In city hall I have five locations where the buildings / departments are. Networks are tied to locations.
City hall contacts are separated by department and location.
Rooms that have assets (server closet / council chambers / conference room(s)) are all listed as contacts with department Facility and location. Cars that have assets (printers / camera's / radios / computers) are listed as contacts with department Vehicle and location.
Unfortunately we don't have the ability (yet) to link documents and files, BUT you can create folders in each and save information appropriately.
And, most unfortunately we don't have the ability (yet) to link multiple anything to a ticket.
What I would suggest in your situation would be something similar to what I implemented. Parent Client (NicholasChangCJ). Contacts and Locations are the ships (HMS-QE / NCC-1701 / AMB-Joe). Link assets to contacts, networks to locations appropriately. Create documents / files folders based on contact names and file appropriately.
For what it is worth, that is what I would recommend.
