Add Value to your Information Every Organization has Information How you manage that information is the key to success Inf...
Why use single-sourcing? Too often, documentation look like this . . .
Content is not connected
This creates isolated silos of information …
Information Silos No Reuse or Communication <ul><li>Poor exchange of information </li></ul><ul><li>Duplication of effort <...
Single-source approach Single-sourcing solves the problem . .
A single-source repository
How it works
How it works
How it works
How it works
How it works
How it works
How is AuthorIT Different? <ul><li>Manage Content  not  Files </li></ul><ul><li>most document and content management syste...
Traditional document authoring
False Single Source Authoring
Content is locked inside documents
Content is locked inside documents <ul><li>Simply changing where these documents are stored will  not  solve your problems...
Allowing reuse of content
Publish to Print, Help, and Web
Single-source Content Management <ul><li>True  single-sourcing enables you to </li></ul><ul><li>write content once </li></...
Store content in a database
The Benefits <ul><li>What you get out of it </li></ul><ul><li>reduced work </li></ul><ul><li>reduced time expenditure </li...
Upcoming SlideShare
Loading in …5
×

Triview Single Sourcing Presentation

636 views

Published on

Basic of Single sourcing and benefits of Content Management in Documentation Processes

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
636
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • As an introduction to the thinking behind AuthorIT, here’s a representation of a typical organisation . . .what we call a disconnected enterprise, with various departments all with documentation requirements - and creating documentation content as they need it . . . often using different tools seldom with any means of collaborating, or of having knowledge of what’s produced elsewhere
  • As an introduction to the thinking behind AuthorIT, here’s a representation of a typical organisation . . .what we call a disconnected enterprise, with various departments all with documentation requirements - and creating documentation content as they need it . . . often using different tools seldom with any means of collaborating, or of having knowledge of what’s produced elsewhere
  • Unfortunately, this gives rise to development of what are often referred to as ‘information silos’ - totally isolated bodies of information in different parts of the organisation this situation can lead to a number of serious problems: high degree of duplication - people in each department reproducing what has already been done elsewhere - wasting time, resources and money with no central control - lack of common standards - document structure, style, presentation, level of detail can vary widely perhaps worst - inconsistencies in what should be identical information - with potentially serious legal, commercial or other implications very common situation - partly due to working practice, but very largely due to the lack of facilities in conventional documentation tools.
  • As an introduction to the thinking behind AuthorIT, here’s a representation of a typical organisation . . .what we call a disconnected enterprise, with various departments all with documentation requirements - and creating documentation content as they need it . . . often using different tools seldom with any means of collaborating, or of having knowledge of what’s produced elsewhere
  • Can see from this that AuthorIT takes the concept of single-source documentation much further than just publishing documents to different outputs See slide . . . So much for creating, using and re-using content, what about the enterprise-wide management . . .
  • may have noticed that I emphasised ‘true’ single-sourcing just now - anybody come across this term before? relatively new concept - for documentation anyway - arising from the growing need to deliver documents via multiple channels - via paper documents on-line help internet and intranet web pages Previously, use different tools to create separate versions of the documents for each - terribly wasteful and a maintenance nightmare!
  • Many documentation tools now claim to be ‘single-source’ systems, just because they address this problem: they create documents in one format can then publish those documents to a number of different outputs Very useful, big advance on the separate tools approach, but essentially a conversion process for whole documents - not much scope for re-using or sharing individual pieces of information between documents
  • Stems largely from the fact that most tools - like Word, FrameMaker - are file-based and work with long documents Long documents are inherently inflexible They are essentially great big files that lump all content together and bind it up with document structure and format if you want to re-use any part for another purpose, usually means cutting and pasting, and quite probably removal and replacement of inbuilt formatting Then you end up with multiple copies of info that have to be maintained separately
  • In AuthorIT, you create information in small, re-usable chunks small content ‘components’ - can be used and re-used - many documents at same time without any copying each object:- single source of that content exists only in one place simply referenced whenever and wherever needed goes not only for items of text, but also graphics, index entries, hyperlinks, everything! every item you create automatically becomes a single-source, re-usable item - available through AuthorIT’s library to all users - again, subject to security permissions.
  • and to ensure total re-usability, the stored content is effectively format neutral, by which we mean that the information in the database is separated from its context, structure and format. only when you use component in a document - represented by the book icon here - and generate an output:- become part of a structure and acquire format. means:- any component can be used in different places at the same, and also that any collection can be assembled into a document and published to multiple outputs without having to think about the format hugely simplifies re-use of content is also a major reason why it is so easy for people to use AuthorIT - they are just not concerned with formatting - concentrate 100% on content. ~~~~~~~~~~~~~~~~~~~~~~~ Put another way, it shields users from the whole process of formatting, which in conventional documentation tools such as Word: accounts for a great deal of a user’s working time makes the programs difficult to learn and, gives rise to inconsistencies from one user, and one document, to another In AuthorIT, users concentrate 100% on writing content. Formatting is controlled entirely by styles and templates which can be defined and locked down. Ad-hoc formatting is simply not possible, so your standards can be set and rigidly enforced. Separating content from format allows content to
  • Can see from this that AuthorIT takes the concept of single-source documentation much further than just publishing documents to different outputs See slide . . . So much for creating, using and re-using content, what about the enterprise-wide management . . .
  • truth is, AuthorIT’s ‘library’ is, in fact, a full-blown relational database AuthorIT is unique in storing content this way, and is at the heart of it’s content management capability Quite simply, there are things you can do when information is stored as components in a database environment that you simply cannot easily do in a file-based system. You can :- quickly find content make widely available for multiple re-use. and, can control exactly who does what with each piece of content ensure the integrity of your documents obtain information about the relationship between any given item of content and any other item can also do things controlling release states and maintaining a full edit history - remember. at the level of individual items of content, not just whole doc’s In short:- the shared database is the key to AuthorIT’s ability to manage content rather than just create documents.
  • The ability to share and re-use information, as well as manage to its use and the standards applied to it reduced work - clearly, you are not duplicating effort reduced time expenditure - assemble new documents quickly using existing content, where applicable. easier maintenance - change content only in one place, no matter how many times it’s been used. All relevant documents will update simultaneously. higher quality and consistency - from centrally defined and enforced standards follows from these that you can get more value from every bit of content you produce, and make major savings in costs. Any questions?
  • Triview Single Sourcing Presentation

    1. 1. Add Value to your Information Every Organization has Information How you manage that information is the key to success Information is an Asset Treat it like one…
    2. 2. Why use single-sourcing? Too often, documentation look like this . . .
    3. 3. Content is not connected
    4. 4. This creates isolated silos of information …
    5. 5. Information Silos No Reuse or Communication <ul><li>Poor exchange of information </li></ul><ul><li>Duplication of effort </li></ul><ul><li>No common standards </li></ul><ul><li>Factual inconsistencies </li></ul>
    6. 6. Single-source approach Single-sourcing solves the problem . .
    7. 7. A single-source repository
    8. 8. How it works
    9. 9. How it works
    10. 10. How it works
    11. 11. How it works
    12. 12. How it works
    13. 13. How it works
    14. 14. How is AuthorIT Different? <ul><li>Manage Content not Files </li></ul><ul><li>most document and content management systems store files created by other applications </li></ul><ul><li>AuthorIT extracts, stores, and manages the information inside files as discrete, reusable components </li></ul><ul><li>components are used to construct many different documents </li></ul><ul><li>which can then be published and delivered to print, help, and web formats </li></ul>
    15. 15. Traditional document authoring
    16. 16. False Single Source Authoring
    17. 17. Content is locked inside documents
    18. 18. Content is locked inside documents <ul><li>Simply changing where these documents are stored will not solve your problems </li></ul>
    19. 19. Allowing reuse of content
    20. 20. Publish to Print, Help, and Web
    21. 21. Single-source Content Management <ul><li>True single-sourcing enables you to </li></ul><ul><li>write content once </li></ul><ul><li>re-use content at the component level </li></ul><ul><li>use it in many different contexts without duplication </li></ul><ul><li>maintain it in a single place </li></ul><ul><li>localize content to any language </li></ul><ul><li>and publish to… </li></ul><ul><li>Print - Word, RTF, PDF </li></ul><ul><li>Help - Windows, Unix, Linux, Mac, </li></ul><ul><li>Web - Internet, Intranet, Extranet, WAP, HTML, XML </li></ul><ul><li>all these output formats without conversion or rework </li></ul>
    22. 22. Store content in a database
    23. 23. The Benefits <ul><li>What you get out of it </li></ul><ul><li>reduced work </li></ul><ul><li>reduced time expenditure </li></ul><ul><li>easier maintenance </li></ul><ul><li>higher quality and consistency </li></ul><ul><li>control over standards and branding </li></ul><ul><li>more value from your work </li></ul><ul><li>reduced overall costs </li></ul>

    ×