In reply to uvmsd:
The sequencer/sequence works on the transaction level. This does not know anything about timing, clock cycles etc. And the sequencer is not sending anything. The driver is retrieving a seq_item from the sequencer. In the default implementation this interface is blocking, i.e. the driver is waiting until a seq_item is ready.
In your case you have to implement ‘your delay’ in the driver. I believe you have soething like an acknowledge indicating your DUT is ready and waiting for a new input.
After seeing this acknowledge you can execute ‘item_done’. Then the driver will get the next seq_item.