Global Environment for Network Innovations (GENI) 

MISSION-ORIENTED RESILIENT CLOUDS (MRC)Mission-oriented Resilient Clouds (MRC) program aims to address

some of these security challenges by developing technologies to detect, diagnose and respond to attacks in the cloud; effectively

building a ‘community health system’ for the cloud.

“The external environment could update resources at random. One solution is a heartbeat: defining a default lease duration

and delaying updates until the next cycle”

URN

JBFSA

VIOLIN

Synergy with REST Extensions Representational State Transfer

UTO

CAPXML

Big Data

HEARTBEATSENSORS

NIST

Equitably Metered <arbitrage>Process by Precedence Resource Class / Priority

SYNCSEED_CLOUD

Agile Self Organizing Federations For Common Goals / Arbitrage Synchronized in Time / Space

S2COP<filters>

 BAA-09-04

Dynamic, Emerging Events and Situations

Across time and space

Network Centric OperationsIndustry Consortium

EVENT ALERT

HEARTBEACONCYCLE

.0001 .05 .01 .1 5 15 30 99

- Set micro-cycle heartbeat state meta data snapshot sync delta interval / window

- Get data prior to data fusion center insertion

Adaptive Federation

Self Organizing:- Reporting Cycle- Directory LDAP- Maps Geo-Spatial

Self OrganizingSystemsOf Systems

<StratML>

Community = ORG ID

Operational Intelligence

Heartbeat beans

DRUPAL: PROJECT HEARTBEAT WORLD BANK API

NIST TIME SERVER

Grant # 0205724Equitable = consensus

AxiomaticTheory of

Economics

ax·i·o·mat·ic ENERGYINDEPENDENCE

PERIODIC / SYNCHRONOUSHEARTBEAT

THE TCP/IP INTERNET HEARTBEAT IS AN OPPORTUNITY / INTERVAL IN TIME TO PERFORM / NOT PERFORM COMPUTATIONAL TASKS

START / STOP / TIME TO LIVE

MASTER CONTROLLER DISTRIBUTED ALGORITHMS

HEART BEAT MESSAGES

MILITARY K00.99 HEARTBEAT MESSAGE- Many Heartbeat messages form SYNC DELTA

USED FOR HOP COUNTIN INTERNET /

ENERGY PROTOCOLS

STATE META DATA SNAPSHOT CLOUD TERM- Checks for changes from time a to time b

Financial Information

eXchange (FIX)

Society for Worldwide Interbank Financial Telecommunication

SWIFT

START

STOP

TTL

802.11

.0001 .05 .01 .1 0 5 15 30 99SENSORS

IEEE C37.118

IEC 61850 IEEE 802.1AG

CHECK STATUS ACK / NACK

GET DATAPUT DATA

NIST TIME SERVER

SNAPSHOTS

EVENT ALERTSMART GRID - CLOUD

• Time Synchronization: IEC 61850 Objects / IEEE C37.118 Harmonization & Synchronization

– Time synchronization required across Smart Grid applications www.nist.gov/smartgrid/.../13-Time_Synch_IEC_61850_and_C37118_ Harmonize.pdf

– Specifies heartbeat update Interval in milliseconds

• IEEE C37.118 Interface:– If a PDC or PMU indicates a data quality or time

synchronization issue– interfaces.osisoft.com/osiif/docs/C37118/PI_C37118.doc

• PMU Measured data time-stamped IAW C37.118

• Specifies heartbeat Update Interval in milliseconds and must be the same on both interface computers

• Phase 2: shared file must store data for 5 failover tags: (1) Active ID (ORG ID / URN)(2) Heartbeat 1.(3) Heartbeat 2.(4) Device Status 1.(5) Device Status 2.

Tag ExDesc digitalset

“UniInt does not examine the remaining attributes, but the point source and location1 must match”

ActiveID [UFO2_ACTIVEID]

IF1_Heartbeat(IF-Node1)

