Skip to main content
Airline fleet parked at gates, used as AeroBrain network context photography.
The lit flight displays and instrument panel of the SkyDynamics A320 FNPT II simulator

LLiDA · Low Level integrated Database Architecture

LLiDA. An offline-first real-time database, with live synchronisation.

LLiDA is the real-time time-series database developed by SkyDynamics for safety-critical and mission-critical systems. It works on the device, in RAM, on disk and at processor level, and keeps every connected node synchronised. It is the data layer AeroBrain reasons over.

What it is

The data is on the device. And every node holds the same record.

LLiDA captures real-time data, such as the data of an aircraft's avionics, as time series. It works in RAM, on disk and at processor level, on RISC-V, ARM and other architectures, from a low-level microprocessor computer to a server. Values are available to the layers above without a round trip to a server, and nodes synchronise live over secured or common networks.

A database on a server
Needs the link
LLiDA
Works on the device, syncs between nodes
A database on a serverAircraftFunctionServerThe dataLink downThe function waits for the networkTiming depends on the round tripLLiDAOn the aircraft nodeRAMDiskAvionicsEdgeGroundRead on the node, no round tripEvery node holds the same record
Illustrative
  • Real-time time series

    Avionics and sensor values are captured as they are produced, each channel read on a fixed period, so timing is known in advance.

  • Live synchronisation

    Nodes exchange data live over secured networks or common networks, so the aircraft, the edge device and the ground hold the same record.

  • High reliability and assurance

    Developed to the rules used for flight software, including MISRA C and the objectives of DO-178C.

LLiDA is SkyDynamics technology and part of AeroBrain. Performance figures depend on the hardware and the function: they are set with the customer and shown for each product.

LLiDA at the edge

On board, on the edge, on the iPad. Five features, one database. Choose one to see it work.

The figure follows avionics data from the sensor to the people who use it: sampled on the aircraft, held by LLiDA nodes that cover for each other, passed across a cryptographic boundary, and read on the crew's and engineers' iPads, where it can be searched by meaning.

From the avionics to the iPad, in real timeIllustrative

Aircraft avionics

Safety-critical, on board

  • Engine 2 vibration0.62 ips
  • Exhaust gas temperature624 °C
  • Hydraulic pressure3011 psi

Sampled on a fixed period

LLiDA nodes

Each holds the record

  • Avionics computerARM
    In sync#8224
  • Edge unitRISC-V
    In sync#8224
  • Ground serverServer
    In sync#8224

Cryptographic boundary

Identity proven by key

  • Crew iPadKey verified
  • Engineer iPadKey verified
  • Unknown deviceRefused: no key

User devices

Through the LLiDA plugin

Crew iPadFlight deck

LLiDA plugin

Engine 2 vibration0.62 ips

Semantic search, on the iPad

engine vibration rising in icing

  1. Engine 2 vibration, last 10 minutes0.94
    Live time series
  2. High engine vibration procedure0.89
    Operator QRH
  3. Engine anti-ice operation0.81
    FCOM

On the device · Low latency · Low energy

Engineer iPadMaintenance

LLiDA plugin

Engine 2 vibration0.62 ips

Every value with its time, on board.

Avionics channels are sampled on a fixed period on the aircraft and held as time series in RAM and on disk, so the layers above read them without a round trip to a server.

  • Time series on board

    Each channel is read on a fixed period on the aircraft itself, so a reading exists at a known time without asking a server for it.

  • Nodes that cover for each other

    There is no master copy. Each node keeps the record, so losing one node does not lose the data or stop the reads.

  • The iPad joins through a plugin

    Crews and engineers see the on-board values on the device they already carry, and the function on board never waits for that device.

  • A key, or no connection

    Every platform proves its identity cryptographically before it is admitted. An unknown device stays outside.

  • Search by meaning, locally

    Vector and semantic search plugins answer "show me what looks like this" on the device, without a cloud service.

  • Evidence for AI

    Each value keeps its source and time, so an AeroBrain answer built on it can be replayed and audited.

Illustrative figure: readings, scores and device names are invented. Timing, latency and energy figures depend on the hardware and the function: they are set with the customer and shown for each product.

Specifications

LLiDA at a glance. Every feature on one sheet.

The features of LLiDA as SkyDynamics states them. Figures for timing, latency, memory and energy depend on the hardware and the function: they are set with the customer and shown for each product.

