69
The CMIS solution for Tenix's M113 Program William P. Hall (PhD) Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land

The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

The CMIS solution for Tenixs M113 Program

William P Hall (PhD)Documentation Systems Analyst Tenix Defence

Paul Brouwers (CMII Cert)Design Resources Manager TD Land

CMIS

MRP

Production

Procurement

RAM

Relex

Opus

LSA

TeraText SGML

TECHNICAL PUBLICATIONS

CAD

ACAD

CATIA

LORA

CMIS

MRP

Production

Procurement

RAM

Relex

Opus

LSALSA

TeraText SGML

TECHNICAL PUBLICATIONS

CAD

ACAD

CATIA

LORALORA

MRP = Mfg Resource PlanningCAD = Computer Aided DesignLORA = Level of Repair AnalysisRAM = Reliability amp MaintainabilityLSA = Logistic Support Analysis

Our project knowledge revolves around CMIS

Scope

bull Some introductory comments about Tenixndash History amp experience with large complex projects

bull Critical issues relating to management of project data information and knowledge

bull A new project allowed us to embody our understanding with the latest product lifecycle management technology

bull Focus on how we have extended the core technology to encompass content management

Company started as AMECON with building warships (Marine Division)

bull $A 7 BN ANZAC project to build 10 frigates for Australian (8) and New Zealand (2) Navies

bull Signed Nov 1989 - 8 ships already deliveredbull Project Protector - preferred tenderer for new

ships for NZ

Tenix Group Tenix Defence

bull One of Australiarsquos largest private companies with defence and commercial clients in Australia New Zealand Fiji Philippines USA and Europe

bull Defence is largest of 6 business units it includesndash Marine (defence amp commercial shipbuilding

logistic support etc)ndash Land (rebuilding as new 350 M113s other heavy

vehicle work logistic amp base support etc)ndash Aerospace (systems integration logistic support)ndash Electronic Systems (systems design integration

related software)

(httpwwwtenixcom)

Some Land Division jobsM113A1 Upgradeldquo

(Another country in the region recently procured around 100 new LAVs for approx $600 M)

bull The Australian Army M113A1s were originally brought into service during the early 1960rsquos

bull The purpose of the M113 Upgrade Contract is to improve protection mobility communications and firepower

bull Tenix is turning 350 well used hulls into new state-of-the-art vehicles with totally new technical data packs for a contract value of $A 391 M

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 2: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

CMIS

MRP

Production

Procurement

RAM

Relex

Opus

LSA

TeraText SGML

TECHNICAL PUBLICATIONS

CAD

ACAD

CATIA

LORA

CMIS

MRP

Production

Procurement

RAM

Relex

Opus

LSALSA

TeraText SGML

TECHNICAL PUBLICATIONS

CAD

ACAD

CATIA

LORALORA

MRP = Mfg Resource PlanningCAD = Computer Aided DesignLORA = Level of Repair AnalysisRAM = Reliability amp MaintainabilityLSA = Logistic Support Analysis

Our project knowledge revolves around CMIS

Scope

bull Some introductory comments about Tenixndash History amp experience with large complex projects

bull Critical issues relating to management of project data information and knowledge

bull A new project allowed us to embody our understanding with the latest product lifecycle management technology

bull Focus on how we have extended the core technology to encompass content management

Company started as AMECON with building warships (Marine Division)

bull $A 7 BN ANZAC project to build 10 frigates for Australian (8) and New Zealand (2) Navies

bull Signed Nov 1989 - 8 ships already deliveredbull Project Protector - preferred tenderer for new

ships for NZ

Tenix Group Tenix Defence

bull One of Australiarsquos largest private companies with defence and commercial clients in Australia New Zealand Fiji Philippines USA and Europe

bull Defence is largest of 6 business units it includesndash Marine (defence amp commercial shipbuilding

logistic support etc)ndash Land (rebuilding as new 350 M113s other heavy

vehicle work logistic amp base support etc)ndash Aerospace (systems integration logistic support)ndash Electronic Systems (systems design integration

related software)

