If there is logic in between, it could be related to a HMI pushbutton or something similar.
With a HMI's momentary pushbutton, it's not like a physical PB which holds an input high as long as you hold the button on. When you press the button, the HMI sends a message to the PLC, saying "set bit x to 1". Then, when you release the button, the HMI sends another message to the PLC, saying "set bit x to 0". If that second message gets dropped, your button is now stuck on. For this reason, any time I use a button on a HMI, I have the PLC immediately turn the button back off, and set a different bit for one scan - and that's the bit I use throughout my code for "button pressed".
This could be something similar: when B1 is activated, turn it straight back off and turn on bit C1. After the rest of the logic does whatever it needs to do, with the knowledge that B1 was activated, C1 gets turned off as well.
Of course, if there's nothing in between those two rungs, then as robert said - seems pretty pointless.