[FUN] Control System Documentation

[Stephen Mitschke]

Dear Mr. Raynor,Your configuration tool keeps track of what block is executed where in thedistributed architecture. You can first design your control strategyregardless of in what device the block will ultimately be executed, andlater assign it to a transmitter, shared central controller, or a positioneretc. The configuration tool can generate the cross-reference of what blockis where and what parameter has been altered etc. We (Smar) make a tool thatcan both print this info and export it to Excel or any ODBC compliantdatabase. If you pass me your email address I can send a sample to you.Best regards,Jonas Berge, Smar Singapore

[Stephen Mitschke]

Dear All,Besides many other activities I also direct the Fieldbus program within INtools, directly involved with development.You are welcome to send me any questions or features that you would like to have in INtools that will support your daily design or documentation activities.Currently, INtools Foundation Fieldbus functionality includes the following:1. Ability to create Fieldbus Instruments2. We provide a list of the Standard Foundation function blocks which can be associated to an instrument3. The user can create new custom function blocks and Associate them to instruments4. Support different wiring methods and topologies of the fieldbus trunk cables and the spurs, either conventional screw terminal strips or plug and socket connectors are supported.5. Creation of Fieldbus segments and associate user defined design rules such as maximum number of devices on a segment, maximum cable lengths, maximum currents, voltage drops, capacitance, etc6. Validation reports that validate your segment wiring design against the rules7. Generation of Data driven segment wiring reports and loop drawings8. Filedbus data sheets9. Revision control of all of these documents and reportsWith regards to implementation of the control strategy across the instruments. Traditionally, the control design has been assigned as DCS and their configuration tools. And as this was the situation, and still it is so, INtools does not support designing the control strategy in the software, the only item that we handle in this matter is to associate function blocks to instruments- as this is part of the instrument specifications that Vendors need to know what are the user requirement, and not because the need to start interconnecting function blocks within an instrument to perform the control.If there will be such a requirement from our users to do it in INtools we may consider that.For your information, we are working on developing an interface with Delta V, targeting it for version 6.0 of INtoolsMeir StehnIntergraph/INtools

[Stephen Mitschke]

Ian,We in SPDC are using for most of the projects INTools version 5.1 or higher.That engineering tool has also the capability for foundation Fieldbuswiring. The revision control is done in that program. This tool is adatabase for the instrumentation part of the project. All specifications,instrument indexes, alarm trip and setting list, junction box drawings,configuration information, loop sheets are produced by that system. Most ofthe well known Process control vendors can import data for theirconfiguration from that data base. Also calculations and may other thingscan be done and is a part of the modular software.RegardsJisk KronemeijerInstrument and Process control & Automation engineer

[tapas]

Is there any future plan of Intergraph/Intools to develop a builtin tool to check FF consistency check if loop is configured for segments designed for sharing Funtionblocks among devices.

considering at your disposal are EDDL,EXTERNAL EDITOR ,INTREPRETOR,CFF,HIST LIST,WEB SERVICE.

Please reply e-mail:tapas@daresd.com (in case I don't come back here often)