Introduction to NCOIC Net-Centric Patterns Mark K Bowler Advanced Tactical Systems Phantom Works The Boeing Company 714.372.1956 [email protected]NIF Architecture Concepts Functional Team Chair October 27, 2010 Approved for Public Release Distribution Unlimited NCOIC-NDIA-MB20101027 Page 1
26
Embed
Introduction to NCOIC Net-Centric Patterns...Introduction to NCOIC Net-Centric Patterns Mark K Bowler Advanced Tactical Systems. Phantom Works . The Boeing Company. 714.372.1956....
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
A global organization focused on an industry neutral approach to NCO adoption:• Use of Open Standards in NCO domains• Net-Centric Architecture Concepts and System Design
Best Practices• Tools for Evaluation and Assessment of Net-Centric
Systems• “Building Blocks” catalog of components & services
compliant with NCOIC recommendations
Members areGlobal Leaders:Academic institutions
Air Traffic Management providers
Service providersConsultingEngineeringLogistics
Defense suppliersAll military servicesMultinational
Government agencies
Human service agencies
IntegratorsCommercial systemsDefense systems
IT firmsCommunicationsData managementHuman-Machine interfaceInformation assurance
Standards bodies
Prescriptive Guidance On How To Build Interoperable,
Network Centric Systems
Page 2
Unity of EffortDifferent Domains, Similar Needs
Functional Teams provide the technical expertise to serve customer domains.The Integrated Project Teams provide operational information from customer domain perspectives.
C3 InteroperabilityIPT
Net Enabled Emergency Response IPT
Aviation IPT MaritimeIPT
BuildingBlocks
Specialized FrameworksNet-Centric
Attributes
SystemsEngineering
and Integration
NCOICInteroperability
Framework
Cyber SecurityIPT
Modeling andSimulation
• Information Assurance• Cloud Computing• Mobile Networking• System Management• Semantic Interoperability• Information, Services, etc.
• Test & Evaluation• Lexicon• Education
& Outreach
SCOPE
NCAT
NIF & Concepts,Principles,Processes,PATTERNS
Net Centric Principles & Attributes
InteroperabilityFrameworks
Net Centric Patterns
Operational Descriptions
Page 3
Where Net-Centric Patterns fit into the NCOIC
BuildingBlocks
SCOPE™& NCAT™
Requirements
Design
Build &Integrate
Test & Eval
Architecture
SCOPE™& NCAT™
NIF™
SpecializedFrameworks
Net-CentricPatterns
Page 4
Why Patterns?
Standards alone do not guarantee interoperability… we also need guidance on architectural approaches, behaviors, design rules, design principles, etc
Often the “best” Standard depends on the mission and performance requirements
In a System-of-Systems, legacy systems cannot be forced to update to newest standard
Does Everyone Understand the Standard the Same Way?
NCOIC Net-Centric Patterns A vehicle for prescriptive recommendations on which standards to use, how to use them, and other
essential guidancePage 5
Page 6
Three Types of Net-Centric Patterns
OPERATIONALPATTERN “A”
OPERATIONALPATTERN “B”
CAPABILITYPATTERN 1
CAPABILITYPATTERN 2
CAPABILITYPATTERN 3
CAPABILITYPATTERN 4
TECHNICALPATTERN
“A”
TECHNICALPATTERN
“B”
TECHNICALPATTERN
“C”
TECHNICALPATTERN
“D”
TECHNICALPATTERN
“E”
TECHNICALPATTERN
“F”
TECHNICALPATTERN
“G”
TECHNICALPATTERN
“X”
TECHNICALPATTERN
“Y”
TECHNICALPATTERN
“Z”
Typical use of NCOIC Resources
Activity NCOIC Resource
Concept Development Specialized Frameworks Operational Patterns
NCOIC Assists Customersin obtaining interoperable solutions:NIF Guides Development of Net-Centric Systems
OperationalAnalysis
ArchitecturalAnalysis
TechnicalAnalysis
OperationalSubject MatterExpert
Enterprise/SystemArchitect
UserCommunity
TechnicalSubject MatterExpert
Plus NIFOverarchingGuidance
Plus SpecializedFrameworks
Integrated ProjectTeams (IPTs) +SCOPE Model
NCOICFocus:Net-CentricInteroperability
NCORequirements
OverarchingGuidance
TechnologyGuidance
Operational(Domain)Patterns
CapabilityPatterns
TechnicalPatterns
Page 20
Page 21
The Problem withInteroperability Standards
Often the “BEST” Standard depends on the Mission– Real-World Condition! Often no “One Size Fits All”
Performance “A”
Performance “B”
Performance“C”
Standard“A”
Standard“B”Standard
“C”
Standard“D”
Standard“E”
Standard“F”
Page 21
Page 22
What is the appropriate level of NetCentricity for a given operational context? May impact selection of Standards!
Not
iona
l Cos
t (or
Ris
k)
Notional Performance
Standard “A”For Technology X
Standard “B”For Technology X
Today’s Range of required performance
Future Range of required performance
Which is the“Best” Standardfor thishypothetical operationalcontext?This example istime-based; manyother perspectives!
The Problem withInteroperability Standards
Page 22
Page 23
“Bad” Standard, or “Bad” System Designs?– Real-World Condition!– In a System-of-Systems, cannot force systems to not use highly-
desirable features when operating independently
Notional Intended Span of Standard
SYSTEM “B” Extension:Added Highly-DesirableFeature
SYSTEM “A” Extension:Added Highly-DesirableRange
% A
-to-B
Inte
rope
rabl
e
100%Interoperable
100%Interoperable
The Problem withInteroperability Standards
Page 23
Page 24
Is Everyone Running the Same Version?– Real-World Condition!– In a System-of-Systems, cannot force Legacy systems to update
to newest standard
ORIGINAL Standard v1.0
% V
ersi
ons
Inte
rope
rabl
e
100% all 3 versionsInteroperable
UPDATED Standard v1.1NEW Standard v2.0: “Backward Compatible”
100% v1.1 & 2.0Interoperable
V1.1 & v2.0
V1.0 & v2.0
The Problem withInteroperability Standards
Page 24
Page 25
Does Everyone Understand the Standard the Same Way?– Real-World Condition! (Not necessarily a bad Standard)– Different Languages; different Cultural backgrounds– Same Standard applied in different Operational Domains,
implemented by designers with different levels of experience, different technical disciplines, different company rules
%In
tero
pera
ble
Interpretation “A” of StandardInterpretation “B” of StandardGUIDED Interpretation of Standard