I'll start off with a question. Are sites needed for my organization?

Now the reason I ask. I was not part of the group that initially set up our ManageEngine products for my organization. I've been in it for about a year myself and in that time I've realized that many things weren't set up in the best use manner. I'm sure this is from lack of understanding since it was all a learning process. And once things got to a point where they worked, it was kept that way since it was good enough.

I work for city government so we have facilities all over the city. When SDP was first set up we considered each facility it's own site. However now I realize that SDP recognizes sites as entirely different geographic locations. So it assumes that techs would not work or associate with multiple sites.

Our sites  for example are: 001 Art Museum, 056 Police Headquarters, 009 Fire Station 9 and so on. 

With a recent AD sync the Office field was selected. This has data other than what we considered sites. Like "Headquarters 3rd Floor, Room 301". SDP considers anything pulled from the Office field in AD as a site. So now our sites list has grown to a few hundred items long and it's only going to get longer.

In my mind our only site should be "City of So&So". But since at that point we'd only have the one site, do we need it at all? 

I've created an additional field under requesters called Location. My AD sync has it aimed at the Office field in AD. I've also disabled the AD sync option for sites. This way it doesn't create any new ones. 

The only drawback I can think of now is under assets. If I change our sites to only one or remove it altogether, then any asset will also lose it's site since it uses the same one of the owner it's assigned to. 

So back to my main question. Do I really need a site(s)? If your organization is similar where you have multiple buildings in the same geographical area, how do you use sites?