All Rocrail features around assembling and operate trains are described here in chapter "trains"
Shunting freight cars and delivery of goods, including logistics by car cards and waybills are a second element in reality.
All Rocrail features around these themes are described here in chapter "operator"
For both issues this dialogue “Operator & Trains” is used.
The Operator Control is an assistance to do car forwarding without real cards, but with help of a dialog. Also composing a consist together is done by this dialog. Cars can be added and left behind for loading, unloading or maintenance.
It offers an easy way for running some parts automatically and the rest by hand.
A card used to represent a specific model car on a layout. It will have at least a basic description of the car such as type and color as well as reporting marks and number to identify it. The carcard information is "permanent," ie. does not change regardless of what the car is currently doing.
A card used with the carcard (above) to indicate the destination, routing and other information about the specific shipment the car is currently being used for. Usually the waybill card is a separate item smaller than the carcard such that it can be clipped to or (more commonly) slipped into the pocket of the carcard leaving the car identification information showing. The waybill may show information about 1, 2, 3, or 4 (sometimes more) movements depending on which side of the waybill is turned up.
The actual "owner" of the card can be either a consist or a location.
This already exists in Rocrail: Locomotive Table.
Every operator get a train/consist, by extended LocControlDialog. (Operator ↔ TrainID)
The dialog contains:
¹) At least the waybill table must be shared by all Rocrail servers.
See: R2Rnet Networking
If every Yard or station is controlled by its own Rocrail server it needs a networking functionality to run trains from station to station in automatic mode.