I know you must be trying to limit the number of possible tags given to a frequency. I'm having some difficulty fitting many of the frequencies I am familiar with into the categories you have listed. I'm trying to fit square pegs into round holes and the round pegs are often falling through square holes and out of sight. Here are my observations on the listed categories.
The federal government, specifically the natural resource management and wildland fire management agencies categorize many of their frequencies into command, tactical, and logistical. Command nets are reserved for communications between division/group supervisors, branch directors, the operations chief, and the incident commander. Command nets usually have repeaters employed. Command is also used between the incident and the local area dispatcher. Tactical nets are for individual resources to communicate with each other and with and their supervisor, whether that be a strike team leader, a division/group supervisor, or the operations chief if the incident is not large enough to divide into divisions and/or groups yet. Tactical nets use simplex. Logistical nets are established to provide communications for such things as incident check-in, food, supply, vehicle maintenance, and between people at the incident base. Logistical nets can utilize repeaters or simplex. This is the way the well known National Interagency Incident Radio Support Cache is organized. The frequencies are perhaps better known as the "NIFC Frequencies" referring to the National Interagency Fire Center. This radio system is often used for nationally significant incidents such as hurricanes, floods, tornadoes, and even the conventions of the two major political parties.
Many radio systems of state and local agencies are being organized in a similar fashion. Agencies are installing repeater networks to be used for command and installing simplex frequencies for tactical purposes. Often these nets are only for use on large incidents which overwhelm the day to day dispatch and tactical nets. They are quite often multi-functional in nature with law enforcement, fire, EMS, animal control, roads, and administrative functions using them. Thus they do not fit any of the "multi" tags as they involve more than LE, Fire, and EMS. The multi tags do not reflect the command function either. The closest tag to the command function is dispatch, either fire or law enforcement, or multi, however this does not reflect the command function that many frequencies and networks are reserved for. I would suggest adding law enforcement, fire, EMS, and multi command tags.
In the area of natural resource management we are seeing more and more jurisdictions splitting their radio systems into separate nets. In the past a National Park or National Forest had one net and it was called "Park Net" or "Forest Net." We are now seeing them split these along functional lines so that you have law enforcement, fire, maintenance, administration split into separate nets, all with repeater systems for each or perhaps fire and law enforcement on a net called the "Emergency" net and everyone else on an "Admin" net. In a few of the very largest and busiest National Parks that are exclusive federal jurisdictions, where the National Park Service provides all EMS services in the park, there is even a EMS net in that park. In the past I've seen these nets tagged with "Forestry Operations" or "Rangers" and these do not reflect the nature of the work done by these agencies or the functions of the listed frequencies. I would guess we will have to use the multi dispatch and tac categories for these agencies, but I would rather see an admin category. Many state natural resource agencies have split up their radio systems and removed law enforcement from all their other functions, giving LE a frequency of their own. I have observed, at the federal level, that following the narrow band mandate of 2005, that agencies have split up their over congested "one size fits all" networks into functional networks due to the increased number of frequencies available. The same will probably happen when state and local agencies are subject to narrow banding in 2013.
The federal tag for all federal government operations does not reflect the functions of natural resource agencies at the federal level and is so broad as to be nearly useless. When I'm looking for frequencies I don't want to lump the Veterans Administration with the Border Patrol along with National Parks and National Forests. These are too different to lump into one broad category.
Many city and county governments establish networks for public works (roads, water, and sewers) and for all other functions (building inspectors, zoning and code enforcement, parks, personnel, IT, animal control, facility maintenance, zoos, etc) have a "Admin" or "Administrative" network. In my mind, and certainly in the minds of most people who work either for the government or with it frequently understand that public works is something you get your hands dirty with and is strictly infrastructure related. Administrative implies all the other things local agencies do.
In summary I would suggest the federal government split into law enforcement, fire, and administrative tags. I would like to see the local agency tag of "public works" split into "public works" (roads, sewer, and water) and administrative (all non public works). In the multi category I would suggest adding a "multi command" tag.
In taxonomy (putting plants and animals into categories such a species, genius, class, kingdoms, etc) it is often said that "there are splitters and there are lumpers." The same is true of any system that places things into categories. My suggestions are a compromise between the two.
