Why NIVOMAX

Built around aviation technical publication programs.

Your technical publication program has to connect content production, licensing, access and use across different operating environments. NIVOMAX brings those activities into one platform, with capabilities selected for the work your organization needs to do.

Request a demo Explore the platform

An aviation technician uses a tablet beside an aircraft on the ramp. — Plan publication delivery for the places your teams work.

Assess the whole publication program.

An OEM managing source content, an operator delivering publications to crews and an MRO working across customer libraries have different requirements. Assess the platform against the content, access rules and delivery conditions your organization actually needs.

Source content

Author and govern structured content where your program needs it.

Published revisions

Prepare libraries for delivery and manage their publication scope.

Licensed access

Administer organizations, users and publication entitlements.

Reader delivery

Match online and locally held content to the operating environment.

Five practical reasons

Keep source work and publication delivery connected.

Syntaxis adds optional authoring and source-content governance. Arkitect prepares publication content for delivery. Their roles sit within the same NIVOMAX platform, with Axis administering access and Horizon presenting the publications.

Choose the parts your program needs. Arkitect, Axis and at least one Horizon delivery are required in every installation. Syntaxis and Aerotrade are optional, and each application, delivery and extension module is licensed separately.

Explore the platform

Work with aviation standards and mixed-format content.

Publication programs often carry a mixture of structured data and existing manuals. NIVOMAX supports S1000D, ATA-100 and ATA iSpec 2200 publication workflows, alongside supported XML, SGML and PDF content.

The details matter. Review your source schemas, graphics, applicability rules and revision process during evaluation. A demonstration should show how the platform handles the content and workflow you intend to use.

Review publishing in Arkitect

Manage publication access as part of the workflow.

Axis holds the records for organizations, users, roles, data licenses and entitlements. Applications authenticate through the shared NIVOMAX identity layer. Software licensing and access to an OEM’s publications have separate scopes.

Add separately licensed capabilities when the requirement calls for them. Vigilance Sentinel manages Horizon Web sessions and shared web-license capacity. Vigilance Watcher supplies tamper-evident access and activity evidence. Vigilance Compliance provides SCIM user lifecycle and access reviews through Axis or REST API.

Review access administration in Axis

Keep control of the installation.

NIVOMAX runs as a single-tenant installation on infrastructure controlled by the Licensee. That can be on premises, in a customer-operated cloud tenancy or in a restricted environment planned around its permitted connections.

Plan infrastructure, identity, updates and recovery with the teams that will operate the installation. Professional Services cover setup, migration, data conversion and custom integration. Infrastructure operations and monitoring are separate service blocks. Training and End-User Support are scoped separately where selected.

Plan deployment

Choose delivery for the connection available.

Horizon Web provides browser access to the installation. Horizon Desktop, iOS and Android hold encrypted libraries locally for offline reading. The Horizon Network Data Server serves a local library to installed Horizon Desktop clients over the site LAN.

An offline workflow also needs a plan for revised content and entitlement renewal. Review those arrangements alongside your device and network requirements, rather than treating the delivery choice as a device list.

Explore Horizon deliveries

Bring the requirements that will shape the installation.

A useful evaluation starts with the working conditions, not a list of every available feature. These four topics help us plan the discussion and identify what the demonstration needs to cover.

Publications

Standards, source formats, library volume and revision frequency.

People and access

User organizations, roles, publication licensing and review responsibilities.

Delivery

Devices, permitted connections, offline use and content-update arrangements.

Operations

Infrastructure, identity, integration, implementation and support needs.

Discuss your project Request a licensing estimate

Experience and support

The company behind NIVOMAX.

Synaxiom has worked in aviation technical publications for more than 20 years. NIVOMAX brings that experience into the software used to author, publish, sell, control and view publication content.

Software updates and application support for designated Licensee contacts are covered during the license term. Direct support for other users in the Licensee’s organization and its customer organizations is available through optional, separately purchased End-User Support. Professional Services are scoped separately.

Visit Synaxiom

Questions

Common questions

Is NIVOMAX intended for OEMs, operators or MROs?

NIVOMAX supports aviation technical publication programs at OEMs, operators and MROs. The installation is scoped around the organization’s content, users, licensing and delivery requirements.

Do we need to license every application and module?

Arkitect, Axis and at least one Horizon delivery are required. Syntaxis and Aerotrade are optional. Applications, deliveries and modules are licensed separately, and module prerequisites depend on the selected capability.

Can we evaluate the platform before sharing our publications?

Yes. Start with your standards and workflow requirements. We can agree which demonstration content to use. A mutual non-disclosure agreement is available on request before discussing confidential material.

Will a software license include access to an OEM’s publications?

Software licensing and publication data licensing are separate. The OEM or publications supplier controls the content access it grants, and those entitlements are administered through Axis.

Discuss your technical publication program.

Tell us about your content, users, workflows, systems and operating environment. We can plan a walkthrough around those requirements and agree which demonstration content to use.

Request a demo Contact the team