ISE Information Interoperability (I2F) Framework

Understanding “Project Interoperability” Tools

Agile Sourcing Working Group BriefingApril 23, 2014

Getting on the Same Page(Common Terminology)

2

What is Information Interoperability?

The ability to transfer and use information in a uniform and efficient manner across multiple organizations and information technology systems

Australian Information Interoperability Framework (2006)

In other words…

It’s the ability of two or more systems or components to exchange information and to use the information that has been exchanged

What is the I2F?

A guidance document for Exec, PM’s, SME and Architects to deliver Interoperable services using common practices, terms and modelsSupports “IT service providers” in efficiently achieving information and system interoperability

Aligns to National Strategies ( Secure, Measureable, Extendable and Implementable Services)• Interoperability Objectives:

• Increase information sharing• Reduce total cost of operations• Promote shared services• Treat information as a National Asset

3

I2F Vision & Approach

4

Operational Agnostic View: I2F guides the implementation of ISE information sharing capabilities across heterogeneous boundaries

Common Practices: It provides mechanisms that can support FSLTT partner agencies (e.g., fusion centers) to share data based on normative terms, common standards, and practices

Integrated Landscape: The I2F will accomplish the above objectives primarily through ISE constituent use of

ISE Architecture Framework GridISE Standards and Specifications FrameworkISE Common Profile Template

5

• Increase Information/

Intelligence Sharing

• Reduce Total Cost of

Operations

• Shared Services

DesiredOutcomes

PriorityObjectives

NationalStrategy2012

GovernmentAuthorities

StakeholderInputs

Interoperability Safeguarding Search & Discovery Access & Retrieval Dissemination

Defense Law Enforcement Foreign Affairs Homeland Security Intelligence

Interoperability Requirements Operational Capabilities

Exchange Patterns Technical Capabilities Technical Standards

Reference Models Exchange Specifications Technical Specifications

FEAF DoDAF PAG

Enables

Constraints/Environment

Federal SLT Private Int’l

Stakeholders

Communities

TOGAF GRA

Architecture Frameworks

Captured

In

I2F Integrated Landscape (I2FIL)

6

I2F provides an extensible, measurable, and implementable approach that is built for the ISE community as a management practice, to enable assured interoperability

Inside I2F Components

7

Mission SpaceOperational Capabilities: references “Current State”

Implementations of functional and technical services coupled with the appropriate policy, process, training,

outreach, and other infrastructure components

Common Practice and Terms• Technical Standards: specific to the development

and implementation of information sharing capabilities into ISE systems

• Technical Capabilities: detailed technical descriptions such as data and metadata that enable the

efficient, secure, and trusted application of the ISE business processes and information flows to share

information

• Exchange Patterns: repeatable sets of tasks that help accomplish a commonly occurring need for

exchange of data or information between two or more partners

Reuse and Shared Capability• Exchange Specifications: is the instantiation of an

exchange pattern, and once implemented correctly enables interoperability

Choreography and Coordination

What Are Exchange Patterns?

8

Query Response

Workflow

Alerts, Broadcast and Notifications

A B

CD

A

These commonly used message/information exchanges support mission needs…think RFI, AWN…SAR, or complex systems like Electronic Court Filing systems.

Alignment to Management Plan & Priority Objectives

9

Extensible Capability: I2F enables multiple priority objectives, implementation guidance and future needs i.e., IDAM, Data Agg, Shared Services, RFI, NIEM-UML, Cyber Initiatives, SBA, NJ-ISE, Cloud, Mobile etc…

Measureable Criteria: I2F supports quantitative performance objectives aligned to PRM and GAO maturity model through identification of requirements

Implementable Approach: I2F supports the delivery of capability through common architecture process, repeatable exchange patterns and harmonized standards and specifications

DiscoverInteroperable Services

BuildInteroperable Services

ExtendInteroperableServices

Standards and Specifications

Vision for Sustainability

10

• Discover Existing Capability or Managed Services• Build New Capability • Extend/Reuse Existing Capability

I3F Repeatable Integrated Continuum

Profil

es

Architecture

Extensible, Measurable, Implementable

I2F Integrated Lifecycle

11

ISE Interoperability Framework

(I2F )

Architecture Frameworks

(Domain/Artifacts)

Industry Standards&

Specifications Framework

Common Profile

Business/Operational Capability

BusinessPerformance

Security

RequirementsDefinitions Reference View

Representative Standards

Technical Capabilities Application/ServicesSecurity Technical Standards Technical ViewExchange Patterns

ExchangeSpecifications

InfrastructureData

SecurityGovernance

Interoperability StandardsImplementation

ViewImplementation Framework

Service Design Principles – Assured Interoperability

Guide

I

Articulate

II

Normalize

III

Populate/

Discover

IV

Extensible, Measurable, Implementable

Enterprise Architecture Requirements and Maturity Models

Baseline FEA Common Approach

Pillar 1

12

I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)

13

Review Enterprise Architecture Common Approach, and identify mission- and business-specific enterprise reference architecture domain needs

