Michael Koester

1
C2 Lab

• Michael Koester
• Interoperability Test Director
• C2 Systems Branch/JITC
• [phone]
• Michael.koester_at_disa.mil

2
C2 Lab Mission

• Mission
• Provide C2 interoperability testing
  certification
• Objectives
• Ensure accurate information exchange
• Verify interoperability
• Assist in problem resolution
• Develop rigorous and repeatable testing through
  configuration management and automated test tools

3
Why Interoperability?

• Identifies
• Inaccurate data
• Missing data
• Systems interoperability limitations
• Critical information lose
• Leads to
• Great user awareness of inaccuracies
• Less user confusion over inaccuracies
• Verifies new fielded systems are interoperable
• Satisfies Joint Staff certification requirement

4
Test Process
5
Interoperability Testing Process
6
C2 Complexities
7
(No Transcript)
8
IOP Test Methodology

• Interoperability testing will focus on J6
  certified IKPP or NR-KPP
• Note GCCS-J critical interfaces in the Block IV
  TEMP Annex
• Testing accomplished during multiple venues
• Technical / lab
• Leverage service testing
• Participate in DTs and track progress / problems
  prior to SAT / OTE
• Operational commands (SAT / OTE)

Programs which lack Joint Staff certified
requirements will be issued an Interoperability
Assessment vice an Joint Interoperability
Certification.
9
Evaluation Measures

• Measure of Interoperability
• Can GCCS-J effectively exchange information with
  X system?
• Measures of Performance
• Accuracy
• Verify data sent or queried is the data received
  or displayed
• Completeness
• Verify all expected data received
• Usability
• Can the warfighter utilize the capability in an
  efficient manner to meet mission requirements

10
Test Events

• GCCS-J v4.0 JOPES SSE OTE, Jun 05
  (GCCS-AF/DCAPES, GCCS-A)
• Integrated Broadcast System Test, (GCCS-J/M), Sep
  04
• JIT 04-06, Oct 04 (GCCS-J/M Link 11/16 receive)
• GCCS-M v4.0 TechEval, Sep/Oct 04
• GCCS-J v4.0 Global SAT, Dec 04
• GCCS-M v4.0 OTE, Dec 04/Jan 05
• CST Test, Mar 05 (GCCS-J, GCCS-M, GCCS-A, TBMCS)
• GCCS-AF/DCAPES DTE, Mar 05
• GCCS-J v4.0 JOPES SSE SAT, Apr 05
• GCCS-J v4.0 Global OTE, Apr 05
• GCCS-M v4.0.1 Regression Test, Jun 05
• GCCS-J v4.0 JOPES SSE OTE Jun 05
• GCCS-J v4.0.1 JOPES and Global Regression Test,
  Jul 05

11
Situational Awareness
12
JIT 04-06 GCCS Testing Architecture
13
CST Interoperability Test
14
CST TEST ARCHITECTURE
JITC
GCCS-J
GCCS-A
XANDER
WILLOW
TOP COP
280R Web Server 4.0
TIGGER
ANYA
BUFFY
GCCSA001
A
B
E
ANGEL
SPIKE
9119
9119
9125
3.x 9119
4.0 9125
Legend
9119
9125
9119
9119
Inject/Feed
CST via SIPRNET
JOTS1
COMMS1
SAASVR
UBMSTRB
Link 11, Link 16, USMTF, OTH-G, TDDS, ETMS
A
C
D
Link 11, Link 16, USMTF, TDDS, OTH-G, ETMS, SBMCS
F
G
B
GCCSM0001
Link 11, Link 16, USMTF, OTH-G, TDDS
C
D
USMTF (S309, S507)
E
GCCS-M
TBMCS
USMTF (ATO, ACO)
F
G
AFC2ISRC
Injects will occur one at a time A, B, C, etc.
and verified at each participating system.
15
GCCS-J 4.0 Global IOP Sites
16
GCCS-J v4.0 and v4.0.1 Global Interoperability
Status
The following non-critical interfaces were not
assessed for interoperability. AMHS, EPLRs,
GALE-LITE, GDSS, GTN, ICC, JOIIS, JSTARS, LATTEL,
OMNITK, SDDC-TEA and TIBS.
17
Situational Awareness Findings

• MTC channel is required to be open in order to
  see all Link 16 Tabs for track attributes
• Segment load versions on Service Systems
• Effects display of track attributes
• Services ability to do MOOTW overlays
• Ability to see space tracks
• CST filters do not apply to C2PC Clients

18
JOPES IOP KPPs (8.1)

• Once data generated by an External system is
  submitted to GCCS JOPES it must arrive for
  operational use in an average of 3 minutes.
• Once external system data arrives in the GCCS
  environment it must transition the network within
  the requirements identified in KPP 1.1
  (synchronization, 3 minutes)
• External systems using B8s will be measured as
  good or better than GCCS 3.x

Under a loaded networked environment with 275
network-wide concurrent users at a general ratio
of 60 Query and 40 Update.
19
GCCS-J 4.0 JOPES IOP Sites
20
GCCS-J v4.0 and v4.0.1 JOPES SSE Interoperability
Status
Partial, not all interfaces tested.
21
Force Projection Findings

• Ability to change locked/validated requirements
• Ability to directly update Combatant Commands
  TPFDD
• Inability to translate TPFDD information between
  3.x and 4.x
• Incorrect rollup of cargo
• Transactions not replicating in a timely manner
• Ability to overwrite TPFDD information when
  working on different DBs

22
Certification Status
JOINT
ARMY
NAVY
AIR FORCE
MARINE CORPS
l
(1) ISP being developed (3) Use 4.x I-KPP (5)
CDD being developed (2) I-KPP (4) CPD being
developed
23
Status Reporting

• Standards Conformance Certification
• System is certified for conformance to a standard
• System-level Interoperability Test Certification
• Full system certification. System meets all
  certified interoperability requirements (I-KPP)
• Specified Interfaces Certification
• System meets subset of the certified
  interoperability requirements
• Non-Certification
• System is fielded -- critical operational impacts
  expected
• Provides a warning to the Warfighter
• Interoperability Assessment
• System is not ready for interoperability
  certification, but PM would like to determine how
  well certain interfaces interoperate
• System may lack Joint Staff certified requirements

Reporting Method for 4.0
24
Summary

• Ensure systems are interoperable when fielded
• Ensure warfighters are aware of limitations and
  inaccuracies
• Identify interoperability requirements not
  specified in documents
• Help improve operating procedures

25
Joint Interoperability, Assured Security, Best
Value, Customer Success
Global Net-Centric Solutions -- The Warfighter's
Edge
26
Contact Information

• POC
• Mr. Michael Koester
• C2 Systems Branch/JITC
• Comm [phone]
• DSN 879-4230
• Michael.Koester_at_disa.mil
• koesterm_at_fhu.disa.smil.mil
• Web URLs
• http//jitc.fhu.disa.mil/gccsiop
• http//jitc.fhu.disa.mil/cop
• http//199.208.204.125/gccsiop/index.html

27
Joint Interoperability Directives Instructions
For IT systems, including NSS, ... JITC shall
provide system interoperability test
certification memoranda ... throughout the system
life-cycle and regardless of ACAT.
28
(No Transcript)
29
Categories Environments
30
Test Venues
31
GCCS-J 4.0 Global Interfaces
Interfaces with an are critical. GCSS is not
listed in current TEMP Annex. Italics Can data
be collected during OT or CST event?
32
GCCS-J 4.0a Interoperability
33
C4I COMPLEXITIES
34
Future C2
35
JITC COP Capabilities