DEPARTMENT OF THE NAVY

CHIEF INFORMATION OFFICER 1000 NAVY PENTAGON WASHINGTON, DC 20350-1000

5 December 20 11 MEMORANDUM FOR DISTRIBUTION Subj: DEPARTMENT OF DEFENSE INFORMATION TECHNOLOGY PORTFOLIO REPOSITORY- DEPARTMENT OF THE NAVY (DITPR-DON) PROCESS GUIDANCE (V1.0) Ref: (a) Department of Defense Information Technology Portfolio Repository- Department of the Navy (DITPR-DON) Registration Guidance for 2006, June 2006

Encl: (1) Department of Defense Information Technology Portfolio Repository- Department of the Navy (DITPR-DON) Process Guidance (vl.O) Enclosure (1) is the Department of Defense (DoD) Information Technology (IT) Portfolio Repository- Department of the Navy (DITPR-DON) Process Guidance (v1.0), which updates and supersedes reference (a). DITPR-DON is the authoritative source for the Department of the Navy (DON) IT systems and is the data source for multiple internal and external reports and processes. This guidance document provides a comprehensive discussion of core DITPR-DON functionality and basic lifecycle transactions. It will enable users to gain the understanding necessary to perform the basic IT asset management functions of registering, transferring, and archiving DON IT systems within DITPR-DON. Enclosure (1) may be revised in the future to address changes in core DITPR-DON processes resulting from changes in DoD or DON policies and/or processes. This guidance is effective immediately. For additional information, please contact Dr. Michelle Schmith, (703) 695-1851, DSN 225, michelle.schmith@navy.mil.

Distribution: CNO (DNS, N091, N093, N09S, N097, N1, N2/N6, N3/S, N4, N8) CMC (ACMC, ARI, M&RA, I, I&L, PP&O, C4, P&R) ASN (RD&A)- ACQUISITION FAM ASN (M&RA)- CIVILIAN PERSONNEL FAM ASN (I&E) ASN (FM&C)- FINANCIAL MANAGEMENT FAM GC- LEGAL FAM DON/AA DUSN/DCMO

Subj: DEPARTMENT OF DEFENSE INFORMATION TECHNOLOGY PORTFOLIO REPOSITORY- DEPARTMENT OF THE NAVY (DITPR-DON) PROCESS GUIDANCE (Vl.O) Distribution: (continued) DUSN (PPOI) ASN RDA CHSENG DASN C41/SPACE DASN AIR DASN SHIPS DASNRDT&E DON DEP CIO (Navy) DON DEP CIO (Marine Corps) COMFLTCYBERCOM Command Information Officer COMUSFLTFORCOM Command Information Officer COMUSNAVEUR Command Information Officer COMPACFLT Command Information Officer COMUSNAVCENT Command Information Officer BUMED Command Information Officer COMNAVDIST Command Information Officer USNA Command Information Officer COMNAVAIRSYSCOM Command Information Officer COMNAVRESFORCOM Command Information Officer NETC Command Information Officer COMNAVSEASYSCOM Command Information Officer COMNAVSUPSYSCOM Command Information Officer DIRSSP Command Information Officer CNIC Command Information Officer NAVPGSCOL Command Information Officer COMNAVFACENGCOM Command Information Officer COMNAVSAFECEN Command Information Officer BUPERS Command Information Officer COMUSNAVSO Command Information Officer ONI Command Information Officer ONR Command Information Officer COMSPAW ARSYSCOM Command Information Officer NA VHISTHERITAGECOM Command Information Officer PEO C41 SAN DIEGO CA PEO CARRIERS WASHINGTON DC PEO EIS WASHINGTON DC PEO SPACE SYSTEMS CHANTILLY VA PEO LAND SYSTEMS QUANTICO VA PEO IWS WASHINGTON DC PEO LMW WASHINGTON DC PEO SHIPS WASHINGTON DC PEO SUB WASHINGTON DC PEO ASW ASM PATUXENT RIVER MD

Subj: DEPARTMENT OF DEFENSE INFORMATION TECHNOLOGY PORTFOLIO REPOSITORY- DEPARTMENT OF THE NAVY (DITPR-DON) PROCESS GUIDANCE (Vl.O) Distribution: (continued) PEOTACAIR PATUXENT RIVER MD PEOUAVNSTRKWPNS PATUXENT RIVER PEO JSF ARLINGTON VA MARCORSYSCOM MARFORCYBERCOM

UNCLASSIFIED

DepartmentofDefense InformationTechnology PortfolioRepository DepartmentoftheNavy (DITPRDON)

PROCESSGUIDANCE
Version1.0 28 November 2011

DEPARTMENTOFTHENAVY CHIEFINFORMATIONOFFICER

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

DOCUMENTCONTROLCHANGE
VersionNumber DateofIssue

Section(s)

BriefDescriptionofChange

Page|i

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED CONTENTS

28November2011

ExecutiveSummary.........................................................................................................................iii 1.0 Introduction............................................................................................................................1 1.1 Purpose..............................................................................................................................1 1.2 Scope.................................................................................................................................1 1.3 Background........................................................................................................................2 1.4 DITPRDONFunctionality..................................................................................................4 2.0 DITPRDONAdministration.....................................................................................................6 2.1 RolesandResponsibilities.................................................................................................6 2.2 AccountRequestandAccessAuthorizationProcess........................................................9 3.0 GeneralGuidelinesforUsage...............................................................................................10 3.1 WhentoRegisteraSystem.............................................................................................10 3.2 WhatMustbeRegisteredinDITPRDON........................................................................11 3.2.1 EntryCriteria................................................................................................................12 3.2.2 RegistrationGuidelines...............................................................................................13 . 3.3 HowtoTransferOwnershipofaSystem........................................................................15 3.3.1 HowtoTransferaSystemtoAnotherService............................................................15 3.3.2HowtoTransferaSystemtoAnotherEchelonII.........................................................16 3.3.3HowtoTransferaSystemtoAnotherFunctionalAreaManager................................16 3.4 HowtoUploadaDITPRDONRecordtoDITPR...............................................................16 3.4.1 UploadCriteria............................................................................................................17 3.4.2 ReviewProcessandSystemUploadtoDITPR.............................................................17 3.5 HowtoArchiveorUnArchiveaDITPRDONRecord......................................................18 3.5.1 HowtoArchiveaSystemRecordinDITPRDON.........................................................19 3.5.2 HowtoUnArchiveaSystemRecordinDITPRDON...................................................20 FIGURES Figure1:ReferenceDocumentsSectioninDITPRDON.................................................................2 Figure2:RelationshipbetweenDADMSModules .........................................................................3 . Figure3:SystemInformationCategories.......................................................................................5 Figure4:ReferenceDocumentsSectioninDADMS.....................................................................12 Figure5:MissingDataBarsonCOREScreen................................................................................18 Figure6:HowtoUnArchiveaSystemRecord.............................................................................21 TABLES Table1:AdministrativeRoles&Responsibilities...........................................................................6 . Table2:UserBasedRoles&Responsibilities.................................................................................7 Table3:OnlyValidReasonsforSystemArchival..........................................................................19 APPENDICES AppendixA: GlossaryofTermsandAcronyms........................................................................A1 Page|ii

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

ExecutiveSummary
This Department of Defense Information Technology Portfolio Repository Department of the Navy (DITPRDON) Process Guidance document provides a comprehensive discussion of core DITPRDONfunctionalityandbasiclifecycletransactions.Thisinformationwillenableallusersto gain the understanding necessary to perform the basic information technology (IT) asset managementfunctionsofregistering,transferring,andarchivingDepartmentoftheNavy(DON) ITsystemswithinDITPRDON.Guidanceisalsoprovidedontheadministrativeanduserbased rolesandresponsibilitiesassociatedwithDITPRDON,clearlydelineatingtherequirementsfor eachtaskandstepwithinthecoretransactions.Specificinformationonhowtoaccessguidance onadditionalfunctionalitycapabilitiesofDITPRDONisalsoprovidedinthisdocument. DITPRDONisthesingleauthoritativesourcefordataregardingITsystems,includingNational Security Systems (NSS). It provides senior DON decision makers with the context and key informationtosupportITinvestmentdecisions.DITPRDONalsoprovidesconsistentautomated processes across the Department to meet both internal and external compliance reporting requirements associated with numerous federal and defense policies and mandates. It is imperative that DON users, administrators, and stakeholders understand the critical role that DITPRDONplaysinITassetmanagementandITinvestmentmanagement,anditsoverallvalue asatooltosupportDONITportfoliomanagement.Thisguidancedocumenthasbeenpublished toensurethataknowledgeablefoundationforDITPRDONusehasbeenestablished.

