Morrow Project Nomenclature

[natehale1971]

I'm trying to come up with how the Project would name each of it's bases.

We have Prime Base, the national headquarters for the entire project. Thus it's name, PRIME Base. And we have the name of the automated Regional Supply Base Delta that is located somewhere in western Kentucky. We also have Commo Base Kilo Echo as an example of a manned communications facilities...

But what kind of names should we use for the other bases?

I had thought of naming bases after the 'greek' alphabet to fit into the regional supply base Delta. But i really think that should only be used for the names of the automated supply bases.

[mikeo80]

Originally Posted by natehale1971

I'm trying to come up with how the Project would name each of it's bases.

We have Prime Base, the national headquarters for the entire project. Thus it's name, PRIME Base. And we have the name of the automated Regional Supply Base Delta that is located somewhere in western Kentucky. We also have Commo Base Kilo Echo as an example of a manned communications facilities...

But what kind of names should we use for the other bases?

I had thought of naming bases after the 'greek' alphabet to fit into the regional supply base Delta. But i really think that should only be used for the names of the automated supply bases.

I agree with this nomenclature. In one game we had a Automated Supply Base in Eastern North Carolina that was called Epsilon.

The naming of teams does not seem to follow a set pattern.

In the games I have been in, we typically run our teams in and around NC (where we live). We use NC - R/S/M/E (for the type of team) - ##

[natehale1971]

I have come up with a set nomenclature for the teams that the new owners of the Morrow Project has actually asked if they can use along with some of the other stuff as well.

two digit state code, then code for team type, then the team number... I even posted examples using the teams that had been used in all of the modules that i've got.

example...

NC-R-09 would be North Carolina Recon Team 09. the ninth recon team assigned to the state of North Carolina. if you get a chance to check out the Combined Operations Group it gives you an example of how i set up the team nomenclatures.

[kato13]

Originally Posted by natehale1971

example...

NC-R-09 would be North Carolina Recon Team 09. the ninth recon team assigned to the state of North Carolina.

While those are fantastic from a management perspective, that type of code could be a hindrance from a security perspective. Lets say the KFS secret police finds the cache for KY-R-11. They then know that there are at least 10 other Recon teams within their state borders. It gets worse if the teams are placed in some type of order. (north to south/east to west, or clockwise or such)

[natehale1971]

Originally Posted by kato13

While those are fantastic from a management perspective, that type of code could be a hindrance from a security perspective. Lets say the KFS secret police finds the cache for KY-R-11. They then know that there are at least 10 other Recon teams within their state borders. It gets worse if the teams are placed in some type of order. (north to south/east to west, or clockwise or such)

The only problem is that the KFS didn't exist when the project came into being... And being the bastard child of a group of industralists the nomenclature would be simple and easy to understand... i had contemplated dividing each state into numbered districts and the number in the team ID was coresponded with the district the team 'embedded' when placed in cryo... but then you could then end up with more than one team of the same speciality ending up with the same number. So i came up with something that would have a unique ID number.

The number could be the order that the team had been emplaced in a combined operation group (example 01 could have be the Command and Control Team, while 09 could have been the first recon team).

[kato13]

I still feel that it is a security risk to go with incremental numbers. It does not have to be KFS it could be a newspaper reporter or an ATF official who runs across the number. If a reporter comes across TX-R-01 and TX-R-24 and puts together what that means, they could possibly extrapolate the overall size of the project.

[Traveller]

For my own game, I use a two-four digit alpha-numeric system, that identifies group and team number, regardless of location/team type.

These Alpha/Numeric call signs are the basic team/unit identifiers within the Project, and are used in radio communications, written and electronic correspondence, and other media. For example the 2nd Recon Team in Texas is known as Recon Team A-10, or simply A-10. The 3rd MARS Team in Kentucky is known as MARS Team K-98, or simply K-98.

As well, MARS Force units are identified by a two character Alpha prefix ZM (Zulu Mike) denoting them as Regional MARS assets, with a two digit numeric suffix; the first digit denoting the specific region they are assigned to and the second digit representing their specific team number. For example, ZM-30 would indicate the MARS-One/Command Team for MARS Force 3 (Region III). ZM-26 on the other hand would indicate the Mortar Support Team of MARS Force 2 (Region II).

Bases also use the two-four digit alpha-numeric identifiers are used by the Project to identify Support Division assets and the other Project Special-Purpose teams. Examples include:

Project Launch Facility (UL-10);
Project Hospital Installations (VF-1-10); and
Project Farm Groups (XF-1-10)

As well, Support Teams have designators such as:

Admin/Liaison Teams (DL-##).
Supply Base Teams (DS-##).
Maintenance/Recovery Teams (DR-##).

I have others of course, but I think you get the idea.

Anyway, I've found this works for me over the years; your results may vary...

Cheers!
Traveller