Skip to content
Gausio

CSDB · S1000D · BREX

The single source of truth for regulated technical documentation.

Common Source Database for S1000D. BREX-validated XML, applicability-driven variants, frozen snapshots, IETP and per-customer export from one governed source.

Request demo accessSee the platform
csdb / aircraft-a / publicationLint report
  • ERRDMC-AC-A-32-11-00-00A-040A-D
  • ERRDMC-AC-A-52-31-00-00A-941A-D
  • WARNDMC-AC-A-24-00-00-00A-018A-D
  • OKPMC-AC-A-00001-00
Validation across a publication. Each finding points to the data module, location and rule that fired.
Source of truth for every data module
0

Source of truth for every data module

Automated checks on XML and graphics
0+

Automated checks on XML and graphics

Change history attributed and traceable
0%

Change history attributed and traceable

Built for
  • Aerospace
  • Naval
  • Rail
  • Automotive
Built on
  • S1000D Issue 6.0
  • ATA iSpec 2200
  • ASD-STE100
  • S2000M

01Built for regulated industries

One platform, every standard your programme needs

Aerospace, defence, rail and automotive share a documentation language. Gausio speaks it natively, without bending generic tools to fit.

Sectors

  • Aeronautics

    Airframe, engine and equipment manuals: AMM, IPD, SRM, wiring and crew documentation, structured by ATA chapter or by S1000D Standard Numbering System.

  • Naval & marine

    Platform and combat-system documentation for ships and submarines, with applicability driven by hull, configuration and mission fit.

  • Railway

    Rolling stock and signalling maintenance documentation: variants by fleet, depot procedures, parts catalogues and component data.

  • Automotive & industrial

    Service literature and parts catalogues for vehicles and heavy equipment, with model-year and option-driven applicability.

Standards & specifications

  • S1000D

    Data modules, publication modules, the CSDB model, BREX business rules and the issue/status lifecycle — natively, not as an export filter.

  • S2000M

    Material management data linked to the same source: spare parts, supersession and provisioning aligned with the documentation.

  • ATA iSpec 2200

    Legacy and parallel ATA-numbered documentation handled alongside S1000D, so a mixed fleet does not mean two systems.

  • ASD-STE100

    Simplified Technical English checks integrated into the lint, so controlled-language rules are enforced where the content lives.

02Platform

What a Common Source Database actually does

Not a folder of XML files with a viewer on top. An environment for the people who write, validate, version and publish technical data.

  • Centralised CSDB

    Every data module, publication module, illustration and resource in one governed repository — searchable by code, status, applicability or content, with no duplicated masters.

  • Spare parts & material data

    Illustrated Parts Data tied to the modules that reference them: part numbers, NSNs, supersession chains and provisioning data managed next to the documentation, not in a separate spreadsheet.

  • XML as a single source of truth

    One authoritative XML per data module, standards-conformant by construction. Everything else — IETP, PDF, print — is a rendering of that source, never a fork of it.

  • Static analysis (lint) for your documentation

    Like a linter for code: schema conformance, BREX business rules, broken cross-references, applicability that doesn't add up, and consistency between SVG graphics and the XML that calls them — flagged before review, not after delivery.

  • Versioning & snapshots

    Full change history on every module and a one-click frozen snapshot of an entire publication: reproduce exactly what shipped for an issue, a configuration or an audit.

  • Applicability & variants

    Model applicability cross-reference tables, product and condition cross-references once, then filter and resolve any deliverable to the exact configuration — without cloning a manual per variant.

  • Per-customer export templates

    Define how a publication looks for each operator or programme — cover pages, numbering, layout, language — and generate compliant deliverables on demand from the same governed source.

  • Traceability — who did what

    Every change attributed: author, reviewer, status transition and standard reference. Answer 'who touched this module, and under which authority' without reconstructing it from emails.

03Workflow

From authoring to validated, versioned delivery

The same five steps for an aircraft manual, a ship's combat system or a fleet of trains — because the standard is the same, even when the product isn't.

  1. Bring in or author your data modules

    Import an existing CSDB or legacy ATA content, or author new modules in Gausio. Codes, metadata and resources are checked and indexed on the way in.

  2. Validate with the lint and your business rules

    Every module is checked against the schema, your BREX rules, cross-references, controlled language and graphics consistency. Issues are listed with file, location and the rule that fired.

  3. Define applicability and variants

    Set up applicability, product and condition cross-references once. Gausio resolves any deliverable to the configuration you ask for.

  4. Freeze a versioned snapshot

    Promote a clean state to an immutable snapshot — the exact content for an issue, a delivery or a certification milestone, reproducible forever.

  5. Publish with your own templates

    Generate the IETP package, PDF or print deliverable for a given operator using their template — compliant output, same source, zero re-keying.

04Quality gate

A lint for your technical documentation

Static analysis brought to data modules. Continuous, automated checks that catch what manual review misses, with every finding tied to the exact rule that fired.

Run it on a single module, a publication or the whole CSDB. Errors block a snapshot; warnings and hints guide the cleanup. Every finding points to the exact file, location and rule.

  • Schema conformance

    Every data module is valid against its S1000D schema — element structure, attributes and identification, not just 'well-formed XML'.

  • Business rules (BREX)

    Your project's BREX data module is enforced as rules: allowed values, mandatory elements, naming conventions and the constraints your customer signed off.

  • Graphics vs XML consistency

    Every SVG (or CGM) referenced by a module actually exists, every hotspot in the graphic maps to a callout in the text, and orphaned or unreferenced illustrations are surfaced.

  • Cross-references

    Internal and external references resolve: referenced data modules, parts, publications and ICN targets exist and are in a usable status.

  • Applicability integrity

    Applicability annotations reference declared product and condition cross-references, with no unreachable content and no contradictions across a publication.

  • Module metadata & language

    Status, security, responsible partner, quality assurance and dates are present and coherent — and Simplified Technical English rules are checked where required.

Sample lint reportlint
  • ERRBREX-014DMC-AC-A-32-11-00-00A-040A-DDisallowed element <para> inside <warning>: project BREX requires <warningAndCautionPara>.
  • ERRGFX-002DMC-AC-A-52-31-00-00A-941A-D / ICN-AC-A-523100-001Referenced graphic ICN-AC-A-523100-001 not found in the CSDB.
  • WARNAPP-007PMC-AC-A-00001-00Condition 'engine-mod-3' is declared in the CCT but never applied — content may be unreachable.
  • INFOSTE-031DMC-AC-A-24-00-00-00A-018A-DSentence exceeds 20 words — Simplified Technical English recommends splitting it.
An example report — three findings on one publication, with severity, code, location and rule.

05FAQ

Questions teams ask before a demo

If yours isn't here, send it. We'd rather answer it before a working session than after a contract.

06Get started

Run Gausio on your own documentation

Bring a data module, a publication or a BREX file. In one session we'll run the CSDB, the lint and a templated export on content you recognise.

Request demo accessTalk to us

No procurement marathon. A working session, your data, straight answers.