Transportation

Documentation across automotive, rail, commercial aviation, and maritime — modes that share a service-network spine. Field assets, technician-facing maintenance content, warranty and safety exposure when procedures are wrong, regulator scrutiny across DOT/NHTSA, FAA, FRA, USCG, and IMO. The chain of evidence in audits and incident investigations runs through the maintenance documentation.

Document types we work in.

Maintenance manuals: Procedure-level technical content for technicians across modes — automotive service repair manuals, aviation Aircraft Maintenance Manuals (AMMs) and Component Maintenance Manuals (CMMs), rail equipment maintenance instructions and locomotive shop manuals, marine machinery and structural maintenance documentation.
Service bulletins: Field-issued guidance for service procedures, modifications, and safety actions. Auto: Technical Service Bulletins (TSBs); aviation: Service Bulletins (SBs) and Airworthiness Directives (ADs); rail: equipment service notices; marine: classification-society safety circulars.
Parts catalogs: Identification, ordering, and supersession data integrated with PIM, parts-database, and ERP systems. Aviation IPCs (Illustrated Parts Catalogs), automotive parts catalogs, rail spare-parts manuals, marine spare-parts reference documents — patterns repeat, format conventions vary.
Operator and crew manuals: Customer- or operator-facing documentation. Automotive owner's manuals, aviation Aircraft Flight Manuals (AFMs) and crew operating manuals, rail locomotive operating manuals, marine bridge and engine-room operating procedures.
Technician and crew training materials: Procedure-driven training across modes — dealer-network certification curricula, A&P/IA certification support content, rail qualification programs, marine STCW-aligned training documentation.
Compliance and warranty documentation: Warranty content tied to service-procedure accuracy; safety case documentation; configuration-management records that satisfy regulator audit. The connection between procedure accuracy and claim approval — or accident-investigation defense — runs through these documents.

Regulatory frameworks and standards.

S1000D (Issues 4.x – 6.0): International specification for technical publications. Originated in defense-aerospace; now load-bearing in commercial aviation, defense vehicles, and increasingly heavy commercial automotive and rail.
ATA Spec 2200 / iSpec 2200: Air Transport Association specification for commercial aviation technical documentation — the spec aviation MROs and airframers run on for non-defense aircraft programs.
SAE J2008: Society of Automotive Engineers digital service-information specification. Used across passenger and commercial vehicle programs.
AAR M-1003 and FRA Title 49 CFR (rail): Association of American Railroads quality-system standard plus federal regulations governing rail equipment documentation. Compliance documentation surfaces as M-1003 audit responses and FRA-required configuration records.
FAA AC 43.13 and Part 43/145 (aviation maintenance): FAA standards for aircraft maintenance documentation and for the certificated repair stations that perform it. EASA Part-145 carries the equivalent in European jurisdictions.
IMO MSC and IACS Common Structural Rules (maritime): International Maritime Organization Maritime Safety Committee circulars and IACS Common Structural Rules — govern shipbuilding and operating documentation across classification societies.
USCG NVIC and ISM Code (maritime operations): U.S. Coast Guard Navigation and Vessel Inspection Circulars; International Safety Management Code requirements for shipboard operating documentation.
OEM, classification-society, and agency-specific standards: Each vehicle program, airframer, classification society, and rail authority carries its own conventions on top of the named standards. Engagements adapt to the program's actual requirements.

CROSS-MODE PATTERNS — TRANSPORTATION

The same artifact, named differently.

Across automotive, commercial aviation, rail, and maritime, the documentation patterns repeat — service manuals, service bulletins, parts catalogs, operator manuals, compliance evidence. The artifact is structurally the same; the name and the governing regulator change. Engineering knowledge transfers across modes; the language and the audit body have to translate.

Document category	Automotive	Aviation	Rail	Maritime
Maintenance manuals	Service repair manuals · ASE-aligned procedures	Aircraft Maintenance Manual (AMM) · Component Maintenance Manual (CMM)	Locomotive shop manuals · equipment maintenance instructions	Machinery and structural maintenance documentation
Service bulletins	Technical Service Bulletin (TSB)	Service Bulletin (SB) · Airworthiness Directive (AD)	Equipment service notice · field bulletin	Classification-society safety circular
Parts catalogs	Parts catalog · IPL	Illustrated Parts Catalog (IPC)	Spare-parts manual	Spare-parts reference document
Operator / crew manuals	Owner's manual	Aircraft Flight Manual (AFM) · crew operating manual	Locomotive operating manual	Bridge and engine-room operating procedures
Compliance / regulator	NHTSA defect reports · warranty docs	FAA Part 145 audit response · NTSB inputs	FRA inspection records · AAR M-1003 audit response	USCG inspection records · IMO MSC compliance docs

