Marker lights are made from config which refers to a Memory LOD points. For example:

class MarkerLights
{
	class RedStill
	{
		name = "cerveny pozicni";
		color[] = { 0.3, 0.03, 0.03, 1 };
		ambient[] = { 0.03, 0.003, 0.003,1 };
		brightness = 0.01;
		blinking = 0;
	};
};

The “name = ” part would refer to the models Memory LOD point.

In the default BIS content anything inheriting from 'class Air' will have those marker lights mentioned before. You would either inherit from BIS classes or make your own base classes for your vehicles/buildings and override or add-to their definitions.

Then you define a single point in your Memory LOD of your model with the same name.

Personally, by-and-large I've always created base classes for stuff that do not inherit at all from BIS default content. Often, to do as little as redefine the memory points for various class properties to anglised versions that are easier for myself and others to understand.

Even though they can 'flash/blink' they are not part of the skeletal or user animation system so don't need CfgModels defining.

'class MarkerLights' is a subclass of the basic CfgVehicles class. They are predominatly used on vehicles (like aircraft) and buildings (like TV & radio towers, runway lights etc.).

They 'turn on/off' by themselves when the time-of-day is dusk-till-dawn and also they can be 'told' to turn 'off/on' through scripting too. (I think that last part is correct s'been a bit since I played with Marker Lights.)

If your current model's config inherits from anything that ultimately inherits from 'class Air' and is not specifically nullifying the definitions for MarkerLights then those 'standard' MarkerLights should be available to your model. To use those ones you'd have to have a similar set of points in the Memory LoD as per that excerpt.

Example of user made marker lights config:

class CfgVehicles
{
	class Air;
	class FDF_AirBase : Air
	{
		class MarkerLights
		{
			class FDF_Lime
			{
				name = "lime";
				...
			};
 
			class FDF_Lime_Blinking
			{
				name = "lime_blinking";
				...
			};
 
			class FDF_BumblebeeYellow
			{
				name = "bumblebeeyellow";
				...
			};
 
			class FDF_BumblebeeYellow_Blinking
			{
				name = "bumblebeeyellow_blinking";
				...
			};
		};
	};
 
	class FDF_HelicopterBase : FDF_AirBase {};
	class FDF_BigGaudyHelicopter : FDF_HelicopterBase {};
	class FDF_LittleGaudyHelicopter : FDF_HelicopterBase {};
	class FDF_FasterThanLightHelicopter : FDF_HelicopterBase {};
};

For your various 'colour' classes of 'class MarkerLights' it's probably a good idea to prefix them with your mod/namespace/projectspace prefix. But I'd advised against prefixing the name=“”; with the same. In both cases create a classname & name that describes the colour & whether it's blinking or not. Do not call your class for instance 'class FDF_RightHand_BlueBlinking'. You'd just call it… 'class FDF_BlueBlinking'.

In the above all 3 FDF_BigGaudyHelicopter, FDF_LittleGaudyHelicopter, FDF_FasterThanLightHelicopter would be able to utilize the marker lights defined with the appropraite names if you desired. Just because they are defined doesn't mean they necessarily need to be enabled. Just don't include the associated Memory LoD named selection point.