(httpwwwtenixcom)

Some Land Division jobsM113A1 Upgradeldquo

(Another country in the region recently procured around 100 new LAVs for approx $600 M)

bull The Australian Army M113A1s were originally brought into service during the early 1960rsquos

bull The purpose of the M113 Upgrade Contract is to improve protection mobility communications and firepower

bull Tenix is turning 350 well used hulls into new state-of-the-art vehicles with totally new technical data packs for a contract value of $A 391 M

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 3: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Scope

bull Some introductory comments about Tenixndash History amp experience with large complex projects

bull Critical issues relating to management of project data information and knowledge

bull A new project allowed us to embody our understanding with the latest product lifecycle management technology

bull Focus on how we have extended the core technology to encompass content management

Company started as AMECON with building warships (Marine Division)

bull $A 7 BN ANZAC project to build 10 frigates for Australian (8) and New Zealand (2) Navies

bull Signed Nov 1989 - 8 ships already deliveredbull Project Protector - preferred tenderer for new

ships for NZ

Tenix Group Tenix Defence

bull One of Australiarsquos largest private companies with defence and commercial clients in Australia New Zealand Fiji Philippines USA and Europe

bull Defence is largest of 6 business units it includesndash Marine (defence amp commercial shipbuilding

logistic support etc)ndash Land (rebuilding as new 350 M113s other heavy

vehicle work logistic amp base support etc)ndash Aerospace (systems integration logistic support)ndash Electronic Systems (systems design integration

related software)

(httpwwwtenixcom)

Some Land Division jobsM113A1 Upgradeldquo

(Another country in the region recently procured around 100 new LAVs for approx $600 M)

bull The Australian Army M113A1s were originally brought into service during the early 1960rsquos

bull The purpose of the M113 Upgrade Contract is to improve protection mobility communications and firepower

bull Tenix is turning 350 well used hulls into new state-of-the-art vehicles with totally new technical data packs for a contract value of $A 391 M

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 4: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Company started as AMECON with building warships (Marine Division)

bull $A 7 BN ANZAC project to build 10 frigates for Australian (8) and New Zealand (2) Navies

bull Signed Nov 1989 - 8 ships already deliveredbull Project Protector - preferred tenderer for new

ships for NZ

Tenix Group Tenix Defence

bull One of Australiarsquos largest private companies with defence and commercial clients in Australia New Zealand Fiji Philippines USA and Europe

bull Defence is largest of 6 business units it includesndash Marine (defence amp commercial shipbuilding

logistic support etc)ndash Land (rebuilding as new 350 M113s other heavy

vehicle work logistic amp base support etc)ndash Aerospace (systems integration logistic support)ndash Electronic Systems (systems design integration

related software)

(httpwwwtenixcom)

Some Land Division jobsM113A1 Upgradeldquo

(Another country in the region recently procured around 100 new LAVs for approx $600 M)

bull The Australian Army M113A1s were originally brought into service during the early 1960rsquos

bull The purpose of the M113 Upgrade Contract is to improve protection mobility communications and firepower

bull Tenix is turning 350 well used hulls into new state-of-the-art vehicles with totally new technical data packs for a contract value of $A 391 M

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 5: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Tenix Group Tenix Defence

bull One of Australiarsquos largest private companies with defence and commercial clients in Australia New Zealand Fiji Philippines USA and Europe

bull Defence is largest of 6 business units it includesndash Marine (defence amp commercial shipbuilding

logistic support etc)ndash Land (rebuilding as new 350 M113s other heavy

vehicle work logistic amp base support etc)ndash Aerospace (systems integration logistic support)ndash Electronic Systems (systems design integration

related software)

(httpwwwtenixcom)

Some Land Division jobsM113A1 Upgradeldquo

(Another country in the region recently procured around 100 new LAVs for approx $600 M)

