A Flow is the simulator’s routing definition: it is the step-by-step description of how an entity moves through a sequence of primary stations, what default labor and machine times apply, what secondary resources or operators are required, and where the entity goes next (including optional alternate next locations, probabilities, transport resources, and travel time). A FlowDesc entry is the higher-level “directory” record that simply defines and names a flow code for a part family. It exists so multiple products can reference the same flow code even if their processing times differ, and so feeder/subassembly routings can be defined as their own distinct flows. In practice, you create the flow codes in FlowDesc, build their detailed routings in Flow, and then assign each product to the correct flow code in the Products table.