notusCSDB is a light-weight but highly functional CSDB (Common Source Database) for managing multiple S1000D projects. From the ground up it offers you a quick to install, easy to learn and adopt CSDB to minimise on-boarding time and maximise return on investment.

Now with our notusBookBuild as an optional server add-on, you can create, manage and deliver all your S1000D content from one simple dashboard.

For more information visit the notusCSDB page.

This video gives a brief overview of notusCSDB.

The Eclipse A350 BookBuild application enables compliant S1000D Data Modules to be rapidly converted into an A350 CDIM Component Maintenance Manual (CMM).

The application creates a PDF file from the Data Modules that includes Special Modules such as Front Cover, List of Acronyms and Table of Contents. Cross referencing between the various Data Modules is automatically resolved and all cross references in the PDF are converted to Hypertext Links. The PDF file can be used to print the CMM to produce a hard copy or delivered as is to provide a straightforward IETP.

Provided the various files have been located in accordance with the A350 CDIM, creating the CMM is just three clicks away.

This video shows the creation of the A350 CMM from start to finish. It introduces some of the requirements of the A350 CDM and then demonstrates the actual creation of the output PDF file.

The Eclipse ATA CMP BookBuild application is designed to enable users to produce an ATA Component Maintenance Publication (CMP) from a number of S1000D Issue 4.2 Data Modules which have been created to the ATA CMP Business Rules. Eclipse S1000D for FrameMaker is a suitable application for creating these modules as it has a preference for working to the ATA CMP Busines Rules.

The build process is driven from a compliant Publication Module and requires little input from the user. Becuase the application has been designed in accordance with the Business Rules there are no user options which can affect the output.

The application creates the initial publication and, at the same time, because there is no historical updating information in Issue 4.2 Data Modules, a History file is created. This file is used to track changes in subsequent updates. Creating the updates is very straightforward using, as it does, the next issue of the Publication Module

This video shows the various background facts and demonstrates the application in use.

This video gives a brief overview of the Eclipse BookBuild application, the principles, functionality and the overall process. This is an essential video for those who are contemplating using BookBuild.

An introduction to the Eclipse BookBuild (for S1000D) providing brief discussion of the application’s purpose and features.

This video shows how to populate the BookBuild file using the Basic method. It covers the insertion of Preliminary Data Modules, Content Data Modules, the MultiDM element, a PMEntry file to allow chapterisation and then initialising the Book.

An introduction to the requirements for the creation of a BookBuild file.

This video shows how to populate the BookBuild file using the Basic method. It covers the insertion of Preliminary Data Modules, Content Data Modules, the MultiDM element, a PMEntry file to allow chapterisation and then initialising the Book.

A presentation showing the creation of the BookBuild file using a basic procedure.

This video shows how an existing Publication Module can be used to populate the BookBuild file. It also indicates the nature of the remedial work required (due to the limited information contained). Setting the publication options is included.

A presentation showing the creation of the BookBuild file using a previously created S1000D Publication Module.

This video covers the sequence of required events to build a book using BookBuild. It explains the overall process and the provided feedback using a Log Console. This video uses screen shots to explain what is happening and the feedback.

A presentation process of building a Book using BookBuild.

This video shows the BookBuild process from the perspective of the Log Console covering each stage as it progresses. This video is almost completely uses the Log Console sequence from start of the build process to the end and the resulting PDF file.

A ‘live’ build showing the Log Console to demonstrate the various stages of the build process.

Demonstrating the steps required to prepare BookBuild for the creation of the next issue.

Moving the BookBuild file from one issue to the next.

The Eclipse BREX Checker provides a tool for checking one or more S1000D Data Modules against a defined set of Business Rules.

This video gives a brief overview of the Eclipse IPD Generator for S1000D. It provides an introduction to the application interface followed by an outline of the workflow used to map the schema to an appropriate spreadsheet and then build the IPD data module using the data extracted from the spreadsheet.

An introduction to the Eclipse IPD Builder for S1000D providing brief discussion of the application’s purpose and features

The spreadsheet file used in the process needs to be a .csv file which is consistent in the location of all the data for inclusion in the IPD data module. This file can be generated from a parts list database or even as a two-stage process with the parts list generating the IPD data information and a spreadsheet programme being used to insert the IDStatus information. This video shows one form of spreadsheet content.