[UFO2_HEARTBEAT:#]

IF2_Heartbeat(IF-Node2)

[UFO2_HEARTBEAT:#]

IF1_DeviceStatus(IF-Node1)

[UFO2_DEVICESTAT:#]

IF2_DeviceStatus(IF-Node2)

[UFO2_DEVICESTAT:#]

IF1_State(IF-Node1) [UFO2_STATE:#] IF_State

IF2_State(IF-Node2) [UFO2_STATE:#] IF_State

HeartbeatMessage asState meta Data snapshot

Firefly Heartbeat Sync

SYNCSEED_CLOUD

.0001 .05 .01 .1 5 15 30 99- Set micro-cycle heartbeat state meta data snapshot sync delta interval / window- Get data prior to data fusion center insertion

Self Organizing:- Reporting Cycle- Directory LDAP- Maps Geo-Spatial

Self OrganizingSystems Of SystemsSupported by a Network of networks

MILITARY MOBILITY RESEARCH+ NON PROFIT STANDARDS

STOCHASTIC HARMONIZATION

Agile, adhoc join, dropsInto federated groupsas merger / acquisitionAlternative / arbitrage

Search, ID potentialusers indicating

willingness to affiliate into federated groups for

agile, adhoc, equitable trade arbitrage based on

Sync’d predicableState meta Data

Updates intervals Prior to data fusion center

<URN> <Org ID>

BUILDING

B1: BUILDING BLOCK 1: TCP/IP HEARTBEAT TIME STAMP & DATA GET / PUT OF ORG ID / URN IN MICRO / MACRO CYCLES PRIOR TO DATA FUSION CENTER INSERTION

B2: BUILDING BLOCK 2: ADAPTIVE, CYCLIC, ITERATIVE PROCEDURAL TEMPLATES: XML ARTIFACTS i.e. UNIT TASK ORDER & K00.99 HEARTBEAT SYNC DELTA MESSAGES / STATE META DATA SNAPSHOTS IN NETWORK EXECUTION MANAGEMENT MARKUP OF SERVICE INTERFACE ARTIFACTS

LEADER”S INTENTDECISIONS

ADHOC / AGILEFEDERATED <ID> GROUPS SYNC’DIN TIME / SPACE

B3: BEACON TECH TYPE I: PAUL REVERE LINEAR, SEQUENTIAL HOP COUNTS

B4 BEACON TECH TYPE II: WATER DROP IN POND RADIUS, CIRCUMFERANCE GEO SPATIO-TEMPORAL

SYNC DELTA

DISTANCE, THRESHOLD,

INTENSITY, DURATION

TASK ON / OFF

S.O.S

SYNC DELTA METRICS IN SLA CLAUSES AS MOE, MOP METER IN TAX CODES,TRANCHE CLASSES / RATINGS ARBITRAGE TRIGGERS

MAP VIEWS GEO-LOCATION SPECIFICSHOW SYNC DELTAS BY <GROUP> / RESOURCE TYPE, EVENT, ALERT / NEWSCAST BY TRANCHE <CLASSES>

UTO

SNAPSHOTS

TF BIZ

APPLIQUE’ OVERLAYS

< / >

FEDERATED GROUP JOINS, MERGE, ADDS, DROPS

SEARCH FOLLOWED BY ARBITRAGE INVITES VIABEACON NEWSCASTS. INVITE ACROSS SPACE / TIME

BLOCKS

NEWSCAST.0001 .05 .01 .1 5 15 30 99

PERIODIC / LOCAL HEARTBEAT EVENTS

ARBITRAGE INVITESProcess by Precedence

MICROCYCLES

MACRO CYCLES

.0001

SYNCSEED_CLOUD

EQUITABLEMETER / METRICS

Interface Name HEARTBEAT Administration Interface [SCOP]

DocumentationURL

http://scop.sourceforge.net/http://www.linuxvirtualserver.org/software/index.html

API Information Functionality Areas Cloud Interface Management, configuration, start, stop cloud services, edit configuration (heartbeat messages)

API Operation Count

Web service access type Web application, front end to [network, device, system] heartbeat]

Language/platform bindings

PHP

Important Interface Characteristics

SCOP is a web application, PHP based, that is a front-end to heartbeat, IP Virtual Server ipvs and ldirectord [check interval e.g., every 5 seconds] software. With SCOP you can start/stop services, view/ edit configuration files e.g., heartbeat message state management snapshots, make backups, take a server online/offline, add/ remove virtual/real servers, etc.

“The external environment could update resources at random…One solution is a heartbeat: defining a default lease duration and delaying updates until the next cycle”

Uniform Resource Name URN

RANDOM: University of Italy, Bologna / University Romania Study proposing using firefly inspired algorithmsTo harmonize stochastic networks – idea isWhen fireflys in a geo-spatial temporal intensityDefined area described by HBC water drop in pond, Paul Revere metaphors Reach a consensus to Closest matching HBC,

Decision to sync to HBC Cycle is made..

NIST TIME SERVER

"what we are interested in is guaranteeing all nodes start and end their cycles at the same time"

Firefly-inspired Heartbeat SynchronizationHARMONIZE STOCHASTIC NETWORKS

.0001 .05 .01 .1 5 15 30 99 .0001 .05 .01 .1 5 15 30 99ORG ID URN

SYNC PULSE

HEARTBEAT EVENT

IEEE 1588

HEARTBEACON + HEARTBEACON INSPIRED FIREFLY SYNC / NEWSCAST PEER SAMPLING SERVICE ACHIEVING STASITICAL MEAN / AVERAGE AGREEMENT TO SET STATE META DATA HARVEST CYCLES LEVERAGING BEST OF BOTH APPROACHES TO HARMONIZE STOCHASTIC NETWORKS REDUCING JITTER IN HIGH AVAILABILITY NETWORKS

CLOUD

“Heartbeat Synchronization strives to have nodes in a distributed system generate periodic local “heartbeat” events approximately at the same time. It differs from classical clock sync in that Nodes are not interested in counting cycles And agreeing on the ID of the current clock cycle. There is no requirement regarding the length of a cycle with respect to real time as long as the length is bounded and all nodes agree on it eventually..”

PERIODIC / LOCAL HEARTBEAT EVENTS

FLASH MESSAGES

EVENTTRIGGERFLASHMESSAGE

NEWSCAST PROTOCOL

CYCLE SYNC

EVENTTRIGGER

EVENTS

PERIODIC / LOCAL HEARTBEAT EVENTS

CYCLE SYNC

STATE META DATA SYNC DELTA MESSAGE SNAPSHOTS

STATE META DATA SYNC DELTA MESSAGE

SNAPSHOTS

NEWS CAST

PEER SAMPLING SERVICE

URN Uniform Resource Names (URNs)A Uniform Resource Identifier (URI). Both URNs (names)

and URLs (locators) are URIs, and a particular URI may be a name and a locator at the same time.

RFC 2141 International Engineering Task Force IETF: The Functional Requirements for Uniform Resource Names are described in RFC 1737. URNs / Uniform Resource Characteristics (URCs), Uniform Resource Locators (URLs).

Each plays a specific role:

- URNs IDENTIFICATION (SENSORS, DEVICES)

- URCs INCLUDE META-INFORMATION

- URLs LOCATE / FIND RESOURCES

- SEARCH ON URN -- AUTOSCALE BY ZONE

ORG ID URN

ADHOC TASK FORCE ORGANIZATION – SPONTANEOUSINTEGRATION - MANEUVER NETWORK

SYNCHRONIZE IN TIME / SPACETO ACHIEVE GOALS: HARVESTPERISHABLE COMMODITIES TRANCH CLASSPOOL BIDS ON COMMODITIES / GOODS ORG ID / URN

TASK ORGANIZEADD / SPLIT / DROP

EQUITABLE, RELIABLE, PREDICABLE SYNC DELTA UPDATEs REFRESH UNIT TASK ORGANIZATION UTO USING TEMPLATES AS MESSAGE DOCUMENT / ARTIFACTS

GEO LOCATION& STATUS = MOVING..

TASK ORGANIZE

AGILE PARTNERING

FEDERATE COOPERATE& GRADUATE

CONCEPT OF OPERATIONS CONOPSSCHEME OF MANEUVER

“JOHN MADDEN CHALK BOARD”

BUSINESS PLAN ALTERNATIVE TO MERGERSE.G., TASK FORCE EARN BLING

APPLIQUE’INTEL OVERLAY

SECURITYFILTER COP

BY ROLEBY RULES

ORGANIZATION IDENTIFIERS: ORG IDBUSINESS, NON PROFIT, CORPORATION OR GOVERNMENT ENTITY IN INTERNET NUMBERS DATABASE -- ARIN AMERICAN REGISTRY

VIEWS BY EVENT,

ACTIVITY, LOCATION

CLASSGEO-SPATIAL

TEMPORALINTENSITY

StratMLIODEF-RID TAGS = Classes

< TAG >

< TAG >

STATE META DATA SNAPSHOTS / HEARTBEAT SYNC DELTA MESSAGES

Before data fusion center

TASK ORDER

< TAG >

SEARCH, FIND INVITE TO ARBITRAGE NEWSCAST, BEACON BROADCAST

FEDERATE

UTO

< TAG >

<Task Force_BLING>

3.2 REST: REpresentational State TransferTo ground our exploration of these new issues, we began by restating REST to verify that it could induce the property of consensus. Our more-rigorous correctness argument elucidated that REST depends on synchronized global clocks to ensure leases expire simultaneously. Synchronization still presumes that every response message specifies its lease interval. Many real-world ORIGINSERVERs do not specify when the next permissible resource update is scheduled. The external environment could update resources at random (e.g. editing a file “by hand”). One solution is a heartbeat: defining a default lease duration and delaying updates until the next cycle.

NSF REST extensionsAnd Heart Beacon CycleBuilding blocks / coreFunctions both focus onUpdating state over a Distributed, wide areaCloud computing / gridEnvironment where a Global clock – in thisDiagram, National Institute of StandardsAnd Technology NIST’sTime Server providingSync pulses to networkTime sync equipment e.g., Symmetricom..

NSF’s REST ORIGIN SERVER corresponds with NIST TIME Server

State meta data snapshots are sampledIn micro-cycles aggregated / “summarized”

The impossibility of consensus is considered to be one of the most fundamental results of the theory of distributed computing [30].

That is, the follower’s value must become equal to the leader’s before it changes. In Figure 2, where world-lines are drawn vertically for the state of the leader and follower processes, this only holds in the shaded region. Note that the second message’s lease expires before it even arrives. In general, it is impossible to guarantee simultaneous agreement for any centralized resource that changes more frequently than 1⁄d times per second.

The Heart Beacon Cycle in comparison is a procedure derived from Military units affiliating / de-affiliating in an adhoc, agile fashion based onLeader decisions where followers (subordinate units) are added and Subtracted from network subnets based on operational situational Plans of maneuver that must be translated into networking changes. Heartbeat messages / sync delta messages are used to convey state updates

UTO

Simultaneous Agreement = federation

SYNCDELTA

The main goal of the Heart Beacon Cycle is to help individuals organize into federated (centrally managed) groups using resourcesIn equitably metered trade arbitrage using new elements synchronized by a global clock (NIST Time Server)

“New Elements” in the Heart Beacon Cycle are consensus within federation to use Organizational ID’s / Uniform Resource Names

A “new” constraint is that the state meta data gathered during heartbeat get / puts must occur prior to data fusion center insertion

Expiry deadlines are defined by micro-cycles which operate within and update longer, operational macro-cycles

Consensus is formed within the federated groups using universally applicable change from null sync deltas measuredBy hop counts linearly and sequentially by a Paul Revere metaphor or in an area / radius by a water drop in pondMetaphor that will assist with geo-temporal intensity measurements and appliqué overlay renderings on decision Support screens that are updated within operational macro-cycles keeping leaders apprised of situational awareness

If, during a “watch” cycle, an entity or resource doesn’t report, it’s icon is gradually faded and eventually removed

NIST TIME SERVER

While A+REST tackled the essential challenge of latency, message routing will focus on improving REST’s support for multiple agencies. The specific property we intend to induce is multilateral extensibility: the ability to add functionality to an application using components owned by several different agencies. The complication is that new 3rd and 4th parties may be trusted by the original client or server, yet distrust each other.

Figure 3 illustrates how the combination of Asynchrony and Routing leads to the highest performance: triangulation. It depicts five approaches to the problem of computing FA(GB(XC))):

The Heart Beacon Cycle addresses“multiple agencies” by stipulating thatConsensus is reached using establishedLibrary’s of tag sets (e.g, NationalInformation Exchange Model NIEM) And DoD’s Strategic Markup LanguageAs examples where the tagging Strategy unique identifies “differentAgencies”. The Heart Beacon Cycle Further extends this concept by Associating agency type and placementBy priority for precedence processing

CAPXML

CAP = Common Alert Protocol OASIS

“provided by multiple agencies” – addressed as Stated in previous slide 10 using XML markup toStratify organizations / agencies where organizations/ agencies are uniquely identified by ORG IDAnd agency resources are identified by URNPrior to data fusion center insertion followingThe network enabled operations model usingA heartbeat to gather state meta data forAggregated snapshots at the device level

ARRESTED cites store andForward end to end xmissionAnd acknowledgement Ack / nack.

Assessor component

Heart Beacon Cycle:Derived from military Situational awarenessSystem that uses a Publish subscribe method

Frequency of updates dependsOn network throughput whereThe smaller the connector, theLess frequent the state meta dataRefresh update cycles

“NOW HORIZON”

NIST TIME SERVER

Heart Beacon Cycle’sState meta data gatherDuring micro-cycles Refreshing operationalMacro-cycles in a Synchronous, predictable,Reliable manner helpsSupport establishmentOf consistent, reliable“NOW HORIZON’S”In NSF ARRESTED Paradigm.

Inertia – of trackedPlatforms, entitiesDetermined byReporting / non-Reporting duringN, n +1 micro-cyclesWhere entitiesPlatforms declared“stale”, inop overTime

Classified ad = newscast, beacon Broadcast of invitations to participate In federated group arbitrage where trade is traded equitably metered by consensus using changes fromThe last sync delta update where unified event / alert trigger is enabled By StratMl conventions and NIEM payloads in CAP schemas

COMMON SYMBOLS

III

THE BIG REDBUTTON

II

SYNCHRONIZEDEVENTS /

ALERTS

I

CAP

NIEM XML Payloads - child schemas - data islands - data files/Efficient XML

Users / platforms / sensor nets are joined, moved, Added, deleted on a adhoc, agile basis based on Needs by decision makers referring to whom is doingWhat with whom in a temporal snapshot displayedOn appliqué decision overlay dashboards referring to Sync matrix activity tables (Excel spreadsheets)

Agile, adhoc joins into federated groups may be Modeled and simulated prior to real world use = Assessment of concepts. “rare” or restricted itemsAre marked by appropriate <tags> e.g., StratMLNIEM etc and processed by precedence

Since ARRESTED is an event-based architectural style, the first phase of developing a decentralized application is still generic event-based analysis: identifying the components, event sources, subscription qualifiers, message formats, and the like. The second phase is a methodology specifically addressing unique concerns raised by decentralization. We propose five steps:1. Identify the agencies. In any real marketplace, the interests of traders, brokers, and the exchange diverge significantly. Note that a single organization may develop the software used to enact all of these agencies’ roles, but the design must remain robust in the face of independent implementations. Part of the challenge of developing architectural styles for decentralization is coming up with abstract models of software written by others.2. Characterize latencies. both networks applications run on top of, and of the real-world phenomena that it is attempting to represent. The latter may be more challenging: it may appear that the NYSE’s ticker stops updating weekend stock’s price but the “afterhours” valuation may keep changing as news breaks.3. Establish web of trust. This requires more than authenticating credentials for each agency; it also determines which external resources ought to be considered “equivalent” to the same concept.

This could range from lexical matching to ‘Semantic Web’ tags .4. Eliminate remote references. This is the constraintunique to the ARRESTED architectural style: replacingall resources owned by external agencies with privateassessments. Architects face tradeoffs between differentprediction engines, compression engines, and other typesof estimators; our style at least isolates such complexity.5. Track the provenance of events. In an era of profligatecomputing resources, event notification is anappropriate use of surplus bandwidth, and audit trails arean appropriate use of surplus storage. Ideally, everydatum displayed to a user interface ought to indicate itsconfidence interval. Furthermore, tracing ownership is essential for re-evaluating results after security breaches,cancellations, or anti-messages invalidate past data

Heartbeat ProtocolSubnet level

“publish, subscribe”get from, send to

data from target hosts, platforms, & computer devices

Increase Multicast Zone

Event/Alert Level Increase / Decrease …

CAPXML

EXCELTable = Sync Matrix

NIST TIME SERVER

6.2 Alternative Approaches to DecentralizationThe challenge of decentralization recurs at many layersof abstraction in computing, from hardware to software:Asynchronous VLSI. As semiconductor performanceincreases, it will become impossible to distribute a clocksignal across a processor die, much less an entire systembus. This requires new kinds of ‘self-timed’ circuits [41].

Control theory. The study of feedback systems, alsoknown as cybernetics, resulted in rules for assessingsignals and estimating state with observer variables [40].

Internetworking. The breakthrough that permits interconnectionof autonomous LANs is the end-to-end hypothesis:the notion that even an unreliable core can be usedto synthesize reliable services, even without signaling.

Middleware. Application integration, even inside asingle organization, faces barriers of interoperability andperformance that led to a vast array of design patterns for

message-oriented & event-based communication [38].

Mobile Systems. Caching and replication are optimisticstrategies for managing inconsistency in disconnectedoperation, such as Bayou [7] or the Coda filesystem [25].

Software Architecture. Other researchers in the fieldhas also described styles for managing latency, such asprocessing real-time news and data streams [35].

The heartbeat is an opportunity in time to do / not do computational tasks e.g., Get / put (CRUD) of data. Therefore, the Heart Beacon Cycle dovetails withARREST yet accounts for potential interaction with NON-ARREST compliantStrategies / protocols / algorithms.. Everything..

2.1 Latency Latency makes simultaneous agreement impossible in many real-world situations. Consider how it affects a stock traded on the (distributed) NASDAQ market. A stockbroker in London interested in knowing the current price of the stock consults a server that broadcasts its current price. Internet delays range up to two seconds, or worse. If actual price in New York were changing at up to 1 Hz, it would become impossible for the London stockbroker to know its current price. Concentric circles in Figure 1 represent latencies (on a logarithmic scale). Radii are correlated with distance, & also determine the maximum update rate of an event source. We call this the ‘now horizon’, since it demarcates which components can reliably refer to the value of a variable ‘right now.’ Latency limits: propagation delay, bandwidth, and disconnection (longest tolerable interruption).

The heartbeat is an opportunity in time to do / not do computational tasks e.g., Get / put (CRUD) of data. Therefore, the Heart Beacon Cycle dovetails with ARREST yet accounts for potential interaction with NON-ARREST compliantStrategies / protocols / algorithms.. Everything..

Heartbeat / Heartbeat Messages Are the Foundation for stock exchange, military, First ResponseEtc. systemsAnd is THEOnly wayTo start, stop,TTL (complex)Processes and HFT algorithms

-1- 2- 3- 4 1 2 3 4

UC BERKELEYSEA GULL PROTOCOL

WATER DROP IN POND / PAUL REVERE METAPHOR HOP COUNT METRICS, MEASURES, AUDIO VISUAL, VIBRATE CUES

METER CHECK TIME STAMP 1METER CHECK TIME STAMP 2

HEARTBEAT SAMPLES SYNC DELTAS < / = / >

IEEE 802.1AG HOP BY HOP DETECTION - IEEE 802.11 HOP BY HOP CONTROL

SEARCH BY RADIUSIN SYNCHRONOUS TIMES STAMPS BY ORG ID / URNTHEN NEWSCASTSYNC DELTAS

HOP COUNT METER / METRICS SLA / E

- IEEE C37.118 Harmonization, Synchronization heartbeat data pulses

SNAPSHOTS

- IEC 61850: Distributed Energy Resources (DER)

CANDLESTICKS

OPEN

CLOSEHIGH

LOW

LOANPOOLS

B B B B

FEDERATE INTOBUYER GROUPSBY ORG ID / URN

AAA/Aaa

AA/Aa

A/A

FIRST LOSS

LAST LOSS

BBB/Baa

B/B

EVERY

GOOD

BOY DOES FINE

INFOCON1

INFOCON2

INFOCON3

INFOCON4

INFOCON5

NEWSCAST

100

200

300

400

5005

4

3

2

1

RIS

K C

OR

RE

LA

TIO

N

AGGREGATEAVERAGESTATISTICAL MEAN

ARBITRAGE

ROUTE <PROCESS>BY <PRECEDENCE>

TIME/SPACE

<UNIFORM RESOURCE NAME><ORGANIZATIONAL ID>

ALERT LEVEL INCREASE / DECREASE BY THRESHOLDS & TEMPORAL FREQUENCY, ACTIVITY INTENSITY

THRESHOLDTRIGGERS INCREASE

BEACON BROADCASTAREA / RADIUS

IN ZONES e.g.TRANCHES

NUMERICALLY / GEO-SPATIAL,

TEMPORALINTENSITY

HOMELAND SECURITY ADVISORY SYSTEM

LOW/NORMAL

GUARDED/ALPHA

ELEVATED/BRAVO

HIGH/CHARLIE

SEVERE/DELTA

EVERY

GOOD

BOY

DOES

FINE

RESPONDERS

COMBINED COMMUNICATIONSELECTRONICS BOARD CCEB

EVERY

GOOD

BOY

DOES

FINEFLASH OVERRIDE

FLASH (Z)

IMMEDIATE (O)

PRIORITY (P)

ROUTINE (R)

ALERT LEVEL CHANGES

CAPXML

INFOCON LEVELS OF CONCERN

INFOCON 1

INFOCON 0

INFOCON 2

INFOCON 3

INFOCON 4

CHILD SCHEMAS, DATA ISLANDS

-8 TO -5 - 4 TO -2-1 TO +2 +6 TO +8 +3 TO +5

CAPXML

AL

ER

T L

EV

EL

IN

CR

AS

E…

> N

EW

CA

ST

ZO

NE

TRIGGERS

EVENT SEVERITY INDEX TRACK BY ORG ID / URN

COLOR CODE CONDITION LEVEL

GREEN

BLUE

YELLOW

ORANGE

RED

LOW

GUARDED

ELEVATED

HIGH

SEVERE

5 LEVEL ALERT SYSTEM

PLANNING

- CHECK- REVIEW

INCREASESURVEILLANCE

TAKE PRECAUTIONSCOORDINATE

W/OTHER GROUPS

CLOSE FACILITIESSTOP PROCESSES

SEVERITYMETRICSTEMPLATE

NIEM

REPLACEMENT SHEET

MARKET BUBBLEFLUCTUATIONS

5

4

3

2

1100

200

300

400

500

RIS

K C

OR

RE

LA

TIO

N

AAA – BBB - D

RATINGS ARIBITRAGECOLLECTIONS DEFINEDBY WATER DROP CLUSTERS

TIME / SPACE / COUNT

602

603

604

+ 1

+ 2

+ 3

+ 2

+ 3

606

601

605

607

Law of Time . org

Starburst Foundation . org

UNIFY / FEDERATE