EA-SOP-0003 (VER 1.0), STANDARD OPERATING PROCEDURE: PROCEDURES FOR SUBMITTING A NASA AGENCY FOREST (NAF) DEVIATION REQUEST AND TRANSITION PLAN (30 JUL 2008)

EA-SOP-0003 (VER 1.0), STANDARD OPERATING PROCEDURE: PROCEDURES FOR SUBMITTING A NASA AGENCY FOREST (NAF) DEVIATION REQUEST AND TRANSITION PLAN (30 JUL 2008)., This document establishes the format and procedures for submitting a Deviation Request and Transition Plan for deviation from the prescribed NASA Agency Forest (NAF) architecture. The NAF architecture prescribes a single Active Directory (AD) forest for the Agency. The Deviation Request and Transition Plan covers the following two major types of cases: (i)Center AD installations not capable of being migrated; and (ii) NAF AD trust with a third party The Deviation Request and Transition Plan differs from a waiver in that while the deviation process recognizes that certain Centers can not fully comply with NAF requirements, it does not provide a variance to the requirement to consolidate into the NAF. Instead this deviation process allows for deviations under specific circumstance and mandates a corresponding Deviation Transition plan that defines when the legacy AD forest will be consolidated into the NAF, or decommissioned. This plan applies to all NASA implementations of Microsoft Active Directory that are in scope of the NASA Consolidation of Active Directory (NCAD) project. Nominally all Agency implementations of AD are in scope for NCAD with the specific exemptions of the Jet Propulsion Laboratory (JPL), Mission networks, and special cases such as Wind Tunnel networks.