How Word styles determine structure hierarchy in Teamcenter

You can create an entire requirement structure in one action by importing a specification document from Word. Teamcenter uses the document's Word heading styles to generate a new structure in the Systems Engineering Requirements view. Together, the sequence of heading styles and their numbered outline levels (1 through 9) determine the parent, child, and sibling hierarchy in the imported specification.

Example

Assume you create a requirement specification document with:

1. Word document name
2. Word Heading 1 style (outline level 1)
3. Word Heading 2 style (outline level 2)
4. Word Heading 2 style (outline level 2)
5. Word Heading 3 style (outline level 3)
6. Word Heading 3 style (outline level 3)

When you import this document, Teamcenter generates a matching specification in the Requirements view:

1. The name of the Word document becomes the name of the new requirement specification. By default, the requirement specification object occupies the top level of the structure.

   Tip: You can change the top-level object type by editing the TcAllowedImportExportPeakSpecObject preference.

2. The text of the first heading becomes the name of the first new requirement. The heading style's outline level places the requirement at the first level below the specification.

3. The text of the second heading becomes the name of the second new requirement, at the second level as a child of the first requirement.

4. The text of the third heading becomes the name of the third new requirement, at the second level as a sibling of the second requirement.

5. The text of the fourth heading becomes the name of the fourth new requirement, at the third level as a child of the third requirement.

6. The text of the fifth heading becomes the name of the fifth new requirement, at the third level as a sibling of the fourth requirement.

7. In the Number property column, each value matches the numbered outline level of that requirement's heading in the Word document.

All Word content below a given heading style becomes the content of the corresponding requirement. Requirement content can include elements such as graphics and tables.

Note: The Body Cleartext property column displays only the text portion of the content.

Caution: Special characters in Word heading styles are replaced by question marks (?) in the imported requirements. If those requirements later are exported to Word, the question marks are included in the output document.

If the document does not begin with a Word heading style, the import process generates a requirement named NO TITLE immediately below the top-level object. This requirement receives all content from the beginning of the document to the first Word heading style, or the entire content if there is no heading style.