Page|iii

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

DepartmentofDefenseInformationTechnology PortfolioRepositoryDepartmentoftheNavy (DITPRDON)ProcessGuidance 1.0 Introduction

1.1 Purpose
The purpose of this guidance is to give users of the Department of the Defense (DoD) Information Technology (IT) Portfolio Repository Department of the Navy (DITPRDON) a foundationalunderstandingofhowtoperformbasicfunctionstoregister,transfertoanother portfolio, and archive DON IT systems. Also provided are sources for additional information aboutotherfunctionality. Afterreadingthisdocumentthereaderwillunderstand: TherelationshipbetweenDITPRDON,DADMS,andDoDDITPR, WhatDITPRDONdoesandwhatcompliancerequirementsitsupports, Whatroles,responsibilities,andactivitiesareassignedtovariousstakeholders/users, HowtogainaccesstoDITPRDON, WhatshouldbeenteredintoDITPRDONandwhen, Howtotransferasystemanotherportfolio, HowtoarchiveandunarchiveanITsystem,and WheretogetadditionalinformationforDITPRDONsupportedprocesses. AcronymsandtermsusedinthisguidancearedefinedinAppendixA.

1.2 Scope
This document focuses on processes behind the core DITPRDON functionality and basic lifecycletransactions(e.g.,systemregistration,transfertoanotherportfolio,andarchiving).It does not address the many specialized processes (e.g., certification and accreditation, architecture compliance, business system certification and annual review, etc.) as these are addressed by other policies and guidance that change regularly. These documents may be foundintheReferenceDocumentssectionofDITPRDON(seeFigure1).

Page|1

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

Figure1:ReferenceDocumentsSectioninDITPRDON

1.3 Background
TheDepartmentoftheNavyChiefInformationOfficer(DONCIO)memorandumof18October 2002 designated the DON Application and Database Management System (DADMS) as the AuthoritativeDataSource(ADS)forDONITandNSSapplicationsanddatabaseinventoryandIT Systems Registration. DADMS is a webenabled repository of IT applications and systems and their associated data structures and data exchange formats. It supports the DON in the reductionoflegacyapplicationsandthedevelopmentofstandardapplications,databases,and data elements. It also supports IT interoperability, Information Assurance (IA) assessments, defense business system investment management, and the construction and maintenance of functionalandenterprisearchitectures. As a result of the Y2K Initiative, Congress created the IT Registry in order to collect and maintainarepositoryofallmissioncritical(MC)andmissionessential(ME)systemswithinthe DoD. In 2004, the Government Accountability Office (GAO) provided a report stating that billions of dollars continued to be invested in DoD business systems modernizations with inadequatemanagementoversightandaccountability.TheDoDITPortfolioRepository(DITPR) wasdevelopedasaresultofthisauditforthepurposeofmanagingDoDbusinesssystems.The Page|2

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

scope of DITPR was expanded to include all DoD IT (including NSS) systems in October 2005 whentheITRegistrywasmergedintoDITPR.Asaresult,DITPRwasdesignatedtheADSforall DoD IT systems and, in January 2006, became the official unclassified DoD data source for severalmajorinternalandexternalreportsandprocesses.Theseincludebutarenotlimitedto: DefenseBusinessSystem(DBS)development/modernizationcertificationsunderthe FY2005NationalDefenseAuthorizationAct(NDAA), FederalInformationSecurityManagementAct(FISMA)of2002, DoDwideinventoryofMCandMEsystems, EAuthenticationreportingincompliancewiththeEGovernmentAct, PrivacyImpactAssessment(PIA)compliance, PrivacyAct(PA)compliance, Interoperabilitycertifications, ClingerCohenAct(CCA)compliance, PortfolioManagementinaccordancewithDepartmentofDefenseDirective(DoDD) 8115.01,and RegistryforsystemsunderDepartmentofDefenseInstruction(DoDI)5000.2. InordertomeettheincreasingnumberofreportingrequirementsofDITPRforITsystems,the DON created a separate and distinct system view within DADMS called the DoD IT Portfolio RepositoryDepartment of the Navy (DITPRDON). DITPRDON provides the capability to manageITsystems.Itisnotanindependentprogram;ratheritisthesystemmodulewithin DADMS.DITPRDONisnowthesingle,authoritativesourcefordataregardingDONITsystems, including NSS. It also serves as the source for collecting the required IT system data and uploadingittotheDITPR.Thisprocessisoutlinedinsection3.4ofthisguidancedocument. Figure2illustratesthedistinctmoduleswithinDADMSusedfortheregistrationofeachtypeof ITassetandtherelationshipbetweenthesemodules.

DADMS
Therearefiveprimaryviewsfor ITassetregistrationinDADMS.Eachoperates independentoftheothersbutallareapartoftheoverallDADMSsystem.

EII(Apps)

FAM(Apps)

FDM(DB)

DITPRDON (Systs)

NETWORK (Ntwk/Srvr/Dvc)

EII&FAMviewsareconnected viaappregistrationprocess

Figure2:RelationshipbetweenDADMSModules

Page|3

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

1.4 DITPRDONFunctionality
DITPRDONisthesystemmodulewithinDADMS.ItcontainstheDONsauthoritativeinventory ofITsystems.DITPRDONisaccessibletoDONusersviatheInternet,andprovidesseniorDON decision makers with the context and key information to support IT investment decisions. DITPRDONalsoprovidesconsistentautomatedprocessesacrosstheDepartmenttomeetboth internalandexternalcompliancereportingrequirementsassociatedwith: BusinessSystemCertificationProcessandannualreportstoCongressrequired byTitle10UnitedStatesCode(USC)2222(g); InformationAssurancemanagementprocessandannualreportstoCongressin accordancewiththeFederalInformationSecurityManagementAct(FISMA)of 2002; DoDwideinventoryofMCandMEsystemsrequiredby10USC2223(a)(5); EAuthentication Report, per Office of Management and Budget (OMB) memorandum M0404, December 16, 2003, EAuthentication Guidance for FederalAgencies,implementingSection203oftheEGovernmentActof2002, (44USCChapter36); Privacy Impact Assessment (PIA) compliance information per OMB Memorandum September 26, 2003, "Guidance for Implementing the Privacy ProvisionsoftheEGovernmentActof2002,II.C.3.a.ii.; ThePrivacyActof1974; InteroperabilitycertificationsrequiredbyDODI4630.8,andCJCSI6212.01E; ITportfoliomanagement,perDODD8115.01forallMissionAreas; ClingerCohenActregistrationperDODI5000.2,E.4.2.4.1; DONEnterpriseArchitecture(EA);and IT Budget information in Naval Information Technology Exhibits/Standard Reporting(NITE/STAR)memo. DITPRDON has many features that support lifecycle and compliance requirements for IT systems. However, this guidance document addresses only the basic IT asset management processes (e.g., registration, transfer, and archiving) that fall within the system overview functionality.TheotherDITPRDONfeaturesdescribedbelow(items2,3,and4)arenotinthe scope of this document. Guidance, process, and policy documents for those out of scope featuresmaybefoundintheReferenceDocumentssectionofDITPRDON(seeFigure1). 1. SystemOverviewDITPRDONcontainsfoundationalinformationnecessarytosupport all major IT management processes such as: system name, acronym, description, approval authority, points of contact (POC), etc. DITPRDON also supports the DON EnterpriseArchitectureprocess. 2. System Compliance DITPRDON is a critical tool used to enforce best practices and standard processes to help the Department satisfy compliance and internal/external reportingrequirements.Thisincludesregularlyscheduledreportsdrivenbylegislativeor regulatorymandates,annualreportsrequiredbyotherfederaldepartments,andadhoc reports.

