Aras Webinar Notes - The Latest on Technical Documentation

Today I watched the on-demand webinar from the Aras Innovator Demo Series - The Latest on Technical Documentation.

If you are trying to keep your Technical documentation up to date with changes being made by Engineering in a PLM system, then this product can relieve a lot of your pain.

Below are my notes:

  1. Technical Documentation includes information about products, e.g. specifications, training materials, work instructions, system and user manuals.
  2. Two years ago, built from ground up a "PLM-based Technical Document Authoring Environment" - meant to exist within Aras Innovator (5:56)
  3. Defines an extensible document schema framework
  4. Publish in XML, PDF, HTML
  5. Web-based application that leverages Aras core features: access control, change management, workflow
  6. Structured content means the technical document is defined by a Data Schema, style is added independently (8:35)
  7. Managed Change - when any part or product is updated in Aras, that triggers an update in associated Technical Documentation (11:35)
  8. Application Demo - walkthrough within Aras Innovator (14:45)
  9. MakerBot technical document example (15:56)
  10. Content embedded in one document can be an independent Technical Document (17:22)
  11. When content changes in one document, it can be updated to latest version in parent documents (18:17)
  12. Document schema determines what types of content can be added
  13. Catalog element in Document contains one or more Catalog-Entry elements, which is a link to a Part or another Item in Innovator.  Inside the document, the catalog-entry references information directly from the Part (22:59)
  14. Q&A (26:21)
    1. Is there a way to add headers and footers?
      1. Yes, within the context of a PDF format.
    2. Can we build documents that work in Word and import them?
      1. Yes, if you build the schema to conform to Open Office XML format and use newer versions of Office to import from.
    3. Are we working within a DITA format?
      1. DITA is an XML-schema, so you could use that and be compliant
    4. Is the document format schema separate from the content schema?
      1. Yes, and the style schema is also separate
    5. How much flexibility does the author have when creating the schema?
      1. Schema is XML and follows those rules, Style is based on CSS and follows those rules
    6. Do you support multiple languages?
      1. Yes.  If you set up separate locales in Innovator, then you will have the option to store separate transformations in each language.  (32:29)