TeamcenterKnowledge

Developing requirements > Unstructured (flat file) import

Example: Configuring identifier tags for requirement objects and trace links

You customize the flat file configuration file for Word to set the PrimaryKeyword to the [[]ID:ENG-FNC1-TSC[0-9]{1,}[]] regular expression and the SecondaryKeyword to the [[]CID:ENG-FNC1-FSR[0-9]{1,}[]] regular expression.

Using the Assign ID dialog box, you create a requirement revision identifier to define a requirement in the unstructured document:

  • Type is set to Requirement Revision
  • Prefix is set to ID
  • ID is set to ENG-FNC1
  • Name is set to TSC001

The resulting valid identifier for the paragraph revision is set to [ID:ENG-FNC1–TSC001].

You also assign the ID for the paragraph revision using the following values:

  • Type is set to Paragraph Revision
  • Prefix is set to CID
  • ID is set to ENG-FSC1
  • Name is set to FSR001

The resulting valid identifier for the paragraph revision is set to [CID:ENG-FNC1–FSR001].

The unstructured document now contains the two identifiers:

[ID:ENG-FNC1–TSC001]
[CID:ENG-FNC1–FSR001]

Related Topics

  • Assign identifiers for new requirement objects in the unstructured document

Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.plm00038/xid851175 · retrieved Fri Jul 10 2026 00:00:00 GMT+0000 (Coordinated Universal Time)