Page|4

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

3. Business System Investment Management DITPRDON includes functionality to support investment management requirements for IT defense business systems (DBS) prescribed by the 2005 NDAA. This functionality includes specialized documentation generation and workflow to track documents submitted through the Business Mission Area (BMA) Investment Review Board (IRB) and the Defense Business Systems Management Committee (DBSMC) for certification of architecture compliance and approvaltoobligatefunds. 4. Business Enterprise Architecture (BEA) Compliance After each major release of the DoDBEA,keyarchitectureproducts/views(i.e.,operationalactivities,systemfunctions, process steps, and business capabilities) are incorporated into DITPRDON. This information is used to support BEA compliance assertions and portfolio management activitieswithintheBMA. Figure3belowsummarizesthesefeatures.
FunctionalInformation Systemname,acronym,description,POCs,lifecycle data DONEnterpriseArchitecture

SystemOverview

SystemCompliance

Generatereportsforinternalandexternal compliancereporting FISMA,PIA/PA,Interoperability,ETP,PKI,etc.

BusinessSystem Management BusinessEnterprise Architecture(BEA) Compliance

RequirementsforDBSIAWFY05NDAA CertificationsandAnnualReviewsofdev/mod funds

SupportsBEAcomplianceassertionsforDBS

Figure3:SystemInformationCategories

Page|5

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

2.0 DITPRDONAdministration
This section provides guidance on the administrative tasks associated with DITPRDON. It defines thevarious roles, responsibilities, and activities of DITPRDON stakeholders and users andexplainshowtoregisterforaDITPRDONaccount.

2.1 RolesandResponsibilities
To ensure that users have a legitimate need to use DITPRDON before granting them access, those requesting access to DITPRDON must have their request endorsed by their supervisor/sponsor (military or civilian (Mil/Civ)) prior to submission. All administrative roles andresponsibilitiesareoutlinedinTable1below.
Table1:AdministrativeRoles&Responsibilities

Role AccountSponsor (Mil/Civ)

Activities Confirmsneedforaccessbyindividual(s)requestingaDITPRDON account NOTE:AccountSponsordoesnotrequireaDADMS/DITPRDON account Appliestheappropriatepermissions(e.g.,view,edit,add)toan approvedDITPRDONaccount NOTE:ServiceAdministratordoesrequireaDADMS/DITPRDON account AssiststheServiceAdministratorinapprovingandapplyingthe appropriatepermissions(e.g.,view,edit,add)toanapproved DITPRDONaccount NOTE:AssistantServiceAdministratordoesrequireDADMS/DITPR DONaccount

Service Administrator (Mil/Civ)

AssistantService Administrator (Mil/Civ/Contractor)

ToprovidesufficientcontrolsandprotectionfortheinformationcontainedinDITPRDON,the DONDeputyCIO(NavyandMarineCorps)andtheDONAssistantforAdministration(DON/AA) must identify a Service Administrator (military or civilian) to serve as the primary liaison between their respective Service or office and the DADMS/DITPRDON Program Office. Individuals assigned as primary liaison also fulfill other administrative responsibilities, as outlined above and as identified by the DADMS Program Manager. Each DDCIO and DON/AA must provide the name of their Service Administrator to the DADMS/DITPRDON Program Manager and to the DADMS Help Desk by September 1 ofeachyear or within 30 days if the positionbecomesvacant. PermissionsandaccessinDITPRDONarebasedontheusertypeandtheroles,responsibilities, andspecificactivitiestheyarerequiredtoperform.TheseareoutlinedinTable2below.

Page|6

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

Table2:UserBasedRoles&Responsibilities

UserType Program Manager/ SystemOwner

Roles&Responsibilities Responsiblefortheentry (i.e.,addition)and maintenanceofsystem records

Activities Registersandupdatessystem information Coordinatessubmissionofnewand updatedsystemdatawiththe owningMarineCorpsMajor SubordinateCommandorNavy EchelonIICommandInformation Officer(IO)andtheappropriate FunctionalAreaManager(FAM) Reviews/updatessystemdataona regularbasisandinaccordancewith allDONsystemreviewpolicies EnsuressystemisidentifiedintheIT budgetinaccordancewiththe FinancialManagementRegulation, Volume2B,Chapter18andthatthe applicableBudgetInitiativeNumber (BIN)orBINExceptionCodeis recordedintheDITPRDONrecord UpdatestheFAMtaxonomyas necessarybaseduponchangesto thefunctionalareaaswellasinputs receivedfromMarineCorpsMajor SubordinateCommand/Navy EchelonIIandbelowCommandIOs Reviewsallsystemswithintheir functionalareafordataaccuracyon aregularbasisandinaccordance withallDONsystemreviewpolicies ProvidesreportstoProgram Managers/SystemOwnerson necessarychanges/updatesneeded tomaintaincompleteandaccurate systemrecords EnsuresallIT(includingNSS) systemsregisteredinDITPRDON areidentifiedintheITbudgetin accordancewiththeFinancial ManagementRegulation,Volume 2B,Chapter18andthatthe applicableBINorBINException Codeisrecordedineachsystems DITPRDONrecord

FunctionalArea Manager(FAM)

Providesfunctionaloversight fortheportfolioconsistent withDoD,DONandASN strategicgoalsandobjectives Establishesacompleteand accurateFAMtaxonomyto whichsystemswillbealigned EnsuresallDITPRDON entriesfortheirfunctional areaarecompleteand accurate

Page|7

UNCLASSIFIED

DITPRDONProcessGuidance UserType MarineCorps Major Subordinate Commandor NavyEchelonII CommandIOIT Registration PointofContact

UNCLASSIFIED
Activities

28November2011

Roles&Responsibilities

Ensuresthatnewsystemsare enteredcorrectlyand completely EnsuresthatallMC,MEand MSsystemsunderthe commandsauspiceshave beenregisteredinDITPR DONinaccordancewiththe systemregistration requirementsperthis guidance EnsuresallDDCIOcompliance andreportingrequirements havebeenmet

DDCIO(Navy andMarine Corps)and DON/AA

ServesastheprimaryPOCfor allsystemsunderhis/her purview o Directsalldatacalls, communications,etc. regardingsystems undertheirpurview throughhis/her respectivechainof command EnsuresServicedatais correctandcompletein accordancewiththesystem registrationrequirementsper thisguidance EnsuresallDONcompliance andreportingrequirements havebeenmet

Reviewsallsystemsunderthe commandspurviewonaregular basisandinaccordancewithall DONsystemreviewpolicies ProvidesreportstoProgram Managers/SystemOwnerson necessarychanges/updatesneeded tomaintaincompleteandaccurate systemrecords EnsuresallIT(includingNSS) systemsregisteredinDITPRDON areidentifiedintheITbudgetin accordancewiththeFinancial ManagementRegulation,Volume 2B,Chapter18andthatthe applicableBINorBINException Codeisrecordedineachsystems DITPRDONrecord Regularlyreviewsanduploadsthe latestDITPRDONsystemdatato theDITPRinaccordancewiththe requirementsaslaidoutinthis guidance ReportsannuallytoDONCIO,by memorandum,thestatusof registrationofallMC,MEand MissionSupport(MS)systems underhis/herpurviewinDITPR DONandcertifiesthatinformation providedthereinisaccurateand complete o Thisrequirementisoutlinedin theannualDONITFiscalPolicy Guidance o Theformatofthisannual certificationshallbedefinedby DONCIOeachyear.Caveatsto thecertificationandcorrective plansofactionwillbeincluded inaPlanofActionand Milestonesforthose certificationitemsnotcomplete Reviews allsystemsunderhis/her

