Proto-6 uses a somewhat more complicated Scheduler Control Services server. This is done for illustration and research purposes.

Without the scheduling aspect, an IMA Model cannot run. So it is there.
The scheduling aspect is the aspect of objects being scheduled in one or more queues. They are placed in a queue in any defined order. And when the time is there, they are taken from the queue due to a weighting mechanism.
Examples are the first-in first-out queue and the inter-arrival-time queue.

In the IMA Model, the scheduling aspect represents the time, without which no ‘running’ is possible.

Many schedulers with different internal structures can be defined using Scheduler Control Services.
Also one must place an object as token in a Scheduler queue as well as ask a Scheduler to release a token that meets given conditions using Scheduler Control Services.

The choosen scheduler mechanism will not, in its full extents, be explained in this document.

The scheduler object model contains all schedulers. They can be structured as one scheduler of a kind, or as a set of schedulers related each to a resource or a task type.
Per resulting entity, queues with all kinds of ordering mechanisms can be added.

On the other hand, a weighting mechanism can be defined for every scheduler. This is always an overall mechanism for the scheduler.

Tokens are placed in the scheduler regarding their structure entity and order type. They are released from the scheduler regarding the weighting mechanism.

The objects to be queued are passive objects within a token.