Publication feedback

LiveConnect

Report the issue with the content that prompted it.

A reader in Horizon can raise a question, attach evidence and send the exact publication context. LiveConnect turns that report into a tracked ticket in Axis, where the responsible team can respond and record the resolution.

For maintenance technicians and engineers, and the publications, support and engineering teams that handle their reports.

Datasheet available upon requestRequest a datasheet

Publication feedback
  1. Horizon report
  2. Tracked ticket in Axis
  3. Reply in Horizon
Conceptual workflow illustration.

Give the responding team the same context as the reader.

A report about a procedure or figure needs a precise location. LiveConnect carries the document context with the issue so the receiving team can identify the publication, revision and content the reader was using.

The conversation stays with the ticket. Both the reporter and the responding team can follow its history, and replies return to the Horizon application where the report was raised.

Extends
Horizon and Axis
Administration
Ticket management in Axis
Offline behavior
Reports submit after reconnection
Capabilities

What LiveConnect adds.

Feedback from the reading surface

Raise a report from the data module, figure or procedure in Horizon. Keep the submission tied to its publication context and applicability.

Supporting evidence

Attach screenshots, markups, photographs, audio or notes that help the responsible team understand the issue.

Ticket routing and history

Route the report to the nominated team in Axis. Track its state, responses and resolution in a threaded record visible to the relevant parties.

Replies and notifications

Return replies to the reporter in Horizon and notify responsible teams when tickets are created or change state. Feedback markers in the contents tree identify locations where issues have been raised.

Offline capture

Keep a report on the device while it is offline and submit it when the device reconnects. Ticket management and the responding team’s work take place in the installation.

Working sequence

One report, shared by the reader and the responsible team.

  1. Capture in Horizon

    Identify the issue in the publication and add the evidence the receiving team needs.

  2. Review in Axis

    The routed ticket carries the content context. The responsible team triages the issue and records its response.

  3. Reply and resolve

    The reporter receives replies in Horizon. The ticket retains the discussion and recorded resolution.

Before configuration

Give incoming reports an owner.

  • Nominate the teams that receive reports and define their routing rules.
  • Assign owners responsible for triage, replies and resolution.
  • Plan attachment storage and retention for ticket history.
Optional, separately licensed extension module

Enable feedback within your licensed Horizon deliveries.

LiveConnect is licensed separately and requires at least one Horizon delivery. It uses the active NIVOMAX session and the organization and role model in Axis.

Ticket data and attachments are held on the Licensee’s infrastructure. Your teams own the response process and decide how a reported issue affects the source publication.

Questions

Frequently asked questions

Does a ticket update the technical publication?

The ticket records the issue and resolution. Publication changes follow the responsible team’s authoring, validation and publishing process.

What happens when the reader is offline?

The report is held locally and submitted when the device reconnects. The responding team receives it after that submission.

Where does the publisher answer?

The responsible team manages and answers the ticket in Axis. Replies are available to the reporter through Horizon.

Related modules

Continue exploring the workflow.

Publication use

SkyTask

Assemble task cards with pinned publication references.

Requires Horizon Web for assemblyExploreSkyTask

Review your publication feedback process.

Show us where reports come from, who receives them and how your teams resolve them. We will review the Horizon and Axis workflow with you.