The XR family consists of the XR/system, the core of all XR applications and any subsequent, sector-specific applications for, e.g. mechanical/plant engineering and aviation. XR is the logical development of the XML Component Content Management System (CCMS) TCToolbox by Ovidius, which it will replace starting the end of 2017. It is an editorial system that can be configured for any DTD or schema. The XR systems offer standardized industry applications which significantly reduce the time-to-market of your documentation. XR allows you to efficiently work on a clearly structured interface – even without any prior XML skills. No “one size fits all”, but optimized solutions tailored to selected industries and quickly deployed with minimum configuration effort. For the development of XR, we worked from the ground up to design an efficient, easy-to-use and scalable system. In this connection, the important key words are: Context-related working, high usability and a modern, lean architecture, facilitating straightforward and cost-effective updates.
XR/airline is a solution for the aviation industry. The central prerequisites for this segment include compliance with the highest regulatory requirements and safety standards – exactly what XR/airline delivers. The focus is on the creation of airplane-specific operations manuals, including the recording of variant information. An additional elementary function is the calculation and display of modification reasons. Regulatory authorities can reliably trace modifications, which accelerates the review and approval of documents.
The information structure is based on a DTD, optimized for the requirements of airline companies. The integration of manufacturer documentation as PDF or optionally as XML facilitates detailed reuse and continuous revision.
XR/airline supports the approval process by automatically generating transmittal letters and change descriptions for submission to approval bodies. The additionally integrated Ovidius Compliance Assistant supports you in recording and reviewing EASA regulatory content.
XR/airline is available as a basic version you can use immediately after just a few process-specific configuration steps.
Server and client – modular, fast and flexible
The XR server consists of a robust, lean core and plugins, providing most of the CCMS functions. It uses structured interfaces to communicate with the plugins, the XR client and external applications. It is also scalable and optimized for high performance. Thanks to its modular structure, functions can be added in a controlled manner without affecting other components.
This poses a number of advantages:
Editing and preview directly in the client – with or without tags. With the internal XR editor, you can create and edit contents directly in the XR client – in WYSIWYG mode, with Box View or via XML View.
Checking in and out occurs in the background.
Working with ease
A modern editorial system with an intuitively operated user interface, permitting context-related work. No more and no fewer than the very functions that are possible in the current context and that have been authorized for a given user are made available .
Documents consist of reusable modules – and modules are usually self-contained content objects. In this case, XR follows modern, topically aligned approaches, such as DITA.
Modules can contain references to graphics, media objects and any random small fragments. Fragments can consist of tables, warnings, etc. You can also reuse fragments, graphics and other media objects.
Editorial support and automation
XR helps to finish your tasks quickly and systematically. Complex tasks can be automated, while supporting functions and systems simplify your work:
XR offers two efficient tools to simply and efficiently manage product variability in your documentation:
A comparative function embedded in XR lets you display differences between document or module versions in various ways:
A list of all classified objects used in XR can be provided and distinguished:
External resources on demand
You can manage variable information such as spare parts information, on-screen texts, variants and data from an SAP system as “resources” and incorporate such at specified points in time, e.g., for publication.
You can trigger validation processes automatically or manually. Defined validation results are displayed via reports.
Connection to third-party systems
XR can be connected to additional systems via connectors. Standard connectors are available for:
XR-Server is the core component containing all of the basic functions. System integration is supported by efficient and structured interfaces.
The range of functions provided by the XR server can be expanded via plugins. Plugins are used to realize a variety of generic or customized functions.
Integration of third-party systems
Standardized or customized interfaces facilitate the integration of third-party systems such as SAP or Translation Memory systems.
XR-Client is the user interface. You can roll it out as a rich client, but also use it via remote app or a terminal server connection. The XR-Client is also expandable via plugins.
With the efficient internal XR editor, you can create and edit contents directly in the XR-Client – in WYSIWYG mode, with Box View or via XML View.
Publication server and publication framework
Publications are created on a publication server. This puts less strain on the XR client and the client processor.
The new publication framework permits the efficient set-up of new publication routes. You can apply existing upstream processes, which ensure that all information is processed uniformly.
Technologies and standards
The current versions of the Microsoft SQL server are used as a database. The application makes intensive use of the XML functionalities provided by the SQL server from Microsoft.
Modules are only stored in the XML format. SGML support continues to be an available option.
Schema languages: DTDs, XML Schema, Schematron and Relax NG
Query languages: SQL and XQuery Transformation languages: XSLT and MetaMorphosis