knowledge management at the datum level trish laedtke project manager datachannel/isogen...

31
Knowledge Management Knowledge Management at the Datum Level at the Datum Level Trish Laedtke Trish Laedtke Project Manager Project Manager DataChannel/ISOGEN International DataChannel/ISOGEN International Austin, March 2000 Austin, March 2000

Upload: isabel-byrd

Post on 18-Dec-2015

216 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Knowledge ManagementKnowledge Managementat the Datum Levelat the Datum Level

Trish LaedtkeTrish Laedtke

Project ManagerProject Manager

DataChannel/ISOGEN InternationalDataChannel/ISOGEN International

Austin, March 2000Austin, March 2000

Page 2: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

XML in Knowledge ManagementXML in Knowledge Management

Phenomenal acceptance across industriesPhenomenal acceptance across industries– Used for structuring dataUsed for structuring data– Used for transferring informationUsed for transferring information– New applications available weeklyNew applications available weekly

Limitations in Knowledge ManagementLimitations in Knowledge Management– Legacy applications and data storesLegacy applications and data stores– Non-XML like data. Non-XML like data.

– Engineering drawingsEngineering drawings– VideoVideo– Etc.Etc.

Page 3: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Knowledge ManagementKnowledge Management

Historically known by a variety of other namesHistorically known by a variety of other names– Document ManagementDocument Management– Product Data ManagementProduct Data Management– Content ManagementContent Management– Data warehousing/miningData warehousing/mining

All are wrestling with data management functionsAll are wrestling with data management functions– AccessAccess– RelationshipsRelationships– AccessAccess– Version managementVersion management– AccessAccess

Page 4: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Knowledge ManagementKnowledge Management

Key to all of these is knowing what data to access, by whom, whenKey to all of these is knowing what data to access, by whom, when This capability must be driven below the file level. -- i.e., pieces of data within a document are the driversThis capability must be driven below the file level. -- i.e., pieces of data within a document are the drivers

– For accessFor access– For reuseFor reuse– For processFor process

The possibilities for increased functionality are exponentialThe possibilities for increased functionality are exponential The gains are too valuable to ignoreThe gains are too valuable to ignore

Page 5: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

History of Product Data ManagementHistory of Product Data Management

PDMs became popular in the mid-90’s for management of engineering information regarding parts, PDMs became popular in the mid-90’s for management of engineering information regarding parts, assemblies, and productsassemblies, and products

Similarity to Document Management Systems (DMS)Similarity to Document Management Systems (DMS)– Application sitting on a databaseApplication sitting on a database– Manages object versioning, relationships, and workflow/processManages object versioning, relationships, and workflow/process– Provides the ability to track development and decision historyProvides the ability to track development and decision history– Access is increasingly web-based, but few files are viewable without downloads.Access is increasingly web-based, but few files are viewable without downloads.

Page 6: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

PDMs (cont.)PDMs (cont.)

Differences from DMS Differences from DMS – Diverse data or file types, some of which cannot be dealt with as XMLDiverse data or file types, some of which cannot be dealt with as XML

– Engineering CAD/CAM/CAEEngineering CAD/CAM/CAE– Miscellaneous supporting documentationMiscellaneous supporting documentation

– Diverse types of usersDiverse types of users– Multiple types of relationshipsMultiple types of relationships– Integration with other systems highly probableIntegration with other systems highly probable

– ERPERP– DMSDMS

Closed, controlled system--imposed limitsClosed, controlled system--imposed limits

Page 7: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

whats it.dwg.1

X

Traditional PDM ExampleTraditional PDM Example

Company A manufactures Whatsits. Company A manufactures Whatsits. Engineer creates whatsit.dwg.1 in a CAD Engineer creates whatsit.dwg.1 in a CAD

application.application.

Page 8: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

BOM forwhatsit

Traditional PDM Example (cont.)Traditional PDM Example (cont.)

Support departments create supporting documentation.Support departments create supporting documentation. May be Microsoft WordMay be Microsoft Word or other publishingor other publishing formats.formats. May be financial May be financial or partsor parts database info.database info.

