Multi-level Distributed Discovery and Dissemination (MD3) Capability Net-Centric Pattern
This pattern prescribes an approach for reliable data discovery and dissemination for a system, or systems of systems, working within the challenging and dynamic environment of a mobile ad hoc network (MANET). The MD3 Pattern uses a distributed registry to enable Service Oriented Architecture (SOA) features such as loosely coupled services. It also improves stability and connectivity of the network through associated metadata modeling, processes and platform attributes. NCOIC developed this pattern for any application needing reliable data and service discovery in distribution networks such as disaster response communications and management.
Read the Multi-level Distributed Discovery and Dissemination (MD3) Capability Net-Centric Pattern
Legacy Services Capability Pattern
Service-oriented architecture (SOA) is revolutionizing software application concepts within commercial business. SOA offers lifecycle cost reduction through software reuse. SOA has been mandated for new systems by NATO and the U.S. Department of Defense. SOA is an enabler for net-centricity because it provides the ability for users to get information they need in a timely manner, irrespective of location. This pattern describes methods for upgrading an existing system, or “legacy system,” into a SOA. Five alternative methods are discussed, along with principles that should be considered in selecting one of these methods.
Read the Legacy Services Capability Pattern v1.10
Design Phase Service Integration Capability Pattern
In software integration projects, several recurrent issues appear: What products should be incorporated and how should they be integrated? What legacy solutions are in place? How will the software evolve? Can 1+1 total more than 2 by employing a network-centric solution? Depending on the answers, different integration models and frameworks are available within or across networks. The integration described in this pattern offers advantages and leads naturally to a scalable net-centric solution. The key is taking integration issues into account at inception. All involved stakeholders -- product provider, integrator and customer -- must share a process compliant to this pattern. Goals include minimal dependencies and appropriate service composition and encapsulation based on a shared service-oriented architecture model. This is also known as separation of concerns. This pattern provides a basis for understanding, along with some implementation guidance and best practices from the field.
Read the Design Phase Service Integration Capability Pattern v1.0
Information Dissemination Shared Database Capability (IDSD) Pattern
This pattern provides a solution for how to exchange and disseminate different types of processed information from different sources to multiple information systems using computing and communications services through and from different organizations. It embodies a network service that enables efficient data sharing among multiple stakeholders. This service provides a single data subscription capability and uses a meta-model to indicate where data are available to a data consumer. The shared data can be videos, pictures, raw data and processed data. In such a multi-organization environment, disseminating information over organizations or joint organizations is difficult because the architecture is often not built for such interaction. Security restrictions and existing interoperability are not efficient enough.
This pattern can be used in a joint, multi-domain (ground/air/maritime, organization/multinational and civil/military) architecture model based on dissemination of information (for example, raw data from sensors and processed information) through and from different organizations. This applies to civil and military domains, such as border security, maritime security, homeland security and large-events security.
Read the Information Dissemination Shared Database Capability Pattern v1.0
Land Force Tracking Gateway Network Centric Capability Pattern
This pattern provides guidance to industry on implementation of a gateway to achieve interoperability among disparate systems from civil or military organizations. It is intended for use in a ground context such as police, military, firefighters, non-governmental organizations (NGOs) and emergency responders who need to exchange localization information between or across systems and organizations. (In this document, the term “force” refers to a coherent set of individuals acting as a group for the purpose of an organization, as in a company’s “workforce” or a city’s “police force.”) Users of this pattern include: subject matter experts from organizations involved in homeland security, aviation, medicine, emergency response, NGOs like the Red Cross, and NATO; and system architects not directly involved in developing systems such as land force tracking systems and command, control and communication (C3) systems. This pattern serves as a key element for information sharing among multiple stakeholders and domains and as a good example of public awareness of a proven solution by using the public NCOIC Building Block Repository. This pattern complies with the NCOIC Interoperability Framework NIF Solution Description Reference Manual.
Read the Land Force Tracking Gateway Network Centric Capability Pattern v3.0
All Hazards Alerts and Warnings Capability (AHAW) Pattern
This pattern provides a practical and pragmatic methodology for efficient and timely generation, authentication, or confirmation and distribution of emergency alerts and warnings based on the latest version of the Common Alerting Protocol (CAP) Standard from the Organization for the Advancement of Structured Information Standards (OASIS). It positions the use of CAP in a global system of systems or network of networks using a service-oriented architecture (SOA). The AHAW Pattern SOA will be reused in associated Net-Enabled Emergency Response (NEER) Integrated Project Team (IPT) patterns as appropriate. This pattern seeks to automate the human-to-machine, machine-to-machine. and machine-to-human interchange during emergency communications as effectively as possible given the limitations of heterogeneous Information and Communication Technology (ICT) systems and system-of-systems.
Read the All Hazards Alerts and Warnings Capability Pattern v1.0
Live, Virtual, and Constructive Integrated Middleware Environment (LVC-IME) Capability Pattern
Whether used for training, test and evaluation, or concept development, modeling and simulation often involves the integration of heterogeneous systems, potentially at different security levels. A Live, Virtual, and Constructive Integrated Middleware Environment (LVC-IME) helps reduce the time and risk of performing the integration of these systems, facilitating information sharing among disparate sources of data, by allowing business units to plug their data source into an existing middleware. Middleware environments developed using the guidance in this pattern will handle protocol and data model translation and may provide security and exercise management services.
Read the Live, Virtual and Constructive Integrated Middleware Environment Capability Pattern
Net-Centric Services Interface Capability Pattern
Service-oriented architecture (SOA) interfaces are in a continuous process of change throughout the lifecycle of a system. The velocity of change of an interface is typically highest during the initial design of an application. After release, changes to an interface are ideally zero, but realistically finite due to changing business requirements, competitive pressure and technology obsolescence. This pattern focuses on the interfaces (or the physical connection points between systems) to which the principles of SOA and net-centricity have been applied. These singular connection points make up what the software development community calls an application programming interface (API) and tend to be in a continuous process of change. Modifying an interface after release can be accomplished by changing elements of the interface, adding additional interfaces with differing elements, or both. How this process is administered or governed is essential for the end-consumer to maintain interoperability. This pattern addresses both the technical aspects of the interface change solution and its governance.
Read the Net-Centric Services Interface Capability Pattern
Flight Data Object Dissemination (FDOD) Capability Pattern
A performance-based air traffic management (ATM) system can only be realized using performance-based information management. The sharing of information of the required quality and timeliness in a secure environment is key to the global ATM concept. The current ATM system is fragmented, with aircraft having limited data link capabilities. This pattern describes system-wide information management dedicated to flight data object dissemination, where the ATM network is considered as a series of nodes (including the aircraft and the airspace users), providing or consuming information. The data object scope extends to all information of potential interest to ATM including trajectories, surveillance data and aeronautical information of all types.
Read the Flight Data Object Dissemination (FDOD) Capability Pattern