Lead
Build capability
We guide your people through the work, building capability that stays with your team.
Back to the business caseDocs per customer · Implementation
Assemble the manual from configuration and dependencies
The workflow joins installed equipment data with content applicability. Relationship checks extend simple filtering to the other procedures an option changes.
Follow the process- Business goal
- Build brand loyalty
- Business metric
- Time to value
Build one configuration-specific manual
Use an approved installed-base snapshot and shared identifiers for models and options. Agree on the manual’s required task coverage with service owners.
The task in this example
Build Northfield Water’s operations and maintenance manual for its PX-400 pumps.
- Step 1
Read the configuration
Retrieve Northfield’s sites, units, and installed options.
Product or customer dataInstalled-base records identify the actual units; missing option values must be resolved before selection.
- Step 2
Select topics
Match topics to model, options, and region.
TaxonomyClassify applicability with controlled values rather than free-text customer names.
- Step 3
Follow dependencies
Find all tasks affected by the drive option.
Ontology and knowledge graphConnect the option to startup, alarms, and related procedures; explain why each topic is included.
- Step 4
Assemble and check
Build the manual in the intended order.
SystemThe publishing pipeline resolves reuse and renders the output.
PeopleService owners review coverage and inappropriate inclusions against the expected set.
- Step 5
Deliver and maintain
Publish the checked manual to Northfield’s portal or devices.
SystemTie the delivered manual to its configuration snapshot and rebuild when an approved configuration change arrives.
This framework provides a practical baseline shaped by experience. Every organization operates under distinct technical and operational realities that require tailored design and governance. While you can adapt these measures independently, we frequently partner with teams to customize governance, integrations, and rollout. Performance outcomes will naturally vary.
Why these content layers matter
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.
Verify the result and handle exceptions
Compare the manual with the expected topic set. Test a drive-equipped unit and a standard unit, and confirm that warnings survive assembly and that excluded procedures remain absent.
Treat unknown configurations, conflicting option records, and missing applicability as exceptions requiring review. A generic fallback manual must be clearly identified and assessed before delivery.
How we work
with your team
We can guide your team, work alongside it, or deliver the work for you. Combine these approaches as your needs and capacity change.
Support
Add specialist backup
Your team owns the work. We provide experienced backup and specialist help where you need it.
Do
Delegate delivery
We handle work that is one-time, specialized, or outside your core business, without adding an ongoing burden to your team.
Build your team's skills with standard and custom courses.
Support for this implementation
Define customer task coverage, content ownership, and review rules before assembling configuration-specific procedures.
- Content strategySet priorities, ownership, and a rollout your team can sustain.
- Metadata and iiRDSDefine classification and delivery metadata, using iiRDS where it fits.
- User experienceDesign and test the experience around real user tasks.
- DITA-OT plugin developmentExtend validation and publishing when your workflow uses DITA.
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.