Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Technical data management system
open-in-new
<h2 id="constituents-of-a-technical-data-management-system">Constituents of a technical data management system</h2> <p>Technical data refers to both scientific and technical information recorded and presented in any form or manner (excluding financial and management information).<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> A Technical Data Management System is created within an organisation for archiving and sharing information such as <a href="/facts/Technical_specifications/xEMUsktp">technical specifications</a>, datasheets and drawings. Similar to other types of data management system, a Technical Data Management System consists of the 4 crucial constituents mentioned below. </p> <h3>Data planning</h3> <p>Data plans (long-term or short-term) are constructed as the first essential step of a proper and complete TDMS. It is created to ultimately help with the 3 other constituents, data acquisition, data management and data sharing. A proper data plan should not exceed 2 pages and should address the following basics:<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p> <ul><li>Types of data (samples, experiment results, reports, drawings, etc.) and <a href="/facts/Metadata/qt35z79C">metadata</a> (data that summarizes and describes other data. In this case, it refers to details such as sample sizes, experiment conditions and procedures, dates of reports, explanations of drawings, etc.)<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li> <li>Means of researches and collections of data (field works, experiments in production lines, etc.)</li> <li>Costs of researches</li> <li>Policies for access, sharing (re-use within the organisation and re-distribution to the public)</li> <li>Proposals for archiving data and maintaining access to it</li></ul> <h3>Data acquisition</h3> <p>Raw data is collected from primary sites of the organisations through the use of modern technologies.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> Please reference the table below for examples.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p> <table><tbody><tr><th>Organisations</th><th>Raw Data</th><th>Primary Sites</th><th>Technologies</th></tr><tr><td>Integrated steel plants, automobile factories</td><td>Feasibility reports, equipment datasheets, etc.</td><td>Test rigs and controls</td><td>Transiting software to digitize data and input software for recording report results and details on datasheets</td></tr><tr><td>Aero-space facilities</td><td>Engineering drawings, operation manuals, maintenance logs, etc.</td><td>Engineering labs</td><td>Scanners for engineering drawings, Input software for maintenance logs</td></tr><tr><td>City corporations</td><td>Survey maps, population reports, etc.</td><td>City to be mapped and city that involves the research</td><td>Digital cameras for survey maps, Input software for statistics of population</td></tr></tbody></table> <p>The data collected is then transferred to technical data centres for data management. </p> <h3>Data management</h3> <p>After data acquisition, data is sorted out, whilst useful data is archived, unwanted data is disposed. When managing and archiving data, the features below of the data are considered.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> </p> <ul><li>Names, labels, values and descriptions for variables and records. (In the case of TDMS, one example is names of equipments on an equipment datasheet)</li> <li>Derived data from the original data, with code, algorithm or command file used to create them. (In the case of TDMS, one example is an expectation report derived from the analysis of an equipment datasheet)</li> <li><a href="/facts/Metadata/qt35z79C">Metadata</a> associates with the data being archived</li></ul> <h3>Data sharing</h3> <p>Archived and managed data are accessible to rightful entities. A proper and complete TDMS should share data to a suitable extent, under suitable security, in order to achieve optimal usage of data within the organisation. It aims for easy access when reused by other researchers and hence it enhances other research processes. Data is often referred in other tests and <a href="/facts/Specification_(technical_standard)/xEMUsktp">technical specifications</a>, where new analysis is generated, managed and archived again. As a result, data is flowing within the organisation under effective management through the use of TDMS.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p> <h2 id="advantages-and-disadvantages-of-usage-of-technical-data-management-systems">Advantages and disadvantages of usage of technical data management systems</h2> <p>There are strengths and weakness when using technical data management systems (TDMS) to archive data. Some of the advantages and disadvantages are listed below.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a><a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a><a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p> <h3>Advantages</h3> <h4>1. Faster and easier data management</h4> <p>Since TDMS is integrated into the organisation's systems, whenever workers develop data files (<a href="/facts/SolidWorks/TunrvoWl">SolidWorks</a>, <a href="/facts/AutoCAD/c83IAlgP">AutoCAD</a>, <a href="/facts/Microsoft_Word/HPSu5W4j">Microsoft Word</a>, etc.), they can also archive and manage data, linking what they need to their current work, at the same time they can also update the archives with useful data. This speeds up working processes and makes them more efficient. </p> <h4>2. Increased security</h4> <p>All data files are centralized, hence internal and external data leakages are less likely to happen, and the data flow is more closely monitored. As a result, data in the organisation is more secured. </p> <h4>3. Increased collaboration within the organisation</h4> <p>Since the data files are centralized and the data flow within the organisation increases, researchers and workers within the organisation are able to work on joint projects. More complex tasks can be performed for higher yields. </p> <h4>4. Compatible to various formats of data</h4> <p>TDMS is compatible to many formats of data, from basic data like Microsoft Words to complex data like voice data. This enhances the quality of the management of data archived. </p> <h3>Disadvantages</h3> <h4>1. Higher financial costs</h4> <p>Implementing TDMS into the organisation's systems involves monetary costs. Maintenance costs certain amount of human resources and money as well. These resources involve opportunity costs as they can be utilized in other aspects. </p> <h4>2. Lower stability</h4> <p>Since TDMS manages and centralizes all the data the organisation processes, it links the working processes within the whole organisation together. It also increases the vulnerability of the organisation data network. If TDMS is not stable enough or when it is exposed to hacker and virus attacks, the organisation's data flow might shut down completely, affecting the work in an organisation-wide scale and leading to a lower stability as results. </p> <h2 id="comparison-between-traditional-data-management-approaches-and-technical-data-management-systems">Comparison between traditional data management approaches and technical data management systems</h2> <p>Test engineers and researchers are facing great challenges in turning complex test results and simulation data into usable information for higher yields of firms. These challenges are listed below.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> </p> <ul><li>Increase in complication of designs</li> <li>Reduced in time and budgets available</li> <li>Higher quality is demanded</li></ul> <h3>Traditional data management approaches</h3> <p>Many organisations are still applying the conventional file management systems, due to the difficulty in building a proper and complete archives for data management. </p><p>The first approach is the simple file-folder system. This costs the problem of ineffectiveness as workers and researchers have to manually go through numerous layers of systems and files for the target data. Moreover, the target data may contain files with different formats and these files may not be stored in the same machine. These files are also easily lost if renamed or moved to another location. </p><p>The second approach is conventional databases such as Oracle. These databases are capable of enabling easy search and access of data. However, a great drawback is that huge effort for preparing and modeling the data is required. For large-scale projects, huge monetary costs are induced, and extra IT human resources must be employed for constant handling, expanding and maintaining the inflexible system, which is custom for specific tasks, instead of all tasks. In the long-term, it is not cost-effective. </p> <h3>Technical data management systems (TDMS)</h3> <p>TDMS is developed based on 3 principles, flexible and organized file storage, self-scaling hybrid data index, and an interactive post-processing environment. The system in practical, mainly consists of 3 components, data files with essential and relevant <a href="/facts/Metadata/qt35z79C">Metadata</a>, data finders for organizing and managing data regardless of files formats, and, a software of searching, analyzing and reporting. With <a href="/facts/Metadata/qt35z79C">metadata</a> attached to original data files, the data finder can identify different related data files during searches, even if they are in different file formats. TDMS hence allows researchers to search for data like browsing the Internet. Last but not least, it can adapt to changes and update itself according to the changes, unlike databases. </p> <h2 id="comparison-between-strong-information-systems-and-weak-information-systems">Comparison between strong information systems and weak information systems</h2> <p>Complex organizations may need large amounts of technical information, which can be distributed among several independent archives. Existing approaches span from "no integration" to "strong integration", that is based on a common database or product model. The so-called weak information systems (WIS)<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a> lie somewhere in the middle. Their basic concept is to add to the pre-existing information a new layer of multiple partial models of products and processes, so that it is possible to reuse existing databases, to reduce the development from scratch, and to provide evolutionary paths relevant for the development of the WIS. Each partial model may include specific knowledge and it acts as a way to structure and access the information according to a specific user view. The comparison between strong and weak information systems may be summarized as follows: </p> <table><tbody><tr><th>Strong information systems</th><th>Weak information systems</th></tr><tr><td><a href="/facts/Common_data_model/z2z9LppL">Common data model</a></td><td>Multiple specific integration models</td></tr><tr><td><a href="/facts/Database-centric_architecture/jApmmBGv">Database oriented architecture</a></td><td>Integration of multiple data sources by adding integration layers</td></tr><tr><td>One shot design</td><td>Growing process</td></tr><tr><td>Redesign of legacy systems</td><td>Integration of legacy systems</td></tr></tbody></table> <p>The architecture of a weak information system is composed of: </p> <ul><li>Information sources (databases, computational programs, etc.)</li> <li>The integration layer</li></ul> <p>The integration layer comprises the following sub-layers: </p> <ul><li>Abstraction layer (information models)</li> <li>Communication layer between models and information sources</li> <li>Communication layer between models and humans (human-computer interface)</li></ul> <h2 id="technical-data-management-systems-in-terms-of-regulations-in-different-countries">Technical data management systems in terms of regulations in different countries</h2> <p>In some countries, such as in the US, record and document management are considered very vital functions, and much stress is given in the management of Technical Archives. Records and documents coming under the public domain are governed by appropriate laws.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> However, this has not been so in many underdeveloped and <a href="/facts/Developing_country/eTfS4kxl">developing nations</a>. For example, India enacted the ' Public Records Act'<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> in 1993. However, many in the country are not aware of the existence of such a law or its importance. </p> <h2 id="applications-and-examples-of-technical-data-management-systems">Applications and examples of technical data management systems</h2> <p>Technical Data Management Systems (TDMS) are widely applied across the globe, in different sectors. Some of the examples are listed below. </p> <ul><li>Voith Hydro tests models of the power plant turbines, including 4 main program parts, engine characteristics values, oscillation and cavitation, and transfer data from 1 program part to the next one using TDMS.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a></li> <li>Danburykline created a knowledge and data platform, SOROS, which is following the wiki based approach. It aims to represent data in accessible and simple forms.<a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a></li> <li>Berghof develops and provides a TDMS to simplify and manage data for development of firms including automobile firms. This TDMS enables reserve of data, centralization of data volumes on an online server. It is also compatible to Windows PC and many other systems.<a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a></li></ul> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Data_management_system/V9a08NTg">Data management system</a></li> <li><a href="/facts/Data_mining/AH53q5ac">Data mining</a></li> <li><a href="/facts/Database/VYcpkevb">Database</a></li> <li><i><a href="/facts/Information_Systems_Research/cqSpB5V5">Information Systems Research</a></i>, an academic journal about information systems and information technology</li></ul> <p><a href="https://www.astera.com/type/blog/data-management-software/">Data management solutions</a> are tools and technologies that organizations use to manage their data. These solutions can include a wide range of different tools and technologies, such as databases and data warehouses, data integration and ETL (extract, transform, load) tools, data governance and quality tools, and data visualization and reporting tools. Data management solutions can help organizations store, organize, and manage their data in a more effective and efficient manner. They can also help to improve the accuracy and reliability of the data that is used to make important decisions and enable organizations to gain insights from their data more easily. </p> <h2 id="further-reading">Further reading</h2> <ul><li>Traina Junior, Caetano; Cordeiro, Robson L. F.; Amo, Sandra de; et al., eds. (February 2015). <a href="https://web.archive.org/web/20160604031753/https://seer.lcc.ufmg.br/index.php/jidm">"JOURNAL OF INFORMATION AND DATA MANAGEMENT"</a>. <i>Journal of Information and Data Management</i>. 6 (1). <a href="/facts/ISSN_(identifier)/DPAflDvU">ISSN</a> <a href="https://search.worldcat.org/issn/2178-7107">2178-7107</a>. Archived from <a href="https://seer.lcc.ufmg.br/index.php/jidm">the original</a> on 2016-06-04. Retrieved 2015-11-03.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"What is technical data? Definition and meaning". BusinessDictionary.com. WebFinance, Inc. 2015-11-03. Retrieved 2015-11-03. <a href="http://www.businessdictionary.com/definition/technical-data.html" target="_blank">http://www.businessdictionary.com/definition/technical-data.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"Data planning". Data Curation. Penn State University Libraries. 2015-11-03. Retrieved 2015-11-03. <a href="https://www.libraries.psu.edu/psul/pubcur/what_is_dm.html#data-planning" target="_blank">https://www.libraries.psu.edu/psul/pubcur/what_is_dm.html#data-planning</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Rouse, Margaret (July 2014). "metadata". WhatIs.com. Search engine optimization (SEO). Retrieved 2015-11-03. <a href="http://whatis.techtarget.com/definition/metadata" target="_blank">http://whatis.techtarget.com/definition/metadata</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Finkl, Karl (2015-11-03). "By using powerful default components, TDM, NI DataFinder, and DIAdem, and without using a database, we considerably reduced our creation and maintenance costs". National Instruments. a-solution GmbH. Retrieved 2015-11-03. <a href="http://sine.ni.com/cs/app/doc/p/id/cs-13019#" target="_blank">http://sine.ni.com/cs/app/doc/p/id/cs-13019#</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Finkl, Karl (2015-11-03). "By using powerful default components, TDM, NI DataFinder, and DIAdem, and without using a database, we considerably reduced our creation and maintenance costs". National Instruments. a-solution GmbH. Retrieved 2015-11-03. <a href="http://sine.ni.com/cs/app/doc/p/id/cs-13019#" target="_blank">http://sine.ni.com/cs/app/doc/p/id/cs-13019#</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"Data Management". Data Curation. Penn State University Libraries. 2015-11-03. Retrieved 2015-11-03. <a href="https://www.libraries.psu.edu/psul/pubcur/what_is_dm.html#data-management" target="_blank">https://www.libraries.psu.edu/psul/pubcur/what_is_dm.html#data-management</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Data Sharing". Data Curation. Penn State University Libraries. 2015-11-03. Retrieved 2015-11-03. <a href="https://www.libraries.psu.edu/psul/pubcur/what_is_dm.html#data-sharing" target="_blank">https://www.libraries.psu.edu/psul/pubcur/what_is_dm.html#data-sharing</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"Product Data Management and Product Lifecycle Management(PDM/PLM)". Razorleaf Solutions. Razorleaf Corporation. 2019-08-16. Retrieved 2019-08-16. <a href="https://www.razorleaf.com/plm-services/core-services/plm-implementation/product-data-management/" target="_blank">https://www.razorleaf.com/plm-services/core-services/plm-implementation/product-data-management/</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>Ahmed, Zeeshan; Gerhard, Detlef (2015-11-03). "Contributions of PDM Systems in Organiza- tional Technical Data Management". arXiv:1008.1321 [cs.OH]. <a href="/wiki/ArXiv_(identifier)" target="_blank">/wiki/ArXiv_(identifier)</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>"Calcium - technical data management". Flow Simulation. Flow Simulation Ltd. 2015-11-03. Retrieved 2015-11-03. <a href="http://www.flosim.com/calcium.aspx" target="_blank">http://www.flosim.com/calcium.aspx</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>"From Raw Data to Engineering Results: The NI Technical Data Management Solution". National Instruments. 2015-10-13. Retrieved 2015-11-03. <a href="http://www.ni.com/white-paper/7389/en/" target="_blank">http://www.ni.com/white-paper/7389/en/</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>Salvaneschi, Paolo; Lazzari, Marco (1997). Weak information systems for technical data management (PDF). Worldwide ECCE Symposium on computers in the practice of building and civil engineering. Lahti, Finland. pp. 310–314. Retrieved 2015-11-29. <a href="http://www.marcolazzari.it/publications/weak-information-systems-for-technical-data-management-preprint.pdf" target="_blank">http://www.marcolazzari.it/publications/weak-information-systems-for-technical-data-management-preprint.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>Best, Steven J.; Foster, Debbie (January 2009). "Document Management in the Digital Law Office". Law Practice Today. American Bar Association. Retrieved 2015-11-03. <a href="http://apps.americanbar.org/lpm/lpt/articles/tch01093.shtml" target="_blank">http://apps.americanbar.org/lpm/lpt/articles/tch01093.shtml</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>MOHANPURIA, K.L. (1993-12-22). "THE PUBLIC RECORDS ACT, 1993 (India)". Government of India. Archived from the original on 2015-09-10. Retrieved 2015-11-03. <a href="https://web.archive.org/web/20150910172723/http://nationalarchives.nic.in/writereaddata/html_en_files/html/public_records93.html" target="_blank">https://web.archive.org/web/20150910172723/http://nationalarchives.nic.in/writereaddata/html_en_files/html/public_records93.html</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>Finkl, Karl (2015-11-03). "By using powerful default components, TDM, NI DataFinder, and DIAdem, and without using a database, we considerably reduced our creation and maintenance costs". National Instruments. a-solution GmbH. Retrieved 2015-11-03. <a href="http://sine.ni.com/cs/app/doc/p/id/cs-13019#" target="_blank">http://sine.ni.com/cs/app/doc/p/id/cs-13019#</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> <li id="fn:16"><p>"Knowledge & Technical Data Management". Danburykline. 2015-11-03. Retrieved 2015-11-03. <a href="http://danburykline.co.uk/DKWP/?page_id=967" target="_blank">http://danburykline.co.uk/DKWP/?page_id=967</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li> <li id="fn:17"><p>"Data availability". Test engineering Technical data management. Berghof. 2015-11-03. Retrieved 2015-11-03. <a href="http://www.berghof.com/en/products/test-engineering/technical-data-management/" target="_blank">http://www.berghof.com/en/products/test-engineering/technical-data-management/</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li> </ol>