|
The Heart
Beacon Quad Chart: 3 Common Denominators Agreement on 3 standards
defining situational awareness (SA), event & alert data exchanges among N complex systems resulting in a global SA engine
/ SA tone. 3 components / common building blocks: I TCP/IP heartbeat
protocol gathered / harvested state Meta data. Consistent, synchronous timing of platform - device state meta-data collection
using the heartbeat / beacon's intrinsic millisecond - 99 minute timing function enabling consistent, synchronized collection
of raw state meta data (geo location, moving, halt, straggler, duress, IP address, unit / org Universal ID) BEFORE transfer
to queues, SANS, dbase... prior to distribution / dissemination then data fusion improving filtering / intelligence fusion.
Once the time tagged data from multiple, disparate sources, the opportunity to apply network discipline to the gather of this
data is gone - the window of opportunity closed. The ability to provide a single, authoritative, data fusion and filtered
Single Integrated Synchronous Operational Picture or SISOP cannot be achieved without first applying the simple fundamental
discipline at the platform level. II "Maneuver the network": Collected
state meta data enables network management of router Management Information Bases MIBs by installing network router MIB updates
for spontaneous (re) organization split, join, adds via multicast - any cast broadcasts of heartbeat harvested state meta
data (geospatial location, status: moving, halt, URN, Org ID, Universal ID) . The Heart Beacon process will functionally enable
re-planning of missions dynamically. It will allow the planning/re-planning processes to be reengineered on the fly to interleave
them with cross-domain execution monitoring with automated planning decision aids. Heartbeat network (re) configuration XML
schemas / messages III Chop chain - XML workflows - business logic over multicast
/ any cast IP using "true cots" tools i.e., Towersoft w/AgileDelta Efficient XML module embedded with the Common
Alert Protocol CAP (XML child schemas and or data islands / embedded files ) broadcasted by multicast of events, alerts via
a unified alert / event trigger mechanism. Common Alert Protocol CAP child schemas with embedded data islands / NIEM payloads
applied as a single, unified trigger mechanism (e.g., the big red button) for alerts customized for Community of Interests
(COI) QUAD CHART 4 IT FOCUS AREAS:
1. Establish consistent timing and synchronous state meta-data collection.
Use the heartbeat / beacon’s (terms used interchangeably) intrinsic millisecond - 99 minute timing function to enable
consistent, synchronized collection of raw state meta data (geo location, moving, halt, IP address, unit / organization Universal
ID) BEFORE transfer to queues, SANS, dbase... prior to data fusion activities to improve filtering / data intelligence fusion.
Use the heartbeat / beacon function (send to / get from devices, platforms...) as a subnet publish-subscribe e.g., OSD Horizontal
Fusion to temporary holding areas awaiting harvesting by more advanced data collection / replication mechanisms that in turn
rely on the heartbeat beacon mechanism e.g., OPenDAP, DARPA’s Cougaar, UMTS cellular, mesh networking standards ZIGBEE,
ZWAVE….
2. “Maneuver the network” Use collected state meta data enabling network management
of router Management Information Bases MIBs installing network router MIB updates for spontaneous (re) organization split,
join, adds via multicast - anycast broadcasts of heartbeat harvested state meta data (geospatial location, status: moving,
halt, URN, Org ID, Universal ID…)
3. Instantiate National Command Authority NCA chopchain - workflows –
business logic over multicast / anycast IP using “true cots” tools in use e.g., Towersoft w/AgileDelta Efficient
XML module embedded via the Common Alert Protocol CAP (XML child schemas and or data islands / embedded files ) to support
the multicast, unicast, or anycast distribution of events, alerts via a unified alert / event trigger mechanism – the
OASIS Common Alert Protocol with child schemas and / or data islands conforming to DHS OPEN: Open Platform for Emergency Networks
to adjust to Communities of Interest (COI's) special needs.
4. Apply beacon technology to enable millisecond data
exchanges vice 30 second screen scrapes while increasing / decreasing radius of disaster / event / alert radius represented
by multicast zones corresponding to US / UK... five level advisory systems
Enable across N complex systems, Y networks
("network of networks") and Z systems ("system of systems")
|