Page 9: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

whats it.dwg.2

Y

BOM forwhatsit

Traditional PDM Example (cont.)Traditional PDM Example (cont.)

Meanwhile, changes occur in the design of Meanwhile, changes occur in the design of Whatsit.Whatsit.

Page 10: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

whats it.dwg.2

Y

W hatsitTechnical

Manual

(Rev B)

BOM forwhatsit

BOM forwhatsit

Traditional PDM Example (cont.)Traditional PDM Example (cont.)

Change is needed in the supporting Change is needed in the supporting documentation, new versions are createddocumentation, new versions are created

Page 11: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

whats it.dwg.2

Y

W hatsitTechnical

Manual

(Rev B)

whosit.dwg.1

Z

BOM forwhatsit

BOM forwhatsit

Traditional PDM Example (cont.)Traditional PDM Example (cont.)

Similar products are createdSimilar products are created

Page 12: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Problems with Traditional PDM Problems with Traditional PDM SystemSystem Relationships are built only at the file levelRelationships are built only at the file level

– Cannot relate parts within drawings to text within a supporting documentCannot relate parts within drawings to text within a supporting document– Cannot track change between versions of a file and the resultant change needed in supporting Cannot track change between versions of a file and the resultant change needed in supporting

documentationdocumentation– Cannot search file content, must rely on metadataCannot search file content, must rely on metadata

Change causes rework in multiple applications, by multiple usersChange causes rework in multiple applications, by multiple users

Page 13: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Problems with Traditional PDM Problems with Traditional PDM System (cont.)System (cont.) Heavily dependent on notification, often requiring employees to Heavily dependent on notification, often requiring employees to

intervene in processintervene in process Expensive: software and time/resourceExpensive: software and time/resource Interchange, being addressed by PDM Elaborations groupInterchange, being addressed by PDM Elaborations group

Page 14: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Key to Redefining Data AccessKey to Redefining Data Access

Data, is Data, is DataData, is Data, is Data– Files are dataFiles are data– Metadata is dataMetadata is data– States are dataStates are data– Relationships are dataRelationships are data

Page 15: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

GrovesGroves

ISO/IEC10744: ISO/IEC10744: A formalized public international standard representationA formalized public international standard representation Provides a common object model, allowing information in many notations to Provides a common object model, allowing information in many notations to

be addressed in a common fashion, be addressed in a common fashion, even if the sources from which groves even if the sources from which groves were generated were not.were generated were not.

Enables effective processing of very large collections of structured content.Enables effective processing of very large collections of structured content.

Page 16: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Groves Are Uniform!Groves Are Uniform!

SGML/XML/HTML Grove CGM Grove

PDF Grove

MS-Excel Grove

API Grove

DB SchemaGrove

HyTime/Xlink Grove

“Style” Grove

Page 17: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Basic Assumptions about GrovesBasic Assumptions about Groves

Groves provide a generic form of data abstractionGroves provide a generic form of data abstraction– Nodes with properties organized as trees or graphsNodes with properties organized as trees or graphs– Simple, consistent API independent of data type detailsSimple, consistent API independent of data type details– Standardized syntaxes and semantics for addressing: HyTime, SDQL, XLink (TBD)Standardized syntaxes and semantics for addressing: HyTime, SDQL, XLink (TBD)– Any kind of data can be mapped to a grove representationAny kind of data can be mapped to a grove representation

Page 18: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

PDM + GrovesPDM + Groves

Diverse types of data can be normalized using Property SetsDiverse types of data can be normalized using Property Sets– Property sets can be reused between different instances of data types…Property sets can be reused between different instances of data types…– ……different data sources present same grove representationdifferent data sources present same grove representation– Opens access to data, not just metadataOpens access to data, not just metadata– Allows for addressing between disparate data typesAllows for addressing between disparate data types– Generation of new data or initialization of processes based on known dataGeneration of new data or initialization of processes based on known data