1. Review the minimum requirements for interoperability2. Coordinate interoperability artifact descriptions3. Identify artifacts relevant to interoperability and information sharing4. Ensure identified applicable architecture artifact is included in your reference,

segment, and solution architecture methodology5. Update Reference Architecture

I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)

14

Use the I2F Architecture Framework Alignment Grid and Reference Architecture template to:

1. Review FEAF CA, and identify mission- and business-specific enterprise reference architecture domain needs

2. Review the minimum requirements for interoperability3. Coordinate interoperability artifact descriptions4. Identify artifacts relevant to interoperability and information sharing5. Ensure identified applicable architecture artifact is included in your reference,

segment, and solution architecture methodology6. Update Reference Architecture

I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)

15

1. Review the minimum requirements for interoperability

Ex., Data Domain - builds on the operational context and defines why information needs to be exchanged. Technical standards are enablers that provide the vocabularies for sharing to assure that the semantic meaning and the context of the data is not lost during transition and transformation. Technical capabilities provide the architectural context within which the exchange is executed. All of these components focus on the interoperability framework. The actual data constructs define the data exchange content model and includes:

Mechanism for identifying and categorizing candidate assets for sharing Framework for capturing data elements and the relationship between them (semantics) How the data is structured, what standards are used, and how data/information can be exchanged so

users are able to both have access to and use the data/information Technical standards to design and implement information sharing capabilities into ISE systems Approach for documenting exchange patterns Data/information flow to include the tagging of the data, discovery, and retrieval Principles, roles, and responsibilities for data management and stewardship

I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)

16

I2F MINIMUM REQUIREMENTS FOR INTEROPERABILITY

I2F ARTIFACT DESCRIPTIONHow it addresses interoperability

requirement

APPLICABLE ARCHITECTURAL ARTIFACTSApplicable view, artifact, etc. – which maps to applicable reference artifact

Common Approach to Federal Enterprise

ArchitectureDoDAF/UAF

GRAService Specification Package, v1.0.0

IC-related(based on ICEA PAG)

TOGAF

DATA DOMAIN Mechanism for identifying and categorizing candidate assets for sharing

(D1) Provide the high-level data concepts and their relationships

Knowledge Management Plan (D2)

Data Asset CatalogProvider-to-Consumer

Matrix

DIV-1: Conceptual Data Model

Domain Vocabulary Conceptual Data Model Phase C: Information Systems Architecture – Data

Application Principals, Data Principals

Framework for capturing data elements and the relationship between them (semantics)

(D2) Document the data requirements and their relationships, as well as the structural business process rules and metadata where necessary

Logical Data Model (D1)

DIV-2: Logical Data Model

Message Definitions Mechanism

Logical Data Model Architecture Definitions Document

Approach for documenting exchange patterns

(D3) Show the repeatable set of tasks that help accomplish the commonly occurring need for exchange of data/information between exchanging partners, as well as the data relationships and how the data relates to the business activities and their rules/policies

Business Process Diagram (B1)

Logical Data Model (D1)

OV-5b: Operational Activity ModelDIV-1: Conceptual Data ModelDIV-2: Logical Data Model

Message Exchange Patterns

Activity DiagramConceptual Data ModelLogical Data Model

Activity ModelBaseline and Target

Data Descriptions

Principles and roles and responsibilities for data managements and stewardship

(D4) Show organizational relationships with respect to the data and its lifecycle

Knowledge Management Plan (D2)

OV-4: Organizational Relationships Chart

(along with narrative)

Operational Concept Description

Data Management, Data Migration, and Data Governance

Technical standards to design and implement information sharing capabilities in ISE systems

(D5) Provide any necessary or relevant data standards to be considered for interoperability

Technical Standards Profile (I3)

StdV-1 Standards Profile

Relevant Mandated Standards

I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)

17

2. Coordinate interoperability artifact descriptions3. Identify artifacts relevant to interoperability and information sharing

Ex., Data Domain - builds on the operational context and defines why information needs to be exchanged. Technical standards are enablers that provide the vocabularies for sharing to assure that the semantic meaning and the context of the data is not lost during transition and transformation. Technical capabilities provide the architectural context within which the exchange is executed. All of these components focus on the interoperability framework. The actual data constructs define the data exchange content model and includes:

Mechanism for identifying and categorizing candidate assets for sharing Framework for capturing data elements and the relationship between them (semantics) How the data is structured, what standards are used, and how data/information can be exchanged so

users are able to both have access to and use the data/information Technical standards to design and implement information sharing capabilities into ISE systems Approach for documenting exchange patterns Data/information flow to include the tagging of the data, discovery, and retrieval Principles, roles, and responsibilities for data management and stewardship

I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)

18

4. Ensure identified applicable architecture artifact is included in your reference, segment, and solution architecture methodology

• DoDAF• DIV-1• OV-4• StdV-1

5.Update Reference Architecture

Applying I2F Concepts to Enable Operational Capabilities

19

