View
10
Download
0
Category
Preview:
Citation preview
Information Sharing Environment Interoperability Framework (I2F) Making Interoperability Common Presented to Collaboration and Transformation SIG
Getting on the Same Page (Definitions)
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?
1. A guidance document for Exec, PM’s, SME and Architects
2. Supports “IT service providers” in efficiently achieving information and system interoperability
3. Aligns to National Strategies ( Secure, Measureable, Extendable and Implementable Services)
4. Interoperability Objectives:
▪ Increase information sharing
▪ Reduce total cost of operations
▪ Promote shared services
▪ Treat information as a National Asset
3
I2F: Vision & Approach
4
•Mission 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 Grid ISE Standards and Specifications Framework ISE Common Profile Template
I2F Integrated Landscape (I2FIL)
5
I2F provides an extensible, measurable, and implementable approach that is built for the ISE community as a management practice, to enable assured interoperability
ISE Interoperability Framework •Interoperability Requirements
• Operational Capabilities •Exchange Patterns •Technical Capabilities •Technical Standards
ISE Architecture Framework Grid • Baseline for Enterprise Architecture
• Business and Technical Alignment
• Identifies Artifacts Across Commonly Used Frameworks
ISE Standards and Specifications Framework
• Functional and Technical Standards
• Implementation frameworks
ISE Common Profile
• Discovery Mechanics
• Governance
• Facilitates Enterprise and Local Inventories
6
• Increase Information/
Intelligence Sharing
• Reduce Total Cost of
Operations
• Shared Services
Priority
Objectives
National
Strategy
2012
Government
Authorities
Stakeholder
Inputs
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
Inside I2F Components
7
Mission Space Operational 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
What Are Exchange Patterns?
8
Query Response
Workflow
Alerts, Broadcast and
Notifications
Choreography and Coordination
A B
C D
A
Standardize
Interfaces!
SOA
REST
WS*
Discover
Interoperable Services
Build
Interoperable Services
Extend
Interoperable
Services
• Discover Existing Capability or Managed Services
• Build New Capability
• Extend/Reuse Existing Capability
Vision for Sustainability
9
I2F Repeatable Integrated Continuum
I2F Integrated Landscape Lifecycle
10
ISE Interoperability Framework
(I2F )
Architecture Frameworks
(Domain/Artifacts)
Industry Standards &
Specifications Framework
Common Profile
Business/ Operational Capability
Business Performance
Security
Requirements Definitions
Reference View
Representative Standards
Technical Capabilities Application/Services Security
Technical Standards
Technical View
Exchange Patterns
Exchange Specifications
Infrastructure Data
Security Governance
Interoperability Standards Implementation View
Implementation Framework
Service Design Principles
Guide
I
Articulate
II
Normalize
III
Populate/
Discover
IV
Why Should Stakeholders Care?
11
Stakeholder I2F Relevancy Value Stream
Executives
• Scope and relevancy of interoperability of national priorities
• Endorse the framework in agency level policy
• Tie to each domain and emphasize “value propositions”
• Align Strategic Priorities to Mission Capability
• Adopt Interoperability Management Practice defined for policy use
Program Managers or Business Owners
• Provide comprehensive and Integrated landscape for communities of interest
• Measure Investments
• Discover Interoperable Services
• Extend Roadmap for Shared, Manage, Cloud, and Mobile Services
Solution Architects or Developers
• Elaborate on interoperability requirements in specific business segment through reference architectures
• Provide common approach to enable interoperability
• Include templates, and use cases etc.
• Extend Interoperability Technical and Functional Standards
• Reuse (Implement) Existing Services
• Build Interoperable Services
Why Should Stakeholders Care?
12
Stakeholder I2F Relevancy Value Stream
Other Federal Partners –OMB,
GAO
• Aligns to federal guidance, authorities, and approaches
• Provides performance criteria and improves information sharing and interoperability maturity of ISE stakeholders
• Adopt I2FIL and Reference Architecture Template
• Align national strategies and guidance in an integrated view to achieve maturity through business and technical disciplines, and best practices
SLTT
• Demonstrates the interoperability concepts, standards, and services utilized by ISE federal partners to better align architectures, systems, applications, and capabilities
• Reuse cross-cutting subject matter expertise through domain specific requirements
• Streamlined and vetted concepts
• Implement Exchange patterns and documentation
• Adopt standards and specifications
Private Sector • Shares the standards and services being
mandated or recommended for the ISE to better align vendor products
• Implement business and technical capability defined for interoperability and information sharing needs
• Support for acquisition processes
• Participate as member of Standards Development Organizations
Foreign Partners
• Focuses on universal concepts—non-government unique, voluntary, consensus standards
• Aligns to progressive efforts such as the Unified Architecture Framework
• Adopt I2FIL management practices
• Adopt tested standards and specifications to meet interoperability objectives
Alignment to National Strategies & Priority Objectives
13
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 Assured Interoperability: I2F provides a comprehensive approach using normalized functional and technical standards, and methods
Contact Information
14
Pamela J. Wise-Martinez, MEM, CGEIT Senior Strategic Enterprise Architect
Office of the Program Manager, Information Sharing Environment
Office of the Director of National Intelligence
pamelaw@dni.gov
(O) 202-331-4071
(c) 240-654-7876
www.ISE.gov
Blog | Twitter | Facebook | YouTube | LinkedIn
Get ISE Email Updates
APPENDIX
16
I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)
17
Review Enterprise Architecture Common Approach, and identify mission- and business-specific enterprise reference architecture domain needs
1. Review the minimum requirements for interoperability 2. Coordinate interoperability artifact descriptions 3. Identify artifacts relevant to interoperability and information sharing 4. Ensure identified applicable architecture artifact is included in your reference,
segment, and solution architecture methodology 5. Update Reference Architecture
I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)
18
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 interoperability
3. Coordinate interoperability artifact descriptions
4. Identify artifacts relevant to interoperability and information sharing
5. Ensure identified applicable architecture artifact is included in your reference, segment, and solution architecture methodology
6. Update Reference Architecture
I2F Use – Building Interoperability into Mission-Based Reference Architecture(s)
19
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)
20
I2F MINIMUM REQUIREMENTS FOR INTEROPERABILITY
I2F ARTIFACT DESCRIPTION
How it addresses interoperability
requirement
APPLICABLE ARCHITECTURAL ARTIFACTS
Applicable view, artifact, etc. – which maps to applicable reference artifact
Common Approach to Federal Enterprise
Architecture DoDAF/UAF
GRA
Service 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 Catalog
Provider-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 Model
DIV-1: Conceptual Data Model
DIV-2: Logical Data Model
Message Exchange Patterns
Activity Diagram
Conceptual Data Model
Logical Data Model
Activity Model
Baseline 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)
21
2. Coordinate interoperability artifact descriptions 3. 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)
22
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
23
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.
Recommended