cortona3d.com

Cortona3D integrates with PLM systems in two main ways: a dedicated integration between its RapidAuthor software and Siemens Teamcenter, and a broader API layer that connects Cortona3D tools to PLM, CMS, and CSDB environments. Both approaches are built around the same goal — authoring and publishing technical documentation directly from product design data, so that documentation stays synchronized when engineering or PLM data changes.

The Teamcenter integration

Cortona3D's RapidAuthor integrates with the Teamcenter portfolio from Siemens DISW. According to Cortona3D, this integration is intended to "streamline your documentation authoring and publishing process" through PLM-driven automation.

In practice, this means documentation is authored against the same product structure and data held in Teamcenter, rather than being recreated separately. Cortona3D also runs webinars on specific releases — for example, "What is new in RapidAuthor 2606 for Teamcenter" — which suggests the Teamcenter integration is actively maintained and versioned alongside RapidAuthor releases.

API-based integration with PLM, CMS, and CSDB

For environments beyond Teamcenter, Cortona3D offers APIs that let you embed its tools into your own software and web environment. The stated use cases are:

• Integration with PLM systems
• Integration with CMS (content management systems)
• Integration with CSDB (common source databases, typically used in S1000D workflows)
• Displaying content in web or mobile applications

This is the path to consider if your documentation pipeline is not built on Teamcenter, or if you need published content to surface inside another application rather than in a standalone authoring tool.

What the integration actually changes

The value of PLM integration here is not just connectivity — it is data reuse and automatic synchronization. Cortona3D describes the following behaviors:

The synchronization point matters most for teams whose products change frequently: if the PLM record changes, the documentation is meant to follow, instead of drifting out of date until someone manually reconciles it.

Standards and formats involved

Cortona3D ships pre-configured templates compliant with S1000D, ATA 2200, and DITA. You can also attach an existing SGML/XML document that complies with one of these standards and generate a corresponding procedure structure from it. If your PLM integration is part of a regulated or standards-bound documentation process, this is the piece that determines whether the output is usable in your existing CSDB or publication pipeline.

How to decide which integration path fits

• Choose the Teamcenter integration if your engineering data lives in Siemens Teamcenter and you want documentation authoring driven directly by that PLM data.
• Choose the API route if you need Cortona3D content inside a different PLM, a CMS, a CSDB, or a custom web/mobile application.
• Check the standards requirement first if you publish under S1000D, ATA, or DITA — template compliance and the ability to attach existing SGML/XML content may be the deciding factor regardless of which integration you use.

Cortona3D offers a live demo and a free trial, and lists a Subscribe option, so the practical next step for evaluating fit is to request a demo against your own data rather than judging from feature descriptions alone.

Cortona3D is a technical documentation platform that turns product design data into 2D and 3D publications. Its core product, RapidAuthor, is used to create parts catalogs, technical manuals, work instructions, and training materials for manufacturing and after-sales support. If your team already works from CAD or PLM data and needs documentation that stays synchronized with it, that is the problem Cortona3D is built to solve.

What Cortona3D actually produces

The platform is organized around producing and maintaining technical publications rather than general-purpose 3D content. According to the site, the main outputs are:

• Parts catalogs — illustrated, structured parts information for ordering and service.
• Technical manuals — procedures and reference content for equipment.
• Work instructions — step-by-step manufacturing or assembly guidance.
• Training materials — animated, interactive guides for operators or service staff.

A single source can be published in different formats: interactive HTML5 documentation with animated 3D illustrations, traditional PDF publications with 2D illustrations, or content for augmented reality.

How it works: authoring from engineering data

The central mechanism is authoring directly from 3D models and engineering actions instead of drawing or writing everything manually.

The practical effect: instead of redrawing an illustration after a design change, the illustration and the surrounding procedure are regenerated from the updated model. Cortona3D claims this results in authoring three times faster with up to 60% cost savings — a vendor figure, so treat it as a directional claim rather than a guaranteed outcome.

Integration and delivery

RapidAuthor offers APIs so the tools can be embedded in a software or web environment, and it integrates with PLM, CMS, and CSDB systems to display content in web or mobile applications. There is also a dedicated integration with Teamcenter (Siemens DISW), which is aimed at PLM-driven automation of the authoring and publishing process. If your documentation pipeline already runs through Teamcenter, that integration is the most relevant part of the offering to evaluate first.

Who this fits

Cortona3D is a reasonable fit when:

• Your documentation must track frequent engineering changes, and manual redrawing is a bottleneck.
• You need to publish the same content as interactive 3D, PDF, and AR output.
• You are required to comply with S1000D, ATA 2200, or DITA.
• You want documentation generated from existing CAD/PLM data rather than authored from scratch.

It is a weaker fit if you only need static, one-off documents with no design-data source, or if your content has no structured standard to conform to.

Seeing it before deciding

The site offers a live demo request and lists webinars — for example, a session on what is new in RapidAuthor 2606 for Teamcenter. A subscription page exists, but the site does not state pricing, so cost and licensing terms need to be confirmed directly. For a concrete evaluation, bring one real procedure and its source CAD/PLM data to a demo and check whether the generated 2D illustrations, tables, and text are usable with minimal cleanup — that is the fastest way to judge whether the automation claim holds for your content.

Cortona3D is built around a single authoring source — typically 3D models and engineering data — that you publish into several documentation types and formats. According to the site, RapidAuthor is used to create parts catalogs, technical manuals, work instructions, and training materials, and the same source can be published as interactive HTML5 documentation with animated 3D illustrations, traditional PDF publications with 2D illustrations, or content for Augmented Reality. If your team already works from CAD or PLM data and needs more than one output format from it, that combination is the core fit.

Documentation types

The four categories named on the site map to different audiences and lifecycle stages:

These are not separate tools — they are outputs of the same authoring environment, which is what makes reuse practical when a product changes.

Output formats from one source

The site describes an "author once — publish in different formats" model. From a single source you can produce:

• Interactive HTML5 documentation with animated 3D illustrations
• Traditional PDF publications with 2D illustrations
• Augmented Reality content

This matters if you serve both a desktop/web audience and a printed or offline audience, or if you want AR overlays for on-site work without maintaining a second authoring pipeline.

What the content is generated from

Two mechanisms drive the content itself:

• Automatic generation from 3D models and actions. The site states that 2D illustrations, DPL tables, and relevant text are generated automatically based on 3D models and actions in a single application, with claims of three times faster authoring and up to 60% cost savings.
• Import and merge of native CAD and PLM data. Technical documentation stays synchronized with product design; when engineering or PLM data changes, 3D geometry, metadata, generated 2D graphics, and procedures update automatically.

There is also a Teamcenter integration (Siemens DISW portfolio) for PLM-driven automation, and APIs for embedding content in your own web or mobile applications or connecting to PLM, CMS, and CSDB systems.

Standards and structured content

If your documentation must follow a specification, the site lists pre-configured templates compliant with S1000D, ATA 2200, and DITA. You can attach an existing SGML/XML document that complies with S1000D, DITA, or ATA standards and generate a corresponding structure of the procedure — useful when you are migrating existing structured content rather than starting from scratch.

When this is a good fit — and when it isn't

Consider Cortona3D if:

• Your source material is CAD/PLM data and you want documentation derived from it rather than redrawn manually.
• You need the same procedure delivered as interactive 3D, PDF, and/or AR.
• You must comply with S1000D, ATA 2200, or DITA.
• You want to integrate publishing into an existing PLM, CMS, or CSDB environment via API.

Look elsewhere if your documentation has no 3D or engineering-data component, or if you only ever produce a single static format — the value here comes from reuse across formats and synchronization with design data.

Seeing it before deciding

The site offers a live demo request and lists webinars (for example, "What is new in RapidAuthor 2606 for Teamcenter"). A free trial and a Subscribe page are referenced in the site's pricing signals, but the available material does not state trial length, subscription terms, or cost — confirm those directly with Cortona3D before planning a rollout.

Cortona3D supports three technical documentation standards: S1000D, ATA 2200, and DITA. According to the company, RapidAuthor ships with pre-configured templates compliant with these standards, and you can attach an existing SGML/XML document that complies with S1000D, DITA, or ATA and generate a corresponding structure of the procedure. This matters most if you produce documentation for aerospace, defense, or other industries where these standards are contractually required.

The three standards at a glance

The common thread is that compliance is handled through templates rather than manual formatting, and existing standard-compliant XML/SGML content can be brought in rather than rebuilt.

How the compliance mechanism works in practice

The workflow described on the site has two entry points:

1. Start from a template. You select a pre-configured template for S1000D, ATA 2200, or DITA, and author within that structure. This is the path for new documentation programs.
2. Attach existing compliant content. If you already have an SGML/XML document that conforms to one of these standards, you attach it and Cortona3D generates a corresponding structure of the procedure. This is the path for migrating or reusing legacy content.

