These are the 12 steps (actually 9, it used to be 12) all front-end programmers must follow to support alarms on a front-end.

1. The front-end programmer is contacted.
2. Front-end programmer prepares the front-end for providing alarms.
3. The front-end programmer contacts Brian Hendricks <hendricks@fnal.gov> to create a download file and to modify D121(non-camac)/D52(camac) to access it (*).
4. Front-end programmer loads initial devices in download file using D121(non-camac)/D52(camac)(*).
5. Front-end programmer reboots the front-end to initialize the alarm blocks.
6. Front-end programmer contacts Brian Hendricks <hendricks@fnal.gov> to modify the alarms configuration database.
7. Front-end programmer updates the alarm and subsystem mask for the front-end in the database using console application page D98.
8. Front-end programmer should verify that at least one device is successfully reported on an alarm screen.
9. Front-end programmer notifies original requester so that they can configure their alarm screens appropriately.

(*) These steps are not necessary for open access and IRM front-ends.