File Structure
The relationship of product structure hierarchy to exported JT file structure is arbitrary. Any node in the hierarchy may be specified as the start of a new JT file. Thus, product structure may be represented in a variety of JT file configurations.
JT supports common product structure-to-file structure mappings. These include:
- Per part - All assembly nodes in a product structure hierarchy are stored in a single JT file, and each part node in the hierarchy is stored in an individual JT file in a subdirectory that is of the same name as the assembly JT file.
- Fully shattered - Each product structure node in the hierarchy is stored in an individual JT file.
- Monolithic - All product structure is stored in a single JT file.
- PLMXML - An open XML-based file format. A PLMXML-structure could link to the model data in another file (an External Representation), or the data can be embedded within the Representation element in the XML file (an InternalRepresentation).
Client applications may use these mappings, or choose to define their own custom mapping.
Read more about this topic: JT (visualization Format)
Famous quotes containing the words file and/or structure:
“While waiting to get married, several forms of employment were acceptable. Teaching kindergarten was for those girls who stayed in school four years. The rest were secretaries, typists, file clerks, or receptionists in insurance firms or banks, preferably those owned or run by the family, but respectable enough if the boss was an upstanding Christian member of the community.”
—Barbara Howar (b. 1934)
“A committee is organic rather than mechanical in its nature: it is not a structure but a plant. It takes root and grows, it flowers, wilts, and dies, scattering the seed from which other committees will bloom in their turn.”
—C. Northcote Parkinson (1909–1993)