Sequence of events:
Sequence of events Coalition Cmdr asks for candidate services to locate enemy sub
UT asks DAML-S Matchmaker for candidate ASW resources in or near Red Sea region
Uses utility model to choose Arabello as best resource, informs Cmdr
Option of showing how policy is used to filter matchmaker results
Coalition Cmdr negotiates with Arabello (off line) to get agreement to join coalition
Coalition IT support specifies policies for Coalition interactions with Arabello
Policies include restrictions on content on IP/IR messages that can be seen by Arabello
Arabello Cmdr establishes JTF,
Arabello IT creates domain and policies for Arabello JTF (ATJF)
AJTF cmdr selects air component, maritime component officers, on agreement to join they get added to the domain (populated by some combination of JTF Cmdr’s assistant agent and KPAT)
CJTF provides initial tasking to air, maritime officers
Maritime task to locate sub, Air task to send helicopter to do recovery assistance for Australian ship
Maritime officer tasks undersea intel officer to monitor for subs using fixed sensors
Maritime officer issues IP for sub activity
Maritime officer shows sub activity on GUI
Maritime officer issues IR for sub location prediction
UMD Sub Position Prediction (SPP) agent responds with IP to supply this information
Continued:
Continued Maritime CMDR subscribes to US SPP (UMD) to anticipate sub location
UMD sends IR for recent sub sightings thru coalition to Arabello
UMD receives IP from Arabello Maritime Agent thru coalition (simultaneously)
UMD subscribes to Maritime Agent, receives position info (not blocked by policy)
UMD receives updated position info from Arabello Maritime officer, generates prediction, sends to Maritime Agent
Arabello Maritime Agent sends ships to follow sub.
Show how IP/IR messages restricted by coalition domain do not reach Arabello