A discussion of a possible spreadsheet which can be used with the Eclipse IPD Builder for S1000D.

This video shows how to start a new mapping file and then continues to show the process required to map the ID area of the spreadsheet to the appropriate schema elements and attributes.

A presentation showing the mapping of the ID part of the schema to the spreadsheet contents.

This video shows the mapping of some of the status schema elements and attributes to the spreadsheet cells.

A presentation showing the mapping of the status part of the schema to the spreadsheet contents.

This video shows the mapping of the figure data, the title and the filename, to the schema elements and attributes. This mapping allows the IPD generation to automatically insert a figure into the IPD data module so that is displayed when opened in a suitably configured application.

A presentation showing the mapping of the figure part of the schema to the spreadsheet contents.

Unlike the previous mapping method, the mapping of the parts data is to the column headings for the many rows of parts data. The application determines which IPD element matches the parts data headings and populates the IPD data module appropriately.

A presentation showing the mapping of the parts list data part of the schema to the spreadsheet contents.

Demonstrates the operation viewed when generating an IPD. It then demonstrates viewing the IPD for QA purposes. In this case we are using the Eclipse S1000D for FrameMaker application.

Building the IPD Data Module and then viewing it using the Eclipse S1000D for FrameMaker application.

This video gives a brief overview of the Eclipse IPL Generator for iSpec 2200. It provides an introduction to the application interface followed by an outline of the workflow used to map the schema to an appropriate spreadsheet and then build the IPL SGML file using the data extracted from the spreadsheet.

An introduction to the Eclipse IPL Generator for iSpec 2200 providing brief discussion of the application’s purpose and features.

The spreadsheet file used in the process needs to be a .csv file which is consistent in the location of all the data for inclusion in the Eclipse IPL SGML file. This file can be generated from a parts list database or even as a two-stage process with the parts list generating the IPL data information. This video shows one form of spreadsheet content.

A discussion of a possible spreadsheet which can be used with the Eclipse IPL Generator for iSpec 2200.

This video shows how to start a new mapping file and then continues to show the process required to map the IPL figure DTD elements to the appropriate DTD elements.

A presentation showing the mapping of the IPL figure data in the DTD to the spreadsheet contents.

This video shows the mapping of some of the IPL data headings which are used to identify the Parts List Data Columns in the spreadsheet.

A presentation showing the mapping of the IPL data headings section of the spreadsheet.

This video shows the mapping of the IPL data section part of the DTD to the spreadsheet contents. Also covered is the built in scripting language to enable the multi function spreadsheet cells to individual parts of the DTD.

A presentation showing the mapping of the IPL data section of the spreadsheet to the DTD. This includes information about the Scripting functions used to extract the IPL data from spreadsheet cells which contain more then one item of data.

This video shows the application generating the IPL SGML file with the feedback. It also shows the insertion of additional information into the conversion process to allow data not included in the spreadsheet to be accommodated. The copying of the SGML file content into a CMM PageBlock is included.

A presentation showing the build process and the subsequent copying of the SGML file into a CMM.

Introduces the iSpec2200 for FrameMaker application. It provides a quick overview of the features provided in the application.

Introduces the iSpec 2200 for FrameMaker application, providing a quick overview of the features provided.

iSpec 2200 provides information on how elements in the structure should be displayed but users will realise that their clients often require deviations from these.

Eclipse iSpec2200 for FrameMaker application provides the means for a user to create their own template to satisfy their client’s requirements.

This video outlines those facilities.

Eclipse iSpec 2200 provides the means for a user to create their own template to satisfy their client’s requirements.

The iSpec 2200 provides for five different task types. Eclipse iSpec2200 for FrameMaker allows the user to select the type required in the publication. Although iSpec 2200 indicates that a CMM should only have one task type throughout, our clients have been faced with the requirement to have PageBlocks with different task types within a CMM.

Provision has also been made to allow for mixed task types within individual PageBlocks.

The iSpec 2200 provides for five different Task types. This application allows the user to select the type required in the publication.

The Illustrated Parts List constitutes and important part of the CMM. The initial IPL PageBlock provides some typical text to explain what the various parts of the IPL indicate. Although this is provided users are free to change this content to suit their particular requirements.

