Net-Centric Enterprise Solutions for Interoperability (NESI) is a Cross-Service effort between Air Force (ESC), Navy (PEO C4I), and Defense Information Systems Agency (DISA). NESI provides, for all phases of the acquisition of net-centric solutions, actionable guidance that meets DoD Network-Centric Warfare goals. The guidance in NESI is derived from the higher level, more abstract concepts provided in various directives, policies and mandates such as the Net-Centric Operations and Warfare Reference Model (NCOW RM) and the ASD(NII) Net-Centric Checklist. As currently structured, NESI guidance is captured in documents covering architecture, design and implementation; a compliance checklist; and a collaboration environment (DoD PKI required) that includes a reuse repository and collaboration tools.

The Open Architecture (OA) Initiative is a multi-faceted strategy providing a framework for developing Joint inter operable systems that adapt and exploit open-system design principles and architectures. The strategy calls, in part, for the establishment of OA Computing Environments (OACE) though the dissemination of guidance and standards that describe types of computing systems that will exploit open systems design principles. The introduction of OA into Naval Warfare Systems will be formally instituted through the Open Architecture Enterprise Team (OAET) established by the Assistant Secretary of the Navy for Research, Development, and Acquisition(ASN (RDA)) in August 2004.

The UAS Control Segment (UCS) Architecture is a framework representing the software-intensive capabilities of current and emerging UAS programs in the U.S. Army, Navy, and Air Force inventories. The goal is to develop an architecture, based upon Service Oriented Architecture (SOA) principles, that will be adopted by each of the Services as a common basis for acquiring, integrating, and extending the capabilities of the control systems for UAS. You can find more information at the UCS home page. 

The UCS Architecure operational objectives include support for both UA platform and sensor C2, sensor product availability, and UA status:

• For UAS in Groups 2 through 5 (gross take-off weight more than 20 lbs.)
• In both Service and Joint operations
• Using networked, line of sight (LOS), and beyond line of sight (BLOS) communications

Defence Standard (Def Stan) 23-03 was been produced on behalf of the Ministry of Defence (MOD) by UK Defence Standardization (DStan). It has been developed through the collaborative efforts of the MOD and industry, and builds on the extant Vehicle Systems Integration (VSI) and previous work including the Vehicle Technology Integration Demonstrator (VTID)

The purpose of this Def Stan 23-09 is to enable the MOD to realise the benefits of an open architecture approach to Land platform design and integration, especially in regard to platform infrastructure and the associated Human Machine Interface (HMI) in order to improve operational effectiveness across all Defence Lines of Development (DLOD), reduce integration risks and reduce the cost of ownership across the fleet. This is achieved by mandating and applying the appropriate interface standards.

Specifically this Def Stan specifies the mandatory standards to be used in the design and implementation of Land platform electronic and power infrastructures, mechanical interfaces, HMI and Health & Usage Monitoring System (HUMS), together with requirements for Interface Control Documents (ICDs) and Verification and Validation (V&V).

Def Stan 23-09, section 13, mandates the use of the DDS API and the DDS Interoperability wire protocol (DDS-RTPS / DDSI) for the Interface Definition and Integration.

The following paragraphs, extracted from a letter from QinetiQ, the UK system integrator that lead the VSI Group that authored the Def Stan document explains the reasons behind the selection of DDS. 

A recent activity for this group has been to address the interface between application software and the architecture, for which we surveyed suitable technologies against UK MOD requirements. The OMG DDS family of standards were easily the most appropriate for military land vehicle application due their openness, the OMGs heritage, the commitment by the vendors to address full interoperability, and technical features of DDS. Most important of the technical features considered were the opportunity to simplify application development through adoption of the data centric nature of DDS and the low coupling achieved by using a publish and subscribe communication model.

In order to fully benefit from the use of DDS and to encourage adoption by its contractors, UK MOD has funded the construction of the UK MOD Land Data Model. This data model will encompass data type definitions, quality of service patterns and vehicle type profiles, it will allow the defence community to generate a set of products that interact over DDS based data network in a number of platforms. The Data Model has been endorsed by the VSI Group and a recommendation to the MOD for standardisation through the GVA Office has enabled the data model to undergo its initial deployment in two procurement activities.

The GVA Guide is available in parallel with this Def Stan to add background to the Def Stan and explain best practice to both MOD and Industry stakeholders. It should be read in conjunction with the Def Stan and is available from GPOC.