Common terms shown. Each mode carries deeper subdivisions — aviation alone splits AMM/CMM/SRM/IPC/SB/AD by ATA chapter; automotive splits TSBs by NHTSA campaign vs internal; rail and maritime each carry classification-society and regulator-specific format conventions on top of the patterns shown.

When this goes wrong.

TRANSPORTATION / SAFETY & WARRANTY

A service-procedure error becomes a warranty event or an accident-investigation finding.

Automotive: a single TSB error replicated across a dealer network becomes a multi-million-dollar warranty claim event and, in safety-relevant cases, a NHTSA-reportable defect. Aviation: a Maintenance Manual procedure error surfaces in an FAA Part 145 audit or, worse, in an NTSB accident report. Rail: an FRA inspection finding tied to maintenance documentation triggers a service-bulletin recall and AAR M-1003 review. Marine: a maintenance-record gap surfaces during port state control or in classification-society withdrawal of cover. The procedure-document chain is the chain of evidence in every one of these.

When you’d reach out.

“Translation costs across our dealer network are climbing faster than vehicle volume.”

Automotive, tactical. Translation cost growth out of proportion to fleet or volume growth signals a lack of single-source authoring; every market variant is being translated independently. The fix is in the reuse architecture, not in translation procurement.
“Our MRO's S1000D conversion has stalled at the data-module structure phase.”

Aviation, operational. Stalled S1000D conversions in MRO contexts usually fail when the source content doesn't decompose into S1000D's required data module types (procedural vs descriptive vs wiring). The IA work has to come before the migration toolchain runs.
“An FRA inspection found maintenance-documentation gaps tied to AAR M-1003 quality-system requirements.”

Rail, tactical. M-1003 quality-system gaps tied to documentation usually mean configuration-management metadata is missing or inconsistent across maintenance work orders. The audit response runs through metadata architecture and CCMS workflow design.
“Our classification society flagged inconsistent operating documentation across vessel classes after a port state control inspection.”

Maritime, tactical. Class-society findings on documentation usually mean variant management is broken — different vessel classes carry different operating procedures and the variant control hasn't kept up with fleet additions. Conditional-content profiling under DITA is the structural fix.

Where Extense's capabilities apply.

Information Architecture: Asset-family and program-level content models across modes — vehicle families and platforms (auto), aircraft type-certificate variants (aviation), rolling-stock platforms (rail), vessel classes and shipyard programs (marine). Conditional content for variant management; integration architecture with parts catalogs and configuration-management systems. Project-Based — asset-family content model work with named acceptance criteria, often the prerequisite for any cross-mode migration.
Content Migration: Often follows M&A, platform consolidation, or regulatory mandate to modernize. Legacy estates converged onto a single CCMS — automotive OEM platform consolidations, MRO toolchain migrations, rail OEM legacy estates from acquired product lines, shipyard documentation systems. Conversion handled at scale. Project-Based — fixed scope, conversion-fidelity acceptance criteria. Often follows M&A or platform consolidation across modes.
CCMS & Publishing: Heavy in this vertical across all four modes. Service-information libraries are large, frequently updated, and operationally critical; CCMS configuration and publishing automation are the operational backbone for every transportation OEM, MRO, and operator that ships maintenance documentation. Project-Based for implementation; Managed Services for ongoing administration of the publishing pipeline once stable.
AI-Ready Content: Service-technician-facing and crew-facing AI assistants are emerging use cases — automotive dealer-network technician tools, aviation MRO troubleshooting assistants, rail maintenance support, marine shipboard reference systems. Retrieval over service-information estates requires the same engineering discipline as regulated-industry RAG; provenance metadata matters more than recency. Often starts as Staff Augmentation during technician-assistant exploratory work; converts to Project-Based once retrieval architecture firms up.

Engagements in this vertical.

A global automotive OEM consolidating dealer service information across 30+ markets.

Single-source DITA across vehicle programs with conditional content for market and trim variants. CCMS-driven workflows replaced parallel publishing chains; translation savings drove the business case across the global dealer network.

A commercial aviation MRO modernizing maintenance documentation onto S1000D.

Migration from legacy FrameMaker manuals to an S1000D-conformant data module repository. Configuration management aligned to airframe type-certificate variants; publishing pipeline integrated with the MRO's work-card system. FAA Part 145 audit trail preserved through the migration.

Case studies anonymized for client confidentiality. Specific scope and named outcomes available under appropriate NDA channels.

Sample Content Assessment

Submit a 20-page service or maintenance documentation sample — automotive, aviation, rail, or marine. We'll return a translation-savings assessment, conversion feasibility, and the architecture decisions that would shape a production migration. Two business days, no obligation to proceed.

Submit a sample →