To assist the user, the IPL functionality includes the facility to generate some lists and indexes automatically. For example, a numerical list of parts can be generated; a function which will save a considerable amount of time.

The Illustrated Parts List constitutes an important part of the CMM. The initial IPL PageBlock provides some typical text to explain what the various parts of the IPL indicate.

For those components which required only very short documentation, the ACMM is an ideal means of providing the information required. The Eclipse iSpec 2200 application provides the functionality to create and maintain this document.

Most of the same functions provided for working with CMMs are provided.

For those components which required only very short documentation, the ACMM is an ideal means of providing the information required. The Eclipse iSpec 2200 application provides the functionality to create and maintain this document.

Revision management forms an important part of working with CMM and ACMM publications. The iSpec 2200 application has  revision management tightly integrated into it.

Revision management forms an important part of working with CMM and ACMM publications. The iSpec 2200 application has revision management tightly integrated into it.

Contiem are delighted to announce the release of version 10 Eclipse S1000D for FrameMaker, which includes a number of new features and enhancements:

** Some of the new features have maximum effect when used in conjunction with the Eclipse S1000D BookBuild application so we will be having a look at the output from that to demonstrate these features more fully.

The video below is a recording of the launch webinar.

This video demonstrates the various stages of installing the Eclipse S1000D for FrameMaker application.

The process described relates to the installation on a standalone computer.

During the process the installer will need to send some information to Contiem so that a valid License key can be obtained. The key must be installed before the Eclipse application can be used in a productive environment.

This video demonstrates the procedure for updating Eclipse S1000D for FrameMaker.

This procedure must be carried out whenever the user needs to update Eclipse S1000D for FrameMaker. This will be necessary when a new version of the application is released.

New releases are made under one or more situations:

It is not necessary to contact Contiem during this process. The license key is not removed during the process and thus remains relevant.

The iSpec 2200 provides for five different Task types. This application allows the user to select the type required in the publication.

Demonstrating the insertion of the basic authoring elements into a descriptive data module. Shows the ease of authoring when using Eclipse S1000D for FrameMaker which in some aspects is as easy to use as one’s favourite Word Processor.

Lists are easily inserted and in the case of bulleted lists, the bullet character is easily changed from the default.

Shows the ease of authoring when using Eclipse S1000D for FrameMaker which in some aspects is as easy to use as one’s favourite word processor.

Demonstrating the insertion of warnings and cautions into a descriptive data module.

The process of inserting warnings and cautions is the same when editing other data module types, especially procedural.

This video also includes the insertion of symbols associated with the warnings and cautions the the method used to re-size them to suitable dimensions for display purposes.

The process of inserting warnings and cautions into a descriptive data module is the same when editing other data module types, especially procedural.

Demonstrating the insertion of an illustration/graphic into a descriptive data module.

The exact term used for an illustration will depend on the industry involved. In all cases an illustration, graphic, picture is inserted using the S1000D figure element.

The process of inserting an illustration is the same when editing other data module types, especially procedural.

This video assumes that the Data Reference Manager facility has not been enabled.

The process of inserting an illustration into a descriptive data module.

Demonstrating the insertion of an illustration/graphic into a descriptive data module using the Data Reference Manager.

The exact term used for an illustration will depend on the industry involved. In all cases an illustration, graphic, picture is inserted using the S1000D figure element.

The process of inserting an illustration is the same when editing other data module types, especially procedural.

The illustration inserted in this video contains hot spots (CGM File) and demonstrates the intuitive hot spot facility included in Eclipse S1000D for FrameMaker.

There is not an ISO 8879 (SGML/XML) method of accommodating hot spots. S1000D has defined how the standard requires hot spots to be handled. Eclipse S1000D FrameMaker conforms to this specification.

Inserting an Illustration/graphic into a Descriptive Data Module using the Data Reference Manager.

Demonstrating the insertion of a cross reference to a hotspot.

The process of inserting a reference to a hotspot is the same when editing other data module types especially procedural.

The process of inserting a cross reference to a hotspot utilises an intuitive interface designed specifically for this purpose.

Demonstrating the insertion of a cross reference to a hotspot.

Demonstrating the insertion of a cross reference from a hotspot to another location within the data module.

