The example below illustrates Action Assertions stated in a form of Structured English (pseudo-code). These rules are operational rules because they reflect constraints on the actual business process and not constraints imposed by system design or implementation decisions.   For Each MISSILE TRACK entity instance If MISSILE TRACK boost phase code > 0, Then MISSILE TRACK acceleration rate is non-null Else MISSILE TRACK drag effect rate is non-null And There Exists a MISSILE TRACK POINT entity instance Such That MISSILE TRACK.SOURCE TRACK identifier = MISSILE TRACK POINT.SOURCE TRACK identifier MISSILE TRACK POINT.SOURCE identifier End If End For

The following is an example Action Assertion that might be part of a Systems Rules Model. The assertion is an example of one that might be necessary mid-way through a system migration, when the databases that support three Forms (FORM-X, FORM-Y, and FORM-Z) have not yet been integrated, so explicit user or application action is needed to keep related data synchronised. The example is given in a form of Structured English. If field A in FORM-X is set to value T, Then field B in FORM-Y must be set to value T And field C in FORM-Z must be set to value T End If

SV-10a Systems Rules Model – Track Correlation Rule Example Track #1 Node Value = X Sum of Matching Correlation Weights = X Correlate to Track #1? Track Number Correlation Weight = 25 Track Class Correlation Weight = 10 Correlate to Existing Track? Track Name Correlation Weight = 30 Event New Contact Report Received Correlate to Track #n? Platform Type Correlation Weight = 10 SCONUM Correlation Weight = 40 Track #n Node Value = Sum of Matching Correlation Weights Nationality Correlation Weight = 10 Create New Track? Category Correlation Weight = 5 Pennant Number Correlation Weight = 20 New Track Node Value = 50 Note: Any new terms used should be fully explained in the associated Integrated Dictionary (CV-2) New Track Threshold = 50

SV-10a Systems Rules Model - Example 3 This example shows an extract from the same Situation Awareness System Track Correlation rule as in Example 2, but this time in a form of Structured English. GET CONTACT(New).Properties AND Next Track # SET Correlation Threshold = 50 FOR EACH TRACK(Index) SET TRACK(Index).Score = 0 COMPARE CONTACT(New).Properties TO TRACK(Index).Properties IF Track Number EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 25 END IF IF Track Class EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 10 END IF IF Track Name EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 30 END IF IF Platform Type EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 10 END IF IF SCONUM EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 40 END IF IF Nationality EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 10 END IF IF Category EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 5 END IF IF Pennant Number EQUAL THEN TRACK(Index).Score = TRACK(Index).Score + 20 END IF END FOR FIND TRACK(Z) WITH MAXIMUM TRACK(Z).Score IF TRACK(Z).Score > Correlation Threshold, THEN MERGE CONTACT(New).Properties WITH TRACK(Z).Properties ELSE CREATE TRACK(Next Track #).Properties FROM CONTACT(New).Properties END IF

Tactical Data Links Architecture – Notional Example OV-1 AEW&C AEW&C P-3C SATCOM GBAD F/A-18 COLLINS SS FFG/FFH LEGEND REGIONAL OPERATIONS CENTRE LINK 11 LINK 11 and/or LINK 16 LINK 4A or LINK 16 LINK 16, LINK 11 and /or AADSLINK OTCIXS/TIBS

SV-11 Example – Notional Logistics System LOGISTICS STAFF SUPPLIERS PROVIDES ACTIONS LISTS CONTAINS PLACES LINE ITEMS REQUISITION DETAILS REQUISITIONS FIELD UNITS ORGANISES DELIVERS CATEGORIES TRANSPORT

Communications Interface NODE A SYSTEMS SYSTEM 1 SYSTEM 2 MEANS SATCOM HF UHF VHF MODES VOICE DATA MSG NODE B SYSTEMS SYSTEM 1 SYSTEM 2 SYSTEM 3 MEANS ISDN PSTN SATCOM MODES VOICE FAX DATA MSG Communications Interface Communications Interface SATCOM Interface one-way NODE C SYSTEMS SYSTEM 1 SYSTEM 4 MEANS ISDN PSTN SATCOM HF UHF VHF MODES VOICE DATA MSG SATCOM Interface EXTERNAL CONNECTION

Training (IT Competency) Provision of Resources TOP SECRET Multiple Security Level Information Exchange SECRET RESTRICTED Process IT Service Delivery Training (IT Competency) Provision of Resources Governance Knowledge Management Infrastructure E-mail / Messaging Directory Services Information Security & Assurance Collaboration Information Storage & Management Network Operational Applications Subscription & Delivery Services Computing Platform (Hardware) Administrative Applications Search & Access Infrastructure Management

OV-6c Communications Net Management Example Network Manager Communications/Network Assets C2 Operational Element Configuration Manager Security & Traffic Managers Status Monitor Comm. Node Manager Comm. Node Assets System Direction Configuration Parameters Configuration Parameters Communications Directives Communications Directives Execution Instructions Status Information H&S Messages Exception Report Exception Report (If necessary, reiterate configuration process) Configuration Confirmation

OV-7 Logical Data Model – Notional Example MISSILE MISSILE-Track No (FK) ___________________ MISSILE-Status TARGET TARGET-Track No (FK) ___________________ Gathers information on P ELINT SENSOR EMISSION-Track No TARGET-Track No (FK) ___________________ TARGET-Time (FK) TARGET-Position (FK) TARGET-Velocity (FK) EMISSION-Identity EMISSION-Time EMISSION-Bearing Sends guidance information to Gathers information on P Sends information to Sends information to P MISSILE GUIDANCE SYSTEM MISSILE-Track No TARGET-Track No (FK) ___________________ MISSILE-Time MISSILE-Position MISSILE-Velocity MISSILE-Status (FK) TARGET-Time (FK) TARGET-Position (FK) TARGET-Velocity (FK) TARGET-Status (FK) COMMAND CENTRE TARGET-Track No (FK) EMISSION-Track No (FK) _____________________ TARGET-Time (FK) TARGET-Position (FK) TARGET-Velocity (FK) EMISSION-Identity (FK) EMISSION-Time (FK) EMISSION-Bearing (FK) TARGET-Hostility TARGET-Status SURVEILLANCE SENSOR TARGET-Track No ________________ TARGET-Time TARGET-Position TARGET-Velocity P Sends engagement information to Sends information to

SV-2 Notional Inter-Nodal Example FIXED NETWORK SYSTEMS UHF SATCOM HF SHIP / SHORE INMARSAT MEANS ISDN PSTN SATCOM HF UHF VHF MODES VOICE MESSAGE DATA VIDEO FACSIMILE TASK GROUP SYSTEMS UHF SATCOM HF SHIP / SHORE INMARSAT LIMK 11 MEANS ISDN PSTN SATCOM HF UHF VHF MODES VOICE MESSAGE DATA VIDEO FACSIMILE AMPHIBIOUS TASK GROUP SYSTEMS UHF SATCOM HF SHIP / SHORE INMARSAT LIMK 11 MEANS ISDN PSTN SATCOM HF UHF VHF MODES VOICE MESSAGE DATA VIDEO FACSIMILE 1 2 3 CIVIL ELEMENTS MEANS SATCOM (INMARSAT) MODES VOICE DATA FACSIMILE 4 4 LEGEND INTERFACE DESCRIPTION BANDWIDTH ENCRYPTION 1 Task Group Network 512 Kbps KG-84 2 Amphibious TG Network 1 Mbps 3 Inter-TG Coordination 600 bps / 64 Kbps KG-11 4 Civil/Military Coordination 256 Kbps None