bull The Australian Army M113A1s were originally brought into service during the early 1960rsquos

bull The purpose of the M113 Upgrade Contract is to improve protection mobility communications and firepower

bull Tenix is turning 350 well used hulls into new state-of-the-art vehicles with totally new technical data packs for a contract value of $A 391 M

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 6: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Some Land Division jobsM113A1 Upgradeldquo

(Another country in the region recently procured around 100 new LAVs for approx $600 M)

bull The Australian Army M113A1s were originally brought into service during the early 1960rsquos

bull The purpose of the M113 Upgrade Contract is to improve protection mobility communications and firepower

bull Tenix is turning 350 well used hulls into new state-of-the-art vehicles with totally new technical data packs for a contract value of $A 391 M

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 7: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Requirements for safe amp effective operation of all products we build

bull Capability when when the client needs itndash Reliably does what it is supposed tondash Available for service when neededndash Maintainable - problems can be fixed when they arise ndash Supportable - critical needs available in supply chain ndash Operable within limits of human knowledge amp capacity

bull Health safety and operational knowledge issuesndash Heavycomplex engineering systems can kill

bull Life-cycle costndash Minimise acquisition costndash Minimise documentation support amp maintenance costsndash Facilitate lean maintenance philosophy

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 8: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Major quality issues in delivering tech data and knowledge

bull Clients operational knowledge delivery goalsndash Correct

bull Correct informationbull Consistent across the fleet

ndash ApplicableEffectivebull Applicable to the configuration of the individual shipvehiclebull Effective for the point in time re engineering changes etc

ndash Availablebull To who needs it when and where it is needed

ndash Useablebull Readily understandable by humansbull Readily managed amp processed in computer systems

bull Suppliers knowledge production and usage goalsndash Fast ndash High quality ndash Low costndash Eliminate rework

bull Total configuration management is the answer

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 9: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

What we are building on

bull ANZAC SHIP PROJECTndash experiencendash Lessons learned

bull ARCHITECTURE GOALS FOR A LARGE PROJECT

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 10: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

CrossbowValidates and integratesNormalises data across15 legacy systems

TeraTextContent management

AMPSNavysmaintmgmt

CSARSProvides correctivefeedback from AMPSinto supplierNavy knowledge developmentactivities

DESIGN ENGPRODUCT DATAMANAGEMENTbull Product Modelbull CAD Drawing

Mgmtbull Config Mgmtbull Eng Changebull Workflow

Process Control

bull Doco Revisionamp Release

DOCO CONTENTMANAGEMENT

DOCUMENTAUTHORING

LSARDATABASE

LOGISTICANALYSIS

TOOLS(prime)

PRODUCT CONFIGMANAGEMENTbull Product Modelbull Drawing Mgmtbull Config Mgmtbull Change Requestbull Workflow

Process Control

bull Doco Revisionamp Release

MAINTENANCEMANAGEMENTbull Schedulebull Resource Reqsbull Proceduresbull Completionbull Downtimebull Resource UsageRECORDING

REPORTINGANALYSIS

TOOLS(prime)

bullbullbull

SUPPLY SYSTEM

change request

configchange

doco change

ECO

change effected

docochangeorder

releaseddocochange

EC docochangerequest

maintenancehistory

docoserver

Analysis ampoptimisation

orders receipts

change task

doco change

shared systems

data change

amp Release

TenixRAN architecture for managing ANZAC Ship technical data and content

UPDATEMAINT DATA

PROCEDURE

UPDATECONFIG

Navy Systems

15 legacysystems

MRPSYSTEM

PlanFabricateAssemble

config changes

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 11: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

The M113 challange

7 variants

~25 builds

350 vehicles

bull Coherently manage all data and documents required to support the M113 fleet through lifendash Engineering data (well known solutions for this)ndash Technical data and publication content

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 12: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

The CMIS solution for Tenixs M113 Program

Big enough project to supportcurrent best practice

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 13: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Knowledge is our most important asset

