Capabilities
What NEMESynth-EMSO brings to each part of spectrum operations, from decision support to decision automation, and where each piece stands. It's the planning and decision side of the house. It does not sense or transmit. Where sensors or radios do the work, NEMESynth-EMSO supplies the data they use.
Built In progress Planned Proposed Draft
1. Electromagnetic support and tactical surveillance
A sensor can tell you there's energy on a frequency. Whether that's a problem depends on whether someone is authorized to be there. If nobody is, it's interference or a threat. If somebody is, it's probably one of ours.
| What you need | What you get | Status |
|---|---|---|
| Know what's friendly before you call something hostile | Every assignment in force right now, by frequency, area and time, straight from the SFAFx record. | Built |
| Get what sensors hear into the picture | A sensor's waterfall arrives live over the data network into the Spectrum tab, on the exercise clock. Each reading is to be kept with its source and marking and checked against the assignments, to flag anything that shouldn't be there. | Live waterfall Built; checking against assignments Planned |
| Cheap sensing at the edge | A small receive-only SDR node that sweeps channel power, does the processing itself, and sends back only short updates. Its waterfall images carry the colour table and a pointer back to the original recording, so full analysis can go back to the source. | RTL-SDR node Built, uncalibrated; calibration Planned |
| Work with other people's sensors | A partner's sensor publishes to the shared network; NEMESynth-EMSO fuses and displays what it reports and can send it taskings. | Proposed |
| Usable by Soldiers who aren't EW specialists | Plain-language help, commands you can type in ordinary words, an assistant that explains what it's doing, and status where you're already looking. | In progress |
2. Autonomous network management
NEMESynth-EMSO does most of its work here: assigning frequencies as things change, and carrying out PACE plans without someone working the phones.
| What you need | What you get | Status |
|---|---|---|
| Dynamic frequency assignment | An optimizer (HiGHS) that fills requirements by priority, highest first, keeps conflicting pairs apart and holds back alternates. The problem is laid out in plain tables, so you can see why each assignment was made. | Built for planning; reassigning live Planned |
| PACE that runs itself | Four separate means for every net, checked to close for the whole operation, and a PACE board that shows where each net stands and why each move was made. The rule for when to switch is a decision sheet, and an interference report on a net's channel is one of its inputs. | Built |
| Switches that fire at the right time | Triggers that go off from the exercise clock or real time, from scheduled changes and from events. The time bar drives the rule engine's clock. | Exercise clock and events Built; real time Planned |
| PACE carried out on the real network | A switch is sent as a command to the network manager that owns the radios, and its answer comes back into the record. NEMESynth-EMSO tells the manager what to do; it never keys a radio itself. | Planned |
| Networks that heal themselves | Finds where a network would split, which links are single points of failure, and which paths can take over, from the wired and wireless links on record. | Planned |
| Open architecture, no vendor lock | A C library you talk to in SQL, open formats (SFAF, SFAFx, GeoPackage, DMN decision tables with S-FEEL cells), no license server, and every engine swappable. Built to MOSA principles as software for CMOSS-class computers. | Built; interface control document Proposed |
| Keep the enterprise and the edge in sync | Sealed SFAFx sets that apply as changes in either direction. A node that's been cut off catches up from the sets it missed. | Sets Built; node sync Planned |
| Keep an eye on every node | Tracks the network connection, how old each feed is, anything sent but not confirmed and anything still waiting to go out. Rules decide what counts as degraded and tell you. | Feeds Built; connection and outbox Planned |
3. Seeing the spectrum and judging effects
A commander wants to know what's going on in the spectrum, what changed, and whether an effect worked, without wading through signal data.
| What you need | What you get | Status |
|---|---|---|
| Read RF levels at a glance | Coverage plots on a colour scale whose lightness follows received power, with the noise floor and protection thresholds marked and a colour bar on the globe. | Built |
| Map and timeline views | A globe over local imagery and terrain, coverage plots, link budgets, pins that group as you zoom out, weather, your own markups, and an exercise clock with a timeline. | Built |
| How things connect, not just where they are | A Graph tab (the NEMESYS vertical view) and a Whiteboard showing how nets, sites, equipment and assignments tie together. | Built |
| Band occupancy and allocation views | A spectrum management tab with the allocation table, band occupancy and deconfliction. | Planned |
| Spot changes and anomalies | Rules that compare what's heard with what's authorized and report anything out of place. | Planned |
| Did the effect work? | Measurements before and after, compared with the baseline taken before the engagement, kept with the effect. | Proposed |
| Get results through a thin pipe | Small, sealed sets; the work is done at the node and only the answer is sent. | Built (sets); prioritizing traffic Proposed |
4. Electromagnetic attack and countermeasures
NEMESynth-EMSO doesn't jam anything. Its job is to make sure the people who do jam know which frequencies to leave alone.
| What you need | What you get | Status |
|---|---|---|
| Effects without fratricide | A restricted frequency list (taboo, protected and guarded) built from the record and the assignments, and published to fires and EA systems. | Planned |
| Stay in step with mission command and fires | The record, PACE status and restricted list published to the shared network in registered formats. | Planned |
Across the board
| What you need | What you get | Status |
|---|---|---|
| Publish, subscribe and take commands on a shared network | A Zenoh client over mutual TLS inside a WireGuard mesh. Decisions go out once they're final, with source and marking. Subscriptions follow what the rules need, and commands get an explicit answer. | Planned |
| Work when the network is cut, spotty or slow, or GPS is denied | Everything (the model, the maps, the rules, the record) is on the device. A node that's cut off still makes decisions, and nodes holding the same set make the same ones. | Built |
| Share operational data securely | Sealed sets, IC ISM and CUI markings on every value that roll up to the record, and the classification banner on every screen. | Built |
| Stay in control, with no surprises | Every action is a command you can undo. You decide whether the assistant asks first or acts while you watch. Anything irreversible needs its own permission. Every PACE switch records which version of which sheet made the call, and which row. | Built; a view of what the assistant is controlling Planned |
| Know when something degrades | Rules over connection and feed status that warn you when something goes bad. | Feeds Built; connection Planned |
| Fill the gaps in the data | Defaults for missing or ambiguous values, synthesized from physics, the standards and the domain's rules. Each is marked synthetic, names what it rests on, and is withdrawn when that changes. | Marking Built; synthesis Planned |
| Fits the platform (SWaP-C) | The same C library on a laptop, iPad, browser or vehicle computer, and a small sensor node for dismounts. | Desktop Built; web and iPad In progress; node Planned |
| On the vehicle | Position and time from the vehicle's VICTORY services on a mounted system. | Proposed |
| Coalition and host-nation coordination | Host nations with their own contacts and agendas, their rules exchanged as decision sheets, and NTIA GMF. | Sheets Draft; GMF Planned |
| Proven at real scale | 124k master reference records imported (9.4 million lines in six minutes, 211 MB of memory), and the engineering checked against reference results. | In progress |
| Training and rehearsal | Scripted exercises on Trazore with screenshots, recordings and briefings, and an assistant that can run an exercise from start to finish while you watch. | Exercises Built; run by the assistant Planned |
Want the detail behind a row?
Tell us which capabilities matter to your unit or program and we'll send what we have on them, or show them to you running.
Get more information