NCOIC PatternsSemantic CommunitySC_6a70bcfc-1371-11e0-9fb7-3c327a64ea2aBrand NiemannNetwork Centric Operations Industry ConsortiumNCOIC_6a70c008-1371-11e0-9fb7-3c327a64ea2a_6a70c198-1371-11e0-9fb7-3c327a64ea2a_6a70c24c-1371-11e0-9fb7-3c327a64ea2aSpace, Air, Ground, and Maritime (SAGM) Mobile CommunicationEnsure end-to-end multimedia information communication while all source and destination nodes are mobile in heterogeneous wireless networks; in ad hoc, connected, and disconnected modes; in different media; and while roaming._6a70c2f6-1371-11e0-9fb7-3c327a64ea2aOperational 1The Space, Air, Ground, and Maritime (SAGM) Mobile Communication and Networking Operational Pattern corresponds to a global surveillance operation involving air, ground, space, and maritime mobile communications. The problem area is how to ensure end-to-end multimedia information communication while all source and destination nodes are mobile in heterogeneous wireless networks; in ad hoc, connected, and disconnected modes; in different media; and while roaming. In concurrence, communication policy management is needed for compliance. https://www.ncoic.org/apps/group_public/download.php/15963/SAGM%20MCN%20Operational%20Pattern_20100407V1.pdf_6a70c3a0-1371-11e0-9fb7-3c327a64ea2aLegacy ServicesDescribe methods for upgrading an existing system into a Service Oriented Architecture._6a70c468-1371-11e0-9fb7-3c327a64ea2aCapability 1Service Oriented Architecture (SOA) is revolutionizing software application concepts within commercial business. SOA offers life cycle cost reduction promise through software reuse. SOA has been mandated for new systems by the North Atlantic Treaty Organization (NATO) and the United States 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, hereinafter designated as the Legacy System, into a SOA. Five alternative methods are discussed, along with principles that should be considered in selecting one of these methods. https://www.ncoic.org/apps/group_public/download.php/14531/Legacy%20Services%20Capability%20Pattern20091211v1.10.pdf_6a70c526-1371-11e0-9fb7-3c327a64ea2aDesign Phase Service IntegrationProvide a basis for understanding software integration projects along with some implementation guidance and best practices._6a70c5f8-1371-11e0-9fb7-3c327a64ea2aCapability 2In software integration projects, several recurrent issues appear: What are the products to incorporate and how should they be integrated? What legacy solutions are in place? How will the software evolve? Can one plus one total more than two by employing a network-centric solution? Depending on the answers, Different integration models and integration frameworks are available within or across networks. The integration described here 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. https://www.ncoic.org/apps/group_public/download.php/15964/DesignPhaseServiceIntegration_NCPattern_20100407V1_0.pdf_6a70c6ca-1371-11e0-9fb7-3c327a64ea2aInformation Dissemination Shared DatabaseProvide a solution for how to exchange and disseminate processed information of different types from different sources to multiple information systems using computing and communications services through and from different organizations. _6a70c7a6-1371-11e0-9fb7-3c327a64ea2aCapability 3The Information Dissemination Shared Database (IDSD) Pattern provides a solution for how to exchange and disseminate processed information of different types from different sources to multiple information systems using computing and communications services through and from different organizations. The IDSD Pattern embodies a network service that enables efficient data sharing among multiple stakeholders. This service provides a single data subscription capability and uses a metamodel to indicate where data are available to a data consumer. The shared data can be videos, pictures, raw data, and processed data. In such 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, multidomain (ground/air/maritime, organization/multinational, 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. https://www.ncoic.org/apps/group_public/download.php/16581/IDSD%20Pattern.pdf_6a70c896-1371-11e0-9fb7-3c327a64ea2aLand Force Tracking Gateway Network Centric CapabilityProvide guidance to industry on implementation of a gateway to achieve interoperability among disparate systems from civil or military organizations. _6a70c990-1371-11e0-9fb7-3c327a64ea2aCapability 4The Land Force Tracking Gateway Network Centric Capability 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. For the purpose of 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 the following: Subject matter experts (SME) from organizations involved in homeland security, aviation, medical, emergency response, NGOs (for example, Red Cross), and NATO. 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 (NSD-RM). https://www.ncoic.org/apps/group_public/download.php/16616/NCOIC_LandForceTrackingGatewayCapabilPatternV3.0_20100303PubRelComp.pdf_6a70ca8a-1371-11e0-9fb7-3c327a64ea2aAll Hazards Alerts and Warnings_6a70cbde-1371-11e0-9fb7-3c327a64ea2aCapability 5The All Hazards Alerts and Warnings (AHAW) Capability Pattern provides a practical, 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). This pattern positions the use of CAP in a global system of systems, 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 where it is 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. https://www.ncoic.org/apps/group_public/download.php/16801/AHAW_Capability_Pattern_V1%200_20100720.pdf_6a70cd00-1371-11e0-9fb7-3c327a64ea2aDIL Communications Management Describe how a network of connected links with variable link capacity operates to maintain communications service and situational awareness. _6a70ce36-1371-11e0-9fb7-3c327a64ea2aTechnical 1The DIL Communications Management Technical PatternThis pattern describes technology-independent logic for adjusting the capacity of links in a DIL environment. The Pattern describes supporting features required at several protocol layers. https://www.ncoic.org/apps/group_public/download.php/14541/DIL%20Technical%20Pattern20091211V1.0.pdf_6a70cf76-1371-11e0-9fb7-3c327a64ea2aSimple and Extensible Email Services (SEES)Give guidance and to specify baseline performance requirements for a simple and extensible e-mail service._6a70d0b6-1371-11e0-9fb7-3c327a64ea2aTechnical 2Proprietary e-mail systems often define their own parameters, sometimes impeding inter-operability. This pattern aims to give guidance and to specify baseline performance requirements for a simple and extensible e-mail service which is: net centric, robust, secure, seamless and, hence, interoperable. https://www.ncoic.org/apps/group_public/download.php/14139/SEES%20Pattern.pdf_6a70d1f6-1371-11e0-9fb7-3c327a64ea2aSecure Formatted Information Exchange Gateway (SFIEG)Describe a portal between two networks which prevents certain data being released from one network to the other network._6a70d34a-1371-11e0-9fb7-3c327a64ea2aTechnical 3The goal of this pattern is to describe a portal between two networks which prevents certain data being released from one network to the other network. This is done by determining, by inspection, whether any message (rather than packet) is marked in a way indicating that it (or part of it) should not be passed on. Alternatively, a message identified as carrying non-releasable information may be modified by the removal or replacement of the non-releasable information before the message is passed on with the remainder of the information intact. This portal is proposed as a filter. It may be used to allow acceptable data to enter a network, as well as to prevent its exit. Nothing in this pattern prevents the incorporation of two opposite directional filters in the same implementation. This pattern proposes a model based upon message labeling and filtering, as opposed to packet filtering. Several alternative models may be applicable to an environment, with this model focusing on a messaging framework foundation. https://www.ncoic.org/apps/group_public/download.php/15965/SFIEG_Pattern_v%201.2_20100329marked.pdf_6a70d49e-1371-11e0-9fb7-3c327a64ea2aCore Network Access (CNA)Describe an encrypted Virtual Private Network (VPN) architecture providing secure interconnections between moveable Local Area Systems (LAS). _6a70d688-1371-11e0-9fb7-3c327a64ea2aTechnical 4This pattern is part of a set of patterns describing an encrypted Virtual Private Network (VPN) architecture providing secure interconnections between moveable Local Area Systems (LAS). This pattern describes a method for connecting a number of non-fixed access networks to a fixed core network. This pattern provides a clear differentiation between non-fixed specialized access networks and the core network that provides long-range information transport between the access networks. Only authenticated and authorized access networks will be permitted to connect to the core network. https://www.ncoic.org/apps/group_public/download.php/17469/CNA_Pattern_V1_0_20100930.pdf _6a70d804-1371-11e0-9fb7-3c327a64ea2a2010-12-29http://semanticommunity.info/Network_Centricity#NCOIC_PatternsOwenAmburOwen.Ambur@verizon.net