Page|8

UNCLASSIFIED

DITPRDONProcessGuidance UserType

UNCLASSIFIED

28November2011

Roles&Responsibilities

Activities auspicesonaregularbasisandin accordancewithallDONsystem reviewpolicies ProvidesreportstotheProgram Managers/SystemOwnerson necessarychanges/updatesneeded tomaintaincompleteandaccurate systemrecords PromulgatesDITPRDON registrationguidance.Updatesas necessary CertifiestotheDoDCIOeachyear thattheDITPRDONdataas submittedtotheDITPRisaccurate andcomplete Reviewsallsystemsinaccordance withallDONsystemreviewpolicies

DONCIO

EnsuresallOfficeofthe SecretaryofDefense(OSD) complianceandreporting requirementshavebeenmet

2.2 AccountRequestandAccessAuthorizationProcess
DITPRDONaccountrequestandaccessauthorizationisatwostepprocess.First,therequester must obtain a DADMS account, which provides read access to DITPRDON. Once a DADMS account has been established, specialized privileges (e.g., add, edit, etc.) for DITPRDON mayberequested.Thesetwostepsaresummarizedbelow.NOTE:DADMSisaPublicKey(PK) enabled web site. Users requesting access must have a valid DoDissued Public Key Infrastructure(PKI)certificatetoaccesstheDADMSwebsite. Step1. CompleteandSubmitOnlineDADMS(includingDITPRDON)AccessRequest a. TheDADMSNewUserRequestformmaybefoundathttps://www.dadms.navy.mil. OntheleftpaneloftheDADMSHomePage,clickDADMSACCESSREQUEST.The NewUserRequestformappears.Ensureallrequireddatafieldsarefilledout.All users, both government and contractor, must provide contact information of a government employee who will serve as account sponsor and will approve the usersrequestforaccesstothesystem.Thegovernmentsponsorisnotrequiredto holdanactiveDADMSaccount.OncetheNewUserRequestformiscompleteand hasbeensubmitted(viatheSubmitbuttonatbottomofpage),theDADMSHelp Deskwillsendanemailtotheaccountsponsorrequestingapprovaloftheaccount request. NOTE: All contractors must download, fill out, and forward to their account sponsor a signed DADMS NonDisclosure Agreement (NDA). The account sponsormustthensignthesameDADMSNDAandsenditasanattachment,along withtheirapprovalemail,totheDADMSHelpDesk.AssoonastheDADMSHelp Deskreceivestheapprovalemailfromtheaccountsponsor,theDADMSaccount requestwillbeprocessedwithintwobusinessdays.ThereisaHELPbuttononthe

Page|9

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

topoftheformforonlineassistance,ortheDADMSHelpDeskmaybecontacted byemailatDADMS@att.comorbyphoneat(703)5065220. Step2. RequestAdditionalDITPRDONPermissions a. All new user accounts are established as Read Only in all views of DADMS, including DITPRDON. To obtain edit privileges in DITPRDON, all users must submitarequestthroughtheproperchainofcommandtotheirrespectiveDITPR DONServiceAdministrator. i. Navy:AlluserpermissionrequestsmustbesubmittedviatheusersEchelon I/IICommandInformationOfficer(IO)office. 1. Echelon I FAM users must submit permission requests via their lead FAMPOC. 2. EchelonIIandbelowFAMusersmustsubmittheirpermissionrequests throughtheirEchelonI/IICommandIOoffice. ii. MarineCorps:Alluserpermissionrequestsmustbesubmittedviatheirlead FAMPOC. iii. SECNAV: All user permission requests must be submitted directly to the ServiceAdministrator.

3.0 GeneralGuidelinesforUsage
ThissectionprovidesguidanceonthecorefunctionsinDITPRDON.Thefollowingsubjectsare discussedinthissection: Whentoregisterasystem; WhatmustberegisteredinDITPRDON; HowtotransferasystemtoanotherEchelonII,FAM,Service,etc; HowtouploadaDITPRDONrecordtoDITPR;and HowtoarchiveandunarchiveasystemrecordinDITPRDON.

3.1 WhentoRegisteraSystem
All systems should be entered into DITPRDON at the time the program is established. For acquisitioncategory(ACAT)IIVprograms,therearethreeprimarysystemcases:nonbusiness systems,businesssystems,andanurgentoperationalneedsystem.Theregistrationpointfor nonbusiness systems, for which the Joint Capability Integration and Development System (JCIDS)processisused,generallyoccurswhenthedesignatedoversightbodyhasapprovedan Initial Capabilities Document (ICD). The registration point for business systems, for which the Business Capability Lifecycle (BCL)process is used, occurs at approval of the business case or the appropriate decision authority has approved the program for implementation. System registrationmayalsooccurwhenaJointUrgentOperationalNeedisapprovedforajointrapid acquisitionthroughtheJCIDSprocessorwhentheServiceapprovesarapidacquisitionviatheir ownrapidacquisitionprocess.

Page|10

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

AllotherITsystemsandacquisitionprograms(i.e.,nonACATprograms),asdefinedintheDoD FinancialManagementRegulation(FMR)Volume2B,Chapter18,June2007,willbereportedin DITPRDON when funding for the system is obligated (including operations and maintenance anddefenseworkingcapitalfundmoney).

3.2 WhatMustbeRegisteredinDITPRDON
To ensure there is a complete and accurate DON inventory of IT systems (including NSS), all afloatandashoreDONITsystems,initiativesthatincludeITsystems,systemsofsystems(SoS), andfamilyofsystems(FoS)mustberegisteredinDITPRDONregardlessofcostorfundingtype (e.g.,procurement,modernization,operationsandmaintenance,workingcapital).ITprograms (i.e., SoS, FoS, and initiatives) must be broken down into their subsystems; each subsystem mustberegisteredinDITPRDONinadditiontotheparentSoS,FoS,orinitiative. DoD policies and doctrine (e.g., DoDD 8500.01E, the JP102, and the CNSS 4009) contain different definitions for IT systems and applications. To ensure consistency in registration and reporting,thefollowingdefinitionsforsystemandapplicationwillbeusedtodeterminewhat shouldbeenteredintoDITPRDONandsubsequentlyintheEchelonII/FAMmodulesinDADMS: A system is defined as any solution that requires a combination of two or more interacting, interdependent, and/or interoperable hardware, software, and/or firmwaretosatisfyarequirementorcapability. Anapplicationisdefinedasanysoftwareapplicationthatusesanexistingoperating system software program to provide the user with a specific capability or function thatisindependentofotherapplications.Ifitisdependentonotherapplicationsit becomesasystem.

IfanITassetmeetsthedefinitionforsystem,itshouldberegisteredinDITPRDON.Ifit meetsthedefinitionforapplication,itshouldberegisteredassuchintheEchelonII/FAM modulesinDADMS(seeFigure2). ProceduresforenteringapplicationsintheEchelonII/FAMmodulesinDADMSarenotcovered in this guidance. This information may be found within the Reference Documents section of DADMS,whichisaccessiblefromtheDADMSMainMenu(seeFigure4).ADADMSaccountis requiredtoaccessthisinformation.

Page|11

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

Figure4:ReferenceDocumentsSectioninDADMS

3.2.1

EntryCriteria

If an IT asset meets the system definition above and satisfies the criteria below, it shall be registeredinDITPRDON. HasundergoneorisrequiredtoundergoIAsecurityaccreditation(e.g.,DIACAP,etc.)per DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process November28,2007,Attachment1toEnclosure3,TableE3.A1.T1. o NOTE:StandalonesystemsnotconnectedtoanetworkmustundergoIAsecurity accreditationandbeenteredinDITPRDONperChairmanoftheJointChiefsof StaffManual(CJCSM)6510.01,OperationoftheJointCapabilitiesIntegrationand Development System (JCIDS) May 11, 2005, and DoDI 8500.2, Information AssuranceImplementationFebruary6,2003. IsdesignatedasPlatformIT(PIT)inaccordancewiththeDONCIOmemorandum0210, IAPolicyUpdateforPlatformITpolicy.