bull Data and documentation are the most important assets to the company

bull CMIS is the custodian AND guardian of the Companyrsquos data and documentsndash Secure Vaults and Storesndash Encryptedndash Access control

bull CM II compliantndash Only recognized commercial CM doctrinendash Qualified by Institute of CM

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 14: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Background

bull Contract All CM in M113 Project according tondash TRAMM (Technical Regulation Army Maint Mgmt)ndash MIL-STD-973 (Configuration management)

bull Other standardsndash Naming follows H6 (US Fed Item Name Directory)ndash NATO Commodity Codes forms part type

bull Rule CMIS manages all tech data for all projectsndash Engineering datandash Source documentsndash Technical Publication content

bull No part released until all metadata correct

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 15: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

CMIS was conceived as an umbrella system

bull Single user interfacebull Data normalization applies to all project data and

document components from the startbull Common workflow management environmentbull Single point

ndash electronic signoffndash engineering change management and trackingndash cost and schedule control

bull The umbrella covers everything

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 16: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Overview

bull CMIS provides primary user interfacebull Two major modules

ndash PDM ndash product data manager ndash Matrix10bull Configuration managementbull Workflow processbull Object management

ndash ANZAC experience proved value of content managementbull Authoring activities delegated from Matrix10bull Configuration management of elements within documentsbull Paragraph version management amp reusebull Authoring in S1000D - deliver any required structured

unstructured format

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 17: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Configuration management

The source of all data generated starts at the concept phase of the product and grows with

the product

SOME QUOTES

Configuration management is adiscipline

notan overhead

Some mad person

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 18: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Configuration Management

bull Very distinct phases of CMndash Developmentndash Productionndash In service

bull Analysis of data types has determined two distinct typesndash Objectsndash Content

bull To manage these we require two distinct processesndash CM of objects - provided in Matrix10 PDM

environmentndash CM of content - delegated to TeraText

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 19: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Configuration Management

bull Baseline management for each engineering phase

bull Principlesndash Items (like Systems) have a lifecycle within the

engineering phase

ndash Items are ldquopromotedrdquo to the next phase through approval only

ndash Items are NEVER deleted ndash they have ldquohistoryrdquo

Preliminary Review Release Obsolete

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 20: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Focus onDocument and content management

It is configuration management of ldquoblocks of textrdquo

It is configuration management to the lowest level inside a document

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 21: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

What is a document

bull The entire history of all versionsbull Each set of variantsbull Each separate versionbull Each rendition ndash SGML HTML PDFbull Each component

ndash volume chapter division warning hellipbull TeraText uses the Document Management

Alliance model which concurrently supports all of these concepts and provides a framework for managing them

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 22: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

What is TeraText

bull Embodies world wide state-of-the-art in information systems research in a commercial productndash Fully web enabled text database system (not relational)ndash Data compression for CPU efficiency and speed

bull High performance compressedinverted file indexes bull typical index ~ size of text

ndash Real-time simultaneous indexingsearchretrievalndash Very sophisticated search engine works against indexndash Standards based

bull XMLSGMLRTFPDF etcbull Z3950 MARC etc

ndash Distributed architecturendash Scalability to multi-terabyte data 10000s usersndash httpwwwteratext com

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 23: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

TeraText

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 24: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

TeraText

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 25: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Users Manual

This is section 1 of the document

This is the

Work File System

ChapterSection

Document

PDF

Fragment

Fragment

Graphic

Storage and sembly RulesDisas

WEB Protocol

Save

Edit

Content Management in the M113 Upgrade

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 26: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

SGML-Content managementStoring XML directly

ParserProcessing engineindexing querying

versioning doc management

Content Attribute Structure

Documentdata operations

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

This is some arbitra

This is some arbitrary text which you should not be able to read

This is some arbitra

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 27: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

HTTPHTML

Z3950

TeraText Web interface overhead

TeraTextApplication server

ApplicationWorkflow

