Information Exchange Requirements

1
Information Exchange Requirements
Requirement Is My Last Name
Receiver A
Sender A
Receiver B
Sender B
Receiver C
Sender C
Receiver D
Sender D
2
What is an IER?

• The 3170 defines Information Exchange
  Requirement as the requirement for information
  to be passed between and among forces,
  organizations, or administrative structures
  concerning on-going activities
• Quality (i.e. frequency, timeliness, security)
  and quantity (i.e. volume, speed, and type of
  information such as data, voice, and video) are
  attributes of the information exchange included
  in the IER
• All you need to understand at this point is that
  an operational IER should tell you
• Who is sending the information
• What information is being sent
• Why the information is being sent
• Who is receiving the information
• How the information must be passed for the
  warfighter mission, business process, or
  transaction to be completed successfully

3
What is an IER?
Issues
Capability Gap
(Key) Performance Parameter
Threshold
Capabilities-Based Requirement
Mission Context
Condition of Success
Attribute
Objective
4
What is an IER?
Issues
Capability Gap
(Key) Performance Parameter
Threshold
Capabilities-Based Requirement
Mission Context
Condition of Success
Attribute
Objective
Interoperability (IERs)

• When an information exchange is inherent in a
  requirement, the IER is a Condition of Success
  for that requirement. The IER is necessary, but
  not sufficient, for meeting that requirement.
• If the operational requirement is key or
  critical, the IERs associated with it are key or
  critical.
• Inversely, if the operational requirement is not
  key or critical, the IERs associated with it are
  not key or critical.

5
SoWhat Else Is an IER?

• IER is a Condition of Success for a requirement
• It is a requirement, but what is desired result
  of the requirement?
• Transmission?
• Reception?
• Cannot be generally understood with single
  threads
• IERs are detailed pictures of how a
  System-of-Systems or Family-of-Systems should
  work to support specific transactions within an
  event
• IERs are statements of why information is needed
  and operational context in which to place the
  data elements
• The connection between system and operational
  architecture
• If properly formulated, the IER makes system
  architecture relevant

6
Information Exchange Requirements
For this event
Event
Information
Performance Requirements (Attributes, Thresholds,
Objectives)
WHAT
HOW
Data Elements
Receiver A
Sender A
OPFAC System Unit
Receiver B
Sender B
WHO
WHO
Receiver C
Sender C
Receiver D
Sender D
Many possible transactions
7
Information Exchange Requirements
For this event
1. Information exchange necessary to support the
event?
Event
Information
Performance Requirements (Attributes, Thresholds,
Objectives)
WHAT
HOW
Data Elements
2. Specifically - what information? Format,
content, data elements, classification, etc.
4. Determine how the information must be passed
to support levels of performance for each set of
operational conditions or circumstances.
Receiver A
Sender A
OPFAC System Unit
Receiver B
Sender B
WHO
WHO
Receiver C
Sender C
3. Go to OPLANS, recent ops, ID possible senders
and receivers, and what conditions and
circumstances they send/receive. Who are the
backups?
Receiver D
Sender D
Many possible transactions
8
Information Exchange Requirements
For this event
Event
Information
Performance Requirements (Attributes, Thresholds,
Objectives)
WHAT
HOW
Data Elements

• Are multiple senders transmitting the same
  information simultaneously?
• Is redundancy a factor?
• Are there designated primary and backup
  receivers?
• What are system assets and abilities for each
  sender possess?

Receiver A
Sender A
WHO
Receiver B
Sender B
WHO
Receiver C
Sender C
Receiver D
Sender D
Many possible transactions
9
Information Exchange Requirements
Event
Information
Performance Requirements (Attributes, Thresholds,
Objectives)
Data Elements

• Any recent performance indicators for this event?
• Think about reasonable contingencies - what if
  scenarios.

