Skip to main content
Shakewell

Explainer

The S-Series, Mapped: S1000D and Its Six Siblings

Most people meet S1000D first and assume it stands alone. It doesn't — it's one member of a seven-spec family that covers supporting a complex product from first analysis to last flight.

The Family

Seven Specs, One Product

The ASD/AIA S-Seriesis a coordinated family of Integrated Product Support specifications — the industry's shared answer to the question every complex program faces: what will supporting this product require, and how do we manage that as data rather than folklore? Each member owns one discipline:

  • S1000DTechnical publications

    The one everyone knows: international specification for technical publications, built on reusable data modules in a common source database.

  • S2000MMateriel management

    Provisioning and materiel data — selecting and managing the support items and spares, and exchanging that data between industry and customer.

  • S3000LLogistic Support Analysis

    The upstream analysis: what supporting the product will require. Its LSA data is the baselining source for publications, materiel, support equipment, and training.

  • S4000PPreventive maintenance

    Developing and continuously improving preventive maintenance — the reliability-driven analysis behind the scheduled maintenance program.

  • S5000FIn-service data feedback

    The return channel: feedback processes and data from the in-service phase, closing the loop back into analysis and maintenance planning.

  • S6000TTraining analysis and design

    Standardizing training needs analysis — deriving who must be trained to do what, from the same product data the rest of the family shares.

  • SX000iThe integrating guide

    The overarching specification for integrated product support: how the family is used together, coherently, across domains and stakeholders.

The Flow

The Data Moves in a Loop

A complex product supported across its whole lifecycle
Analysis decides the tasks, publications document them, materiel provisions them, service experience feeds back — one loop, seven specs.

The map matters because the family is a pipeline, not a shelf. S3000L analysis decides which maintenance tasks exist and what each consumes; those tasks become the procedures authored under S1000D and the support items provisioned under S2000M; S4000P shapes the preventive program; S6000T derives the training; and S5000F carries what the fleet actually experiences back upstream to revise all of it — with SX000i as the guide that keeps the disciplines speaking one language. When the loop is connected, the manual, the parts catalog, and the training course describe the same product. When it isn't, each team re-derives the data by hand, and the divergence surfaces at the worst possible reviews.

Our practice lives mostly in the publications and delivery end of the loop — S1000D authoring, CSDB operations, and the platforms that serve the output — but the family map is where every scoping conversation should start, because what a program owes under one spec is usually defined by data another spec owns.

FAQ

Questions We Hear

What is the ASD/AIA S-Series?

A family of international Integrated Product Support (IPS) specifications jointly produced by the ASD and AIA aerospace industry associations, covering the support of complex products end to end: S1000D for technical publications, S2000M for materiel management, S3000L for Logistic Support Analysis, S4000P for preventive maintenance development, S5000F for in-service data feedback, S6000T for training analysis and design, and SX000i as the overarching guide that keeps the family coherent.

Why does the family structure matter if my contract only cites S1000D?

Because the specs describe one product from connected angles, and the data is designed to flow between them: the maintenance tasks your S1000D procedures document are derived under S3000L analysis; the parts your IPC lists are provisioned under S2000M; in-service findings return through S5000F to revise all of it. A program that treats its cited spec as an island re-derives shared data by hand — and the disagreements surface in front of the customer.

Do all programs use all seven?

No. S1000D and S2000M are by far the most commonly contracted, and many programs cite only one or two family members while handling the other disciplines by national or company standards. The family's value is that when a program does scale up, the interfaces are already designed — adopting a sibling extends the data model rather than colliding with it.

Where do the specifications come from, and what do they cost?

They are published jointly by ASD (the AeroSpace and Defence Industries Association of Europe) and the AIA (Aerospace Industries Association), with the official S-Series site as the source of record for current issues and downloads. S1000D has long been famous for being freely downloadable; check the official site for the terms on each sibling rather than trusting third-party mirrors.

Get In Touch

Which Siblings Does Your Program Owe?

If your contract cites one family member, the data it depends on probably lives under another. We scope S-Series obligations before they become findings.