XML engineDocument Manager

TeraText DBSXML engine

Content queryObject Management

Repository

Ace

Ace

XML Engine

XML Engine

User Interface Module

WorkflowEnactmentService

DocumentVersion

ManagerMetadataSupport

XMLSGMLParser

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 28: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

PDM(Matrix10)

Tech Documents(TeraText)Document

Authoring(FM+)

EC process

Managing document technical data

bull Authoring process for controlled changes to authored content

bull Achieves ndash Consistency (via

standards base DTD and EDD)

ndash Reuse

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 29: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Technical manuals and data modules are managed with CMIS lifecycle process in

same way as any other configuration items

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 30: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

We are addressing the content management challenge byhellip

bull Adopting a long term view of the content

bull Ensuring the document model supports authoring at the document component and fragment levels

bull Truly sharing (reusing) common texts vs rekeying common texts

bull Direct sourcing of PDM data into parts lists tables

bull Supporting auditable review processes and version control

bull Using tools and content model to assess impact of change

bull Building documentation set using industry standards and tools

bull Using COTS authoring tools bull Applying industry standards for long

life content

Users Manual

Maintenance Manual

Reuse Texts

Publishing and Review Processes

COTS authoring tools

Vehicle Variants

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 31: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

What real world problems are solved

bull The in-service life for an APC is many decadesndash Most documents contain configuration sensitive contentndash File system does not track the changes through timendash Lifetime of a word processor format is about 5 yearsndash DMS does not provide point-in-time supportndash TeraText Content Management System manages versions

and provides point-in-time search across versionsndash SGML(~XML) is essentially unchanged since 1986

bull Many versions of each manual changes to individual vehicles etc leads to many hundreds of documentsndash DMS typically limited to about 100000 piecesndash TeraText Content Management System scales to many

hundreds of thousands of documents and millions of configuration sensitive components

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 32: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

What real world problems are solved

bull About 80 of content is common to all manualsndash DMS only manages whole documents and does not know

what is common to other documentsndash TeraText Content Management system manages the

components that make up the documentndash Reuse dont rewrite

bull Only small component may change in a documentndash DMS or file system requires whole document to be stored

againndash TeraText Content Management System stores

common components once and tracks versions of components as well as whole documents

ndash Know where used

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 33: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

What real world problems are solved

bull May need to strip out classified material for unclassified usersndash static documents donrsquot allow for changed detailsndash TeraText can strip out elements on-the-fly

bull Need to support hypertext link managementndash a word processor alone cannot validate links between

multiple documentsndash TeraText manages links and link validation

bull Need to support collaborative authoring of large documentsndash TeraText allows whole documents or individual

components to be edited

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 34: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

The costbenefit equation for content management vs DMSIm

plem

enta

tion

Initi

al d

ocum

ent s

et

Proliferation of configurationsIn-service maintenance

CMIS

Traditional DMS

Cos

t

Time Note CMIS cost is for first project only

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 35: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Our major success factors to stay ahead of the competition

bull In the starting blocksndash Complex project with no legacy systemsndash Limited budget emphasised need to work smartndash Management willing to try new solutions

bull Success on the trackndash Knowing what was possiblepractical

bull Leveraging prior successesbull Continuing RampD to track technology with specifications

ndash Project controlled by end-users who had to deliver physical and knowledge products

ndash In-country application implementation and interfacing expertise

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 36: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Thank YouNow what does it look like

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 37: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

ILS Data tab in Tree ViewILS Data tab in Tree View

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 38: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Browser based - we could be doing this anywhere in the world

bull Note that we are working on an end-user PCbull The only reason the presentation isnt live is that

ndash Our development environment is on an isolated server

ndash No one plays with live data

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 39: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Data Modules associated with Hardware Part 15004514 in the eMatrix PDM

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 40: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Data Module Graphics associated with Part 15004514 in the eMatrix PDM

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 41: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Operations and TeraText Interface Screen for Equipment Overview Data Module

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 42: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Online View of Data Module retrieved from

