The functions every defence n.e.c. company runs on. It has no schema of its own: companies here are mapped on the Defence schema, and what it does not cover is recorded as gaps.
Focused research on the organizations with the fewest mapped parts in defence n.e.c.; what it finds is public for everyone.
How automatable each primitive is, estimated from the 0 organizations mapped in public on the Defence schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.
| Primitive | Layer | Automation | Peers on software | Software parts named most |
|---|---|---|---|---|
Defence financial management Money: getting funded and paying | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Command and control systems Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Secure communications Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Interoperability Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.