Docs per customer

Give each customer the procedures their equipment requires

An operations manual can contain accurate topics and still be wrong for a customer. If a drive-equipped pump receives standard motor-starter instructions, the operator must work out what to ignore. Configuration-aware content makes inclusion and exclusion deliberate.

See the comparison

The task in this example

Build Northfield Water’s operations and maintenance manual for its PX-400 pumps.

Business goal: Build brand loyalty
Business metric: Time to value

The installed options determine the manual

Northfield’s installed pumps have variable-speed drives in both cases. The comparison holds the equipment constant and changes whether topic applicability and option dependencies drive assembly.

A generic manual leaves selection to the operator

Topics have no option applicability.

The manual includes standard motor-starter startup and leaves the drive-specific sequence difficult to locate.

Equipment: PX-400 with variable-speed drive
Startup selection: Generic motor-starter procedure
Exclusions: Not checked

Operators must ask which procedure applies

The manual follows the installed configuration

Topic metadata and dependencies connect the drive option to its startup and alarm procedures.

The assembled manual includes the drive-specific tasks and excludes procedures for options Northfield lacks.

Equipment: PX-400 with variable-speed drive
Startup selection: Drive-specific procedure
Exclusions: Checked against configuration

The manual can support commissioning

Match coverage to the installed equipment

Personalization is useful when it removes uncertainty without dropping necessary tasks. Measure coverage and incorrect inclusions before claiming a faster path into operation.

Select applicable content

Match model, options, and region to maintained topics.
- Procedure coverage
- Nothing extra
Use the manual

Operators attempt the relevant maintenance and startup tasks.
- Operator calls

Business metric

Time to value

Measure time from an agreed delivery milestone to verified operational readiness for comparable installations.

What to measure and how to interpret it

Create a reviewed expected topic set for a sample configuration. Check every required procedure and every exclusion against that set, including option-dependent tasks.

Procedure coverage: Share of required tasks present for the installed configuration; record safety-critical omissions separately.
Nothing extra: Share of included tasks that apply to the customer’s equipment. Inspect misleading instructions even when coverage is high.
Operator calls: Contacts asking which procedure applies, classified by configuration and task.
Writer hours: Effort to assemble, check, and maintain each configuration-specific manual.

Check the business result

Compare readiness time for similar installations and record delays attributable to incorrect or missing procedures. Track wrong-procedure incidents as a quality constraint. Equipment, training, and commissioning conditions also affect readiness.

Schedule a call

Make applicability part of the topic

The installed-base record says what the customer has. Content must say which tasks apply and what other tasks an option changes.

PX-400 / Startup / Drive option

Applicability rule

Select the drive-specific startup procedure

Use the variable-speed-drive startup task when the installed unit includes that option.

Match: Model PX-400; variable-speed-drive option present
Include: Drive startup and applicable drive alarm tasks
Exclude: Standard motor-starter startup
Dependency: Drive option changes startup and alarm coverage
Rebuild trigger: Approved installed-configuration change

Intelligent content

Maintain reusable procedures that can stand alone in an assembled manual, with their prerequisites and warnings intact.

Taxonomy

Use curated model, option, region, and task values shared with installed-base data.

Ontology and knowledge graph

Represent dependencies between an option and all affected tasks. The drive’s presence changes more than a single topic selection.

A practical starting point

Model one customer configuration and compare the generated manual with a service engineer’s expected set. Include a configuration change to test rebuild behavior.

Installed-base owners maintain the equipment record. Publishing assembles outputs; service and documentation owners verify that the manual is complete for the intended work.

See how this scenario works

Explore the work with Intuitive Stack

How much of your manual asks operators to choose what applies?

Intuitive Stack can help model topic applicability and option dependencies, then test a customer-specific manual with your service and installed-base teams.

Configuration-to-topic matching
Required and excluded procedures
Rebuilds after equipment changes

Schedule a call Explore the implementation