As described in Puget Sound's custom Rigor Code modeling, the standard extract job contains a custom step which calls the job on the report server to run this modeling. (This step is in the Extract 2 job.)

The standard extract is modified with this custom step because the custom modeling job needs to run after the extract: calling the custom modeling job from within the extract job ties the run times of these jobs together so that both will change if the extract job's schedule is changed.