Groves are not implemented for the sake of groves but as the means to a multitude of value-adding endsGroves are not implemented for the sake of groves but as the means to a multitude of value-adding ends

Page 19: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Access to All DataAccess to All Data

Removes reliance on and limits of metadataRemoves reliance on and limits of metadata– SearchingSearching– Combined with relationships, better sense of Combined with relationships, better sense of

applicabilityapplicability

Normalizaton of data using groves Normalizaton of data using groves allows access to data itselfallows access to data itself

W hatsitTechnical

Manual(Rev A)

Metadata:• Author• Creation date• Revision info• Identification• Key words• Abstract

Page 20: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Conversion to Other FormatsConversion to Other Formats

Enables access to data without the originating software, by Enables access to data without the originating software, by removing the proprietary formatremoving the proprietary format

Allows a single grove aware process to output from several Allows a single grove aware process to output from several different formatsdifferent formats

W hatsitTechnical

Manual(Rev A)

Grove

M icroso ft W ord

W hatsitTechnical

Manual(Rev A)

A S C II/XM L

Page 21: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Relationships at the Data LevelRelationships at the Data Level

Allow the relationship of parts within drawings to text within Allow the relationship of parts within drawings to text within supporting documentationsupporting documentation– Addressing via HyTime or Xlink/XpointerAddressing via HyTime or Xlink/Xpointer– NOTE: only applicable parts of data need to be converted to grovesNOTE: only applicable parts of data need to be converted to groves

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

Grove

Part Info Grove

Part Info

Page 22: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Added Automation CapabilityAdded Automation Capability

Masters can be established in appropriate application and Masters can be established in appropriate application and be used as key data for other filesbe used as key data for other files

Changes in master files are noted, and related info is Changes in master files are noted, and related info is updatedupdated

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

BOM forwhatsit

G roveIncluding

Parts/Assy. Info

GroveIncluding

W BS/BOM

GroveIncluding

W BS/BOM

Page 23: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Allows Creation of New InformationAllows Creation of New Information

Data from diverse formats can Data from diverse formats can be combined and be combined and normalized, then normalized, then converted to another converted to another structured data format, structured data format, e.g., SGML/XML and e.g., SGML/XML and combined to create new combined to create new information productsinformation products

whats it.dwg.1

W hatsitTechnical

Manual(Rev A)

X

BOM forwhatsit

G roveIncluding

Parts/Assy. Info

GroveIncluding

W BS/BOM

GroveIncluding

W BS/BOM

NewFile/Product

Page 24: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Data Transfer Between SystemsData Transfer Between Systems

Files, metadata, and relationships can Files, metadata, and relationships can be modeled in groves, converted to an be modeled in groves, converted to an interchange format, e.g., XMLinterchange format, e.g., XML– NamespacesNamespaces– ArchitecturesArchitectures

whats it.dwg.1

W hatsitTechnical

Manual

(Rev A)

X

whats it.dwg.2

X

W hatsitTechnical

Manual

(Rev B)

whosit.dwg.1

Z

BOM forwhatsit

BOM forwhatsit

G roveInc lud ing files,m etadata, and

re latiosh ipsis com posed o f

sou rce

vers ion

is described by

Page 25: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Degrees of ImplementationDegrees of Implementation

Groves are built andGroves are built andstored external to thestored external to thePDM. Could serve asPDM. Could serve asthe users’ mainthe users’ mainpoint of access to data.point of access to data.

PDM

Gro

ve R

epre

sen

tati

on

s

Topic Mapsand Links

Queries

Pro/EGroves

LSA DataGroves

BOMGroves

OtherGroves...

Pro/E

LSA Data

BOM

Other...

LogisticsProducts

Page 26: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Further IntegrationFurther Integration

Groves are stored and Groves are stored and managed along with the source managed along with the source data. data.

Relationships can exist between Relationships can exist between data in groves within the PDM.data in groves within the PDM.

PDM

Topic Mapsand Links

Queries/Main point of user access

Pro/EGroves

LSA DataGroves