Page|12

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

IsaDBSasdefinedbyTitle10USCSec2222(j)(2)orhasamodernizationapprovedby theDBSMC. HasbeendesignatedasMCorMEsystemperTitle10USC2223(a)(5). Is a MS IT system (required by the 20072008 DITPR and SIPRNET IT Registration GuidanceAugust10,2009,AppendixC,ParagraphA.3). Is a MC or ME system required to undergo Title 40 (formerly CCA) (required per DoDI 5000.02, Operation of the Defense AcquisitionSystem December 8, 2008, Enclosure 5, Table8). IscategorizedasaNSS,orhasbeenassignedaMissionAssuranceCategory(MAC)level, orhasbeendesignatedasaMajorAutomationInformationSystem(MAIS)(requiredper the20072008DITPRandSIPRNETITRegistrationGuidanceAugust10,2009,Appendix C,ParagraphA.4).

3.2.2

RegistrationGuidelines

No data shall be entered into DITPRDON that would result in the disclosure of classified information. The classification level of information about IT systems is determined by the MarineCorpsMajorSubordinateCommandorNavyEchelonIICommand.ItisDONpolicythat allsystemsincludingNSSwillberegisteredonlyonceineitherDITPRDONortheDoDSIPRNET ITRegistrywiththefollowingrestrictionsandexceptions: Systems registered in DITPRDON may be unclassified, sensitive unclassified, CONFIDENTIAL, or SECRET. However, registration data for all systems registered in DITPRDONshallonlyincludeunclassifiedorsensitiveunclassifiedinformation. Systems registered in the DoD SIPRNET IT Registry may be unclassified, sensitive unclassified, CONFIDENTIAL, or SECRET. However, registration data for all systems registered in the DoD SIPRNET IT Registry shall only include unclassified, sensitive unclassified,CONFIDENTIALorSECRETinformation. Sensitive Compartmented Information (SCI) and SpecialAccess Program (SAP) systems willberegisteredinaccordancewithIntelligenceCommunityregistrationrequirements. In the event a systems registration data is collateral TOP SECRET, contact the Marine CorpsMajorSubordinateCommandorNavyEchelonIICommandIOofficeforguidance.

ThefollowingadditionalguidelinesandexceptionsapplywhenregisteringsystemsinDITPRDON: MajorCommandDesignation: TheMarineCorpsMajorSubordinateCommandorNavyEchelonIICommandthatisthe sourceoftherequirementforthesystemshouldbeenteredastheMajorCommandin DITPRDON. Exceptionstothisruleincludebutarenotlimitedtothefollowingsituations: o AnExecutiveAgent(EA)hasbeennamedforthesystemotherthanthesourceof therequirementforthesystem.Inthiscase,theEAshallberesponsibleforthe

Page|13

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

registrationofandmaintenanceofthesystemrecordandwillbeenteredasthe MajorCommandinDITPRDON. o Aseparateagreementhasbeenmade(e.g.,MemorandumofAgreement(MOA)) betweenthesourceoftherequirementforthesystemandasecondparty MarineCorpsMajorSubordinateCommandorNavyEchelonIICommand,stating thatthesecondpartycommandshallberesponsiblefortheregistrationofand maintenanceofthesystemrecordandwillbeenteredastheMajorCommandin DITPRDON. JointSystemRegistration: A joint system is any system used by two or more Military Departments (MilDeps) and/or Defense Agencies. Joint systems are those that have been deployed/implemented under a single IA security accreditation and Title 40 (formerly CCA) confirmation (as applicable) without subsequent modification at any operating DefenseAgencyorMilDep. MarineCorpsMajorSubordinateCommandandNavyEchelonIICommandswillregister theirdeployment/implementationofjointsystemsonlyincaseswheretheyarethe designatedEAofthejointsysteminordertopreventduplicativereportinginDoD DITPR. VariantsofJointSystems: o All variants of joint systems used by the Navy and Marine Corps will be registeredinDITPRDON.Variantsareconsideredtoexistwhen: The Marine Corps Major Subordinate Command or Navy Echelon II Commandexecutesitsownfundingtomodifyaformalreleaseorversion ofthejointsystemtomeetitsuniquerequirements;or Ratherthanimplementanewformalreleaseorversionofajointsystem, the Marine Corps Major Subordinate Command or Navy Echelon II Commanddecidestoretainaformerversion. All variants of joint systems will be uniquely identified by system name andsystemacronym: The systemname will include both the parent system name and theMarineCorpsMajorSubordinateCommandorNavyEchelonII Commandname. Thesystemacronymwillincludeboththeparentsystemacronym and the Marine Corps Major Subordinate Command or Navy EchelonIICommandplainlanguageaddress(PLA). SeparateIAsecurityaccreditationofavariantisrequired. AnintradepartmentalsystemisanysystemusedbytwoormoreMarineCorpsMajor SubordinateCommandsand/orNavyEchelonIICommandswithintheDONonly.These aresystemsthathavebeendeployed/implementedunderasingleIAsecurity accreditationandTitle40(formerlyCCA)confirmation(asapplicable)without

IntraDepartmentalSystemRegistration:

Page|14

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

subsequentmodificationatanyoperatingMarineCorpsMajorSubordinateCommand orNavyEchelonIICommand. MarineCorpsMajorSubordinateCommandsandNavyEchelonIICommandswill registertheirdeployment/implementationofintradepartmentalsystemsonlyincases wheretheyarethedesignatedEAoftheintradepartmentalsysteminordertoprevent duplicativereportinginDoDDITPR. VariantsofIntraDepartmentalSystems: o All variants of intradepartmental systems used by Marine Corps Major Subordinate Commands and Navy Echelon II Commands will be registered in DITPRDON.Variantsareconsideredtoexistwhen: The Marine Corps Major Subordinate Command or Navy Echelon II Commandexecutesitsownfundingtomodifyaformalreleaseorversion oftheintradepartmentalsystemtomeetitsuniquerequirements;or Rather than implement a new formal release or version of an intra departmentalsystem,theMarineCorpsMajorSubordinateCommandor NavyEchelonIICommanddecidestoretainaformerversion. All variants of intradepartmental systems will be uniquely identified by systemnameandsystemacronym: The systemname will include both the parent system name and theMarineCorpsMajorSubordinateCommandorNavyEchelonII Commandname. Thesystemacronymwillincludeboththeparentsystemacronym and the Marine Corps Major Subordinate Command or Navy EchelonIICommandPLA. SeparateIAsecurityaccreditationofavariantisrequired.

3.3 HowtoTransferOwnershipofaSystem
All system records in DITPRDON are assigned to portfolios within the DON based on system ownershipandthecorefunctionalityofthesystem.EachsystemisassignedtoeithertheNavy or the Marine Corps as the owning Service. System ownership is further broken down by EchelonIIdesignation.EachsysteminDITPRDONisalsoassignedtoaportfolio(i.e.,functional area)basedonitsprimaryfunction.

3.3.1

HowtoTransferaSystemtoAnotherService

UponinitialregistrationinDITPRDON,asystemisassignedtoaService(i.e.,NavyorMarine Corps). NOTE: Secretariat systems (i.e., systems managed by DON/AA) are registered under NavyinDITPRDON.Afterinitialsystemregistration,thisassignmentislockedandcannotbe changedwithinthesystemrecordinDITPRDON.InordertotransferasystemfromoneService to another (e.g., change Service designation in DITPRDON from Navy to Marine Corps), the programmanagermustmanuallycoordinatethesystemtransferwithandreceivewritten(e.g., memorandum or email) concurrence from both DDCIO (Navy) and DDCIO (Marine Corps) to Page|15

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

ensurethatbothServicesareawareofandagreetothetransferofthesystemfromoneService portfoliototheother.AfterconcurrencehasbeenobtainedfrombothDDCIOs,thePMwill: 1. Upload the written concurrence from the current and receiving DDCIOs to the DOC screenoftheDITPRDONsystemrecord. 2. SendthetransferrequestwiththewrittenconcurrenceoftheDDCIOstotheDADMS/ DITPRDONPMforexecutionofthetransfer.

