Hall brouwers2004tenixmatrixinovsummitcmis(present)


Published on

Hall, W.P. and Brouwers, P. 2004. The CMIS solution for Tenix's M113 program. MatrixOne Innovation Summit. Shangri-La's Rasa Sentosa Resort, Singapore, 12 - 14 August, 2004.
System described here still represents world-wide state of the art

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Hall brouwers2004tenixmatrixinovsummitcmis(present)

  1. 1. The CMIS solution for TenixsM113 ProgramWilliam P. Hall (PhD)Documentation Systems Analyst, Tenix DefencePaul Brouwers (CMII Cert.)Design Resources Manager, TD Land
  2. 2. CMISMRPProductionProcurementRAMRelexOpusLSATeraText SGMLTECHNICALPUBLICATIONSCADACADCATIALORACMISMRPProductionProcurementRAMRelexOpusLSALSATeraText SGMLTECHNICALPUBLICATIONSCADACADCATIALORALORAMRP = Mfg. Resource PlanningCAD = Computer Aided DesignLORA = Level of Repair AnalysisRAM = Reliability & MaintainabilityLSA = Logistic Support AnalysisOur project knowledge revolves aroundCMIS
  3. 3. Scope• Some introductory comments about Tenix– History & experience with large, complex projects• Critical issues relating to management of projectdata, information and knowledge• A new project allowed us to embody ourunderstanding with the latest product lifecyclemanagement technology• Focus on how we have extended the coretechnology to encompass content management
  4. 4. Company started as AMECON withbuilding warships (Marine Division)• $A 7 BN ANZAC project to build 10 frigates forAustralian (8) and New Zealand (2) Navies• Signed Nov. 1989 - 8 ships already delivered• Project Protector - preferred tenderer for newships for NZ
  5. 5. Tenix Group / Tenix Defence• One of Australia’s largest private companies, withdefence and commercial clients in Australia, NewZealand, Fiji, Philippines, USA and Europe• Defence is largest of 6 business units, it includes:– Marine (defence & commercial shipbuilding,logistic support, etc)– Land (rebuilding as new 350 M113s, other heavyvehicle work, logistic & base support, etc.)– Aerospace (systems integration, logistic support)– Electronic Systems (systems design, integration,related software)(http://www.tenix.com/)
  6. 6. Some Land Division jobsM113A1 "Upgrade“(Another country in the region recently procured around 100 new LAVs for approx. $600 M)• The Australian Army M113A1s were originallybrought into service during the early 1960’s.• The purpose of the M113 Upgrade Contract is toimprove protection, mobility, communications andfirepower.• Tenix is turning 350 "well used" hulls into newstate-of-the-art vehicles with totally new technicaldata packs for a contract value of $A 391 M.
  7. 7. Requirements for safe & effectiveoperation of all products we build• Capability when when the client needs it– Reliably does what it is supposed to– Available for service when needed– Maintainable - problems can be fixed when they arise– Supportable - critical needs available in supply chain– Operable within limits of human knowledge & capacity• Health, safety and operational knowledge issues– Heavy/complex engineering systems can kill!• Life-cycle cost– Minimise acquisition cost– Minimise documentation, support & maintenance costs– Facilitate "lean maintenance" philosophy
  8. 8. Major quality issues in delivering techdata and knowledge• Clients operational knowledge delivery goals– Correct• Correct information• Consistent across the fleet– Applicable/Effective• Applicable to the configuration of the individual ship/vehicle• Effective for the point in time re engineering changes, etc.– Available• To who needs it, when and where it is needed– Useable• Readily understandable by humans• Readily managed & processed in computer systems• Suppliers knowledge production and usage goals– Fast – High quality – Low cost– Eliminate rework!• Total configuration management is the answer
  9. 9. What we are building on• ANZAC SHIP PROJECT– experience!– Lessons learned• ARCHITECTURE GOALS FOR A LARGE PROJECT
  10. 10. CrossbowValidates and integrates/Normalises data across15 legacy systemsTeraTextContent managementAMPSNavysmaintmgmtCSARSProvides correctivefeedback from AMPSinto supplier/Navyknowledge developmentactivitiesDESIGN / ENGPRODUCT DATAMANAGEMENT• Product Model• CAD / DrawingMgmt• Config Mgmt• Eng Change• WorkflowProcessControl• Doco Revision& ReleaseDOCO CONTENTMANAGEMENTDOCUMENTAUTHORINGLSARDATABASELOGISTICANALYSISTOOLS(prime)PRODUCT CONFIGMANAGEMENT• Product Model• Drawing Mgmt• Config Mgmt• Change Request• WorkflowProcessControl• Doco Revision& ReleaseMAINTENANCEMANAGEMENT• Schedule• Resource Reqs• Procedures• Completion• Downtime• Resource UsageRECORDINGREPORTINGANALYSISTOOLS(prime)•••SUPPLY SYSTEMchange requestconfigchangedoco changeECOchange effecteddocochangeorderreleaseddocochangeEC /docochangerequestmaintenancehistorydocoserverAnalysis &optimisationorders receiptschange taskdoco changeshared systems?data change& ReleaseTenix/RAN architecture for managing ANZACShip technical data and contentUPDATEMAINT DATA/PROCEDUREUPDATECONFIGNavy Systems15 legacysystems!MRPSYSTEMPlanFabricateAssembleconfig changes
  11. 11. The M113 challange7 variants~25 builds350 vehicles• Coherently manage all data and documents required tosupport the M113 fleet through life– Engineering data (well known solutions for this)– Technical data and publication content
  12. 12. The CMIS solution for Tenixs M113 ProgramBig enough project to supportcurrent best practice
  13. 13. Knowledge is our most important asset• Data and documentation are the most importantassets to the company• CMIS is the custodian AND guardian of theCompany’s data and documents– Secure Vaults and Stores– Encrypted– Access control• CM II compliant– Only recognized commercial CM doctrine– Qualified by Institute of CM
  14. 14. Background• Contract: All CM in M113 Project according to– TRAMM (Technical Regulation Army Maint Mgmt)– MIL-STD-973 (Configuration management)• Other standards– Naming follows H6 (US Fed Item Name Directory)– NATO Commodity Codes forms part type• Rule: CMIS manages all tech data for all projects– Engineering data– Source documents– Technical Publication content• No part released until all metadata correct
  15. 15. CMIS was conceived as an "umbrella"system• Single user interface• Data normalization applies to all project data anddocument components from the start• Common workflow management environment• Single point:– electronic signoff– engineering change management and tracking– cost and schedule control• The umbrella covers everything!
  16. 16. Overview• CMIS provides primary user interface• Two major modules– PDM – product data manager – Matrix10• Configuration management• Workflow process• Object management– ANZAC experience proved value of contentmanagement• Authoring activities delegated from Matrix10• Configuration management of elements within documents• Paragraph version management & reuse• Authoring in S1000D - deliver any required structured/unstructured format
  17. 17. Configuration managementThe source of all data generated starts at theconcept phase of the product and grows withthe product!*SOME QUOTES:Configuration management is adisciplinenotan overhead!** Some mad person
  18. 18. Configuration Management• Very distinct phases of CM– Development– Production– In service• Analysis of data types has determined twodistinct types– Objects– Content• To manage these we require two distinctprocesses– CM of objects - provided in Matrix10 PDMenvironment– CM of content - delegated to TeraText
  19. 19. Configuration Management• Baseline management for each engineeringphase• Principles– Items (like Systems) have a lifecycle within theengineering phase.– Items are “promoted” to the next phase throughapproval only.– Items are NEVER deleted – they have “history”.PreliminaryReviewReleaseObsolete
  20. 20. Focus on:Document and content managementIt is configuration management of “blocks oftext”It is configuration management to the lowestlevel inside a document!
  21. 21. What is a document?• The entire history of all versions?• Each set of variants?• Each separate version?• Each rendition – SGML, HTML, PDF?• Each component– volume, chapter, division, warning …?• TeraText uses the Document ManagementAlliance model which concurrentlysupports all of these concepts and providesa framework for managing them
  22. 22. What is TeraText:• Embodies world wide state-of-the-art in informationsystems research in a commercial product– Fully web enabled text database system (not relational)– Data compression for CPU efficiency and speed• High performance compressed/inverted file indexes• typical index ~ size of text– Real-time simultaneous indexing/search/retrieval– Very sophisticated search engine works against index– Standards based• XML/SGML/RTF/PDF etc.• Z39.50, MARC, etc.– Distributed architecture– Scalability to multi-terabyte data, 10,000s users– http://www.teratext com
  23. 23. TeraText
  24. 24. TeraText
  25. 25. Users ManualThis is section 1of the documentThisis theWork File SystemChapterSectionDocumentPDFFragmentFragmentGraphicStorage andsembly RulesDis/asWEB ProtocolSaveEditContent Management in theM113 Upgrade
  26. 26. SGML-Content management:Storing XML directlyParser/Processing engineindexing queryingversioning doc managementContent Attribute StructureDocument/data operationsThis is somearbitrary text whichyou should not beable to readThis is somearbitraThis is somearbitraThis is somearbitrary text whichyou should not beable to readThis is somearbitraThis is somearbitraThis is somearbitrary text whichyou should not beable to readThis is somearbitra
  27. 27. HTTP/HTMLZ39.50TeraText:Web interface overheadTeraTextApplication serverApplicationWorkflowXML engineDocument ManagerTeraText DBSXML engineContent queryObject ManagementRepositoryAceAceXML EngineXML EngineUser Interface ModuleWorkflowEnactmentServiceDocumentVersionManagerMetadataSupportXML/SGMLParser
  28. 28. PDM(Matrix10)Tech Documents(TeraText)DocumentAuthoring(FM+)EC processManaging document technical data• Authoring processfor controlledchanges toauthored content• Achieves– Consistency (viastandards base,DTD and EDD)– Reuse
  29. 29. Technical manuals and data modules aremanaged with CMIS lifecycle process insame way as any other configuration items
  30. 30. We are addressing the contentmanagement challenge by…• Adopting a long term view of thecontent• Ensuring the document modelsupports authoring at the document,component and fragment levels• Truly sharing (reusing) common textsvs rekeying common texts• Direct sourcing of PDM data into partslists tables• Supporting auditable review processesand version control• Using tools and content model toassess impact of change• Building documentation set usingindustry standards and tools• Using COTS authoring tools• Applying industry standards for longlife contentUsersManualMaintenanceManualReuseTextsPublishingand ReviewProcessesCOTSauthoringtoolsVehicleVariants
  31. 31. What real world problems are solved?• The in-service life for an APC is many decades– Most documents contain configuration sensitive content– File system does not track the changes through time– Lifetime of a word processor format is about 5 years– DMS does not provide point-in-time support– TeraText Content Management System manages versionsand provides point-in-time search across versions– SGML(~XML) is essentially unchanged since 1986• Many versions of each manual, changes to individualvehicles etc, leads to many hundreds of documents– DMS typically limited to about 100,000 pieces– TeraText Content Management System scales to manyhundreds of thousands of documents and millions ofconfiguration sensitive components
  32. 32. What real world problems are solved?• About 80% of content is common to allmanuals– DMS only manages whole documents and does not knowwhat is common to other documents– TeraText Content Management system manages thecomponents that make up the document– Reuse, dont rewrite!• Only small component may change in adocument– DMS or file system requires whole document to be storedagain– TeraText Content Management System storescommon components once and tracks versions ofcomponents as well as whole documents– Know "where used"
  33. 33. What real world problems are solved?• May need to strip out classified material for unclassifiedusers– static documents don’t allow for changed details– TeraText can strip out elements on-the-fly• Need to support hypertext link management– a word processor alone cannot validate links betweenmultiple documents– TeraText manages links and link validation• Need to support collaborative authoring of largedocuments– TeraText allows whole documents or individualcomponents to be edited
  34. 34. The cost/benefit equation for contentmanagement vs DMSImplementationInitialdocumentsetProliferation of configurationsIn-service maintenanceCMISTraditional DMSCostTime Note: CMIS cost is for first project only.
  35. 35. Our major success factors to stay aheadof the competition• In the starting blocks– Complex project with no legacy systems– Limited budget emphasised need to work smart– Management willing to try new solutions• Success on the track– Knowing what was possible/practical• Leveraging prior successes• Continuing R&D to track technology with specifications– Project controlled by end-users who had todeliver physical and knowledge products– In-country application implementation andinterfacing expertise
  36. 36. Thank You!Now, what does it look like?
  37. 37. ILS Data tab in Tree ViewILS Data tab in Tree View
  38. 38. Browser based - we could be doing thisanywhere in the world!• Note that we are working on an end-user PC• The only reason the presentation isnt live is that– Our development environment is on an isolatedserver.– No one "plays" with live data!
  39. 39. Data Modules associated with HardwarePart 15004514 in the eMatrix PDM
  40. 40. Data Module Graphics associated with Part15004514 in the eMatrix PDM
  41. 41. Operations and TeraText Interface Screenfor Equipment Overview Data Module
  42. 42. Online View of DataModule retrieved fromthe Tenix CMISIITeraText RepositoryAnnotation points
  43. 43. Option to retrieve previous versions of aData Module from the Tenix CMISIITeraText Repository
  44. 44. Facility to check a Data Module out of the TeraTextrepository for editing and launch it in the editor ofchoice [currently FrameMaker], convert it to SGMLand check it back in to the repository [Check-in]
  45. 45. Authoring Environment• Tenix modified FrameMaker to use the TeraTextInterface.• The CMIS option on the tool bar accessesfunctions to help authors find and insert:– Warnings, cautions and notes– Data module references (links)– External source publication references (links)– Data module graphics, and– to save the data modules in SGML format.
  46. 46. CMIS functions
  47. 47. Insert a CautionInsert a Caution
  48. 48. Searching TeraText databasefor a Graphic element
  49. 49. Capturing contextual knowledge with linksand annotations in the ANZAC Ship Project• Explicit and implicit links encode contextual knowledge• Links are 2-way connections• Annotations are the key to converting implicit contextualknowledge to codified explicit knowledgeCONTENT MANAGEMENT REPOSITORYANNOTATIONMETADATA-------------------------PRIMARY LINK-------------------------ANNOTATIONTEXT-------------------------SECONDARYLINKSANNOTATIONMETADATA-------------------------PRIMARY LINK-------------------------ANNOTATIONTEXT-------------------------SECONDARYLINKSSOURCEREGISTRYPRIMARY DOCUMENTMETADATA---------------------------------CONTENTPRIMARYOBJECTS(i.e., <para>)PRIMARYOBJECTS(i.e., <para>)1:1Documentelement(i.e., <para>)PRIMARYOBJECTS(i.e., <para>)PRIMARYOBJECTS(i.e., <para>)PRIMARYOBJECTS(i.e., <para>)0:manyOTHERDELIVERABLESANDSOURCEDOCUMENTSSOURCE REPOSITORYANNOTATIONMETADATA-------------------------PRIMARY LINK-------------------------ANNOTATIONTEXT-------------------------SECONDARYLINKSDocumentelement(i.e., <para>)
  50. 50. Annotations• Annotations provide the key to capturing contextSource registry referenceAnnotation maybe added hereYellow markerindicatesannotation existshere. Click onmarker to see it
  51. 51. Annotations in CMIS
  52. 52. Annotations in CMIS
  53. 53. Technical Manuals list page identifies and showslifecycle status of manuals produced for theselected vehicle
  54. 54. Tracking document work
  55. 55. • The TechnicalManual is generatedas a backgroundprocess.• When the generatemanual process hasbeen completed anemail is sent to themanual ownersgroup.Generating a deliverable document
  56. 56. Technical manual delivery files are stored in3 formats: on-line, PDF and SGML
  57. 57. Browser view
  58. 58. Acrobat PDF view
  59. 59. SGML version and the associated graphicelements are delivered in a ZIP File
  60. 60. EXTRA SLIDES
  61. 61. Our latest best practices:Land Division• Domain expertise in:– Design and manufacture of ArmouredPersonnel Carriers– Upgrade of military vehicles– Design, manufacture, modification andrepair support of all kinds of majormilitary vehicles– Civilian support, armoured & heavyvehicle maintenance, warehousing atmilitary sites• Present major vehicle projects– Australian Army M113 project– ASLAV Phase 3 Project
  62. 62. Configuration and knowledge managementarchitecture goals for a large project• Product and textualdata are structuredand are managed ascontent• Production mgmt datais transactional and ismanaged as recordsand fields• Goal is to manageall project datawithin a singleconfigurationmanagementumbrella MRP / PRODUCTION MGMT• MBOM• Production planning• Production schedule• Procurement• Warehousing• Establish & release workordersProjectScheduleHRMAccountingCS2RFTCapability requirements Documentation requirementsPRODUCT MODELS(structured designs )MODELS / BOMs:• Component definitions• Component hierarchies- System- Physical structural- AvailabilityOBJECTS MANAGED• Drawings• Parts lists• Configurations• Component metadataDOCUMENT MODELS(structured documents )MODELS:• Element definitions- Content- Attributes• Element hierarchies• Element sequencesOUTPUT OBJECTS• Contract/subcontractdocuments• Procedures/instructions• Deliverable documents• All other controlleddocumentsCOMMON REQUIREMENTS• Config control / Change mgmt- Develop/Author- Release- Effectivity• Workflow management- Configuration changes- Document changes- Other business objects• Track and control source dataLink element to componentManage elementsLSA toolsLSAR databaseManagedesignactivitiesEBOMEBOMManage documentationactivitiesCatalogueDrawings
  63. 63. Users - InterfacesCMISMRPCADRAMTechPubsACADCATIATeraTextSGMLRelexOpusProductionProcurement
  64. 64. SGML-DMS:The traditional approachParsing Enginefragment/coalesceContent RelationFull Text IndexingEngineRelational EngineContent Attribute, Structure, ContentDocument/data operations
  65. 65. Traditional DBMS:Web interface overheadWeb serverApplication logicXML engineDocument ManagerObject ManagerRDBMSWorkflow Content QueryHTTP/HTMLSQLODBC/CORBA…ODMA?CustomSQLSQLWAPICustomCGI/ISAPICGI/Java…Omnimark/Perl…CustomC++/JavaSQLCustom/WfMC Custom