11
V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

Embed Size (px)

Citation preview

Page 1: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 1

“Patterns 101”

Webex Meeting for Journalists

October 27, 2009

Network-Centric OperationsIndustry Consortium (NCOIC)

Page 2: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 2

How is the NCOIC going to makeDiverse Systems Interoperate?

NCOIC has developed Standard Tools & Procedures(all are free for Public Use)– SCOPE Model to understand Interoperability Needs– NCAT™ Assessments to measure degree of Interoperability– NCOIC Interoperability Framework (NIF™)

& Net-Centric Patterns

A Net-Centric Pattern provides practical expert guidance based on open standards for creating systems with desired net-centric capabilities in order to mitigate specific net-centric interoperability problems

NCOIC Member Companies agree to follow commonNet-Centric Patterns in developing solutions and services– Provide “Building Blocks” that conform to Net-Centric Patterns

for use in constructing Interoperable Systems– Goal is for Governments to use Net-Centric Patterns in Procurements

Page 3: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 3

Pattern Categories

There are three categories of Patterns:

– Operational: Describes standard practices and their interoperability requirements needed to conduct activities (military operations or business objectives) in a given mission context

– Capability: Describes the standard methods and functions needed to support required activities in a mission context from an interoperability perspective as specified in Operational Pattern(s)

– Technical: Describes the technical standards, technologies, and interoperability techniques needed to support required capabilities in a functional context specified in Capability Pattern(s)

Each Category provides Guidance for different Needs(Mission-oriented, Function-oriented, and Technology-oriented)

Each Category provides Guidance for different Needs(Mission-oriented, Function-oriented, and Technology-oriented)

Page 4: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 4

Operational Patterns

Analogy: Objective to Build a House– “Open Standards” would be City Building Codes

• Interoperability with City systems for Electricity, Water, Natural Gas, Sewer, etc.

– “Practical Expert Guidance” would be “How-To” books from experienced contractors

– Requires Construction Capabilities, such as“Fasten Wood” Capability Pattern

Page 5: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 5

Capability Patterns

Analogy: Capability to Fasten Wood for Constructing House Frames– “Open Standards” would be City Building Codes

• “Practical Expert Guidance” would be “How-To” booksfrom experienced contractors

– Supports many different construction missions, such as “Build A House”

– Requires Technical Tools, such as “Hammer” Technical Pattern

Page 6: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 6

Technical Patterns

Analogy: Technology would be “Hammer”– “Open Standards” would be standard types of Hammers

• “Practical Expert Guidance” would be “How-To” booksfrom experienced contractors

– Supports Capabilities such as “Fasten Wood” Capability Pattern

Page 7: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 7

Characteristics ofNet-Centric Patterns

Net-Centric Patterns are:– Prescriptive guidelines for practical use by designers and

implementers that can be tailored and re-used for solving interoperability problems

– Guidance for hardware, software, processes, and procedures

Net-Centric Patterns are not:– Theoretical or philosophical discussions of interoperability

– Rigid specifications for point design solutions

Net-Centric Patterns provide Practical Expert GuidanceNet-Centric Patterns provide Practical Expert Guidancebased on Open Standardsbased on Open Standards

Net-Centric Patterns provide Practical Expert GuidanceNet-Centric Patterns provide Practical Expert Guidancebased on Open Standardsbased on Open Standards

Page 8: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 8

Net-Centric PatternsMust be Practical & Concise

Users of Net-Centric Patterns need practical and concise guidance on how to achieve interoperable solutions!

Users of Net-Centric Patterns need practical and concise guidance on how to achieve interoperable solutions!

NO!

YES!

Page 9: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26

Net-Centric Pattern Hierarchy

Operational Pattern

Capability Pattern

Technical Pattern

supports

requires

also maysupport other

types ofconstruction

supports

requires

also mayrequire othercapabilities

also mayrequire other

tools

also maysupport otherconstruction

activities

Page 10: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26

Patterns Mapping

Pattern Name Step/Term

Capability offered

Problem Solved

Legacy Integration Technical Pattern Short C1 Pb, Pd

Secure Formal Information Exchange Gateway Technical pattern Short C1 Pd, Pe

Land Friendly force Tracking gateway (NFFI Standard Guidance) Technical Pattern Short C2 Pa, Pe

Information Dissemination Shared Database Technical Pattern Short C1, C2 Pa, Pc

Secured Shared Core Network Technical Pattern Short C2 Pd

Data Distribution Technical Pattern Short C1 Pc

Data Replication Technical pattern Short C1

Asset Allocation Planning Pattern Mid C2 Pc

Resource Tracking Information Exchange Pattern Mid C1, C3, C4 Pd, Pf

ISR Collect. & Exploit. Orchestration Capability pattern Mid

C2 Collaboration Capability Pattern Mid

Common Operating picture, Shared Situation Awareness Capability Pattern Mid C1, C3, C4 Pd, Pf

Tactical Service-Oriented Architecture Capability Pattern Mid

Simple Extended Email Service Capabiltiy Pattern Mid

QoS/QoIS Technical Pattern Mid

Information MetaModel Technical Pattern Mid

Information Template Model Technical Pattern Mid

Publish/Subscribe Technical Pattern Mid

Role Based Access Control Mid

Discovery Service Technical Pattern Long C2, C6 Pf

WebServices Technical Pattern Long

Time Services Technical Pattern Long

Page 11: V1.0-2009-10-26 Page 1 “Patterns 101” Webex Meeting for Journalists October 27, 2009 Network-Centric Operations Industry Consortium (NCOIC)

V1.0-2009-10-26Page 11

Net-EnabledFuture

TODAY: Stovepiped Systems, Point-to-Point Networks

Australia

Canada

Denmark

Finland

France

Germany

ItalyIreland

Israel Netherlands

Poland

Romania

Spain

South Korea

Sweden

Switzerland

Turkey

United Kingdom

United States

AustraliaAustralia

CanadaCanada

DenmarkDenmark

FinlandFinland

FranceFrance

GermanyGermany

ItalyItalyIrelandIreland

IsraelIsrael NetherlandsNetherlands

PolandPoland

RomaniaRomania

SpainSpain

South KoreaSouth Korea

SwedenSweden

SwitzerlandSwitzerland

TurkeyTurkey

United KingdomUnited Kingdom

United StatesUnited States