NESI , or Net-centric Enterprised Solutions for Interoperability is a joint effort between the United States Navy’s Executive Office for C4I and the United States Air Force’s Electronic Systems Center. It provides implementation guidance qui Facilitates the design, development and maintenance, evolution, and use of information systems for the Net-Centric Operations and Warfare ( NCOW ) environment. NESI has also been provided to other Department of Defense (DoD) services and agencies for potential adoption. [1]

NESI includes six parts, each focusing on a specific area of ​​guidance. NESI provides guidance, best practices, and examples for developing Net-Centric software. The overall goal is to provide common, cross-service guidance for the program managers and developers of net-centric solutions. The objective is not to relocate or repeat existing direction, but to plethora of mandated and sometimes contradictory guidance on the topic of net-centric compliance and standards. [1] [2]

NESI documentation

NESI subsumes two now obsolete references; In particular, the Air Force C2 Enterprise Technical Reference Architecture (C2ERA) and the Navy Reusable Applications Integration and Development Standards (RAPIDS). NASI is a leading provider of network-based, multi-threaded, multi-threaded, multi-threaded, multi- For Interoperability (NESI). This guidance will continue to evolve as the direction and understanding of the requirements of net-centricity evolve. NESI will be updated to reflect changes to the guiding documents and new regulations.


The NESI documentation, has six-part information set, is available as PDF files. These parts consist of:

  1. Overview: Introduction and vision
  2. ASD / NII Checklist Guidance: “How to implement” guidance
  3. Migration Guidance: Guidance for maintenance / upgrade activities leading to net-centric systems
  4. Node Design Guidance: Guidance for developing nodes and their infrastructure to support net-centric services
  5. Developer / Technical Guidance: Detailed development guidance
  6. Acquisition Guidance: Incorporating NESI during the acquisition process

Technical guidance

  • Complementary to GIG / NCES infrastructure;
  • Tied to net-centric objectives such as interoperability and flexibility;
  • Vendor, program, platform, and service neutral;
  • Focused on decoupling stovepipe systems into services (eg, SOA and web services).

* Acquisition guidance *

  • Is intended for program managers and DoD contractors;
  • Outlines process and system / product requirements;
  • Relates the steps of the System Acquisition Framework.

Evaluation checklist

In order to evaluate programs / projects, NESI has developed a technical checklist. The current status of a program / project. NESI guidance. The technical checklist is produced from the guidance and provision of NESI guidance. Overall, the checklist will provide a uniform interpretation for all participating organizations. [3]

Component definitions

  • Perspective : provides a way to encapsulate information, based on subject areas.
  • Guidance Detail : provides measurable requirements and rationale for net-centricity and interoperability . [4]
  • Best Practice : provides advice on net-centricity and interoperability.
  • Examples : demonstrate application of guidance and best practices net-centricity and interoperability.
  • References : provides further information about guidance, best practices and examples
  • Glossary : Perspectives, Guidance Details, Best Practice Details and Examples.


  1. ^ Jump up to:a b “Net-Centric Enterprise Solutions for Interoperability (NESI)” (PDF) . Mike Dettman APEO Deputy for Engineering . . Retrieved 21 August 2012 .
  2. Jump up^ “NESI Executive Summary” . . Retrieved 21 August 2012 .
  3. Jump up^ NESI CAC Public Site
  4. Jump up^ “System of systems Interoperability challenges and potential approaches” (PDF) . . Retrieved 21 August 2012 .

Leave a Comment

Your email address will not be published. Required fields are marked *