BOMGroves

OtherGroves...

Pro/E

LSA Data

BOM

Other...

Page 27: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

An Idealist ApproachAn Idealist Approach

Given the right infrastructure (resources Given the right infrastructure (resources and OS), groves could become The and OS), groves could become The PDM in a bounded file-system.PDM in a bounded file-system.– Access and storage/lock mechanismsAccess and storage/lock mechanisms– Simple GUI for usersSimple GUI for users– Minimal controls imposedMinimal controls imposed– Workflow versioning/trackingWorkflow versioning/tracking

Page 28: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

An Idealist ApproachAn Idealist Approach

Topic Mapsand Links

Pro/E

LSA Data

BOM

LogisticsProducts

1. Work is Done/Files are Created

3. Groves Created

2. OS LevelCM and Access

Management(Could include Workflow)

Gro

ve R

ep

resen

tati

on

s..

.

Pro/EGroves

LSA DataGroves

BOMGroves

LogisticsGroves...

4. Topic Mapsand Links Created

5. User Interface •Queries•Metrics Produced•Non-proprietary access and viewing of information

6. User finds topic/file needed:At this point, can reuseinformation withoutconverting or ...

7. …’checks out’ and updates filein appropriate applicationFile is run back through conversion process

Page 29: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

Advantages to Groves in PDMAdvantages to Groves in PDM

In and of themselves, groves can be used to open data normally not available to the user or systemIn and of themselves, groves can be used to open data normally not available to the user or system Once data is ‘open’, other standards can be applied to add more value and functionality to dataOnce data is ‘open’, other standards can be applied to add more value and functionality to data

– XSLTXSLT– HyTimeHyTime– DSSSLDSSSL– Etc.Etc.

Page 30: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

““STEP/SGML Harmonization”STEP/SGML Harmonization”

Attempt to formally define relationship between STEP (ISO 10303) and grovesAttempt to formally define relationship between STEP (ISO 10303) and groves– Enable automatic grove representation of STEP entitiesEnable automatic grove representation of STEP entities– Enable automatic representation of grove nodes as STEP entitiesEnable automatic representation of grove nodes as STEP entities– Immediate goal: full integration of engineering CAD/CAM/CAE data and hypermedia through HyTime/XLinkImmediate goal: full integration of engineering CAD/CAM/CAE data and hypermedia through HyTime/XLink

Work progressing but not yet formally publishedWork progressing but not yet formally published– Have established correspondence between the modelsHave established correspondence between the models– Have modeled SGML and HyTime using EXPRESSHave modeled SGML and HyTime using EXPRESS– Need to produce demonstration implementations and formalize resultsNeed to produce demonstration implementations and formalize results

Done within ISO TC184/SC4 committee Done within ISO TC184/SC4 committee Contact: W. Eliot Kimber, [email protected]: W. Eliot Kimber, [email protected]

Page 31: Knowledge Management at the Datum Level Trish Laedtke Project Manager DataChannel/ISOGEN International Austin, March 2000

ResourcesResources

HyTime StandardHyTime Standardwww.hytime.org/papers/htguide.html www.hytime.org/papers/htguide.html ftp.ornl.gov/pub/sgml/wg8/document/n1920/html/n1920.htmlftp.ornl.gov/pub/sgml/wg8/document/n1920/html/n1920.html

GROVES PapersGROVES Papersxml.com/pub/2000/04/19/groves/index.htmlxml.com/pub/2000/04/19/groves/index.htmlwww.hightext.com/IHC96/ek8.htmwww.hightext.com/IHC96/ek8.htmwww.prescod.net/groves/shorttut/www.prescod.net/groves/shorttut/www.oasis-open.org/cover/groves.htmlwww.oasis-open.org/cover/groves.htmlwww.techno.comwww.techno.com

Topic Map StandardTopic Map Standardwww.infoloom.com/tminfo.htm www.infoloom.com/tminfo.htm www.infoloom.com/tmsample/moo1.htmwww.infoloom.com/tmsample/moo1.htm