LLiDALow Level integratedDatabase ArchitectureMISRA C · DO-178CTime seriesFixed sampling periodRAM · disk · processorRISC-V · ARM · serverLive synchronisationNo single point of failureCryptographic identityPluginsiPad · vector · semantic
Illustrative
LLiDA at a glance.
CriterionLLiDA
Full nameLow Level integrated Database Architecture
TypeReal-time time-series database, offline first, with live synchronisation
Data modelTime series: every value stored with the time it was measured, channel by channel
SamplingA fixed period per channel, set before the system runs
StorageRAM for the working data, disk for the record, and a layer at processor level
ProcessorsRISC-V, ARM and other architectures, from a microcontroller to a server
SynchronisationLive between nodes, over secured networks or common networks
ResilienceNo single point of failure: every node holds the record; a stopped node is isolated
SecurityAdmission by cryptographic identity; data between nodes and devices protected cryptographically
User devicesDevice plugin for crew and engineer iPads, across a defined boundary
SearchVector and semantic search plugins on the device, designed for high speed, low latency and low energy
AIThe real-time data layer of AeroBrain; each value keeps its source and time for audit
DevelopmentMISRA C and the objectives of DO-178C
Standards that frame itDO-330, DO-278A, DO-326A; ECSS, IEC 62304 or IEC 61508 per programme
DeploymentOn the device, at the edge, on premises, air-gapped; ground records in the EU, Switzerland or on premises
UseOn its own, or with the other AeroBrain technologies

Certification is granted for a specific product on specific hardware, with the authority, and is shown for that product.

How it works

The life of a value. From the sensor to the audit record, in six steps.

Every value in LLiDA follows the same path, on every node. Nothing on the path needs a server to be reachable.

  1. Sampled

    The channel is read on its fixed period. The value is stored with the time it was measured.

  2. Held in memory

    The newest samples stay in RAM, where the functions above read them at once.

  3. Written to disk

    The record is kept on disk on the same node, so it survives the working window in memory.

  4. Synchronised

    Connected nodes exchange the record live, over secured or common networks.

  5. Read where it is needed

    By the function on board, by AeroBrain, and by crews and engineers through the iPad plugin.

  6. Kept as evidence

    Each value keeps its source and time, so a decision made on it can be traced afterwards.

Architecture

Low level, by design. What "Low Level integrated Database Architecture" means.

LLiDA is built close to the hardware, so that the same architecture can run on a microcontroller beside a sensor and on a server on the ground. These are its parts.

ChannelsVibrationTemperaturePressureEach on a fixed periodOne LLiDA nodeRead by the functions aboveRAM: the newest samplesDisk: the recordProcessor levelRISC-VARMOthersNode on the edgeSame recordNode on the groundSame recordNo single point of failureEvery node holds the record
Illustrative
  • Time series as the data model

    Every value is stored with the time it was measured, channel by channel. That is the shape of avionics and sensor data, so nothing has to be converted on the way in.

  • Fixed sampling periods

    Each channel has its own period, set in advance. The system knows when a value will exist before it runs, which is what real-time functions need.

  • RAM, disk and processor level

    The working data lives in memory for fast reads, the record lives on disk, and the lowest layer works at processor level. One architecture covers all three.

  • RISC-V, ARM and other architectures

    The same database runs from a low-level microprocessor computer near the sensor to an avionics computer and a ground server.

  • Live synchronisation between nodes

    Nodes exchange data as it is written, over secured networks or common networks, so the aircraft, the edge device and the ground hold the same record.

  • No single point of failure

    Every node holds the record. A node that stops is isolated, and the other nodes keep serving the data.

Plugins

Extend it where the work is. Plugins for devices and for search, on top of the same record.

The core of LLiDA stays small and assured. Plugins connect it to the devices people carry and add search for on-device AI, without changing what runs on board.

LLiDA recordSmall, assured coreUnchanged on boardDevice pluginVibrationCrew andengineeriPadsVector searchNearest matches, on the deviceSemantic searchvibration rising in icing0.940.890.81AeroBrain retrievalE1Live readingE2ProcedureE3LimitsFast · low latency · low energy
Illustrative

Security

No key, no connection. Cyber security built into how platforms connect.

A database that reaches from the aircraft to an iPad must decide, every time, who is allowed in. In LLiDA that decision is cryptographic.

On boardAvionics nodeSafety-critical functionEdge nodeHolds the same recordKeeps running on its own nodes,whatever happens on the device sideCryptographic boundaryCrew iPadKey verified · protected linkEngineer iPadKey verified · protected linkUnknown deviceRefused: no key
Illustrative
Aviation data hosting
  • Cryptographic identity

    Platforms connect only through their cryptographic identity. A device that cannot prove its key is refused.

  • Protected between nodes and devices

    Data exchanged between nodes, and between nodes and devices, is protected cryptographically.

  • A boundary, not a bridge

    User devices join across a defined boundary. The safety-critical function keeps running on its own nodes whatever happens on the device side.

  • Secured or common networks

    Synchronisation runs over secured networks or common networks; the cryptographic layer is what makes a common network usable.

  • Framed by DO-326A

    The airworthiness security process frames how synchronisation over networks is assessed for an aircraft programme.

  • Where the record is kept

    On the ground, records can be hosted in the EU, in Switzerland or on your premises.

