Download PDF - Department of Navy Chief Information Officer - U.S. ...

NavyDAANavyCAAcquisition & ProgramManagementDIACAP Working Group (DWG)DON CIODWG GovernanceOPNAV N6/HQMCUSMCDAATechnicalRequirementsUSMCCATransition &ImplementationPEO C4IPMW 160TrainingGovernanceFigure 2 identifies the organizations and the major functionalcomponents of the DON DIACAP transition effort managed byProgram Management Warfare (PMW) 160, Networks, InformationAssurance and Enterprise Services, under Program ExecutiveOffice for Command, Control, Communications, Computersand Intelligence (PEO C4I).PMW 160, as the technical agent for the DON CIO, will developa standardized end-to-end C&A process and acquire andimplement CAST, thus enabling the DON to fully transition fromDITSCAP to DIACAP in a robust, controlled manner. In fulfillingthis role, PMW 160 is providing the strategic planning, subjectmatter expertise and acquisition competency needed to notonly fulfill DON CIO objectives, but to ensure a well-engineered,comprehensive and supportable tool is provided in a timelymanner to support the entire C&A community.Figure 2. DIACAP Transition Governance Structure.priately, this tool is named the C&A Support Tool. Without CASTproviding C&A automation, from initial system registration toeventual system decommissioning, the benefits resulting fromDIACAP would be dramatically limited.The increased DoD emphasis on system security, as a resultof recent Federal Information Security Management Act (FISMA)mandates, makes it critical to automate the entire C&A process.A DON automated tool to improve and standardize the C&Aprocess was recognized in early fiscal year 2007 and is now wellunderway. The plan indicates the procurement of CAST willoccur in late 2008, with initial operational capability available inearly 2009.Figure 3. DIACAP workflow illustration.DON DIACAP Transition ExecutionThe preliminary work in the DON DIACAP transition effortbegan in October 2007. To capture relevant requirements, a seriesof tabletop exercises and process walkthroughs were conductedwith representatives from virtually all C&A stakeholderperspectives. The result was a C&A community understandingof the complexities of the DIACAP process, the respective rolesand responsibilities of each level of interest and a very detailedprocess workflow chart characterized by five levels of fidelity.This detail is illustrated in Figure 3, where Level 1 entails theprocess overview, Level 2 defines all activities, Level 3 assignsall tasks that must be performed, Level 4 delineates each taskand the estimated time for completion, and Level 5 defines howeach task is completed.This workflow chart has been the basis for all follow-on effortsassociated with requirementsdefinition, procurement guidance, thetraining approach and communityimplementation.To fully migrate from DITSCAP toDIACAP, four key program componentsmust be successfully executed:• C&A package generation and requirementsestimation;• Provision for DIACAP transition technicalsupport;• Acquisition of CAST to support endto-endC&A processes; and• CAST training to familiarize the C&Acommunity with the tool’s capability.As envisioned, CAST must support upto 25,000 users ashore and afloat, with aminimum of 2,500 concurrent users. Thisrate is estimated for NIPRNET, with up toan additional 5 percent of this activitylevel expected on the SIPRNET.The architectural approach will notonly accommodate this level of activity,but will also allow seamless expansionshould greater access be required in thefuture.CHIPS October – December 2008 39