Concepts described in the I2F , when applied within a specific mission context, enable operational capabilities. The Use Case methodology and example that will be developed will provide an example of applying these concepts to the Maritime Domain Awareness Use Case. The use case will be developed from an operational perspective and should be technology neutral unless the use of specific technology is dictated. • Exchange Patterns:

• patterns for how data is exchanged between information sharing providers, consumers, and/or information brokers. Exchange patterns are the mechanism to standardize certain types of exchanges that incorporate technical standards and technical services

• Technical Standards:• technical methodologies and practices to design and implement information sharing capabilities into ISE systems

• Technical Services:• services address specific technical needs or problems, are reference implementations of one or more technical

standards, and provide the technical functionality required to implement a business architecture

• Functional Standards:• constitute detailed mission descriptions, data, and metadata on focused areas that use ISE business processes and

information flows to share information. These standards address a specific mission need or problem, are often collaborative in nature, apply mission context to the technical standard.

• Operational Capabilities:• reference implementations of functional standards, technical standards, and services.

I2F Interoperability Maturity Model

20

OMG/ Gov DTF

Information Sharing Workgroup Contributions

21

Pillar 2

Information Sharing Viewpoints

22

Content Service Policy*Process

What we can know

and communicate structured in terms of concepts, terms and

symbols we understand

What we do and when we do it.

Processes use and produce

information, assets and

services

How we interact to exchange

information, products

and services for

mutual benefit

Rules about content, process

and services based on security,

privacy and other

concerns

RequirementsDefinition

(Focus – Users)

RepresentationStandards

InteroperabilitySpecifications

Technical Standards

Implementation Frameworks

Standards & Framework Taxonomy

23

Content Service Policy*Process

RequirementsDefinition(Focus – Users)

Technical Standards

InteroperabilitySpecifications

ProcessDefinition

ProcessStandards

ProcessOrchestration

ContentDefinition

DataStandards

DataSchema

Services Definition

ServiceStandards

ServiceInterfaces

PoliciesDefinition

PolicyStandards

ExecutableRules

RepresentationStandards

ProcessRepresentation

ContentRepresentation

ServicesRepresentation

PolicyRepresentation

* Includes Security & Privacy Rules

Mission Context

ProcessOrchestration

Schema &Management

ServiceComponents

PolicyExecution

Inte

rope

rabi

lity

Roa

dmap

Sco

pe

Technical Specification Layering

24

RequirementsDefinition

(Focus – Users)

RepresentationStandards

InteroperabilitySpecifications

User relevant requirements and specifications of functionality from the users perspective

EG: Suspicious activity reporting requirements

Technical Standards

General technical capabilities and standards that may be used to provide user functionality

EG: WS-Encryption, NIEM-XML

Languages, notations and formats representing functional and technical specifications

EG: UML

Specifications for interoperability and information sharing that implement a functional specification using a set of technical standards

EG: SAR Specification in NIEM-XML IEPD and Web Services

ImplementationFrameworks

Technologies and products that implement a set of technical standards in support of implementing interoperability specifications

EG: .NET or JEE

IISC Standards WorkgroupContributions

ISO-10000-Profiling Practice

Pillar 3

25

Extensible, Measurable, Implementable

Profile Overview

• What is a Profile?– A Profile describes a capability and its attributes including common

processes and information exchanges and the integration of these

attributes with other capabilities within and across lines of business

– Profile content will increase in detail as it matures through an

iterative lifecycle

• How are Profiles used?– Profiles are used to formalize standards for implementation and to

enable integration by standardizing business attributes that are

significant to the enterprise

definesStandards

outcomes

Enable cross- functional

integration & interoperability

IC BT Capability

Business Profile Path

Requirements

Business Profile

context

Extensible, Measurable, Implementable

Tech Spec

Profile Package

PROFILE VIEWS AND COMPONENTS

27

Technical Base Specs/Standards

Mission/Business Configurations

Device/Service/…Solution Implementation

Instance

Device/Service/…Solution

Art

ifact

Ref

Art

ifact

Ref

Art

ifact

Ref

Methods &Techniques

Guidance

Compliance & Conformance

Arch Ref

General Attributes

Implementation Reference

Link

Link

Link

Link

Link

Link

Policy/Policy Standards

Implementation Instance View

• Operational Techniques• Model Configuration

Parameters

Tech Guidance View• Ref Spec

• Ref Architecture• Standards

• Domain Guidance• MOEs, MOAs

• Mission Applicability• Compliance Mechanisms

Reference View• Description

• Maturity• Classification

• Version• Arch Component

• Enterprise Architecture Reference

• Scope Applicability

Service Specification

Capability

Contact Information

28

Pamela J. Wise-Martinez, MEM, CGEITSenior Strategic Enterprise ArchitectOffice of the Program Manager, Information Sharing EnvironmentOffice of the Director of National Intelligencepamelaw@dni.gov(O) 202-331-4071 (C) 240-654-7876

www.ISE.govBlog | Twitter | Facebook | YouTube | LinkedInGet ISE Email Updates

Click Here for Project Interoperability ---Online Documentation