4. Top-Level Interoperability Information Exchange Requirements
a. For ORDs, top-top leveltop level IERS are defined as those information
exchanges that are external to the system (i.e., with other combatant
commands/Services/agencies (C/S/A), allied and coalition systems).
b. A top-level IER matrix provided in a worksheet format will be part of
ORDs when submitted.Top-level IERs identify who exchanges
what information with whom,
why the information is necessary, and how
the information exchange must occur. Top-level IERs identify warfighter
information used in support of a particular mission-related task and
exchanged between at least two operational systems supporting a joint or
c. Top-level IERs and the interoperability KPP will be extracted from the
ORD and used in the development of the C4ISP. Top-level IERs will be
provided in the matrix format shown in Table D-1.
d. Top-level IERs may also be imported into modeling and evaluation
including network warfare simulation (NETWARS) and Joint C4ISR architecture
planning and analysis system (JCAPS). NETWARS and JCAPS both require
additional fields than those depicted in Figure D-1.
e. Note that there is more detail in an ORD top-level IER matrix than in
a CRD top-level IER matrix. The ORD will include all applicable top-level
IER(s) identified in the CRD (if a CRD exists). If the ORD is using a
time-phased, evolutionary or block requirements approach, the ORD must
identify the IERs for each phase or block.
f. The top-level IER matrix must correlate with the proposed high level
operational concept graphic(s) and system interface description.
(1) Sample ORD top-level IER matrices are illustrated in Table
(2) In the development of the top-level IER matrix, the originator will
determine if a given top-level IER is critical (top-level IER matrix field
g. An ORD critical top-level IER supports its associated CRD
critical top-level IER, or will severely and adversely impact on a
warfighter mission if not