the Tenix CMISII TeraText Repository

Annotation points

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 43: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Option to retrieve previous versions of a Data Module from the Tenix CMISII

TeraText Repository

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 44: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor of choice [currently FrameMaker] convert it to SGML

and check it back in to the repository [Check-in]

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 45: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Authoring Environment

bull Tenix modified FrameMaker to use the TeraTextInterface

bull The CMIS option on the tool bar accesses functions to help authors find and insertndash Warnings cautions and notesndash Data module references (links)ndash External source publication references (links)ndash Data module graphics andndash to save the data modules in SGML format

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 46: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

CMIS functions

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 47: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Insert a CautionInsert a Caution

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 48: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Searching TeraText database for a Graphic element

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 49: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Capturing contextual knowledge with links and annotations in the ANZAC Ship Project

bull Explicit and implicit links encode contextual knowledgebull Links are 2-way connectionsbull Annotations are the key to converting implicit contextual

knowledge to codified explicit knowledge

CONTENT MANAGEMENT REPOSITORYANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

SOURCEREGISTRY

PRIMARY DOCUMENT

METADATA---------------------------------

CONTENT

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

11

Documentelement

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

PRIMARYOBJECTS

(ie ltparagt)

0many

OTHERDELIVERABLES

ANDSOURCE

DOCUMENTS

SOURCE REPOSITORY

ANNOTATION

METADATA-------------------------

PRIMARY LINK-------------------------

ANNOTATIONTEXT

-------------------------SECONDARY

LINKS

Documentelement

(ie ltparagt)

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 50: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Annotations

bull Annotations provide the key to capturing context

Source registry reference

Annotation may be added here

Yellow marker indicates annotation exists here Click on marker to see it

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 51: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Annotations in CMIS

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 52: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Annotations in CMIS

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 53: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Technical Manuals list page identifies and shows lifecycle status of manuals produced for the

selected vehicle

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 54: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Tracking document work

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 55: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

bull The Technical Manual is generated as a background process

bull When the generate manual process has been completed an email is sent to the manual owners group

Generating a deliverable document

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 56: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Technical manual delivery files are stored in 3 formats on-line PDF and SGML

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 57: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Browser view

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 58: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Acrobat PDF view

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 59: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

SGML version and the associated graphicelements are delivered in a ZIP File

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 60: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

EXTRA SLIDES

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 61: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Our latest best practicesLand Division

bull Domain expertise in ndash Design and manufacture of Armoured

Personnel Carriersndash Upgrade of military vehiclesndash Design manufacture modification and

repair support of all kinds of major military vehicles

ndash Civilian support armoured amp heavy vehicle maintenance warehousing at military sites

bull Present major vehicle projectsndash Australian Army M113 projectndash ASLAV Phase 3 Project

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 62: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Configuration and knowledge management architecture goals for a large project

bull Product and textual data are structuredand are managed as content

bull Production mgmt data is transactional and is managed as records and fields

bull Goal is to manage all project data within a single configuration management umbrella

MRP PRODUCTION MGMTbull MBOMbull Production planningbull Production schedulebull Procurementbull Warehousingbull Establish amp release workorders

ProjectSchedule

HRM

Accounting

CS2

RFT

Capability requirements Documentation requirements

PRODUCT MODELS(structured designs )

MODELS BOMsbull Component definitionsbull Component hierarchies

- System- Physical structural- Availability

OBJECTS MANAGEDbull Drawingsbull Parts listsbull Configurationsbull Component metadata

DOCUMENT MODELS(structured documents )

MODELSbull Element definitions

- Content- Attributes

bull Element hierarchiesbull Element sequences

OUTPUT OBJECTSbull Contractsubcontract

documentsbull Proceduresinstructionsbull Deliverable documentsbull All other controlled

documents

COMMON REQUIREMENTSbull Config control Change mgmt

