Ascii1000D Demonstration

DMC-ASDEMO-AAAA-000-00-00-01A-000B-A

Figure 1. Simple Example of Ascii1000D CCS^[1] Functionality

Premise

The S1000D specification combines three separate specifications:

1. Business Architecture Specification includes elements like DMC components (MODELIC, SDC, MICC, SNS, etc), Applicability, CIRs and other constructs supporting defense and aerospace technical data.

2. Semantic Specification relates elements to semantic elements, like //step as procedural element, //challrsp as challenge / response element.

3. Markup Specification the actual XSD that defines the XML markup.

Full S1000D systems have combined costs ranging from $12k per user per year to $50k per user per year, not counting migration and maintenance costs. Smaller organizations are unable to support these costs while remaining competitive.

However the Business Architecture is often the singular critical aspect for supporting aerospace and defense projects. Ascii1000D uses the S1000D business architecture as applied in the Asciidoc LML (lightweight markup language), with additional Semantic Specification requirements supported via the use of Asciidoc Roles.

Using an LML provides a CCMS framework with standard technology on established tooling, rather than bespoke CCMS (component content management system), bespoke editor, and likely a separate bespoke build engine for PDFs and IETMs.

Ascii1000D

Demonstration of an S1000D publication architecture using the Asciidoc LML (lightweight markup language).

• S1000D-style filenaming conventions

• CIRs/TIRs (Common Information Repositories) / (Technical Information Repositories) via Include Directive to tagged regions

• Conditional Content aka Applicability via Asciidoc Conditional Directives

• Content re-use PM (Publication Module) and DMRL (Data Module Requirement List) via Asciidoc Include Directives, and DMRLs for project planning.

• Validation requirement is satisfied/exceeded via usage of linters: LanguageTools, Vale, and/or Redpen.cc.

• Line art parts identification via SVG+CSS or inclusion of X3D or applicable HTML5 web 3d format.

See Parts Data Flow for details on data flow from parts information systems to the Ascii1000D files.

Parts data information is always customized for each business. In the below example, we can see that parts data changes as the product maturity advances.

Figure 2. The red line shows one of the big problems: MTAs need to be done before writers start writing.

---

1. Component Content System