Frequently asked questions

Voluspa develops Operational Systems Intelligence: software for examining stress, transitions, interactions and possible consequences in complex operating environments. It combines observed data with analytical models to support investigation, planning and decisions—not to replace human judgment.

No. Yggdrasil is designed as a common analytical runtime across industries. Maritime, commodity markets and strategic policy are the principal current application areas; support for any new industry depends on the availability of suitable data, models and validation.

Yggdrasil is the shared computational runtime. Meridian applies it to maritime operations, Helios to commodity-market behaviour and Aegis to strategic and policy-related uncertainty. Aether is an aviation and aerospace application area under development. Each module has its own data requirements, assumptions and validation boundaries.

Potential users include operations and network-planning teams, risk and resilience functions, commodity and procurement teams, strategy groups and research analysts. The relevant workflow depends on the customer's assets and the decision being supported.

A data dashboard usually displays measurements and reports. Voluspa aims to examine how conditions evolve, how signals relate across a system, and how outcomes differ under explicit scenarios. That additional inference must still be supported by appropriate data and validation; it is not a claim to replace every specialist platform.

Not necessarily. Voluspa is intended to add an analytical layer that examines system behaviour and conditional outcomes. A client evaluation would determine how it complements existing data providers, planning tools and internal systems.

Depending on the module and licensed coverage, inputs may include vessel movement, weather and ocean observations, commodity-market data, and public event or policy evidence. Client-owned data can be assessed for integration. Data coverage and permitted uses vary by source and deployment.

Not uniformly. Some inputs are refreshed frequently; others arrive on scheduled cycles or are historical research datasets. Where available, the interface distinguishes the observation date from the time data was received, and identifies delayed or unavailable feeds. Refreshing the screen does not make an older observation current.

Voluspa can characterize observed conditions and explore model-dependent scenarios. That is not the same as guaranteeing an event, a market price or an arrival time. Some scenario probabilities are conditional on analyst-supplied assumptions and are not calibrated probabilities of real-world events. Capabilities and limits must be reviewed for each application.

It can surface relevant observations, model signals and competing explanations for investigation. An association or regime change alone is not proof of causation. Stronger causal claims require suitable controls, data and validation.

Selected research and demonstration workflows support conditional scenario analysis. The degree of configurability differs by module and interface; not every underlying model or regime parameter is currently interactive. A client-specific scenario workflow would be scoped and validated separately.

Validation is specific to a dataset, geography, time window and intended decision. It can include historical replay, held-out testing, baseline comparisons, sensitivity analysis and checks on data or model consistency. A result validated for one setting should not automatically be treated as validated everywhere.

We would define one decision problem, the relevant assets or geography, required data, a comparison baseline and explicit success criteria. The goal is to determine whether a particular capability adds measurable value before broadening scope.

Potentially. Integration depends on data formats, access permissions, security requirements, licensing and the use case. Integration feasibility and responsibilities should be established during technical scoping rather than assumed from a demonstration.

Access controls, permitted data uses, deployment architecture and contractual protections need to be specified for each engagement. Restricted third-party datasets cannot be enabled or redistributed without the necessary rights. Public demonstrations are not evidence of a particular security certification or deployment guarantee.

Enterprise terms depend on the selected capabilities, geographic and asset coverage, integration requirements, data rights and support commitments. Pricing is scoped to an evaluation or deployment rather than presented as a universal self-service subscription.