™
Publication use
SkyTask™
Assemble task cards with pinned publication references.
Requires Horizon Web for assemblyExploreSkyTask
Publishing workflow and revisions
Chronos™
Put each publication release through an accountable process.
Chronos coordinates validation, review and approval around the publishing pipeline. Define the stages a release must pass, schedule the work between them, and retain the history of what changed and who approved it.
For publication managers, configuration controllers and release coordinators at OEMs and publications suppliers.
Datasheet available upon requestRequest a datasheet
- Release stages
- Validation and review
- Approved publication
Keep the release process with the publication.
A publication release involves more than processing the source files. Someone must own validation, review the changes and authorize the output. Chronos gives those responsibilities a defined place in the publishing workflow.
Arkitect continues to process and publish the technical content. Chronos governs the stages around that work, including revision cycles that begin in Syntaxis when the installation uses it.
- Extends
- Arkitect publishing
- Requires
- Arkitect
- Administration
- Workflow in Arkitect; roles in Axis
- Data location
- The Licensee’s installation
Capabilities
What Chronos™ adds.
Defined stages and gates
Set the release stages and the validation, review and approval conditions required to advance. Apply the same process across the libraries or programs that use it.
Accountable transitions
Restrict stage changes to the responsible roles. Record the person and time associated with each transition so the release history shows how the decision was made.
Scheduled pipeline work
Run validation and revision tasks between stages on the agreed schedule. Record the results and present failures that must be corrected before the workflow continues.
Revision history
Keep the history of each library release, including changes between revisions and the reasons recorded for them. Review or export that history when investigating a release.
Working sequence
A governed publication cycle.
Define the release
Choose the workflow, stages, accountable roles and intended publication cycle.
Validate and review
Run the pipeline steps and resolve failures. Route the release through the required human review and approval gates.
Publish and retain
Arkitect produces the approved output. Chronos retains the transitions and revision history for later review.
Before configuration
Define the process before configuring the workflow.
- Document the stages, release gates and people accountable for each decision.
- Nominate reviewers and approvers with the corresponding roles in Axis.
- Agree schedules and retention for workflow and revision history.
Optional, separately licensed extension module
License workflow governance for your publishing installation.
Chronos is licensed separately and requires Arkitect. Syntaxis can participate where source authoring is part of the revision cycle; it is not a Chronos prerequisite.
Workflow and history data are held on the Licensee’s infrastructure. Implementation or integration services for the release process are scoped separately.
Questions
Frequently asked questions
Does Chronos replace Arkitect?
Arkitect processes and publishes the technical content. Chronos coordinates the workflow, gates and revision history around that pipeline.
Are releases approved automatically?
Pipeline tasks can run automatically, while stage transitions and approval authority follow the roles and gates defined for the workflow.
Do readers need to stay online for Chronos?
Chronos operates within the publishing installation. Its workflow is separate from whether a reader’s Horizon device is currently online.
Related modules
Continue exploring the workflow.
Reporting
NIVOMAX Insights™
Analyze publication use, licensing and application activity.
Administration in AxisExploreNIVOMAX Insights
Walk through your publication release process.
Bring the stages, validation requirements and approval responsibilities you use today. We will review how Chronos can organize them.