Net-Centric Enterprise Solutions for Interoperability (NESI) provides actionable guidance for acquiring net-centric solutions that meet DoD Network Centric Warfare goals. The concepts in various directives, policies and mandates, such as those included in the References section of this perspective, are the basis of NESI guidance. The NESI Net-Centric Implementation documentation does the following: addresses architecture, design and implementation; provides compliance checklists; and includes a collaboration environment with a repository.
NESI is a body of architectural and engineering knowledge that helps guide the design, implementation, maintenance, evolution, and use of Information Technology (IT) in net-centric solutions for military application. NESI provides specific technical recommendations that a DoD organization can use as references. NESI serves in many areas as a reference set of compliant instantiations of DoD directives, policies and mandates.
NESI is derived from a studied examination of enterprise-level needs and from the collective practical experience of recent and on-going program-level implementations. NESI is based on current and emergent technologies and describes the practical experience of system developers within the context of a minimal top-down technical framework. NESI guidance strives to be consistent with commercial best practices in the area of enterprise computing and IT.
NESI applies to all phases of the acquisition process as defined in DoD Directive 5000.1 [R1164] and DoD Instruction 5000.2; [R1165] NESI provides explicit guidance for implementing net-centricity in new acquisitions and for migrating legacy systems to greater degrees of net-centricity.
NESI subsumes a number of references and directives; in particular, the Air Force C2 Enterprise Technical Reference Architecture (C2ERA) and the Navy Reusable Applications Integration and Development Standards (RAPIDS). Initial authority for NESI is per the Memorandum of Agreement between Commander, Space and Naval Warfare Systems Command (SPAWAR); Navy Program Executive Officer, C4I & Space (now PEO C4I); and the United States Air Force Electronic Systems Center (ESC), dated 22 December 2003, Subject: Cooperation Agreement for Net-Centric Solutions for Interoperability (NESI). The Defense Information Systems Agency (DISA) formally joined the NESI effort in 2006.
|Perspectives||NESI Perspectives describe a topic and encompass related, more specific Perspectives or encapsulate a set of Guidance and Best Practice details, Examples, References, and Glossary entries that pertain to the topic.|
|Guidance||NESI Guidance is in the form of atomic, succinct, absolute and definitive Statements related to one or more Perspectives. Each Guidance Statement is linked to Guidance Details which provide Rationale, relationships with other Guidance or Best Practices, and Evaluation Criteria with one or more Tests, Procedures and Examples which facilitate validation of using the Guidance through observation, measurement or other means. Guidance Statements are intended to be binding in nature, especially if used as part of a Statement of Work (SOW) or performance specification.|
|Best Practices||NESI Best Practices are advisory in nature to assist program or project managers and personnel. Best Practice Details can have all the same parts as NESI Guidance. The use of NESI Best Practices are at the discretion of the program or project manager.|
|Examples||NESI Examples illustrate key aspects of Perspectives, Guidance, or Best Practices.|
|Glossary||NESI Glossary entries provide terms, acronyms, and definitions used in the context of NESI Perspectives, Guidance and Best Practices.|
|References||NESI References identify directives, instructions, books, Web sites, and other sources of information useful for planning or execution.|
NESI Net-Centric Implementation v3.5 is cleared for public release by competent authority in accordance with DoD Directive 5230.9; [R1232] Distribution Statement A: Approved for public release; distribution is unlimited applies to the documentation set. Obtain electronic copies of this document at the NESI Public Site: http://www.nesi.csd.disa.mil.
Note: Due to DoD and Navy Web site reduction efforts, the original NESI Public Site (http://nesipublic.spawar.navy.mil) has transitioned to a DISA site (http://www.nesi.csd.disa.mil).
NESI documentation sometimes refers to specific vendors and their products in the context of examples and lists. However, NESI is vendor-neutral. Mentioning a vendor or product is not intended as an endorsement, nor is a lack of mention intended as a lack of endorsement. Code examples typically use open-source products since NESI is built on the open-source philosophy. NESI accepts inputs from multiple sources so the examples tend to reflect contributor preferences. Any products described in examples are not necessarily the best choice for every circumstance. Users are encouraged to analyze specific project requirements and choose tools accordingly. There is no need to obtain, or ask contractors to obtain, the tools that appear as examples in this guide. Any lists of products or vendors are intended only as examples, not as a list of recommended or mandated options.
Every effort has been made to make NESI documentation as complete and accurate as possible. Even with frequent updates, this documentation may not always immediately reflect the latest technology or guidance. Also, references and links to external material are as accurate as possible; however, they are subject to change or may have additional access requirements such as Public Key Infrastructure (PKI) certificates, Common Access Card (CAC) for user identification, and user account registration.
NESI is an open project that involves the entire development community. Anyone is welcome to contribute comments, corrections, or relevant knowledge to the guides via the following email address: firstname.lastname@example.org.
DoD Directive 5000.01, The Defense Acquisition System, 12 May 2003 (certified current as of 20 November 2007); http://www.dtic.mil/whs/directives/corres/pdf/500001p.pdf.
DoD Instruction 5000.02, Operation of the Defense Acquisition System, 8 December 2008; http://www.dtic.mil/whs/directives/corres/pdf/500002p.pdf.
DoD CIO Global Information Grid Architectural Vision ; Version 1.0, June 2007 [http://www.msco.mil/documents/_7_GIG%20Architectural%20Vision%20-%20200706%20v1.0.pdf]
DoD Net-Centric Data Strategy, DoD Chief Information Officer, 9 May 2003, http://dodcio.defense.gov/Portals/0/Documents/Net-Centric-Data-Strategy-2003-05-092.pdf
CJCSI 3170.01H, Joint Capabilities Integration and Development System, 10 January 2012; http://www.dtic.mil/cjcs_directives/cdata/unlimit/3170_01.pdf.
CJCSI 6212.01F, Net Ready Key Performance Parameter (NR KPP), 21 March 2012; http://www.dtic.mil/cjcs_directives/cdata/unlimit/6212_01.pdf.
Net-Centric Operations and Warfare Reference Model (NCOW RM), v1.1, 17 November 2005.
Note: CJCSI 6212.01E removed the NCOW RM element of the Net-Ready Key Performance Parameter (NR-KPP), integrating the components of the former NCOW RM into other elements of the NR-KPP.
Net-Centric Checklist, V2.1.3, Office of the Assistant Secretary of Defense for Networks and Information Integration/Department of Defense Chief Information Officer, 12 May 2004; http://dodcio.defense.gov/Portals/0/Documents/ISE/NetCentric_Checklist_v2-1-3_.pdf.
Note: User registration and valid DoD PKI Certificate required to access the site.
Net-Centric Attributes List, Office of the Assistant Secretary of Defense for Networks and Information Integration/Department of Defense Chief Information Officer, 2 February 2007; http://dodcio.defense.gov/Portals/0/Documents/NetCentricAttributesOfficial.pdf.
DoD Directive 5230.09, Clearance of DoD Information for Public Release, 22 August 2008
This reference formerly was Chairman, Joint Chiefs of Staff Manual (CJCSM) 3170.01. CJCSI 3170.01G of 1 March 2009 [R1173] cancelled CJCSM 3170.01C which now is available in an online format on Intelink; access may require DoD Public Key Certificate and user registration.
Assistant Secretary of Defense for Networks and Information Integration, Memorandum; Joint Net-Centric Capabilities, 15 July 2003
DoD Net-Centric Services Strategy, DoD CIO, 4 May 2007, http://dodcio.defense.gov/Portals/0/Documents/Services_Strategy.pdf
DoD Directive 8000.01 Management of the Department of Defense Information Enterprise ASD(NII)/DoD CIO; 10 February 2009 [http://www.dtic.mil/whs/directives/corres/pdf/800001p.pdf]
DoD Directive 5144.1 Assistant Secretary of Defense for Networks and Information Integration/DoD Chief Information Officer (ASD(NII)/DoD CIO) ; 2 May 2005 [http://www.dtic.mil/whs/directives/corres/pdf/514401p.pdf]
The Deputy Secretary of Defense, in a memorandum with the subject "Disestablishment of the Assistant Secretary of Defense for Networks and Information Integration (ASD(NII)) and Related Matters" and dated 11 January 2012, deleted the position of ASD(NII). The DoD CIO will assume most ASD(NII) responsibilities and will continue to exercise control over the Director, Defense Information Systems Agency (DISA).