Biography Of Angeliki Cooney | Senior Vice President Life Sciences | Albany, ...
PM ISE Information Interoperability Presentation -agile sourcing brief
1. ISE Information Interoperability (I2F)
Framework
Understanding “Project Interoperability” Tools
Agile Sourcing Working Group Briefing
April 23, 2014
2. 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
3. What is the I2F?
A guidance document for Exec, PM’s, SME and Architects to
deliver Interoperable services using common practices, terms and
models
Supports “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
4. 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 Grid
ISE Standards and Specifications Framework
ISE Common Profile Template
6. 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
7. 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
8. 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.
9. 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
13. 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 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
14. 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 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
15. 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
16. I2F Use – Building Interoperability into Mission-
Based Reference Architecture(s)
16
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
17. I2F Use – Building Interoperability into
Mission-Based Reference Architecture(s)
17
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
18. 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
19. 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.
22. Information Sharing
Viewpoints
22
Content Service Policy*Process
What we
can know
and
communicat
e 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
Requirements
Definition
(Focus – Users)
Representation
Standards
Interoperability
Specifications
Technical
Standards
23. Implementation
Frameworks
Standards & Framework
Taxonomy
23
Content Service Policy*Process
Requirements
Definition
(Focus – Users)
Technical
Standards
Interoperability
Specifications
Process
Definition
Process
Standards
Process
Orchestration
Content
Definition
Data
Standards
Data
Schema
Services
Definition
Service
Standards
Service
Interfaces
Policies
Definition
Policy
Standards
Executable
Rules
Representation
Standards
Process
Representation
Content
Representation
Services
Representation
Policy
Representation
* Includes Security & Privacy Rules
Mission Context
Process
Orchestration
Schema &
Management
Service
Components
Policy
Execution
Interoperability
Roadmap
Scope
24. Technical Specification Layering
24
Requirements
Definition
(Focus – Users)
Representation
Standards
Interoperability
Specifications
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
Implementation
Frameworks
Technologies and products that implement a set of technical standards in
support of implementing interoperability specifications
EG: .NET or JEE
26. 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
defines
Standards
outcomes
Enable cross-
functional
integration &
interoperability
IC BT
Capability
Business Profile Path
Requirements
Business
Profile
context
27. 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
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
28. Contact Information
28
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
Click Here for Project Interoperability ---
Online Documentation
Notas do Editor
Leverage established Best Practices:Leveraged to IC Community adopted implementationMapped back to FEA constructsAdheres to OMB requirement for TemplatesProvides Stakeholders clear and concise examples of practical implementationsGives Private Sector understanding of Government direction
Commonly used message/information exchanges
Exchange Patterns: Exchange patterns are the basic 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. The purpose of exchange patterns is to ‘build’ interoperability into the pattern itself. Technical Standards: ISE technical standards are specific technical methodologies and practices to design and implement information sharing capabilities into ISE systems. They are an intrinsic element of both functional standards and technical services. These standards are very technical in nature, and are often developed as a result of identified needs, are foundational in nature, address specific problems, are not very mission focused, and can be easily applied to different communities of interest. Technical standards are developed by the Standards Development Organizations, working with the stakeholders and industry organizations, and are usually published as a ‘normative standard specification’ that is used to define and measure conformance.Technical Services:ISE technical services constitute detailed technical descriptions, data, and metadata on focused areas that enable the efficient, secure and trusted application of the ISE business processes and information flows to share information. These 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:ISE 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 standards, and once adopted by the community of interest, significantly enable requirements for interoperability across agencies and jurisdictions. These standards may be government-unique or a combination of other functional standards as appropriate.Operational Capabilities:Operational Capabilities are the reference implementations of functional and technical standards and services coupled with the appropriate policy, process, training, outreach, and other infrastructure components. A mission partner executes a combination of standards within their mission technology and application environment that enables interoperability and information sharing. Users can work more effectively when they employ the resulting mission capability.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. A Use Case is developed at varying levels of detail to help visualize and describe specific activities or information flows in order to get agreement on an information flow from beginning to end. The use case should be developed from an operational perspective and should be technology neutral unless the use of specific technology is dictated.
Profiles package together several artifacts to form a consolidated set of information that is needed to construct and re-use a capabilityThe artifacts include standards, technical configuration guidance, specifications, etc.The profiles have three distinct views for different stakeholders; strategic planners, engineers, and developers.The set of profile content is what supports the policy that directs to community to operate a capability according to a common or standards based implementation.Re-use comes form the aggregation of the essential information together to construct and realize the capabilityThe profile therefore is the binding package or recipe for the capability.