Orchard
Mission context
Information becomes useful when it is connected to the mission. Orchard organises information around the mission, the user and the task.
Operational environments can produce more information than users can interpret or communications can move. Sensors, platforms, reports, applications and partner services may all contribute, but their value depends on whether the information reaches the right person with the context needed to understand it.
Orchard is the mission-context element within the BSS Tactical Sensors-to-Effects Web. It provides an approach for organising information around mission outcomes, user roles and operational tasks rather than around the structure of individual systems.

Start with the user and the decision
Orchard begins with the operational outcome and the people responsible for achieving it. Different roles need different information, levels of detail and time horizons. A commander, operator, analyst and maintainer should not automatically receive the same view or every available data item.
BSS identifies what each role must know, which decision the information supports, how current it must be and what uncertainty or limitation must remain visible. This creates the context against which sources, applications and information flows can be assessed.
Mission context connects information to meaning
A track, alert or report has limited value when its relationship to the task is unclear. Mission context can include the operational objective, area, phase, role, authority, priority and the activity to which the information relates.
Orchard uses that context to help organise information around what the user is trying to achieve. It does not change the underlying authority of the source or turn an observation into a verified assessment. It provides a structured way to understand why the information matters and who may need it.
Source, timing and confidence remain visible
Information becomes difficult to trust when its origin, age or processing history is unclear. Users need to distinguish a direct observation from an automated association, an analyst assessment or information received from another organisation.
Orchard supports the preservation of available provenance such as source, time, location, identity, confidence, processing status and known limitations. The exact attributes depend on the contributing systems and approved interfaces.
Preserving provenance does not guarantee that information is correct. It allows users and applications to judge it with greater awareness of where it came from and how it has changed.
Role-relevant information reduces cognitive burden
Sending more information to the user can increase workload rather than improve understanding. Orchard supports the selection and organisation of information according to role, task and authority.
The objective is not to hide relevant detail or create one simplified picture for everyone. It is to make the most relevant information visible first while allowing authorised users to investigate supporting detail where required.

Context across different systems and sources
Customer environments may include command applications, intelligence tools, sensor-management systems, reports and databases from multiple suppliers. These systems can describe the same activity using different formats and terminology.
Orchard provides the mission-oriented structure needed to relate information across those boundaries. BSS defines mappings, responsibilities and information relationships for the assessed workflow without assuming that every source or application is universally compatible.

Supporting prioritisation at the tactical edge
When communications resources are constrained, mission context helps determine which information should move first, which can be delayed and which should remain available locally. This relationship connects Orchard with Mycelium, the mission-connectivity element of TSEW.
Orchard identifies the relevance of information to the mission and user. Mycelium then supports prioritised exchange across the communications paths available to the capability. The two elements work together without treating context and connectivity as the same function.
Validation through J-CIE
Mission context must be evaluated with the users and systems that depend on it. J-CIE, the BSS Joint Capability Integration Environment, provides a setting for experimentation, integration, training, validation and structured critical challenge.
Representative scenarios can examine whether information reaches the correct role, remains understandable, preserves important context and supports the intended workflow. Findings can lead to engineering changes, revised information priorities, different presentation or additional training.
Context that can evolve with the mission
Missions, roles, information sources and technologies change over time. Orchard supports a lifecycle approach in which context, priorities and information relationships can be reviewed as the capability evolves.
The result is not a new universal data store or one application for every user. It is a mission-oriented structure that helps existing and emerging systems deliver information in a way that is more relevant, understandable and supportable.
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.