Home → Standards → GEIA-STD-0007
Logistics product data is authored elsewhere. Ironmark ingests it into a project, maps it to the source-of-record modules, and lets the applicability model align it with downstream S1000D or MIL-STD-40051 output.
| Ingest | Source-project → master-project with applicability-tagged rollup. Preview shows per-document dispositions (new / merge / skip) before commit. |
| Baseline tracking | Each ingest is recorded with source baseline id + name. "Newer baseline available" state surfaces when the source project has advanced past the last ingest. |
| Applicability alignment | An applic_tag attaches to the ingested content so downstream applicability filters (CCT / ACT / PCT) pick it up on the same terms as native-authored content. |
| Graphics | Cross-project graphics come across scoped to the master project. ICNs are cross-project-unique so a shared ICN across two sources doesn't collide. |
| Traceability | Ingest records keep the source-of-record link for audit. A downstream S1000D DM referencing an ingested LSA row can trace back to the source baseline. |
A project scoped to the LSA/product-data source. Applicability filters describe which target manuals the rows apply to.
From the master project, pick a source baseline, an applicability tag, and preview. Ironmark shows per-document dispositions. Confirm to commit; the ingest record is created and rows land in the master project's document set with the applic tag applied.
The master project publishes to whatever target its docs conform to — S1000D DMs, 40051 WPs, PDF, IADS. Ingested rows participate in applicability filters like native content.