Author, publish, and hand off every technical manual from one browser.

Browser-based, schema-aware editor with context-filtered element completion, real-time validation, and inline error reporting. No desktop installation required.

Fig. 4.1 — Four editor views: structured, visual, preview, and source XML. Tabs cycle every 4 seconds.

• .01Element palette filtered by active standard and cursor position
• .02Real-time XSD, DTD, and BREX validation with inline markers
• .03Structured preview with proper admonition styling
• .04Check out / check in with exclusive locking
• .05Change notice and effectivity tracking on every check-in
• .06CGM, SVG, PNG, and TIFF graphic support with ICN management

Central repository for all technical documents. Browse, search, and filter by type, status, standard, or validation state. Every revision stored with author, timestamp, and change notice reference.

Fig. 5.1 — The library, filtered.

• .01Search and filter by DMC, type, standard, status, or validation
• .02Version history with element-level structural comparison
• .03Named baselines for publication milestones
• .04Side-by-side diff at paragraph, step, table row, and figure level
• .05HMAC-chained audit log exportable for SIEM integration

Role-based review workflow routes documents through Peer Review, QA, and Final Approval. Inline review (IPRF) comments carry category and severity classification. Field reviewer redline submissions flow into the QA queue for triage.

Fig. 6.1 — Queue view with severity chips.

• .01Author → Peer Review → QA → Approval gates
• .02Threaded comments with mandatory / recommended / query severity
• .03Aggregate review result: Approved, Accepted with Comments, Rejected
• .04Full review history per document version and cycle

Full manual assembly with cover page, warning summary, LEP, table of contents, all work packages in order, and alphabetical index — in a single PDF. Change bars computed automatically from version history.

Fig. 7.1 — Publications with cycle history.

• .01MIL-STD-40051 compliant PDF stylesheets via Apache FOP
• .02Automatic change bars from baseline comparison
• .03Automatic List of Effective Pages generation
• .04IETP-X / MIL-PRF-63029J interactive output
• .05Multiple output profiles per program
• .06Applicability filtering applied at publish time

Common Source Database with full DMC management, SNS tree visualization, and cross-reference integrity checking. Automatic DMRL generation and SNS gap analysis.

Fig. 8.1 — DMC parser, SNS gap analysis, and xref health.

• .01DMC parsing and validation for S1000D document coding
• .02SNS tree with gap analysis and suggestions
• .03Cross-reference extraction and broken-link detection
• .04Business rule management with BREX integration

An interactive builder for structureObjectRule entries — pick the target element, scope, allowed values, and messaging from the form, or drop into an XPath escape hatch when the form isn't enough. Dry-run against the project to see what would flag before you commit the rule.

Fig. 9.1 — Existing rules on the left, form + XPath preview on the right.

• .01Quick-start templates: "element must have an attribute", "attribute must be one of a list", …
• .02Full XPath escape hatch for rules the form can't express
• .03allowedObjectFlag semantics surfaced directly in the form
• .04Test-against-project button before adding a rule to the live BREX DM
• .05Rules land as regular S1000D BREX data modules — no proprietary rule format

Group projects across different standards into a single acquisition program. Trace GEIA-STD-0007 logistics product data — breakdown elements, maintenance tasks, provisioning, and support equipment — directly to the S1000D or MIL-STD-40051 data modules that document them.

• .01Program groups associate projects across different SDM families
• .02Auto-discover links by matching part numbers, NSNs, CAGE codes, and EIAC/DMC codes
• .03Bidirectional navigation — click from logistics data to the procedure, or back
• .04Traceability matrix report with confidence scoring and coverage statistics
• .05Manual link creation for non-automatable relationships

Every program ships with a branded, customer-facing portal. Assigned customers see the current revision set, acknowledge receipt against a specific revision, and download the package from a URL you own — not a vendor's.

Fig. 11.1 — Subscribed program showing an outstanding acknowledgment.

• .01Per-program access grants — individual users or named recipient lists
• .02Release-note visibility and full prior-revision history on every deliverable
• .03Receipt confirmation gated by an ack-before-download setting when contractually required
• .04Email release notifications when a new revision is promoted
• .05CFI/GFI back-flow — customers upload furnished info against the program record
• .06Expiring, use-capped share links for contacts without portal accounts
• .07Every download logged with user, IP, and timestamp for audit
• .08Custom wordmark, logo, accent color, and CSS per install — airgap-safe, no CDN dependencies

Deliverables table with release notes on every revision, full history, downloads gated to acknowledgment when required, and a customer-side upload panel for CFI/GFI — visible to the contractor team from the same program record.

Fig. 11.2 — Expanded deliverable with release notes and prior revisions.

The internal Deliverables page groups every program's release history in one view. Compare revisions, promote or supersede, mint expiring share links, or review the CFI/GFI a customer has pushed back — without leaving the platform.

Fig. 11.3 — Contractor page with incoming CFI/GFI panel.

A visual builder that produces the actual IADS wire format — a top-of-file <Package> manifest followed by per-file gzip streams, with a proper dataset.xml and, for non-S1000D projects, a nested toc.xml. Round-trips with IADS Native.

Fig. 13.1 — Custom TOC editor with depth controls.

• .01Dataset metadata form — weapon system, revision, publish date, service branch, security marking
• .02All-content or pick-individually document selection
• .03Nested TOC editor with depth controls — chapters, sections, entries
• .04Or upload your own toc.xml built externally in IADS Native
• .05Automatic exclusion of non-content types (DDN, BREX, catalog) unless opted in
• .06S1000D projects skip toc.xml automatically — the Publication Module drives navigation

Maintain a register of every controlled copy issued. Track receipt confirmation, manage supersession and recall, and monitor expiry dates with automatic notifications.

Fig. 14.1 — Numbered copies with receipts and transmission references.

• .01Numbered controlled copies with classification markings
• .02Receipt confirmation and transmission reference tracking
• .03Supersession with automatic replacement issuance
• .04Expiry notifications with configurable lead time
• .05Full chain-of-custody audit trail per copy

A baseline freezes every document's version at a point in time and carries a contract reference. Re-publish from a baseline for a re-issue, diff two baselines to see what changed between deliveries, or bundle multiple baselines into a single export archive with per-baseline subdirectories.

Fig. 15.1 — Named baselines with contract references.

• .01Named, locked snapshots with contract references (CDRL number, delivery ID)
• .02Re-publish or re-export from any baseline without disturbing head
• .03Compare two baselines — per-document version diff, added / removed documents
• .04Multi-baseline export archive: each baseline in its own subdirectory, graphics shared at the root
• .05Change-bar rendering can reference any baseline as the diff origin

Real-time dashboard for program managers showing document status, review pipeline, team activity, and automated alerts for overdue reviews and expiring copies.

Fig. 16.1 — Counts, pipeline, workload, and alerts.