An introduction to the concepts, benefits and terminology of product data management
Identifieur interne : 000D87 ( Istex/Corpus ); précédent : 000D86; suivant : 000D88An introduction to the concepts, benefits and terminology of product data management
Auteurs : Mike PhilpottsSource :
- Industrial Management & Data Systems [ 0263-5577 ] ; 1996-06-01.
Abstract
Product data management PDM systems help to keep track of the masses of information needed to design, manufacture or build products and then to maintain them. They can be applied to a wide range of products and industries and across the whole spectrum of organizational functions. Benefits extend far beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality. Defines and describes the type of features and functions that should be found in a PDM system and addresses the following data vault and document management workflow and process management product structure management classification project management communication and notification data transport and translation image services system administration and PDM environments.
Url:
DOI: 10.1108/02635579610117467
Links to Exploration step
ISTEX:BFF38C6A204BD985CA34AC9818DBB760841F8C3BLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">An introduction to the concepts, benefits and terminology of product data management</title>
<author wicri:is="90%"><name sortKey="Philpotts, Mike" sort="Philpotts, Mike" uniqKey="Philpotts M" first="Mike" last="Philpotts">Mike Philpotts</name>
<affiliation><mods:affiliation>Business Consultant in Product Data Management, CIMdata Ltd, Coventry, UK</mods:affiliation>
</affiliation>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:BFF38C6A204BD985CA34AC9818DBB760841F8C3B</idno>
<date when="1996" year="1996">1996</date>
<idno type="doi">10.1108/02635579610117467</idno>
<idno type="url">https://api.istex.fr/document/BFF38C6A204BD985CA34AC9818DBB760841F8C3B/fulltext/pdf</idno>
<idno type="wicri:Area/Istex/Corpus">000D87</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">An introduction to the concepts, benefits and terminology of product data management</title>
<author wicri:is="90%"><name sortKey="Philpotts, Mike" sort="Philpotts, Mike" uniqKey="Philpotts M" first="Mike" last="Philpotts">Mike Philpotts</name>
<affiliation><mods:affiliation>Business Consultant in Product Data Management, CIMdata Ltd, Coventry, UK</mods:affiliation>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series><title level="j">Industrial Management & Data Systems</title>
<idno type="ISSN">0263-5577</idno>
<imprint><publisher>MCB UP Ltd</publisher>
<date type="published" when="1996-06-01">1996-06-01</date>
<biblScope unit="volume">96</biblScope>
<biblScope unit="issue">4</biblScope>
<biblScope unit="page" from="11">11</biblScope>
<biblScope unit="page" to="17">17</biblScope>
</imprint>
<idno type="ISSN">0263-5577</idno>
</series>
<idno type="istex">BFF38C6A204BD985CA34AC9818DBB760841F8C3B</idno>
<idno type="DOI">10.1108/02635579610117467</idno>
<idno type="filenameID">0290960403</idno>
<idno type="original-pdf">0290960403.pdf</idno>
<idno type="href">02635579610117467.pdf</idno>
</biblStruct>
</sourceDesc>
<seriesStmt><idno type="ISSN">0263-5577</idno>
</seriesStmt>
</fileDesc>
<profileDesc><textClass></textClass>
<langUsage><language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en">Product data management PDM systems help to keep track of the masses of information needed to design, manufacture or build products and then to maintain them. They can be applied to a wide range of products and industries and across the whole spectrum of organizational functions. Benefits extend far beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality. Defines and describes the type of features and functions that should be found in a PDM system and addresses the following data vault and document management workflow and process management product structure management classification project management communication and notification data transport and translation image services system administration and PDM environments.</div>
</front>
</TEI>
<istex><corpusName>emerald</corpusName>
<author><json:item><name>Mike Philpotts</name>
<affiliations><json:string>Business Consultant in Product Data Management, CIMdata Ltd, Coventry, UK</json:string>
</affiliations>
</json:item>
</author>
<subject><json:item><lang><json:string>eng</json:string>
</lang>
<value>Database management</value>
</json:item>
<json:item><lang><json:string>eng</json:string>
</lang>
<value>Databases</value>
</json:item>
<json:item><lang><json:string>eng</json:string>
</lang>
<value>Process management</value>
</json:item>
<json:item><lang><json:string>eng</json:string>
</lang>
<value>Product information</value>
</json:item>
<json:item><lang><json:string>eng</json:string>
</lang>
<value>Product lifecycle</value>
</json:item>
</subject>
<language><json:string>eng</json:string>
</language>
<abstract>Product data management PDM systems help to keep track of the masses of information needed to design, manufacture or build products and then to maintain them. They can be applied to a wide range of products and industries and across the whole spectrum of organizational functions. Benefits extend far beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality. Defines and describes the type of features and functions that should be found in a PDM system and addresses the following data vault and document management workflow and process management product structure management classification project management communication and notification data transport and translation image services system administration and PDM environments.</abstract>
<qualityIndicators><score>5.421</score>
<pdfVersion>1.1</pdfVersion>
<pdfPageSize>595 x 842 pts (A4)</pdfPageSize>
<refBibsNative>false</refBibsNative>
<keywordCount>5</keywordCount>
<abstractCharCount>795</abstractCharCount>
<pdfWordCount>4029</pdfWordCount>
<pdfCharCount>26708</pdfCharCount>
<pdfPageCount>7</pdfPageCount>
<abstractWordCount>116</abstractWordCount>
</qualityIndicators>
<title>An introduction to the concepts, benefits and terminology of product data management</title>
<genre.original><json:string>e-viewpoint</json:string>
</genre.original>
<genre><json:string>other</json:string>
</genre>
<host><volume>96</volume>
<publisherId><json:string>imds</json:string>
</publisherId>
<pages><last>17</last>
<first>11</first>
</pages>
<issn><json:string>0263-5577</json:string>
</issn>
<issue>4</issue>
<subject><json:item><value>Economics</value>
</json:item>
<json:item><value>Labour economics</value>
</json:item>
<json:item><value>Knowledge sharing</value>
</json:item>
<json:item><value>Information & knowledge management</value>
</json:item>
<json:item><value>Knowledge management</value>
</json:item>
<json:item><value>Knowledge sharing</value>
</json:item>
<json:item><value>Knowledge sharing</value>
</json:item>
<json:item><value>Information & knowledge management</value>
</json:item>
<json:item><value>Information systems</value>
</json:item>
<json:item><value>Knowledge management</value>
</json:item>
<json:item><value>Management science & operations</value>
</json:item>
<json:item><value>Logistics</value>
</json:item>
<json:item><value>Quality management/systems</value>
</json:item>
<json:item><value>Supply chain management</value>
</json:item>
<json:item><value>Supply chain information systems</value>
</json:item>
</subject>
<genre><json:string>Journal</json:string>
</genre>
<language><json:string>unknown</json:string>
</language>
<title>Industrial Management & Data Systems</title>
<doi><json:string>10.1108/imds</json:string>
</doi>
</host>
<publicationDate>1996</publicationDate>
<copyrightDate>1996</copyrightDate>
<doi><json:string>10.1108/02635579610117467</json:string>
</doi>
<id>BFF38C6A204BD985CA34AC9818DBB760841F8C3B</id>
<fulltext><json:item><original>true</original>
<mimetype>application/pdf</mimetype>
<extension>pdf</extension>
<uri>https://api.istex.fr/document/BFF38C6A204BD985CA34AC9818DBB760841F8C3B/fulltext/pdf</uri>
</json:item>
<json:item><original>false</original>
<mimetype>application/zip</mimetype>
<extension>zip</extension>
<uri>https://api.istex.fr/document/BFF38C6A204BD985CA34AC9818DBB760841F8C3B/fulltext/zip</uri>
</json:item>
<istex:fulltextTEI uri="https://api.istex.fr/document/BFF38C6A204BD985CA34AC9818DBB760841F8C3B/fulltext/tei"><teiHeader><fileDesc><titleStmt><title level="a" type="main" xml:lang="en">An introduction to the concepts, benefits and terminology of product data management</title>
</titleStmt>
<publicationStmt><authority>ISTEX</authority>
<publisher>MCB UP Ltd</publisher>
<availability><p>EMERALD</p>
</availability>
<date>1996</date>
</publicationStmt>
<sourceDesc><biblStruct type="inbook"><analytic><title level="a" type="main" xml:lang="en">An introduction to the concepts, benefits and terminology of product data management</title>
<author><persName><forename type="first">Mike</forename>
<surname>Philpotts</surname>
</persName>
<affiliation>Business Consultant in Product Data Management, CIMdata Ltd, Coventry, UK</affiliation>
</author>
</analytic>
<monogr><title level="j">Industrial Management & Data Systems</title>
<idno type="pISSN">0263-5577</idno>
<idno type="DOI">10.1108/imds</idno>
<imprint><publisher>MCB UP Ltd</publisher>
<date type="published" when="1996-06-01"></date>
<biblScope unit="volume">96</biblScope>
<biblScope unit="issue">4</biblScope>
<biblScope unit="page" from="11">11</biblScope>
<biblScope unit="page" to="17">17</biblScope>
</imprint>
</monogr>
<idno type="istex">BFF38C6A204BD985CA34AC9818DBB760841F8C3B</idno>
<idno type="DOI">10.1108/02635579610117467</idno>
<idno type="filenameID">0290960403</idno>
<idno type="original-pdf">0290960403.pdf</idno>
<idno type="href">02635579610117467.pdf</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><creation><date>1996</date>
</creation>
<langUsage><language ident="en">en</language>
</langUsage>
<abstract xml:lang="en"><p>Product data management PDM systems help to keep track of the masses of information needed to design, manufacture or build products and then to maintain them. They can be applied to a wide range of products and industries and across the whole spectrum of organizational functions. Benefits extend far beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality. Defines and describes the type of features and functions that should be found in a PDM system and addresses the following data vault and document management workflow and process management product structure management classification project management communication and notification data transport and translation image services system administration and PDM environments.</p>
</abstract>
<textClass><keywords scheme="keyword"><list><head>Keywords</head>
<item><term>Database management</term>
</item>
<item><term>Databases</term>
</item>
<item><term>Process management</term>
</item>
<item><term>Product information</term>
</item>
<item><term>Product lifecycle</term>
</item>
</list>
</keywords>
</textClass>
<textClass><keywords scheme="Emerald Subject Group"><list><label>cat-ECO</label>
<item><term>Economics</term>
</item>
<label>cat-LBEC</label>
<item><term>Labour economics</term>
</item>
<label>cat-KS</label>
<item><term>Knowledge sharing</term>
</item>
</list>
</keywords>
</textClass>
<textClass><keywords scheme="Emerald Subject Group"><list><label>cat-IKM</label>
<item><term>Information & knowledge management</term>
</item>
<label>cat-KMG cat-KM</label>
<item><term>Knowledge management</term>
</item>
<label>cat-KS</label>
<item><term>Knowledge sharing</term>
</item>
<label>cat-KS</label>
<item><term>Knowledge sharing</term>
</item>
</list>
</keywords>
</textClass>
<textClass><keywords scheme="Emerald Subject Group"><list><label>cat-IKM</label>
<item><term>Information & knowledge management</term>
</item>
<label>cat-ISYS</label>
<item><term>Information systems</term>
</item>
<label>cat-KMG cat-KM</label>
<item><term>Knowledge management</term>
</item>
</list>
</keywords>
</textClass>
<textClass><keywords scheme="Emerald Subject Group"><list><label>cat-MSOP</label>
<item><term>Management science & operations</term>
</item>
<label>cat-LOG</label>
<item><term>Logistics</term>
</item>
<label>cat-QMS</label>
<item><term>Quality management/systems</term>
</item>
<label>cat-SCMT</label>
<item><term>Supply chain management</term>
</item>
<label>cat-SCIS</label>
<item><term>Supply chain information systems</term>
</item>
</list>
</keywords>
</textClass>
</profileDesc>
<revisionDesc><change when="1996-06-01">Published</change>
</revisionDesc>
</teiHeader>
</istex:fulltextTEI>
<json:item><original>false</original>
<mimetype>text/plain</mimetype>
<extension>txt</extension>
<uri>https://api.istex.fr/document/BFF38C6A204BD985CA34AC9818DBB760841F8C3B/fulltext/txt</uri>
</json:item>
</fulltext>
<metadata><istex:metadataXml wicri:clean="corpus emerald not found" wicri:toSee="no header"><istex:xmlDeclaration>version="1.0" encoding="UTF-8"</istex:xmlDeclaration>
<istex:document><!-- Auto generated NISO JATS XML created by Atypon out of MCB DTD source files. Do Not Edit! --><article dtd-version="1.0" xml:lang="en" article-type="e-viewpoint"><front><journal-meta><journal-id journal-id-type="publisher-id">imds</journal-id>
<journal-id journal-id-type="doi">10.1108/imds</journal-id>
<journal-title-group><journal-title>Industrial Management & Data Systems</journal-title>
</journal-title-group>
<issn pub-type="ppub">0263-5577</issn>
<publisher><publisher-name>MCB UP Ltd</publisher-name>
</publisher>
</journal-meta>
<article-meta><article-id pub-id-type="doi">10.1108/02635579610117467</article-id>
<article-id pub-id-type="original-pdf">0290960403.pdf</article-id>
<article-id pub-id-type="filename">0290960403</article-id>
<article-categories><subj-group subj-group-type="type-of-publication"><compound-subject><compound-subject-part content-type="code">e-viewpoint</compound-subject-part>
<compound-subject-part content-type="label">Viewpoint</compound-subject-part>
</compound-subject>
</subj-group>
<subj-group subj-group-type="subject"><compound-subject><compound-subject-part content-type="code">cat-ECO</compound-subject-part>
<compound-subject-part content-type="label">Economics</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-LBEC</compound-subject-part>
<compound-subject-part content-type="label">Labour economics</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-KS</compound-subject-part>
<compound-subject-part content-type="label">Knowledge sharing</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="subject"><compound-subject><compound-subject-part content-type="code">cat-IKM</compound-subject-part>
<compound-subject-part content-type="label">Information & knowledge management</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-KMG cat-KM</compound-subject-part>
<compound-subject-part content-type="label">Knowledge management</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-KS</compound-subject-part>
<compound-subject-part content-type="label">Knowledge sharing</compound-subject-part>
</compound-subject>
<compound-subject><compound-subject-part content-type="code">cat-KS</compound-subject-part>
<compound-subject-part content-type="label">Knowledge sharing</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="subject"><compound-subject><compound-subject-part content-type="code">cat-IKM</compound-subject-part>
<compound-subject-part content-type="label">Information & knowledge management</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-ISYS</compound-subject-part>
<compound-subject-part content-type="label">Information systems</compound-subject-part>
</compound-subject>
</subj-group>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-KMG cat-KM</compound-subject-part>
<compound-subject-part content-type="label">Knowledge management</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
<subj-group subj-group-type="subject"><compound-subject><compound-subject-part content-type="code">cat-MSOP</compound-subject-part>
<compound-subject-part content-type="label">Management science & operations</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-LOG</compound-subject-part>
<compound-subject-part content-type="label">Logistics</compound-subject-part>
</compound-subject>
</subj-group>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-QMS</compound-subject-part>
<compound-subject-part content-type="label">Quality management/systems</compound-subject-part>
</compound-subject>
</subj-group>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-SCMT</compound-subject-part>
<compound-subject-part content-type="label">Supply chain management</compound-subject-part>
</compound-subject>
<subj-group><compound-subject><compound-subject-part content-type="code">cat-SCIS</compound-subject-part>
<compound-subject-part content-type="label">Supply chain information systems</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
</subj-group>
</article-categories>
<title-group><article-title>An introduction to the concepts, benefits and terminology of product data management</article-title>
</title-group>
<contrib-group><contrib contrib-type="author"><string-name><given-names>Mike</given-names>
<surname>Philpotts</surname>
</string-name>
<aff>Business Consultant in Product Data Management, CIMdata Ltd, Coventry, UK</aff>
</contrib>
</contrib-group>
<pub-date pub-type="ppub"><day>01</day>
<month>06</month>
<year>1996</year>
</pub-date>
<volume>96</volume>
<issue>4</issue>
<fpage>11</fpage>
<lpage>17</lpage>
<permissions><copyright-statement>© MCB UP Limited</copyright-statement>
<copyright-year>1996</copyright-year>
<license license-type="publisher"><license-p></license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="02635579610117467.pdf"></self-uri>
<abstract><p>Product data management (PDM) systems help to keep track of the masses of information needed to design, manufacture or build products and then to maintain them. They can be applied to a wide range of products and industries and across the whole spectrum of organizational functions. Benefits extend far beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality. Defines and describes the type of features and functions that should be found in a PDM system and addresses the following: data vault and document management; workflow and process management; product structure management; classification; project management; communication and notification; data transport and translation; image services; system administration; and PDM environments.</p>
</abstract>
<kwd-group><kwd>Database management</kwd>
<x>, </x>
<kwd>Databases</kwd>
<x>, </x>
<kwd>Process management</kwd>
<x>, </x>
<kwd>Product information</kwd>
<x>, </x>
<kwd>Product lifecycle</kwd>
</kwd-group>
<custom-meta-group><custom-meta><meta-name>peer-reviewed</meta-name>
<meta-value>no</meta-value>
</custom-meta>
<custom-meta><meta-name>academic-content</meta-name>
<meta-value>yes</meta-value>
</custom-meta>
<custom-meta><meta-name>rightslink</meta-name>
<meta-value>included</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
<ack><p>© CIM data Ltd 1996</p>
</ack>
</front>
<body><p>CAD/CAM/CAE and CIM systems, with their ability to quickly generate and change product data, have strained the conventional systems used to manage data and the process of creating and using this data. Users can easily create vast amounts of product related information. To complicate matters further, this information is often stored in different formats within a variety of systems and resides on different, dispersed computers. It may also be stored on multiple media types such as computer files, paper, and aperture cards.</p>
<p>Product data management (PDM) is a tool that helps engineers and others manage both data and the product development process. PDM systems keep track of the masses of data and information required to design, manufacture or build products and then support and maintain them.</p>
<p>Product data management is a general extension of techniques commonly known as engineering data management (EDM), document management, product information management (PIM), technical data management (TDM), technical information management (TIM), image management and other titles. PDM provides a common term, encompassing all systems that are used to manage product definition information.</p>
<p>PDM integrates and manages processes, applications and information that define products across multiple systems and media. The profitability of products is dependent on orderly and efficient development, fabrication and distribution. PDM systems help achieve these goals.</p>
<p>PDM manages all product‐related information ‐ including electronic documents, digital files and database records. Examples of “products” include: <list list-type="bullet"><list-item><label>•</label>
<p>manufactured products ‐ motor vehicles, computers, refrigerators, mobile phones;</p>
</list-item>
<list-item><label>•</label>
<p>projects ‐ buildings, bridges, highways;</p>
</list-item>
<list-item><label>•</label>
<p>plant ‐ oil refineries, offshore platforms, pharmaceutical or food processing plants;</p>
</list-item>
<list-item><label>•</label>
<p>facilities ‐ airports, harbours, railway systems, logistics warehouses; and</p>
</list-item>
<list-item><label>•</label>
<p>assets ‐ utility distribution networks for electricity, telecommunications, water, gas, cable TV and power plants.</p>
</list-item>
</list>
</p>
<p>While the whole organization can benefit from the use of PDM, individuals with a particular interest in its advantages are: chief executives, technical directors, chief engineers, engineering managers and engineers of all disciplines, heads of information technology or of information services, design managers, CAD/CAM/CAE managers, production engineers, project managers, operations and maintenance managers, estimators and purchasing officers, marketing and sales managers.</p>
<p>Companies in every industry segment that design and manufacture products can benefit from the use of PDM. Some examples include: <list list-type="bullet"><list-item><label>•</label>
<p>aerospace;</p>
</list-item>
<list-item><label>•</label>
<p>automotive: assembly and components;</p>
</list-item>
<list-item><label>•</label>
<p>general mechanical manufacturing;</p>
</list-item>
<list-item><label>•</label>
<p>electrical and electronic products;</p>
</list-item>
<list-item><label>•</label>
<p>computer manufacturing;</p>
</list-item>
<list-item><label>•</label>
<p>defence industries;</p>
</list-item>
<list-item><label>•</label>
<p>oil and gas exploration and production;</p>
</list-item>
<list-item><label>•</label>
<p>chemical and process engineering;</p>
</list-item>
<list-item><label>•</label>
<p>food and drinks industries;</p>
</list-item>
<list-item><label>•</label>
<p>pharmaceuticals;</p>
</list-item>
<list-item><label>•</label>
<p>power generation;</p>
</list-item>
<list-item><label>•</label>
<p>construction companies;</p>
</list-item>
<list-item><label>•</label>
<p>transport operators; road, rail, sea, air;</p>
</list-item>
<list-item><label>•</label>
<p>utilities: electricity, water, telecommunications;</p>
</list-item>
<list-item><label>•</label>
<p>design and management consultants; and</p>
</list-item>
<list-item><label>•</label>
<p>central and local government.</p>
</list-item>
</list>
</p>
<sec><title> Benefits</title>
<p>PDM systems and methods provide a structure in which all types of information used to define, manufacture and support products are stored, managed and controlled. Typically, PDM will be used to work with electronic documents, digital files and database records, including: <list list-type="bullet"><list-item><label>•</label>
<p>product configurations;</p>
</list-item>
<list-item><label>•</label>
<p>part definitions and other design data;</p>
</list-item>
<list-item><label>•</label>
<p>specifications;</p>
</list-item>
<list-item><label>•</label>
<p>CAD drawings;</p>
</list-item>
<list-item><label>•</label>
<p>geometric models;</p>
</list-item>
<list-item><label>•</label>
<p>images (scanned drawings, photographs, etc.);</p>
</list-item>
<list-item><label>•</label>
<p>engineering analysis models and results;</p>
</list-item>
<list-item><label>•</label>
<p>manufacturing process plans and routeings;</p>
</list-item>
<list-item><label>•</label>
<p>numerically controlled part programmes;</p>
</list-item>
<list-item><label>•</label>
<p>software components of products;</p>
</list-item>
<list-item><label>•</label>
<p>electronically stored documents, notes and correspondence;</p>
</list-item>
<list-item><label>•</label>
<p>audio and live video annotations;</p>
</list-item>
<list-item><label>•</label>
<p>hardcopy (paper‐based and microform) documents (by reference);</p>
</list-item>
<list-item><label>•</label>
<p>project plans;</p>
</list-item>
<list-item><label>•</label>
<p>others.</p>
</list-item>
</list>
</p>
<p>In short, any information needed throughout a product’s life can be managed by a product data management system, making correct data accessible to all people and systems that have a need to use them. PDM is not limited to managing the design cycle alone but, according to user needs, can manage product conception, detailed design, prototyping and testing, manufacturing or fabrication, operation and maintenance. The product development process is managed as well as the data; PDM systems control product information, states, approval processes and authorizations, as well as other activities that impact on product data. By providing data management and security, PDM systems ensure that users always get and share the most up to date, approved information.</p>
<p>The implementation of PDM technology doesn’t have to be an all‐or‐nothing undertaking. PDM will provide significant productivity gains when it is used by a workgroup. However, a much greater impact will result when PDM becomes an enterprise‐wide environment.</p>
<p>While the emphasis in this article is on engineering, manufacturing and other industrial uses, the concepts presented here can just as effectively be used in publishing, software development, financial services, or any other environment in which product information and processes will benefit from control. PDM systems provide direct benefits throughout an organization.</p>
<p>Within the area of product design and development, almost everyone in an organization can gain an advantage through the use of this technology. Typical users of PDM systems include designers, engineers, manufacturing engineers, operations engineers, project managers, administrators and purchasing agents. At the discretion of project managers, people who may customarily be “left in the dark” during early project phases can be allowed to see and contribute to product design and development by using PDM’s abilities to distribute and control access to product information.</p>
<p>Linking product data through a database is a major factor in assuring its integrity. Knowing and managing who is using data, and how, provides the foundation required to maintain information integrity. Data inconsistencies can be avoided and relationships between data maintained.</p>
<p>Because of their application to a broad set of users and disciplines and their facilities for controlling the flow of information, PDM systems serve as enablers for implementing concurrent engineering practices.</p>
<p>The benefits of this technology extend well beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality, in addition to the benefits of reducing engineering design time. Product changes are inevitable, but they can become ruinously expensive and disruptive if they occur late in the product life cycle, such as during production or fabrication. Product changes will occur earlier in the product life cycle if product teams are encouraged to share data and documents in a PDM environment. This is the path to better products, reduced costs, saved time, less scrap and less wasteful re‐work.</p>
</sec>
<sec><title> Functions and features</title>
<p>PDM is still a relatively new technology. Although the concept has been around in various guises for a long time, the first commercially available computerized systems were introduced in the early 1980s. While the technological base is growing rapidly, there are not yet standards that define the functionality necessary to have useful PDM systems. The following definitions are based on CIMdata’s numerous consulting projects with PDM users and suppliers and our experience in reviewing and evaluating commercial PDM systems.</p>
<p>The types of features and functions that should be found in a PDM system will be defined and described. This is done independently of any particular application or data form. Features and functions are presented in terms of an “ideal” PDM system. None of the systems on the market today contains all of the features discussed. However, many suppliers are adding to and improving their systems along the general lines outlined.</p>
<p>In addition to the direct functionality of the PDM system, environmental factors affect the system’s use and value. Issues related to distributed networks, client‐server architectures, the user interface and database management are all important in determining the size and make‐up of a productive PDM system.</p>
<p>A PDM system is an application in its own right. For a PDM system to support any particular type of product development, it needs a basic set of functions. These functions serve all of the disciplines that benefit from PDM.</p>
<p>PDM systems comprise: <list list-type="bullet"><list-item><label>•</label>
<p>an electronic vault or data repository;</p>
</list-item>
<list-item><label>•</label>
<p>a set of user functions; and</p>
</list-item>
<list-item><label>•</label>
<p>a set of utility functions.</p>
</list-item>
</list>
</p>
<p>Information from additional computer applications is controlled by the PDM system’s assumption of the roles of file access and saving. This is accomplished by either embedding PDM commands in other applications that create data (such as CAD, word processors, spreadsheets, desktop publishing, or specialized software), or vice versa.</p>
<p>Legacy documents, such as drawings on paper or aperture cards, or other hardcopy records can be captured by scanning and storing them as images within the electronic vault. Some users prefer to convert images of textual documents by optical character recognition (OCR) into computer‐readable text. It is feasible to convert some raster (scanned) images of drawings into vector data via software, while some users prefer to capture vector data by digitization techniques.</p>
<p>An electronic vault is used as a repository to control all kinds of product information. The vault is a data store that contains some data within itself and controls other externally‐generated data by managing access to it. Two types of data are stored: <list list-type="order"><list-item><label>1. </label>
<p>1Product data generated in various applications, such as specifications, CAD models, CAE data, maintenance records, operating manuals.</p>
</list-item>
<list-item><label>2. </label>
<p>2Meta‐data, which is data relating to PDM‐controlled information. Meta‐data is stored in a PDM database and supports the functions performed by the PDM system.</p>
</list-item>
</list>
</p>
<p>The functionality of PDM systems falls into two broad categories: user functions and utility functions. User functions provide the user’s interface to the PDM system’s capabilities including data storage, retrieval and management. Different types of users employ different subsets of the user functions. These functions are divided into five categories: <list list-type="order"><list-item><label>1. </label>
<p>1Data vault and document management.</p>
</list-item>
<list-item><label>2. </label>
<p>2Workflow and process management.</p>
</list-item>
<list-item><label>3. </label>
<p>3Product structure management.</p>
</list-item>
<list-item><label>4. </label>
<p>4Classification.</p>
</list-item>
<list-item><label>5. </label>
<p>5Programme management.</p>
</list-item>
</list>
</p>
<p>Utility functions provide support to both simplify the use of the system and provide support to the user functions mentioned above. Utility functions interface with the operating environment and insulate its functions from the user. Tailoring permits systems to operate in conformance with the user’s environment. Utility functions include: <list list-type="bullet"><list-item><label>•</label>
<p>communication and notification;</p>
</list-item>
<list-item><label>•</label>
<p>data transport;</p>
</list-item>
<list-item><label>•</label>
<p>data translation;</p>
</list-item>
<list-item><label>•</label>
<p>image services;</p>
</list-item>
<list-item><label>•</label>
<p>system administration.</p>
</list-item>
</list>
</p>
<sec><title>Data vault and document management</title>
<p>A major issue for many companies is ensuring that product data is up to date, correct and protected from accidental or deliberate damage. Data vault and document management provides secure storage and retrieval of product definition information. Check‐in and check‐out functions work with data stored in an electronic vault to provide secure storage and access control. Release levels for design data are defined and users are assigned access authorizations.</p>
<p>The electronic vault either contains the product information itself or information that allows users to access the data. Users and applications must go through the PDM system to get controlled data. This may seem like a road block to getting the job done, but this is not the case. For it means that users do not have to know where information is actually located and ensures that they get the latest versions of data. This works in a fashion similar to library systems with a card index (the meta‐data) that leads users to books (the product data). Meta‐data and other attributes help users search for and retrieve relevant data.</p>
<p>The release management process ensures that data attains release status only after passing a pre‐defined approval process. Various approval scenarios can be used. User access to released information is based on project, password and other user‐defined controls.</p>
<p>Meta‐data stores information about product data so that changes, release levels, approval authorizations and other data controls can be tracked and audited. The meta‐data also is used to create relationships among product data so that information can be grouped and related by common usage and among products. Product definition data can be associated with product configurations as well as parts.</p>
<p>Data stored in locations other than the vault (paper drawings, documents stored on remote computing systems, etc) can be controlled by reference. Of course, this does not provide the same level of security as for data in the vault. However, security is at least as good as that found in manual systems and tracking is simplified.</p>
</sec>
<sec><title>Workflow and process management</title>
<p>Using data vault and document management alone, a PDM system can react to users’ <italic>ad hoc</italic>
demands. With workflow and process management, a PDM system can, in addition, be pro‐active. It can interact with people, working according to an organization’s pre‐defined business processes and with data and documents, to achieve corporate objectives. Repetitive processes can be programmed within the PDM system and it can map a model of the organization. Workflow and process management provide a route to drive a business with information.</p>
<p>Workflow and process management can define and control changes to product configurations, part definitions, other product data, data relationships and data versions or variations. Workflow and process management defines and controls the process of reviewing and approving changes to product data. The workflow and processes are defined in terms of a sequence of events that must occur before modified product information is allowed to be released.</p>
<p>Individuals authorized to approve changes to particular design information are identified within the PDM system. The system tracks the approval process.</p>
<p>As changes to product data are promoted for approval, a designated workflow or process can be triggered automatically. The approvers for the specific information are notified automatically by the PDM system that the proposed changes are awaiting their approval.</p>
<p>As the change is processed, approval or disapproval is indicated electronically. After all steps in the approval process have been successfully completed, the approved product data are released at the next version level and stored in the vault. The product data have successfully followed the defined workflow process and other users will be notified that the version of the data has been updated.</p>
<p>Workflows can automatically route electronic folders of data or work packages, to reviewers either serially or concurrently. Additionally, workflow utilities can monitor processes ‐ ensuring one finishes before another starts ‐ and can provide management reporting.</p>
<p>The PDM system records each step in a process. Users and managers can review the complete change history at any time.</p>
</sec>
</sec>
<sec><title> Product structure management</title>
<p>Product structure management facilitates the creation and management of product configurations and bills of material. As configurations change over time, the PDM system tracks versions, effectivities and design variations. Typical product structures contain attribute, instance and location information, in addition to standard BOM data. Such data enhances the structure’s value for activities outside of manufacturing planning. Standard BOMs can be generated automatically from the product structure.</p>
<p>PDM systems allow users and applications to link or associate product definition data, such as drawings, documents and process plans, to parts and product structures. This allows users to determine easily which information will be affected by changes.</p>
<p>Remember, the product could be a unique plant such as an oil refinery, a utility’s pipe network system, a port facility, etc. Tracking the product structure of all such products is feasible and simplifies their design, construction, operation and maintenance. Product structure management can track physical components and their connections, or virtual objects such as a cooling system or an emergency escape procedure.</p>
<p>Different disciplines require unique views of product information. PDM systems allow views that can show structural relationships, manufacturing processes, documentation, financial, support and repair as well as other relationships embodied in product definition data.</p>
<p>Data for process and manufacturing planning is available in the PDM environment and may be transferred to MRP systems. The PDM system provides control and tracking of this data, just as it does of other product data.</p>
<p>MRP systems maintain and control vital information about a company’s product production. This information may be transferred into PDM systems, providing relevant data for the product development cycle.</p>
<sec><title>Classification</title>
<p>PDM classification functions provide much more efficient mechanisms for finding standard and similar parts than catalogues and other manual systems. When engineers and designers are able to find such parts easily, they are more likely to re‐use them instead of designing from scratch, with less “re‐invention of the wheel”.</p>
<p>Classification of parts allows similar or standard parts, processes and other design information to be grouped by common attributes and retrieved for use in products. This leads to greater product standardization, reduced re‐design, savings in purchasing and fabrication, and reduced inventories.</p>
<p>Parts can be grouped and found by various attributes. These may include part function code, shape classification, material, release date, revision, designer, or other parameters. These and other attributes, such as project, owner and creation date can be associated with other product data linked to the parts.</p>
<p>Parts and designs can be found that match specific attributes, ranges of attributes and logical combinations of attributes. Accordingly, users can easily identify products that are identical to, or similar to, a required design.</p>
<p>Standard libraries of parts such as fasteners, electronic components, pipe components, or building materials are available and can be accessed using similar mechanisms.</p>
</sec>
<sec><title>Project management</title>
<p>Project management provides work breakdown structures and allows resource scheduling and project tracking. Resources and managed data are combined to provide an added level of planning and tracking. These capabilities are frequently provided through links to third‐party project management systems. A key advantage stems from the ability to relate the WBS tasks to the PDM system’s knowledge of approval cycles and product configurations.</p>
<p>Tasks required to complete the project are ordered within the work breakdown structure, so resources and the project schedule can be monitored. As the project progresses from task to task, expended resources are recorded against the plan. Completion of the data required from each task is reported through the approval processes defined using workflow capabilities.</p>
</sec>
<sec><title>Communication and notification</title>
<p>On‐line, automated notification of critical events means that all personnel are informed regarding the current state of the project. Designers and others know as quickly as possible when product information is ready to be processed through the next task and which information is the most up to date.</p>
<p>Electronic mail is used to notify people about important events or required actions on‐line. Delays and misplaced communications are minimized. This mechanism may also be used to delegate activity when a user is unable to complete an assigned task.</p>
<p>A software mechanism known as a “trigger” is used to spawn notifications and other actions automatically. Almost any event in the product development process can cause a message to be sent or cause another event (such as the translation of data to another application) to occur. Triggers are used to streamline data vault and document management in addition to workflow and process management procedures.</p>
</sec>
<sec><title>Data transport</title>
<p>PDM systems keep track of data locations and allow users to access it knowing only a data set’s name. Such names are not limited by the local computer’s file‐naming conventions, so they can be more meaningful. In fact, the user need not know how to use the computer’s file and directory commands.</p>
<p>Moving data from one location to another, or from one application to another, is an operation that the PDM system performs ‐ users do not need to be concerned with operating systems and network commands.</p>
</sec>
<sec><title>Data translation</title>
<p>The system administrator can pre‐define data translators to be used to convert data between pairs of applications and to formats for various display and output devices. This allows enforcement of standard data forms. While translators may not be provided as an integral part of the PDM system, they may be applied because the system knows the data format of each controlled file and which translation is appropriate.</p>
<p>Triggers can cause data to be translated automatically from one application to another at appropriate times. Thus, the correct data is more likely to be used in any situation.</p>
</sec>
<sec><title>Image services</title>
<p>Raster, vector and video images are treated the same as any other data by the PDM system. Online access is provided to a wide range of previously difficult‐to‐distribute product data, providing this information in a structured manner to more users.</p>
<p>Raster and vector image viewing allows users such as managers and shopfloor workers to view drawings and other design data on PCs or terminals, enabling access to a wide audience. Mark‐up capabilities allow checkers, reviewers and approvers to add comments and annotations to raster images.</p>
<p>Image services accelerate processes such as engineering change requests and orders by facilitating the exchange of information and comments among users.</p>
</sec>
<sec><title>System administration</title>
<p>The administrator sets up the operational parameters of the PDM system and will typically monitor: <list list-type="bullet"><list-item><label>•</label>
<p>access and change permissions;</p>
</list-item>
<list-item><label>•</label>
<p>authorizations;</p>
</list-item>
<list-item><label>•</label>
<p>approval procedures;</p>
</list-item>
<list-item><label>•</label>
<p>data back‐up and security;</p>
</list-item>
<list-item><label>•</label>
<p>data archive.</p>
</list-item>
</list>
</p>
<p>Most systems can be tailored to conform to corporate standards and to improve the efficiency of operations for individual users. In addition to normal user interface customization, the operational features of PDM systems can be tailored. For instance, the approval process may be set to require sequential approval by several individuals in one case and to allow a majority vote of all approvers in another. Systems can be tailored in many ways, including: <list list-type="bullet"><list-item><label>•</label>
<p>user interface layout;</p>
</list-item>
<list-item><label>•</label>
<p>modification of system messages and terminology;</p>
</list-item>
<list-item><label>•</label>
<p>integration of third‐party applications;</p>
</list-item>
<list-item><label>•</label>
<p>addition of new functionality.</p>
</list-item>
</list>
</p>
<p>Many PDM systems provide off‐the‐shelf interfaces to popular applications such as AutoCAD, Pro/ENGINEER, Interleaf, and Microsoft Office. In addition, most systems offer interface toolkits, GUI builders and application interface toolkits.</p>
</sec>
<sec><title>PDM environments</title>
<p>In many organizations, product data is dispersed among computer systems and applications. To gain the fullest value from a PDM system, it must be able to deal with information across and among these systems.</p>
<p>Many types of computers (mainframes, mini‐computers, workstations, and PCs) are typically used during the product life cycle. These include systems used by engineering, manufacturing planning, shopfloor, purchasing, operations, administration and other parts of the organization. Their machines may or may not be connected in one or more wide‐ or local‐area networks. A fully developed PDM system will operate across these systems and networks. However, some software bridges may still be required to move information between incompatible systems.</p>
<p>PDM systems are designed to conform to a set of industry standards. These include IGES, TCP/IP, SQL, Motif, X‐Windows and other national and international standards, as well as the currently evolving PDES/STEP and CALS initiatives. In the case of CALS and STEP, the complete product life cycle is being addressed so that there will be a standard mechanism for sharing geometry, version, effectivity and other control information.</p>
<p>PDM systems have evolved to support process definition and control and to manage an end‐to‐end process. Some PDM systems allow users to define steps in their product life cycle, the tools to be used at each step and the rules governing movement of data between steps and tools. PDM systems are becoming a framework for the enterprise, not just for a subset such as E‐CAD. Initially, PDM systems will interface to discipline‐specific frameworks and incorporate them into the larger scope of the total product life cycle.</p>
<p>As for other software tools, the user interface of a PDM system is a key factor in how productive the tool will be. Because PDM systems are used by a diverse set of people with various computer skill levels, ease of use becomes a very important factor. Most interfaces are being or have been upgraded from old style on‐screen tables using command line input to modern Motif‐based graphical interfaces with menus, icons, dialogue boxes, drag and drop, and other easy‐to‐learn interaction methods. It is important that the interface is simple to learn and re‐learn (especially for casual or infrequent users), as well as tailorable so that different disciplines or classes of users including experienced “power” users can be supported efficiently.</p>
<p>PDM systems use a database management system to maintain meta‐data, product configuration, process and administrative information. Today, the majority of PDM systems employ relational database management systems. PDM system users are sheltered from the DBMS and its query language by the PDM system ‐ with the exception of system implementers, who are required to know and work with the underlying DBMS technology.</p>
<p>Some PDM systems are designed to operate with an object‐oriented database management system. As this technology becomes commonly accepted more systems will support it.</p>
<p>Many product development organizations are geographically distributed, with manufacturing or a plant in a different building, city, country, or continent from product design. Network interfaces allow these dispersed users to access data from common data stores and to communicate product changes as quickly and easily as if they were all working at the same location.</p>
<p>A server‐client architecture is used across a network to provide access to product data for multiple users. The server provides a controlled storage environment that all PDM users can access.</p>
</sec>
</sec>
<sec><title> Summary</title>
<p>PDM systems are an important tool for companies that create all kinds of products. PDM can have a dramatic and positive impact on time to market and product quality by supporting development methods that are faster and produce fewer errors.</p>
<p>Further information about PDM technology and products is available from my organization, CIMdata, which since its founding in 1983 has become a major resource in the application of computers throughout engineering, manufacturing and other disciplines. The company provides in‐depth market research and technical consulting for end‐users and system suppliers worldwide. Additionally, its expertise spans the spectrum of information systems and technologies used in industry, with particular emphasis on PDM and CAD/CAM. The company also produces the following series of publications about PDM to help potential users to justify, specify and select PDM systems: <list list-type="bullet"><list-item><label>•</label>
<p><italic>PDM Buyer’s Guide</italic>
defines the technology and reviews and compares many internationally available PDM products. This information is essential for all organizations that want to quickly identify products and PDM suppliers that are potentially able to meet their requirements.</p>
</list-item>
<list-item><label>•</label>
<p><italic>PDM Benefits Analysis Guide</italic>
provides a methodology and spreadsheet models for justifying the purchase of PDM systems and measuring their value throughout their implementation and use. Focusing on benefits in a structured way not only helps the decision‐makers, but it also ensures that needs will be properly identified, the best system for users will be found and that its operation will be in the best interests of the organization. It forces attention on needs, the users and the enterprise, rather than on computer technology.</p>
</list-item>
<list-item><label>•</label>
<p><italic>PDM Case Studies</italic>
is a service available by annual subscription that provides authoritative and in‐depth PDM case‐studies. These explain the secrets of how early implementers have identified needs, selected and implemented systems, the difficulties they experienced and overcame, the benefits found and the lessons they learnt. The case‐studies cover PDM applications in a range of industries and countries throughout the world, using different types of PDM systems.</p>
</list-item>
<list-item><label>•</label>
<p><italic>STEP Applications Guide</italic>
contains information about the current status of the STEP standard, products that support STEP and how this important product information definition and exchange standard affects PDM users.</p>
</list-item>
</list>
</p>
<p><italic>Note</italic>
: For further information, please call Mike Philpotts at CIMdata Ltd on 01203 441129; Stanley Port on 01483 421970; or see CIMdata’s Web‐site: <ext-link ext-link-type="uri" xlink:href="http://CIMdata.com">http://CIMdata.com</ext-link>
</p>
</sec>
</body>
</article>
</istex:document>
</istex:metadataXml>
<mods version="3.6"><titleInfo lang="en"><title>An introduction to the concepts, benefits and terminology of product data management</title>
</titleInfo>
<titleInfo type="alternative" lang="en" contentType="CDATA"><title>An introduction to the concepts, benefits and terminology of product data management</title>
</titleInfo>
<name type="personal"><namePart type="given">Mike</namePart>
<namePart type="family">Philpotts</namePart>
<affiliation>Business Consultant in Product Data Management, CIMdata Ltd, Coventry, UK</affiliation>
</name>
<typeOfResource>text</typeOfResource>
<genre type="other" displayLabel="e-viewpoint"></genre>
<originInfo><publisher>MCB UP Ltd</publisher>
<dateIssued encoding="w3cdtf">1996-06-01</dateIssued>
<copyrightDate encoding="w3cdtf">1996</copyrightDate>
</originInfo>
<language><languageTerm type="code" authority="iso639-2b">eng</languageTerm>
<languageTerm type="code" authority="rfc3066">en</languageTerm>
</language>
<physicalDescription><internetMediaType>text/html</internetMediaType>
</physicalDescription>
<abstract lang="en">Product data management PDM systems help to keep track of the masses of information needed to design, manufacture or build products and then to maintain them. They can be applied to a wide range of products and industries and across the whole spectrum of organizational functions. Benefits extend far beyond engineering design to include cost savings in manufacturing, reduced time to market and increased product quality. Defines and describes the type of features and functions that should be found in a PDM system and addresses the following data vault and document management workflow and process management product structure management classification project management communication and notification data transport and translation image services system administration and PDM environments.</abstract>
<subject><genre>Keywords</genre>
<topic>Database management</topic>
<topic>Databases</topic>
<topic>Process management</topic>
<topic>Product information</topic>
<topic>Product lifecycle</topic>
</subject>
<relatedItem type="host"><titleInfo><title>Industrial Management & Data Systems</title>
</titleInfo>
<genre type="Journal">journal</genre>
<subject><genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-ECO">Economics</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-LBEC">Labour economics</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-KS">Knowledge sharing</topic>
</subject>
<subject><genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-IKM">Information & knowledge management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-KMG cat-KM">Knowledge management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-KS">Knowledge sharing</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-KS">Knowledge sharing</topic>
</subject>
<subject><genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-IKM">Information & knowledge management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-ISYS">Information systems</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-KMG cat-KM">Knowledge management</topic>
</subject>
<subject><genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-MSOP">Management science & operations</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-LOG">Logistics</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-QMS">Quality management/systems</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-SCMT">Supply chain management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-SCIS">Supply chain information systems</topic>
</subject>
<identifier type="ISSN">0263-5577</identifier>
<identifier type="PublisherID">imds</identifier>
<identifier type="DOI">10.1108/imds</identifier>
<part><date>1996</date>
<detail type="volume"><caption>vol.</caption>
<number>96</number>
</detail>
<detail type="issue"><caption>no.</caption>
<number>4</number>
</detail>
<extent unit="pages"><start>11</start>
<end>17</end>
</extent>
</part>
</relatedItem>
<identifier type="istex">BFF38C6A204BD985CA34AC9818DBB760841F8C3B</identifier>
<identifier type="DOI">10.1108/02635579610117467</identifier>
<identifier type="filenameID">0290960403</identifier>
<identifier type="original-pdf">0290960403.pdf</identifier>
<identifier type="href">02635579610117467.pdf</identifier>
<accessCondition type="use and reproduction" contentType="copyright">© MCB UP Limited</accessCondition>
<recordInfo><recordContentSource>EMERALD</recordContentSource>
</recordInfo>
</mods>
</metadata>
<serie></serie>
</istex>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/OcrV1/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000D87 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000D87 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Ticri/CIDE |area= OcrV1 |flux= Istex |étape= Corpus |type= RBID |clé= ISTEX:BFF38C6A204BD985CA34AC9818DBB760841F8C3B |texte= An introduction to the concepts, benefits and terminology of product data management }}
![]() | This area was generated with Dilib version V0.6.32. | ![]() |