3.3.2HowtoTransferaSystemtoAnotherEchelonII
TheassignmentofaSubOrganization/EchelonIIinDITPRDONmaybechangeddirectlywithin thesystemrecordbytheprogrammanager.PriortotransferringasystemfromoneEchelonII toanother(e.g.,changeEchelonIIfromNAVAIRtoSPAWAR),thePMmustmanuallycoordinate the systemtransfer with and receive written (e.g., memorandum or email) concurrence from boththeEchelonIICommandIOfortheEchelonIIcurrentlylistedintheDITPRDONrecordand from the Echelon II Command IO for the Echelon II the system is being transferred to. After concurrencehasbeenobtainedfrombothEchelonIIs,thePMwill: 1. UploadthewrittenconcurrencefromthecurrentandreceivingEchelonIICommandIOs totheDOCscreenoftheDITPRDONsystemrecord. 2. ChangetheEchelonIIdatafieldontheCOREscreenintheDITPRDONsystemrecord toreflectthenewEchelonII. NOTE: Once the transfer has been made in DITPRDON (i.e., the Echelon II field has been changed), the original owning PM and Echelon II will no longer be able to edit the system record.Anychangestothesystemrecord,includingfurthertransfersofownershipinEchelonII, FAM,etc.,mustbemadebythenewowningEchelonIIorganization.

3.3.3HowtoTransferaSystemtoAnotherFunctionalAreaManager
TheassignmentofaFAMinDITPRDONmaybechangeddirectlywithinthesystemrecordby the PM. Prior to transferring a system from one FAM to another (e.g., change FAM from LogisticstoEnterpriseServices),thePMmustmanuallycoordinatethesystemtransferwithand receivewritten(e.g.,memorandumoremail)concurrencefromboththeFAMcurrentlylistedin theDITPRDONrecordandtheFAMthesystemisbeingtransferredto.Afterconcurrencehasbeen obtainedfrombothFAMs,thePMwill: 1. UploadthewrittenconcurrencefromthecurrentandreceivingFAMstotheDOCscreen oftheDITPRDONsystemrecord. 2. ChangetheFAMdatafieldontheCOREscreenintheDITPRDONsystemrecordto reflectthenewFAM.

3.4 HowtoUploadaDITPRDONRecordtoDITPR
AfterasystemhasbeenenteredintoDITPRDONitwillbeuploadedintotheDITPR,theADSfor DoD systems information. DITPRDON and DITPR data is exchanged daily via a web service

Page|16

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

interfacebetweenthetwosystems.However,systemsregisteredinDITPRDONarenotinitially automatically uploaded to DITPR (i.e., first time upload from DITPRDON to DITPR is not automatic). Title 10 USC Sec 5013 states that the Secretary of the Navy has the authority to equip,train,formulateprograms,etc.,fortheDON.Becauseofthisauthority,theDepartment controlswhatsystemsarereportedtoDITPRandwhentheyarereported. AsystemmustmeettheDITPRDONuploadcriteriaoutlinedbelowinordertobereviewedand markedforuploadtoDITPR.ThedesignatedDDCIO(Navy),DDCIO(MarineCorps),andDON/AA representatives are responsible for reviewing systems that meet upload criteria and marking themforinitialuploadtoDITPR.Thisreviewforuploadprocessshouldoccuronacontinuous basistoensureregularandaccuratereportingofDONsystemdatatoDITPR.

3.4.1

UploadCriteria

InordertomaintainthequalityofDITPRdata,systemsthathavebeenregisteredinDITPRDON buthavenotyetbeenuploadedtoDITPRmustmeetatleastoneofthefollowingtwocriteriain ordertobeflaggedinDITPRDONas"MEETSUPLOADCRITERIA." Criteria1: ThefieldActive/InactiveisActiveand The field DON Record Type is Family of Systems (FoS), System of Systems (SoS),Initiative,orPlatform,SystemorNetwork or Criteria2: ThefieldActive/InactiveisActiveand The DITPRDON entry has been assigned an OSD Budget Identification Number (BIN) or a valid BIN Exception Code. If BIN Exception Code is 9990, the system musthaveaBINExplanationinordertoreceiveMEETSUPLOADCRITERIAflag.

3.4.2

ReviewProcessandSystemUploadtoDITPR

WhetherthesystemhaseverbeenuploadedtoDITPRinthepastdeterminestheprocessthat will be used to upload a record to DITPR. A system must fall into one of the following two categoriesforitsrecordtobeuploadedtoDITPRinthedailyupload: 1. SystemrecordhasneverbeenuploadedtoDITPR: a. SystemrecordhasbeenflaggedasMEETSUPLOADCRITERIA. b. Systemrecordisindividuallyreviewed,authorizedforupload,andmarkedfor export by the designated DDCIO (Navy), DDCIO (Marine Corps), or DON/AA representative. i. NOTE: Service representatives must check the System Core Basic screenofeachsystempriortomarkingitoffforinitialexporttoDITPR.If a system record has a pink bar at the top of the System Core Basic screenindicatingeitherMissingCOREorMissingTriggerdatawithin the system record (see Figure 5), the request to export the system to DITPRwillberejectedbythewebserviceinterfaceschema. Page|17

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

2. SystemrecordalreadyexistsinDITPR(i.e.,previouslyuploadedtoDITPR) a. SomeorallofthesystemrecordhasbeenupdatedinDITPRDONsincethelast dailyexportofdatatoDITPR.Onlythosedatafieldsinthesystemrecordthat havebeenupdatedsincethelastdailyexportwillbeuploadedtoDITPR.This uploadoccursautomaticallyviathewebserviceinterfacebetweenDITPRDON andDITPR(i.e.,nomanualreviewandcheckoffbyreviewerisrequired).

Figure5:MissingDataBarsonCOREScreen

ReviewofsystemsforexporttoDITPRmaytakeplaceatanytime;however,whenthereisa highvisibilityreportcomingdue(e.g.,AnnualFISMAReport),theDONmayimplementahold on marking new systems for initial export to DITPR. The DON will notify the DDCIO (Navy), DDCIO(MarineCorp),andDON/AArepresentativeschargedwithreviewingsystemsforexport withthespecifictimeperiodswhennewsystemscannotbemarkedforexport.

3.5 HowtoArchiveorUnArchiveaDITPRDONRecord
AsystemrecordmayonlybearchivedorunarchivedbythePMortheowningNavyEchelon II/MarineCorpsMajorSubordinateCommandunlessdelegationtodosohasbeenauthorized and duly noted in writing (e.g., memorandum or email). This written authorization should be uploaded to the DOC screen of the system record. For the purposes of this guidance, it is assumedthatthePMwillinitiateallsystemarchivingorunarchiving.

Page|18

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

3.5.1 HowtoArchiveaSystemRecordinDITPRDON
Therearemanyreasonswhyasystemrecordmayneedtobearchived.Table3outlinesthe reasonswhyasystemrecordmaybearchivedinDITPRDON.
Table3:OnlyValidReasonsforSystemArchival

ArchiveReason Retirement

ApplicableConditions Systemfunding(includingallprocurementandsustainment funding)isnolongeravailableand/ortheproject/technologycan nolongerbesupported. Thesystemisterminatedbygovernmentdirection. Thesystemisnolongerconnectedtothenetwork,nolonger requiressecuritycertificationandaccreditation,andisnolongerin use. Recordwasaplaceholderandhasbeenreplacedbyanotherentry. ThesystemwasaddedtoDITPRDONasanewITacquisitionoran ITdevelopmenteffortandthegovernmentdecidedtocancelthe newsystemordevelopmenteffort. o Thiswouldapplytosystemsthatneverreachedthe deploymentstageandwouldthusnotqualifyasretired. RecordwasincorrectlyaddedtoDITPRDONtwice. Thesystemsfunctionalitywassubsumed(ormigrated)into anothersystem.Thefunctionalityitprovidesisnolongerrequired. RecordissomethingthatshouldnthavebeenenteredintoDITPR DONtobeginwith(e.g.,application). Systems/recordshavebeencombinedintoasinglerecord.