The process of inserting a cross reference from a hotspot is the same when editing other data module types especially procedural.

The process of inserting a cross reference from a hotspot utilises an intuitive interface designed specifically for this purpose. Without this interface this procedure can, at times, be very difficult.

Creating a cross reference from a hotspot to another location within the data module.

Demonstrating the insertion of a reference to another data module (the dmRef element). The video shows the use of the Data Reference Manager during this procedure.

The process of inserting a dmRef is the same when editing other data module types, especially procedural.

Inserting the dmRef element without the use of the DRM can be difficult at times. The correct working of the reference to other data modules using the dmRef element relies on the accuracy of the data module code (DMC) value being inserted.

If a single character in the code is incorrect the link will not work when the publication is published. Correctly using the Data Reference Manager almost eliminates the chance of inserting an incorrect link value.

This video also includes the updating of the references table found at the beginning of all data modules.

Demonstrating the insertion of a reference to another data module (the dmRef / RefDM element).

Demonstrating the insertion of a table in a data module.

The process of inserting a table is the same when editing other data module types, especially procedural.

Once the table has been inserted using the Eclipse S1000D for FrameMaker application it is possible to modify the table in most ways using the native FrameMaker editing functions. Using these:

The process of inserting a table is the same when editing other data module types especially procedural.

Demonstrating the insertion of steps etc into a procedural data module.

From S1000D Issue 4 steps have been recursive and this video demonstrates the insertion of the step element.

Demonstrating the insertion of steps etc into a procedural data module.

Demonstrating the insertion of data into one of the standard tables found at the start of the procedural (and some other) data modules. The tables, in the preliminary requirements section of the data module, are for:

The content structure of these three tables are the same. Populating the tables by hand is an arduous undertaking and even more so when considering that the same information often has to be inserted into several data modules.

Using the Data Reference Manager, the database is populated with the necessary information. Insertion of the data into the tables is largely a matter of deciding what entries are required. The authors need only to select which entries are required and then click the insert button for the table to be correctly populated.

Inserting data into one of the standard tables found at the start of the procedural, and some other, data modules.

This video in the series was replaced by a new video under the Working with Common Repositories section – see below

Very often in creating and editing data modules the user finds themself using the same phrase or structure but has to start creating it from scratch. The alternative is to open a data module where the phrase or structure is located and then copy it into the current data module.

The common phrases feature enables the user to store common text or even common structures in the Data Reference Manager for future use.

This feature also ensures that these phrases will used consistently without mistakes. This is of particular importance when a specific mark up structure has been agreed for use.

The common phrases feature enables the user to store common text or even common structures into the Data Reference Manager for future use.

The Data Reference Manager can be used to store preliminary requirements items which can then be used to rapidly populate the preliminary requirements table in procedural and other data module types.

There are four types of preliminary requirements:

The population of the preliminary requirements table in the Data Reference Manager is sped up by using data already stored in the DRM eg data module code.

The Data Reference Manager can be used to store preliminary requirements items which can then be used to rapidly populate the preliminary requirements table in procedural and other data module types.

Captions are a very useful way to displaying annunciator and mimic panels in data modules. These are often indicators and/or illuminated switches which can be problematic to illustrate.

Captions were introduced with the Aircrew (now Crew) data module to represent the indicators in Aircraft. Since then there have been a number of other uses defined.

This short video shows how a very simple caption arrangement can be created in a data module.

This short video shows how a very simple caption arrangement can be created in a data module.

The warnings and cautions repository comprises a normal descriptive data module which has been given an information code of 012 and a deviation code of A.

If there is more than one repository file the procedure is slightly different and this is explained in the user guide to which reference should be made.

The common phrases feature enables the user to store common text or even common structures into the Data Reference Manager for future use.

This video demonstrates how references to relevant data modules are inserted in a container module so that the applicability mechanism (not part of Eclipse S1000D for FrameMaker application) can be used to determine which data module is used in the final output.

This video demonstrates how references to relevant data modules are inserted in a container module

This video demonstrates how a tools table in a procedural data module (and any other data module that has the preliminary requirements section) can extract information from the tools repository.

Although the reference in this video is to the tools repository, the procedures are equally relevant to the spares and consumable information.

This video demonstrates how a tools Table in a Procedural Data Module can extract information from the Tools Repository.