One of the DHS's top three goals is (enabling) “A national common operating picture for critical infrastructure”. A congressional directive states “nothing less than network centric homeland security akin to network centric warfare”. The Heartbeat Beacon addresses the interoperability challenge where unique Federal/military situational awareness (SA) systems and Telco networks supporting First Responder public safety systems agree on common settings of three common denominators: (1) TCP/IP heartbeat protocol, system heartbeat, heartbeat beacon, beacon frames . . . (2) heartbeat (XML) messages that convey network configuration data (e.g., router management information databases—MIBs/multicast group subscriptions that can be implemented via transponder beacon technology that increases/decreases the multicast radius corresponding to the DHS threat condition criteria) (3) Common Alert Protocol (CAP) child schemas and/or data islands embedded in the CAP schemas with the option to code small data files as Efficient XML to accommodate extremely low bandwidth connections used by airborne or ground mobile units. When the DOD's system integrators and the world's public safety Telco network providers agree on these three common denominators/building blocks, direct collaboration based on consistent timing of events and common symbology will be achieved. A common symbol set will improve high level emergency action center & muddy boots (tactical) collaboration. Web standards verses decades old military message standards or hybrid solutions limit us to 30 second web screen scrapes that are not useful reacting to 9/11 scenarios. “Timing is everything”.;SEQUENCE LISTINGSee diagram 1, diagram 2, diagram 3, and table 1 of this document. Different scenarios and different situations stimulate different work flow logic and filter logic activation as well as different message sets that are impractical to represent in a single document. Military systems of systems testing comprise hundreds if not thousands of mission threads (analogous to commercial business logic) shown in state, flow and sequence diagrams. Different scenarios flow differently through the enterprise architectures which are different. Speaking to diagram 3, the Heartbeat Beacon in system view, a generic topology was used vice architecture to represent a generic, universally applicable methodology that will be implemented across n complex systems in an application, product, and operating system neutral method. Diagram 1 is a replication of the Army's Army Battle Command System Force XXI Battle Command Brigade
展开▼