DON CIO Memo - March 26, 2013
This memo delineates records management (RM) policy for electronic information systems (EISs) and records management applications (RMAs) within the Department of the Navy. This policy pertains to new, updated and existing DON EISs and RMAs. In addition to complying with policies, statutes and regulations, effective EIS RM facilitates information discovery and visibility, which improves information sharing.
Joint DON Memo - November 15, 2012
This memo details the significant changes to the requirements for investment review and
certification of defense business systems before appropriated and non-appropriated funds can be obligated. These changes necessitate modifications to the Department of the Navy's business system review process, which supports the Department of Defense's investment review process.
DON CIO Memo - October 1, 2012
The purpose of this memo is to announce the release of the Department of the Navy Enterprise Architecture (DON EA) v4.0.000, which updates DON EA v3.1.000.
DON Guidance - December 8, 2011
The Department of Defense Information Technology Portfolio Repository-Department of the Navy (DITPR-DON) process guidance document provides a comprehensive discussion of core DITPR-DON functionality and basic lifecycle transactions. This information will enable all users to gain the understanding necessary to perform the basic IT asset management functions of registering, transferring and archiving DON IT systems within ...
DON CIO Memo - January 10, 2012
The purpose of this memo is to articulate the Department of the Navy expectations associated with ensuring that an acquisition is consistent with the Global Information Grid policies and architecture, as part of the Title 40/Clinger-Cohen Act confirmation process.
DON CIO Memo - August 5, 2011
The Department of the Navy Chief Information Officer has published the DON Architecture Development Guide (ADG) version 2.0. The ADG, formerly known as the Architecture Product Guide, serves as the overarching guidance for developing and maintaining all architecture models within the department. The ADG incorporates DoD Architecture Framework (DoDAF) v2.0 guidance and provides a number of model examples, a list of ...
DON CIO Memo - July 22, 2011
This memo requests that the Navy and Marine Corps each designate an Information Technology Expenditure Approval Authority (ITEAA). The ITEAA will be responsible to ensure that all information technology projects undertaken by the Navy and Marine Corps are integral parts of rationalized service portfolios, aligned with DON IT goals and conform to the DON and Department of Defense enterprise architectures. No resource ...
DTG 211312Z APR11 - April 21, 2011
This Naval message updates guidance for requesting public key enablement waivers through the Department of Defense Information Technology Portfolio Repository-DON. While the requirement for a waiver for a system that is not public key enabled has not changed, the process was incorporated into the DON Enterprise Architecture compliance assessment.
DON CIO Memo - February 25, 2011
This memo provides guidance on the process to request a waiver for continued use of unsupported Commercial Off-the-Shelf software.
DON CIO Memo - October 14, 2010
This memo clarifies the scope of the Department of the Navy Enterprise Architecture compliance reviews to be performed during FY11. It states that DON EA compliance reviews will only be required for information management/information technology (IM/IT) programs, projects, investments and initiatives that are required to be registered in the DON variant of the Department of Defense Information Technology Portfolio ...
DON CIO Memo - October 14, 2010
This document provides a detailed explanation of the content contained in the Department of the Navy Enterprise Architecture v2.0.000, which was released July 30, 2010. It also provides specific applicability and compliance requirements for each individual artifact contained in DON EA v2.0.000. Enforcement of compliance with DON EA v2.0.000 will commence Oct. 1, 2010. This document is intended for all:
Program Offices ...
DON CIO Memo - October 4, 2010
The purpose of this memo is to announce the release of Department of the Navy Enterprise Architecture (EA) Governance and Configuration Management (CM) Plan. These documents formalize the governance and CM framework and processes, which have been piloted since May 2009.
The DON EA Governance formalizes the roles, responsibilities and standard operating procedures of the DON EA Approval Board, DON EA working group and ...
DTG 242248Z JUL 10 - August 23, 2010
This Naval message directs all DON Mission Critical, Mission Essential and Mission Support information technology systems, including National Security Systems, to be registered in the DoD IT Portfolio Repository-Department of the Navy (DITPR-DON).
DON CIO Memo - May 14, 2010
This memo authorizes DON Deputy Chief Information Officers (Navy and Marine Corps) to provide a Non-Tier Disposition of "review/accepted" and "review/rejected." It also describes a broad spectrum of potential consequences, which would result from a "review/rejected" disposition.
DON CIO Memo - March 30, 2010
This memo is an update to the initial DON DODAF 2.0 Guidance, which was released March 2009. It provides implementation guidance on the DON requirements for compliance with DoDAF v2.0 and its underlying data model.
Enclosure 1 to the memo has been updated as of June 1, 2010.
DON CIO Memo - December 18, 2009
The purpose of this memo is to provide an update to the Department of the Navy Enterprise Architecture (DON EA) Compliance Waiver Request and Approval Process memo, which was originally released Sept. 21, 2009.
The DON EA compliance waiver process has now been automated in the DON variant of the Department of Defense Information Technology Portfolio Repository (DITPR-DON). Effective Dec. 21, 2009, all DON
SECNAVINST 5230.14 - November 11, 2009
This instruction establishes Department of the Navy policies and procedures for the management of information technology and national security systems investments as portfolios across the DON enterprise that focuses on improving DON capabilities and mission outcomes.
It also establishes standard operating procedures that leverage the existing decisional processes of Planning, Programming, Budgeting, and Execution ...
DON CIO Memo - October 26, 2009
The DON IM/IT Investment Review Process Guidance v4.0 of Oct. 1, 2009, supersedes the DON IT Business System Certification and Annual Review Guidance v3.0 of Dec. 19, 2007. It reflects the changes in the Department of Defense certification and annual review requirements for Defense Business Systems (DBSs) promulgated by the DoD IT DBSs Investment Review Process Guidance of Jan. 21, 2009. It also reflects the changes in ...
DON CIO Memo - October 19, 2009
The purpose of this memorandum is to provide guidance on the requirement that all Department of the Navy Information Technology, including National Security System investments, requesting Title 40/Clinger-Cohen Act (Title 40/CCA) Compliance Confirmation, be compliant with the Department of the Navy Enterprise Architecture (DON EA). Assessment of compliance with the DON EA, as part of the Title 40/CCA Compliance ...
DON CIO Memo - October 19, 2009
The purpose of this memorandum is to provide guidance for the formal Department of the Navy Enterprise Architecture (DON EA) waiver request and approval process. Assessment of compliance of Information Technology, including National Security System investments with the DON EA will begin Oct. 1, 2009, as part of three existing processes:
Department of the Navy Information Management/Information Technology Investment ...
DoD Memo - July 27, 2010
This memo rescinds and replaces the Sept. 6, 2007, Department of Defense Information Technology Portfolio Repository (DITPR) and DoD SIPRNET IT Registry Guidance 2007-2008 memo. This memo directs that all IT and National Security Systems must be registered in DITPR.
DON CIO Memo - July 8, 2009
This memorandum builds upon the Department of the Navy Enterprise Architecture Strategy Memo that was released on Feb. 18, 2009. This memo is part of a series of policy documents that articulate the DON strategy for development, management and use of the DON EA. Operational Subject Matter Experts (SMEs) shall comprise Communities of Practice (COP) that will provide and validate operational content within DON Segment
DON CIO Memo - June 29, 2009
This memorandum is part of a series of policy documents that articulate the DON strategy for development, management and use of the DON EA. As stated in this memo, DON CIO, Deputy DON CIO (Navy), Deputy DON CIO (USMC), Assistant Secretary of the Navy for Research, Development and Acquisition -- Chief System Engineer (ASN (RDA) CHSENG) will work together to create the following foundational elements:
DON EA Repository ...
SECNAVINST 5230.15 - April 17, 2009
SECNAVINST 5230.15 mandates that all COTS software in use across the Department of the Navy be vendor supported. DON organizations desiring to continue to use COTS software that is no longer supported must request and receive a waiver to this policy.
DON CIO Memo - January 12, 2009
This memo promulgates policy defining the initial implementation and directs the use of the DON Enterprise Architecture (EA) Hierarchy. The DON EA Hierarchy provides a structure to relate the complete set of activities occurring within the DON. The hierarchy is a key component of the DON EA intended to provide a means for senior leaders to make informed decisions and relate activities and capabilities within the DON to ...
DON CIO Report - October 23, 2008
The DON Enterprise Architecture Federation Pilot Initiative Final Report serves as a guide to support the Department of the Navy’s architecture federation efforts and outlines a methodology for federating architectures across the DoD. The objective of the DON EA Federation Pilot Initiative was to build upon the concepts, objectives and rules developed within the DoD Global Information Grid (GIG) Architecture Federation ...
DON CIO memo - November 4, 2008
This memorandum promulgates policy defining the initial implementation of the Naval Architecture Elements Reference Guide (NAERG) within the Department of the Navy (DON). The memorandum designates the Assistant Secretary of the Navy for Research, Development and Acquisition, Chief Systems Engineer (RDA CHSENG) as the DON organization responsible for NAERG development and maintenance. Additionally, the memorandum ...
10 U.S.C § 332 - January 11, 2008
Defense Business Enterprise Architecture, System Accountability and Conditions for Obligation of Funds for Defense Business System Modernization
OSD/NII/DCIO Memo - June 5, 2008
This strategy outlines how existing architectures will be linked and related to provide a comprehensive view of the Department of Defense enterprise, while allowing for autonomy of individual architectures. The federated approach is one that accommodates the delivery of an organization as large as DoD. Upon clicking the link, select "general public documents" in the "quick links section" of the webpage, then type in the ...
DTG 161552Z MAY 07 - December 17, 2007
This Naval message contains updated Department of the Navy Guidance for program managers of DON Defense Business Systems whose primary mission area and domain is Real Property and Inventory Life Cycle Management.
SECNAVINST 5000.36A - December 17, 2007
This instruction establishes policy for DON applications and data management and describes the responsibilities of the Functional Area Managers, Functional Data Managers and Functional Namespace Coordinators. It also establishes responsibilities for DON IT processes and tools to transform applications and data into net-centric naval capabilities consistent with DoD policy for interoperability and data sharing. ...
SECNAVINST 5000.2C - December 17, 2007
This instruction serves to issue mandatory procedures for Department of the Navy implementation of DoDD 5000.1 and DoDI 5000.2 for major and non-major defense acquisition programs and major and non-major information technology acquisition programs.
DON CIO Memo - August 23, 2010
This charter supports the establishment of DADMS as the authoritative data source for information about DON information technology applications and databases. It establishes the DADMS Configuration Control Board as the body to address and prioritize Navy and Marine Corps requirements for DADMS support.
DON Guidance - October 25, 2011
The Department of Navy Chief Information Officer has developed information technology capital planning and portfolio management processes to assist DON organizations with their responsibilities and initiatives related to selecting, managing and evaluating IT investments to ensure they are compliant with the Government Performance and Results Act and the Clinger-Cohen Act. The Guide for Developing and Using IT Performance ...
December 14, 2012
The Department of the Navy is implementing changes for the annual review of all systems in the DON Business Mission Area (BMA) beginning in FY13.
by Sue Shuryn and Victor Ecarma - July 30, 2012
A critical component to achieving cost savings is transparency of business information technology data, which provides needed insight into, and thus enables more effective management of, the financial and programmatic status of the enterprise. The Department of the Navy Enterprise Architecture (EA) process is essential to providing visibility of such vital information. The DON EA assessment process is cyclical and ...
by Victor Ecarma - October 26, 2011
In May 2011, the Department of the Navy Chief Information Officer released the DON Information Management/Information Technology/Cyberspace Campaign Plan for Fiscal Years 2011-2013. As stated in the campaign plan, "Fiscal realities in the Defense community today and in the anticipated future will not support our continued development and delivery of Information Management (IM), Information Technology (IT) and Information ...
August 8, 2011
In another move to promote effectiveness and efficiencies in the Department of the Navy, the Navy, Marine Corps and DON Secretariat have each designated an Information Technology Expenditure Approval Authority (ITEAA). The ITEAAs are responsible for ensuring that all IT projects undertaken in the Department are integral parts of rationalized portfolios, aligned with DON and Department of Defense enterprise architectures.
by Victor Ecarma - April 29, 2011
The Department of the Navy Enterprise Architecture (EA), with its initial release in July 2009 and version 2.0.000 release in July 2010, continues to support departmental efforts toward effectiveness and efficiency by providing standardized processes, detailed guidance and a central location for DON EA information. By using the DON EA, program managers can avoid duplication of effort and more quickly produce enterprise ...
May 3, 2011
The process for requesting waivers for systems that have not been properly Public Key Enabled (PKE) has been updated. System owners requesting a PKE waiver must now also assert the system's overall compliance with the DON Enterprise Architecture.
by Victor Ecarma & Fumie Wingo - January 21, 2011
The Department of the Navy Enterprise Architecture (DON EA) continues to provide stakeholder value and support DON transformation. Since its initial release in July 2009, the DON EA has been focused on two overarching goals:
by Kimberly N. Brooks - May 17, 2010
The Department of the Navy Chief Information Officer has released updated DON DoD Architecture Framework (DoDAF) v2.0 Implementation Guidance. This guidance clarifies what it means to be compliant at the current time with the requirements of DoDAF v2.0, within the DON.
by Victor Ecarma - February 23, 2010
The DON Enterprise Architecture helps decision makers make informed decisions about investments in new technology and, at the same time, capitalize upon vast existing technology assets. In addition, the DON EA is focused on maintaining alignment between the Department's goals and objectives, and its information management/information technology (IM/IT) investments.
June 22, 2009
DON CIO Team Member Dan Slick recently received the Chief Information Officers Council Leadership Award. He received this honor for evolving the transition from the baseline architecture to a comprehensive and actionable enterprise architecture by providing a fundamental vision for advancing and implementing his agency's enterprise architecture directives, specifically Data Sharing in a Net-Centric Department of Defense. ...
March 12, 2009
The Department of the Navy Chief Information Officer recently signed out the DON Enterprise Architecture (EA) Strategy Memo, a first in a series of memos, to articulate the near-term strategy for continued development of the DON EA. The memo establishes direction to ensure alignment of all DON, Navy and Marine Corps programs and initiatives to the Joint Staff devel
by Victor Ecarma - February 20, 2009
Federally mandated enterprise architectures (EA) are a strategically-based means for the departments of Defense and the Navy (DON) to capitalize on their vast technological assets and make sound decisions about investments in new technology that will support the warfighter.