eko•ILS Logistics GmbH has become a renowned service provider and point of contact when it comes to creating technical documentation for the AECMA and ASD/AIA S1000D specifications.
Our experience in this regard has allowed us to successfully complete a large number of projects for the German Navy and Air Force as end users and, in recent years, for a large number of system manufacturers and suppliers as well.
Any documentation to be created in this area is based on the ASD S1000D specification, versions 1.7 through 4.0.
Additional standardisation specifications are also taken into account for specific projects. When it comes to the German armed forces, this includes the various editions of the National Style Guide NSG (up to the current 3.4 version). Other projects also take more far-reaching/other requirements into account that more closely define the application of the respective S1000D specification. Hence, these must be carefully analysed at the start of any project in order to determine how to process them.
An IETD is generally created in accordance with the process defined in ASD S1000D. Any required specific details are stipulated in a Guidance Document and can be further adapted in specific cases and after consultation with the customer.
After the SNS and DMRL/DMSL have been submitted and approved in order to define the documentation breakdown, structure and information types involved, additional content related components of the IETD are then created and delivered. This is followed by the Comment procedure, which is used to review by the contracting authority until final delivery of the IETD.
The various process steps involved in the creation, review and approval of an IETD require a variety of suitable IT-based tools in order to achieve end-to-end information and procedural conformity.
In this regard, we at eko•ILS Logistics GmbH not only rely on well-established, commercially available products, but have also been able to apply our longstanding experience to the development of our own tools.
Not only do we use a standardised editor (PTC Arbortext Editor) to generate the required XML components, we also use our own applications and test guidelines for our in-house QA testing purposes.