Don't get this.
DevOps is an example of one of many processes that can be applied in the event of a fire, if it happens to be the way your work, but how does that make DevOps different, special, unique?
As much as I dislike twitter, they are as much as part of the same process, communicate is pretty important to.. during the event (and actually if your doing it right - before - "Hey Customer, When/if this happens, don't panic, this is what's we're going to be doing.. and this is how long it will take, and this is when you get an update and this is the role that will be doing the update, so communicate that to your management and give them the impression you are in control.")
I mean having an up to date out of office telephone list of your IT department is probably more important.
And, in any 'Fire' the biggest uncertainty is finding out what happened. If your doing it right you don't need to find out "Hey Bob, what happened?" - "I dunno, we failed over to our other location, we'll get someone looking at it now, it's still a P2 as we've lost some redundancy" If you're not, then you need to get on that phone list and start calling, to get the people to figure it out what to fix, and if it's code, what's that -10% of the time, then you need to get them to figure a fix - and then, finally you call upon automated delivery. Whoopee, so if at that point they say - it'll take 3 days to release - cause it's not DevOps? Not likely.
Frankly, spontaneous code issues, that cause a fire, are relatively rare. Unless we're talking releases. And that's should be covered by engineers pre-booked, and rollback procedures.
TL;DR If DevOps is core in your 'fire' safety procedure, you're more Dev than Ops, and you certainly don't know enough to plan tackling it.