DITA (Darwin Information Typing Architecture) is one of the most widely used information models for authoring and publishing data in XML. Originally introduced for software documentation, the standard has been continually developed to cover other sectors like the machinery industry as well. DITA is a file-based architecture, but can also be used in content management systems. The current version of the standard is DITA 1.3.
With its latest release issued in October 2017, Technical Publishing supports the use of DITA 1.3. An implementation of the standard’s Technical Content Edition has been included in the pre-configured administration package, which can be used to set up a new installation of the system. It is, however, also possible to implement the DITA 1.3 DTDs in an existing configuration if you have upgraded to Technical Publishing 2.6.
DITA 1.3 Troubleshooting topicsDITA 1.3 opens a number of new possibilities for Technical Publishing authors. Most significant is a new topic type for troubleshooting. Aimed at providing help in case of known problems, the topic starts by describing an undesired behavior as experienced by the user (condition). Following that, the reason for this behavior is explained (cause) and the user is told what to do to solve the issue (remedy). As the initial condition can be the symptom of several problems, multiple causes and remedies are allowed. In addition to the new topic type, troubleshooting information can also be embedded in tasks and descriptions.
Another important feature available is the hazardstatement element. Introduced with DITA 1.2, the element is designed to contain warning information based on ANSI Z535 and ISO 3864. In accordance with these and other regulations, authors can select the severity and specify the type of the hazard in question (typeofhazard). DITA hazard elementIt is possible to add a graphic representing the hazard (hazardsymbol) and describe the consequences of failing to avoid it (consequence). How this is done is described in one or more short instructions (howtoavoid). The new element can be used to replace the note element where something more standardized is required.
DITA 1.3 also introduces a number of new domains like MathML or SVG. These are designed to enable specialized markup and provide numerous elements to include the respective content. Some new features are not supported in Technical Publishing. Scoped keys and branch filtering, for example, are based on authoring DITA maps, and the latter is somewhat redundant with classification functionality. Teamcenter Technical Publishing provides mechanisms for both, which can be done automatically in the system, without editing the XML.
About the author:
Helmut Hinck is a technical writer and internal consultant with several years of experience in Teamcenter Technical Publishing. His focus is on simplifying intricate user tasks and promoting the user perspective in complex IT environments.
Cost estimators and other decision makers need accurate information for decision-making and they need this information earlier than ever. To address these needs we continuously improve our solution for Product Cost Management. The new version 8.2 provides enhanced capabilities which supports manufacturers to increase visibility of cost drivers in the early stages of product development, helping them to avoid costly engineering rework downstream before the start of production.
To avoid a manually executed synchronization by cost engineers, which is very time consuming and error prone, the new version provides a new capability to update BOMs (bill of materials), BOPs (work plans) and BOEs (plant resources such as tools and machines) within Teamcenter product cost management at a glance. These synchronization activities can be automated and cost engineers can focus on value adding activities as calculation, controlling, and analysis of cost drivers.
Improved calculation efficiency through automations in Excel or web service import
The new version provides several enhancements to increase automation during the data import stage which consequently results in efficiency improvements for cost engineers.
Possibility to save calculation results as master data material
Cost calculation can now be saved or “published” as a master data material; and therefore, improve the calculation re-use and automation.
Increased flexibility of calculation engine to support further use cases
OEM’s and suppliers demand more precise and transparent costing to be better prepared for negotiations with customers or suppliers and have a better understanding of underlying cost drivers. As a result, the new version 8.2 includes additional direct material cost types to support a more specific calculation and roll-up of product or commodity costs.
Increased consistency with the improved validation framework
Validation is an important part of Teamcenter product cost management to ensure consistency and avoid errors by showing corresponding warning or an error message. With the improvement of this capability, hard-coded validation was replaced with the possibility to generate custom specific validations.
Custom terminology for more consistency within calculations
Possibility to re-name fields to reflect custom terminology by generating a company or even department specific terminology as a parallel structure to the Teamcenter product cost management terminology.
Consistent and reliable tool cost estimates through advanced feature recognition with NX Feature2Cost
The new module NX Feature2Cost supports OEMs, suppliers and tool makers in the tool costing process. It recognizes important geometrical information like general part dimensions, ribs, undercuts, bends, etc. and drives them into actual cost drivers. In case of analysis, Teamcenter product cost management can start NX, pass a geometry file and wait for the result after further interaction of the user with NX. NX provides two feature recognition modules, NX Feature2Cost Molding and NX Feature2Cost Stamping. These modules are able to automatically analyze the geometry file, provide capabilities to manually modify the feature recognition and corresponding cost drivers and then pass them back to Teamcenter product cost management. Within, there are a crucial input into the actual tool cost calculation which is carried out based on existing capabilities within Teamcenter product cost management.
Looking for easier PLM administration tools? Did you know the Teamcenter Deployment Center can deploy your custom software in just three easy steps?
Your BMIDE templates are already capable of being installable through the Teamcenter Environment Manager (TEM). Let me show you how you can enable the same BMIDE template to be installable through the Deployment Center. (For an overview of Deployment Center, take a look at my last blog, "Easy PLM? Take a closer look at Deployment Center.")
Step 1: Download
First, download the Deployment Center from Doc Center (customer-only access). Follow the Deployment Center user guide to get it installed, and drop Teamcenter software into the software repository. See the guide for information on the versions of Teamcenter supported by the Deployment Center.
Step 2: Create 3 XML Files
Next, locate the “Deployment Center Configuration Guide.docx” located in the Deployment Center download in the “\additional_tools\Teamcenter\Samples” directory. This guide explains how to configure your existing BMIDE template to be supported through Deployment Center. It will require you to create 3 XML files. Note that this step only has to be performed once for each BMIDE template. The configuration guide also lists a couple of sample software packages that can be found in the same “additional_tools\Teamcenter\Samples” directory.
Step 3: Add Package to Repository
Finally, after you finish with the XML configuration, you can drop your software package into the Deployment Center’s repository, just like you do for the Active Workspace software, and then use the Deployment Center to configure the install. It’s that easy!