Offline first, with sync

Work without a connection. Synchronise when there is one.

The same principle runs through SkyDynamics products: the data a person needs is on the device they hold, and it synchronises with the other devices and the ground when a link exists.

NetworkLinkNo linkLinkOn the nodeNever stopsOther nodesIn step while linkedThe work continues on the deviceThe function does not wait for a serverThe same principle runs through AeroTechLog, the aeroEBT instructor app and OpsEye.
Illustrative
Offline and between iPads in AeroTechLog
  • On the aircraft and the edge

    LLiDA holds the working data in memory and the record on disk on the node itself, so the function does not wait for a server.

  • AeroTechLog

    Crew members make entries and read aircraft data without a connection. The data synchronises when the connection returns, and company iPads sync directly with each other, without internet.

  • aeroEBT instructor app

    Instructors grade offline in the simulator. The session synchronises automatically, with signatures and records.

  • OpsEye

    OpsEye keeps working on the workstation with local storage during a network outage and syncs when the connection returns.

Where it runs

One architecture. From a microcontroller to a server, and on to the iPad.

One architecture, synchronised liveLLiDAMicrocontrollerRISC-VBeside the sensorLLiDAAvionicscomputerARMOn the aircraftLLiDAGroundserverServerOperations, maintenanceCrew iPadLLiDA pluginWhere people work
Illustrative
One architecture.
CriterionProcessorRole
MicrocontrollerRISC-VLow-level computer close to the sensor
Avionics computerARMOn the aircraft
Ground systemServerOperations and maintenance
Crew and engineer iPadsThrough the device pluginThe on-board values where people work

Links between nodes run over secured networks or common networks.

Where it applies

Built for data that cannot wait. Six fields LLiDA is designed for.

Choose a field to see what LLiDA holds there and why its design matters. These are the fields the technology is designed for, not a list of deployments.

1 of 6

Avionics

Real-time data on the aircraft, for next-generation avionics.

Engine, systems and flight parameters are captured as time series on the avionics computer or on a microcontroller close to the sensor.

  • Each channel sampled on a fixed period
  • Values read without a round trip to a server
  • The data AeroBrain reasons over in real time

ARM · RISC-V · DO-178C objectives

Each deployment is specified with the customer and its assurance level.

How it differs

Not a server database on a small computer. A different design, for a different job.

Server time-series databases are built for data centres and dashboards. LLiDA is built for the node where the data is produced and the function that depends on it.

Server time-series databaseSensorNetworkData centreDashboardThe function reads from the server, so it depends on the network and the cluster.LLiDASensorLLiDA nodeOther nodesiPad, AeroBrainThe function reads from memory on its own node; the record is shared with the other nodes.The function reads here
Illustrative
Not a server database on a small computer.
CriterionServer time-series databaseLLiDA
Built forCollecting metrics in a data centreSafety-critical and mission-critical functions on the node
Where the function readsFrom a server, over the networkFrom memory on its own node
If a server or node stopsDepends on the cluster set-upThe other nodes keep serving the record
Smallest targetA server or a virtual machineA RISC-V or ARM microcontroller
People's devicesThrough a web dashboardiPads through a device plugin, admitted by key
Search for AIUsually a separate vector serviceVector and semantic search plugins on the device
Development rulesGeneral software practiceMISRA C and the objectives of DO-178C

A general comparison; individual products differ. LLiDA figures depend on the hardware and the function and are set with the customer.

A worked example

One event, end to end. Engine vibration rises in the climb, in icing conditions.

An illustrative example of how LLiDA carries one event from the sensor to the crew, the ground and the audit record. The values and the event are invented.

  1. On the sensor

    A RISC-V microcontroller beside the engine samples vibration on its fixed period and writes each value with its time.

  2. On the avionics computer

    The ARM avionics node holds the newest samples in RAM. The trend above the normal band is visible as it happens.

  3. To AeroBrain

    The RAG engine retrieves the live trend with the procedure and limits that apply, each with its source and time.

  4. On the crew iPad

    Through the device plugin the crew see the reading beside the options. A semantic search for "vibration in icing" finds the related passages on the device.

  5. If a node stops

    Should the edge unit stop during the event, it is isolated and the other nodes keep serving the record.

  6. On the ground

    Maintenance control holds the same record, synchronised over a secured link, and the crew's decision is kept with the evidence.

