{"id":14785,"date":"2023-03-09T13:37:49","date_gmt":"2023-03-09T18:37:49","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/teamcenter\/?p=14785&preview=true&preview_id=14785"},"modified":"2026-03-26T08:58:14","modified_gmt":"2026-03-26T12:58:14","slug":"documentation-management-practice-2","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/teamcenter\/documentation-management-practice-2\/","title":{"rendered":"\ud83d\udcc4 Document management best practice in the digital thread"},"content":{"rendered":"\n
<\/div>\n\n\n\n

We all know the product lifecycle has gone digital.  However, that doesn\u2019t mean we\u2019ve removed the need for documentation in product lifecycles. Capturing and exchanging information in document form is still helpful, and in some cases, necessary. Examples include online product fact sheets, test procedures and results, specifications, and service execution feedback.<\/p>\n\n\n\n

Siemens Xcelerator is helping customers manage documents, with as much functionality is needed for each use case.\u00a0Here\u2019s a quick step by step decision and deploy process you can follow to take advantage of features available in every Teamcenter author license.<\/p>\n\n\n\n

\"Document<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Determine if you really need a document.  Are you collecting information that only needs to be available as a report?  Then check out the reporting functions available in Teamcenter<\/strong><\/a>. <\/p>\n\n\n\n

If you need to archive, exchange or deliver a document to other users, keep reading!<\/p>\n\n\n\n

<\/div>\n\n\n\n

Do I need a document?<\/h2>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
<\/div>\n\n\n\n
<\/div>\n\n\n\n
\n
Check out reporting capabilities<\/strong><\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n

Defining document behavior<\/h2>\n\n\n\n
<\/div>\n\n\n\n

To save users time, you need to define your documents. Without definition, you’re only storing a file.  Definition starts with two templates, object and file. These functions are building blocks, that can be used together or individually<\/strong>. Every document can be tailored to suit each use case. The best part is that these features are available to you in Teamcenter now!<\/strong><\/p>\n\n\n\n

The repository object templates<\/strong> are called DMTemplates. These define the behavior of documents. You can define your own naming conventions and required metadata for each.<\/p>\n\n\n\n

The file template<\/strong>, which is created in the native application defines the boilerplate content.<\/p>\n\n\n\n

Boost productivity and keep your document content consistent with them. Define the rules and make it easier for users to find the document in the future. <\/p>\n\n\n\n

Below is a optional deploy process you can follow. It features both document object and file templates.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Creating a document object template<\/h2>\n\n\n\n
<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Create a document object template<\/strong> to define the behavior of documents<\/strong>.<\/p>\n\n\n\n