Application · emergency operations

OpenEOC: the whole incident in one memory.

A command centre, field teams, hospitals and ambulances, the radio log with its ICS-309 numbering, positions on a map, assignments, announcements and messages. FrogNet’s own application, written fresh and GPL-2.0-only, measured against the open-source OpenEOC’s screens, words, forms and test suite.

The application family

As many RAMs as it needs.

The general RAM

Everyone in the application joins it: positions, the roster, the radio log, the mission and assignments, announcements, and messages between teams.

Team RAMs

Each team has its own RAM for its own data and its team messages. A team’s host is the one its lead designates: the lead’s device or the SystemRam’s host.

Every RAM is a role

The host that serves each one is chosen by OpenEOC’s selection over the capability tuples. After a split, the selection activates a host on each side; at the merge, owners reassert and the log comes back together.

Desktop and phone

The same pages on Windows, Android and the node.

The EOC runs on the Windows app and first responders on the Android app; both open the same node-served pages. Each device writes its own presence with its position: the phone from its GPS on every fix, a desktop from Windows’ location service when it has one. Nothing is made up.

Measured

What the first cut did with two posts and a phone.

A real rina-host, two posts (each a node’s web server), three devices in Chromium. RESULTS.md

Stock OpenEOC’s equivalent of the uplink cut is a Report Packet: a file carried by hand and merged on the other device.
checkresult
an entry typed at post A, on post B’s radio log209 ms
two scribes logging at once, 25 entries each54 on each screen, 54 distinct numbers, the same order on both, 7.5 s
a new position logged at A, on B’s map236 ms
post B’s uplink cutB keeps logging on its own RAM
B’s uplink backB’s cut-off entries on A in 7.1–7.5 s; 58 rows on both
the board on a fresh phone, nothing set upall 58, newest first, every team’s last word
Administration

Login is a read.

The application’s access definition, its teams and their password verifiers, is in its configuration tuples, so a device’s own edge checks a login by reading them. There is no login server. A device keeps its role and writes its access record again after every RAM change, so nobody has to do anything after a split or a merge. App setup and operation

The code

pathwhat it is
opt/fdf/src/fdf-source/fdf/www/openeocthe application’s pages
opt/frognet_semantic/ribbit/examples/openeocthe plan, the suite map, the results, deployment
opt/fdf/src/openeoc-app/README.mdthe desktop and phone application and its release notes

FrogNet for emergency operations covers the wider case.