Assurance

Engineered so the evidence exists. The standards that frame LLiDA.

LLiDA is developed to high-assurance practice. Certification is granted for a specific product on specific hardware, with the authority, and is shown for that product.

Forward: every requirement reaches a testRequirementDO-178C objectivesDesignDO-178C objectivesCodeMISRA CTestDO-330 toolsEvidenceWith the releaseBack: every line of code answers a requirementStandards that frame the productDO-278A groundDO-326A securityECSS spaceIEC 62304 medicalIEC 61508Certification is granted for a specific product on specific hardware, with the authority.
Illustrative
Standards and assurance across AeroBrain
  • MISRA C

    The coding rules for C in critical systems, followed in LLiDA's C code.

  • The objectives of DO-178C

    Requirements, design, code, tests and evidence traceable in both directions.

  • DO-330

    Tool qualification, for tools whose output is relied on without further checking.

  • DO-278A

    Ground-based systems: the ground side that the aircraft synchronises with.

  • DO-326A

    The airworthiness security process: synchronisation over networks.

  • ECSS, IEC 62304, IEC 61508

    Space, medical and other safety-critical fields, agreed for each programme.

What it is for

The data layer of AeroBrain. Real-time data for AI that has to be audited.

A person decides, and it is recordedAssurance Small Language ModelSecured RAG engineContextual Composition ProtocolLLiDA real-time databaseAvionics data inEach value keepsSourceTimeSo an answer replays
Illustrative

LLiDA: questions engineers ask

LLiDA (Low Level integrated Database Architecture) is a real-time time-series database developed by SkyDynamics for high-reliability and high-assurance systems. It works in RAM, on disk and at processor level, on RISC-V, ARM and other architectures, synchronises live over secured or common networks, and is developed to safety-critical rules such as MISRA C and the objectives of DO-178C.

LLiDA is built for that. The working data is held in memory and the record on disk on the node itself, so values are available without a round trip to a server, and connected nodes synchronise live over secured or common networks, from the aircraft to the edge device and the ground.

RISC-V, ARM and other architectures, from a low-level microprocessor computer to an avionics computer and a server. The same architecture covers the working data and the stored record.

It is designed not to. Every node holds the record; if one node stops, it is isolated and the other nodes keep serving the data.

Yes, through the LLiDA device plugin. The iPad connects to the nodes on board across a cryptographic boundary, so on-board values reach the device directly while the safety-critical function keeps running on its own nodes.

Platforms connect only through their cryptographic identity, so a device that cannot prove its key is refused, and data between nodes and devices is protected cryptographically. For an aircraft programme, DO-326A frames how synchronisation over networks is assessed.

Yes, through plugins that run on the device. They find the readings and passages closest in meaning to a question and are designed for high speed, low latency and low energy, for high-assurance AI at the edge.

It is designed for operations of that kind: data held on the node between links, synchronisation when a link exists, and RISC-V and ARM processors. The software standards for a space programme, such as ECSS-E-ST-40C and ECSS-Q-ST-80C, and the evidence are agreed with the customer.

LLiDA is the real-time data layer of AeroBrain. It captures the aircraft's avionics data as time series; the AeroBrain RAG engine retrieves over that data and over the operator's approved manuals, and each piece of evidence keeps its source and its time, so an answer can be audited.

LLiDA is developed to safety-critical rules such as MISRA C and the objectives of DO-178C. Certification belongs to a specific product on specific hardware and is shown for that product.

Yes. Each AeroBrain technology can be used alone; LLiDA can be the database of a system that has no AI at all, and AeroBrain can be added later on the same data.

Yes. AeroTechLog works offline at the aircraft and synchronises when the connection returns, and company iPads sync directly with each other. The aeroEBT instructor app grades offline in the simulator and synchronises automatically. OpsEye keeps working on the workstation during a network outage.

Low Level integrated Database Architecture. "Low level" because it is built close to the hardware, down to processor level; "integrated" because the same architecture covers the working data in RAM, the record on disk and the synchronisation between nodes.

LLiDA is a real-time time-series database. Vector and semantic search are added through plugins that run on the device, so the same record can be searched by meaning for on-device AI.

Start with a technical briefing: the signals, the processor, the network and the assurance level. SkyDynamics then shows how LLiDA holds and synchronises that data, and which evidence comes with it.

Bring your data and your hardware.

Tell us the signals, the processor and the time budget. We show how LLiDA holds and synchronises them.

We respond within one business day.