When complex products, such as aircraft, automobiles, or factory machines, are delivered to customers, they typically come in a customer-specific configuration. The configuration determines the components included in a particular product.
For example, when an aircraft maker sells an aircraft to airlines, each airline orders their own configuration of the aircraft. Needless to say that a component (such as an engine or a certain version of the software) may be part of multiple configurations, and new configurations are constantly built. Engineers provided with the configuration name, usually have a way to find out which components should be included in each configuration.
Technical documentation teams also need to have an efficient (and preferably automated) way to identify which content describing individual components is required for a specific configuration and to assemble it into a complete set of documentation deliverables.
In this webinar, you will learn:
- What a configuration database is
- How product content is matched to the product configuration
- Why the traditional way of content profiling doesn't always work for configuration-based product assembly
- How Boolean statements can be used in conditional content expressions and why they make conditional content filtering more flexible
- Why content has to be in a structured format to enable automatic content assembly