Replaced Cancelled

Duplication

EnteredinError

Consolidation ArchivingasystemrecordinDITPRDONisatwostepprocess. Step1: DetermineifProhibitedConditionsExist.Priortoarchiving,ensurenoprohibited conditionsexisttopreventsystemarchivinginDITPRDON.Donotarchivethesystemif: ThesystemstillmeetsANYDITPRDONregistrationrequirement. Thesystemslifecycleenddateisscheduledaftertheplannedsystemarchivedate. ThisinformationisfoundinDITPRDONunderSystemCoreBasicandthenunder theLifecycletab. Thesystemhasanycurrentorplanneddevelopmentormodernization.Thisapplies toallsystemsinallmissionareas.ThisinformationisfoundinDITPRDONunderthe Development/Modernization subsection of the Trigger tab. This section asks

Page|19

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

the question: Current or planned system modernization. If this question is answeredYes,thesystemshouldnotbearchived. ThesystemisaDBSandiscurrentlyintheDoDEnterpriseTransitionPlan(ETP).This informationisfoundinDITPRDONunderSystemComplianceandthenunderthe ETPtab.

Step2: Archive System Record in DITPRDON. The PM will archive the system record in DITPRDON. To archive an active system record in DITPRDON, click the Change Status buttonintheActive/InactivedatafieldontheSystemCoreBasicscreeninthesystem record.IfanyprohibitedconditionsexistthatwillnotallowthePMtoelectronicallyarchive the system, these will be noted on the System Archive screen. Any such item must be correctedbeforethesystemmaybearchived(seeStep1).Iftherearenoprohibitions,the PMwillselectthereasonforarchivingtherecord(Table3)andsubmit.

3.5.2 HowtoUnArchiveaSystemRecordinDITPRDON
SystemrecordsinDITPRDONshouldonlybearchivediftheymeetoneoftheacceptable conditionsforarchivalfromTable3,above.Ifitisdeterminedthatasystemrecordhasbeen incorrectlyarchived(i.e.,archivedinviolationofthebusinessrulesandvalidreasonsfor archival),itmustbeunarchived. TheunarchivalofasystemrecordinDITPRDONisatwostepprocess. Step1: Determine if a Violation of System Archival Has Occurred. Ensure that no prohibited conditions existed at the time of system archival. The system should not have beenarchivedif: ThesystemstillmeetingsANYDITPRDONregistrationrequirement. Thesystemisstillinadevelopmentaloroperationallifecyclephase. Thesystemstillhasanyfundingin thebudgetand/oris obligatinganyfundingfor development,modernization,oroperations.

Step2: UnArchiveSystemRecordinDITPRDON.Ifitisdeterminedthatthesystemisstill inoperationwithfundsbeingexecutedagainstit,thePMwillunarchivethesystemrecord in DITPRDON. To unarchive an inactive system record in DITPRDON, select the Active/InactiveStatusdropdownboxatthetopoftheSystemCoreBasicscreeninthe inactive system record. Change the status from Inactive . to Active Record (see Figure6).

Page|20

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

Figure6:HowtoUnArchiveaSystemRecord

Page|21

UNCLASSIFIED

DITPRDONProcessGuidance

UNCLASSIFIED

28November2011

AppendixA: GlossaryofTermsandAcronyms
Term or Acronym Full Spelling or Definition

AcquisitionCategory (ACAT)

Categoriesestablishedtofacilitatedecentralized decisionmakingand executionandcompliancewithstatutorilyimposedrequirements.TheACAT determinesthelevelofreview,validationauthority,andapplicable procedures.ReferencedprovidesthespecificdefinitionforeachACAT.(CJCSI 3170.01G) AuthoritativeDataSource Anysoftwareapplicationthatusesanexistingoperatingsystemsoftware programtoprovidetheuserwithaspecificcapabilityorfunctionthatis independentofotherapplications.Ifitisdependentonotherapplicationsit becomesasystem. CertificationandAccreditation DepartmentoftheNavyApplicationandDatabaseManagementSystem Aninformation system,otherthananational securitysystem,operatedby, for,oronbehalfoftheDepartmentofDefense,includingfinancialsystems, mixedsystems,financialdatafeedersystems,andinformationtechnologyand informationassuranceinfrastructure,usedtosupportbusinessactivities,such asacquisition,financialmanagement,logistics,strategicplanningand budgeting,installationsandenvironment,andhumanresourcemanagement. (2005NDAASec.3322222(j)(2)) DefenseBusinessSystemsManagementCommittee DepartmentoftheNavyDeputyChiefInformationOfficer TheDoDprocessforidentifying,implementing,validating,certifying,and managingIAcapabilitiesandservices,expressedasIAcontrols,and authorizingtheoperationofDoDISs,includingtestinginaliveenvironment, inaccordancewithstatutory,Federal,andDoDrequirements.(DoDI8510.01) DepartmentofDefenseInformationTechnologyPortfolioRepository DepartmentofDefenseInformationTechnologyPortfolioRepository DepartmentoftheNavy DepartmentofDefense DepartmentoftheNavy Departmentof the NavyChiefInformationOfficer FunctionalAreaManager

ADS Application

C&A DADMS DefenseBusinessSystem (DBS)

DBSMC DDCIO DoDInformation AssuranceCertification andAccreditationProcess (DIACAP) DITPR DITPRDON DoD DON DONCIO FAM

Page|A1

UNCLASSIFIED

DITPRDONProcessGuidance
Term or Acronym

UNCLASSIFIED

28November2011

Full Spelling or Definition

FamilyofSystems(FoS)

Asetofsystemsthatprovidesimilarcapabilitiesthroughdifferentapproaches toachievesimilarorcomplementaryeffects.Forinstance,thewarfightermay needthecapabilitytotrackmovingtargets.TheFoSthatprovidesthis capabilitycouldincludeunmannedormannedaerialvehicleswithappropriate sensors,aspacebasedsensorplatformoraspecialoperationscapability.Each canprovidetheabilitytotrackmovingtargets,butwithdiffering characteristicsofpersistence,accuracy,timeliness,etc.(CJCSI3170.01F) FinancialFeederSystemsaresometimesalsoreferredtoasmixedor secondaryfinancialsystems.Financialfeedersystemsaresystemsthat supportfunctionswithbothfinancialandnonfinancialaspects,suchas logistics,acquisition,andpersonnel.Theyprovidekeyinformationrequiredin financialprocesses.Forafeedersystem,allcommandsmustreportthe percentageofeachfeedersystemthatsupportsfinancialrequirements.(DoD FinancialManagementRegulationVolume2B,Chapter18,June2007) FinancialManagementsystemsperformthefunctionsnecessarytoprocessor supportfinancialmanagementactivities.Thesesystemscollect,process, maintain,transmit,and/orreportdataaboutfinancialeventsorsupporting financialplanningorbudgetingactivities.Thesesystemsmayalsoaccumulate orreportcostinformation,supportpreparationoffinancialtransactionsor financialstatementsortrackfinancialeventsandprovideinformation significanttotheAgencysfinancialmanagement.(DoDFinancialManagement RegulationVolume2B,Chapter18,June2007) ensuringtheiravailability,integrity,authentication,confidentiality,andnon repudiation.Thisincludesprovidingforrestorationofinformationsystemsby incorporatingprotection,detection,andreactioncapabilities.(DoDD8500.1)

FinancialFeederSystems

FinancialManagement Systems

InformationAssurance(IA) Measuresthatprotectanddefendinformationandinformationsystemsby

Initiative

