In the customization of Instrumentation & Wiring tokens, templates and wiring diagrams the question comes to mind:
How does the data from the Plant Project Database go via the template onto the actual newly created drawing?
Data is passed thru the template into the new drawing created using System Queries. These queries temporarily hold data and are rebuilt as loops are generated. They are the containers for data storage while the drawings are being generated.
All System Queries labled DOCTOKENS are designed to extract specific tokens. The following list defines what type of token is pulled from each query:
Query NameTokenDoctokens1lineSingle line queryDoctokensCoreConCable core connectivity queryDoctokensDevice Associated with Motor Schematics &endash; Device related informationDoctokensDeviceTermAssociated with Motor Schematics &endash; Device termination dataDoctokensEquipAssociated with Motor Schematics &endash; Equipment related informationDoctokensEquipTermAssociated with Motor Schematics &endash; Equipment termination dataDoctokensLoopDetailed loop related informationDoctokensLoopConAuto-generated loop drawingsDoctokensLoopExtExtension of detailed loop related information (i.e., DoctokensLoop)DoctokensMotorAssociated with Motor Schematics &endash; Motor related informationDoctokensMotorControlAssociated with Motor Schematics &endash; Motor control related informationDoctokensMotorLoopAssociated with Motor Schematics &endash; Motor loop related informationDoctokensMotorTermAssociated with Motor Schematics &endash; Motor termination dataDoctokensPanelTermPanel terminations &endash; panel templatesDoctokensReg&RevAll revision related informationDoctokensStreamInstrument template process informationDoctokensTermConTermination related data
All System Queries with CON on the end indicates that the tokens are used in the auto-generated drawing queries.
Tokens are assigned prefixes which will indicate which type of information it is trying to pull. The following is a list of the token prefixes:
Token Prefix Information TypeIInstrumentsRRevisionsDDeviceMMotor, MCCTMulti Tstrip Terminations
In addition to the prefixes, the REG_APP field from the DOC_REG table will also direct the software as to which query to open up. The following is a list of the REG_APPs:
Reg_AppDocTokenQuery opened by DefaultJoinKEYTAGInstr-LoopPROJECT;REG&REV;INSTR;LOOPCON;LOOP;MOTOR;EQUIPLOOP_IDElect-1LinePROJECT;REG&REV;1LINEDOC_IDElect-3LinePROJECT;REG&REV;LOOPCON;MOTOR;DEVICE;MOTORTERM;DEVICETERM;
MOTORCONTROL;EQUIP;EQUIPTERMLOOP_IDInstr-TermPROJECT;REG&REV;TERMCONPANEL_IDCable-CorePROJECT;REG&REV;CORECONCABLE_IDPanel-TermPROJECT;REG&REV;PANELTERMPANEL_IDHkupsPROJECT;Query for tag type in RebisView tableTag_TypeDsheetsPROJECT;Query for tag type in RebisView tableTag_TypeSsheetsPROJECT;Query for tag type in RebisView tableTag_Type
The token structure has changed from the previous Instrumentation version. The following diagram shows the relationship of the previous token structure as related to the new token structure:
The new structure of the software has removed the need for column designations. Because of this new structure, the old tokens which referred to the columns A, J, K, W&ldots; are obsolete. The new structure will be as follows: (&) or (_) + Token Prefix + Order number + Connection Position + Row number + separator (.) + token (field name from query). The (&) or (_) has to be placed in the token structure as it was in the previous version. The (_) has to be used in tokens for Excel, but both will work for AutoCAD. The order number will be found in the Loop’s Instrument Properties in the ORD field. The position an item is found in the Layout Designer when you open the Detail Connections window and edit the loop in question. The headers will show the position the token is using. The row number relates back to the row that the Instrument is sitting on. The separator will indicate that the data has been defined in the query and all that is required now is the token itself which is the field from the defined query.
The DoctokensPanelTerm query is structured slightly different, because a Panel can contain multiple Tstrips the structure is as follows: Token Prefix (T) + Tstrip Number + Separator (_) + Row Number, where Tstrip Number = Tstrip.ORD and Row Number = Term.Row_pos. The Query is constructed to return all Incoming &endash; Current (Panel Tstip’s) &endash; Outgoing information as shown below: