Vectors in Federal Cloud Computing …
Network-centric Interoperability
(ncoic view)
SATCCI Spring 2009: Workshop for Federal Computing
Stakeholders
23 March 2009
Krishna Sankar(ksankar@cisco.com)
Thanks to Bob Marcus, Terry Morgan, Michael Curtis, Kevin Jackson,
David Lounsbury, Raina Wissing, Ginger Carney, Vish Dixit & Stuart
Charlton, for their encouragement & insights 1

Agenda
 About NCOIC
 Cloud WG
 Patterns …
 Call for action
2

NCOIC™ - Achieving the Vision and
Accomplishing the Mission
Vision
Industry working together with our customers to provide a network
centric environment where all classes of information systems interoperate
by integrating existing and emerging open standards into a common
evolving global framework that employs a common set of principles and
processes.
NCO
System B
System A System C
Mission
Our mission is to facilitate the global realization of Network Centric
Operations. We seek to enable interoperability across the spectrum of
joint, interagency, intergovernmental, and multinational industrial and
commercial operations. NCOIC is global, with membership open to those
who wish to apply the vast potential of network centric technology to the
operational challenges faced by our nations and their citizens.

Definitions …
 Net-Centricity
– The concept of allowing authenticated, trusted and verified
information to be provided and shared among authorized users,
applications and platforms in a seamless fashion without apriori
knowledge of what information is available or needed.
 Network-Centric
– Related to systems and patterns of behavior that are influenced
significantly or enabled by current and emergent networks and
network technologies. Often these center around IP-based
internetworking, but the term is sometimes used to include any type
of enabling network.
 Pattern
– Canonical solution to a problem
4

Meet The NCOIC –
Its Members And Advisors
A global perspective to facilitate
Canada Finland
NCO adoption
Denmark France
Australia
Members from 19 Countries, Experienced
Advisory Council representing 26 key
Ireland Italy
government and civilian stakeholders from
Netherlands
Germany Israel
Australia, France, Germany, Italy, NATO,
Sweden, U.K., & U.S.
Romania South Korea
Spain Sweden
Poland
Turkey United States
Switzerland United Kingdom
An industry neutral perspective to
facilitate NCO adoption
90+ Member Organizations, including leading
IT and Aerospace & Defense companies,
government organizations, non-
governmental organizations and academic
institutions

NCOIC Goal: To Facilitate Implementation
of Network Centric Operations
Members are
 Increase interoperability within and among systems involved in
Global Leaders:
Interagency and Multinational operations
Academic institutions
Aviation Service
 Lower development costs and increase commonality of design in
providers
future systems – tailored standards and best practices
Defense suppliers
All military services

Multinational
Improve application readiness through more rapid fielding of
network centric systems – leverage technical “lessons learned”
Government agencies
Human service agencies
 Reduce systems cost and sustainability through re-use and
Integrators
commonality – facilitate ease of integration, upgrade, and support
Commercial systems
Defense systems
 Reduce Development Risk by identifying the common
IT firms
Communications
components needed for the network centric environment –
Data management
Develop them where none exist
Human-Machine interface
Information assurance

Service providers Improve Application Effectiveness through new, more focused
Consulting
development on domain specific capabilities
Engineering
Logistics
Standards bodies

NCOIC Assists Customers
in obtaining interoperable solutions:
The Role of NCOIC Deliverables
MISSIONS RESULTING
CUSTOMER MISSION SOLUTIONS TO NEEDS
TO ACHIEVE CAPABILITIES
GOALS NEEDS (EXISTING AND FUTURE)
GOALS & SERVICES
Typical Process Steps to Solutions:
End-to-End
1. Analysis of Alternatives
NCO Initiatives Database
Quality
2. Requirements Derivation
of Service
SCOPE Model 3. Requirements Validation
4. Design Synthesis
Network
NCOIC Interoperability Framework
N
(NIF™) Centric
N
B Analysis
C
I
B Tool
F A (NCAT™)
The NCOIC deliverables work
T
together to assist in achieving
5. Design Verification Building
interoperable systems, services,
6. Deployment Blocks
and capabilities
7. Support (BB)
8. Upgrade or Disposal
Modeling & Simulation and Demonstrations of missions, needs, & solutions
Test & Evaluation of solutions & results

NCOIC Cloud Computing Ad-Hoc WG
 Form
 Norm
We are
here
 Storm
Working Towards
critical mass
 Perform
•From customers &
•From members
8

NCOIC Cloud Computing Workgroup Roadmap
(WIP)
 Embrace collaboration
– With Federal Projects and stakeholders aid their effort to leverage
cloud computing across the Federal Government
– With Vendors & standard bodies
 Work with folks on pragmatic cloud projects, as and when
appropriate
 Use Capability and Operational patterns to validate operational
impact of cloud interoperability
 Identify key net-centric operations interoperability requirements
and preferences within identified technical patterns
 Iterate with NCOIC stakeholder companies and government
organizations
 Leverage analysis to drive cloud interoperability
recommendations and best practices

Net-Centric Patterns for Cloud
Computing
 Which interoperability capabilities supported?
– E.g. Search, Intelligent Inference, Semantic Metadata
Representation, Elastic Compute/Storage/Network infrastructure
 Which interoperability challenges are mitigated?
– E.g. Security, SLA management, Declarative Policies, Resource
Monitoring & Usage
 Which structural elements require interoperability
guidance?
– E.g., organizations, policies, physical assets
– Different cloud postures
 What operational & technical standards are
relevant to interoperability problems in the scenario?
10

Net-Centric Cloud Computing Patterns must
guide users away from known problem areas!
Page 11 V1.0-2009-02-24

Definition & Intent of
Net-Centric Patterns
 Patterns are:
– Prescriptive guidelines for practical use by designers and implementers
that can be tailored and re-used for solving interoperability problems
– Sufficiently detailed to facilitate verification of vendor evidence of
conformance to the pattern
– Guidance for Hardware, Software, Processes, and Procedures
(more than just traditional software patterns)
 Patterns are not:
– Intended as theoretical or philosophical discussions of the “nature” of
net-centricity and interoperability approaches, which are best
addressed elsewhere
– Intended as rigid specifications for point design solutions
Page 12 V1.0-2009-02-24

Conditions Change! Need to keep Net-
Centric Patterns Current
Page 13 V1.0-2009-02-24

Net-Centric Pattern Hierarchy
Technical Patterns
A Top-Down
Approach
Capability Pattern A
Operational Pattern
Capability Pattern B
Capability Pattern C
Capability Pattern D
Page 14 V1.0-2009-02-24

Call For Action
Operational Technical
Enterprise/System
Subject Matter Subject Matter
Architect
Expert Expert
User
Community
Operational Architectural Technical
Analysis Analysis Analysis
NCO Technology
Overarching
Guidance
Requirements Guidance
NCOIC
Operational Technical
Capability
Focus:
Patterns
Patterns
Net-Centric
Patterns
Interoperability
Technology doesn’t set standards.
Federal use cases set the standards
15

Long Term Strategy !