Embed Size (px)
Citation preview
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Introduction to Design Rules in NATO NISP
Mr Peder BlomqvistCIO Strategist, Swedish Armed Forces (SWAF) CIO Department at the Supreme Commanders Staff CIO strategic and directive program C4I architect Member of NATO Open Systems Working Group since 2005
Mr Niklas HäggströmSenior IT-Architect , Centric Labs
Integrated EA conference London March 09-10 2010
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
What Design Rules are and why they are useful
NATO Open System Working Group and NISP development
How Design Rules are to be incorporated into NATO NISP
A walkthrough of the Design Rule for International Military Interoperability
Presentation content
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
What Design Rules are and why they are useful
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Transformation
Revolution
Evolution
Previous vision
Platform-centric,service embedded,large conflict,well established C2
New vision
Network-centric,interoperable,joint, integrated,flexible
Existing structure Future structure
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
DR reference of importance
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
The holy Franciscus, Il Poverollo, 1182-1226 “A rule excludes permanent wiggling between
different alternatives. It makes it possible to follow a defined line. It is not the amount of details, but abeyance to a few directives that is of importance. The directives shall be so short and clear that you immediately can recall them in your memory
“The rule should be practical, addressed directly to the sense and shall be personal. Not until you thoroughly have considered the rule, elaborated it carefully, have allowed it to mature and hardened it you should train yourself in being fateful to it”
Design Rules 1200,
The holy Franciscus
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
A design rule is a solution to a problem in a specific context with the following characteristics:
Definition of a Design Rule
Belongs to aproblem domain
Packages knowledgein a reusable form
Standardize solutionsto design problems
within NNEC
Gives value tothe re-user
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Standards – often WHAT but not always HOW How to apply the standard on a specific problem Relations between different standards Applicability in different domains A vast number of standards are applicable for NEC
does not mean that complex system work!
Are not standards enough?
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Design Rules Design
Design Rules & Design
Generic generally applicable Mostly non functional Long-lived When following design rules the design work will be ”NNEC compliant”
Capability independent
What will be realizable in order to meet the functional requirements How will it be practicable Will be used to support the purchasing Some parts will be long-lived and reusable in design work to come when adding new functional requirements
Capability dependent
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
OASIS SOA Reference model v1.0
adopted by NATO
Service Oriented Architecture
Design Rules Framework
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Interoperability Design Rule
Focus Areas
Flexibility Mobility Scalability Interoperability Security
Interoperability
Legacy IntegrationInternational Mil Interop.
Civil Interoperability
Produced and used in the Swedish NEC program
NISP v4 development phase
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
NATO Interoperability Standards & Profiles
development
NOSWG -
NATO Open System Working Group
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
NISP v4 --- ADatP34 (D)
Rationale N
ISP
Standard
s and P
rofiles
Vol. 1 Vol. 2 Vol. 3 Vol. 4 Vol. 5
MA
NA
GE
ME
NT
NE
AR
TE
RM
0-2 y
Rationale N
ISP
SO
A &
Design
-R
ules
Vol.6
MID
TE
RM
3-6 y 6+ yL
ON
G T
ER
M
Standards & Profiles
SOA & Design Rules
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
How Design Rules are to be incorporated into the NISP
Outline - 3
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Design Rule Guidance &
DR -International Mil
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Profile configuration support
NISP-NAF Relations
Profile NISP v4
ArchitectureNAF v3
StandardsDesignRules
howwhat
Mission
Objectives
Capabilities
Actor
Profile description support
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Strategic views
Services views
Systems views
Operational views
NISP Profile - NAF relation
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
NISP
Standards &Profiles
guidance/mandate
Architecture Repository
Target Architectures:Implementation
Reference Architectures:Solution Patterns
Overarching Architecture:Services Framework
NAF v3.1
Architectures & NISP
guidance
requirements
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Walkthrough of the Design Rule for International Military Interoperability
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
The design rule describes how military organizations can develop and implement the ability to exchange information with each other to support interoperability issues
Much of this design rule can also be applied when exchanging information with other actors than military organizations
Definition of interoperability in this context:− The ability of technical systems and/or organizations using
technical systems to operate together by making (necessary) data & information and/or services produced by one system or organization available to the others, in an agreed format
Introduction
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
The Design Rule elements
Context
Problem
Requirements
Challenges / Issues
Solution
Principles
Solution description
NISP Standards
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Context
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
The international military
federation
Federation agreement
Actor domain
Federation domain
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Scope of the design rule
Community of Interest
Information Integration
Communication
Info
rma
tion
Ass
ura
nce
Se
rvic
e M
an
age
me
nt
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Problem
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Basic requirements for information exchange People from the different organisational actors SHALL be able to
communicate with each other using voice or text communication. It SHALL be possible to discover and retrieve information (i.e.
search) provided to the federation by different actors.
Challenges Challenges based on international agreements and regulations Challenges based on national law, national integrity and regulations Challenges based on interpretation of information content Challenges based on technical issues Challenges based on culture, lack of trust and organizational issues
Each challenge has a set of related issues
Requirements and challenges
are identified
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Architecture and technical implementations of information systems differ
The complete technical system will probably not be homogenous, rather a federation of heterogeneous systems
Maturity of using architecture and design as governing tools is likely to vary greatly among collaborating parties
Agreeing on standards for information exchange is a critical success factor
Sovereignty of the parties will increase the complexity of this task There is no governing organ that can make the decisions
Without security mechanisms, no information can be exchanged There is a need to have the means to organize and prioritize what to
share
Example - Challenges based
on technical issues
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Solution
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Architecture for interoperability
Key principles The information aspect The security aspect
The Information Exchange Gateway Concept
Information zones
Technology and profiles− Discovery services − Repository Services− Collaboration Services− Messaging Services− Mediation Services− Information Assurance
Services− Service Management
Services− Summary
Outline for the solution chapter
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
The international military
federation architecture
Actor internal network
Federation network
Information Exchange Gateway
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Sovereignty of collaborating parties Each collaborating party
decides which information to publish into the federation
View on information Information published into the
arena is available to all parties, if no restrictions have been agreed
Agreements for Information Exchange Requirements, models,
translations and format for information exchange in the arena are regulated by agreements
Architecture The technical architecture for
information exchange follows the tenets of the Service Oriented Architecture concept
Technology Technical services for
information exchange uses open standards whenever possible
Security Service consumers and service
providers use a common methods for authentication and authorization of users and services
Key principles –
some examples
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Technologies summary
Service discovery
Collaboration Information discovery
Ser
vice
Man
agem
ent
Directory
Info
rmat
ion
Ass
ura
nce
Protocol Switch
TransformEnrichRoute Distribute Correlate
ProviderConsumer
Registry
Messaging
Authenticate
Authorize
Translation
Introduction to Design Rules in NATO NISP. Integrated EA conference London March 09-10 2010
Thank you!