ForDITPRDONpurposes,aninitiativereferstotheITBudgetdefinitionand usage:AllITresourceswillbereportedwithininitiatives.Withtheexception ofDefensebusinesssystems(see180103(G)(2)),initiativescanbesystems, programs,projects,organizations,activitiesorgroupingofsystems....Group ofSystems.WiththeexceptionofDefensebusinesssystems(see180102(G)), initiativescanbegroupingsofsystemsifallthesystemsarewithinthesame MissionArea;managedunderthesameconstruct,andfinancedunderthe sameresourceconstruct(program/project/organization).(DoDFinancial ManagementRegulationVolume2B,Chapter18,June2007) InvestmentReviewBoard

IRB

Page|A2

UNCLASSIFIED

DITPRDONProcessGuidance
Term or Acronym

UNCLASSIFIED

28November2011

Full Spelling or Definition

InformationTechnology (IT)

Anyequipmentorinterconnectedsystemorsubsystemofequipmentthatis usedintheautomaticacquisition,storage,manipulation,management, movement,control,display,switching,interchange,transmissionorreception ofdataorinformationbytheDoDComponent.Forpurposesofthepreceding sentence,equipmentisusedbyaDoDComponentiftheequipmentisusedby theDoDComponentdirectlyorisusedbyacontractorunderacontractwith theDoDComponentthat: E2.1.8.1.Requirestheuseofsuchequipment;or E2.1.8.2.Requirestheuse,toasignificantextent,ofsuchequipment intheperformanceofaserviceorthefurnishingofaproduct.The term"informationtechnology"includescomputers,ancillary equipment,software,firmwareandsimilarprocedures,services (includingsupportservices),andrelatedresources.Notwithstanding theabove,theterm"informationtechnology"doesnotincludeany equipmentthatisacquiredbyaFederalcontractorincidentaltoa Federalcontract.(DoDD8000.1) Connotesactivities,operations,organizations,etc.,inwhichelementsoftwo ormoreMilitaryDepartmentsandparticipate(JointPublication102) MilitaryDepartments Asystemthatmeetsthedefinitionsofinformationsystemandnational securitysystemintheCCA,thelossofwhichwouldcausethestoppageof warfighteroperationsordirectmissionsupportofwarfighteroperations.(The designationofmissioncriticalshallbemadebyaComponentHead,a CombatantCommander,ortheirdesignee.AfinancialmanagementITsystem shallbeconsideredamissioncriticalITsystemasdefinedbytheUnder SecretaryofDefense(Comptroller)(USD(C)).)AMissionCriticalInformation TechnologySystemhasthesamemeaningasaMissionCriticalInformation System.(DoDI5000.2,December8,2008) Asystemthatmeetsthedefinitionofinformationsystemin[theCCA], that theacquiringComponentHeadordesigneedeterminesisbasicandnecessary fortheaccomplishmentoftheorganizationalmission.(Thedesignationof missionessentialshallbemadebyaComponentHead,aCombatant Commander,ortheirdesignee.AfinancialmanagementITsystemshallbe consideredamissionessentialITsystemasdefinedbytheUSD(C).)A MissionEssentialInformationTechnologySystemhasthesamemeaningas aMissionEssentialInformationSystem.(DoDI5000.2,December8,2008) Asystem(asdefinedinthisappendix)thatisneither MissionCriticalnor MissionEssential.

Joint MilDeps MissionCritical(MC) System

MissionEssential(ME) System

MissionSupport(MS) System

Page|A3

UNCLASSIFIED

DITPRDONProcessGuidance
Term or Acronym

UNCLASSIFIED

28November2011

Full Spelling or Definition

NationalSecuritySystem (NSS)

(A)Theterm"nationalsecuritysystem"meansany informationsystem (includinganytelecommunicationssystem)usedoroperatedbyanagencyor byacontractorofanagency,orotherorganizationonbehalfofanagency i)thefunction,operation,oruseofwhich (I)involvesintelligenceactivities; (II)involvescryptologicactivitiesrelatedtonationalsecurity; (III)involvescommandandcontrolofmilitaryforces; (IV)involvesequipmentthatisanintegralpartofaweapon orweaponssystem;or (V)subjecttosubparagraph(B),iscriticaltothedirect fulfillmentofmilitaryor intelligencemissions;or (ii)isprotectedatalltimesbyproceduresestablishedforinformation thathavebeenspecificallyauthorizedundercriteriaestablishedby anExecutiveorderoranActofCongresstobekeptclassifiedinthe interestofnationaldefenseorforeignpolicy. (B)Subparagraph(A)(i)(V)doesnotincludeasystemthatistobeusedfor routineadministrativeandbusinessapplications(includingpayroll,finance, logistics,andpersonnelmanagementapplications).(44USC3542(b)(2)) NationalDefenseAuthorizationAct NavalInformationTechnologyExhibits/StandardReporting;ThisistheDONs authoritativedatasource(ADS)forITbudgetreporting. OfficeoftheSecretaryofDefense REFERS TO: Computer resources, both hardware and software, that are physically part of, dedicated to, or essential in real time to the mission performance of specialpurpose systems. PIT does not include general purposesystems. 2. MAY: a. Resideaboardoronaplatform b. Bestandalone c. HaveaninterconnectiontootherPlatformIT(knownasaPlatform ITtoPlatformITInterconnection) d. HaveaPlatformITInterconnection(seeDoDI8500.1)tootherITthat isnotPlatformIT(e.g.,ageneraluseshipsnetwork,suchasISNS,or anonPlatformITsystem) (DerivedfromDoDD8500.1,ParagraphE2.1.16.4) ProgramManager Portalisaterm,generallysynonymouswithgateway,foraWorldWideWeb sitethatisorproposestobeamajorstartingsiteforuserswhentheyget connectedtotheWeborthatuserstendtovisitasananchorsite.Portals provideawayforenterprisestoprovideaconsistentlookandfeelwithaccess controlandproceduresformultipleapplicationsanddatabases,which otherwisewouldhavebeendifferententitiesaltogether.Examplesofpublic webportalsareAOL,iGoogle,MSNBC,Netvibes,andYahoo!. 1.

NDAA NITE/STAR OSD PlatformInformation Technology(PIT)

PM Portal

Page|A4

UNCLASSIFIED

DITPRDONProcessGuidance
Term or Acronym

UNCLASSIFIED

28November2011

Full Spelling or Definition

StandAloneSystem System

Asystemoperatingindependentlyofandwithoutinterconnectiontoanyother informationsystem.(DoDI8510.01) Anysolutionthatrequiresacombinationoftwoormoreinteracting, interdependent,and/orinteroperablehardware,software,and/orfirmwareto satisfyarequirementorcapability. Asetorarrangementofinterdependentsystemsthatarerelatedorconnected toprovideagivencapability.Thelossofanypartofthesystemcould significantlydegradetheperformanceorcapabilitiesofthewhole.The developmentofaSoSsolutionwillinvolvetradespacebetweenthesystemsas wellaswithinanindividualsystemperformance.(CJCSI3170.01F) Avariantoccurswhen(1)theMarineCorps orNavyEchelonIIcommand executesitsownfundingtomodifyaformalreleaseorversionofthejoint system/initiativetomeetitsuniquerequirements;or(2)ratherthan implementanewformalreleaseorversionofajointsystem/initiative,the MarineCorpsorNavyEchelonIIcommanddecidestoretainaformerversion. VariantsrequireseparateIAsecurityaccreditationandinformationentered shoulduniquelyidentifythesystem. Webservicesprovideastandardmeansofinteroperatingbetweendifferent softwareapplications,runningonavarietyofplatformsand/orframeworks. Webservicesarecharacterizedbytheirgreatinteroperabilityand extensibility,aswellastheirmachineprocessabledescriptionsthankstothe useofXML.Theycanbecombinedinalooselycoupledwayinorderto achievecomplexoperations.Programsprovidingsimpleservicescaninteract witheachotherinordertodeliversophisticatedaddedvalueservices.(World WideWebConsortium,http://www.w3.org/2002/ws/Activity)

SystemofSystems(SoS)

Variant

WebServices

Page|A5

UNCLASSIFIED