I don?t know of a document that spells out step-by-step how to design one. You?ve got to put the pieces together.
Look @ the basics:
Fire alarm system ? system of devices & wires that detect and signal high heat (indicative of flame) or smoke (again, indicative of flame)
You know you need a panel ? easy.
You know you need wire between the panel and field devices ? easy.
What field devices do you need???
Initiating (the stuff that ?sees? the problem):
To see high heat, heat detectors (not always needed/required)
To see high heat, smoke detectors (could be on a ceiling or in a duct or elsewhere)
To manually tell others that there?s a problem (manual stations or pull boxes ? not always needed).
Indicating (the stuff that tell people of the problem)
Audible devices (typically horns)
Visual devices (typically strobes)
The job of the designer is to?
First:
* Determine if the building requires a system
* This is done by putting codes together IBC
If required?
Second:
* Find and apply spacing criteria for the different types of required devices. Not really that tough.
* Use circuit types (A or B) that comply w/ local demands
Fire alarm systems are often designed very, very, very subjectively simply because PEOPLE DON?T KNOW ANY BETTER! I don?t believe in or practice CYA engineering. It?s a waste of $ and I won?t allow my name to be associated w/ it.
They can be very easy and w/o subjectivity if you put the parts and pieces together and make records of where/how you did what you done did.
I know that doesn?t answer the question, but hopefully is paints a picture of the basics of the process. No entity wants to attach their name to any document that in sum "tells you how step-by-step". One death/injury/failure/etcetera and the "well I read in Joe Shmoe's book..." crap starts.