- DevelopAuthor- Release- Effectivity

bull Workflow management- Configuration changes- Document changes- Other business objects

bull Track and control source data

Link element to component

Manage elements

LSA toolsLSAR database

Manage design activities

EBOMEBOM

Manage documentation activitie

s

Catalogue

Drawings

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 63: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Users - Interfaces

CMIS

MRP

CAD

RAM

TechPubsACAD

CATIA

TeraText

SGML

Relex

Opus

Production

Procurement

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 64: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

SGML-DMSThe traditional approach

Parsing Enginefragmentcoalesce

Content Relation

Full Text IndexingEngine Relational Engine

Content Attribute Structure Content

Documentdata operations

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead
Page 65: The CMIS Solution for Tenix's M113 Program · Documentation Systems Analyst, Tenix Defence Paul Brouwers (CMII Cert.) Design Resources Manager, TD Land. CMIS MRP Production ... product

Traditional DBMSWeb interface overhead

Web server

Application logic

XML engine

Document Manager

Object Manager

RDBMS

Workflow Content Query

HTTPHTML

SQL

ODBCCORBAhellip

ODMA

Custom

SQLSQL

WAPI

Custom

CGIISAPICGIJavahellip

OmnimarkPerlhellip

Custom

C++Java

SQL

CustomWfMC Custom

  • The CMIS solution for Tenixs M113 Program
  • Our project knowledge revolves around CMIS
  • Scope
  • Company started as AMECON with building warships (Marine Division)
  • Tenix Group Tenix Defence
  • Some Land Division jobs
  • Requirements for safe amp effective operation of all products we build
  • Major quality issues in delivering tech data and knowledge
  • What we are building on
  • TenixRAN architecture for managing ANZAC Ship technical data and content
  • The M113 challange
  • The CMIS solution for Tenixs M113 Program
  • Knowledge is our most important asset
  • Background
  • CMIS was conceived as an umbrella system
  • Overview
  • Configuration management
  • Configuration Management
  • Configuration Management
  • Focus onDocument and content management
  • What is a document
  • What is TeraText
  • TeraText
  • TeraText
  • Content Management in the M113 Upgrade
  • SGML-Content managementStoring XML directly
  • TeraText Web interface overhead
  • Managing document technical data
  • Technical manuals and data modules are managed with CMIS lifecycle process in same way as any other configuration items
  • We are addressing the content management challenge byhellip
  • What real world problems are solved
  • What real world problems are solved
  • What real world problems are solved
  • The costbenefit equation for content management vs DMS
  • Our major success factors to stay ahead of the competition
  • Thank YouNow what does it look like
  • Browser based - we could be doing this anywhere in the world
  • Data Modules associated with Hardware Part 15004514 in the eMatrix PDM
  • Data Module Graphics associated with Part 15004514 in the eMatrix PDM
  • Operations and TeraText Interface Screen for Equipment Overview Data Module
  • Online View of Data Module retrieved from the Tenix CMISII TeraText Repository
  • Option to retrieve previous versions of a Data Module from the Tenix CMISII TeraText Repository
  • Facility to check a Data Module out of the TeraText repository for editing and launch it in the editor of choice [currently Fr
  • Authoring Environment
  • Insert a Caution
  • Capturing contextual knowledge with links and annotations in the ANZAC Ship Project
  • Annotations
  • Annotations in CMIS
  • Annotations in CMIS
  • Technical Manuals list page identifies and shows lifecycle status of manuals produced for the selected vehicle
  • Tracking document work
  • Generating a deliverable document
  • Technical manual delivery files are stored in 3 formats on-line PDF and SGML
  • Browser view
  • Acrobat PDF view
  • SGML version and the associated graphicelements are delivered in a ZIP File
  • Our latest best practicesLand Division
  • Configuration and knowledge management architecture goals for a large project
  • Users - Interfaces
  • SGML-DMSThe traditional approach
  • Traditional DBMSWeb interface overhead