I've started looking at this as I have a batch process to automate and I think what gears the SFC programming is really the sequencing. Instead of writing a sequence in ladder with bits in a DINT for steps, it displays nicely with indication of where the process is at.
If used with PlantPAx elements or process strategies it's even cleaner as a lot of the code is "hidden" away in a sub-routine.
The Equipment phase helps to have dedicated code that runs in different stages. You'll notice as well that if you were to code the Holding, Stopping or Resetting stages you probably wouldn't use SFC as a lot of times there won't be a sequence as such and it's more of a single waiting state for valves to close and motors to stop rather than a sequence.