Receiver A
Sender A
Receiver B
Sender B
WHO
Receiver C
Sender C
Receiver D
Sender D
Many possible transactions
10
Information Exchange Requirements
For this event
Event
Information
Performance Requirements (Attributes, Thresholds,
Objectives)
WHAT
HOW
Data Elements
Receiver A
Sender A
Receiver B
Sender B
WHO
WHO
Receiver C
Sender C
Receiver D
Sender D
Many possible transactions
11
Information Exchange Requirements
For this event
Event
Information
Performance Requirements (Attributes, Thresholds,
Objectives)
WHAT
HOW
Data Elements
Receiver A
Sender A
Receiver B
Sender B
WHO
WHO
Receiver C
Sender C
Receiver D
Sender D
Many possible transactions
12
Information Exchange Requirements
Many possible transactions
13
Information Exchange Requirements
Representing IERs in this manner bridges
requirements to support plans. This works for
all transactions - not just IERs!
14
IER Pre-requisites?
System Candidates
15
IER Pre-requisites?
Issues
Capability Gap
(Key) Performance Parameter
Threshold
Requirement
Condition of Success
Attribute
Mission Context
Objective
16
IER Pre-requisites?
Issues
Capability Gap
(Key) Performance Parameter
Threshold
Requirement
Mission Context
Condition of Success
Attribute
Objective
Interoperability (IERs)
The mission centric definition of information is
needed, and how it must be delivered relevant to
an operational event in order to ensure a
successful transaction.
NR-KPP
The system-centric answer to delivering the
information in a Net-Centric environment.
17
IER Pre-requisites?
Issues
Capability Gap
(Key) Performance Parameter
Threshold
Requirement
Mission Context
Condition of Success
Attribute
Objective
Interoperability (IERs)
18
Attribute Characterization Model
MOP Sensor data accurate within 10 meters
MOP C4 system navigation error lt 1 meter
MOE Target Position Data 98 accurate
Network Transmitter C
Network Receiver D
Data Collection Point
Data Collection Point
Data Collection Point
Sensor A
Shooter F
Processor B
Processor E
Information Target Position Data
You must specify which portion of the model
applies to the KPP thresholds and objectives.
19
FCB Oversight
Issues
BIG DOTMLPF AOA
Operational Requirements
Integrated DOTMLPF Strategy
(Key) Performance Parameter
Threshold
Functional Requirements
Mission Context
Condition of Success
Attribute
Objective
little dotmlpf The fielded solution
Doctrine Support Plan Products
Facilities (Engineering) Support Plan Products
DOTMLPF Change Package
Training Support Plan Products
Organizational Support Plan Products
C4I Support Plan. Specs, etc. Products
Leadership Support Plan Change Mgmt Products
Personnel Support Plan Products
20
FCB Oversight
Issues
BIG DOTMLPF AOA
Operational Requirements
Integrated DOTMLPF Strategy
(Key) Performance Parameter
Threshold
Functional Requirements
Mission Context
Condition of Success
Attribute
Objective
Interoperability (IERs)
little dotmlpf The fielded solution
Doctrine Support Plan Products
Facilities (Engineering) Support Plan Products
DOTMLPF Change Package
Training Support Plan Products
Organizational Support Plan Products
C4I Support Plan. Specs, etc. Products
Leadership Support Plan Change Mgmt Products
Personnel Support Plan Products
21
DOTMLPF Adaptation
Analyze each FoS for in-theater technical
capabilities deficiencies (including
interoperability)
ID DOTMLPF drivers and barriers across C/S/As to
achieving concept
Develop concept
ID functions associated with concept
Build FoSs associated with each function
Operational Concept Matrix for each new
technology needed to achieve new service concept
Apply MAP to create operational architecture view
for assessment and experimentation
Perform paper validation and assessment
ID new technology capabilities (RD lab, ACTD,
ST, etc.) from all C/S/As
Establish sharing agreements, MOUs
Establish suitability of other C/S/As technology
in service concept
Conduct assessments experiments which
incorporate technologies needed to achieve
service concept
Develop phase architecture views for
time-phased DOTMLPF implementation
Adjust overall concept, OPCON, architecture views
as needed
Establish time-phased DOTMLPF implementation POA
Communicate findings to RD and ST community
Finalize DOTMLPF program strategy
Apply 3170, 3180 process
Develop DOTMLPF change package (all support plan
needed for implementation)
Begin acquisition
22
Contacts