Mycelium
Mission connectivity
Connectivity must serve the mission, not the network diagram. Mycelium supports prioritised information exchange across changing communications environments.
Tactical users, sensors, platforms and applications may depend on several communications paths with different capacity, latency, reach, security and availability. The challenge is not simply to create a connection. It is to keep mission-relevant information moving as conditions change.
Mycelium is the mission-connectivity element within the BSS Tactical Sensors-to-Effects Web. It provides an approach for relating information priorities and operational needs to the communications environment available to the capability.

Start with what must be exchanged
Mycelium begins with the users, systems and information exchanges that support the mission. Voice, command messages, position, alerts, tracks, imagery, sensor feeds and application updates place different demands on communications and do not all carry the same operational importance.
BSS identifies which exchanges are critical, how current they must be, what can be delayed and which local functions should continue when wider services are constrained. These requirements shape the connectivity approach rather than allowing one preferred technology to define the mission.
Heterogeneous communications are the normal case
Tactical environments may combine radios, mesh networks, satellite, cellular, line-of-sight links, local wired or wireless networks, gateways and customer-owned infrastructure. Each path brings different strengths and limitations.
Mycelium supports the use of approved communications options as part of one mission-oriented environment. It does not imply that every bearer is interchangeable or that every system is automatically compatible. Interfaces, versions, configurations and security conditions remain part of the assessed baseline.
Prioritisation across the complete path
When bandwidth or availability is constrained, information priority must be preserved beyond one application or network segment. A priority setting has limited value if gateways, external services or receiving systems do not recognise it.
Mycelium supports the engineering of prioritised information exchange across the complete route. The mission relevance established through Orchard can inform which exchange receives preference, while the communications design determines how that priority is implemented under the available conditions.

Local continuity at the tactical edge
The tactical edge is the environment close to deployed users, sensors and platforms, where access to central infrastructure may be limited. Selected applications, data and processing may need to remain available locally.
Mycelium connects communications with tactical-edge services so the capability can continue where the approved architecture supports it. Local continuity does not reproduce every central service. It preserves the functions and information selected as necessary for the task within their assessed limits.
Predictable degraded behaviour
Resilience is not a claim that connectivity will never fail. Users need to understand what continues, what is delayed, what becomes unavailable and how the capability behaves when a preferred path is lost.
BSS defines expected transitions, fallback options, system state and recovery for the relevant configuration. Any statement about operation under jamming, positioning denial, electromagnetic interference, cyber disruption or disconnected conditions remains limited to the systems and scenario assessed.
Controlled synchronisation and recovery
Local operation during disruption can create different versions of information across the environment. When connectivity returns, systems may need to exchange updates, reconcile changes and restore access to wider services.
Mycelium supports a controlled approach to reconnection that considers timing, duplication, conflict, ownership, security and actions taken from an earlier state. Recovery should return the capability to a known condition rather than simply re-establish a link.

Visibility, diagnostics and support
A communications path can appear available while a route, gateway, identity service, application or information exchange remains unavailable. Mission connectivity therefore depends on visibility of the complete path.
BSS includes system state, logging, diagnostics, ownership and recovery procedures within the integration baseline. Support teams need to trace issues across networks, applications, interfaces and supplier boundaries, with operational effect considered alongside technical status.
Working with existing networks and services
Mycelium is not a requirement to replace the customer’s communications estate. BSS works with approved radios, networks, gateways, applications and services where the necessary interfaces and responsibilities can be established.
Open standards and documented interfaces can support integration and change, but they do not prove end-to-end interoperability. Compatibility remains tied to the defined systems, software versions and operating conditions evaluated.
Validation through J-CIE
J-CIE provides the environment for evaluating Mycelium with representative systems, information and users. Activities can examine congestion, latency, path transition, unavailable reach-back, information priority, local operation, synchronisation, diagnostics and recovery.
Red teaming can introduce controlled disruption or misleading system states to challenge assumptions. Findings remain connected to the assessed configuration and can lead to engineering, procedure, training or support actions.
Mission connectivity that can adapt
Mycelium connects the communications environment to the mission rather than treating connectivity as an isolated technical service. It makes information priorities, paths, dependencies, degraded behaviour and recovery more explicit.
The result is a controlled connectivity approach that can use existing and emerging technologies while keeping the operational need, user and evidence in view.
Together we solve tough problems
Bring us the operational problem. We bring the systems, the integration and the team to prove it in the field.