Kevin
I don't see this being very complicated even if we do not have a Runbook available.
Think of this in the fact that it is regular SAML and as long as both entities participating in the Federated SSO work as per SAML specification, it should be easy to understand IdP and SP requirements, then map that into a Federation Partnership at both ends.
The key things I'd take care of is....
- Is it IdP Initiated Journey OR SP intiated journey.
- Who is IdP and who is SP.
- Audience Info.
- Assertion Consumer Service URLs.
- Exchanging the IdP IDs and SP IDs.
- Finalizing Assertion Attributes.
- Signing Certificate and Signing Assertions.
I'd begin with a basic partnership and build from there.
Regards
Hubert