In both cases, the output is produced from a single source and can be published in different formats — interactive HTML5 with animated 3D illustrations, traditional PDF with 2D illustrations, or content for augmented reality.

Why the "attach and generate structure" step is the one to test

Generating a procedure structure from an attached SGML/XML file is the highest-risk part of any standards-compliance claim, because the result depends on how cleanly your source content maps to the target schema. Before committing, take one representative existing document and run it through this path. Check that the generated structure matches what your reviewers expect, not just that the import succeeds.

Which standard applies to your situation

• S1000D — choose this if you are in aerospace, defense, or another sector where the customer or contract specifies S1000D for equipment technical publications.
• ATA 2200 — choose this if you produce air transport maintenance documentation and your program follows ATA conventions.
• DITA — choose this if your organization already uses topic-based structured authoring and wants to keep that model while adding 3D and 2D illustrations generated from engineering data.

If none of these are required by your contracts, the standards support is not the deciding factor — the more relevant question becomes whether authoring directly from CAD and PLM data fits your process.

What to verify before relying on compliance

The site states template compliance and the ability to attach compliant SGML/XML, but it does not publish the specific schema versions or validation rules behind those claims. Before you treat compliance as settled:

• Ask which S1000D issue number, ATA 2200 revision, and DITA version the templates target.
• Request a validation run against your own schema or a customer-supplied sample.
• Confirm how the attached-document structure generation handles your existing content, since that step is where mismatches surface.

Cortona3D also offers a live demo and a free trial, which are the practical ways to test these points against your own files rather than against a generic example.

Cortona3D's stated benefits center on producing technical documentation directly from product design data rather than writing and illustrating it by hand. According to the company, this approach yields three times faster authoring with up to 60% cost savings, automatic generation of 2D illustrations, DPL tables, and related text from 3D models and actions, and synchronized updates when engineering or PLM data changes. These claims apply to teams already working with CAD or PLM data who need parts catalogs, technical manuals, work instructions, or training materials.

The core claim: faster authoring at lower cost

Cortona3D states that its RapidAuthor tool enables "three times faster authoring with up to 60% cost savings." The mechanism behind this claim is automation: instead of manually drawing 2D illustrations, building parts tables, and writing procedural text, the software generates these from 3D models and the actions defined on them, all within a single application.

The practical implication is that the author's role shifts from creating illustrations and tables from scratch to reviewing and refining automatically generated output. Whether the 3x/60% figures hold for a specific team depends on how much of the current workflow is manual illustration and table work — a team already highly automated would see less relative gain.

What gets generated automatically

Per the site, RapidAuthor automatically generates:

• 2D illustrations derived from 3D models
• DPL tables (parts lists) based on model structure
• Relevant text tied to 3D models and actions

Because text, 3D, and 2D visual content are all authored from the same engineering information, the output stays consistent across formats. This matters most where a single procedure must appear as an interactive HTML5 guide, a PDF with 2D illustrations, and AR content — the "author once, publish in different formats" model.

Reuse of existing CAD and PLM data

Cortona3D claims effective reuse of existing CAD and PLM data through import and merge of native CAD and PLM data. The stated result is that technical documentation stays synchronized with product design: when engineering or PLM data changes, 3D geometry, metadata, generated 2D graphics, and procedures update automatically.

For a team whose products change frequently, this is the benefit with the clearest operational value — it replaces a manual re-illustration and re-write cycle with an update-and-review cycle. The condition is that the source CAD/PLM data must be available and structured well enough to drive generation.

Shorter time-to-market and standards compliance

Cortona3D links these capabilities to improved time-to-market schedules, on the reasoning that content authored directly from engineering information removes handoff and rework between engineering and documentation. It also claims easy compliance with industry standards through pre-configured templates for S1000D, ATA 2200, and DITA, including the ability to attach an existing SGML/XML document compliant with those standards and generate a corresponding procedure structure.

What to verify before relying on these claims

The benefits above are vendor-stated. Before committing, check:

• Your data readiness — automatic generation depends on usable 3D models and PLM metadata; gaps there reduce or eliminate the time savings.
• Your current baseline — the 3x/60% figures are relative; measure your own manual illustration and table effort first.
• Format coverage you actually need — confirm the HTML5, PDF, and AR outputs match your delivery requirements.
• Standards you must meet — if you need S1000D, ATA 2200, or DITA, test the pre-configured templates against your real documents.

Cortona3D offers a live demo and lists a free trial and subscription option, so the practical next step is to run a representative procedure through the tool and compare the result against your current process.