Add Rotation Logistics (#625)

Move from the internal document to Handbook.
Rearranged some sections and eliminated duplication.

_articles/appdev-oncall-guide.md

@@ -18,14 +18,21 @@ distribute the load. Before being added to the oncall rotation, an engineer must
 5. SSM access to production
 6. Join the #login-situation channel
 
-## AWS Incident Manager Team & Rotations
+## AWS Incident Manager
 
-Rotations:
+See [AWS Incident Manager]({% link _articles/platform-aws-incident-manager.md %}) for more on our paging system.
+
+## Rotations
 
 1. appdev-primary
 2. appdev-secondary
 
-See [AWS Incident Manager]({% link _articles/platform-aws-incident-manager.md %}) for more on our paging system.
+### Logistics
+
+* Expected frequency is about once/every two months but depends on the number of engineers in the rotation.
+* If an employee is unable to cover a specific time frame during their rotation schedule they will need to coordinate with another employee to ensure coverage for the time frame.
+* If primary on-call has not responded within 15 min, secondary on-call will be paged.
+* Every effort will be made to ensure that the same person does not work on the same holidays.
 
 ## Emergency Contacts
 
@@ -37,6 +44,8 @@ For Login.gov and vendor emergency contact information see [Emergency Contacts](
 
 The AppDev Rotation hands off every **Monday at 12pm Eastern (9am Pacific)**.
 
+Handoffs on holidays will be managed on a case-by-case basis.
+
 When handing off:
 
 * Update the `@login-appdev-oncall` Slack handle to be the new person